From gigglechildren at gmail.com Sat Jun 2 22:41:03 2012 From: gigglechildren at gmail.com (Evan Peck) Date: Sat, 02 Jun 2012 15:41:03 -0700 Subject: Hug Day! Me, oh my! Message-ID: <4FCA967F.8000501@gmail.com> Ubuntu Software Centre Hug Day Idea Proposal Hi, I am Evan Peck from America and I enjoy triaging bugs and drinking coffee. I also like to drink coffee. I would like to organize a HugDay for Ubuntu Software Centre on August 25th, 2011. Are there any other plans for this day? Evan Peck (brokenfingers). In accordance with https://wiki.ubuntu.com/UbuntuBugDay/Organizing Hip hip hooray! From trekcaptainusa.tw at gmail.com Sun Jun 3 13:52:05 2012 From: trekcaptainusa.tw at gmail.com (Thomas Ward) Date: Sun, 3 Jun 2012 09:52:05 -0400 Subject: Hug Day! Me, oh my! In-Reply-To: <4FCA967F.8000501@gmail.com> References: <4FCA967F.8000501@gmail.com> Message-ID: Doesn't look like anything else is on that day. At first glance I see a lot of Natty-filed bugs, so there may be a bunch of stuff that just gets closed or won't fix'd. There are a lot of python error bugs there too, most of which are unconfirmed. One of the goals of the HugDay would be to confirm those, but as some are semi-old, I am not sure of the feasibility of that. There are also a lot of wishlist bugs. Correct me if I am wrong, but wouldn't software-center upstream need to handle those, or decide whether to implement them? We may want to coordinate with upstream as well, since some of these bugs are wishlist-type, and those probably need upstream handling. ------ Thomas LPID: trekcaptainusa-tw Ubuntu BugSquad On Sat, Jun 2, 2012 at 6:41 PM, Evan Peck wrote: > Ubuntu Software Centre Hug Day Idea Proposal > > Hi, I am Evan Peck from America and I enjoy triaging bugs and drinking > coffee. I also like to drink coffee. > > I would like to organize a HugDay for Ubuntu Software Centre on August 25th, > 2011. Are there any other plans for this day? > > Evan Peck (brokenfingers). > > In accordance with https://wiki.ubuntu.com/UbuntuBugDay/Organizing Hip hip > hooray! > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From webmaster at ubuntu.com Sat Jun 2 02:15:58 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 02 Jun 2012 02:15:58 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_brokenfingers?= Message-ID: <20120602021558.18760.98764@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by brokenfingers: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=175&rev2=176 Comment: Changed def. for security threat. At then bottom of the page, there are some extra options you can use to make your bug report more complete: - * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to crack your system. (TODO: better wording?) + * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to compromise your security or safety, as well as cause issues such as identity theft, "hi-jacking", or a corrupt installation/partition. * '''Tags:''' You can add here [[http://wiki.ubuntu.com/Bugs/Tags|tags]] that pertain to your bug report. The predefined values should be left alone. * '''Include an attachment:''' Using this option, you can add supporting attachments to explain or help others reproduce the bug. This might include a screenshot, a video capture of the problem or a sample document that triggers the fault. Additional attachments, if necessary, can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. From gigglechildren at gmail.com Mon Jun 4 18:56:59 2012 From: gigglechildren at gmail.com (Evan Peck) Date: Mon, 4 Jun 2012 11:56:59 -0700 Subject: Hug Day! Me, oh my! Message-ID: Yes- I see what you mean - I was more thinking about how software-center is laggy, it sometimes has odd behaviours, and is resource-hungry. Evan Peck On Mon, Jun 4, 2012 at 5:00 AM, wrote: > Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > > Today's Topics: > > 1. Re: Hug Day! Me, oh my! (Thomas Ward) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 3 Jun 2012 09:52:05 -0400 > From: Thomas Ward > To: ubuntu-bugsquad at lists.ubuntu.com > Subject: Re: Hug Day! Me, oh my! > Message-ID: > > > Content-Type: text/plain; charset=UTF-8 > > Doesn't look like anything else is on that day. At first glance I see > a lot of Natty-filed bugs, so there may be a bunch of stuff that just > gets closed or won't fix'd. > > There are a lot of python error bugs there too, most of which are > unconfirmed. One of the goals of the HugDay would be to confirm > those, but as some are semi-old, I am not sure of the feasibility of > that. > > There are also a lot of wishlist bugs. Correct me if I am wrong, but > wouldn't software-center upstream need to handle those, or decide > whether to implement them? > > We may want to coordinate with upstream as well, since some of these > bugs are wishlist-type, and those probably need upstream handling. > > ------ > Thomas > LPID: trekcaptainusa-tw > Ubuntu BugSquad > > On Sat, Jun 2, 2012 at 6:41 PM, Evan Peck > wrote: > > Ubuntu Software Centre Hug Day Idea Proposal > > > > Hi, I am Evan Peck from America and I enjoy triaging bugs and drinking > > coffee. I also like to drink coffee. > > > > I would like to organize a HugDay for Ubuntu Software Centre on August > 25th, > > 2011. Are there any other plans for this day? > > > > Evan Peck (brokenfingers). > > > > In accordance with https://wiki.ubuntu.com/UbuntuBugDay/Organizing Hip > hip > > hooray! > > > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > ------------------------------ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > End of Ubuntu-bugsquad Digest, Vol 72, Issue 3 > ********************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at ubuntu.com Mon Jun 4 23:53:50 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Mon, 04 Jun 2012 23:53:50 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_brian-murray?= Message-ID: <20120604235350.31581.62879@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by brian-murray: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=176&rev2=177 At then bottom of the page, there are some extra options you can use to make your bug report more complete: - * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to compromise your security or safety, as well as cause issues such as identity theft, "hi-jacking", or a corrupt installation/partition. + * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to compromise your security or safety, as well as cause issues such as identity theft or "hi-jacking". * '''Tags:''' You can add here [[http://wiki.ubuntu.com/Bugs/Tags|tags]] that pertain to your bug report. The predefined values should be left alone. * '''Include an attachment:''' Using this option, you can add supporting attachments to explain or help others reproduce the bug. This might include a screenshot, a video capture of the problem or a sample document that triggers the fault. Additional attachments, if necessary, can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. From noreply at ubuntu.com Tue Jun 5 22:41:56 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 05 Jun 2012 22:41:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_penalvch?= Message-ID: <20120605224156.19347.45380@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Tags" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=190&rev2=191 Comment: Added bisect tags as per https://lists.launchpad.net/ubuntu-bugcontrol/msg03737.html || [[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 || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-bisect|`needs-bisect`]] || This is for when a bisect is requested or required to fix the bug. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-bisect|`performing-bisect`]] || The reporter, developer, or triager is in the process of performing a bisection. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=bisect-done|`bisect-done`]] || Add when a bisect has been completed and the offending commit(s) identified. || === SRU Specific === From noreply at ubuntu.com Thu Jun 7 00:27:53 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 07 Jun 2012 00:27:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_brok?= =?utf-8?q?enfingers?= Message-ID: <20120607002753.30914.51849@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by brokenfingers: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=119&rev2=120 1. Launch the application. 2. Open a Terminal (GNOME: Applications -> Accessories -> Terminal | KDE: K -> Applications -> System -> Terminal). 3. In the terminal, type `xprop WM_CLASS`. Your mouse pointer should now turn to crosshairs. + {{attachment:xprop1.png}} 4. Click anywhere in the application's window. - 5. The terminal will now list a line like `WM_CLASS(STRING) = "terminator", "Terminator"`. Write down the first value ("terminator"). + 5. The terminal will now list a line like `WM_CLASS(STRING) = "deja-dup", "Deja-dup"`. Write down the first value ("deja-dup"). + {{attachment:xprop2.png}} - 6. In the terminal, type `locate -b "\[executable name]"`. (In this case, `locate -b "\terminator"`.) The backslash (\) is important! + 6. In the terminal, type `locate -b "\[executable name]"`. (In this case, `locate -b "\deja-dup"`.) The backslash (\) is important! 7. Write down the line printed on the terminal. (If there are multiple lines, use the first one.) This is the full executable path. ==== Finding the Package Name ==== From noreply at ubuntu.com Fri Jun 8 11:24:08 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 08 Jun 2012 11:24:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?= =?utf-8?q?lson?= Message-ID: <20120608112408.17000.57024@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs" page has been changed by chrisccoulson: http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=77&rev2=78 You may find that you need to use the Terminal for some of these commands. If you are not sure how to use a terminal, please see the [[https://help.ubuntu.com/community/UsingTheTerminal|Terminal Guide]] for a basic introduction. - We get a lot of Firefox bug reports from Ubuntu users, and many of those don't contain enough useful information to sufficiently describe the problem or determine the cause of the problem. Please understand that we don't have the manpower available to spend time on every single bug report to continually ask reporters for information that ''could'' be provided up-front. To increase the chances that your bug report attracts the attention of a developer, you '''must''' follow these guidelines. + We get a lot of Firefox bug reports from Ubuntu users and the majority of those don't contain sufficient useful information to progress them further, or sometimes even understand what the actual problem is. Please understand that we don't have the manpower available to spend time on every single bug report to continually ask reporters for information that ''could'' be provided up-front. To increase the chances that your bug report attracts the attention of a developer, you '''must''' follow these guidelines. A developer will ask you for the required information that you didn't provide, so following these guidelines will save time for the person who looks at your bug report. Here are some instructions you should follow before filing a bug report: @@ -190, +190 @@ == Excessive memory usage == - If you are reporting a bug about excessive memory usage, you '''must''' copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport. + If you are reporting a bug about excessive memory usage, you '''must''' copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport. Please don't report bugs about memory usage without this information, as it will be the first thing a developer asks for anyway. In the future, we hope to automate this step. + + You can access about:memory in both Firefox and Thunderbird from Help -> Troubleshooting Information (or you could just type it in to the address bar in Firefox if you prefer). + + When reporting your bug, please also describe the scenario which triggers the problem. Does it happen on a particular site? If so, please provide a URL. Please also try disabling all of your addons (you will be asked to do this anyway, so you can save other peoples time by doing this when reporting your bug). Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] and [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]] From noreply at ubuntu.com Wed Jun 13 13:13:58 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 13 Jun 2012 13:13:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?= =?utf-8?q?lson?= Message-ID: <20120613131358.25609.61225@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs" page has been changed by chrisccoulson: http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=78&rev2=79 This could be a problem with the server, or it could be that somebody is impersonating the server. It is generally '''not a bug with Firefox''' - If a site provides a certificate signed by an intermediate CA (one which is not in the root store, but with a trust chain to an existing root), the server must provide the intermediate certificates. Failure to do this will result in this error. + If a site provides a certificate signed by an intermediate CA (one which is not in the root store, but with a trust chain to an existing root), the server must provide the intermediate certificates. Failure to do this will result in this error if the intermediate certificates do not already exist in your certificate store. ==== For certificates signed by RapidSSL (Geotrust) ==== @@ -264, +264 @@ In some cases when experiencing "unknown issuer" errors when visiting certain sites, it may be tempting to open a bug report to request that the issuer CA is added to the root store shipped with Firefox. Doing this would defeat the whole trust system. There is a '''well defined''' process for CA's to request that their certificate(s) be added and be shipped with Firefox. Details of this can be found at [[https://wiki.mozilla.org/CA:How_to_apply|https://wiki.mozilla.org/CA:How_to_apply]] - '''We will not bypass this process under any circumstances''', so please make these types of requests. Requests of this type '''will be rejected'''. + We will not bypass this process under any circumstances, so please don't make these types of requests. Requests of this type '''will be rejected'''. === Problems launching external applications === From costamagnagianfranco at yahoo.it Thu Jun 14 10:10:50 2012 From: costamagnagianfranco at yahoo.it (Gianfranco Costamagna) Date: Thu, 14 Jun 2012 11:10:50 +0100 (BST) Subject: No subject Message-ID: <1339668650.33903.YahooMailNeo@web133001.mail.ir2.yahoo.com> http://www.casanosambaqui.com.br/wp-content/themes/sambaqui/googlemail.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From thinkndev at gmail.com Tue Jun 19 02:09:42 2012 From: thinkndev at gmail.com (John Kim) Date: Mon, 18 Jun 2012 19:09:42 -0700 Subject: On getting started w/5-a-day Message-ID: Hello bug squad, I'm John, and I want to participate in Ubuntu development. Reading through the wikia, I felt encouraged to try out on the 5-a-day program. I've read what 5-a-day was about very carefully, that newcomers should confirm new bugs or link them to bugs from upstream trackers if possible. Also, is it recommended for the prospective developer to get the latest release of the next version for finding bugs? I'm thinking that the stable release isn't the best grounds for it. For instance, I stumbled on this low importance bug. https://bugs.launchpad.net/unity/+bug/882470 It affects oneiric, and I don't know if it has been resolved yet. In precise, is it possible to replicate the bug? To confirm the bug, must I replicate it first and see if the description is suffice for replication? And how can I know if there is a bug similar to this one, so that I may link it to the upstream? Thanks for the help. John -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.fischer at canonical.com Tue Jun 19 02:46:16 2012 From: matthew.fischer at canonical.com (Matt Fischer) Date: Mon, 18 Jun 2012 20:46:16 -0600 Subject: On getting started w/5-a-day In-Reply-To: References: Message-ID: <4FDFE7F8.5020700@canonical.com> On 06/18/2012 08:09 PM, John Kim wrote: > Hello bug squad, > > I'm John, and I want to participate in Ubuntu development. Reading > through the wikia, I felt encouraged to try out on the 5-a-day > program. I've read what 5-a-day was about very carefully, that > newcomers should confirm new bugs or link them to bugs from upstream > trackers if possible. > > Also, is it recommended for the prospective developer to get the > latest release of the next version for finding bugs? I'm thinking > that the stable release isn't the best grounds for it. > > For instance, I stumbled on this low importance bug. > https://bugs.launchpad.net/unity/+bug/882470 > > It affects oneiric, and I don't know if it has been resolved yet. In > precise, is it possible to replicate the bug? > > To confirm the bug, must I replicate it first and see if the > description is suffice for replication? And how can I know if there > is a bug similar to this one, so that I may link it to the upstream? > > Thanks for the help. > > John > > > Hi John, Thanks for volunteering to help out. I think that doing 5-a-day is an excellent way to learn your way around Launchpad and Ubuntu in general. Confirming and linking bugs upstream is important. You can also work on finding the right packages for bugs ( https://wiki.ubuntu.com/Bugs/FindRightPackage) or work with submitters to get more info on bugs where it is required. In the specific case you cited, if the bug really is in Unity, it's already filed "upstream" as Unity is an Ubuntu-specific project tracked in Launchpad. (See how it's filed against Unity and Unity-Ubuntu)? The comment in the bug is interesting, can you reproduce it with another application? Does it still occur in Precise or Quantal? I'd suggest you try those items and post your results as a comment, along with the versions of Unity you're trying. -------------- next part -------------- An HTML attachment was scrubbed... URL: From afrowildo at gmail.com Tue Jun 19 12:48:49 2012 From: afrowildo at gmail.com (Chris Wilson) Date: Tue, 19 Jun 2012 13:48:49 +0100 Subject: On getting started w/5-a-day In-Reply-To: <4FDFE7F8.5020700@canonical.com> References: <4FDFE7F8.5020700@canonical.com> Message-ID: Another good way to get started is to get involved in the Hundred Papercuts project , since this deals with small and trivial bugs found through the system. This way you will get experience with the different packages shipped on Ubuntu as well as the various upstream sources without getting in too far over your head with complex technical issues. Chris On 19 June 2012 03:46, Matt Fischer wrote: > On 06/18/2012 08:09 PM, John Kim wrote: > > Hello bug squad, > > I'm John, and I want to participate in Ubuntu development. Reading > through the wikia, I felt encouraged to try out on the 5-a-day program. > I've read what 5-a-day was about very carefully, that newcomers should > confirm new bugs or link them to bugs from upstream trackers if possible. > > Also, is it recommended for the prospective developer to get the latest > release of the next version for finding bugs? I'm thinking that the stable > release isn't the best grounds for it. > > For instance, I stumbled on this low importance bug. > https://bugs.launchpad.net/unity/+bug/882470 > > It affects oneiric, and I don't know if it has been resolved yet. In > precise, is it possible to replicate the bug? > > To confirm the bug, must I replicate it first and see if the description > is suffice for replication? And how can I know if there is a bug similar > to this one, so that I may link it to the upstream? > > Thanks for the help. > > John > > > > > Hi John, > > Thanks for volunteering to help out. I think that doing 5-a-day is an > excellent way to learn your way around Launchpad and Ubuntu in general. > Confirming and linking bugs upstream is important. You can also work on > finding the right packages for bugs ( > https://wiki.ubuntu.com/Bugs/FindRightPackage) or work with submitters to > get more info on bugs where it is required. > > In the specific case you cited, if the bug really is in Unity, it's > already filed "upstream" as Unity is an Ubuntu-specific project tracked in > Launchpad. (See how it's filed against Unity and Unity-Ubuntu)? The > comment in the bug is interesting, can you reproduce it with another > application? Does it still occur in Precise or Quantal? I'd suggest you > try those items and post your results as a comment, along with the versions > of Unity you're trying. > > > > -- > 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 Wed Jun 20 09:47:27 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 20 Jun 2012 09:47:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_mpt?= Message-ID: <20120620094727.12050.41013@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by mpt: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=351&rev2=352 Comment: shortens awkward "some of the sentences" This response is appropriate when a bug is not reported in English or some error messages are not in English. + || Some of this bug report is not in English. Please translate it into English to make it more understandable to triagers. Thanks!|| - || We noticed that some of the sentences in this bug report are not in English. If they were translated in English they would be more understandable to triagers. Could you please translate them?|| - == Suspected bad ISO download == From melchiaros at aol.com Wed Jun 20 17:55:58 2012 From: melchiaros at aol.com (melchiaros) Date: Wed, 20 Jun 2012 19:55:58 +0200 Subject: Approval Message-ID: <4FE20EAE.2050206@aol.com> Hi, I am melchiaros and would like to join the BugSquad team. In the last years I was mainly on openSUSE(since version 11.0 I thing) and came to Ubuntu with the end of the last year. I actual help out with bugreporting from Ubuntu development version and answering question in launchpad ubuntu. I have thought that it is time to step a bit deeper. Greetings From melchiaros at aol.com Sat Jun 23 18:30:32 2012 From: melchiaros at aol.com (melchiaros) Date: Sat, 23 Jun 2012 20:30:32 +0200 Subject: karmic bug from this year Message-ID: <4FE60B48.4020806@aol.com> Hi, I have found https://bugs.launchpad.net/ubuntu/+source/bugzilla/+bug/916350 The reported uses a karmic system which is heavily outdated, but still reports in year 2012 from it. How to handle this? I would like to inform the reporter about the end of support for karmic and ask s/he to upgrade to a supported(newest at best) version of Ubuntu and doing a retesting with a bugzilla package that is there. Statements. From mitya57 at gmail.com Sat Jun 23 18:35:28 2012 From: mitya57 at gmail.com (Dmitry Shachnev) Date: Sat, 23 Jun 2012 22:35:28 +0400 Subject: karmic bug from this year In-Reply-To: <4FE60B48.4020806@aol.com> References: <4FE60B48.4020806@aol.com> Message-ID: I believe you should use https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL. -- Dmitry Shachnev On Sat, Jun 23, 2012 at 10:30 PM, melchiaros wrote: > Hi, > > I have found > > https://bugs.launchpad.net/ubuntu/+source/bugzilla/+bug/916350 > > The reported uses a karmic system which is heavily outdated, but still > reports in year 2012 from it. > > How to handle this? > > I would like to inform the reporter about the end of support for karmic > and ask s/he to upgrade to a supported(newest at best) version of Ubuntu > and doing a retesting with a bugzilla package that is there. > > Statements. > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From noreply at ubuntu.com Mon Jun 25 10:33:56 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 25 Jun 2012 10:33:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/Debugging/Backlight=22_by?= =?utf-8?q?_penalvch?= Message-ID: <20120625103356.25413.50453@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Kernel/Debugging/Backlight" page has been changed by penalvch: http://wiki.ubuntu.com/Kernel/Debugging/Backlight?action=diff&rev1=9&rev2=10 Comment: Added polished Report Minimum Requirements section as per https://lists.launchpad.net/ubuntu-bugcontrol/msg03742.html * Backlight control does not work and there are no entries in {{{/sys/class/backlight}}}. * Neither the ACPI backlight driver nor any vendor specific driver were able to find a valid interface. Either requires a new vendor driver (which is unlikely) or the ACPI BIOS is broken (see below). Updates to the ACPI BIOS are rare as well but in some cases it is possible to work with upstream to extend the Linux side to handle some of that brokenness. - = Filing Bugs = + = Reporting Backlight Bugs = + * Please do not report a backlight bug without first reading this wiki article and performing all the relevant actions mentioned here. Failure to do so will delay your bug getting addressed as quickly as possible. - When filing bugs about backlight control, try to classify the issue into the classes above. Also describe whether there was a previous kernel that worked, or whether this was never the case. Also be very specific in the bug title about the laptop vendor and model. Backlight control is very specific to hardware and a bug titled "''backlight control does not work''" just causes other people to use that bug even if they have a completely different laptop. It is much simpler to look into issues separately than to mix things. + * When filing bugs about backlight control, please classify the issue into one of the classes above. Also describe whether there was a previous kernel that worked, or whether this was never the case. Also be very specific in the bug title about the laptop vendor and model. Backlight control is very specific to hardware and a bug titled "''backlight control does not work''" just causes other people to use that bug even if they have a completely different laptop. It is much simpler to look into issues separately than to mix things. - - Also, depending on the class of issues, provide additional information about the kernel interface. Does it exist, do any values change when writing into the control files? Is there any effect? + * Also, depending on the class of issues, provide additional information about the kernel interface. Does it exist, do any values change when writing into the control files? Is there any effect? - - If the kernel interface does not work, add the dump of the ACPI BIOS as described below. + * If the kernel interface does not work, add the dump of the ACPI BIOS as described below. + + == Report Minimum Requirements == + + * Please file backlight bugs by executing at the Terminal: <
> {{{ubuntu-bug linux}}} <
> <
> If it turns out to be a non-linux package issue, it can be changed to the appropriate package. + * Install the prerequisites by executing at the Terminal: <
> {{{sudo apt-get install -y acpidump fwts dmidecode}}} + * Execute each of the following via a terminal, and post the results to your report: <
> {{{grep -r . /proc/acpi/video}}} <
> {{{ls /sys/class/backlight}}} <
> {{{sudo acpidump -o acpidump.txt}}} <
> {{{acpixtract acpidump.txt}}} <
> {{{iasl -d DSDT.dat}}} <
> {{{sudo fwts > fwts}}} <
> {{{sudo fwts method > fwts method}}} <
> {{{dmesg | grep 'ACPI: Video'}}} <
> {{{dmidecode > dmidecode.log}}} <
> {{{cat /proc/version}}} + * Add kernel parameter atkbd.softraw=0 to /boot/grub/menu.lst . Then, switch to any console, e.g. Ctrl+Alt+F1, login by root account and execute: {{{showkey -s}}} <
> <
> Then, press Fn+Left and Fn+Right key to check the code that shows up on screen. Post the results to the report. For example: <
> <
> Fn+Left: <
> 0xe0 0x4c 0xe0 0xcc <
> <
> Fn+Right: <
> 0xe0 0x54 0xe0 0xd4 + + === Thinkpads === + + * Add kernel parameters thinkpad-acpi.brightness_enable=1 acpi_backlight=vendor to /boot/grub/menu.lst . Execute: <
> {{{sudo update grub}}} <
> <
> Restart, and comment on if brightness may be changed via hotkeys and/or brightness applet. + ** As well, execute the following and post results to your report: <
> {{{lsmod | grep thinkpad_acpi}}} + + === Intel === + + * If using an intel board, add the kernel parameter acpi_backlight=vendor /boot/grub/menu.lst . Execute: <
> {{{sudo update grub}}} <
> <
> Restart, and comment on if brightness may be changed via hotkeys and/or brightness applet. Then execute the following and post results to your report: <
> {{{ls -la /sys/class/backlight/intel_backlight/}}} + + * Comment on how the brightness changes if one executes: <
> {{{sudo su}}} <
> {{{sudo echo 8 > /sys/class/backlight/intel_backlight/brightness}}} = Diagnostic Techniques = From delstrick at frontier.com Mon Jun 25 22:42:36 2012 From: delstrick at frontier.com (delstrick) Date: Mon, 25 Jun 2012 18:42:36 -0400 Subject: Kpat bug Message-ID: <4FE8E95C.5000907@frontier.com> Upgrading to 12.04 left me with a bug in Kpat. With sound enabled there is an @ 4sec. delay before cards will drop. Disable sound and the cards will drop normally. From noreply at ubuntu.com Thu Jun 28 15:04:29 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 28 Jun 2012 15:04:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20120628150429.30282.72123@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=63&rev2=64 Starting with Intrepid the '''cupsys''' package has been renamed to '''cups'''. Subsequently, bugs about Intrepid (8.10) and newer releases should be assigned to the '''cups''' package and bug reports about previous releases should be assigned to '''cupsys'''. = Printer detection = + + NOTE: If you have a USB -> Parallel adapter, proceed as for a USB printer. == USB printer == @@ -35, +37 @@ 2. Open a terminal/console and check if the lp, ppdev, and parport_pc kernel modules are loaded: <
> {{{$ lsmod | grep lp}}} <
> {{{$ lsmod | grep ppdev}}} <
> {{{$ lsmod | grep parport_pc}}} 3. Check if the kernel detected the parallel port during bootup: <
> {{{$ dmesg | grep par }}} 4. Check if the device files of the parallel port(s) are created and have the correct permissions and ownerships: <
> {{{$ ls -l /dev/lp* /dev/parport* }}} - 5. Check if the printer auto-detection result appears in the kernel's virtual file system: <
{{{$ ls -l /proc/sys/dev/parport/parport*/autoprobe* }}} <
> {{{$ sudo cat /proc/sys/dev/parport/parport*/autoprobe* }}} + 5. Check if the printer auto-detection result appears in the kernel's virtual file system: <
> {{{$ ls -l /proc/sys/dev/parport/parport*/autoprobe* }}} <
> {{{$ sudo cat /proc/sys/dev/parport/parport*/autoprobe* }}} 6. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 7. Run the parallel port CUPS backend separately, once with standard user privileges and once as root: <
> {{{$ /usr/lib/cups/backend/parallel }}} <
> {{{$ sudo /usr/lib/cups/backend/parallel }}} 8. Attach the output of the above commands to the bug report. From noreply at ubuntu.com Thu Jun 28 15:54:33 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 28 Jun 2012 15:54:33 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20120628155433.3329.27887@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=64&rev2=65 6. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 7. Run the parallel port CUPS backend separately, once with standard user privileges and once as root: <
> {{{$ /usr/lib/cups/backend/parallel }}} <
> {{{$ sudo /usr/lib/cups/backend/parallel }}} 8. Attach the output of the above commands to the bug report. + + Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), HPLIP (package "hplip"), and several third-party printer drivers. + + == Network printer == + + 1. Make sure the printer is turned on and connected to your network. In the case of a WLAN (wireless) printer the printer needs to be configured to use your wireless network. + + 2. Check the printer's configuration by printing a configuration page via the printer's front panel menus. This gives information about the IP address of the printer and about the protocols it supports (JetDirect/AppSocket, LPD, IPP, SMB/Windows, ...). + + 3. You can also find the printer's IP address via the configuration web interface of your router. Many routers you can configure that the printer always gets the same IP and you can also assign a host name. + + 4. To change the printer's configuration either use the printer's front panel menus or the printer's web configuration interface. To access this web interface, enter the IP address of the printer into the address or URL line of a web browser. + + 5. If your printer is supposed to connect via WLAN and it does not get an IP address, make sure that your WLAN is turned on and that the correct network name (SSID) and password are set by the front panel menus of the printer. If the printer has no front panel menus, you have to connct it with an ethernet cable first and configure the WLAN access through the web interface. On some HP printers there is WLAN connection but no ethernet connection. These you have to connect via USB and then use the hp-wificonfig tool from the hplip-gui package to configure them. + + 6. Set up the printer via system-config-printer ("Add" button). Wait around 15 seconds for the network scan (spinning icon must disappear). Usually you should select the default connection type as system-config-printer tries to find the best possibility. Generally use HP printers through the HPLIP connection, other printers preferably with DNS-SD connections (will continue to work whn the router changes the IP of the printer) and from the protocols use preferably AppSocket/jetDirect. The implementation of IPP in the printer's firmware has often bugs. Make sure the desired protocols and DNS-SD/mDNS/BonJour support are active in the printer's hardware configuration. + + 7. Open a terminal/console and run the commands: <
> {{{$ ping }}} <
> {{{$ nmap }}} <
> Replace "" by the printer's IP address. The first command checks whether you can access the printer through the network, the second shows which port numbers are used by the printer and through this which protocols are active (80: Has web interface, 139: SMB, 443: encrypted IPP or encrypted web interface, 515: LPD, 631: IPP, 9100: JetDirect/AppSocket). Install the "nmap" package if needed. + + 8. Run the commands: <
> {{{$ /usr/lib/cups/backend/snmp}}} <
> {{{$ sudo /usr/lib/cups/backend/dnssd}}} <
> The output shows whether the printers get found by CUPS or system-config-printer and with which device URIs and protocols. + + 9. Run the command <
> {{{$ /usr/lib/cups/backend/snmp }}} <
> if a printer does not get found by the simple "/usr/lib/cups/backend/snmp" call. + + 10. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} + + 11. Attach the output of the above commands to the bug report. Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), HPLIP (package "hplip"), and several third-party printer drivers. From noreply at ubuntu.com Fri Jun 29 16:19:11 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 29 Jun 2012 16:19:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20120629161911.5244.95232@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=66&rev2=67 10. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} + 11. Run the commands: <
> {{{$ avahi-browse -a -v -t -r}}} <
> {{{$ avahi-browse -a -v -c -r}}} <
> These commands show whether your printer is visible via DNS-SD/mDNS/BonJour. + + 12. Run <
> {{{$ ifconfig}}} <
> {{{$ route}}} <
> to check general network health. + - 11. Attach the output of the above commands to the bug report. + 13. Attach the output of the above commands to the bug report. Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), HPLIP (package "hplip"), and several third-party printer drivers. From webmaster at ubuntu.com Sat Jun 30 17:38:10 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 30 Jun 2012 17:38:10 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20120630173810.8681.71279@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=178&rev2=179 Comment: Add note, "As well, unless asked of you by..." -> == 3. Make sure the bug hasn't already been reported == If the problem is not in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you have further information about an already reported bug, add this information to the existing report, rather than opening a new one. - /!\ '''For sound, X drivers, and kernel bugs''': please open a '''new''' bug instead of commenting on a similar bug: chances are that your hardware does not match the existing bug's hardware, so the bug will not be addressed. + /!\ '''For sound, X drivers, and kernel bugs''': please open a '''new''' bug instead of commenting on a similar bug: chances are that your hardware does not match the existing bug's hardware, so the bug will not be addressed. As well, unless asked of you by a developer or experienced triager, please do not mark your bug a duplicate of another reporter's bug. [[#Top|Back to top]]