From sense at ubuntu.com Mon Aug 2 07:07:06 2010 From: sense at ubuntu.com (Sense Hofstede) Date: Mon, 2 Aug 2010 09:07:06 +0200 Subject: Start of an Ayatana Debugging wiki page created Message-ID: Hello, When dealing with bugs in the Ayatana project and the people triaging them I've found that many people have troubles fully grasping what every bit does and what information would be useful. That's why I created , to have a place that explains all the different Ayatana projects, what uses what and where to report bugs for what. It also contains a start of the debugging information. I plan on extending this page in the future. If anyone has got more information, feel free to help and add your information. The page is now linked to from DebuggingProcedures and Ayatana on the wiki. Regards, -- Sense Hofstede http://sensehofstede.nl/ From noreply at ubuntu.com Sun Aug 1 17:58:51 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 01 Aug 2010 17:58:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=22_by_qense?= Message-ID: <20100801175851.2536.70600@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by qense: http://wiki.ubuntu.com/DebuggingAyatana The comment on the change is: Initial creation New page: #language en #title Debugging Ayatana <> The [[Ayatana]] project concerns several subprojects of a diverse nature. However, because it is developed within the same project by the same group of people within the same company and because they share components it is possible to give some general advise on debugging for results of Ayatana. ||<>|| = General Information = This section gives some general information on the different projects that make up [[Ayatana]]. == What is what == The umbrella project of [[Ayatana]] on Launchpad is ''[[https://launchpad.net/ayatana|ayatana]]'', but bugs shouldn't be reported against that. The first place to report bugs when using the packages from Ubuntu are the packages' source packages in Launchpad. || '''Own Launchpad project''' ||'''Ubuntu source package'''|| '''Description''' || || [[https://launchpad.net/indicator-application|Application Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-application|indicator-application]]''|| The indicator that shows the Application Indicators, as well as the library for allowing applications to register their Application Indicators. || || [[https://launchpad.net/indicator-appmenu|Application Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-appmenu|indicator-appmenu]]''|| The indicator that hosts the menus extracted from applications using ''appmenu-gtk' and ''appmenu-qt''. || || [[https://launchpad.net/appmenu-gtk|AppMenu GTK+]] ||''[[https://launchpad.net/ubuntu/+source/appmenu-gtk|appmenu-gtk]]''|| The GTK+ module that makes menus appear in the panel applet ''indicator-appmenu'', using GtkMenuProxy.|| || [[https://launchpad.net/bamf|BAMF]] ||''[[https://launchpad.net/ubuntu/+source/bamf|bamf]]''|| Provides a DBus daemon and a C library for matching application/window instances. Used by Unity to make sure every application appears only once in the launcher. || || [[https://launchpad.net/clutk|Clutter Toolkit]] ||''[[https://launchpad.net/ubuntu/+source/clutk|clutk]]''|| A Clutter toolkit library used by the Unity launcher. || || [[https://launchpad.net/indicator-datetime|Date and Time Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-datetime|indicator-datetime]]''|| The indicator that is a replacement for the clock applet, showing date and time, and a calendar. || || [[https://launchpad.net/dbusmenu|DBus Menu]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu|libdbusmenu]]''|| Library for passing GtkMenus over DBus. Used by vritually all Indicator projects. || || [[https://launchpad.net/evolution-indicator|Evolution Indicator]] ||''[[https://launchpad.net/ubuntu/+source/evolution-indicator|evolution-indicator]]''|| Uses ''libindicate'' to display an entry for Evolution in the Messaging Menu. || || [[https://launchpad.net/indicator-applet|Indicator Applet]] ||''[[https://launchpad.net/ubuntu/+source/indicator-applet|indicator-applet]]''|| The applet that contains the most important of the indicators. || || [[https://launchpad.net/libdbusmenu-qt|libdbusmenu-qt]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu-qt|libdbusmenu-qt]]''|| Whereas the regular DBus Menu library is for passing on GtkMenus over DBus, this library is for passing Qt menus over DBus. || || [[https://launchpad.net/libindicate|Libindicate]] ||''[[https://launchpad.net/ubuntu/+source/libindicate|libindicate]]''|| The library used by applications to appear in the Messaging Menu, although theoretically it could be used for other purposes as well. || || [[https://launchpad.net/libindicate-qt|libindicate-qt]] ||''[[https://launchpad.net/ubuntu/+source/libindicate-qt|libindicate-qt]]''|| The Qt bindings for ''libindicate''. || || [[https://.launchpad.net/libindicator|libindicator|Libindicator]] ||''[[https://launchpad.net/ubuntu/+source/libindicator|libindicator]]''|| The library for creating indicators, therefore used by all indicators. Also used by the Indicator Applet and the Session Menu to collect indicators they want to display, from a static list. || || [[https://launchpad.net/indicator-me|Me Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-me|indicator-me]]''|| The indicator that shows your username and provides for integration with your chat accounts and has a field for updating your microblogging status. || || [[https://launchpad.net/indicator-network|Network Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-network|indicator-network]]''|| The Connection Manager based network indicator, replacing nm-applet. For now only used in the Ubuntu Netbook Edition. || || [[https://launchpad.net/notify-osd|Notify OSD]] ||''[[https://launchpad.net/ubuntu/+source/notify-osd|notify-osd]]''|| The Notification Daemon from the [[Ayatana]] project. || ||[[https://launchpad.net/plasma-widget-menubar|Plasma Menu Bar]] ||''[[https://launchpad.net/ubuntu/+source/plasma-widget-menubar|plasma-widget-menubar]]''|| The Plasma menu bar for showing the Application Menus, extracted from applications by either appmenu-gtk or appmenu-qt, before being exported over DBus. || || [[https://launchpad.net/indicator-sound|Sound Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-sound|indicator-sound]]''|| The indicator for changing your volume and controlling your music player. || || [[https://launchpad.net/unity|Unity]] ||''[[https://launchpad.net/ubuntu/+source/unity|unity]]''|| The Ubuntu Netbook Edition's interface, providing a launcher, a top panel and a search interface. It doesn't use the Indicator Applet, but instead implements its own indicator displayer. Uses ''libbamf'' and ''libclutk''.|| === A note on the Indicator Applet === The Indicator Applet is the applet that shows all indicators on the panel. This is not limited to the Messaging Menu. It has several indicators is shows, like the Application Indicators (which is one), the Messaging Menu and the Sound Menu. The applet 'indicator-applet' includes just those three, the Session Indicator and the Me Menu are shown by a separate applet: 'indicator-session'. There is one applet that shows all: 'indicator-applet-complete' includes the indicators from 'indicator-applet' and 'indicator-session'. Please keep in mind that bugs should be reported against their indicator first, and only against the Indicator Applet when you're absolutely sure the problem lies there. == Where to look for information == User session logging is done in ''$XDG_CACHE_HOME'', by default ''$HOME/.cache'', by default ''~/.cache''. There are several files of interst in that directory, related to the [[Ayatana]] project: * indicator-applet.log * indicator-applet-appmenu.log * indicator-applet-complete.log * indicator-applet-session.log * notify-osd.log The directory ''$XDG_CACHE_HOME/indicators/'' contains the cached links to desktop files that were registered at the Message Indicator and the Sound Menu, respectively in ''$XDG_CACHE_HOME/indicators/messages/seen-db.keyfile'' and ''$XDG_CACHE_HOME/indicators/sound/familiar-players-db.keyfile''. The cache of Application Indicators, however, is located in the ''$XDG_CONFIG_HOME/indicators/application/lru-file.json'' file. == Watching DBus == The [[Ayatana]] projects make heavy use from DBus to communicate. Sometimes it is good to look at the DBus communications to learn more about what exactly is going on. Most Ayatana projects communication over the DBus SessionBus, so you want to use the command '''dbus-monitor --session''' to watch a live stream of the DBus communications. To prevent your console from being swamped by DBus communication from other applications, which can happen quite fast, you can specify what information you want. The command 'dbus-monitor "interface='org.ayatana.indicator.application.service'" --session' gives you all DBus communication sent from the ''org.ayatana.indicator.application.service'' DBus interface, which is all communication between the Application Indicators' registry and the actually Application Indicators indicator. If you want to see the communication between the application and the Application Indicators registry you should use 'dbus-monitor "interface='org.kde.StatusNotifierItem'" --session'. ---- CategoryAyatana CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Sun Aug 1 18:01:50 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 01 Aug 2010 18:01:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_qense?= Message-ID: <20100801180150.8584.68111@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by qense: http://wiki.ubuntu.com/DebuggingProcedures?action=diff&rev1=102&rev2=103 The comment on the change is: Added a link to the [[Ayatana]] project's debugging procedures ------------------------------------------------------------------------------ == Desktop Applications == + * [[DebuggingAyatana|Ayatana project]] * [[DebuggingFirefox|Firefox Web Browser]] * [[DebuggingEvince|Evince Document Viewer]] * [[DebuggingEvolution|Evolution Mail]] From noreply at ubuntu.com Mon Aug 2 08:22:49 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 02 Aug 2010 08:22:49 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=22_by_vish?= Message-ID: <20100802082249.24802.22032@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/DebuggingAyatana?action=diff&rev1=1&rev2=2 The comment on the change is: fixing markups ------------------------------------------------------------------------------ #title Debugging Ayatana <> - The [[Ayatana]] project concerns several subprojects of a diverse nature. However, because it is developed within the same project by the same group of people within the same company and because they share components it is possible to give some general advise on debugging for results of Ayatana. + The [[Ayatana]] project concerns several sub-projects of a diverse nature. However, because it is developed within the same project by the same group of people within the same company and because they share components it is possible to give some general advise on debugging for results of Ayatana. ||<>|| @@ -16, +16 @@ || '''Own Launchpad project''' ||'''Ubuntu source package'''|| '''Description''' || || [[https://launchpad.net/indicator-application|Application Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-application|indicator-application]]''|| The indicator that shows the Application Indicators, as well as the library for allowing applications to register their Application Indicators. || - || [[https://launchpad.net/indicator-appmenu|Application Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-appmenu|indicator-appmenu]]''|| The indicator that hosts the menus extracted from applications using ''appmenu-gtk' and ''appmenu-qt''. || + || [[https://launchpad.net/indicator-appmenu|Application Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-appmenu|indicator-appmenu]]''|| The indicator that hosts the menus extracted from applications using ''appmenu-gtk'' and ''appmenu-qt''. || - || [[https://launchpad.net/appmenu-gtk|AppMenu GTK+]] ||''[[https://launchpad.net/ubuntu/+source/appmenu-gtk|appmenu-gtk]]''|| The GTK+ module that makes menus appear in the panel applet ''indicator-appmenu'', using GtkMenuProxy.|| + || [[https://launchpad.net/appmenu-gtk|AppMenu GTK+]] ||''[[https://launchpad.net/ubuntu/+source/appmenu-gtk|appmenu-gtk]]''|| The GTK+ module that makes menus appear in the panel applet ''indicator-appmenu'', using {{{GtkMenuProxy}}}.|| || [[https://launchpad.net/bamf|BAMF]] ||''[[https://launchpad.net/ubuntu/+source/bamf|bamf]]''|| Provides a DBus daemon and a C library for matching application/window instances. Used by Unity to make sure every application appears only once in the launcher. || || [[https://launchpad.net/clutk|Clutter Toolkit]] ||''[[https://launchpad.net/ubuntu/+source/clutk|clutk]]''|| A Clutter toolkit library used by the Unity launcher. || || [[https://launchpad.net/indicator-datetime|Date and Time Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-datetime|indicator-datetime]]''|| The indicator that is a replacement for the clock applet, showing date and time, and a calendar. || - || [[https://launchpad.net/dbusmenu|DBus Menu]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu|libdbusmenu]]''|| Library for passing GtkMenus over DBus. Used by vritually all Indicator projects. || + || [[https://launchpad.net/dbusmenu|DBus Menu]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu|libdbusmenu]]''|| Library for passing {{{GtkMenus}}} over DBus. Used by virtually all Indicator projects. || - || [[https://launchpad.net/evolution-indicator|Evolution Indicator]] ||''[[https://launchpad.net/ubuntu/+source/evolution-indicator|evolution-indicator]]''|| Uses ''libindicate'' to display an entry for Evolution in the Messaging Menu. || + || [[https://launchpad.net/evolution-indicator|Evolution Indicator]] ||''[[https://launchpad.net/ubuntu/+source/evolution-indicator|evolution-indicator]]''|| Uses {{{libindicate}}} to display an entry for Evolution in the Messaging Menu. || || [[https://launchpad.net/indicator-applet|Indicator Applet]] ||''[[https://launchpad.net/ubuntu/+source/indicator-applet|indicator-applet]]''|| The applet that contains the most important of the indicators. || - || [[https://launchpad.net/libdbusmenu-qt|libdbusmenu-qt]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu-qt|libdbusmenu-qt]]''|| Whereas the regular DBus Menu library is for passing on GtkMenus over DBus, this library is for passing Qt menus over DBus. || + || [[https://launchpad.net/libdbusmenu-qt|libdbusmenu-qt]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu-qt|libdbusmenu-qt]]''|| Whereas the regular DBus Menu library is for passing on {{{GtkMenus}}} over DBus, this library is for passing Qt menus over DBus. || || [[https://launchpad.net/libindicate|Libindicate]] ||''[[https://launchpad.net/ubuntu/+source/libindicate|libindicate]]''|| The library used by applications to appear in the Messaging Menu, although theoretically it could be used for other purposes as well. || - || [[https://launchpad.net/libindicate-qt|libindicate-qt]] ||''[[https://launchpad.net/ubuntu/+source/libindicate-qt|libindicate-qt]]''|| The Qt bindings for ''libindicate''. || + || [[https://launchpad.net/libindicate-qt|libindicate-qt]] ||''[[https://launchpad.net/ubuntu/+source/libindicate-qt|libindicate-qt]]''|| The Qt bindings for {{{libindicate}}}. || || [[https://.launchpad.net/libindicator|libindicator|Libindicator]] ||''[[https://launchpad.net/ubuntu/+source/libindicator|libindicator]]''|| The library for creating indicators, therefore used by all indicators. Also used by the Indicator Applet and the Session Menu to collect indicators they want to display, from a static list. || || [[https://launchpad.net/indicator-me|Me Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-me|indicator-me]]''|| The indicator that shows your username and provides for integration with your chat accounts and has a field for updating your microblogging status. || || [[https://launchpad.net/indicator-network|Network Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-network|indicator-network]]''|| The Connection Manager based network indicator, replacing nm-applet. For now only used in the Ubuntu Netbook Edition. || || [[https://launchpad.net/notify-osd|Notify OSD]] ||''[[https://launchpad.net/ubuntu/+source/notify-osd|notify-osd]]''|| The Notification Daemon from the [[Ayatana]] project. || ||[[https://launchpad.net/plasma-widget-menubar|Plasma Menu Bar]] ||''[[https://launchpad.net/ubuntu/+source/plasma-widget-menubar|plasma-widget-menubar]]''|| The Plasma menu bar for showing the Application Menus, extracted from applications by either appmenu-gtk or appmenu-qt, before being exported over DBus. || || [[https://launchpad.net/indicator-sound|Sound Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-sound|indicator-sound]]''|| The indicator for changing your volume and controlling your music player. || - || [[https://launchpad.net/unity|Unity]] ||''[[https://launchpad.net/ubuntu/+source/unity|unity]]''|| The Ubuntu Netbook Edition's interface, providing a launcher, a top panel and a search interface. It doesn't use the Indicator Applet, but instead implements its own indicator displayer. Uses ''libbamf'' and ''libclutk''.|| + || [[https://launchpad.net/unity|Unity]] ||''[[https://launchpad.net/ubuntu/+source/unity|unity]]''|| The Ubuntu Netbook Edition's interface, providing a launcher, a top panel and a search interface. It doesn't use the Indicator Applet, but instead implements its own indicator displayer. Uses {{{libbamf}}} and {{{libclutk}}}.|| === A note on the Indicator Applet === - The Indicator Applet is the applet that shows all indicators on the panel. This is not limited to the Messaging Menu. It has several indicators is shows, like the Application Indicators (which is one), the Messaging Menu and the Sound Menu. The applet 'indicator-applet' includes just those three, the Session Indicator and the Me Menu are shown by a separate applet: 'indicator-session'. There is one applet that shows all: 'indicator-applet-complete' includes the indicators from 'indicator-applet' and 'indicator-session'. + The Indicator Applet is the applet that shows all indicators on the panel. This is not limited to the Messaging Menu. It has several indicators is shows, like the Application Indicators (which is one), the Messaging Menu and the Sound Menu. The applet ''indicator-applet'' includes just those three, the Session Indicator and the Me Menu are shown by a separate applet: ''indicator-session''. There is one applet that shows all: ''indicator-applet-complete'' includes the indicators from ''indicator-applet'' and ''indicator-session''. Please keep in mind that bugs should be reported against their indicator first, and only against the Indicator Applet when you're absolutely sure the problem lies there. == Where to look for information == - User session logging is done in ''$XDG_CACHE_HOME'', by default ''$HOME/.cache'', by default ''~/.cache''. + User session logging is done in {{{$XDG_CACHE_HOME}}}, [by default in {{{$HOME/.cache}}} or {{{~/.cache}}} ]. + - There are several files of interst in that directory, related to the [[Ayatana]] project: + There are several files of interest in that directory, related to the [[Ayatana]] project: * indicator-applet.log * indicator-applet-appmenu.log * indicator-applet-complete.log * indicator-applet-session.log * notify-osd.log - The directory ''$XDG_CACHE_HOME/indicators/'' contains the cached links to desktop files that were registered at the Message Indicator and the Sound Menu, respectively in ''$XDG_CACHE_HOME/indicators/messages/seen-db.keyfile'' and ''$XDG_CACHE_HOME/indicators/sound/familiar-players-db.keyfile''. + The directory {{{$XDG_CACHE_HOME/indicators/}}} contains the cached links to desktop files that were registered at the Message Indicator and the Sound Menu, respectively in {{{$XDG_CACHE_HOME/indicators/messages/seen-db.keyfile}}} and {{{$XDG_CACHE_HOME/indicators/sound/familiar-players-db.keyfile}}}. - The cache of Application Indicators, however, is located in the ''$XDG_CONFIG_HOME/indicators/application/lru-file.json'' file. + The cache of Application Indicators, however, is located in the {{{$XDG_CONFIG_HOME/indicators/application/lru-file.json}}} file. == Watching DBus == The [[Ayatana]] projects make heavy use from DBus to communicate. Sometimes it is good to look at the DBus communications to learn more about what exactly is going on. - Most Ayatana projects communication over the DBus SessionBus, so you want to use the command '''dbus-monitor --session''' to watch a live stream of the DBus communications. + Most Ayatana projects communication over the DBus Session-bus. To watch a live stream of the DBus communications use command : + {{{ + dbus-monitor --session + }}} - To prevent your console from being swamped by DBus communication from other applications, which can happen quite fast, you can specify what information you want. The command 'dbus-monitor "interface='org.ayatana.indicator.application.service'" --session' gives you all DBus communication sent from the ''org.ayatana.indicator.application.service'' DBus interface, which is all communication between the Application Indicators' registry and the actually Application Indicators indicator. - If you want to see the communication between the application and the Application Indicators registry you should use 'dbus-monitor "interface='org.kde.StatusNotifierItem'" --session'. + Using the above command your console will be swamped by DBus communication from other applications, which can happen quite fast.To prevent this you can specify what information you want. + + To only watch DBus communication sent from the {{{org.ayatana.indicator.application.service}}} DBus interface ,which is all communication between the Application Indicators' registry and the actual Application-Indicators indicator, use command : + {{{ + dbus-monitor "interface='org.ayatana.indicator.application.service'" --session + }}} + + If you want to watch the communication between the application and the Application Indicators registry use command : + {{{ + dbus-monitor "interface='org.kde.StatusNotifierItem'" --session + }}} ---- CategoryAyatana CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Mon Aug 2 18:39:36 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 02 Aug 2010 18:39:36 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_brian-murray?= Message-ID: <20100802183936.6972.84069@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=161&rev2=162 ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=uec-images|`uec-images`]] || This bug is related to the Ubuntu Enterprise Cloude (UEC) [[http://uec-images.ubuntu.com/releases|images]] || || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch|`patch`]] || This bug has a patch attached to it or contains a link to a patch || || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-needswork|`patch-needswork`]] || This bug has a patch attached to it that needs some work done on it || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-refused|`patch-refused`]] || This bug has a patch attached to it that was not included in Ubuntu || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected|`patch-rejected`]] || This bug has a patch attached to it that was not included in Ubuntu || || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-upstreaminput|`patch-upstreaminput`]] || This bug has a patch attached to it that has been forwarded upstream and requires their input or incorporation || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-upstream|`patch-forwarded-upstream`]] || This bug has a patch attached to it that has been forwarded upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-debian|`patch-forwarded-debian`]] || This bug has a patch attached to it that has been forwarded to debian || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-upstream|`patch-rejected-upstream`]] || This bug has a patch attached to it that has been rejected by upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-debian|`patch-rejected-debian`]] || This bug has a patch attached to it that has been rejected by debian || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-upstream|`patch-accepted-upstream`]] || This bug has a patch attached to it that has been accepted by upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-debian|`patch-accepted-debian`]] || This bug has a patch attached to it that has been accepted by debian || == Hardware Specific == From pik4387etrc at googlemail.com Tue Aug 3 06:23:21 2010 From: pik4387etrc at googlemail.com (ewqihn vhjnredli) Date: Tue, 3 Aug 2010 07:23:21 +0100 Subject: developing a free device driver Message-ID: My particular interest is to develope a free device driver for my wi-fi adapter, for which Ubuntu apparently uses a proprietary driver Where do I go to pursue this? Regards, Conrad Watkins -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Aug 3 19:36:05 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 03 Aug 2010 19:36:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_vish?= Message-ID: <20100803193605.30164.59075@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=297&rev2=298 The comment on the change is: we no longer have the menu item Help > Report a problem in stable releases. ------------------------------------------------------------------------------ == Bugs without a package == Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.<
>(With many applications, you can report a future bug directly on the appropriate package by opening the application's "Help" menu and choosing "Report a Problem". https://wiki.ubuntu.com/ReportingBugs)|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. For more information: https://wiki.ubuntu.com/ReportingBugs|| == Bugs resolved after update or config change == - Ocassionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. + Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. || This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.|| From noreply at ubuntu.com Tue Aug 3 20:00:41 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 03 Aug 2010 20:00:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_vish?= Message-ID: <20100803200041.5352.90713@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=298&rev2=299 The comment on the change is: use the direct link than a re-direct ------------------------------------------------------------------------------ == Bugs without a package == Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. For more information: https://wiki.ubuntu.com/ReportingBugs|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. For more information : https://help.ubuntu.com/community/ReportingBugs|| == Bugs resolved after update or config change == Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. From webmaster at ubuntu.com Tue Aug 3 19:56:32 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Tue, 03 Aug 2010 19:56:32 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_vish?= Message-ID: <20100803195632.23753.45077@acerola.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The following page has been changed by vish: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=138&rev2=139 The comment on the change is: we no longer have the menu item Help > Report a problem in stable releases, moving it lower down ------------------------------------------------------------------------------ Note 2: After the bug is reported, please '''always''' leave the Status set to ''New'' (Curious about bug status? Details [[https://wiki.ubuntu.com/Bugs/Status|here]]). - == Use the menu - try this first! == - - '''Note:''' Since [[https://wiki.ubuntu.com/LucidLynx|10.04]] this only works for the Development Releases, If you're running Lucid you might want to use the [[https://help.ubuntu.com/community/ReportingBugs#Filing%20a%20bug%20with%20ubuntu-bug|ubuntu-bug]] method. (See [[https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/BugHandling|Lucid/BugHandling]] for information on this change.) - - If you want to report a bug on an application that is ''running and responding'', use the application's help menu: '''Help -> Report a problem'''. - - {{attachment:report-a-problem.png}} - - This method is preferable to filing a bug at the Launchpad website - it automatically attaches relevant information, which helps analyze the problem. - - If an application crashes, and you're using a version of Ubuntu which is actively under development, [[https://wiki.ubuntu.com/Apport|Apport]] will start automatically, raising an appropriate bug report for you to complete in Launchpad. This provides developers with rich debugging information that will make it easier to fix the problem. - - {{attachment:apport-1.png}} - == Filing a bug with ubuntu-bug == - - If you can't file your report from the menu, for example: - - * You're using the Server Edition - * The application doesn't have the appropriate menu item - * The application won't start at all - * Your problem is not related to an application but is an infrastructure component, such as the Linux kernel or graphics subsystem - - You can still help us by using `ubuntu-bug`. === Ubuntu 8.10 and later === @@ -89, +66 @@ If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://launchpad.net/distros/ubuntu/|Launchpad]]. When doing so please ensure that you have determined which package it should be filed against. Read '[[http://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]' for guidance or use [[ http://launchpad.net/ubuntu/ | Launchpad's package search feature ]]. To file a bug against a specific package use a url similar to the following, `http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect`, where PACKAGENAME is the name of the source package about which you want to file the bug. In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the [[ https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu | wiki ]]. To report a bug when you don't know the package name [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect]] + + == Using the menu == + + '''Note:''' Since [[https://wiki.ubuntu.com/LucidLynx|10.04]] this only works for the Development Releases, If you're running Lucid you might want to use the [[https://help.ubuntu.com/community/ReportingBugs#Filing%20a%20bug%20with%20ubuntu-bug|ubuntu-bug]] method. (See [[https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/BugHandling|Lucid/BugHandling]] for information on this change.) + + If you want to report a bug on an application that is ''running and responding'', use the application's help menu: '''Help -> Report a problem'''. + + {{attachment:report-a-problem.png}} + + This method is preferable to filing a bug at the Launchpad website - it automatically attaches relevant information, which helps analyze the problem. + + If an application crashes, and you're using a version of Ubuntu which is actively under development, [[https://wiki.ubuntu.com/Apport|Apport]] will start automatically, raising an appropriate bug report for you to complete in Launchpad. This provides developers with rich debugging information that will make it easier to fix the problem. + + {{attachment:apport-1.png}} === Adding Apport Debug Information to an Existing Launchpad Bug === From sense at ubuntu.com Wed Aug 4 08:38:59 2010 From: sense at ubuntu.com (Sense Hofstede) Date: Wed, 4 Aug 2010 10:38:59 +0200 Subject: New bug tag for Nautilus desktop icons problems Message-ID: Hello, There are a few usability problems with the desktop provided by Nautilus. I'm mostly talking about the icons here. It is troublesome to align icons properly, to make sure they don't stack, not everyone is fond of the grid. Etc, etc. A lot of these issues overlap or should be addressed together. Therefore I've created a tag called 'nautilus-desktop-icons'. I want to ask everyone to tag all bugs related to the desktop with this tag, so we get a better overview of the different issues related to the desktop. That should make it easier to find duplicates and when someone starts working on the desktop issue, it would be easy to find the problems. https://launchpad.net/ubuntu/+bugs?field.tag=nautilus-desktop-icons Regards, -- Sense Hofstede http://sensehofstede.nl/ From noreply at ubuntu.com Wed Aug 4 08:28:05 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 04 Aug 2010 08:28:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_qense?= Message-ID: <20100804082805.3175.62769@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by qense: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=162&rev2=163 The comment on the change is: Sorted the lists alphabetically, reorganised the page, removed duplicate 'indicator-application' tag from wrong category and added new tag 'desktop-icons' ------------------------------------------------------------------------------ == Different ways you can help == || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=bitesize|`bitesize`]] || This bug is easy to fix and suitable for new contributors. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-artwork|`needs-artwork`]] || A bug that needs new artwork to be created || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-sound|`needs-sound`]] || A bug that needs new sound to be created || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-coding|`needs-coding`]] || A bug that needs new source code to be written || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-design|`needs-design`]] || A bug that needs UI design done first || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging|`needs-packaging`]] || Packaging requests - software that isn't packaged for Ubuntu yet || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=bitesize|`bitesize`]] || This bug is easy to fix and suitable for new contributors. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-sound|`needs-sound`]] || A bug that needs new sound to be created || == Generic bug tags == || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-bug|`apport-bug`]] || A bug reported using "Report a Problem" in an application's Help menu contains lots of details! || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-collected|`apport-collected`]] || A bug that has had apport-collect ran against it which will contain additional information || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-crash|`apport-crash`]] || A crash reported by apport - Ubuntu's automated problem reporter || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-package|`apport-package`]] || A bug reported by apport when a package failed to install or upgrade || + || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=derivatives|`derivatives`]] || Bugs related to Derivatives || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=desktop-file|`desktop-file`]] || The bug requests the addition/fix of a .desktop file. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=desktop-icons|`desktop-icons`]] || Bugs related to the desktop, especially the alignment, display and grid of icons. || + || [[https://launchpad.net/ubuntu/+bugs?field.status:list=FIXRELEASED&field.tag=fix-to-verify|`fix-to-verify`]] || A bug that is Fix Released and should be verified when performing iso testing of daily builds or milestones || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ftbfs|`ftbfs`]] || Bugs describing build failures of packages. || + || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=gobuntu|`gobuntu`]] || Bugs related to Gobuntu || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=hw-specific|`hw-specific`]] || A bug that requires a specific piece of hardware to duplicate || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=iso-testing|`iso-testing`]] || A bug found when performing iso testing and also tracked at https://iso.qa.ubuntu.com/ || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup|`likely-dup`]] || The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=manpage|`manpage`]] || This bug is about a package's manpage being incorrect. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=metabug|`metabug`]] || This bug has a high probability of duplicate reports being filed. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup|`likely-dup`]] || The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=screencast|`screencast`]] || This bug report includes a screencast of the bug in action! || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=string-fix|`string-fix`]] || This bug is a string fix (not code) and is great for new contributors. For spelling and grammatic errors. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=manpage|`manpage`]] || This bug is about a package's manpage being incorrect. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=triage-mentoring-available|`triage-mentoring-available`]] || This bug has been identified as one that could use some additional information and another triager is offering guidance for getting that information. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=packaging|`packaging`]] || The bug is likely to be a packaging mistake. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=desktop-file|`desktop-file`]] || The bug requests the addition/fix of a .desktop file. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=upgrade|`upgrade`]] || Bugs that request new upstream versions - please help reviewing them carefully. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ftbfs|`ftbfs`]] || Bugs describing build failures of packages. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=unmetdeps|`unmetdeps`]] || Bugs that indicate packages not being installable due to missing dependencies. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-crash|`apport-crash`]] || A crash reported by apport - Ubuntu's automated problem reporter || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-bug|`apport-bug`]] || A bug reported using "Report a Problem" in an application's Help menu contains lots of details! || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-package|`apport-package`]] || A bug reported by apport when a package failed to install or upgrade || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-collected|`apport-collected`]] || A bug that has had apport-collect ran against it which will contain additional information || || [[https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.status%3Alist=New&field.status%3Alist=Incomplete&field.status%3Alist=Invalid&field.status%3Alist=Won%27t+Fix&field.status%3Alist=Confirmed&field.status%3Alist=Triaged&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status%3Alist=Fix+Released&field.tag=needs-devrelease-testing&search=Search|`needs-devrelease-testing`]] || A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-reassignment|`needs-reassignment`]] || A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=packaging|`packaging`]] || The bug is likely to be a packaging mistake. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=screencast|`screencast`]] || This bug report includes a screencast of the bug in action! || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=string-fix|`string-fix`]] || This bug is a string fix (not code) and is great for new contributors. For spelling and grammatical errors. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=touch|`touch`]] || an issue with touch support in applications or X || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=triage-mentoring-available|`triage-mentoring-available`]] || This bug has been identified as one that could use some additional information and another triager is offering guidance for getting that information. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=iso-testing|`iso-testing`]] || A bug found when performing iso testing and also tracked at https://iso.qa.ubuntu.com/ || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=hw-specific|`hw-specific`]] || A bug that requires a specific piece of hardware to duplicate || - || [[https://launchpad.net/ubuntu/+bugs?field.status:list=FIXRELEASED&field.tag=fix-to-verify|`fix-to-verify`]] || A bug that is Fix Released and should be verified when performing iso testing of daily builds or milestones || - || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=gobuntu|`gobuntu`]] || Bugs related to Gobuntu || - || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=derivatives|`derivatives`]] || Bugs related to Derivatives || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=indicator-application|`indicator-application`]] || Bugs that are related to [[ https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators | application indicators ]] in Lucid || || [[https://launchpad.net/ubuntu/+bugs?field.tag=units-policy|`units-policy`]] || A bug that violates the UnitsPolicy || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=touch|`touch`]] || an issue with touch support in applications or X || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=unmetdeps|`unmetdeps`]] || Bugs that indicate packages not being installable due to missing dependencies. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=upgrade|`upgrade`]] || Bugs that request new upstream versions - please help reviewing them carefully. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=work-intensive|`work-intensive`]] || triaging requires intensive work to validate/reproduce || - - == Ayatana == - Specific bugs concerning parts of the [[https://launchpad.net/ayatana|Ayatana project]]. - - || '''Tag''' || '''Use case''' || - ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=app-menu|`app-menu`]] || Bugs related to the [[DesktopExperienceTeam/ApplicationMenu|App Menu]] that will be used for the first time in the Ubuntu Maverick Netbook Edition. || - ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-applet|`indicator-applet`]] || Bugs related to the use of the Indicator Applet that are not in the 'indicator-applet' package (no Application Indicators!) || - ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application|`indicator-application`]] || Bugs related to the use of Indicator Application that are not in the 'indicator-application' package || - ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=trayaway|`trayaway`]] || Bugs related to the [[NotificationAreaTransition|Notification Area transition]].|| - - == X Specific == - - For X tags please check [[X/Tagging|X Tagging]] with all the official X tags - - == Kernel Specific == - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.searchtext=linux&field.tag=bitesize|`bitesize` ]] || With regards to the kernel, this includes things like enabling modules and changing kernel config options || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=cherry-pick|`cherry-pick`]] || A kernel bug that has a git commit SHA from the upstream kernel || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-bug|`kernel-bug`]] || A "BUG:" message output was noted in the logs but it did not contain an Oops || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-oops|`kernel-oops`]] || This bug causes a kernel Oops message || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-kerneloops|`apport-kerneloops`]] || This Kernel Oops was reported using apport. || - || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=suspend+resume|`suspend resume`]] || This bug was triggered by a suspend/resume failure || - || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=hibernate+resume|`hibernate resume`]] || This bug was triggered by a hibernate/resume failure || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=xorg-needs-kernel-fix|`xorg-needs-kernel-fix`]] || This is an xorg bug which is dependent on a kernel patch || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-testing|`needs-upstream-testing`]] || This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds || - - For more tags see [[Kernel/Tagging|Kernel/Tagging]]. - - == SRU Specific == - - See StableReleaseUpdates for more information. - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed|`verification-needed`]] || A Stable Release Update bug with a package in -proposed needing testing || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-done|`verification-done`]] || A Stable Release Update bug with a package in -proposed that has been confirmed to fix the bug || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-failed|`verification-failed`]] || A Stable Release Update bug with a package in -proposed that has been verified to not fix the bug || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-proposed |`regression-proposed`]] || A bug in a stable release of Ubuntu that was found when testing a package from -proposed || - - == Regression specific == - - See the [[http://qa.ubuntu.com/reports/regression/regression_tracker.html|regression tracker]] for a list of these bugs and [[QATeam/RegressionTracking]] for more information. - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-potential|`regression-potential`]] || A bug in the development release that was not present in the stable release. When this bug is a result of a transition in the default application for a task, also use the [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=default-application|`default-application`]] tag. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-release|`regression-release`]] || A bug in a stable release that was not present in a previous stable release || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-update|`regression-update`]] || A bug in a stable release that was introduced by a package from -updates || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-proposed|`regression-proposed`]] || A bug in a stable release of Ubuntu that was found when testing a package from -proposed || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-retracer|`regression-retracer`]] || An apport crash bug report that was identified by the retracer as having the same characteristics as a fixed crash report || - - == More specific == - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ngo|`ngo`]] || This bug affects [[NGO|NGOs]]. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ldap|`ldap`]] || This bug is a LDAP problem. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=nscd|`nscd`]] || This bug deals with nscd which is part of the glibc package || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=usability|`usability`]] || This bug is a usability problem. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=a11y|`a11y`]] || This bug is an accessibility problem. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=xinerama|`xinerama`]] || This bug is a xinerama problem. Multiple-monitor configuration. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=linuxfirmwarekit|`linuxfirmwarekit`]] || This bug contains Linux firmware kit test results. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=java-headless|`java-headless`]] || This bug is related to a Java program or library that could run headless but depends on a full Java environment (including graphics and sound) || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=notifications|`notifications`]] || This bug is related to the new notification system (notify-osd) introduced in Jaunty || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=dxteam|`dxteam`]] || This bug is specifically targeted by Canonical developers, only to be associated with the 'notifications' tag above|| - || [[https://launchpad.net/ubuntu/+bugs?field.tag=rtl|`rtl`]] || This bug is a right-to-left problem. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ec2-images|`ec2-images`]] || This bug is related to Ubuntu on [[https://help.ubuntu.com/community/EC2StartersGuide|EC2]]. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=uec-images|`uec-images`]] || This bug is related to the Ubuntu Enterprise Cloude (UEC) [[http://uec-images.ubuntu.com/releases|images]] || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch|`patch`]] || This bug has a patch attached to it or contains a link to a patch || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-needswork|`patch-needswork`]] || This bug has a patch attached to it that needs some work done on it || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected|`patch-rejected`]] || This bug has a patch attached to it that was not included in Ubuntu || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-upstreaminput|`patch-upstreaminput`]] || This bug has a patch attached to it that has been forwarded upstream and requires their input or incorporation || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-upstream|`patch-forwarded-upstream`]] || This bug has a patch attached to it that has been forwarded upstream || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-debian|`patch-forwarded-debian`]] || This bug has a patch attached to it that has been forwarded to debian || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-upstream|`patch-rejected-upstream`]] || This bug has a patch attached to it that has been rejected by upstream || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-debian|`patch-rejected-debian`]] || This bug has a patch attached to it that has been rejected by debian || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-upstream|`patch-accepted-upstream`]] || This bug has a patch attached to it that has been accepted by upstream || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-debian|`patch-accepted-debian`]] || This bug has a patch attached to it that has been accepted by debian || - - == Hardware Specific == - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ac97-jack-sense|`ac97-jack-sense`]] || This bug deals with headphone sense for AC'97 based codecs (0401) || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=hda-jack-sense|`hda-jack-sense`]] || This bug deals with headphone sense for HDA based codecs (0403) || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ps3|`ps3`]] || Some bug reports are about people running Ubuntu on a Playstation 3 || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=macbook|`macbook`]] || These bugs deal with Mac Book systems || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=macbookpro|`macbookpro`]] || These bugs deal with Mac Book Pro systems || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=ume|`ume`]] || These bugs deal with Ubuntu Mobile and Embeded systems || - - == Kubuntu Specific == - - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-report|`needs-upstream-report`]] || This bug needs the report to be forwarded to the upstream project || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=upstream|`upstream`]] || This bug is reported to the upstream project || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-sync|`needs-upstream-sync`]] || This bug has been forwarded to the upstream project which has released a fix that has not been merged yet || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=guidance-powermanager|`guidance-powermanager`]] || This kde-guidance bug is in powermanager || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-displayconfig|`kde-guidance-displayconfig`]] || This kde-guidance bug is in displayconfig || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-userconfig|`kde-guidance-userconfig`]] || This kde-guidance bug is in userconfig || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-mountconfig|`kde-guidance-mountconfig`]] || This kde-guidance bug is in mountconfig || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-serviceconfig|`kde-guidance-serviceconfig`]] || This kde-guidance bug is in serviceconfig || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-wineconfig|`kde-guidance-wineconfig`]] || This kde-guidance bug is in wineconfig || == Application Specific Tags == ##These tags are pulled from other wiki pages - you can determine which one by looking at the bit after "Include(". So the first set are pulled from the DebuggingNetworkManager wiki page. @@ -165, +66 @@ || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-jaunty|`ffox36-jaunty`]] || Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-karmic|`ffox36-karmic`]] || Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 || + == Other specific bug tags == + + === Ayatana === + Specific bugs concerning parts of the [[https://launchpad.net/ayatana|Ayatana project]]. + + || '''Tag''' || '''Use case''' || + ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=app-menu|`app-menu`]] || Bugs related to the [[DesktopExperienceTeam/ApplicationMenu|App Menu]] that will be used for the first time in the Ubuntu Maverick Netbook Edition. || + ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-applet|`indicator-applet`]] || Bugs related to the use of the Indicator Applet that are not in the 'indicator-applet' package (no Application Indicators!) || + ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application|`indicator-application`]] || Bugs related to the use of Indicator Application that are not in the 'indicator-application' package || + ||[[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=trayaway|`trayaway`]] || Bugs related to the [[NotificationAreaTransition|Notification Area transition]].|| + + === Hardware Specific === + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ac97-jack-sense|`ac97-jack-sense`]] || This bug deals with headphone sense for AC'97 based codecs (0401) || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=hda-jack-sense|`hda-jack-sense`]] || This bug deals with headphone sense for HDA based codecs (0403) || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=macbook|`macbook`]] || These bugs deal with Mac Book systems || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=macbookpro|`macbookpro`]] || These bugs deal with Mac Book Pro systems || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ps3|`ps3`]] || Some bug reports are about people running Ubuntu on a Playstation 3 || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ume|`ume`]] || These bugs deal with Ubuntu Mobile and Embeded systems || + - == Historical Tags == + === Historical Tags === These tags were relevant previously for Ubuntu bugs and may still appear in some bugs. The needs retracing tags are added automatically for Gutsy. @@ -174, +96 @@ || [[https://launchpad.net/ubuntu/+bugs?field.tag=need-i386-retrace|`need-i386-retrace`]] || The bug contains a crash report that needs retracing with `apport-retrace` on `i386` || || [[https://launchpad.net/ubuntu/+bugs?field.tag=need-powerpc-retrace|`need-powerpc-retrace`]] || The bug contains a crash report that needs retracing with `apport-retrace` on `powerpc` || + + === Kernel Specific === + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-kerneloops|`apport-kerneloops`]] || This Kernel Oops was reported using apport. || + || [[https://launchpad.net/ubuntu/+bugs?field.searchtext=linux&field.tag=bitesize|`bitesize` ]] || With regards to the kernel, this includes things like enabling modules and changing kernel config options || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=cherry-pick|`cherry-pick`]] || A kernel bug that has a git commit SHA from the upstream kernel || + || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=hibernate+resume|`hibernate resume`]] || This bug was triggered by a hibernate/resume failure || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-bug|`kernel-bug`]] || A "BUG:" message output was noted in the logs but it did not contain an Oops || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-oops|`kernel-oops`]] || This bug causes a kernel Oops message || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-testing|`needs-upstream-testing`]] || This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds || + || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=suspend+resume|`suspend resume`]] || This bug was triggered by a suspend/resume failure || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=xorg-needs-kernel-fix|`xorg-needs-kernel-fix`]] || This is an xorg bug which is dependent on a kernel patch || + + For more tags see [[Kernel/Tagging|Kernel/Tagging]]. + + === Kubuntu Specific === + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=guidance-powermanager|`guidance-powermanager`]] || This kde-guidance bug is in powermanager || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-displayconfig|`kde-guidance-displayconfig`]] || This kde-guidance bug is in displayconfig || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-mountconfig|`kde-guidance-mountconfig`]] || This kde-guidance bug is in mountconfig || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-serviceconfig|`kde-guidance-serviceconfig`]] || This kde-guidance bug is in serviceconfig || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-userconfig|`kde-guidance-userconfig`]] || This kde-guidance bug is in userconfig || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kde-guidance-wineconfig|`kde-guidance-wineconfig`]] || This kde-guidance bug is in wineconfig || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-report|`needs-upstream-report`]] || This bug needs the report to be forwarded to the upstream project || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-sync|`needs-upstream-sync`]] || This bug has been forwarded to the upstream project which has released a fix that has not been merged yet || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=upstream|`upstream`]] || This bug is reported to the upstream project || + + === More specific === + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=a11y|`a11y`]] || This bug is an accessibility problem. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=dxteam|`dxteam`]] || This bug is specifically targeted by Canonical developers, only to be associated with the 'notifications' tag. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ec2-images|`ec2-images`]] || This bug is related to Ubuntu on [[https://help.ubuntu.com/community/EC2StartersGuide|EC2]]. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=java-headless|`java-headless`]] || This bug is related to a Java program or library that could run headless but depends on a full Java environment (including graphics and sound) || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ldap|`ldap`]] || This bug is a LDAP problem. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=linuxfirmwarekit|`linuxfirmwarekit`]] || This bug contains Linux firmware kit test results. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=ngo|`ngo`]] || This bug affects [[NGO|NGOs]]. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=notifications|`notifications`]] || This bug is related to the new notification system (notify-osd) introduced in Jaunty || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=nscd|`nscd`]] || This bug deals with nscd which is part of the glibc package || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=usability|`usability`]] || This bug is a usability problem. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=rtl|`rtl`]] || This bug is a right-to-left problem. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=uec-images|`uec-images`]] || This bug is related to the Ubuntu Enterprise Cloude (UEC) [[http://uec-images.ubuntu.com/releases|images]] || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=xinerama|`xinerama`]] || This bug is a xinerama problem. Multiple-monitor configuration. || + + === Patch specific === + + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch|`patch`]] || This bug has a patch attached to it or contains a link to a patch || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-debian|`patch-accepted-debian`]] || This bug has a patch attached to it that has been accepted by Debian || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-upstream|`patch-accepted-upstream`]] || This bug has a patch attached to it that has been accepted by upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-debian|`patch-forwarded-debian`]] || This bug has a patch attached to it that has been forwarded to Debian. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-upstream|`patch-forwarded-upstream`]] || This bug has a patch attached to it that has been forwarded upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-needswork|`patch-needswork`]] || This bug has a patch attached to it that needs some work done on it || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected|`patch-rejected`]] || This bug has a patch attached to it that was not included in Ubuntu || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-debian|`patch-rejected-debian`]] || This bug has a patch attached to it that has been rejected by Debian || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-upstream|`patch-rejected-upstream`]] || This bug has a patch attached to it that has been rejected by upstream || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-upstreaminput|`patch-upstreaminput`]] || This bug has a patch attached to it that has been forwarded upstream and requires their input or incorporation || + + === Regression specific === + + See the [[http://qa.ubuntu.com/reports/regression/regression_tracker.html|regression tracker]] for a list of these bugs and [[QATeam/RegressionTracking]] for more information. + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-potential|`regression-potential`]] || A bug in the development release that was not present in the stable release. When this bug is a result of a transition in the default application for a task, also use the [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=default-application|`default-application`]] tag. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-proposed|`regression-proposed`]] || A bug in a stable release of Ubuntu that was found when testing a package from -proposed || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-release|`regression-release`]] || A bug in a stable release that was not present in a previous stable release || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-retracer|`regression-retracer`]] || An apport crash bug report that was identified by the retracer as having the same characteristics as a fixed crash report || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-update|`regression-update`]] || A bug in a stable release that was introduced by a package from -updates || + + === SRU Specific === + + See StableReleaseUpdates for more information. + + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=regression-proposed |`regression-proposed`]] || A bug in a stable release of Ubuntu that was found when testing a package from -proposed || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-done|`verification-done`]] || A Stable Release Update bug with a package in -proposed that has been confirmed to fix the bug || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-failed|`verification-failed`]] || A Stable Release Update bug with a package in -proposed that has been verified to not fix the bug || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed|`verification-needed`]] || A Stable Release Update bug with a package in -proposed needing testing || + + === X Specific === + + For X tags please check [[X/Tagging|X Tagging]] with all the official X tags + ---- Go back to '''[[BugSquad]]'''.<
> [[CategoryBugSquad]] From noreply at ubuntu.com Wed Aug 4 08:32:26 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 04 Aug 2010 08:32:26 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_qense?= Message-ID: <20100804083226.9287.89599@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by qense: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=163&rev2=164 The comment on the change is: Renamed 'desktop-icons' to 'nautilus-desktop-icons', to emphasise it is about Nautilus' desktop. ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-package|`apport-package`]] || A bug reported by apport when a package failed to install or upgrade || || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=derivatives|`derivatives`]] || Bugs related to Derivatives || || [[https://launchpad.net/ubuntu/+bugs?field.tag=desktop-file|`desktop-file`]] || The bug requests the addition/fix of a .desktop file. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=desktop-icons|`desktop-icons`]] || Bugs related to the desktop, especially the alignment, display and grid of icons. || || [[https://launchpad.net/ubuntu/+bugs?field.status:list=FIXRELEASED&field.tag=fix-to-verify|`fix-to-verify`]] || A bug that is Fix Released and should be verified when performing iso testing of daily builds or milestones || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ftbfs|`ftbfs`]] || Bugs describing build failures of packages. || || [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=gobuntu|`gobuntu`]] || Bugs related to Gobuntu || @@ -38, +37 @@ || [[https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup|`likely-dup`]] || The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=manpage|`manpage`]] || This bug is about a package's manpage being incorrect. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=metabug|`metabug`]] || This bug has a high probability of duplicate reports being filed. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=nautilus-desktop-icons|`nautilus-desktop-icons`]] || Bugs related to the Nautilus desktop, especially the alignment, display and grid of icons. || || [[https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.status%3Alist=New&field.status%3Alist=Incomplete&field.status%3Alist=Invalid&field.status%3Alist=Won%27t+Fix&field.status%3Alist=Confirmed&field.status%3Alist=Triaged&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status%3Alist=Fix+Released&field.tag=needs-devrelease-testing&search=Search|`needs-devrelease-testing`]] || A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-reassignment|`needs-reassignment`]] || A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to || || [[https://launchpad.net/ubuntu/+bugs?field.tag=packaging|`packaging`]] || The bug is likely to be a packaging mistake. || From noreply at ubuntu.com Wed Aug 4 13:21:40 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 04 Aug 2010 13:21:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_yofel?= Message-ID: <20100804132140.1966.98012@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by yofel: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=299&rev2=300 The comment on the change is: mention ubuntu-bug in the no-package response again ------------------------------------------------------------------------------ == Bugs without a package == Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. For more information : https://help.ubuntu.com/community/ReportingBugs|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. + + When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.|| == Bugs resolved after update or config change == Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. From noreply at ubuntu.com Wed Aug 4 13:43:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 04 Aug 2010 13:43:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_yofel?= Message-ID: <20100804134342.10011.82988@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by yofel: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=301&rev2=302 The comment on the change is: use direct link instead of redirect ------------------------------------------------------------------------------ == Bugs without a package == Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.<
><
>When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.<
><
>When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.|| == Bugs resolved after update or config change == Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. From noreply at ubuntu.com Wed Aug 4 13:27:11 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 04 Aug 2010 13:27:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_yofel?= Message-ID: <20100804132711.8597.10831@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by yofel: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=300&rev2=301 The comment on the change is: fix the layout... ------------------------------------------------------------------------------ == Bugs without a package == Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME. + || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.<
><
>When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.|| - - When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.|| == Bugs resolved after update or config change == Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses. From brian at ubuntu.com Thu Aug 5 00:37:22 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 4 Aug 2010 17:37:22 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by brian-murray In-Reply-To: <20100802183936.6972.84069@jostaberry.canonical.com> References: <20100802183936.6972.84069@jostaberry.canonical.com> Message-ID: <20100805003722.GF32174@murraytwins.com> On Mon, Aug 02, 2010 at 06:39:36PM -0000, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The following page has been changed by brian-murray: > http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=161&rev2=162 > > ------------------------------------------------------------------------------ > || [[https://launchpad.net/ubuntu/+bugs?field.tag=uec-images|`uec-images`]] || This bug is related to the Ubuntu Enterprise Cloude (UEC) [[http://uec-images.ubuntu.com/releases|images]] || > || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch|`patch`]] || This bug has a patch attached to it or contains a link to a patch || > || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-needswork|`patch-needswork`]] || This bug has a patch attached to it that needs some work done on it || > - || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-refused|`patch-refused`]] || This bug has a patch attached to it that was not included in Ubuntu || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected|`patch-rejected`]] || This bug has a patch attached to it that was not included in Ubuntu || > || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-upstreaminput|`patch-upstreaminput`]] || This bug has a patch attached to it that has been forwarded upstream and requires their input or incorporation || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-upstream|`patch-forwarded-upstream`]] || This bug has a patch attached to it that has been forwarded upstream || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-forwarded-debian|`patch-forwarded-debian`]] || This bug has a patch attached to it that has been forwarded to debian || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-upstream|`patch-rejected-upstream`]] || This bug has a patch attached to it that has been rejected by upstream || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-rejected-debian|`patch-rejected-debian`]] || This bug has a patch attached to it that has been rejected by debian || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-upstream|`patch-accepted-upstream`]] || This bug has a patch attached to it that has been accepted by upstream || > + || [[https://launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-debian|`patch-accepted-debian`]] || This bug has a patch attached to it that has been accepted by debian || The patch tags are really on a separate web page and it would be better if we could use an include for this. I realize I'm critiquing my own work here. ;-) I was in a hurry when and did this and hope someone can help me out. Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Thu Aug 5 18:45:21 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 05 Aug 2010 18:45:21 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100805184521.19081.73829@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=16&rev2=17 ------------------------------------------------------------------------------ == In case your touchpad doesn't work at all (No response from the touchpad) == + This is generally a case of kernel('''linux''') or '''xorg''' bug. Check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 4. Press Crtl+Alt+F7 to switch back to X. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + + If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: + 1. File the bug against '''linux''' 1. Provide the [[#generalinfo|general information]]. 1. Enter the following command in a terminal/console: {{{ @@ -36, +61 @@ 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. == In case your touchpad stops working after a while == + + This is generally a case of kernel('''linux''') or '''xorg''' bug. In this case, in description field, specify the steps to make the touchpad stop working. eg- hit a key, drag or something. Now check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 4. Press Crtl+Alt+F7 to switch back to X. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + + If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: 1. Provide the [[#generalinfo|general information]]. 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ @@ -63, +113 @@ In any case, include the outputs of the following commands: {{{ $ cat /proc/bus/input/devices >~/devices - $ sudo lspci -vvnn > ~/lspci $ xinput --list > ~/xinput $ cat /var/log/Xorg.0.log > Xorg.0.log }}} @@ -76, +125 @@ eg - Jumpy cursor, scrolling problems, touchpad area is misdetected, circular scrolling, buttons not correctly mapped. 1. Enter the following command in a terminal/console: {{{ + $ xmodmap -pp >~/xmodmap - $ synclient -l > ~/synclient - $ xmodmap -pp - $ xinput --list-props }}} + $ xinput --list-props >~/xinput }}} + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 4. Press Crtl+Alt+F7 to switch back to X. - 2. Attach {{{~/synclient}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. + 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. In {{{ xinput --list-props }}}, is of your touchpad in {{{ xinput --list }}}. + + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} === In case your multitouch features does not work === @@ -92, +158 @@ '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. - For any other case, include the outputs in the bug report in separate comments. {{{ + 1. For any other case, include the outputs in the bug report in separate comments. {{{ - $ synclient -l > ~/synclient - $ xinput --list-props }}} + $ xinput --list-props >~/xinput }}} - + 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 3. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 4. Press Crtl+Alt+F7 to switch back to X. - Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. + 5. Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. {{{ - {{{ $ xev | grep -i button > ~/xev}}} + $ xev | grep -i button > ~/xev}}} + 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - - Attach these outputs in separate attachments, in the bug report. In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + - Before filing new bug please look in the common bugs section. + Before filing new bug please look in the '''common bugs''' section. = Some general work flow for Triagers = @@ -130, +211 @@ For problems such as scrolling area, touch area, button wrong mapping, multitouch try investigating with {{{ - $ synclient -m 100 + $ evtest /dev/input/eventX $ xev }}} @@ -139, +220 @@ $ xinput --list-props 6 }}} - = Help regarding using debug utilities = - - - In case when using {{{ synclient -m 100 }}} reports ''SHMConfig'' disabled. Try adding these lines to your xorg.conf file in respective sections. Please make a backup copy of your xorg.conf file before trying this. - - Section "Module" - Load "synaptics" - EndSection - #... - 4 Section "InputDevice" - Driver "synaptics" - Identifier "TouchPad" - Option "Protocol" "auto-dev" - Option "SHMConfig" "on" - EndSection - #... - Section "ServerLayout" - InputDevice "TouchPad" "CorePointer" - EndSection - - - = Known bugs = Synaptics Touchpad Multitouch https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/308191 From noreply at ubuntu.com Thu Aug 5 18:45:57 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 05 Aug 2010 18:45:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22simar/Touchpad=22_by_simar?= Message-ID: <20100805184557.19076.57176@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/simar/Touchpad?action=diff&rev1=3&rev2=4 ------------------------------------------------------------------------------ == In case your touchpad doesn't work at all (No response from the touchpad) == + This is generally a case of kernel('''linux''') or '''xorg''' bug. Check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 4. Press Crtl+Alt+F7 to switch back to X. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + + If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: + 1. File the bug against '''linux''' 1. Provide the [[#generalinfo|general information]]. 1. Enter the following command in a terminal/console: {{{ @@ -36, +61 @@ 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. == In case your touchpad stops working after a while == + + This is generally a case of kernel('''linux''') or '''xorg''' bug. In this case, in description field, specify the steps to make the touchpad stop working. eg- hit a key, drag or something. Now check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 4. Press Crtl+Alt+F7 to switch back to X. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + + If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: 1. Provide the [[#generalinfo|general information]]. 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ @@ -59, +109 @@ To check whether to report for kernel or not {{{ $ cat /proc/bus/input/devices >~/devices }}} - If this include the name of your touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''Xserver'''. + If this include the name of your touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal In any case, include the outputs of the following commands: {{{ $ cat /proc/bus/input/devices >~/devices - $ sudo lspci -vvnn > ~/lspci $ xinput --list > ~/xinput $ cat /var/log/Xorg.0.log > Xorg.0.log }}} @@ -76, +125 @@ eg - Jumpy cursor, scrolling problems, touchpad area is misdetected, circular scrolling, buttons not correctly mapped. 1. Enter the following command in a terminal/console: {{{ + $ xmodmap -pp >~/xmodmap - $ synclient -l > ~/synclient - $ xmodmap -pp - $ xinput --list-props }}} + $ xinput --list-props >~/xinput }}} + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 4. Press Crtl+Alt+F7 to switch back to X. - 2. Attach {{{~/synclient}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. + 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. In {{{ xinput --list-props }}}, is of your touchpad in {{{ xinput --list }}}. + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + === In case your multitouch features does not work === - This bug is common in Synaptics Touchpad V7.2 where multitouch works perfect in windows but not in linux. This is not a bug related to xserver-xorg-input-synaptics. Multitouch capabilities are not detected but the kernel itself as evident in {{{ xinpit --list-props }}} shows + This bug is common in Synaptics Touchpad V7.2 where multitouch works perfect in windows but not in linux. This is not a bug related to xserver-xorg-input-synaptics. Multitouch capabilities are not detected but the kernel itself as evident in {{{ xinput --list-props }}} shows {{{ Synaptics Capabilities (277): 1, 1, 1, 0, 0 }}} This bug is already known (see the '''Known bugs''' below). In this case please don't file any new bugs and instead add a comment in the existing bug for any relevent information that you have. '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. - For any other case, include the outputs in the bug report in separate comments. {{{ + 1. For any other case, include the outputs in the bug report in separate comments. {{{ - $ synclient -l > ~/synclient - $ xinput --list-props }}} + $ xinput --list-props >~/xinput }}} - + 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + 3. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 4. Press Crtl+Alt+F7 to switch back to X. - Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. + 5. Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. {{{ - {{{ $ xev | grep -i button > ~/xev}}} + $ xev | grep -i button > ~/xev}}} + 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - - Attach these outputs in separate attachments, in the bug report. In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. + Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 + + Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + - Before filing new bug please look in the common bugs section. + Before filing new bug please look in the '''common bugs''' section. = Some general work flow for Triagers = @@ -130, +211 @@ For problems such as scrolling area, touch area, button wrong mapping, multitouch try investigating with {{{ - $ synclient -m 100 + $ evtest /dev/input/eventX $ xev }}} @@ -139, +220 @@ $ xinput --list-props 6 }}} - = Help regarding using debug utilities = - - - In case when using {{{ synclient -m 100 }}} reports ''SHMConfig'' disabled. Try adding these lines to your xorg.conf file in respective sections. Please make a backup copy of your xorg.conf file before trying this. - - Section "Module" - Load "synaptics" - EndSection - #... - 4 Section "InputDevice" - Driver "synaptics" - Identifier "TouchPad" - Option "Protocol" "auto-dev" - Option "SHMConfig" "on" - EndSection - #... - Section "ServerLayout" - InputDevice "TouchPad" "CorePointer" - EndSection - - - = Known bugs = Synaptics Touchpad Multitouch https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/308191 From noreply at ubuntu.com Thu Aug 5 18:56:10 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 05 Aug 2010 18:56:10 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100805185610.18917.22282@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=18&rev2=19 ------------------------------------------------------------------------------ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - N: Name="SynPS/2 Synaptics TouchPad" + {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - P: Phys=isa0060/serio2/input0 + {{{ P: Phys=isa0060/serio2/input0 }}} - S: Sysfs=/devices/platform/i8042/serio2/input/input8 + {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - U: Uniq= + {{{ U: Uniq= }}} - H: Handlers=mouse2 event8 + {{{ H: Handlers=mouse2 event8 }}} - B: EV=b + {{{ B: EV=b }}} - B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - B: ABS=11000003}}} + {{{ B: ABS=11000003 }}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -73, +73 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - N: Name="SynPS/2 Synaptics TouchPad" + {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - P: Phys=isa0060/serio2/input0 + {{{ P: Phys=isa0060/serio2/input0 }}} - S: Sysfs=/devices/platform/i8042/serio2/input/input8 + {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - U: Uniq= + {{{ U: Uniq= }}} - H: Handlers=mouse2 event8 + {{{ H: Handlers=mouse2 event8 }}} - B: EV=b + {{{ B: EV=b }}} - B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - B: ABS=11000003}}} + {{{ B: ABS=11000003 }}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -137, +137 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - N: Name="SynPS/2 Synaptics TouchPad" + {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - P: Phys=isa0060/serio2/input0 + {{{ P: Phys=isa0060/serio2/input0 }}} - S: Sysfs=/devices/platform/i8042/serio2/input/input8 + {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - U: Uniq= + {{{ U: Uniq= }}} - H: Handlers=mouse2 event8 + {{{ H: Handlers=mouse2 event8 }}} - B: EV=b + {{{ B: EV=b }}} - B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - B: ABS=11000003}}} + {{{ B: ABS=11000003 }}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -172, +172 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - N: Name="SynPS/2 Synaptics TouchPad" + {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - P: Phys=isa0060/serio2/input0 + {{{ P: Phys=isa0060/serio2/input0 }}} - S: Sysfs=/devices/platform/i8042/serio2/input/input8 + {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - U: Uniq= + {{{ U: Uniq= }}} - H: Handlers=mouse2 event8 + {{{ H: Handlers=mouse2 event8 }}} - B: EV=b + {{{ B: EV=b }}} - B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - B: ABS=11000003}}} + {{{ B: ABS=11000003 }}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} From noreply at ubuntu.com Thu Aug 5 18:49:15 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 05 Aug 2010 18:49:15 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100805184915.19074.82899@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=17&rev2=18 ------------------------------------------------------------------------------ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 @@ -48, +48 @@ H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 70000 0 0 0 0 0 0 0 0 - B: ABS=11000003 + B: ABS=11000003}}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -73, +73 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 @@ -81, +81 @@ H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 70000 0 0 0 0 0 0 0 0 - B: ABS=11000003 + B: ABS=11000003}}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -137, +137 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 @@ -145, +145 @@ H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 70000 0 0 0 0 0 0 0 0 - B: ABS=11000003 + B: ABS=11000003}}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} @@ -172, +172 @@ Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + {{{I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 @@ -180, +180 @@ H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 70000 0 0 0 0 0 0 0 0 - B: ABS=11000003 + B: ABS=11000003}}} Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} From noreply at ubuntu.com Fri Aug 6 22:14:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 06 Aug 2010 22:14:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_hggdh2?= Message-ID: <20100806221442.4118.68697@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=130&rev2=131 The comment on the change is: add note about checking for privacy issues any and all stacktraces ------------------------------------------------------------------------------ * If there is no `Stacktrace.txt (retraced)` attachment, then the most probable reason is that the `CoreDump.gz` attachment is broken. Please check with Martin Pitt (`pitti` in IRC, `martin.pitt at ubuntu.com`) about the reason since he can look into log files. - * Check if the `Stacktrace.txt (retraced)` attachment has anything that looks like sensitive data passed as function arguments. Examples are passwords, things that look like bank account numbers, CSS keys, etc. If you don't find anything, you may mark the bug as public ("This report is public/private" in the top right of the bug report). This is not required though, it is fine to keep the bug private throughout its lifetime. + * Check if any of stacktrace attachments (original stacktraces, `Stacktrace.txt (retraced)` and `ThreadStacktrace.txt (retraced)`) have anything that looks like sensitive data passed as function arguments. Examples are passwords, things that look like bank account numbers, CSS keys, user names, server names, etc. If you don't find anything, you may mark the bug as public ("This report is public/private" in the top right of the bug report). This is not required though, it is fine to keep the bug private throughout its lifetime. Except for those privacy issues, crash reports should be handled like normal bugs in terms of duplicate searching/marking, upstream forwarding, etc. From webmaster at ubuntu.com Sat Aug 7 11:32:54 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Sat, 07 Aug 2010 11:32:54 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_alex-harkema?= Message-ID: <20100807113254.14214.22288@acerola.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The following page has been changed by alex-harkema: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=140&rev2=141 ------------------------------------------------------------------------------ '''If you've come here when trying to file a bug about Ubuntu in Launchpad this was deliberate. Please read the following documentation regarding how to report a bug about Ubuntu.''' - In case you are '''well aware''' of the information given below on the preferred ways to file bug reports but you insist on using Launchpad, you can continue [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect|here]]. + In case you are '''well aware''' of the information given below on the preferred ways to file bug reports, but you insist on manually creating a report using Launchpad, you can continue [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect|here]]. = Reporting bugs = From noreply at ubuntu.com Sat Aug 7 21:31:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 07 Aug 2010 21:31:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_hggdh2?= Message-ID: <20100807213134.2638.88023@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=302&rev2=303 ------------------------------------------------------------------------------ || We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!|| == Bugs without a package == - Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder. + Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholdeer. + + /!\ If you use this response, you must assign a package. If you do not know what package to assign, please leave the bug alone, and ask for help. || Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.<
><
>When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.|| From pedro at ubuntu.com Mon Aug 9 16:59:31 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 09 Aug 2010 12:59:31 -0400 Subject: Bugsquad Meeting Reminder - Tuesday 10th August 2010 Message-ID: <1281373171.1973.26.camel@wombat> Hello Folks, Just a reminder that the Tuesday 10th of August 2010 at 1700 UTC we're having our Monthly BugSquad Meeting at #ubuntu-bugs, as always everybody is welcome to join us, the agenda[1] so far looks like: * Mentorship program update from Mentors * Open Discussions. As always don't hesitate to add or modify the topics as needed. If you're a Mentor or Student in the BugSquad mentoring program please attend since we'd like to hear updates on how's everything working for you (how is your student/mentor doing), if you have updates but cannot attend to the meeting please send an email to any of the Mentors admins[2]. 1- https://wiki.ubuntu.com/BugSquad/Meeting 2- https://wiki.ubuntu.com/BugSquad/Mentors/AdminList Have a great day!, pedro. From noreply at ubuntu.com Mon Aug 9 17:37:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 09 Aug 2010 17:37:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_mte?= =?utf-8?q?rry?= Message-ID: <20100809173734.32630.60713@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by mterry: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=50&rev2=51 The comment on the change is: Recommend bash, not dash for alsa-info.sh ------------------------------------------------------------------------------ In the event that you are not running Jaunty Jackalope (9.04) you can less automatically gather sound information using the following script from the alsa project site: [[http://www.alsa-project.org/alsa-info.sh|alsa-info.sh]]. By default, the script uploads the information to alsa-project.org . This information can be used by ALSA developers to improve current support for some cards. If you do not wish your information to be uploaded, please use the --no-upload argument when running the script. The script was written to aid the alsa developers, and also to help the people in #alsa to sort out sound issues. Please download the file to your home directory and run the script as follows: {{{ - $ sh ./alsa-info.sh + $ bash ./alsa-info.sh }}} or if you put it in your ~/bin and ~/bin is in your path and you make the file executable (chmod +x ~/bin/alsa-info.sh) From pedro at ubuntu.com Tue Aug 10 15:52:09 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 10 Aug 2010 11:52:09 -0400 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 12th August 2010 Message-ID: <1281455529.1936.13.camel@wombat> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Operation Cleansweep[1] which deals with reviewing patches and forwarding them to our Upstream partner projects, this week we have: * 100 Bugs with patches to be reviewed! Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 12th August 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100812 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs and #ubuntu-reviewers (FreeNode) the BugSquad and the Ubuntu Reviewers team will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs 1- https://wiki.ubuntu.com/OperationCleansweep Have a nice day, pedro. From noreply at ubuntu.com Thu Aug 12 13:02:09 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:02:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812130209.11969.35902@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=51&rev2=52 ------------------------------------------------------------------------------ '''''In other words, if in doubt, the bug should be filed against linux and have the ubuntu-audio team subscribed to the bug report.''''' - = Basic troubleshooting = + Running Lucid (10.04) or later? There is a troubleshooter that checks for some of the most common problems. Open a Terminal (Program -> Accessories -> Terminal), then enter this command: + {{{ + ubuntu-bug audio + }}} + Running Ubuntu Karmic Koala (9.10)? [[https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats|First have a look at this list]] of the most common problems with sound in this release. + == Identifying your hardware == If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device) From noreply at ubuntu.com Thu Aug 12 13:09:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:09:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812130942.12115.97681@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=52&rev2=53 ------------------------------------------------------------------------------ Please do not report problems on this page; use the normal support channels instead. See http://www.ubuntu.com/support - If you feel you have encountered a software bug, please report the bug using the following command in a terminal: + If you feel you have encountered a software bug, the way to report it varies between versions. + For Ubuntu Lucid Lynx (10.04) and later, run the following terminal command: {{{ + ubuntu-bug audio - - ubuntu-bug -p alsa-base - }}} + For Ubuntu Jaunty (9.04) or Karmic (9.10), run the following terminal command: - This will submit a detailed bug report regarding your current system and will work on any release later than and including 9.04 (Jaunty Jackalope). - - - == Automatic Sound Information Collection == - - In the event that you are not running Jaunty Jackalope (9.04) you can less automatically gather sound information using the following script from the alsa project site: [[http://www.alsa-project.org/alsa-info.sh|alsa-info.sh]]. By default, the script uploads the information to alsa-project.org . This information can be used by ALSA developers to improve current support for some cards. If you do not wish your information to be uploaded, please use the --no-upload argument when running the script. The script was written to aid the alsa developers, and also to help the people in #alsa to sort out sound issues. Please download the file to your home directory and run the script as follows: - - {{{ + {{{ - $ bash ./alsa-info.sh + ubuntu-bug -p alsa-base }}} - or if you put it in your ~/bin and ~/bin is in your path and you make the file executable (chmod +x ~/bin/alsa-info.sh) + This will submit a detailed bug report with information about your current system. + For older versions, or if the above fails for some reason, you can file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]]. - {{{ - $ alsa-info.sh - }}} - - - * The script will generate a URL. Please add this URL to your bug report. - * If for some reason the script does not generate a URL, please use the --pastebin option (our original upload method) - * The alsa-info.sh script can either be run as 'bash alsa-info.sh' _or_ made executable and run as './alsa-info.sh'. = Further sound troubleshooting = From noreply at ubuntu.com Thu Aug 12 13:19:05 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:19:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812131905.12128.44896@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=53&rev2=54 ------------------------------------------------------------------------------ #title Debugging Sound Problems <> ||<>|| - - '''Notes for triagers:''' - * General no-sound/low-sound/headphone-no-sound/etc. bugs should be marked against the "linux" source package. - * Only assign bugs to the "alsa-driver" source package if the reporter is using the alsa-source binary package with module-assistant OR is requesting a blacklist or slots/index modification. - - '''''In other words, if in doubt, the bug should be filed against linux and have the ubuntu-audio team subscribed to the bug report.''''' = Basic troubleshooting = @@ -94, +88 @@ For older versions, or if the above fails for some reason, you can file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]]. + == Triaging sound bugs == + + In general, no-sound/low-sound/headphone-no-sound/no auto-mute/etc. bugs should be: + * Filed against the '''linux''' source package. + * Add the '''kernel-sound''' tag + * '''Subscribe''' (do not assign) the Ubuntu-audio team + + Only assign bugs to the "alsa-driver" source package if the reporter is using the alsa-source binary package with module-assistant OR is requesting a blacklist or slots/index modification. + + * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes. + = Further sound troubleshooting = After reporting a bug you might want to see the community documentation: From noreply at ubuntu.com Thu Aug 12 13:27:14 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:27:14 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812132714.12119.51875@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=55&rev2=56 ------------------------------------------------------------------------------ == Preliminary checks == 1. Is your sound system plugged in and switched on. I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-( + 2. Is your speaker or microphone muted? Check here: + [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] + [[Audio/CheckForMutedMicrophone|Check for muted microphone]] + + ---- /!\ '''Edit conflict - other version:''' ---- 2. Is your speaker or microphone muted? Check here (9.10 and later) : * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] + + ---- /!\ '''Edit conflict - your version:''' ---- + + ---- /!\ '''End of edit conflict''' ---- == Checking volume levels == Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Rhythmbox. From noreply at ubuntu.com Thu Aug 12 13:26:45 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:26:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812132645.12130.26819@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=54&rev2=55 ------------------------------------------------------------------------------ == Preliminary checks == 1. Is your sound system plugged in and switched on. I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-( + 2. Is your speaker or microphone muted? Check here (9.10 and later) : + * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] + * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] == Checking volume levels == Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Rhythmbox. From kamusin at gmail.com Thu Aug 12 14:01:49 2010 From: kamusin at gmail.com (Kamus) Date: Thu, 12 Aug 2010 10:01:49 -0400 Subject: Bugsquad Mentors Updates In-Reply-To: <1281620355.1911.12.camel@wombat> References: <1281620355.1911.12.camel@wombat> Message-ID: On Thu, Aug 12, 2010 at 9:39 AM, Pedro Villavicencio Garrido wrote: > Hello Mentors!, > > As you might know, we're collecting the updates from our Mentors at > every Bugsquad Meeting but we didn't received yours yet. May you please > send an email to the ubuntu-bugsquad Mailing List with some updates > about your students? This is pretty important for us to know if the > program is doing a good job or not, thanks for your help! > Hello all! sorry for not reply in time but I had lot of work last days.. so things are fine here, I have sent initial contact mail to tree099 and devildante (ilidrissi.amine) (my assigned students) but I haven't heard any notice from tree009 (3 mails sent, one per week and no news), instead devildante has been doing a great job! triaging lot of reports, hacking software-center for include addons support and participating in our hugdays (he has increased his karma around 30%), so I am very proud and glad of him (actually I think his time here like a student should be passenger). That's all from here folks! Victor -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From noreply at ubuntu.com Thu Aug 12 13:50:29 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:50:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812135029.19284.61301@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=56&rev2=57 ------------------------------------------------------------------------------ == Preliminary checks == 1. Is your sound system plugged in and switched on. I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-( - 2. Is your speaker or microphone muted? Check here: - [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] - [[Audio/CheckForMutedMicrophone|Check for muted microphone]] - - ---- /!\ '''Edit conflict - other version:''' ---- 2. Is your speaker or microphone muted? Check here (9.10 and later) : * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] - - ---- /!\ '''Edit conflict - your version:''' ---- - - ---- /!\ '''End of edit conflict''' ---- == Checking volume levels == Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Rhythmbox. From noreply at ubuntu.com Thu Aug 12 13:53:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:53:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812135342.19289.62619@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=57&rev2=58 ------------------------------------------------------------------------------ Running Ubuntu Karmic Koala (9.10)? [[https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats|First have a look at this list]] of the most common problems with sound in this release. - - == Identifying your hardware == - If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device) - - Please paste the output of the following command at the top of your bug description: - - {{{ - find /proc/asound/card* -type f | grep codec | xargs grep "^Codec\|^Vendor Id\|^Subsystem Id\|^Revision Id" | grep -B2 -A1 $(lspci -nv | grep -A1 0403 | grep Subsystem | sed 's/://g' | awk '{ print $2 }') - }}} - - You should see output similar to: - {{{ - /proc/asound/card0/codec#0:Codec: Realtek ALC883 - /proc/asound/card0/codec#0:Vendor Id: 0x10ec0883 - /proc/asound/card0/codec#0:Subsystem Id: 0x10438284 - /proc/asound/card0/codec#0:Revision Id: 0x100002 - }}} - - If you are about to file a driver bug (e.g., absolutely no applications output sound, microphone does not work even after toggling nocap, speakers continue to emit sound after headphones have been inserted), and you think that you see a bug report that matches your symptoms, '''STOP''' and check the bug's attachments to see if these 4 bits of data match. If all four match '''and''' the symptom matches, subscribe to the existing bug. If '''any''' of the 4 data points disagree, you probably have found one of the myriad cases where many different bugs with different root causes that need different patches have the same symptom on the surface. In which case: '''file a new bug.''' == Preliminary checks == @@ -96, +77 @@ In general, no-sound/low-sound/headphone-no-sound/no auto-mute/etc. bugs should be: * Filed against the '''linux''' source package. * Add the '''kernel-sound''' tag - * '''Subscribe''' (do not assign) the Ubuntu-audio team + * '''Subscribe''' (do not assign) the '''Ubuntu-audio''' team (not the ubuntu-audio-dev team) Only assign bugs to the "alsa-driver" source package if the reporter is using the alsa-source binary package with module-assistant OR is requesting a blacklist or slots/index modification. - * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes. + * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes. If in doubt, file a new bug. + + === Identifying your hardware === + If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device) + + Please paste the output of the following command at the top of your bug description: + + {{{ + find /proc/asound/card* -type f | grep codec | xargs grep "^Codec\|^Vendor Id\|^Subsystem Id\|^Revision Id" | grep -B2 -A1 $(lspci -nv | grep -A1 0403 | grep Subsystem | sed 's/://g' | awk '{ print $2 }') + }}} + + You should see output similar to: + {{{ + /proc/asound/card0/codec#0:Codec: Realtek ALC883 + /proc/asound/card0/codec#0:Vendor Id: 0x10ec0883 + /proc/asound/card0/codec#0:Subsystem Id: 0x10438284 + /proc/asound/card0/codec#0:Revision Id: 0x100002 + }}} + + If you are about to file a driver bug (e.g., absolutely no applications output sound, microphone does not work even after toggling nocap, speakers continue to emit sound after headphones have been inserted), and you think that you see a bug report that matches your symptoms, '''STOP''' and check the bug's attachments to see if these 4 bits of data match. If all four match '''and''' the symptom matches, subscribe to the existing bug. If '''any''' of the 4 data points disagree, you probably have found one of the myriad cases where many different bugs with different root causes that need different patches have the same symptom on the surface. In which case: '''file a new bug.''' + + = Further sound troubleshooting = From noreply at ubuntu.com Thu Aug 12 13:58:23 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 12 Aug 2010 13:58:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100812135823.25545.86190@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=58&rev2=59 ------------------------------------------------------------------------------ Running Ubuntu Karmic Koala (9.10)? [[https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats|First have a look at this list]] of the most common problems with sound in this release. + == Preliminary checks == - == Preliminary checks == 1. Is your sound system plugged in and switched on. I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-( + 2. Is your speaker or microphone muted? Check here (9.10 and later) : * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] @@ -111, +112 @@ * https://help.ubuntu.com/community/SoundTroubleshooting * https://help.ubuntu.com/community/DebuggingSoundProblemsMisc + ---- CategoryDocumentation CategoryBugSquad CategoryDebugging From txwikinger at ubuntu.com Thu Aug 12 17:41:59 2010 From: txwikinger at ubuntu.com (Ralph Janke) Date: Thu, 12 Aug 2010 13:41:59 -0400 Subject: Bugsquad Mentors Updates In-Reply-To: <1281620355.1911.12.camel@wombat> References: <1281620355.1911.12.camel@wombat> Message-ID: <4C643267.6010909@ubuntu.com> Sorry, your meeting times fall within my working times and I do not always have time to attend. I have had a couple of talks with my mentee. We haven't been able to hook up again for about 1 or 2 weeks. I think he is a little busy at the moment. txwikinger On 08/12/2010 09:39 AM, Pedro Villavicencio Garrido wrote: > Hello Mentors!, > > As you might know, we're collecting the updates from our Mentors at > every Bugsquad Meeting but we didn't received yours yet. May you please > send an email to the ubuntu-bugsquad Mailing List with some updates > about your students? This is pretty important for us to know if the > program is doing a good job or not, thanks for your help! > > Have a great day!, > > pedro. > > From mrand at pobox.com Thu Aug 12 21:01:38 2010 From: mrand at pobox.com (Marc Randolph) Date: Thu, 12 Aug 2010 16:01:38 -0500 Subject: [Ubuntu-bugcontrol] Latest Updates from Mentors In-Reply-To: <1279135188.2082.35.camel@wombat> References: <1279135188.2082.35.camel@wombat> Message-ID: On Wed, Jul 14, 2010 at 2:19 PM, Pedro Villavicencio Garrido wrote: > Hello folks, > > At our last BugSquad meeting we asked for Mentors updates to see how > their students are doing it, the updates we got during the meeting: > > om26er: His student is working on Empathy bugs since om26er adopted that > package, he said the student is a learner and get things done in no > time. > > qense: The student was focusing on the Synaptics input driver, but he > felt a bit lonely there. There weren't much people working on those kind > of drivers. He's a quick learner as well. > > hggdh: Didn't heard from his student since 3 weeks, the student was > unassigned and he's looking for another one. > > pedro: Currently working with elopio and njin, the first one is focusing > on gwibber, gnome-media and working on bugs without a package. njin just > started with the program a day ago and he's working on bugs without a > package. > > We encourage all the mentors on the list that are currently working with > a student to send a short update to know what's going on on their side, > please reply to this email mentors ;-). > > If you're looking for a new student to mentor please have a look to: > > https://wiki.ubuntu.com/BugSquad/Mentors/Students > > And let us know which student you'd like to help. > > Looking forward to read your updates ;-) > > Have a nice day, Sorry for the slow response - I was waiting until I had something more meaningful to report. I've been in contact with both chilicuil and Dr. Kenobi. Both of them continue to express interest, but they both appear (and myself too, actually) to be pretty busy with real life, so no specific triaging questions have come up yet. Have fun, Marc From noreply at ubuntu.com Sat Aug 14 16:14:51 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 14 Aug 2010 16:14:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGNOMEPowerManager=22_by?= =?utf-8?q?_cyan-spam?= Message-ID: <20100814161451.18001.20134@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by cyan-spam: http://wiki.ubuntu.com/DebuggingGNOMEPowerManager?action=diff&rev1=32&rev2=33 The comment on the change is: add link to bug 481312 under known bugs ------------------------------------------------------------------------------ '''Closed''' || '''Bug#''' || '''Description''' || - || [[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896|#8896]] || This bug can be identified by ... || + || [[https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/481312|481312]] || Laptop suspends when connecting/disconnecting power (caused by bad BIOS) || == Non-bugs == From noreply at ubuntu.com Sun Aug 15 08:20:46 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 15 Aug 2010 08:20:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_pascal-devuyst?= Message-ID: <20100815082046.31958.60631@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pascal-devuyst: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=44&rev2=45 The comment on the change is: Added Opinion status ------------------------------------------------------------------------------ * If you have to ask the reporter questions, set the bug to {{{Incomplete}}} * Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail. * <> + * '''Opinion''': + * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on the them, but discussion can still be on-going. + * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months. * '''Invalid''': * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter * This should also be used if the reported problem is not a bug at all, but for example user error From brian at ubuntu.com Mon Aug 16 17:00:31 2010 From: brian at ubuntu.com (Brian Murray) Date: Mon, 16 Aug 2010 10:00:31 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Status" by pascal-devuyst In-Reply-To: <20100815082046.31958.60631@jostaberry.canonical.com> References: <20100815082046.31958.60631@jostaberry.canonical.com> Message-ID: <20100816170030.GD11024@murraytwins.com> On Sun, Aug 15, 2010 at 08:20:46AM -0000, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The following page has been changed by pascal-devuyst: > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=44&rev2=45 > > The comment on the change is: > Added Opinion status > > ------------------------------------------------------------------------------ > * If you have to ask the reporter questions, set the bug to {{{Incomplete}}} > * Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail. > * <> > + * '''Opinion''': > + * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on the them, but discussion can still be on-going. > + * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months. It might be worth mentioning the date the three month counter started on. -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From kamusin at gmail.com Tue Aug 17 13:47:07 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 17 Aug 2010 09:47:07 -0400 Subject: Announcing the Next Ubuntu Bug Day! - August 19th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Banshee! * 72 New bugs need a hug * 15 Incompletes bugs need a status check * 19 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 19th August 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100819 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From noreply at ubuntu.com Tue Aug 17 12:54:57 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 17 Aug 2010 12:54:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20100817125457.11786.32887@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pvillavi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=233&rev2=234 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100819| Banshee]] || hugday-20100819 || || [[UbuntuBugDay/20100715| Pidgin]] || hugday-20100715 || || [[UbuntuBugDay/20100701| bugs without a package]] || hugday-20100708 || || [[UbuntuBugDay/20100701| Xkeyboard-config]] || hugday-20100701 || From brian at ubuntu.com Wed Aug 18 16:41:22 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 18 Aug 2010 09:41:22 -0700 Subject: New Launchpad Feature - Easier Duplicate Consolidation Message-ID: <20100818164122.GW11024@murraytwins.com> I wanted to let you know about a new Launchpad feature that landed on production with the last release. It is now possible to mark a bug with duplicates as a duplicate of another bug[1]. This should obsolete lp-set-dup in ubuntu-dev-tools. If you have any issues with it please report a bug about malone. Additionally, if you feel like thanking somebody don't thank me - thank Deryck! [1] http://blog.launchpad.net/cool-new-stuff/dupety-dupe -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Aug 18 16:46:28 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 18 Aug 2010 16:46:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingApparmor=22_by_jdstrand?= Message-ID: <20100818164628.20497.25032@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jdstrand: http://wiki.ubuntu.com/DebuggingApparmor?action=diff&rev1=19&rev2=20 ------------------------------------------------------------------------------ = Fixing profile bugs = - Fixing apparmor profiles bugs is usually straightforward. Enable 'complain' mode (see above), then exercise your application. You can then either use 'aa-logprof' to walk you through the process of updating the profile, or simply edit the profile directly. Please use the 'tunables' found in /etc/apparmor.d/tunables when appropriate. Eg, rather than using a rule like:{{{ + Fixing apparmor profile bugs is usually straightforward. Enable 'complain' mode (see above), then exercise your application. You can then either use 'aa-logprof' to walk you through the process of updating the profile, or simply edit the profile directly. Please use the 'tunables' found in /etc/apparmor.d/tunables when appropriate. Eg, rather than using a rule like:{{{ /home/*/ r, }}}use:{{{ @{HOME}/ r, @@ -86, +86 @@ }}} After the profile is working as desired, you can attach it to the bug report, stating that you have a working profile. For more on editing and creating profiles, see the community [[https://help.ubuntu.com/community/AppArmor|AppArmor]] documentation. + + Ubuntu 10.10 and higher users can also use the local include mechanism by adding rules to the /etc/apparmor.d/local/... file instead of adjusting the profile directly. This is particular helpful for small additions that aren't suitable for all of Ubuntu, but there are caveats with this approach. Please see /etc/apparmor.d/local/README for details. = AppArmor and chroot environments = From noreply at ubuntu.com Wed Aug 18 16:51:46 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 18 Aug 2010 16:51:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingApparmor=22_by_jdstrand?= Message-ID: <20100818165146.20667.77694@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jdstrand: http://wiki.ubuntu.com/DebuggingApparmor?action=diff&rev1=20&rev2=21 ------------------------------------------------------------------------------ After the profile is working as desired, you can attach it to the bug report, stating that you have a working profile. For more on editing and creating profiles, see the community [[https://help.ubuntu.com/community/AppArmor|AppArmor]] documentation. - Ubuntu 10.10 and higher users can also use the local include mechanism by adding rules to the /etc/apparmor.d/local/... file instead of adjusting the profile directly. This is particular helpful for small additions that aren't suitable for all of Ubuntu, but there are caveats with this approach. Please see /etc/apparmor.d/local/README for details. + Starting with Ubuntu 10.10, users can also use the local include mechanism by adding rules to the /etc/apparmor.d/local/... file instead of adjusting the profile directly. This is particular helpful for small additions that aren't suitable for all of Ubuntu, but there are caveats with this approach. Please see /etc/apparmor.d/local/README for details. = AppArmor and chroot environments = From noreply at ubuntu.com Wed Aug 18 18:40:00 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 18 Aug 2010 18:40:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_pascal-devuyst?= Message-ID: <20100818184000.23531.3153@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pascal-devuyst: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=45&rev2=46 The comment on the change is: added starting date as suggested by Brian Murray ------------------------------------------------------------------------------ * <> * '''Opinion''': * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on the them, but discussion can still be on-going. - * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months. + * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months starting from July 7th, 2010. * '''Invalid''': * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter * This should also be used if the reported problem is not a bug at all, but for example user error From noreply at ubuntu.com Wed Aug 18 18:40:17 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 18 Aug 2010 18:40:17 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_pascal-devuyst?= Message-ID: <20100818184017.23534.18885@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pascal-devuyst: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=46&rev2=47 ------------------------------------------------------------------------------ * <> * '''Opinion''': * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on the them, but discussion can still be on-going. + + ---- /!\ '''Edit conflict - other version:''' ---- * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months starting from July 7th, 2010. + + ---- /!\ '''Edit conflict - your version:''' ---- + * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months starting from July 7th, 2010. + + ---- /!\ '''End of edit conflict''' ---- * '''Invalid''': * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter * This should also be used if the reported problem is not a bug at all, but for example user error From noreply at ubuntu.com Wed Aug 18 18:42:12 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 18 Aug 2010 18:42:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_pascal-devuyst?= Message-ID: <20100818184212.23522.86269@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pascal-devuyst: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=47&rev2=48 The comment on the change is: added starting date as suggested by Brian Murray ------------------------------------------------------------------------------ * <> * '''Opinion''': * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on the them, but discussion can still be on-going. - - ---- /!\ '''Edit conflict - other version:''' ---- * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months starting from July 7th, 2010. - - ---- /!\ '''Edit conflict - your version:''' ---- - * This status 'opinion' is considered an experiment, and will be closely monitored over the next 3 months starting from July 7th, 2010. - - ---- /!\ '''End of edit conflict''' ---- * '''Invalid''': * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter * This should also be used if the reported problem is not a bug at all, but for example user error From ilidrissiamine at gmail.com Thu Aug 19 21:55:30 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Thu, 19 Aug 2010 21:55:30 +0000 Subject: Hugday proposition: Jaunty bugs Message-ID: Hello, fellow BugSquaders :) I'd like to propose a new Hug Day target: Jaunty bugs. Jaunty will be EOL in 2 months, and a simple search reveals more than 700 bugs having the jaunty tag. These bugs need confirmation and testing. It would be good if I could organize it on September 2nd (not 08/26, since there is Ubuntu translations there). Please share your thoughts and opinions ;) Thank you, Mohamed Amine IL Idrissi -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Thu Aug 19 22:39:15 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 19 Aug 2010 15:39:15 -0700 Subject: Hugday proposition: Jaunty bugs In-Reply-To: References: Message-ID: <20100819223915.GE11024@murraytwins.com> On Thu, Aug 19, 2010 at 09:55:30PM +0000, Mohammed Amine IL Idrissi wrote: > Hello, fellow BugSquaders :) > > I'd like to propose a new Hug Day target: Jaunty bugs. Jaunty will be EOL in > 2 months, and a simple search reveals more than 700 bugs having the jaunty > tag. These bugs need confirmation and testing. This sounds like an interesting idea to me but 700+ is quite a large target. Perhaps it could be made more manageable by looking at a particular status like Confirmed or Triaged rather than every bug. Also depending on how you searched the results count may be of bug tasks and not bugs. -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From ilidrissiamine at gmail.com Thu Aug 19 23:30:23 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Thu, 19 Aug 2010 23:30:23 +0000 Subject: Hugday proposition: Jaunty bugs In-Reply-To: <20100819223915.GE11024@murraytwins.com> References: <20100819223915.GE11024@murraytwins.com> Message-ID: Of course, we can't include 700+ bugs. But we can reduce it by including 100-200 bugs in the list. Here's some search results: - There were 228 New bugs. - There were 271 Incomplete bugs. - There were 215 Confirmed bugs. Which is a total of 713 bugs. Maybe we should take 100-150 bugs from each status? (150 might sound like a high number, but there's a probability that there are a lot of bugs with an inappropriate tag) Thank you, Mohamed Amine IL Idrissi PS: It seems bughelper is no longer in the repos. Is there an alternative to this package (and more specifically the bugnumbers utility)? On Thu, Aug 19, 2010 at 10:39 PM, Brian Murray wrote: > On Thu, Aug 19, 2010 at 09:55:30PM +0000, Mohammed Amine IL Idrissi wrote: > > Hello, fellow BugSquaders :) > > > > I'd like to propose a new Hug Day target: Jaunty bugs. Jaunty will be EOL > in > > 2 months, and a simple search reveals more than 700 bugs having the > jaunty > > tag. These bugs need confirmation and testing. > > This sounds like an interesting idea to me but 700+ is quite a large > target. Perhaps it could be made more manageable by looking at a > particular status like Confirmed or Triaged rather than every bug. > > Also depending on how you searched the results count may be of bug tasks > and not bugs. > > -- > Brian Murray > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkxtspMACgkQDTAwc5ER+zXyegCeNjmj5cYQU4qceS1Kg29Ye/nK > QEkAnjKHA+hSSFp2F2GR9WbfTyNpRXK9 > =HKtj > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From micahg at ubuntu.com Thu Aug 19 23:36:11 2010 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 19 Aug 2010 18:36:11 -0500 Subject: Hugday proposition: Jaunty bugs In-Reply-To: References: <20100819223915.GE11024@murraytwins.com> Message-ID: <4C6DBFEB.6060501@ubuntu.com> This seems like a good target for after Final Freeze, perhaps we should pick a default app with a lot of bugs for the next few hugdays to try to get any last minute fixes into Maverick? Perhaps just the hottest bugs that have been found in maverick to date? Or maybe the most recent 100 bugs each in New, Confirmed, Incomplete? On 08/19/2010 06:30 PM, Mohammed Amine IL Idrissi wrote: > Of course, we can't include 700+ bugs. But we can reduce it by including > 100-200 bugs in the list. > Here's some search results: > - There were 228 New bugs. > - There were 271 Incomplete bugs. > - There were 215 Confirmed bugs. > Which is a total of 713 bugs. Maybe we should take 100-150 bugs from > each status? (150 might sound like a high number, but there's a > probability that there are a lot of bugs with an inappropriate tag) > > Thank you, > Mohamed Amine IL Idrissi > PS: It seems bughelper is no longer in the repos. Is there an > alternative to this package (and more specifically the bugnumbers utility)? > > On Thu, Aug 19, 2010 at 10:39 PM, Brian Murray > wrote: > > On Thu, Aug 19, 2010 at 09:55:30PM +0000, Mohammed Amine IL Idrissi > wrote: > > Hello, fellow BugSquaders :) > > > > I'd like to propose a new Hug Day target: Jaunty bugs. Jaunty will > be EOL in > > 2 months, and a simple search reveals more than 700 bugs having > the jaunty > > tag. These bugs need confirmation and testing. > > This sounds like an interesting idea to me but 700+ is quite a large > target. Perhaps it could be made more manageable by looking at a > particular status like Confirmed or Triaged rather than every bug. > > Also depending on how you searched the results count may be of bug tasks > and not bugs. > > -- > Brian Murray > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkxtspMACgkQDTAwc5ER+zXyegCeNjmj5cYQU4qceS1Kg29Ye/nK > QEkAnjKHA+hSSFp2F2GR9WbfTyNpRXK9 > =HKtj > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From david.lygagnon at gmail.com Fri Aug 20 17:22:25 2010 From: david.lygagnon at gmail.com (David Ly-Gagnon) Date: Fri, 20 Aug 2010 10:22:25 -0700 Subject: looking for a mentor Message-ID: Hello, I am looking for a mentor. I now have some time to work on triaging some bugs. Is anyone interested? cheers, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ilidrissiamine at gmail.com Fri Aug 20 17:29:23 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Fri, 20 Aug 2010 17:29:23 +0000 Subject: looking for a mentor In-Reply-To: References: Message-ID: This is what you're looking for: https://wiki.ubuntu.com/BugSquad/Mentors Please follow the instructions there (precisely in the 'How To Request a Mentor' section). Regards, Mohamed Amine IL Idrissi On Fri, Aug 20, 2010 at 5:22 PM, David Ly-Gagnon wrote: > > Hello, > > I am looking for a mentor. I now have some time to work on triaging some bugs. > Is anyone interested? > > cheers, > David > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sun Aug 22 08:55:02 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 22 Aug 2010 08:55:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_simar?= Message-ID: <20100822085502.6777.87162@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=49&rev2=50 ------------------------------------------------------------------------------ * you should reset the status to New. [[Hggdh]] * Converting Question to Bug, the reporter of Question, or confirming comments there, can be counted as another person(s), so the new bug can be right away set to Confirmed in such case? * Common sense should prevail. If ''more than one person'' can confirm the issue, then it should be Confirmed. [[Hggdh]] + * What if the bug can be confirmed even with the information provided by a bug reported during bug reporting and now the bug reporter and any other affected person cannot provide/is not available for providing further information, due to any reason? + * In that case you should mark the bug as Invalid, with a comment to the bug reporter that he could reopen the bug by resetting the bug status to 'New' again ,any time when he can provide us with further information. [[simar]] ---- CategoryBugSquad From kamus at ubuntu.com Mon Aug 23 16:31:28 2010 From: kamus at ubuntu.com (Kamus) Date: Mon, 23 Aug 2010 12:31:28 -0400 Subject: Announcing the Next Ubuntu Bug Day! - August 26th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Ubuntu Translations! * 15 New bugs need a hug * 31 Incompletes bugs need a status check * 42 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 26th August 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100826 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From jose.angel.fernandez.freire at gmail.com Tue Aug 24 11:08:44 2010 From: jose.angel.fernandez.freire at gmail.com (=?ISO-8859-1?Q?Jos=E9_=C1=2E_Fern=E1ndez?=) Date: Tue, 24 Aug 2010 11:08:44 +0000 Subject: Cancelar: Ubuntu-bugsquad Digest, Vol 50, Issue 20 Message-ID: <1282648124.4420.3.camel@unr> A non-text attachment was scrubbed... Name: calendar.ics Type: text/calendar Size: 3480 bytes Desc: not available URL: From charlieb at nashuaisp.co.za Mon Aug 23 13:40:46 2010 From: charlieb at nashuaisp.co.za (Charlie Brook) Date: Mon, 23 Aug 2010 15:40:46 +0200 Subject: ref ubuntu ver 10.04 bug report Message-ID: <63C7E452EA194DB38F2EF9164126FCEB@xgr> I am reporting a bug in Ubuntu 10.04 and 10.04.01 and I couldn't find any other way of communicating. The program does not run on my PC. It boots up with the purple screen for a short while, then starts scrolling script and then freezes at the point shown on the attached photo. Nothing I do can get it going again. Ubuntu 8.04 and 9.10 both run on my PC although 9.10 first went into a terminal window before continuing to load the GUI Background: I am a Linux novice with little previous experience. The Ubuntu versions I have tried which do not work are 10.4 and 10.4.1 downloaded as iso files from the internet and burned to CD. The same CD which has 10.4 on it was used to install Ubuntu on 2 other PC's without a problem. They were both AMD CPU machines with low specifications. Specifications of present PC on which the problem is found CPU: Intel E8400 core 2 duo Motherboard: Gigabyte GA-G41M-ES2L with onboard video RAM: 2 GB Kingston Hard Drive 500GB Seagate SATA DVD Sony DVD RW Samsung I don't know what other information would be of help Regards Charlie Brook -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMG_5486-2.jpg Type: image/jpeg Size: 420386 bytes Desc: not available URL: From noreply at ubuntu.com Mon Aug 23 11:58:50 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 23 Aug 2010 11:58:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_dpm?= Message-ID: <20100823115850.27151.4955@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by dpm: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=234&rev2=235 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100826| Ubuntu Translations]] || hugday-20100826 || || [[UbuntuBugDay/20100819| Banshee]] || hugday-20100819 || || [[UbuntuBugDay/20100715| Pidgin]] || hugday-20100715 || || [[UbuntuBugDay/20100701| bugs without a package]] || hugday-20100708 || From noreply at ubuntu.com Tue Aug 24 13:25:23 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 24 Aug 2010 13:25:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_pvillavi?= Message-ID: <20100824132523.19166.36811@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pvillavi: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=131&rev2=132 ------------------------------------------------------------------------------ == Regressions == - A regression is a bug introduced after an update. These kind of bugs are especially important because if something breaks that used to work it interferes with the customs of a user. This attracts more attention than normal bugs. + A regression is a bug introduced after an update. These kind of bugs are especially important because if something breaks that used to work it interferes with the customs of a user. This attracts more attention than normal bugs. To make keeping track of regressions easier we use tags. Please make sure to use the tags when doing Triage. - To make keeping track of regressions easier we use tags. + <> - This table shows when to use which tag: - ||'''A regression in the'''||'''Tag'''|| - ||current release||''regression-release''|| - ||updated packages||''regression-update''|| - ||proposed updates||''regression-proposed''|| - ||next release||''regression-potential''|| Once tagged, the bugs will appear on the [[http://qa.ubuntu.com/reports/regression/regression_tracker.html|regression tracking page]] and will from there be escalated to the development teams. See [[QATeam/RegressionTracking]] for more information. From ian at codingfriends.com Tue Aug 24 18:40:48 2010 From: ian at codingfriends.com (Ian Porter) Date: Tue, 24 Aug 2010 19:40:48 +0100 Subject: ref ubuntu ver 10.04 bug report In-Reply-To: <63C7E452EA194DB38F2EF9164126FCEB@xgr> References: <63C7E452EA194DB38F2EF9164126FCEB@xgr> Message-ID: Hi Charlie, The only thing that I can think of is something that was similar to myself, in that the BIOS was not setting up the video memory correctly and thus telling the kernel where to place the video memory on the onboard graphics card. Are you able to use a 1GB of ram to see if that sorts out the problem ? Regards Ian On Mon, Aug 23, 2010 at 2:40 PM, Charlie Brook wrote: > I am reporting a bug in Ubuntu 10.04 and 10.04.01 and I couldn't find any > other way of communicating. > The program does not run on my PC. It boots up with the purple screen for a > short while, then starts scrolling script and then freezes at the point > shown on the attached photo. Nothing I do can get it going again. > Ubuntu 8.04 and 9.10 both run on my PC although 9.10 first went into a > terminal window before continuing to load the GUI > > Background: > I am a Linux novice with  little previous experience. > The Ubuntu versions I have tried which do not work are 10.4 and 10.4.1 > downloaded as iso files from the internet and burned to CD. The same CD > which has 10.4 on it was used to install Ubuntu on 2 other PC's without a > problem. They were both AMD CPU machines with low specifications. > > Specifications of present PC on which the problem is found > CPU:                        Intel E8400 core 2 duo > Motherboard:        Gigabyte GA-G41M-ES2L with onboard video > RAM:                        2 GB  Kingston > Hard Drive            500GB Seagate SATA > DVD                        Sony > DVD RW                Samsung > > I don't know what other information would be of help > > Regards > Charlie Brook > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- King regards Ian Porter www: www.codingfriends.com From stenten at gmail.com Tue Aug 24 18:52:55 2010 From: stenten at gmail.com (Steven) Date: Tue, 24 Aug 2010 14:52:55 -0400 Subject: ref ubuntu ver 10.04 bug report In-Reply-To: <63C7E452EA194DB38F2EF9164126FCEB@xgr> References: <63C7E452EA194DB38F2EF9164126FCEB@xgr> Message-ID: Looks like a problem with the intel graphics driver being loaded. See if you can boot into safe graphics mode and then file a bug with 'ubuntu-bug xserver-xorg-video-intel', and also attach /var/log/kern.log. -Stenten -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.schuster at kdemail.net Wed Aug 25 16:56:45 2010 From: david.schuster at kdemail.net (David Schuster) Date: Wed, 25 Aug 2010 18:56:45 +0200 Subject: Kubuntu package libqyoto4.5-cil Message-ID: <201008251856.45658.david.schuster@kdemail.net> Hello, I am trying to develop Qt software using the Qt bindings of the KDE project. (Qyoto and Kimono) When I used the debian package "libqyoto4.5-cil" theres a broken symlink in /usr/lib/cli/qt-dotnet/libqyoto.so So every binary or dll built with the bindings will throw an DllNotFoundException at startup. FIX: #rm libqyoto.so && sudo ln -s ../../libqyoto.so.2 libqyoto.so I was in contact with the developer of the bindings and he said I should report the bug to this list, hope it helps, its a real annoying small bug. Regards, Dave From sense at ubuntu.com Thu Aug 26 14:21:12 2010 From: sense at ubuntu.com (Sense Hofstede) Date: Thu, 26 Aug 2010 16:21:12 +0200 Subject: Beginners Team and Bug Squad Mentoring In-Reply-To: References: Message-ID: On 25 August 2010 14:01, Duane Hinnen wrote: > I am a member of the Ubuntu Beginners Team. We help new user with Ubuntu, > and help them get involved in the community.  We have Focus Groups that help > users get involved in different parts of the community. We have a Launchpad > Focus Group that is primarily involved in teaching people about Bug Triage. > Recently we have been drawing up guidelines and better organizing our > efforts. While doing this we realized that Bug Squad was also reorganising > and reinvigorating their effort. We are interested in determining how these > two efforts can best serve the community. First I want to open a dialogue > about the simultaneous  existence of the two programs, and if you feel there > is room for both. The Beginners Team is for community members who not only > want to learn about the community but want to become a mentor themselves. I > feel that would be the main distinction between the two efforts. Users are > assigned a mentor and after showing a certain level of commitment and > expertise are granted membership in the Beginners Team at which point they > start mentoring people themselves. Other than that our process is very > similar to the Bug Squad Mentor program. I have thought a lot about this and > if the members responsible for the Bug Squad Mentor program feel this is a > duplication of effort that is somehow a negative we can do one of two > things. > > 1. Our members responsible for the Launchpad Focus Group would join the Bug > Squad Mentor Program. Then when users approach the Beginners Team about Bug > Mentoring they would be assigned a Beginners Team Mentor who is also a Bug > Squad Mentor. They would then go through the established program you have in > place. Then at a certain time in the process also become a Beginners Team > member. > > 2. We could gracefully close up our Bug Triage Mentoring and just send > people your way. > > Please let me know what you think about having two places in the community > people could go for Triage Mentoring. If you feel that is a problem let me > know what you think the best solution might be. One of the 2 ideas I > outlined or possibly something I have not thought of. > > Thank you for your serious consideration of this matter. > > -- > Duane Hinnen > duanedesign at ubuntu.com > sip:duanedesign at ekiga.net > Hello, Thank you for raising this point. It is good to take a look at this and make sure we are not wasting time on duplicate efforts. Let me first explain our system before I continue to explore how both programmes could interact. The Bug Squad Mentorship programme works like this: after reading the instructions on the programme's wiki page [1] and making the requested information available the prospective students request membership of the 'bugsquad-mentorship' Launchpad team. [2] The four administrators of the programme — Pedro Villavicencio, hggdh, Vishnoo, and I — go through the list to check whether the applicants fulfil the requirements. If that isn't the case the applicant is rejected and asked to reapply once (s)he has provided all the required information. If the applicant fulfils the requirements the administrator adds him or her to the list of prospective students. [3] If there is a mentor available — the mentors are listed in a table on the programme's wiki page [1] — one of the administrator assigns a student to the mentor, basing his decision on the timezone and interests of the student and the available mentor. Then he mails the student to let him or her know that a mentor is assigned to him or her. A similar mail is sent to the mentor. In that mail the mentor is urged to make first contact as soon as possible. The mentors are asked to provide monthly updates of the status of their students either at the Bug Squad meeting, or on the mailing list if they weren't available during the meeting times. The goal of the mentorship programme is not to make the students mentors themselves, but to make them ready for membership of Ubuntu Bug Control. When a mentor approves the application of his or her student for Ubuntu Bug Control, the application is accepted and the student becomes a former student. I hope that the above makes our methods clear to you. Now, lets return to the subject of the intersections of both programmes. I feel that it would be a waste of effort to run both programmes next to each other, separately. Having two places where people can get bug triaging mentorship could work confusing. It would also spread the mentors thin, while we need any mentor we can get. Letting the two programmes exist next to each other is not what I would prefer. Instead I would suggest, and I hope that this isn't painful for you — I really appreciate your efforts, because we always need more triagers — to ask your mentors to join the Bug Squad Mentorship programme and make that the only programme. You could, like you suggested, refer to us when people need mentorship. That would seem like the best solution to me, since the Bug Squad is the closest you can get to the Bug Squad, so you're sure its mentorship programme is following the latest recommendations and guidelines, and that the students have easy access to the Bug Control. Another reason is that I, personally, feel that the Beginner Team is more about general introductions to the community. I.e. explaining the people how to use Launchpad, or learning them how to use the community resources. More specific things, like teaching the process of bug triaging, seems better at place in the Bug Squad. I would also like to hear what the other Bug Squad Mentorship programme administrators think, or anyone else. Do you agree? Of course, suggestions for improving the current system are also welcome, if the Beginner Team has got a different (better?) process for admitting students. [1] https://wiki.ubuntu.com/BugSquad/Mentors [2] https://launchpad.net/~bugsquad-mentorship [3] https://wiki.ubuntu.com/BugSquad/Mentors/Students Kind regards, -- Sense Hofstede http://sensehofstede.nl/ From noreply at ubuntu.com Thu Aug 26 10:18:56 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 26 Aug 2010 10:18:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_mar?= =?utf-8?q?krijckenberg?= Message-ID: <20100826101856.2953.93573@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by markrijckenberg: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=59&rev2=60 ------------------------------------------------------------------------------ * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] == Checking volume levels == + Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Rhythmbox. You can access the volume levels for the various channels from the command line or the GUI. @@ -36, +37 @@ * Starting with Ubuntu 7.04, the sound volume control is also accessible from Menu->Sound&Video->Volume Control. It may be hidden in your menus but can be shown by going to System > Preferences > Main Menu and under Applications > Sound&Video ticking Volume Control. == Checking sound device assignment == + 1. Most sound applications output to card0 by default. In some cases, other audio devices (like a USB MIDI Keyboard) might be recognized as a soundcard and take card0, bumping your real soundcard to card1. To see which devices are connected to which cards, do the following: * {{{ cat /proc/asound/cards @@ -47, +49 @@ The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth. In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device. For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Rhythmbox, but your other applications will play through your other soundcard. FIXME PLEASE: for more information go to the ALSA-Configuration kernel document. == Checking permissions and resources == + 1. Make sure that all users needing access to the Sound Device can "Use audio devices" in the "User Privileges" tab of users-admin (System->Administration->Users and Groups). 1. Test different "Sound Servers": Go to System > Preferences > Sound ("Multimedia Systems Selector" in earlier editions of Ubuntu). From there, you can test the different options. In some scenarios several different sound servers may be installed, and only one may work. This is probably the origin of the problem if you cannot play audio with xine or rhythmbox, but you can with xmms or helix/realplayer. 1. If you application sounds works, but your system sounds does not (login, logout, error sounds...) try removing the .asoundrc* files from your own directory (e.g. with 'rm .asoundrc*'). It should make the system sounds work without a reboot. 1. If you can get absolutely no sound and you have an onboard sound chip you can try to disable it in the BIOS. This solves the problem is some cases. 1. If you have no sound and you have a regular sound card type "lsmod | grep snd" in the terminal and see if there is more than one card listed. It's possible that you have a motherboard sound chip that is interfering. Add it to the bottom of the blacklist file. For example, sudo nano /etc/modprobe.d/blacklist then add "blacklist snd_via82xx" to the bottom. - = Reporting Sound Bugs = @@ -85, +87 @@ * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes. If in doubt, file a new bug. === Identifying your hardware === + If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device) Please paste the output of the following command at the top of your bug description: @@ -103, +106 @@ If you are about to file a driver bug (e.g., absolutely no applications output sound, microphone does not work even after toggling nocap, speakers continue to emit sound after headphones have been inserted), and you think that you see a bug report that matches your symptoms, '''STOP''' and check the bug's attachments to see if these 4 bits of data match. If all four match '''and''' the symptom matches, subscribe to the existing bug. If '''any''' of the 4 data points disagree, you probably have found one of the myriad cases where many different bugs with different root causes that need different patches have the same symptom on the surface. In which case: '''file a new bug.''' - - = Further sound troubleshooting = After reporting a bug you might want to see the community documentation: + + * https://help.ubuntu.com/community/SoundTroubleshootingProcedure * https://help.ubuntu.com/community/Sound * https://help.ubuntu.com/community/SoundTroubleshooting * https://help.ubuntu.com/community/DebuggingSoundProblemsMisc - ---- CategoryDocumentation CategoryBugSquad CategoryDebugging From brian at ubuntu.com Thu Aug 26 17:30:41 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 26 Aug 2010 10:30:41 -0700 Subject: [noreply@ubuntu.com: [Ubuntu Wiki] Update of "Bugs/Status" by simar] Message-ID: <20100826173041.GC27845@murraytwins.com> ----- Forwarded message from Ubuntu Wiki ----- Date: Sun, 22 Aug 2010 08:55:02 -0000 From: Ubuntu Wiki To: Ubuntu Wiki Subject: [Ubuntu Wiki] Update of "Bugs/Status" by simar X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=49&rev2=50 ------------------------------------------------------------------------------ * you should reset the status to New. [[Hggdh]] * Converting Question to Bug, the reporter of Question, or confirming comments there, can be counted as another person(s), so the new bug can be right away set to Confirmed in such case? * Common sense should prevail. If ''more than one person'' can confirm the issue, then it should be Confirmed. [[Hggdh]] + * What if the bug can be confirmed even with the information provided by a bug reported during bug reporting and now the bug reporter and any other affected person cannot provide/is not available for providing further information, due to any reason? + * In that case you should mark the bug as Invalid, with a comment to the bug reporter that he could reopen the bug by resetting the bug status to 'New' again ,any time when he can provide us with further information. [[simar]] ----- End forwarded message ----- I find this question rather confusing - particularly "bug can be confirmed" ... "cannot provide". These two things contradict themselves in my mind. Perhaps the question should really be "bug can not be confirmed"? -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Thu Aug 26 17:22:30 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 26 Aug 2010 17:22:30 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_brian-mur?= =?utf-8?q?ray?= Message-ID: <20100826172230.16383.10398@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=132&rev2=133 ------------------------------------------------------------------------------ == Regressions == - A regression is a bug introduced after an update. These kind of bugs are especially important because if something breaks that used to work it interferes with the customs of a user. This attracts more attention than normal bugs. To make keeping track of regressions easier we use tags. Please make sure to use the tags when doing Triage. + A regression is a bug introduced after an update. These kind of bugs are especially important because if something breaks that used to work it interferes with the workflows of software users. These can be more obvious and painful for users than bugs. To make keeping track of regressions easier we use tags. Please make sure to use the tags when doing Triage. <> From noreply at ubuntu.com Thu Aug 26 19:05:18 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 26 Aug 2010 19:05:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/FAQ=22_by_joshuaschroij?= =?utf-8?q?en?= Message-ID: <20100826190518.16678.72483@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by joshuaschroijen: http://wiki.ubuntu.com/BugSquad/FAQ?action=diff&rev1=12&rev2=13 The comment on the change is: Fixed a little grammatical error ( 'i' should be 'I' ) ------------------------------------------------------------------------------ = General Questions = - == How do i start to Triage a bug ? == + == How do I start to Triage a bug ? == We recommend to every new triager to read our [[https://wiki.ubuntu.com/Bugs/HowToTriage|Triage Guide]] and to request a [[https://wiki.ubuntu.com/BugSquad/Mentors|Mentor]], if you have doubts regarding any part of the document please contact us. From cyan.spam at gmail.com Fri Aug 27 17:24:44 2010 From: cyan.spam at gmail.com (David Tombs) Date: Fri, 27 Aug 2010 13:24:44 -0400 Subject: Kubuntu package libqyoto4.5-cil In-Reply-To: <201008251856.45658.david.schuster@kdemail.net> References: <201008251856.45658.david.schuster@kdemail.net> Message-ID: <4C77F4DC.6030208@gmail.com> On 08/25/2010 12:56 PM, David Schuster wrote: > Hello, > > I am trying to develop Qt software using the Qt bindings of the KDE project. > (Qyoto and Kimono) > When I used the debian package "libqyoto4.5-cil" theres a broken symlink > in /usr/lib/cli/qt-dotnet/libqyoto.so > So every binary or dll built with the bindings will throw an > DllNotFoundException at startup. > FIX: #rm libqyoto.so && sudo ln -s ../../libqyoto.so.2 libqyoto.so > > I was in contact with the developer of the bindings and he said I should > report the bug to this list, hope it helps, its a real annoying small bug. > > Regards, Dave > Hi David, This list is actually not for /filing/ bugs but for discussing them. Please file a bug according to the instructions at . You'll probably use "ubuntu-bug libqyoto4.5-cil". Thanks! David From cyan.spam at gmail.com Fri Aug 27 17:37:18 2010 From: cyan.spam at gmail.com (David Tombs) Date: Fri, 27 Aug 2010 13:37:18 -0400 Subject: launchpad +filebug redirect Message-ID: <4C77F7CE.2030404@gmail.com> Hi all, I was just looking at the ReportingBugs wiki page[1] and thought that the current intro (between the two "Reporting Bugs" headers) is a little awkward. It's obviously there because the +filebug launchpad page[2] simply redirects users to the wiki page, and that might confuse users. Since streamlining the bug reporting process is definitely in our favor, I suggest a clearer and less awkward process: what if the +filebug page presented a message to the user that it is no longer the way to report bugs and then just /linked/ to the wiki page for further information? This way we can get rid of the introduction on ReportingBugs, reducing the text users have to read and possibly some confusion for first-time reporters. Thoughts? Thanks, David [1] https://help.ubuntu.com/community/ReportingBugs/ [2] https://bugs.launchpad.net/ubuntu/+filebug/ From cyan.spam at gmail.com Fri Aug 27 18:11:25 2010 From: cyan.spam at gmail.com (David Tombs) Date: Fri, 27 Aug 2010 14:11:25 -0400 Subject: [noreply@ubuntu.com: [Ubuntu Wiki] Update of "Bugs/Status" by simar] In-Reply-To: <20100826173041.GC27845@murraytwins.com> References: <20100826173041.GC27845@murraytwins.com> Message-ID: <4C77FFCD.3020000@gmail.com> On 08/26/2010 01:30 PM, Brian Murray wrote: > ----- Forwarded message from Ubuntu Wiki ----- > > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The following page has been changed by simar: > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=49&rev2=50 > > ------------------------------------------------------------------------------ > * you should reset the status to New. [[Hggdh]] > * Converting Question to Bug, the reporter of Question, or confirming comments there, can be counted as another person(s), so the new bug can be right away set to Confirmed in such case? > * Common sense should prevail. If ''more than one person'' can confirm the issue, then it should be Confirmed. [[Hggdh]] > + * What if the bug can be confirmed even with the information provided by a bug reported during bug reporting and now the bug reporter and any other affected person cannot provide/is not available for providing further information, due to any reason? > + * In that case you should mark the bug as Invalid, with a comment to the bug reporter that he could reopen the bug by resetting the bug status to 'New' again ,any time when he can provide us with further information. [[simar]] > > ----- End forwarded message ----- > > I find this question rather confusing - particularly "bug can be > confirmed" ... "cannot provide". These two things contradict themselves > in my mind. Perhaps the question should really be "bug can not be > confirmed"? > > Good point, Brian. I converted all the comments into an FAQ style; I think it's a bit more professional and clearer. David From simar.i3r at gmail.com Fri Aug 27 18:18:08 2010 From: simar.i3r at gmail.com (Gursimran singh) Date: Fri, 27 Aug 2010 23:48:08 +0530 Subject: [noreply@ubuntu.com: [Ubuntu Wiki] Update of "Bugs/Status" by simar] In-Reply-To: <4C77FFCD.3020000@gmail.com> References: <20100826173041.GC27845@murraytwins.com> <4C77FFCD.3020000@gmail.com> Message-ID: Seems to be better now.. :-)) On Fri, Aug 27, 2010 at 11:41 PM, David Tombs wrote: > On 08/26/2010 01:30 PM, Brian Murray wrote: > > ----- Forwarded message from Ubuntu Wiki ----- > > > > Dear Wiki user, > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for > change notification. > > > > The following page has been changed by simar: > > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=49&rev2=50 > > > > > ------------------------------------------------------------------------------ > > * you should reset the status to New. [[Hggdh]] > > * Converting Question to Bug, the reporter of Question, or confirming > comments there, can be counted as another person(s), so the new bug can be > right away set to Confirmed in such case? > > * Common sense should prevail. If ''more than one person'' can > confirm the issue, then it should be Confirmed. [[Hggdh]] > > + * What if the bug can be confirmed even with the information provided > by a bug reported during bug reporting and now the bug reporter and any > other affected person cannot provide/is not available for providing further > information, due to any reason? > > + * In that case you should mark the bug as Invalid, with a comment to > the bug reporter that he could reopen the bug by resetting the bug status to > 'New' again ,any time when he can provide us with further information. > [[simar]] > > > > ----- End forwarded message ----- > > > > I find this question rather confusing - particularly "bug can be > > confirmed" ... "cannot provide". These two things contradict themselves > > in my mind. Perhaps the question should really be "bug can not be > > confirmed"? > > > > > > Good point, Brian. I converted all the comments into an FAQ style; I > think it's a bit more professional and clearer. > > David > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Fri Aug 27 18:59:11 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 27 Aug 2010 11:59:11 -0700 Subject: [noreply@ubuntu.com: [Ubuntu Wiki] Update of "Bugs/Status" by simar] In-Reply-To: <4C77FFCD.3020000@gmail.com> References: <20100826173041.GC27845@murraytwins.com> <4C77FFCD.3020000@gmail.com> Message-ID: <20100827185911.GJ27845@murraytwins.com> On Fri, Aug 27, 2010 at 02:11:25PM -0400, David Tombs wrote: > On 08/26/2010 01:30 PM, Brian Murray wrote: > > ----- Forwarded message from Ubuntu Wiki ----- > > > > Dear Wiki user, > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > > > The following page has been changed by simar: > > http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=49&rev2=50 > > > > ------------------------------------------------------------------------------ > > * you should reset the status to New. [[Hggdh]] > > * Converting Question to Bug, the reporter of Question, or confirming comments there, can be counted as another person(s), so the new bug can be right away set to Confirmed in such case? > > * Common sense should prevail. If ''more than one person'' can confirm the issue, then it should be Confirmed. [[Hggdh]] > > + * What if the bug can be confirmed even with the information provided by a bug reported during bug reporting and now the bug reporter and any other affected person cannot provide/is not available for providing further information, due to any reason? > > + * In that case you should mark the bug as Invalid, with a comment to the bug reporter that he could reopen the bug by resetting the bug status to 'New' again ,any time when he can provide us with further information. [[simar]] > > > > ----- End forwarded message ----- > > > > I find this question rather confusing - particularly "bug can be > > confirmed" ... "cannot provide". These two things contradict themselves > > in my mind. Perhaps the question should really be "bug can not be > > confirmed"? > > > > > > Good point, Brian. I converted all the comments into an FAQ style; I > think it's a bit more professional and clearer. Outstanding - thanks for doing that! -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Fri Aug 27 18:08:11 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 27 Aug 2010 18:08:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_cyan-spam?= Message-ID: <20100827180811.9977.29262@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by cyan-spam: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=50&rev2=51 The comment on the change is: converted "Comments" section into FAQs ------------------------------------------------------------------------------ * It is most often used for bugs with a release target that will not be fixed in that particular release but may be fixed later * It may also be used for feature requests that the developers do not want to implement - === Comments === + === Frequently Asked Questions === + + ''If you have a question, please feel free to add it here without an answer. A [[BugSquad]] member will add the answer later.'' + - * What should a triager do if the bug's reporter later says the bug no longer exists, and the related changelog is nowhere to be found? NanleyChery + * What is the appropriate status if the bug's reporter later says the bug no longer exists but the related changelog does not note a fix? - * I believe this is covered by the first case under Invalid. BrianMurray - * What about a case when we (and upstream developers) agree that a report is valid but there is no good solution? For example the current icon isn't a BIG complaint but no one can present a better alternative for it. KrzysztofKlimonda - * The bug should remain open (it is a real issue); we might have it as either WishList, or Triaged. [[Hggdh]] - * If I'm the bug reporter and I provide more information, should I change the status back to "new" or let it stay at Incomplete? -- [[Diwic]] - * you should reset the status to New. [[Hggdh]] - * Converting Question to Bug, the reporter of Question, or confirming comments there, can be counted as another person(s), so the new bug can be right away set to Confirmed in such case? - * Common sense should prevail. If ''more than one person'' can confirm the issue, then it should be Confirmed. [[Hggdh]] - * What if the bug can be confirmed even with the information provided by a bug reported during bug reporting and now the bug reporter and any other affected person cannot provide/is not available for providing further information, due to any reason? - * In that case you should mark the bug as Invalid, with a comment to the bug reporter that he could reopen the bug by resetting the bug status to 'New' again ,any time when he can provide us with further information. [[simar]] + * See the first point under "Invalid", the bug does not have sufficient information. + * What should a triager do if there is consensus ''among users and developers'' that an issue is valid but there is no good solution? + * Keep the bug open with a status of "Wishlist" or "Traiged", depending on the severity. + * Should the bug reporter reset the bug status to "New" if providing more information to an "Incomplete" bug? + * Yes. + * When converting a question to a bug, can the bug status immediately be set to "Confirmed" if comments in the question indicate that multiple users experience the bug? + * Make a judgment call: as long as ''more than one person'' experiences the bug, the proper status is "Confirmed". + * What should a triager do if a bug needs more information but the original reporter is not available to provide it? + * Mark the bug as Invalid with a comment that the reporter could provide the information and reopen the bug by resetting its status to 'New'. + ---- CategoryBugSquad From noreply at ubuntu.com Fri Aug 27 18:46:41 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 27 Aug 2010 18:46:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_brian-murray?= Message-ID: <20100827184641.18090.82128@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=51&rev2=52 ------------------------------------------------------------------------------ * Yes. * When converting a question to a bug, can the bug status immediately be set to "Confirmed" if comments in the question indicate that multiple users experience the bug? * Make a judgment call: as long as ''more than one person'' experiences the bug, the proper status is "Confirmed". - * What should a triager do if a bug needs more information but the original reporter is not available to provide it? + * What should a triager do if a bug needs more information, including steps to reproduce, but the original reporter is not available to provide it? - * Mark the bug as Invalid with a comment that the reporter could provide the information and reopen the bug by resetting its status to 'New'. + * Mark the bug as Invalid with a comment that the reporter should provide the information and reopen the bug by resetting its status to 'New'. ---- From bilalakhtar at ubuntu.com Mon Aug 30 07:30:28 2010 From: bilalakhtar at ubuntu.com (Bilal Akhtar) Date: Mon, 30 Aug 2010 10:30:28 +0300 Subject: launchpad +filebug redirect In-Reply-To: <4C77F7CE.2030404@gmail.com> References: <4C77F7CE.2030404@gmail.com> Message-ID: <1283153428.2544.4.camel@bilal-laptop> I completely agree with this. It is irritating for devs as well. If one needs to file a needs-packaging bug in Ubuntu, he/she will need to add no-redirect to the query string to fine a generic bug in Ubuntu. Bilal Akhtar. On Fri, 2010-08-27 at 13:37 -0400, David Tombs wrote: > Hi all, > > I was just looking at the ReportingBugs wiki page[1] and thought that > the current intro (between the two "Reporting Bugs" headers) is a little > awkward. It's obviously there because the +filebug launchpad page[2] > simply redirects users to the wiki page, and that might confuse users. > > Since streamlining the bug reporting process is definitely in our favor, > I suggest a clearer and less awkward process: what if the +filebug page > presented a message to the user that it is no longer the way to report > bugs and then just /linked/ to the wiki page for further information? > > This way we can get rid of the introduction on ReportingBugs, reducing > the text users have to read and possibly some confusion for first-time > reporters. > > Thoughts? > > Thanks, > David > > [1] https://help.ubuntu.com/community/ReportingBugs/ > [2] https://bugs.launchpad.net/ubuntu/+filebug/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From noreply at ubuntu.com Mon Aug 30 10:55:02 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 30 Aug 2010 10:55:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22PulseAudio/Log=22_by_diwic?= Message-ID: <20100830105502.28730.60437@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by diwic: http://wiki.ubuntu.com/PulseAudio/Log?action=diff&rev1=7&rev2=8 The comment on the change is: Added timestamps to PA log ------------------------------------------------------------------------------ LANG=C pulseaudio -vvvv > ~/pulseverbose.log 2>&1 }}} + * Open a second terminal and enter this command: + {{{ + pacmd set-log-time 1 + }}} + * Do what you need to reproduce the bug. * Switch back to the terminal and press Ctrl-C to stop !PulseAudio. * Open your Launchpad bug and attach the file ~/pulseverbose.log (in your home directory) to that message. From bilalakhtar at ubuntu.com Mon Aug 30 07:24:13 2010 From: bilalakhtar at ubuntu.com (Bilal Akhtar) Date: Mon, 30 Aug 2010 10:24:13 +0300 Subject: launchpad +filebug redirect In-Reply-To: <4C77F7CE.2030404@gmail.com> References: <4C77F7CE.2030404@gmail.com> Message-ID: <1283153053.2544.3.camel@bilal-laptop> I completely agree with this. It is irritating for devs as well. If one needs to file a needs-packaging bug in Ubuntu, he/she will need to add no-redirect to the query string to fine a generic bug in Ubuntu. Bilal Akhtar. On Fri, 2010-08-27 at 13:37 -0400, David Tombs wrote: > Hi all, > > I was just looking at the ReportingBugs wiki page[1] and thought that > the current intro (between the two "Reporting Bugs" headers) is a little > awkward. It's obviously there because the +filebug launchpad page[2] > simply redirects users to the wiki page, and that might confuse users. > > Since streamlining the bug reporting process is definitely in our favor, > I suggest a clearer and less awkward process: what if the +filebug page > presented a message to the user that it is no longer the way to report > bugs and then just /linked/ to the wiki page for further information? > > This way we can get rid of the introduction on ReportingBugs, reducing > the text users have to read and possibly some confusion for first-time > reporters. > > Thoughts? > > Thanks, > David > > [1] https://help.ubuntu.com/community/ReportingBugs/ > [2] https://bugs.launchpad.net/ubuntu/+filebug/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From yofel at gmx.net Mon Aug 30 18:14:35 2010 From: yofel at gmx.net (Philip Muskovac) Date: Mon, 30 Aug 2010 20:14:35 +0200 Subject: launchpad +filebug redirect In-Reply-To: <1283153428.2544.4.camel@bilal-laptop> References: <4C77F7CE.2030404@gmail.com> <1283153428.2544.4.camel@bilal-laptop> Message-ID: <4C7BF50B.4010605@gmx.net> On 08/30/2010 09:30 AM, Bilal Akhtar wrote: > I completely agree with this. It is irritating for devs as well. If one > needs to file a needs-packaging bug in Ubuntu, he/she will need to add > no-redirect to the query string to fine a generic bug in Ubuntu. > > Bilal Akhtar. Sorry for my irritation, but how are devs affected by this? The redirect is disabled for members of the Bug Control team and upwards. Upstream developers can get Bug Control membership pretty easy afaik. > > On Fri, 2010-08-27 at 13:37 -0400, David Tombs wrote: >> Hi all, >> >> I was just looking at the ReportingBugs wiki page[1] and thought that >> the current intro (between the two "Reporting Bugs" headers) is a little >> awkward. It's obviously there because the +filebug launchpad page[2] >> simply redirects users to the wiki page, and that might confuse users. >> >> Since streamlining the bug reporting process is definitely in our favor, >> I suggest a clearer and less awkward process: what if the +filebug page >> presented a message to the user that it is no longer the way to report >> bugs and then just /linked/ to the wiki page for further information? >> >> This way we can get rid of the introduction on ReportingBugs, reducing >> the text users have to read and possibly some confusion for first-time >> reporters. >> >> Thoughts? >> >> Thanks, >> David >> >> [1] https://help.ubuntu.com/community/ReportingBugs/ >> [2] https://bugs.launchpad.net/ubuntu/+filebug/ >> > > While I'm personally not too happy about the current state either I have seen a lot less useless reports since we enabled the redirect so I really want it to stay like this. As I understand you, you want to post a message linking to the help page on the +file-bug page, but that's already the case. Below the description box it says: ------------------------------------------------- Ubuntu bug reporting guidelines: Please include, if possible: The source package you found the bug in, for help see https://wiki.ubuntu.com/Bugs/FindRightPackage . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu. 2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic. 3) What you expected to happen 4) What happened instead A lot of this information is gathered when you use apport to report the bug. See https://help.ubuntu.com/community/ReportingBugs for complete details. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures. Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ------------------------------------------------- and as users happily ignored that we implemented the redirect in the first place. Or do you mean something else? Yofel From bilalakhtar at ubuntu.com Mon Aug 30 20:07:38 2010 From: bilalakhtar at ubuntu.com (Bilal Akhtar) Date: Mon, 30 Aug 2010 23:07:38 +0300 Subject: launchpad +filebug redirect In-Reply-To: <4C7BF50B.4010605@gmx.net> References: <4C77F7CE.2030404@gmail.com> <1283153428.2544.4.camel@bilal-laptop> <4C7BF50B.4010605@gmx.net> Message-ID: <1283198858.3088.2.camel@bilal-laptop> On Mon, 2010-08-30 at 20:14 +0200, Philip Muskovac wrote: > Sorry for my irritation, but how are devs affected by this? The redirect > is disabled for members of the Bug Control team and upwards. Upstream > developers can get Bug Control membership pretty easy afaik. > Well, I am a member of BC, but this used to affect me before I was a BC member. And, not every Upstream dev is a BC member. I am sorry if my message wasn't clear, but I just wanted to point out another case in which the redirection is irritating. Bilal Akhtar. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From kamusin at gmail.com Tue Aug 31 20:25:39 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 31 Aug 2010 16:25:39 -0400 Subject: Announcing the Next Ubuntu Bug Day! - September 2nd 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Empathy! * 44 New bugs need a hug * 109 Incompletes bugs need a status check * 23 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 2nd September 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100902 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile.