From brian at ubuntu.com Wed Sep 1 16:55:30 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 1 Sep 2010 09:55:30 -0700 Subject: launchpad +filebug redirect In-Reply-To: <1283153053.2544.3.camel@bilal-laptop> References: <4C77F7CE.2030404@gmail.com> <1283153053.2544.3.camel@bilal-laptop> Message-ID: <20100901165530.GD2636@murraytwins.com> On Mon, Aug 30, 2010 at 10:24:13AM +0300, 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. Personally, I'm not really certain that we need more needs-packaging bug reports. I'd guess that only a small portion of these bugs actually get resolved. -- 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 brian at ubuntu.com Wed Sep 1 17:01:40 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 1 Sep 2010 10:01:40 -0700 Subject: launchpad +filebug redirect In-Reply-To: <4C77F7CE.2030404@gmail.com> References: <4C77F7CE.2030404@gmail.com> Message-ID: <20100901170140.GE2636@murraytwins.com> On Fri, Aug 27, 2010 at 01:37:18PM -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. It really isn't that much text and I'd imagine that most people who go to that wiki page are actually being redirected there and not navigating to it directly. Additionally, I really don't think have a link to the no-redirect page in the second sentence is a good idea at all. It just makes it that much easier for people to not read the instructions regarding bug filing which then leads to low quality bug reports. > 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 would require some additional changes to Launchpad which can be a time consuming process. > 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. Has anybody heard of any complaints from people reading that page who were not redirected to it? -- 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 Wed Sep 1 17:13:01 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Wed, 1 Sep 2010 17:13:01 +0000 Subject: launchpad +filebug redirect In-Reply-To: <20100901170140.GE2636@murraytwins.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> Message-ID: On Wed, Sep 1, 2010 at 5:01 PM, Brian Murray wrote: > On Fri, Aug 27, 2010 at 01:37:18PM -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. > > It really isn't that much text and I'd imagine that most people who go > to that wiki page are actually being redirected there and not navigating > to it directly. > > Additionally, I really don't think have a link to the no-redirect page > in the second sentence is a good idea at all.  It just makes it that > much easier for people to not read the instructions regarding bug filing > which then leads to low quality bug reports. > >> 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 would require some additional changes to Launchpad which can be a > time consuming process. > >> 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. > > Has anybody heard of any complaints from people reading that page who > were not redirected to it? > > -- > Brian Murray > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkx+hvQACgkQDTAwc5ER+zVEpACdEKUpR8sFP0ysAJJfBgAJa+Ct > de8AoJnS0CdsbtEwD29Gsz8NKdB9jNa8 > =qAMU > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Maybe we could redirect them to another wiki page that explains that this is not the recommended way to report a bug, and then give them a link to file a bug anyway, and a link to ReportingBugs. Thank you, Mohamed Amine IL Idrissi From kklimonda at ubuntu.com Wed Sep 1 17:23:02 2010 From: kklimonda at ubuntu.com (Krzysztof Klimonda) Date: Wed, 01 Sep 2010 19:23:02 +0200 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> Message-ID: <1283361782.13048.25.camel@blue> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: > Maybe we could redirect them to another wiki page that explains that > this is not the recommended way to report a bug, and then give them a > link to file a bug anyway, and a link to ReportingBugs. But that would defeat the purpose of ReportingBug page as most visitors wouldn't ever read it but click the link to file a bug immediately. People who have problems are not interested in reading text, they just want to get their it fixed. Unfortunately this way they file low quality reports that make our work harder and most of us are not full-time bug triagers. We already get more reports we can really deal with (i.e. triage and fix in stable release) anyway. Cheers, KK -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From ilidrissiamine at gmail.com Wed Sep 1 17:36:46 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Wed, 1 Sep 2010 17:36:46 +0000 Subject: launchpad +filebug redirect In-Reply-To: <1283361782.13048.25.camel@blue> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> Message-ID: People who are not interested in reading text already click the link to file a bug immediately, since there is a link to it in ReportingBugs. Creating another wiki page would reduce the amount of text people would have to read, without removing the instructions for those who want to file good bug reports. Adding to this, we could tell them to run "ubuntu-bug " where is found according to Bugs/FindRightPackage, or to run "ubuntu-bug" if they are not sure, and follow the instructions. What would be ideal is that the user follow these steps: 1. Run "ubuntu-bug". 2. The current window opens, but with two more options: "Application problem" and "Specific package problem (advanced)". 2a. Choosing "Application problem" will open a window where you can drag-and-drop an application from the menu. 2b. Choosing "Specific package problem" will show a text entry where the user can type the package name. 3. If the user still can't know the specific problem, an alert shows and warns him that filing a bug without a package is not recommended, with a checkbox named: "This bug is about an application that needs packaging". Thank you, Mohamed Amine IL Idrissi On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: > On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: >> Maybe we could redirect them to another wiki page that explains that >> this is not the recommended way to report a bug, and then give them a >> link to file a bug anyway, and a link to ReportingBugs. > > But that would defeat the purpose of ReportingBug page as most visitors > wouldn't ever read it but click the link to file a bug immediately. > People who have problems are not interested in reading text, they just > want to get their it fixed. Unfortunately this way they file low quality > reports that make our work harder and most of us are not full-time bug > triagers. We already get more reports we can really deal with (i.e. > triage and fix in stable release) anyway. > > Cheers, >  KK > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From mathieu-tl at ubuntu.com Wed Sep 1 18:06:30 2010 From: mathieu-tl at ubuntu.com (Mathieu Trudel-Lapierre) Date: Wed, 1 Sep 2010 14:06:30 -0400 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> Message-ID: On Wed, Sep 1, 2010 at 1:36 PM, Mohammed Amine IL Idrissi wrote: [...] > What would be ideal is that the user follow these steps: > 1. Run "ubuntu-bug". > 2. The current window opens, but with two more options: "Application > problem" and "Specific package problem (advanced)". > 2a. Choosing "Application problem" will open a window where you can > drag-and-drop an application from the menu. > 2b. Choosing "Specific package problem" will show a text entry where > the user can type the package name. > 3. If the user still can't know the specific problem, an alert shows > and warns him that filing a bug without a package is not recommended, > with a checkbox named: "This bug is about an application that needs > packaging". > What you're describing sounds to me like adding a new Symptom, and maybe it's not such a bad idea, as it could reduce the amount of interaction some people have to have with the command-line when they are new to Ubuntu and still want to report bugs. I think it would benefit a bit more thought though, as maybe it's a little too many clicks the way you're describing it. The way I see this, there should also be a .desktop file shipped with apport/ubuntu-bug so that such generic bugs can be filed from somewhere in the menu (I'm thinking System>Administration, even if it doesn't seem like the right place). We could then simply tell users in bug reports: click X, then Y, then type in the name of the package (which would probably be given to them by the triager), or use the cursor to click on the application that is frozen (à la xprop), and have them avoid the CLI completely. Definitely something I'll look into when I have some free time :) Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu.tl at gmail.com 4096R/EE018C93 1967 8F7D 03A1 8F38 732E  FF82 C126 33E1 EE01 8C93 From cjk at teamcharliesangels.com Wed Sep 1 18:10:52 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Wed, 1 Sep 2010 12:10:52 -0600 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> Message-ID: <20100901121052.3a85c500@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Sep 2010 17:36:46 +0000 Mohammed Amine IL Idrissi wrote: > People who are not interested in reading text already click the link > to file a bug immediately, since there is a link to it in > ReportingBugs. Creating another wiki page would reduce the amount of > text people would have to read, without removing the instructions for > those who want to file good bug reports. > Adding to this, we could tell them to run "ubuntu-bug " where > is found according to Bugs/FindRightPackage, or to run > "ubuntu-bug" if they are not sure, and follow the instructions. > > What would be ideal is that the user follow these steps: > 1. Run "ubuntu-bug". > 2. The current window opens, but with two more options: "Application > problem" and "Specific package problem (advanced)". > 2a. Choosing "Application problem" will open a window where you can > drag-and-drop an application from the menu. > 2b. Choosing "Specific package problem" will show a text entry where > the user can type the package name. > 3. If the user still can't know the specific problem, an alert shows > and warns him that filing a bug without a package is not recommended, > with a checkbox named: "This bug is about an application that needs > packaging". > > Thank you, > Mohamed Amine IL Idrissi > > On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: > > On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: > >> Maybe we could redirect them to another wiki page that explains that > >> this is not the recommended way to report a bug, and then give them a > >> link to file a bug anyway, and a link to ReportingBugs. > > > > But that would defeat the purpose of ReportingBug page as most visitors > > wouldn't ever read it but click the link to file a bug immediately. > > People who have problems are not interested in reading text, they just > > want to get their it fixed. Unfortunately this way they file low quality > > reports that make our work harder and most of us are not full-time bug > > triagers. We already get more reports we can really deal with (i.e. > > triage and fix in stable release) anyway. > > > > Cheers, > >  KK > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > > So, even though we already have the link, and people don't bother reading, you suggest another wiki page to further complicate their desire to file bad bugs? We already tell them the recommended way to file the bug, if they ignore that, why make it easier to ignore? - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMfpcsAAoJEFNEIRz9dxbAxpcIAIVYnusj2BSiLEYHKnEPppNi Gn44ut9sX5CI8hZwsg+XVQS2q+2fuMXDsIX/HEGJRp94K1k5UY5v68G2ygsgOLyp cfhXmIl80vqr3HiIEIepTBrnQhi9XoIt8DTPH8cp/i1OuUaZS7GqbYcQTuZk3NnK xApcOUNv+MY8iwaOg5jlDLebS0kWDn0jM/BM1bqKbj6FrxvQZAQuGlAgII1cLtCF CoQNlXbNDx5nc/Si0yQFIGFeTYdA+KIoIOlaazoNfH3Or4cVbkGDdGsMzkItcC+l P3pJUEq/511pV2p89js9h84k7MpWIfUH8NClHsZtMssmPkLXtc+r/cT0vcZKw+I= =GOKY -----END PGP SIGNATURE----- From yofel at gmx.net Wed Sep 1 18:59:00 2010 From: yofel at gmx.net (Philip Muskovac) Date: Wed, 01 Sep 2010 20:59:00 +0200 Subject: launchpad +filebug redirect In-Reply-To: <20100901121052.3a85c500@teamcharliesangels.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> Message-ID: <4C7EA274.3040904@gmx.net> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: > On Wed, 1 Sep 2010 17:36:46 +0000 > Mohammed Amine IL Idrissi wrote: > >> People who are not interested in reading text already click the link >> to file a bug immediately, since there is a link to it in >> ReportingBugs. Creating another wiki page would reduce the amount of >> text people would have to read, without removing the instructions for >> those who want to file good bug reports. >> Adding to this, we could tell them to run "ubuntu-bug " where >> is found according to Bugs/FindRightPackage, or to run >> "ubuntu-bug" if they are not sure, and follow the instructions. > >> What would be ideal is that the user follow these steps: >> 1. Run "ubuntu-bug". >> 2. The current window opens, but with two more options: "Application >> problem" and "Specific package problem (advanced)". >> 2a. Choosing "Application problem" will open a window where you can >> drag-and-drop an application from the menu. >> 2b. Choosing "Specific package problem" will show a text entry where >> the user can type the package name. >> 3. If the user still can't know the specific problem, an alert shows >> and warns him that filing a bug without a package is not recommended, >> with a checkbox named: "This bug is about an application that needs >> packaging". > >> Thank you, >> Mohamed Amine IL Idrissi > >> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: >>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: >>>> Maybe we could redirect them to another wiki page that explains that >>>> this is not the recommended way to report a bug, and then give them a >>>> link to file a bug anyway, and a link to ReportingBugs. >>> >>> But that would defeat the purpose of ReportingBug page as most visitors >>> wouldn't ever read it but click the link to file a bug immediately. >>> People who have problems are not interested in reading text, they just >>> want to get their it fixed. Unfortunately this way they file low quality >>> reports that make our work harder and most of us are not full-time bug >>> triagers. We already get more reports we can really deal with (i.e. >>> triage and fix in stable release) anyway. >>> >>> Cheers, >>> KK >>> >>> -- >>> Ubuntu-bugsquad mailing list >>> Ubuntu-bugsquad at lists.ubuntu.com >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> >>> > > > So, even though we already have the link, and people don't bother > reading, you suggest another wiki page to further complicate their > desire to file bad bugs? We already tell them the recommended way to > file the bug, if they ignore that, why make it easier to ignore? > The link at the top was added recently: 140 2010-08-07 10:57:04 11547 oCean_ Mention the no-redirect url at top from the launchpad page oCean_ seems to be a new user, does anyone know him? I don't like the link being at the top either. Also, as I already wrote: the reporting guidelines at the +filebug page originally only required the user to add the application package if possible, the app version and the ubuntu release they're running. Many happily ignored that, so why do you think they would actually stop filing the bug there and click themselves through like a dozen windows for a kernel report? I seriously doubt they would do that. As for needs-packaging. The official documentation for that [1] has a link that uses ?no-redirect and adds the tag to the bug. Why don't people use that? You can file bugs with gpg signed mails too btw which would be another easy way to file those IMO. From yofel at gmx.net Wed Sep 1 19:00:29 2010 From: yofel at gmx.net (Philip Muskovac) Date: Wed, 01 Sep 2010 21:00:29 +0200 Subject: launchpad +filebug redirect In-Reply-To: <4C7EA274.3040904@gmx.net> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> Message-ID: <4C7EA2CD.6050701@gmx.net> On 09/01/2010 08:59 PM, Philip Muskovac wrote: > On 09/01/2010 08:10 PM, Charlie Kravetz wrote: >> On Wed, 1 Sep 2010 17:36:46 +0000 >> Mohammed Amine IL Idrissi wrote: >> >>> People who are not interested in reading text already click the link >>> to file a bug immediately, since there is a link to it in >>> ReportingBugs. Creating another wiki page would reduce the amount of >>> text people would have to read, without removing the instructions for >>> those who want to file good bug reports. >>> Adding to this, we could tell them to run "ubuntu-bug " where >>> is found according to Bugs/FindRightPackage, or to run >>> "ubuntu-bug" if they are not sure, and follow the instructions. >> >>> What would be ideal is that the user follow these steps: >>> 1. Run "ubuntu-bug". >>> 2. The current window opens, but with two more options: "Application >>> problem" and "Specific package problem (advanced)". >>> 2a. Choosing "Application problem" will open a window where you can >>> drag-and-drop an application from the menu. >>> 2b. Choosing "Specific package problem" will show a text entry where >>> the user can type the package name. >>> 3. If the user still can't know the specific problem, an alert shows >>> and warns him that filing a bug without a package is not recommended, >>> with a checkbox named: "This bug is about an application that needs >>> packaging". >> >>> Thank you, >>> Mohamed Amine IL Idrissi >> >>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: >>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: >>>>> Maybe we could redirect them to another wiki page that explains that >>>>> this is not the recommended way to report a bug, and then give them a >>>>> link to file a bug anyway, and a link to ReportingBugs. >>>> >>>> But that would defeat the purpose of ReportingBug page as most visitors >>>> wouldn't ever read it but click the link to file a bug immediately. >>>> People who have problems are not interested in reading text, they just >>>> want to get their it fixed. Unfortunately this way they file low quality >>>> reports that make our work harder and most of us are not full-time bug >>>> triagers. We already get more reports we can really deal with (i.e. >>>> triage and fix in stable release) anyway. >>>> >>>> Cheers, >>>> KK >>>> >>>> -- >>>> Ubuntu-bugsquad mailing list >>>> Ubuntu-bugsquad at lists.ubuntu.com >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>>> >>>> >> >> >> So, even though we already have the link, and people don't bother >> reading, you suggest another wiki page to further complicate their >> desire to file bad bugs? We already tell them the recommended way to >> file the bug, if they ignore that, why make it easier to ignore? >> > > The link at the top was added recently: > 140 2010-08-07 10:57:04 11547 oCean_ Mention the no-redirect > url at top > from the launchpad page oCean_ seems to be a new user, does anyone know > him? I don't like the link being at the top either. > > Also, as I already wrote: the reporting guidelines at the +filebug page > originally only required the user to add the application package if > possible, the app version and the ubuntu release they're running. Many > happily ignored that, so why do you think they would actually stop > filing the bug there and click themselves through like a dozen windows > for a kernel report? I seriously doubt they would do that. > > As for needs-packaging. The official documentation for that [1] has a > link that uses ?no-redirect and adds the tag to the bug. Why don't > people use that? You can file bugs with gpg signed mails too btw which > would be another easy way to file those IMO. > Actually add the reference -.- [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages From kklimonda at ubuntu.com Wed Sep 1 19:49:27 2010 From: kklimonda at ubuntu.com (Krzysztof Klimonda) Date: Wed, 01 Sep 2010 21:49:27 +0200 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> Message-ID: <1283370567.13803.25.camel@blue> On Wed, 2010-09-01 at 14:06 -0400, Mathieu Trudel-Lapierre wrote: > On Wed, Sep 1, 2010 at 1:36 PM, Mohammed Amine IL Idrissi > wrote: > > The way I see this, there should also be a .desktop file shipped with > apport/ubuntu-bug so that such generic bugs can be filed from > somewhere in the menu (I'm thinking System>Administration, even if it > doesn't seem like the right place). We could then simply tell users in > bug reports: click X, then Y, then type in the name of the package > (which would probably be given to them by the triager), or use the > cursor to click on the application that is frozen (à la xprop), and > have them avoid the CLI completely. Wouldn't it be even worse than the "Report a Problem..." menu item in Help for every application? In 10.04 the "Report a Problem.." has been disable before release (or RC?) for a reason. We have to prioritize our time. There aren't enough bug triagers and developers to cope with amount of bugs that are being reported. The closer to release it is the chance for bug to be either duplicate or an edge case is getting bigger. Also we have to work with reporters to fix some bugs - it's more likely that the person who has read through the whole ReportingBugs page is actually determined to see it fixed. Your approach would only make it easier to file "fire-and-forget" bugs during the normal, daily workflow and then those bugs, which would have to be triaged anyway, would just rot. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From mathieu-tl at ubuntu.com Wed Sep 1 21:04:35 2010 From: mathieu-tl at ubuntu.com (Mathieu Trudel-Lapierre) Date: Wed, 01 Sep 2010 17:04:35 -0400 Subject: ubuntu-bug improvements / Report a bug in menu [was Re: launchpad +filebug redirect] In-Reply-To: <1283370567.13803.25.camel@blue> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <1283370567.13803.25.camel@blue> Message-ID: <1283375075.20508.84.camel@demeter> On mer, 2010-09-01 at 21:49 +0200, Krzysztof Klimonda wrote: > On Wed, 2010-09-01 at 14:06 -0400, Mathieu Trudel-Lapierre wrote: > > On Wed, Sep 1, 2010 at 1:36 PM, Mohammed Amine IL Idrissi > > wrote: > > > > The way I see this, there should also be a .desktop file shipped with > > apport/ubuntu-bug so that such generic bugs can be filed from > > somewhere in the menu (I'm thinking System>Administration, even if it > > doesn't seem like the right place). We could then simply tell users in > > bug reports: click X, then Y, then type in the name of the package > > (which would probably be given to them by the triager), or use the > > cursor to click on the application that is frozen (à la xprop), and > > have them avoid the CLI completely. > > Wouldn't it be even worse than the "Report a Problem..." menu item in > Help for every application? In 10.04 the "Report a Problem.." has been > disable before release (or RC?) for a reason. > As I said, I don't personally see using the console as a major issue, but I do think it's intimidating to some people... even when they already filed a bug (with +filebug) and there is information missing, which could be easily gathered with apport-collect. Perhaps I expressed myself incorrectly, as my principal interest is to facilitate getting good info from bug reporters in bugs that have already been filed. My point isn't necessarily to have a link somewhere, but that instead of making +filebug harder to use to "incorrectly" file a bug, there will probably be more benefit in having *ubuntu-bug* (and its friends) easier to get to to send high-quality bug reports. I wasn't part of the discussion on disabling "Report a Problem" in the release, so I wouldn't know what the reasoning was (will check). I can understand the idea, but feel it should still be easy enough to add information to a bug when requested, and to report legitimate issues after release. [...] > Also we have to work with reporters to fix some bugs - it's more likely > that the person who has read through the whole ReportingBugs page is > actually determined to see it fixed. Your approach would only make it > easier to file "fire-and-forget" bugs during the normal, daily workflow > and then those bugs, which would have to be triaged anyway, would just > rot. As the usage of ubuntu-bug increases along with the completeness of hooks provided by different packages, my hope is that even fire-and-forget bugs reported with ubuntu-bug would eventually have enough data to be fixable. Regards, -- Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu.tl at gmail.com 4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93 From studiofmt at gmail.com Fri Sep 3 09:52:44 2010 From: studiofmt at gmail.com (fmt) Date: Fri, 3 Sep 2010 11:52:44 +0200 Subject: mm 10.10 help Message-ID: I updated today to ubuntu 10.10 beta. When logging in, a terminal page appears asking for user's name and password. That's OK, but on the next line I'm lost: username at computername:^$ _ I re-logged on recovery mode as graphics only. I would like to know, if possible, what happened and how to proceed further. I never had such a problem with ll 10.4. In case this post was not correctly addressed, pls indicate where I can find some help. -- Fabrizio Maria Tirotti Studio d'Ingegneria FMT Viale Corsica 4 20137 MILANO (ITALIA) tel. +39 0270105502 fax +39 0299983128 gsm +39 3475884539 studiofmt at gmail.com http://sites.google.com/site/studiofmt skype/msn/yahoo/voipstunt userid = studiofmt Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. This message contains confidential and privileged information and is intended only for the individuals to whom it is addressed. It should not be reviewed, retransmitted, disseminated or otherwise used by persons or entities other than the intended recipient. If you received this message in error, please contact the sender and delete the material from your computer system(s). Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dreadpiratejeff at gmail.com Fri Sep 3 13:33:45 2010 From: dreadpiratejeff at gmail.com (J) Date: Fri, 3 Sep 2010 09:33:45 -0400 Subject: mm 10.10 help In-Reply-To: References: Message-ID: On Fri, Sep 3, 2010 at 05:52, fmt wrote: > I updated today to ubuntu 10.10 beta. When logging in, a terminal page > appears asking for user's name and password. That's OK, but on the next line > I'm lost: > username at computername:^$ _ > I re-logged on recovery mode as graphics only. I would like to know, if > possible, what happened and how to proceed further. > I never had such a problem with ll 10.4. > In case this post was not correctly addressed, pls indicate where I can find > some help. Hi, yeah, this probably isn't the right list... the support list is ubuntu-users at lists.ubuntu.com That being said, ask over there. BUT, in the meantime, think about your graphics card... log in and type the command startx and see if it starts the GUI or if you just get errors. And when you post over in ubuntu-users, be sure to specify what video card you have. If you're like me, it's nVidia and needs the nVidia drivers. The drivers package for 10.10 currently contains an older version of the nVidia driver that does not support the current ABI and thus does not work. The options in that case are to download the driver directly from nVidia, or wait a bit, as the new driver has been fix-committed for this bug and should appear as an update for maverick soon. Cheers, Jeff From jeremy.foshee at canonical.com Fri Sep 3 18:28:51 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Fri, 3 Sep 2010 14:28:51 -0400 Subject: Kernel Triage Summit September 11th 1400-1800 UTC Message-ID: <20100903182851.GB2741@nightcrawler> Folks, I look forward to seeing all of you on September 11th between the hours of 10AM and 2PM EST, which translates to 1400 to 1800 UTC or 2PM to 6PM for those not accustomed to 24 hour clocks, for the first ever Kernel Triage Sumit! :-) The information and schedule is available on the Fridge Calendar. [1] We will be holding a general session at 1400 covering general kernel team information as well as the new subsystem breakdown of bugs. This will be followed by a session on Graphics, a session on Audio and finally a session on the various hardware stacks. Each of these sessions will be geared toward providing the tools necessary to conduct a basic level of triage on the relevant bugs. There will also be reference material noted online for further review. This information, as well as some of the possible topics of the sessions is available on the wiki. [2] Your feedback on the usefulness of these sessions is welcome. Please send us some feedback after the event to the kernel team mailing list at kernel-team at lists.ubuntu.com. Hope to see many of you there! ~JFo [1] http://fridge.ubuntu.com/node/2038 [2] https://wiki.ubuntu.com/Kernel/BugTriage/Summit/Maverick From chrisccoulson at ubuntu.com Fri Sep 3 18:43:49 2010 From: chrisccoulson at ubuntu.com (Chris Coulson) Date: Fri, 03 Sep 2010 19:43:49 +0100 Subject: Firefox and Apport in Ubuntu Message-ID: <1283539429.25166.26.camel@chris-laptop> Hi, Starting in Maverick, we have blacklisted Firefox in Apport and switched on the upstream crash reporter. This means that we should no longer be receiving crash reports for Firefox in Launchpad, but users will be submitting them upstream instead. So, why have we made this change? Previously, Mozilla have had quite poor visibility of crashes on Linux, primarily because most users run the Firefox version provided by their distribution rather than the builds provided from Mozilla. Information from crash reports is an important part of their QA process to ensure they can deliver high quality updates, and catch regressions early. In addition to this, crash reports have generally piled up on Launchpad over time, and we don't have the manpower required to forward these reports to where they will be most useful (ie, to Mozilla). Crash reports forwarded to their Bugzilla are generally less useful anyway, as it is more difficult to spot patterns or common issues across crash reports. So, how does this affect you? Traditionally, if a user reported a bug in Launchpad saying that Firefox is crashing, but without using Apport or providing a useful backtrace, one of the following would happen: 1) The report would be closed and the reporter asked to submit a new report using Apport. 2) The reporter would be asked for a backtrace. Starting in Maverick (and also in Lucid when Firefox 3.6.9 is released later this month), bug triagers should follow the following process when somebody reports that Firefox is crashing: 1) Ask the reporter to submit their crash report directly to Mozilla using the upstream crash reporter. 2) Ask the reporter to provide the crash ID from their crash report (available in about:crashes). The crash ID will resolve to something like this: http://crash-stats.mozilla.com/report/index/bp-ae5a1427-d9f6-4966-bc7e-1dd4a2100831 If it is obvious from the backtrace that the crash is an upstream problem, then the Launchpad bug can be closed. However, please don't do this unless you are absolutely sure of this (If in doubt, please ask Micah Gersten or myself). If the backtrace indicates that the problem might be with one of our platform libraries, then please ask the reporter to provide a new backtrace in the usual way (a new backtrace is required here because the Mozilla server doesn't have access to the symbols required to properly resolve issues outside of Mozilla code). If you have any questions, please don't hesitate to contact me. Thanks Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From yofel at gmx.net Fri Sep 3 19:02:39 2010 From: yofel at gmx.net (Philip Muskovac) Date: Fri, 03 Sep 2010 21:02:39 +0200 Subject: launchpad +filebug redirect In-Reply-To: <1283370567.13803.25.camel@blue> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <1283370567.13803.25.camel@blue> Message-ID: <4C81464F.2030603@gmx.net> Before we forget about the matter: should the no-redirect link on the top of [1] be removed? I personally don't like it being there nor do I know the person that put it there, nor does anyone else I asked. [1] https://help.ubuntu.com/community/ReportingBugs From cjk at teamcharliesangels.com Fri Sep 3 19:18:16 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Fri, 3 Sep 2010 13:18:16 -0600 Subject: launchpad +filebug redirect In-Reply-To: <4C81464F.2030603@gmx.net> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <1283370567.13803.25.camel@blue> <4C81464F.2030603@gmx.net> Message-ID: <20100903131816.2eb6dbc2@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 03 Sep 2010 21:02:39 +0200 Philip Muskovac wrote: > Before we forget about the matter: should the no-redirect link on the > top of [1] be removed? I personally don't like it being there nor do I > know the person that put it there, nor does anyone else I asked. > > [1] https://help.ubuntu.com/community/ReportingBugs > +1 to remove - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMgUn4AAoJEFNEIRz9dxbAqbAIAIms7M6U3+uoik1jNjKZ8XsO PPnyOzhcJOf09BlMcYW0Jfk7CnKH+WcsxgsJVpM2mXyQFy/wZD1p6NxA40BJ+GN3 Rtg3nkk4Ns8K+MfdYGz77aKe823V0CgZq5pjuw1lhVVVSOY073RzU74yBFBENQjc O8Y9Y9NqCt+NsMsa8dmtJe4+vJl1TlmFiwgvjccG0H4/+jpDKv5O+uc193EJ+iLO XGoIM2cL0sP5a8SCM+RtKotERyro7nthV2DmJcVzg5UfcT/SBFTNKgUqxA2GrmPW khgPjJbplfQ68tIQULYdwW8Wv8hQERaMqHCCvNqRwM7M3DkInrICSiepZ4n09OQ= =+lDb -----END PGP SIGNATURE----- From ilidrissiamine at gmail.com Fri Sep 3 19:23:26 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Fri, 3 Sep 2010 19:23:26 +0000 Subject: launchpad +filebug redirect In-Reply-To: <4C81464F.2030603@gmx.net> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <1283370567.13803.25.camel@blue> <4C81464F.2030603@gmx.net> Message-ID: On Fri, Sep 3, 2010 at 7:02 PM, Philip Muskovac wrote: > Before we forget about the matter: should the no-redirect link on the > top of [1] be removed? I personally don't like it being there nor do I > know the person that put it there, nor does anyone else I asked. > > [1] https://help.ubuntu.com/community/ReportingBugs > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > Yes, this should be removed. From kklimonda at ubuntu.com Fri Sep 3 19:40:16 2010 From: kklimonda at ubuntu.com (Krzysztof Klimonda) Date: Fri, 03 Sep 2010 21:40:16 +0200 Subject: launchpad +filebug redirect In-Reply-To: <4C81464F.2030603@gmx.net> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <1283370567.13803.25.camel@blue> <4C81464F.2030603@gmx.net> Message-ID: <1283542816.3067.1.camel@blue> On Fri, 2010-09-03 at 21:02 +0200, Philip Muskovac wrote: > Before we forget about the matter: should the no-redirect link on the > top of [1] be removed? I personally don't like it being there nor do I > know the person that put it there, nor does anyone else I asked. > > [1] https://help.ubuntu.com/community/ReportingBugs > As mentioned on IRC I've already reverted last two commits. Cheers, KK -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From webmaster at ubuntu.com Fri Sep 3 19:36:53 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Fri, 03 Sep 2010 19:36:53 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_kklimonda?= Message-ID: <20100903193653.26432.25428@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 kklimonda: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=141&rev2=142 The comment on the change is: Manually "revert" last two commits by removing the newly added sentence that hasn't been discussed. ------------------------------------------------------------------------------ <> '''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 manually creating a report using Launchpad, you can continue [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect|here]]. = Reporting bugs = From cyan.spam at gmail.com Mon Sep 6 21:04:38 2010 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 06 Sep 2010 17:04:38 -0400 Subject: launchpad +filebug redirect In-Reply-To: <4C7EA2CD.6050701@gmx.net> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> Message-ID: <4C855766.9070908@gmail.com> On 09/01/2010 03:00 PM, Philip Muskovac wrote: > On 09/01/2010 08:59 PM, Philip Muskovac wrote: >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: >>> On Wed, 1 Sep 2010 17:36:46 +0000 >>> Mohammed Amine IL Idrissi wrote: >>> >>>> People who are not interested in reading text already click the link >>>> to file a bug immediately, since there is a link to it in >>>> ReportingBugs. Creating another wiki page would reduce the amount of >>>> text people would have to read, without removing the instructions for >>>> those who want to file good bug reports. >>>> Adding to this, we could tell them to run "ubuntu-bug " where >>>> is found according to Bugs/FindRightPackage, or to run >>>> "ubuntu-bug" if they are not sure, and follow the instructions. >>> >>>> What would be ideal is that the user follow these steps: >>>> 1. Run "ubuntu-bug". >>>> 2. The current window opens, but with two more options: "Application >>>> problem" and "Specific package problem (advanced)". >>>> 2a. Choosing "Application problem" will open a window where you can >>>> drag-and-drop an application from the menu. >>>> 2b. Choosing "Specific package problem" will show a text entry where >>>> the user can type the package name. >>>> 3. If the user still can't know the specific problem, an alert shows >>>> and warns him that filing a bug without a package is not recommended, >>>> with a checkbox named: "This bug is about an application that needs >>>> packaging". >>> >>>> Thank you, >>>> Mohamed Amine IL Idrissi >>> >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: >>>>>> Maybe we could redirect them to another wiki page that explains that >>>>>> this is not the recommended way to report a bug, and then give them a >>>>>> link to file a bug anyway, and a link to ReportingBugs. >>>>> >>>>> But that would defeat the purpose of ReportingBug page as most visitors >>>>> wouldn't ever read it but click the link to file a bug immediately. >>>>> People who have problems are not interested in reading text, they just >>>>> want to get their it fixed. Unfortunately this way they file low quality >>>>> reports that make our work harder and most of us are not full-time bug >>>>> triagers. We already get more reports we can really deal with (i.e. >>>>> triage and fix in stable release) anyway. >>>>> >>>>> Cheers, >>>>> KK >>>>> >>>>> -- >>>>> Ubuntu-bugsquad mailing list >>>>> Ubuntu-bugsquad at lists.ubuntu.com >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>>>> >>>>> >>> >>> >>> So, even though we already have the link, and people don't bother >>> reading, you suggest another wiki page to further complicate their >>> desire to file bad bugs? We already tell them the recommended way to >>> file the bug, if they ignore that, why make it easier to ignore? >>> >> >> The link at the top was added recently: >> 140 2010-08-07 10:57:04 11547 oCean_ Mention the no-redirect >> url at top >> from the launchpad page oCean_ seems to be a new user, does anyone know >> him? I don't like the link being at the top either. >> >> Also, as I already wrote: the reporting guidelines at the +filebug page >> originally only required the user to add the application package if >> possible, the app version and the ubuntu release they're running. Many >> happily ignored that, so why do you think they would actually stop >> filing the bug there and click themselves through like a dozen windows >> for a kernel report? I seriously doubt they would do that. >> >> As for needs-packaging. The official documentation for that [1] has a >> link that uses ?no-redirect and adds the tag to the bug. Why don't >> people use that? You can file bugs with gpg signed mails too btw which >> would be another easy way to file those IMO. >> > > Actually add the reference -.- > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages > Well, I did not mean to start such a big discussion here; I don't think the problem is /that/ bad, so I don't think it needs a complex solution. :) To clarify my problem statement, the Reporting Bugs howto just has too much header material. You have: 1) Some BOLD text which catches your eye, possibly unrelated to the reason you came to the page. 2) A redundant "Reporting bugs" header, which further emphasizes the awkwardness of the bold text. 3) A reasonable intro. 4) Note 1 -- more distraction. 5) Note 2 -- and more distraction. This is just not user-friendly. A smattering of notes and distractions just obfuscates the real information on the page and makes it less useful. Perhaps you don't agree with me, but in both my personal and professional life I have found this to be true. If changing launchpad would be too hard, the idea of an alternative redirect page makes a lot of sense to me. How about the following content: ------- Since you've ended up on this page, you were probably trying to file a bug about Ubuntu in Launchpad. Although filing directly on Launchpad used to be an acceptable method of reporting a bug, using tools built-in to your Ubuntu system is now recommended. Please see [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for instructions. Thank you for your cooperation. ------- Disagreements welcome, but please explain why this idea would be inferior to the status quo. Thanks! Regards, David From cjk at teamcharliesangels.com Mon Sep 6 21:50:09 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Mon, 6 Sep 2010 15:50:09 -0600 Subject: launchpad +filebug redirect In-Reply-To: <4C855766.9070908@gmail.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> Message-ID: <20100906155009.53b70a5d@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 06 Sep 2010 17:04:38 -0400 David Tombs wrote: > On 09/01/2010 03:00 PM, Philip Muskovac wrote: > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: > >>> On Wed, 1 Sep 2010 17:36:46 +0000 > >>> Mohammed Amine IL Idrissi wrote: > >>> > >>>> People who are not interested in reading text already click the link > >>>> to file a bug immediately, since there is a link to it in > >>>> ReportingBugs. Creating another wiki page would reduce the amount of > >>>> text people would have to read, without removing the instructions for > >>>> those who want to file good bug reports. > >>>> Adding to this, we could tell them to run "ubuntu-bug " where > >>>> is found according to Bugs/FindRightPackage, or to run > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. > >>> > >>>> What would be ideal is that the user follow these steps: > >>>> 1. Run "ubuntu-bug". > >>>> 2. The current window opens, but with two more options: "Application > >>>> problem" and "Specific package problem (advanced)". > >>>> 2a. Choosing "Application problem" will open a window where you can > >>>> drag-and-drop an application from the menu. > >>>> 2b. Choosing "Specific package problem" will show a text entry where > >>>> the user can type the package name. > >>>> 3. If the user still can't know the specific problem, an alert shows > >>>> and warns him that filing a bug without a package is not recommended, > >>>> with a checkbox named: "This bug is about an application that needs > >>>> packaging". > >>> > >>>> Thank you, > >>>> Mohamed Amine IL Idrissi > >>> > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: > >>>>>> Maybe we could redirect them to another wiki page that explains that > >>>>>> this is not the recommended way to report a bug, and then give them a > >>>>>> link to file a bug anyway, and a link to ReportingBugs. > >>>>> > >>>>> But that would defeat the purpose of ReportingBug page as most visitors > >>>>> wouldn't ever read it but click the link to file a bug immediately. > >>>>> People who have problems are not interested in reading text, they just > >>>>> want to get their it fixed. Unfortunately this way they file low quality > >>>>> reports that make our work harder and most of us are not full-time bug > >>>>> triagers. We already get more reports we can really deal with (i.e. > >>>>> triage and fix in stable release) anyway. > >>>>> > >>>>> Cheers, > >>>>> KK > >>>>> > >>>>> -- > >>>>> Ubuntu-bugsquad mailing list > >>>>> Ubuntu-bugsquad at lists.ubuntu.com > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>>>> > >>>>> > >>> > >>> > >>> So, even though we already have the link, and people don't bother > >>> reading, you suggest another wiki page to further complicate their > >>> desire to file bad bugs? We already tell them the recommended way to > >>> file the bug, if they ignore that, why make it easier to ignore? > >>> > >> > >> The link at the top was added recently: > >> 140 2010-08-07 10:57:04 11547 oCean_ Mention the no-redirect > >> url at top > >> from the launchpad page oCean_ seems to be a new user, does anyone know > >> him? I don't like the link being at the top either. > >> > >> Also, as I already wrote: the reporting guidelines at the +filebug page > >> originally only required the user to add the application package if > >> possible, the app version and the ubuntu release they're running. Many > >> happily ignored that, so why do you think they would actually stop > >> filing the bug there and click themselves through like a dozen windows > >> for a kernel report? I seriously doubt they would do that. > >> > >> As for needs-packaging. The official documentation for that [1] has a > >> link that uses ?no-redirect and adds the tag to the bug. Why don't > >> people use that? You can file bugs with gpg signed mails too btw which > >> would be another easy way to file those IMO. > >> > > > > Actually add the reference -.- > > > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages > > > > Well, I did not mean to start such a big discussion here; I don't think > the problem is /that/ bad, so I don't think it needs a complex solution. :) > > To clarify my problem statement, the Reporting Bugs howto just has too > much header material. You have: > > 1) Some BOLD text which catches your eye, possibly unrelated to the > reason you came to the page. > 2) A redundant "Reporting bugs" header, which further emphasizes the > awkwardness of the bold text. > 3) A reasonable intro. > 4) Note 1 -- more distraction. > 5) Note 2 -- and more distraction. > > This is just not user-friendly. A smattering of notes and distractions > just obfuscates the real information on the page and makes it less > useful. Perhaps you don't agree with me, but in both my personal and > professional life I have found this to be true. > > If changing launchpad would be too hard, the idea of an alternative > redirect page makes a lot of sense to me. How about the following content: > > ------- > Since you've ended up on this page, you were probably trying to file a > bug about Ubuntu in Launchpad. Although filing directly on Launchpad > used to be an acceptable method of reporting a bug, using tools built-in > to your Ubuntu system is now recommended. Please see > [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for > instructions. > > Thank you for your cooperation. > ------- > > Disagreements welcome, but please explain why this idea would be > inferior to the status quo. Thanks! > > Regards, > David > Somehow, redirecting me to the same page I started on is not good. Why do we have to redirect the user at all. If the page is written that bad, why not suggest a re-write, instead of a re-direct. If they are going to read the new page they are sent to, they will read the page they are already at. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMhWIRAAoJEFNEIRz9dxbAdHUIAJA/WNWteQgrTwaLhLxk7Axx ARZ0RxmO5WJxDcRtU0nNRW/YNLYhHxV+vjzsGLX/dz8dKoB3NY6lIq5KiHh+lIjK cwTmP8zVBOp4UtcNUlvAs4X2vjXy5CxeeRwO7o5ovRvUAJYJM5bxm5qEEsaVRnvV p3ijrKzmhDO55/yxFEiT43AwfNYNEcKjDxggUWvYzAAheV8rvA4SZjnUOjuvXPZA es8txM2U/uaoXejOnKTj1Kk8AOHZK96cpxxM9CFQuRTxP+8bBjjntRp69/W0ou3h F2l5fTc5I//P9MtpeQ3iOCKIpRp0Xi47/hhrOe+3qVE4tGPkrU9imeMACUEwr64= =f7SD -----END PGP SIGNATURE----- From cjk at teamcharliesangels.com Mon Sep 6 21:51:47 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Mon, 6 Sep 2010 15:51:47 -0600 Subject: launchpad +filebug redirect In-Reply-To: <4C855766.9070908@gmail.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> Message-ID: <20100906155147.0c263c65@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 06 Sep 2010 17:04:38 -0400 David Tombs wrote: > On 09/01/2010 03:00 PM, Philip Muskovac wrote: > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: > >>> On Wed, 1 Sep 2010 17:36:46 +0000 > >>> Mohammed Amine IL Idrissi wrote: > >>> > >>>> People who are not interested in reading text already click the link > >>>> to file a bug immediately, since there is a link to it in > >>>> ReportingBugs. Creating another wiki page would reduce the amount of > >>>> text people would have to read, without removing the instructions for > >>>> those who want to file good bug reports. > >>>> Adding to this, we could tell them to run "ubuntu-bug " where > >>>> is found according to Bugs/FindRightPackage, or to run > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. > >>> > >>>> What would be ideal is that the user follow these steps: > >>>> 1. Run "ubuntu-bug". > >>>> 2. The current window opens, but with two more options: "Application > >>>> problem" and "Specific package problem (advanced)". > >>>> 2a. Choosing "Application problem" will open a window where you can > >>>> drag-and-drop an application from the menu. > >>>> 2b. Choosing "Specific package problem" will show a text entry where > >>>> the user can type the package name. > >>>> 3. If the user still can't know the specific problem, an alert shows > >>>> and warns him that filing a bug without a package is not recommended, > >>>> with a checkbox named: "This bug is about an application that needs > >>>> packaging". > >>> > >>>> Thank you, > >>>> Mohamed Amine IL Idrissi > >>> > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda wrote: > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: > >>>>>> Maybe we could redirect them to another wiki page that explains that > >>>>>> this is not the recommended way to report a bug, and then give them a > >>>>>> link to file a bug anyway, and a link to ReportingBugs. > >>>>> > >>>>> But that would defeat the purpose of ReportingBug page as most visitors > >>>>> wouldn't ever read it but click the link to file a bug immediately. > >>>>> People who have problems are not interested in reading text, they just > >>>>> want to get their it fixed. Unfortunately this way they file low quality > >>>>> reports that make our work harder and most of us are not full-time bug > >>>>> triagers. We already get more reports we can really deal with (i.e. > >>>>> triage and fix in stable release) anyway. > >>>>> > >>>>> Cheers, > >>>>> KK > >>>>> > >>>>> -- > >>>>> Ubuntu-bugsquad mailing list > >>>>> Ubuntu-bugsquad at lists.ubuntu.com > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>>>> > >>>>> > >>> > >>> > >>> So, even though we already have the link, and people don't bother > >>> reading, you suggest another wiki page to further complicate their > >>> desire to file bad bugs? We already tell them the recommended way to > >>> file the bug, if they ignore that, why make it easier to ignore? > >>> > >> > >> The link at the top was added recently: > >> 140 2010-08-07 10:57:04 11547 oCean_ Mention the no-redirect > >> url at top > >> from the launchpad page oCean_ seems to be a new user, does anyone know > >> him? I don't like the link being at the top either. > >> > >> Also, as I already wrote: the reporting guidelines at the +filebug page > >> originally only required the user to add the application package if > >> possible, the app version and the ubuntu release they're running. Many > >> happily ignored that, so why do you think they would actually stop > >> filing the bug there and click themselves through like a dozen windows > >> for a kernel report? I seriously doubt they would do that. > >> > >> As for needs-packaging. The official documentation for that [1] has a > >> link that uses ?no-redirect and adds the tag to the bug. Why don't > >> people use that? You can file bugs with gpg signed mails too btw which > >> would be another easy way to file those IMO. > >> > > > > Actually add the reference -.- > > > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages > > > > Well, I did not mean to start such a big discussion here; I don't think > the problem is /that/ bad, so I don't think it needs a complex solution. :) > > To clarify my problem statement, the Reporting Bugs howto just has too > much header material. You have: > > 1) Some BOLD text which catches your eye, possibly unrelated to the > reason you came to the page. > 2) A redundant "Reporting bugs" header, which further emphasizes the > awkwardness of the bold text. > 3) A reasonable intro. > 4) Note 1 -- more distraction. > 5) Note 2 -- and more distraction. > > This is just not user-friendly. A smattering of notes and distractions > just obfuscates the real information on the page and makes it less > useful. Perhaps you don't agree with me, but in both my personal and > professional life I have found this to be true. > > If changing launchpad would be too hard, the idea of an alternative > redirect page makes a lot of sense to me. How about the following content: > > ------- > Since you've ended up on this page, you were probably trying to file a > bug about Ubuntu in Launchpad. Although filing directly on Launchpad > used to be an acceptable method of reporting a bug, using tools built-in > to your Ubuntu system is now recommended. Please see > [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for > instructions. > > Thank you for your cooperation. > ------- > > Disagreements welcome, but please explain why this idea would be > inferior to the status quo. Thanks! > > Regards, > David > I guess I should have added that the more pages I have to shovel my way through, the more frustrating the task becomes. It really is much simpler and more convenient to stay on the page than to have to open more pages to read what could have already been said. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMhWJzAAoJEFNEIRz9dxbArmwH/1nNqBOcCwrrTluDdASErwuA OvfgbXZXT2oAxkCDOc8WoPwVllQWY3oBDazaZj8hocY0/wa8YFzVuWWiToPvQw5D wfQir4XGr0rDjFxp3LCegc0Ut/5w3S2OCJxUYxBdi4XZcIhB4nfvJhBvdYrLPbEu Girv13wqjNAfS76UXnA7a+GyF63L+fZ+h3OgR+yV5cjcOZmgFum29EDboxMKrCPD XWqMkIcl3Jiw/hZ84n6qDTuTzbPY4xxU6AqFrwIDQJtkKw7LdZYB+SpQrnCxm053 hrpwZYnivX74IERdEUZuY4Ei8hFF/QDR9kUpiv/l1ZcXcU7kaG9945AqY+oowsY= =MDM6 -----END PGP SIGNATURE----- From ilidrissiamine at gmail.com Mon Sep 6 21:53:50 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Mon, 6 Sep 2010 21:53:50 +0000 Subject: launchpad +filebug redirect In-Reply-To: <20100906155009.53b70a5d@teamcharliesangels.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> Message-ID: I'm in the process of rewriting the ReportingBugs page. I'll re-post when I'll have something working. On Mon, Sep 6, 2010 at 9:50 PM, Charlie Kravetz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 06 Sep 2010 17:04:38 -0400 > David Tombs wrote: > > > On 09/01/2010 03:00 PM, Philip Muskovac wrote: > > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: > > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: > > >>> On Wed, 1 Sep 2010 17:36:46 +0000 > > >>> Mohammed Amine IL Idrissi wrote: > > >>> > > >>>> People who are not interested in reading text already click the link > > >>>> to file a bug immediately, since there is a link to it in > > >>>> ReportingBugs. Creating another wiki page would reduce the amount of > > >>>> text people would have to read, without removing the instructions > for > > >>>> those who want to file good bug reports. > > >>>> Adding to this, we could tell them to run "ubuntu-bug " > where > > >>>> is found according to Bugs/FindRightPackage, or to run > > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. > > >>> > > >>>> What would be ideal is that the user follow these steps: > > >>>> 1. Run "ubuntu-bug". > > >>>> 2. The current window opens, but with two more options: "Application > > >>>> problem" and "Specific package problem (advanced)". > > >>>> 2a. Choosing "Application problem" will open a window where you can > > >>>> drag-and-drop an application from the menu. > > >>>> 2b. Choosing "Specific package problem" will show a text entry where > > >>>> the user can type the package name. > > >>>> 3. If the user still can't know the specific problem, an alert shows > > >>>> and warns him that filing a bug without a package is not > recommended, > > >>>> with a checkbox named: "This bug is about an application that needs > > >>>> packaging". > > >>> > > >>>> Thank you, > > >>>> Mohamed Amine IL Idrissi > > >>> > > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda < > kklimonda at ubuntu.com> wrote: > > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi wrote: > > >>>>>> Maybe we could redirect them to another wiki page that explains > that > > >>>>>> this is not the recommended way to report a bug, and then give > them a > > >>>>>> link to file a bug anyway, and a link to ReportingBugs. > > >>>>> > > >>>>> But that would defeat the purpose of ReportingBug page as most > visitors > > >>>>> wouldn't ever read it but click the link to file a bug immediately. > > >>>>> People who have problems are not interested in reading text, they > just > > >>>>> want to get their it fixed. Unfortunately this way they file low > quality > > >>>>> reports that make our work harder and most of us are not full-time > bug > > >>>>> triagers. We already get more reports we can really deal with (i.e. > > >>>>> triage and fix in stable release) anyway. > > >>>>> > > >>>>> Cheers, > > >>>>> KK > > >>>>> > > >>>>> -- > > >>>>> Ubuntu-bugsquad mailing list > > >>>>> Ubuntu-bugsquad at lists.ubuntu.com > > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > >>>>> > > >>>>> > > >>> > > >>> > > >>> So, even though we already have the link, and people don't bother > > >>> reading, you suggest another wiki page to further complicate their > > >>> desire to file bad bugs? We already tell them the recommended way to > > >>> file the bug, if they ignore that, why make it easier to ignore? > > >>> > > >> > > >> The link at the top was added recently: > > >> 140 2010-08-07 10:57:04 11547 oCean_ > Mention the no-redirect > > >> url at top > > >> from the launchpad page oCean_ seems to be a new user, does anyone > know > > >> him? I don't like the link being at the top either. > > >> > > >> Also, as I already wrote: the reporting guidelines at the +filebug > page > > >> originally only required the user to add the application package if > > >> possible, the app version and the ubuntu release they're running. Many > > >> happily ignored that, so why do you think they would actually stop > > >> filing the bug there and click themselves through like a dozen windows > > >> for a kernel report? I seriously doubt they would do that. > > >> > > >> As for needs-packaging. The official documentation for that [1] has a > > >> link that uses ?no-redirect and adds the tag to the bug. Why don't > > >> people use that? You can file bugs with gpg signed mails too btw which > > >> would be another easy way to file those IMO. > > >> > > > > > > Actually add the reference -.- > > > > > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages > > > > > > > Well, I did not mean to start such a big discussion here; I don't think > > the problem is /that/ bad, so I don't think it needs a complex solution. > :) > > > > To clarify my problem statement, the Reporting Bugs howto just has too > > much header material. You have: > > > > 1) Some BOLD text which catches your eye, possibly unrelated to the > > reason you came to the page. > > 2) A redundant "Reporting bugs" header, which further emphasizes the > > awkwardness of the bold text. > > 3) A reasonable intro. > > 4) Note 1 -- more distraction. > > 5) Note 2 -- and more distraction. > > > > This is just not user-friendly. A smattering of notes and distractions > > just obfuscates the real information on the page and makes it less > > useful. Perhaps you don't agree with me, but in both my personal and > > professional life I have found this to be true. > > > > If changing launchpad would be too hard, the idea of an alternative > > redirect page makes a lot of sense to me. How about the following > content: > > > > ------- > > Since you've ended up on this page, you were probably trying to file a > > bug about Ubuntu in Launchpad. Although filing directly on Launchpad > > used to be an acceptable method of reporting a bug, using tools built-in > > to your Ubuntu system is now recommended. Please see > > [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for > > instructions. > > > > Thank you for your cooperation. > > ------- > > > > Disagreements welcome, but please explain why this idea would be > > inferior to the status quo. Thanks! > > > > Regards, > > David > > > > Somehow, redirecting me to the same page I started on is not good. Why > do we have to redirect the user at all. If the page is written that > bad, why not suggest a re-write, instead of a re-direct. If they are > going to read the new page they are sent to, they will read the page > they are already at. > > - -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJMhWIRAAoJEFNEIRz9dxbAdHUIAJA/WNWteQgrTwaLhLxk7Axx > ARZ0RxmO5WJxDcRtU0nNRW/YNLYhHxV+vjzsGLX/dz8dKoB3NY6lIq5KiHh+lIjK > cwTmP8zVBOp4UtcNUlvAs4X2vjXy5CxeeRwO7o5ovRvUAJYJM5bxm5qEEsaVRnvV > p3ijrKzmhDO55/yxFEiT43AwfNYNEcKjDxggUWvYzAAheV8rvA4SZjnUOjuvXPZA > es8txM2U/uaoXejOnKTj1Kk8AOHZK96cpxxM9CFQuRTxP+8bBjjntRp69/W0ou3h > F2l5fTc5I//P9MtpeQ3iOCKIpRp0Xi47/hhrOe+3qVE4tGPkrU9imeMACUEwr64= > =f7SD > -----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 m.schneider91 at gmx.net Sun Sep 5 10:28:24 2010 From: m.schneider91 at gmx.net (Matthias Schneider) Date: Sun, 05 Sep 2010 12:28:24 +0200 Subject: Bug Kubuntu 10.04 Message-ID: <4C8370C8.3060806@gmx.net> Hi, while trying to update my software in the KPackageKit I received the following error: Error Type: Error Value: coercing to Unicode: need string or buffer, exceptions.SystemError found File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2216, in main() File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2213, in main run(args, options.single) File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2175, in run backend.dispatcher(args) File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 699, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 606, in dispatch_command self.refresh_cache(force) File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 202, in _locked_cache func(*args, **kwargs) File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 1498, in refresh_cache format_string(error.message)) File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 723, in format_string txt = unicode(text, encoding, errors='replace') Can You maybe explain me how I can solve this problem? Yours Matthias Schneider -- Matthias Schneider m.schneider91 at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at ubuntu.com Sat Sep 4 12:12:31 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Sat, 04 Sep 2010 12:12:31 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_loldrup?= Message-ID: <20100904121231.31195.41020@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 loldrup: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=142&rev2=143 The comment on the change is: fixed: The sections -Fiing bugs at Launchpad- says one can go to launchpad to file a bug, but when doing so, and clicking 'file a bug' one is taken back to this very wiki page!! Circularity linking... ------------------------------------------------------------------------------ == Filing bugs at Launchpad.net == - 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 ]]. + If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 == From webmaster at ubuntu.com Sat Sep 4 12:15:35 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Sat, 04 Sep 2010 12:15:35 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_loldrup?= Message-ID: <20100904121535.31219.5149@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 loldrup: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=143&rev2=144 The comment on the change is: A bit more polish/clarification in the same section ------------------------------------------------------------------------------ == Filing bugs at Launchpad.net == - If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 ]]. + If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 you can also use a URL like 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 ]]. == Using the menu == From webmaster at ubuntu.com Sat Sep 4 12:18:42 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Sat, 04 Sep 2010 12:18:42 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_loldrup?= Message-ID: <20100904121842.1533.4385@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 loldrup: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=144&rev2=145 ------------------------------------------------------------------------------ In the event that you have a bug with your internet connection or want to file a bug for another system you can still do this using apport. Using the command `apport-cli -f -p` ''``'' on the target system will collect information and provide you with an option to "K: Keep report file for sending later or copying to somewhere else". The report is then saved on the target system, in your ''/tmp'' directory which is cleared out on reboot, with a .apport extension. After copying it to a different system you can file that report using `ubuntu-bug ` ''``''. + == Filing bugs at Launchpad.net == + + If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 you can also use a URL like 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 ]]. + + == Using the help menu in the affected application == + + '''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 translation bugs == All translation issues should be filed against the [[https://bugs.launchpad.net/ubuntu-translations | Ubuntu Translations project]] (ubuntu-translations). From there the bugs will be triaged and assigned to the right person and package. @@ -61, +86 @@ * A template/translation is no longer used in Ubuntu and should be disabled from [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] You can also consult the [[https://bugs.launchpad.net/ubuntu-translations|current bugs]] to see the big picture. In case of doubt, you can always [[http://wiki.ubuntu.com/Translations/Contact|contact the Translations team]]. - - == Filing bugs at Launchpad.net == - - If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 you can also use a URL like 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 ]]. - - == 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 webmaster at ubuntu.com Sat Sep 4 12:24:36 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Sat, 04 Sep 2010 12:24:36 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_loldrup?= Message-ID: <20100904122436.4402.48480@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 loldrup: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=145&rev2=146 ------------------------------------------------------------------------------ === Adding Apport Debug Information to an Existing Launchpad Bug === If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. If this fails then run `apport-collect -p bug_number`. - + + [[#Top|Back to top]] - == Writing a useful report == + = Writing a useful report = When a developer fixes a bug, they will test that the bug occurs, make a small change to the program, then see if the bug has gone away. Depending on the bug, they might need to run the same test dozens or hundreds of times. When you submit a bug report, it's important to specify three things: @@ -106, +107 @@ Add supporting attachments to explain or help others reproduce your bug. This might include a screenshot or video capture of the problem or a sample document that triggers the fault. To add an attachment to the bug use the '''Include an attachment''' section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vvnn" and "dmesg", after a fresh boot, will help a lot. + - - [[#Top|Back to top]] = When not to file a bug = * '''Requesting new software''' you should follow the guidelines in https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages From noreply at ubuntu.com Sun Sep 5 07:28:13 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 05 Sep 2010 07:28:13 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_trinikrono?= Message-ID: <20100905072813.27208.72232@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 trinikrono: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=304&rev2=305 ------------------------------------------------------------------------------ == Not described well == - || Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.<
><
> We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures <
><
>At a minimum, we need:<
>1. the specific steps or actions you took that caused you to encounter the problem,<
>2. the behavior you expected, and<
>3. the behavior you actually encountered (in as much detail as possible).<
>Thanks! || + ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.<
><
> We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures <
><
>At a minimum, we need:<
>1. the specific steps or actions you took that caused you to encounter the problem,<
>2. the behavior you expected, and<
>3. the behavior you actually encountered (in as much detail as possible).<
>Thanks! || == Missing Steps to Recreate Bug == ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:<
><
>* Is this reproducible?<
>* If so, what specific steps should we take to recreate this bug?<
><
>This will help us to find and resolve the problem.|| + + == Missing Apport Information == + ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:<
>apport-collect BUGNUMBER<
>When reporting bugs in the future please use apport, using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.|| == Package or domain specific questions == The following packages or type of bugs require the specific debugging information: From ilidrissiamine at gmail.com Tue Sep 7 00:02:35 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Tue, 7 Sep 2010 00:02:35 +0000 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> Message-ID: I've set up a prototype page. Please visit https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and share your thoughts (especially on the TODO bits). Thanks, Mohamed Amine IL Idrissi On Mon, Sep 6, 2010 at 9:53 PM, Mohamed Amine IL Idrissi < ilidrissiamine at gmail.com> wrote: > I'm in the process of rewriting the ReportingBugs page. I'll re-post when > I'll have something working. > > > On Mon, Sep 6, 2010 at 9:50 PM, Charlie Kravetz < > cjk at teamcharliesangels.com> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Mon, 06 Sep 2010 17:04:38 -0400 >> David Tombs wrote: >> >> > On 09/01/2010 03:00 PM, Philip Muskovac wrote: >> > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: >> > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: >> > >>> On Wed, 1 Sep 2010 17:36:46 +0000 >> > >>> Mohammed Amine IL Idrissi wrote: >> > >>> >> > >>>> People who are not interested in reading text already click the >> link >> > >>>> to file a bug immediately, since there is a link to it in >> > >>>> ReportingBugs. Creating another wiki page would reduce the amount >> of >> > >>>> text people would have to read, without removing the instructions >> for >> > >>>> those who want to file good bug reports. >> > >>>> Adding to this, we could tell them to run "ubuntu-bug " >> where >> > >>>> is found according to Bugs/FindRightPackage, or to run >> > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. >> > >>> >> > >>>> What would be ideal is that the user follow these steps: >> > >>>> 1. Run "ubuntu-bug". >> > >>>> 2. The current window opens, but with two more options: >> "Application >> > >>>> problem" and "Specific package problem (advanced)". >> > >>>> 2a. Choosing "Application problem" will open a window where you can >> > >>>> drag-and-drop an application from the menu. >> > >>>> 2b. Choosing "Specific package problem" will show a text entry >> where >> > >>>> the user can type the package name. >> > >>>> 3. If the user still can't know the specific problem, an alert >> shows >> > >>>> and warns him that filing a bug without a package is not >> recommended, >> > >>>> with a checkbox named: "This bug is about an application that needs >> > >>>> packaging". >> > >>> >> > >>>> Thank you, >> > >>>> Mohamed Amine IL Idrissi >> > >>> >> > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda < >> kklimonda at ubuntu.com> wrote: >> > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi >> wrote: >> > >>>>>> Maybe we could redirect them to another wiki page that explains >> that >> > >>>>>> this is not the recommended way to report a bug, and then give >> them a >> > >>>>>> link to file a bug anyway, and a link to ReportingBugs. >> > >>>>> >> > >>>>> But that would defeat the purpose of ReportingBug page as most >> visitors >> > >>>>> wouldn't ever read it but click the link to file a bug >> immediately. >> > >>>>> People who have problems are not interested in reading text, they >> just >> > >>>>> want to get their it fixed. Unfortunately this way they file low >> quality >> > >>>>> reports that make our work harder and most of us are not full-time >> bug >> > >>>>> triagers. We already get more reports we can really deal with >> (i.e. >> > >>>>> triage and fix in stable release) anyway. >> > >>>>> >> > >>>>> Cheers, >> > >>>>> KK >> > >>>>> >> > >>>>> -- >> > >>>>> Ubuntu-bugsquad mailing list >> > >>>>> Ubuntu-bugsquad at lists.ubuntu.com >> > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > >>>>> >> > >>>>> >> > >>> >> > >>> >> > >>> So, even though we already have the link, and people don't bother >> > >>> reading, you suggest another wiki page to further complicate their >> > >>> desire to file bad bugs? We already tell them the recommended way to >> > >>> file the bug, if they ignore that, why make it easier to ignore? >> > >>> >> > >> >> > >> The link at the top was added recently: >> > >> 140 2010-08-07 10:57:04 11547 oCean_ >> Mention the no-redirect >> > >> url at top >> > >> from the launchpad page oCean_ seems to be a new user, does anyone >> know >> > >> him? I don't like the link being at the top either. >> > >> >> > >> Also, as I already wrote: the reporting guidelines at the +filebug >> page >> > >> originally only required the user to add the application package if >> > >> possible, the app version and the ubuntu release they're running. >> Many >> > >> happily ignored that, so why do you think they would actually stop >> > >> filing the bug there and click themselves through like a dozen >> windows >> > >> for a kernel report? I seriously doubt they would do that. >> > >> >> > >> As for needs-packaging. The official documentation for that [1] has a >> > >> link that uses ?no-redirect and adds the tag to the bug. Why don't >> > >> people use that? You can file bugs with gpg signed mails too btw >> which >> > >> would be another easy way to file those IMO. >> > >> >> > > >> > > Actually add the reference -.- >> > > >> > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages >> > > >> > >> > Well, I did not mean to start such a big discussion here; I don't think >> > the problem is /that/ bad, so I don't think it needs a complex solution. >> :) >> > >> > To clarify my problem statement, the Reporting Bugs howto just has too >> > much header material. You have: >> > >> > 1) Some BOLD text which catches your eye, possibly unrelated to the >> > reason you came to the page. >> > 2) A redundant "Reporting bugs" header, which further emphasizes the >> > awkwardness of the bold text. >> > 3) A reasonable intro. >> > 4) Note 1 -- more distraction. >> > 5) Note 2 -- and more distraction. >> > >> > This is just not user-friendly. A smattering of notes and distractions >> > just obfuscates the real information on the page and makes it less >> > useful. Perhaps you don't agree with me, but in both my personal and >> > professional life I have found this to be true. >> > >> > If changing launchpad would be too hard, the idea of an alternative >> > redirect page makes a lot of sense to me. How about the following >> content: >> > >> > ------- >> > Since you've ended up on this page, you were probably trying to file a >> > bug about Ubuntu in Launchpad. Although filing directly on Launchpad >> > used to be an acceptable method of reporting a bug, using tools built-in >> > to your Ubuntu system is now recommended. Please see >> > [[https://help.ubuntu.com/community/ReportingBugs|ReportingBugs]] for >> > instructions. >> > >> > Thank you for your cooperation. >> > ------- >> > >> > Disagreements welcome, but please explain why this idea would be >> > inferior to the status quo. Thanks! >> > >> > Regards, >> > David >> > >> >> Somehow, redirecting me to the same page I started on is not good. Why >> do we have to redirect the user at all. If the page is written that >> bad, why not suggest a re-write, instead of a re-direct. If they are >> going to read the new page they are sent to, they will read the page >> they are already at. >> >> - -- >> Charlie Kravetz >> Linux Registered User Number 425914 [http://counter.li.org/] >> Never let anyone steal your DREAM. [http://keepingdreams.com] >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.10 (GNU/Linux) >> >> iQEcBAEBAgAGBQJMhWIRAAoJEFNEIRz9dxbAdHUIAJA/WNWteQgrTwaLhLxk7Axx >> ARZ0RxmO5WJxDcRtU0nNRW/YNLYhHxV+vjzsGLX/dz8dKoB3NY6lIq5KiHh+lIjK >> cwTmP8zVBOp4UtcNUlvAs4X2vjXy5CxeeRwO7o5ovRvUAJYJM5bxm5qEEsaVRnvV >> p3ijrKzmhDO55/yxFEiT43AwfNYNEcKjDxggUWvYzAAheV8rvA4SZjnUOjuvXPZA >> es8txM2U/uaoXejOnKTj1Kk8AOHZK96cpxxM9CFQuRTxP+8bBjjntRp69/W0ou3h >> F2l5fTc5I//P9MtpeQ3iOCKIpRp0Xi47/hhrOe+3qVE4tGPkrU9imeMACUEwr64= >> =f7SD >> -----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 eapache at gmail.com Tue Sep 7 00:39:46 2010 From: eapache at gmail.com (Evan) Date: Mon, 6 Sep 2010 20:39:46 -0400 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> Message-ID: On Mon, Sep 6, 2010 at 8:02 PM, Mohamed Amine IL Idrissi wrote: > I've set up a prototype page. Please > visit https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and > share your thoughts (especially on the TODO bits). > Thanks, > Mohamed Amine IL Idrissi I quite like it. I've already made some minor tweaks here and there. My biggest question is whether section 5 "Write a Useful Report" should be before section 4 "File the Bug". I imagine that most people will run ubuntu-bug in section 4 and finish the whole process before going to section 5 - at which point it is too late to instruct them on how to write good reports. Another option would be to merge them somehow. Thoughts? Evan > On Mon, Sep 6, 2010 at 9:53 PM, Mohamed Amine IL Idrissi > wrote: >> >> I'm in the process of rewriting the ReportingBugs page. I'll re-post when >> I'll have something working. >> >> On Mon, Sep 6, 2010 at 9:50 PM, Charlie Kravetz >> wrote: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Mon, 06 Sep 2010 17:04:38 -0400 >>> David Tombs wrote: >>> >>> > On 09/01/2010 03:00 PM, Philip Muskovac wrote: >>> > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: >>> > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: >>> > >>> On Wed, 1 Sep 2010 17:36:46 +0000 >>> > >>> Mohammed Amine IL Idrissi wrote: >>> > >>> >>> > >>>> People who are not interested in reading text already click the >>> > >>>> link >>> > >>>> to file a bug immediately, since there is a link to it in >>> > >>>> ReportingBugs. Creating another wiki page would reduce the amount >>> > >>>> of >>> > >>>> text people would have to read, without removing the instructions >>> > >>>> for >>> > >>>> those who want to file good bug reports. >>> > >>>> Adding to this, we could tell them to run "ubuntu-bug " >>> > >>>> where >>> > >>>> is found according to Bugs/FindRightPackage, or to run >>> > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. >>> > >>> >>> > >>>> What would be ideal is that the user follow these steps: >>> > >>>> 1. Run "ubuntu-bug". >>> > >>>> 2. The current window opens, but with two more options: >>> > >>>> "Application >>> > >>>> problem" and "Specific package problem (advanced)". >>> > >>>> 2a. Choosing "Application problem" will open a window where you >>> > >>>> can >>> > >>>> drag-and-drop an application from the menu. >>> > >>>> 2b. Choosing "Specific package problem" will show a text entry >>> > >>>> where >>> > >>>> the user can type the package name. >>> > >>>> 3. If the user still can't know the specific problem, an alert >>> > >>>> shows >>> > >>>> and warns him that filing a bug without a package is not >>> > >>>> recommended, >>> > >>>> with a checkbox named: "This bug is about an application that >>> > >>>> needs >>> > >>>> packaging". >>> > >>> >>> > >>>> Thank you, >>> > >>>> Mohamed Amine IL Idrissi >>> > >>> >>> > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda >>> > >>>> wrote: >>> > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi >>> > >>>>> wrote: >>> > >>>>>> Maybe we could redirect them to another wiki page that explains >>> > >>>>>> that >>> > >>>>>> this is not the recommended way to report a bug, and then give >>> > >>>>>> them a >>> > >>>>>> link to file a bug anyway, and a link to ReportingBugs. >>> > >>>>> >>> > >>>>> But that would defeat the purpose of ReportingBug page as most >>> > >>>>> visitors >>> > >>>>> wouldn't ever read it but click the link to file a bug >>> > >>>>> immediately. >>> > >>>>> People who have problems are not interested in reading text, they >>> > >>>>> just >>> > >>>>> want to get their it fixed. Unfortunately this way they file low >>> > >>>>> quality >>> > >>>>> reports that make our work harder and most of us are not >>> > >>>>> full-time bug >>> > >>>>> triagers. We already get more reports we can really deal with >>> > >>>>> (i.e. >>> > >>>>> triage and fix in stable release) anyway. >>> > >>>>> >>> > >>>>> Cheers, >>> > >>>>>  KK >>> > >>>>> >>> > >>>>> -- >>> > >>>>> Ubuntu-bugsquad mailing list >>> > >>>>> Ubuntu-bugsquad at lists.ubuntu.com >>> > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> > >>>>> >>> > >>>>> >>> > >>> >>> > >>> >>> > >>> So, even though we already have the link, and people don't bother >>> > >>> reading, you suggest another wiki page to further complicate their >>> > >>> desire to file bad bugs? We already tell them the recommended way >>> > >>> to >>> > >>> file the bug, if they ignore that, why make it easier to ignore? >>> > >>> >>> > >> >>> > >> The link at the top was added recently: >>> > >> 140        2010-08-07 10:57:04     11547           oCean_ >>> > >>  Mention the no-redirect >>> > >> url at top >>> > >> from the launchpad page oCean_ seems to be a new user, does anyone >>> > >> know >>> > >> him? I don't like the link being at the top either. >>> > >> >>> > >> Also, as I already wrote: the reporting guidelines at the +filebug >>> > >> page >>> > >> originally only required the user to add the application package if >>> > >> possible, the app version and the ubuntu release they're running. >>> > >> Many >>> > >> happily ignored that, so why do you think they would actually stop >>> > >> filing the bug there and click themselves through like a dozen >>> > >> windows >>> > >> for a kernel report? I seriously doubt they would do that. >>> > >> >>> > >> As for needs-packaging. The official documentation for that [1] has >>> > >> a >>> > >> link that uses ?no-redirect and adds the tag to the bug. Why don't >>> > >> people use that? You can file bugs with gpg signed mails too btw >>> > >> which >>> > >> would be another easy way to file those IMO. >>> > >> >>> > > >>> > > Actually add the reference -.- >>> > > >>> > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages >>> > > >>> > >>> > Well, I did not mean to start such a big discussion here; I don't think >>> > the problem is /that/ bad, so I don't think it needs a complex >>> > solution. :) >>> > >>> > To clarify my problem statement, the Reporting Bugs howto just has too >>> > much header material. You have: >>> > >>> > 1) Some BOLD text which catches your eye, possibly unrelated to the >>> > reason you came to the page. >>> > 2) A redundant "Reporting bugs" header, which further emphasizes the >>> > awkwardness of the bold text. >>> > 3) A reasonable intro. >>> > 4) Note 1 -- more distraction. >>> > 5) Note 2 -- and more distraction. >>> > >>> > This is just not user-friendly. A smattering of notes and distractions >>> > just obfuscates the real information on the page and makes it less >>> > useful. Perhaps you don't agree with me, but in both my personal and >>> > professional life I have found this to be true. >>> > >>> > If changing launchpad would be too hard, the idea of an alternative >>> > redirect page makes a lot of sense to me. How about the following >>> > content: >>> > >>> > ------- >>> > Since you've ended up on this page, you were probably trying to file a >>> > bug about Ubuntu in Launchpad. Although filing directly on Launchpad >>> > used to be an acceptable method of reporting a bug, using tools >>> > built-in >>> > to your Ubuntu system is now recommended. Please see >>> > [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for >>> > instructions. >>> > >>> > Thank you for your cooperation. >>> > ------- >>> > >>> > Disagreements welcome, but please explain why this idea would be >>> > inferior to the status quo. Thanks! >>> > >>> > Regards, >>> > David >>> > >>> >>> Somehow, redirecting me to the same page I started on is not good. Why >>> do we have to redirect the user at all. If the page is written that >>> bad, why not suggest a re-write, instead of a re-direct. If they are >>> going to read the new page they are sent to, they will read the page >>> they are already at. >>> >>> - -- >>> Charlie Kravetz >>> Linux Registered User Number 425914          [http://counter.li.org/] >>> Never let anyone steal your DREAM.           [http://keepingdreams.com] >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.10 (GNU/Linux) >>> >>> iQEcBAEBAgAGBQJMhWIRAAoJEFNEIRz9dxbAdHUIAJA/WNWteQgrTwaLhLxk7Axx >>> ARZ0RxmO5WJxDcRtU0nNRW/YNLYhHxV+vjzsGLX/dz8dKoB3NY6lIq5KiHh+lIjK >>> cwTmP8zVBOp4UtcNUlvAs4X2vjXy5CxeeRwO7o5ovRvUAJYJM5bxm5qEEsaVRnvV >>> p3ijrKzmhDO55/yxFEiT43AwfNYNEcKjDxggUWvYzAAheV8rvA4SZjnUOjuvXPZA >>> es8txM2U/uaoXejOnKTj1Kk8AOHZK96cpxxM9CFQuRTxP+8bBjjntRp69/W0ou3h >>> F2l5fTc5I//P9MtpeQ3iOCKIpRp0Xi47/hhrOe+3qVE4tGPkrU9imeMACUEwr64= >>> =f7SD >>> -----END PGP SIGNATURE----- >>> -- >>> 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 > > From ilidrissiamine at gmail.com Tue Sep 7 00:56:47 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Tue, 7 Sep 2010 00:56:47 +0000 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> Message-ID: Thanks a lot for feedback! We could either link to section 5 from section 4, or rename section 4 so it doesn't look like it's the final step. Thanks again, Mohamed Amine IL Idrissi On Tue, Sep 7, 2010 at 12:39 AM, Evan wrote: > On Mon, Sep 6, 2010 at 8:02 PM, Mohamed Amine IL Idrissi > wrote: > > I've set up a prototype page. Please > > visit > https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and > > share your thoughts (especially on the TODO bits). > > Thanks, > > Mohamed Amine IL Idrissi > > I quite like it. I've already made some minor tweaks here and there. > > My biggest question is whether section 5 "Write a Useful Report" > should be before section 4 "File the Bug". I imagine that most people > will run ubuntu-bug in section 4 and finish the whole process before > going to section 5 - at which point it is too late to instruct them on > how to write good reports. Another option would be to merge them > somehow. Thoughts? > > Evan > > > On Mon, Sep 6, 2010 at 9:53 PM, Mohamed Amine IL Idrissi > > wrote: > >> > >> I'm in the process of rewriting the ReportingBugs page. I'll re-post > when > >> I'll have something working. > >> > >> On Mon, Sep 6, 2010 at 9:50 PM, Charlie Kravetz > >> wrote: > >>> > >>> -----BEGIN PGP SIGNED MESSAGE----- > >>> Hash: SHA1 > >>> > >>> On Mon, 06 Sep 2010 17:04:38 -0400 > >>> David Tombs wrote: > >>> > >>> > On 09/01/2010 03:00 PM, Philip Muskovac wrote: > >>> > > On 09/01/2010 08:59 PM, Philip Muskovac wrote: > >>> > >> On 09/01/2010 08:10 PM, Charlie Kravetz wrote: > >>> > >>> On Wed, 1 Sep 2010 17:36:46 +0000 > >>> > >>> Mohammed Amine IL Idrissi wrote: > >>> > >>> > >>> > >>>> People who are not interested in reading text already click the > >>> > >>>> link > >>> > >>>> to file a bug immediately, since there is a link to it in > >>> > >>>> ReportingBugs. Creating another wiki page would reduce the > amount > >>> > >>>> of > >>> > >>>> text people would have to read, without removing the > instructions > >>> > >>>> for > >>> > >>>> those who want to file good bug reports. > >>> > >>>> Adding to this, we could tell them to run "ubuntu-bug " > >>> > >>>> where > >>> > >>>> is found according to Bugs/FindRightPackage, or to run > >>> > >>>> "ubuntu-bug" if they are not sure, and follow the instructions. > >>> > >>> > >>> > >>>> What would be ideal is that the user follow these steps: > >>> > >>>> 1. Run "ubuntu-bug". > >>> > >>>> 2. The current window opens, but with two more options: > >>> > >>>> "Application > >>> > >>>> problem" and "Specific package problem (advanced)". > >>> > >>>> 2a. Choosing "Application problem" will open a window where you > >>> > >>>> can > >>> > >>>> drag-and-drop an application from the menu. > >>> > >>>> 2b. Choosing "Specific package problem" will show a text entry > >>> > >>>> where > >>> > >>>> the user can type the package name. > >>> > >>>> 3. If the user still can't know the specific problem, an alert > >>> > >>>> shows > >>> > >>>> and warns him that filing a bug without a package is not > >>> > >>>> recommended, > >>> > >>>> with a checkbox named: "This bug is about an application that > >>> > >>>> needs > >>> > >>>> packaging". > >>> > >>> > >>> > >>>> Thank you, > >>> > >>>> Mohamed Amine IL Idrissi > >>> > >>> > >>> > >>>> On Wed, Sep 1, 2010 at 5:23 PM, Krzysztof Klimonda > >>> > >>>> wrote: > >>> > >>>>> On Wed, 2010-09-01 at 17:13 +0000, Mohammed Amine IL Idrissi > >>> > >>>>> wrote: > >>> > >>>>>> Maybe we could redirect them to another wiki page that > explains > >>> > >>>>>> that > >>> > >>>>>> this is not the recommended way to report a bug, and then give > >>> > >>>>>> them a > >>> > >>>>>> link to file a bug anyway, and a link to ReportingBugs. > >>> > >>>>> > >>> > >>>>> But that would defeat the purpose of ReportingBug page as most > >>> > >>>>> visitors > >>> > >>>>> wouldn't ever read it but click the link to file a bug > >>> > >>>>> immediately. > >>> > >>>>> People who have problems are not interested in reading text, > they > >>> > >>>>> just > >>> > >>>>> want to get their it fixed. Unfortunately this way they file > low > >>> > >>>>> quality > >>> > >>>>> reports that make our work harder and most of us are not > >>> > >>>>> full-time bug > >>> > >>>>> triagers. We already get more reports we can really deal with > >>> > >>>>> (i.e. > >>> > >>>>> triage and fix in stable release) anyway. > >>> > >>>>> > >>> > >>>>> Cheers, > >>> > >>>>> KK > >>> > >>>>> > >>> > >>>>> -- > >>> > >>>>> Ubuntu-bugsquad mailing list > >>> > >>>>> Ubuntu-bugsquad at lists.ubuntu.com > >>> > >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>> > >>>>> > >>> > >>>>> > >>> > >>> > >>> > >>> > >>> > >>> So, even though we already have the link, and people don't bother > >>> > >>> reading, you suggest another wiki page to further complicate > their > >>> > >>> desire to file bad bugs? We already tell them the recommended way > >>> > >>> to > >>> > >>> file the bug, if they ignore that, why make it easier to ignore? > >>> > >>> > >>> > >> > >>> > >> The link at the top was added recently: > >>> > >> 140 2010-08-07 10:57:04 11547 oCean_ > >>> > >> Mention the no-redirect > >>> > >> url at top > >>> > >> from the launchpad page oCean_ seems to be a new user, does anyone > >>> > >> know > >>> > >> him? I don't like the link being at the top either. > >>> > >> > >>> > >> Also, as I already wrote: the reporting guidelines at the +filebug > >>> > >> page > >>> > >> originally only required the user to add the application package > if > >>> > >> possible, the app version and the ubuntu release they're running. > >>> > >> Many > >>> > >> happily ignored that, so why do you think they would actually stop > >>> > >> filing the bug there and click themselves through like a dozen > >>> > >> windows > >>> > >> for a kernel report? I seriously doubt they would do that. > >>> > >> > >>> > >> As for needs-packaging. The official documentation for that [1] > has > >>> > >> a > >>> > >> link that uses ?no-redirect and adds the tag to the bug. Why don't > >>> > >> people use that? You can file bugs with gpg signed mails too btw > >>> > >> which > >>> > >> would be another easy way to file those IMO. > >>> > >> > >>> > > > >>> > > Actually add the reference -.- > >>> > > > >>> > > [1] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages > >>> > > > >>> > > >>> > Well, I did not mean to start such a big discussion here; I don't > think > >>> > the problem is /that/ bad, so I don't think it needs a complex > >>> > solution. :) > >>> > > >>> > To clarify my problem statement, the Reporting Bugs howto just has > too > >>> > much header material. You have: > >>> > > >>> > 1) Some BOLD text which catches your eye, possibly unrelated to the > >>> > reason you came to the page. > >>> > 2) A redundant "Reporting bugs" header, which further emphasizes the > >>> > awkwardness of the bold text. > >>> > 3) A reasonable intro. > >>> > 4) Note 1 -- more distraction. > >>> > 5) Note 2 -- and more distraction. > >>> > > >>> > This is just not user-friendly. A smattering of notes and > distractions > >>> > just obfuscates the real information on the page and makes it less > >>> > useful. Perhaps you don't agree with me, but in both my personal and > >>> > professional life I have found this to be true. > >>> > > >>> > If changing launchpad would be too hard, the idea of an alternative > >>> > redirect page makes a lot of sense to me. How about the following > >>> > content: > >>> > > >>> > ------- > >>> > Since you've ended up on this page, you were probably trying to file > a > >>> > bug about Ubuntu in Launchpad. Although filing directly on Launchpad > >>> > used to be an acceptable method of reporting a bug, using tools > >>> > built-in > >>> > to your Ubuntu system is now recommended. Please see > >>> > [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] > for > >>> > instructions. > >>> > > >>> > Thank you for your cooperation. > >>> > ------- > >>> > > >>> > Disagreements welcome, but please explain why this idea would be > >>> > inferior to the status quo. Thanks! > >>> > > >>> > Regards, > >>> > David > >>> > > >>> > >>> Somehow, redirecting me to the same page I started on is not good. Why > >>> do we have to redirect the user at all. If the page is written that > >>> bad, why not suggest a re-write, instead of a re-direct. If they are > >>> going to read the new page they are sent to, they will read the page > >>> they are already at. > >>> > >>> - -- > >>> Charlie Kravetz > >>> Linux Registered User Number 425914 [http://counter.li.org/] > >>> Never let anyone steal your DREAM. [http://keepingdreams.com > ] > >>> -----BEGIN PGP SIGNATURE----- > >>> Version: GnuPG v1.4.10 (GNU/Linux) > >>> > >>> iQEcBAEBAgAGBQJMhWIRAAoJEFNEIRz9dxbAdHUIAJA/WNWteQgrTwaLhLxk7Axx > >>> ARZ0RxmO5WJxDcRtU0nNRW/YNLYhHxV+vjzsGLX/dz8dKoB3NY6lIq5KiHh+lIjK > >>> cwTmP8zVBOp4UtcNUlvAs4X2vjXy5CxeeRwO7o5ovRvUAJYJM5bxm5qEEsaVRnvV > >>> p3ijrKzmhDO55/yxFEiT43AwfNYNEcKjDxggUWvYzAAheV8rvA4SZjnUOjuvXPZA > >>> es8txM2U/uaoXejOnKTj1Kk8AOHZK96cpxxM9CFQuRTxP+8bBjjntRp69/W0ou3h > >>> F2l5fTc5I//P9MtpeQ3iOCKIpRp0Xi47/hhrOe+3qVE4tGPkrU9imeMACUEwr64= > >>> =f7SD > >>> -----END PGP SIGNATURE----- > >>> -- > >>> 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 > > > > > > -- > 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 ilidrissiamine at gmail.com Tue Sep 7 01:07:52 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Tue, 7 Sep 2010 01:07:52 +0000 Subject: launchpad +filebug redirect In-Reply-To: <20100906190308.331651af@teamcharliesangels.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> Message-ID: On Tue, Sep 7, 2010 at 1:03 AM, Charlie Kravetz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 7 Sep 2010 00:02:35 +0000 > Mohamed Amine IL Idrissi wrote: > > > I've set up a prototype page. Please visit > > https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and > > share your thoughts (especially on the TODO bits). > > > > Thanks, > > Mohamed Amine IL Idrissi > > > Very nice job on a very difficult page. I would be happy to see it as > it stands. It reads very well. > Thanks :) Two things to consider, though. LTS releases are actually supported for > 5 years, so Ubuntu 6.06, Dapper Drake, is still supported on servers. > Perhaps a note that says something like "Server admins, please see > 'Filing bugs at Launchpad.net'. > I think server admins are actually wary of how to report bugs, especially if they are on a very old (but supported) version. That's just my opinion, though. > Also, firefox in maverick and soon to be in 10.04 (Lucid) will require > users report the bugs directly to mozilla. That should be added as it > actually happens, though. > Yes, I'll add a note on the page later. Thanks again for the feedback, Mohamed Amine IL Idrissi > > - -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJMhY9MAAoJEFNEIRz9dxbAiTcH/AuWXaircMhE1HDVmjTHXz5P > HHf6rWtCcs+/F/ROtSNoC7oRJqb5rCZFrfNCSjM1dZOAgT0mcvwNg/TQLNljty8P > LxrrCIS0imIFZzBnZZ3pOo743RCn0GVuzngAuroDujuqBC+bkDw03C/h4b65Qc5+ > 5XgfzOd5GLc5ort1hQ4oIcbyrWdHacWoirJdbwYZ+LC/Z6Qf561u93rhKQUejUiL > rJgKMyD0UXN2B2ZaQNOd16XeBTo3HzPrOzfxGEmmHaDxMW8xRlsLGms0ktXJF/Sh > 2N2vPRVLUXaDLmFm07jORxy0VPSDqvjnA6i3omEnOc5ryBR32bz8hoRj6oX7EUA= > =mdPp > -----END PGP SIGNATURE----- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikem2314 at gmail.com Tue Sep 7 01:28:02 2010 From: mikem2314 at gmail.com (Mike Metcalf) Date: Mon, 6 Sep 2010 21:28:02 -0400 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> Message-ID: <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> Nice page so far, informative and a good flow. The only thing I had to add Charlie already covered, about reporting bugs with firefox. Nice job! -Mike Metcalf Sent from my iPhone On Sep 6, 2010, at 9:07 PM, Mohamed Amine IL Idrissi wrote: > On Tue, Sep 7, 2010 at 1:03 AM, Charlie Kravetz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 7 Sep 2010 00:02:35 +0000 > Mohamed Amine IL Idrissi wrote: > > > I've set up a prototype page. Please visit > > https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and > > share your thoughts (especially on the TODO bits). > > > > Thanks, > > Mohamed Amine IL Idrissi > > > Very nice job on a very difficult page. I would be happy to see it as > it stands. It reads very well. > > Thanks :) > > > Two things to consider, though. LTS releases are actually supported for > 5 years, so Ubuntu 6.06, Dapper Drake, is still supported on servers. > Perhaps a note that says something like "Server admins, please see > 'Filing bugs at Launchpad.net'. > > I think server admins are actually wary of how to report bugs, especially if they are on a very old (but supported) version. That's just my opinion, though. > > Also, firefox in maverick and soon to be in 10.04 (Lucid) will require > users report the bugs directly to mozilla. That should be added as it > actually happens, though. > > Yes, I'll add a note on the page later. > > Thanks again for the feedback, > Mohamed Amine IL Idrissi > > - -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJMhY9MAAoJEFNEIRz9dxbAiTcH/AuWXaircMhE1HDVmjTHXz5P > HHf6rWtCcs+/F/ROtSNoC7oRJqb5rCZFrfNCSjM1dZOAgT0mcvwNg/TQLNljty8P > LxrrCIS0imIFZzBnZZ3pOo743RCn0GVuzngAuroDujuqBC+bkDw03C/h4b65Qc5+ > 5XgfzOd5GLc5ort1hQ4oIcbyrWdHacWoirJdbwYZ+LC/Z6Qf561u93rhKQUejUiL > rJgKMyD0UXN2B2ZaQNOd16XeBTo3HzPrOzfxGEmmHaDxMW8xRlsLGms0ktXJF/Sh > 2N2vPRVLUXaDLmFm07jORxy0VPSDqvjnA6i3omEnOc5ryBR32bz8hoRj6oX7EUA= > =mdPp > -----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 rohangarg at ubuntu.com Tue Sep 7 04:17:27 2010 From: rohangarg at ubuntu.com (Rohan Garg) Date: Tue, 7 Sep 2010 09:47:27 +0530 Subject: Bug Kubuntu 10.04 In-Reply-To: <4C8370C8.3060806@gmx.net> References: <4C8370C8.3060806@gmx.net> Message-ID: Hi Could you try switching to the aptcc backend and try again? #kubuntu-devel might be able to help in this regard Regards Rohan Garg On Sun, Sep 5, 2010 at 3:58 PM, Matthias Schneider wrote: > Hi, > > while trying to update my software in the KPackageKit I received the > following error: > > Error Type: > Error Value: coercing to Unicode: need string or buffer, > exceptions.SystemError found > File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2216, in > main() > File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2213, in main > run(args, options.single) > File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2175, in run > backend.dispatcher(args) > File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 699, in > dispatcher > self.dispatch_command(args[0], args[1:]) > File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 606, in > dispatch_command > self.refresh_cache(force) > File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 202, in > _locked_cache > func(*args, **kwargs) > File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 1498, in > refresh_cache > format_string(error.message)) > File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 723, in > format_string > txt = unicode(text, encoding, errors='replace') > > Can You maybe explain me how I can solve this problem? > > > Yours > > Matthias Schneider > -- > > Matthias Schneider > m.schneider91 at gmx.net > > -- > 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 Tue Sep 7 13:46:50 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 07 Sep 2010 13:46:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20100907134650.23899.86429@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=235&rev2=236 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100909| apt]] || hugday-20100909 || || [[UbuntuBugDay/20100826| Ubuntu Translations]] || hugday-20100826 || || [[UbuntuBugDay/20100819| Banshee]] || hugday-20100819 || || [[UbuntuBugDay/20100715| Pidgin]] || hugday-20100715 || From cjk at teamcharliesangels.com Tue Sep 7 16:25:59 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Tue, 7 Sep 2010 10:25:59 -0600 Subject: Announcing the Next Ubuntu Bug Day! - 2010-09-09 Message-ID: <20100907102559.270249a2@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* apt! * 100 New bugs need a hug * 43 Incomplete bugs need a status check * 100 Confirmed bugs need a review apt is not the biggest name in packages, but it sure is important to keep your system up-to-date. It gets involved whenever we use Synaptic Package Manager, apt-get, and Software Center, to name a few places. Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday, 2010-09-09 * http://wiki.ubuntu.com/UbuntuBugDay/20100909 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, head to http://wiki.ubuntu.com/Bugs Have a nice day, charlie-tca [From the BugSquad] - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMhmeXAAoJEFNEIRz9dxbAvpoIAI/QPkAAlc4P3egH9fUbGRoz J6cjiuBsBZhuKZQfddi/971y19YLWgR8/vENTPO1ff1u9b625lSDMEE5pfils2rg iBCrjNFAbtYMXQ+qnHHrrANBwquzPlHcNGAUzncjNAJPk4EI6RpH8ver6CuIL+Y3 6cSsmbDizi40c3wT0mvrZsf0EMxCS1lJEn4A6pg97gt5EmMEAIC7LgUTg45Lfg3S T1Dqncy2rIfzLYGH2u2Le56SyIqoGctdnsNrNi/Ux1/c028SWgEe7IL0oeiJSvrZ tiRQOfJU2drSDKVeOBKt6rbFvyoET54g17EICFxWjk97X4BW6f0SyK7T8SzadVo= =560R -----END PGP SIGNATURE----- From ilidrissiamine at gmail.com Wed Sep 8 13:13:29 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Wed, 8 Sep 2010 13:13:29 +0000 Subject: launchpad +filebug redirect In-Reply-To: <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> Message-ID: Thanks for your feedback! I have two remaining questions: - Is there a guide about reporting bugs in upstream Mozilla that we can link to? - Apart from that, do you think this is ready to replace the current ReportingBugs page? If there are any issues you notice, please tell me. Thank you, Mohamed Amine IL Idrissi On Tue, Sep 7, 2010 at 1:28 AM, Mike Metcalf wrote: > Nice page so far, informative and a good flow. The only thing I had to add > Charlie already covered, about reporting bugs with firefox. Nice job! > > -Mike Metcalf > > Sent from my iPhone > > On Sep 6, 2010, at 9:07 PM, Mohamed Amine IL Idrissi < > ilidrissiamine at gmail.com> wrote: > > On Tue, Sep 7, 2010 at 1:03 AM, Charlie Kravetz < > cjk at teamcharliesangels.com> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Tue, 7 Sep 2010 00:02:35 +0000 >> Mohamed Amine IL Idrissi < >> ilidrissiamine at gmail.com> wrote: >> >> > I've set up a prototype page. Please visit >> > >> https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate and >> > share your thoughts (especially on the TODO bits). >> > >> > Thanks, >> > Mohamed Amine IL Idrissi >> > >> > Very nice job on a very difficult page. I would be happy to see it as >> it stands. It reads very well. >> > > Thanks :) > > > Two things to consider, though. LTS releases are actually supported for >> 5 years, so Ubuntu 6.06, Dapper Drake, is still supported on servers. >> Perhaps a note that says something like "Server admins, please see >> 'Filing bugs at Launchpad.net'. >> > > I think server admins are actually wary of how to report bugs, especially > if they are on a very old (but supported) version. That's just my opinion, > though. > > >> Also, firefox in maverick and soon to be in 10.04 (Lucid) will require >> users report the bugs directly to mozilla. That should be added as it >> actually happens, though. >> > > Yes, I'll add a note on the page later. > > Thanks again for the feedback, > Mohamed Amine IL Idrissi > >> >> - -- >> Charlie Kravetz >> Linux Registered User Number 425914 [ >> http://counter.li.org/] >> Never let anyone steal your DREAM. [ >> http://keepingdreams.com] >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.10 (GNU/Linux) >> >> iQEcBAEBAgAGBQJMhY9MAAoJEFNEIRz9dxbAiTcH/AuWXaircMhE1HDVmjTHXz5P >> HHf6rWtCcs+/F/ROtSNoC7oRJqb5rCZFrfNCSjM1dZOAgT0mcvwNg/TQLNljty8P >> LxrrCIS0imIFZzBnZZ3pOo743RCn0GVuzngAuroDujuqBC+bkDw03C/h4b65Qc5+ >> 5XgfzOd5GLc5ort1hQ4oIcbyrWdHacWoirJdbwYZ+LC/Z6Qf561u93rhKQUejUiL >> rJgKMyD0UXN2B2ZaQNOd16XeBTo3HzPrOzfxGEmmHaDxMW8xRlsLGms0ktXJF/Sh >> 2N2vPRVLUXaDLmFm07jORxy0VPSDqvjnA6i3omEnOc5ryBR32bz8hoRj6oX7EUA= >> =mdPp >> -----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 hggdh2 at ubuntu.com Wed Sep 8 14:25:36 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 8 Sep 2010 09:25:36 -0500 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> Message-ID: <20100908092536.0f291572@xango2> On Wed, 8 Sep 2010 13:13:29 +0000 Mohamed Amine IL Idrissi wrote: > I have two remaining questions: > - Is there a guide about reporting bugs in upstream Mozilla that we > can link to? Not sure about that, probably Micah can answer. > - Apart from that, do you think this is ready to replace the current > ReportingBugs page? If there are any issues you notice, please tell > me. I suggest waiting a bit more, to get more feedback. I like what I see, BTW. Two small changes: * added a caveat for sound/X/kernel bugs: better to open a new bug than to comment on an existing one. * I went ahead and swapped (4) and (5). Of course, this will not make people _read_ how to write an useful report _before_ opening the bug, but... hope springs eternal. Thank you for this work! ..C.. -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From pedro at ubuntu.com Wed Sep 8 14:52:17 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Wed, 08 Sep 2010 10:52:17 -0400 Subject: Bugsquad Meeting Reminder - Tuesday 14th September 2010 Message-ID: <1283957537.2025.5.camel@wombat> Hello Folks, Just a reminder that the Tuesday 14th of September 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. * Regression tags and workflow. * Review of the ReportingBugsAlternate page. * 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 arche1 at gmx.at Wed Sep 8 17:59:06 2010 From: arche1 at gmx.at (Noah Essl) Date: Wed, 08 Sep 2010 19:59:06 +0200 Subject: Bug from GNOME maybe reffered to bug from UBUNTU Message-ID: <20100908175906.108170@gmx.net> Dear Bugsquad, I reportet a bug to bugzilla.gnome.org and was told that this might not be a bug of GNOME but of UBUNTU and that I should contakt you. https://bugzilla.gnome.org/show_bug.cgi?id=628751 Would you mind reading through the comments there, and tell me how to continue the bug report? I do not know if I can report a bug caused by a application in GNOME via Launchpad to the UBUNTU buglist. Yours sincerely, Noah Essl From noreply at ubuntu.com Wed Sep 8 18:04:19 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 08 Sep 2010 18:04:19 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_kklimonda?= Message-ID: <20100908180419.17442.843@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 kklimonda: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=133&rev2=134 The comment on the change is: Fix a link to untriaged bugs section ------------------------------------------------------------------------------ Every bug report is a conversation with the reporter. The first contact any reporter usually has with the Ubuntu community is through a bug triager, who tries to put together a complete bug report. It's very important that we give a good impression, so please be polite and try to use your best English. - Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[#untriaged|Untriaged bugs]] explains where to find them. + Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]] explains where to find them. <> ||{{attachment:bugsquad.png}}||'''Bug Types'''|| From macoafi at gmail.com Wed Sep 8 18:29:11 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 8 Sep 2010 14:29:11 -0400 Subject: Bug from GNOME maybe reffered to bug from UBUNTU In-Reply-To: <20100908175906.108170@gmx.net> References: <20100908175906.108170@gmx.net> Message-ID: On Wed, Sep 8, 2010 at 1:59 PM, Noah Essl wrote: > Dear Bugsquad, > > I reportet a bug to bugzilla.gnome.org and was told that this might not be a bug of GNOME but of UBUNTU and that I should contakt you. > > https://bugzilla.gnome.org/show_bug.cgi?id=628751 > > Would you mind reading through the comments there, and tell me how to continue the bug report? > I do not know if I can report a bug caused by a application in GNOME via Launchpad to the UBUNTU buglist. To file a bug in Ubuntu against any package, just run: ubuntu-bug So like: ubuntu-bug gnome-bluetooth Do you still have the .crash from this in your /var/crash/ directory? If so, Launchpad can automatically perform a retrace with debug symbols on it. -- Mackenzie Morgan From maghajan at gmail.com Wed Sep 8 22:15:00 2010 From: maghajan at gmail.com (Matthew Aghajanian) Date: Wed, 8 Sep 2010 17:15:00 -0500 Subject: ubuntu 10.10 beta amd64, error during install Message-ID: Hi, i was installing ubuntu 10.10 beta x64 in VirtualBox with a Windows 7 host and during install an error occurred. It told me to submit an error report, not sure where to submit it or how. Attached are /var/log/syslog and partman. -------------- next part -------------- A non-text attachment was scrubbed... Name: partman Type: application/octet-stream Size: 129347 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: syslog Type: application/octet-stream Size: 127944 bytes Desc: not available URL: From pedro at ubuntu.com Thu Sep 9 14:12:07 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Thu, 09 Sep 2010 10:12:07 -0400 Subject: [Fwd: QA Meeting Summary - 2010-09-08] Message-ID: <1284041527.1856.5.camel@wombat> FYI. -------------- next part -------------- An embedded message was scrubbed... From: Jean-Baptiste Lallement Subject: QA Meeting Summary - 2010-09-08 Date: Thu, 09 Sep 2010 10:17:49 +0200 Size: 5418 URL: From cyan.spam at gmail.com Fri Sep 10 18:28:11 2010 From: cyan.spam at gmail.com (David Tombs) Date: Fri, 10 Sep 2010 14:28:11 -0400 Subject: launchpad +filebug redirect In-Reply-To: <20100908092536.0f291572@xango2> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> <20100908092536.0f291572@xango2> Message-ID: <4C8A78BB.7010300@gmail.com> On 09/08/2010 10:25 AM, C de-Avillez wrote: > * I went ahead and swapped (4) and (5). Of course, this will not make > people _read_ how to write an useful report _before_ opening the > bug, but... hope springs eternal. Isn't this out of order now, though? I agree with your hope, but now you get information on writing the description before you even see the screen in front of you. Great job, though, Mohammed. I think it's much better. What's the plan for alternate instructions for older versions of Ubuntu? Thanks for the hard work, David From ilidrissiamine at gmail.com Fri Sep 10 20:17:52 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Fri, 10 Sep 2010 20:17:52 +0000 Subject: launchpad +filebug redirect In-Reply-To: <4C8A78BB.7010300@gmail.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> <20100908092536.0f291572@xango2> <4C8A78BB.7010300@gmail.com> Message-ID: It's great that it pleases you! For older versions of Ubuntu, I simply removed the instructions pertaining to them because they were just plain confusing: for Ubuntu 8.10 and later, we have a set of instructions ; for Ubuntu 8.04 to 9.04, we have another set of instructions (isn't 8.10 and 9.04 part of the first set of instructions) ; and for Ubuntu 9.10 and later, we have the same first set of instructions! Besides, there is the issue of EOL: 8.10 is EOL, 9.04 will be in one month, and 8.04 in seven months (the last one receives mostly security updates). That's why I removed these instructions, though you may put them there again if you disagree. Anyway, I've just updated the page to include a guide through Launchpad's web interface. Can you please give your feedback (besides Brian Murray's one, who already stated this was a bad idea)? It would be of course great if someone could fix the grammar ; I'm not great with it :( Thank you, Mohamed Amine IL Idrissi On Fri, Sep 10, 2010 at 6:28 PM, David Tombs wrote: > On 09/08/2010 10:25 AM, C de-Avillez wrote: > > > * I went ahead and swapped (4) and (5). Of course, this will not make > > people _read_ how to write an useful report _before_ opening the > > bug, but... hope springs eternal. > > Isn't this out of order now, though? I agree with your hope, but now you > get information on writing the description before you even see the > screen in front of you. > > Great job, though, Mohammed. I think it's much better. What's the plan > for alternate instructions for older versions of Ubuntu? > > Thanks for the hard work, > David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From macoafi at gmail.com Sat Sep 11 04:55:57 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sat, 11 Sep 2010 00:55:57 -0400 Subject: launchpad +filebug redirect In-Reply-To: References: <4C77F7CE.2030404@gmail.com> <4C8A78BB.7010300@gmail.com> Message-ID: <201009110055.58121.macoafi@gmail.com> On Friday, September 10, 2010 04:17:52 pm Mohamed Amine IL Idrissi wrote: > Besides, there is the issue of EOL: 8.10 is EOL, 9.04 will be in one month, > and 8.04 in seven months (the last one receives mostly security updates). Uh...maybe on the desktop, but 8.04's going to be around til April 2013 on the server, and ubuntu-bug exists there too. Also, regarding out-of-order: make that step "think about how to describe.... and when you're ready, do foo" maybe? -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com From javiromero_mx at hotmail.com Sat Sep 11 06:07:52 2010 From: javiromero_mx at hotmail.com (Javier Romero) Date: Sat, 11 Sep 2010 03:07:52 -0300 Subject: I am new in the list. Message-ID: Hi, My name is Javier and my e-mail is: javiromero_mx at hotmail.com Thanks for your attention and hope, I can be useful. With best regards, Xavi. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Sat Sep 11 15:23:05 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sat, 11 Sep 2010 11:23:05 -0400 Subject: I am new in the list. In-Reply-To: References: Message-ID: <4C8B9ED9.4090504@gmail.com> Welcome to the team, Javier. :) Please let us know if you have any questions. David On 09/11/2010 02:07 AM, Javier Romero wrote: > Hi, My name is Javier and my e-mail is: javiromero_mx at hotmail.com > > Thanks for your attention and hope, I can be useful. > With best regards, > > Xavi. > From rahul21sep at gmail.com Sat Sep 11 21:29:48 2010 From: rahul21sep at gmail.com (Rahul Sharma) Date: Sat, 11 Sep 2010 17:29:48 -0400 Subject: I am new in the list. In-Reply-To: <4C8B9ED9.4090504@gmail.com> References: <4C8B9ED9.4090504@gmail.com> Message-ID: Hi All, I have recently joined the bug-squad community as well. I have been a tester on web and client-server applications for 4 yrs. Look forward to working with the team. Regards, Rahul On Sat, Sep 11, 2010 at 11:23 AM, David Tombs wrote: > Welcome to the team, Javier. :) Please let us know if you have any > questions. > > David > > On 09/11/2010 02:07 AM, Javier Romero wrote: >> Hi, My name is Javier and my e-mail is: javiromero_mx at hotmail.com >> >> Thanks for your attention and hope, I can be useful. >> With best regards, >> >> Xavi. >> > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From noreply at ubuntu.com Sat Sep 11 07:08:41 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 11 Sep 2010 07:08:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_diw?= =?utf-8?q?ic?= Message-ID: <20100911070841.22552.98244@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=60&rev2=61 The comment on the change is: Removed section about hardware detection in favour of linking to such an article. ------------------------------------------------------------------------------ * 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. + [[Audio/SameHardware|Here's an article]] of how to determine whether you have the same hardware as the original bug reporter. - === 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 hggdh2 at ubuntu.com Sun Sep 12 00:30:12 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sat, 11 Sep 2010 19:30:12 -0500 Subject: launchpad +filebug redirect In-Reply-To: <4C8A78BB.7010300@gmail.com> References: <4C77F7CE.2030404@gmail.com> <20100901170140.GE2636@murraytwins.com> <1283361782.13048.25.camel@blue> <20100901121052.3a85c500@teamcharliesangels.com> <4C7EA274.3040904@gmx.net> <4C7EA2CD.6050701@gmx.net> <4C855766.9070908@gmail.com> <20100906155009.53b70a5d@teamcharliesangels.com> <20100906190308.331651af@teamcharliesangels.com> <4948BD92-68B9-4704-A929-E7BD5136261B@gmail.com> <20100908092536.0f291572@xango2> <4C8A78BB.7010300@gmail.com> Message-ID: <20100911193012.62c1ea16@xango2> On Fri, 10 Sep 2010 14:28:11 -0400 David Tombs wrote: > On 09/08/2010 10:25 AM, C de-Avillez wrote: > > > * I went ahead and swapped (4) and (5). Of course, this will not > > make people _read_ how to write an useful report _before_ opening > > the bug, but... hope springs eternal. > > Isn't this out of order now, though? I agree with your hope, but now > you get information on writing the description before you even see > the screen in front of you. Sort of, I agree. But it is, I think, better to at least have an idea of what to do _before_ you have a chance of actually doing it. -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From flipefr at gmail.com Sun Sep 12 12:06:11 2010 From: flipefr at gmail.com (Felipe Franco) Date: Sun, 12 Sep 2010 14:06:11 +0200 Subject: I am new in the list Message-ID: Hi everybody My name is Felipe and i am new in the list, my email is flipefr at gmail.com. I am waiting a mentor to know how to start. Can anybody tell me where to begin. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Sun Sep 12 19:01:28 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 12 Sep 2010 15:01:28 -0400 Subject: ubuntu 10.10 beta amd64, error during install In-Reply-To: References: Message-ID: <4C8D2388.7070308@gmail.com> Hi Matthew, The best thing to do would be to run the Live CD in VirtualBox and then run "ubuntu-bug ubiquity" using Alt+F2. Make sure to attach your syslog file to the bug report once ubuntu-bug creates it. Thanks! David On 09/08/2010 06:15 PM, Matthew Aghajanian wrote: > Hi, i was installing ubuntu 10.10 beta x64 in VirtualBox with a > Windows 7 host and during install an error occurred. It told me to > submit an error report, not sure where to submit it or how. Attached > are /var/log/syslog and partman. > From cyan.spam at gmail.com Sun Sep 12 21:28:04 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 12 Sep 2010 17:28:04 -0400 Subject: I am new in the list. In-Reply-To: References: , <4C8B9ED9.4090504@gmail.com> Message-ID: <4C8D45E4.7020000@gmail.com> On 09/11/2010 10:43 PM, Javier Romero wrote: > */_Dear David:_/* > */__/* > Thanks for your welcome and your kind attention. > First of all I´ll present myself, as you know my name is Javier and > I live in Argetina. > I´am 38 years old, married, and work as Electronic Technician repairing > Computers since I was 18. > Now working in a NETWORK OPERATIONS CENTER of an ISP form here > as Servers administrator, all of them working on a Linux OS. > Joined the Team as I would like to help others, I not a Linux expert, > but perhaps think can be useful for the Team. > Questions......yes....how can I help?....and where can start doing > this?.....can I contact you via IRC to guide me? > Again, thanks for your atenttion David. > Best regards, > Hi Javier (and all the other new folks), Great, I think you'll definitely be able to help! The basic guide for how to get involved is it , which you may have read already. Probably the best way to get started would be finding a mentor. See the instructions at for how to do that. If you'd rather just dive in instead of having a mentor, just make sure you have read the How To Triage guide[1] and you can start triaging bugs. Of course, you'll need to pick a set of bugs to work on. Two suggestions I would have are bugs without a package[2] or hug days[3]. For any questions while doing triaging, just ask in the #ubuntu-bugs channel. Hope it helps, and thank _you_ for the help, David [1] https://wiki.ubuntu.com/Bugs/HowToTriage [2] [3] https://wiki.ubuntu.com/UbuntuBugDay/20100909 From cyan.spam at gmail.com Sun Sep 12 21:31:45 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 12 Sep 2010 17:31:45 -0400 Subject: launchpad +filebug redirect In-Reply-To: <201009110055.58121.macoafi@gmail.com> References: <4C77F7CE.2030404@gmail.com> <4C8A78BB.7010300@gmail.com> <201009110055.58121.macoafi@gmail.com> Message-ID: <4C8D46C1.9@gmail.com> On 09/11/2010 12:55 AM, Mackenzie Morgan wrote: > On Friday, September 10, 2010 04:17:52 pm Mohamed Amine IL Idrissi wrote: >> Besides, there is the issue of EOL: 8.10 is EOL, 9.04 will be in one month, >> and 8.04 in seven months (the last one receives mostly security updates). > > Uh...maybe on the desktop, but 8.04's going to be around til April 2013 on the > server, and ubuntu-bug exists there too. Well, everyone makes mistakes. My suggestion for the alternate versions would be to have the changes inline instead of having different sections for each version. There's not that much difference between 8.04 and 10.04 here. I'll try to implement this during the week if I get a chance. David From noreply at ubuntu.com Sun Sep 12 23:55:59 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 12 Sep 2010 23:55:59 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_cyan-spam?= Message-ID: <20100912235559.16196.32904@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/HowToTriage?action=diff&rev1=134&rev2=135 The comment on the change is: add exceptions to normal triaging process ------------------------------------------------------------------------------ Below are some common actions you will perform while Triaging. The [[https://launchpad.net/launchpad-gm-scripts |Launchpad Greasemonkey scripts]] can be a great time-saver while performing the below actions! + /!\ Please note that some teams have their own policies on triaging, see: + * [[Kernel/BugTriage]] + * [[X/Triaging]] + == Confirming == The 'Confirmed' status is used when it is certain the bug exists. If the bug adheres to '''ANY''' of the following criteria it can be considered confirmed: From alonso1290 at live.com Mon Sep 13 02:03:48 2010 From: alonso1290 at live.com (Alonso) Date: Sun, 12 Sep 2010 19:03:48 -0700 Subject: Netbook edition Message-ID: I have a Dell mini 10 with gma500 graphics. Upon startup and booting, nothing apears only the wallpaper and that is all. Apart from a cursor with an "x", that is all that is shown after boot up. From noreply at ubuntu.com Mon Sep 13 12:36:58 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 13 Sep 2010 12:36:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20100913123658.11442.39754@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=236&rev2=237 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100914| upgrades]] || hugday-20100914 || || [[UbuntuBugDay/20100909| apt]] || hugday-20100909 || || [[UbuntuBugDay/20100826| Ubuntu Translations]] || hugday-20100826 || || [[UbuntuBugDay/20100819| Banshee]] || hugday-20100819 || From jean-baptiste at ubuntu.com Mon Sep 13 13:29:35 2010 From: jean-baptiste at ubuntu.com (Jean-Baptiste Lallement) Date: Mon, 13 Sep 2010 15:29:35 +0200 Subject: Announcing the Next Ubuntu Bug Day! - September 14th 2010 Message-ID: <4C8E273F.7010304@ubuntu.com> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* upgrade bugs! * 166 package installation bugs need a hug * 49 new bugs in update-manager need a hug too Bookmark it, add it to your calendars, turn over those egg-timers! * Tuesday 14th September 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100914 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, head to http://wiki.ubuntu.com/Bugs Have a nice day, Jibel >From the BugSquad From macoafi at gmail.com Mon Sep 13 16:12:01 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Mon, 13 Sep 2010 12:12:01 -0400 Subject: Netbook edition In-Reply-To: References: Message-ID: On Sun, Sep 12, 2010 at 10:03 PM, Alonso wrote: > I have a Dell mini 10 with gma500 graphics. Upon startup and booting, > nothing apears only the wallpaper and that is all. Apart from a cursor > with an "x", that is all that is shown after boot up. Sounds like a failsafe login. On the login screen try choosing a different option in the Session menu. If none of the options in there work, report a bug. To do that, you can hit ctrl+alt+f1 to reach a terminal, then: ubuntu-bug -s display -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo From asbjoerngabrielsen at gmail.com Tue Sep 14 14:33:53 2010 From: asbjoerngabrielsen at gmail.com (=?ISO-8859-1?Q?Asbj=F8rn_Gabrielsen?=) Date: Tue, 14 Sep 2010 16:33:53 +0200 Subject: faulty driver rt2870sta Message-ID: <4C8F87D1.5010707@gmail.com> Hi I've come across a problem with the Ralink RT2870 (rt2870sta) wifi driver in lucid. My adapter is wrongly recognized as an rt2800 chipset and lucid loads the rt2800usb driver, instead of the rt2870sta. The 2800-driver doesn't work with my adapter. After 13 hours of googling and trying different approaches, I've got the adapter to work. I had to blacklist the rt2800-driver and download the latest driver from the Ralink website. I then had to modify the driver's device list for the new driver to include my adaptor and the config.mk file to activate WPA encryption. This should be an easy fix for the maverick release. The new driver is found here: http://www.ralinktech.com/support.php?s=2 (RT2870 chipset) The missing device in the list (/common/rtusb_dev_id.c) is the Gigabyte AirCruiser N300, GN-WB31N-RH, usb id 1044:800C WPA-support can be activated in the file /os/linux/config.mk Best regards Asbjørn Gabrielsen Oslo, Norway From cjk at teamcharliesangels.com Tue Sep 14 21:11:37 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Tue, 14 Sep 2010 15:11:37 -0600 Subject: Announcing the Next Ubuntu Bug Day! - 2010-09-16 Message-ID: <20100914151137.3485124c@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow Ubuntu Triagers! A second chance to help this week! We have plenty to do, so let's all get together and help out. This week's Bug Day target is *drum roll please* Brasero! * 38 New bugs need a hug * 99 Incomplete bugs need a status check * 31 Confirmed bugs need a review Brasero is yet another application to burn CD/DVD for the gnome desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly. Bookmark it, add it to your calendars, turn over those egg-timers! * 2010-09-16 * http://wiki.ubuntu.com/UbuntuBugDay/20100916 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, head to http://wiki.ubuntu.com/Bugs Have a nice day, charlie-tca [From the BugSquad] - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMj+UJAAoJEFNEIRz9dxbAh6QH+wcECBJVP1Vxk4VhqY4dvo45 iHhun5VA252YgdjAO32ddN+pG6L8a/K6sGiWHuybZWczJP+AnpjsWHyIwIjQeQyK Upios15vYCrSKTUe7dtBzG/dHSF5w5m35V5LrxBKnW/LlT8EBi+56lRyNB2GcQl3 h/nxiAD2ATcMNzjtntCUkqP1blFnsLIZz3WyhmSlX/5woXDEPZoET3AW/nEbbdrs Iq/sDD5qMmfvvlhDltrUSPUaY6qoUfbmTPwNZfOf8l831GLQlz/2eVJ4JQfldKQE 3lL5XICLZPXj7bp2ol3gy+VXQgHTEeYqD6Ef+xdowYMyLU0lLxsZMmPnRZgj0Nw= =qrpS -----END PGP SIGNATURE----- From brian at ubuntu.com Tue Sep 14 21:57:27 2010 From: brian at ubuntu.com (Brian Murray) Date: Tue, 14 Sep 2010 14:57:27 -0700 Subject: Tool to help forwarding bugs to Debian Message-ID: <20100914215727.GA2958@murraytwins.com> I've written a python script[1] to facilitate forwarding bugs from Launchpad to the Debian bug tracking system. The script uses launchpadlib to gather some information about the existing Ubuntu bug report and then uses reportbug, which is part of the reportbug package, to create a properly formatted email for sending to the Debian bug tracker. Keep in mind that not every Ubuntu bug report should be forwarded to Debian so use this script judiciously. And of course don't forget to link those forwarded bugs! You can find this script in the ubuntu-qa-tools bzr branch. [1] http://bazaar.launchpad.net/%7Eubuntu-bugcontrol/ubuntu-qa-tools/master/annotate/head%3A/launchpadlib-scripts/forward-bug-to-debian.py -- 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 brian at ubuntu.com Wed Sep 15 22:25:00 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 15 Sep 2010 15:25:00 -0700 Subject: Launchpad Greasemonkey Scripts in Chromium Message-ID: <20100915222500.GE2958@murraytwins.com> In case you don't follow my blog regularly, for which you should be ashamed ;-) , I've put some work into getting the Launchpad Greasemonkey Scripts working in Chromium. The full details can be found in my posting[1]. Anyway, they should all work, aside of loading standard responses from the xml file, in Chromium and currently must be installed on an individual basis. [1] http://www.murraytwins.com/blog/?p=89 I hope you find this useful! -- 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 brian at ubuntu.com Wed Sep 15 22:42:08 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 15 Sep 2010 15:42:08 -0700 Subject: Imported Bug Comments Message-ID: <20100915224208.GF2958@murraytwins.com> Launchpad has had the ability to display bug comments from upstream bug trackers for some time now but it only works with some upstreams. I thought it would be helpful to have a list of the Ubuntu packages in Launchpad that are displaying bug comments from upstream bug trackers so we can focus on forwarding these package's bugs upstream and adding the bug watches. If you'd like an example of what I am talking about see http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) bug task linked to an upstream Wine bug report and the comments from the upstream bug tracker appearing in-line. So if we were to make a list of packages it'd include: wine1.2 wine thunderbird firefox What else? I am asking as this is rather hard to determine from Launchpad itself - at least as far as I can tell. You can find bug mail about imported comments by looking for mail from "Bug Watch Updater" and with the body "Launchpad has imported" some number "comments from the remote bug". When I was filtering "Launchpad has imported" returned no false positives. I think posting to the list is a good way to build an initial list, as it'll help people learn about the packages, and then we can make a wiki page with them. 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 brian at ubuntu.com Wed Sep 15 22:44:43 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 15 Sep 2010 15:44:43 -0700 Subject: Imported Bug Comments In-Reply-To: <20100915224208.GF2958@murraytwins.com> References: <20100915224208.GF2958@murraytwins.com> Message-ID: <20100915224443.GG2958@murraytwins.com> On Wed, Sep 15, 2010 at 03:42:08PM -0700, Brian Murray wrote: > Launchpad has had the ability to display bug comments from upstream bug > trackers for some time now but it only works with some upstreams. I > thought it would be helpful to have a list of the Ubuntu packages in > Launchpad that are displaying bug comments from upstream bug trackers so > we can focus on forwarding these package's bugs upstream and adding the > bug watches. > > If you'd like an example of what I am talking about see > http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) > bug task linked to an upstream Wine bug report and the comments from the > upstream bug tracker appearing in-line. > > So if we were to make a list of packages it'd include: > > wine1.2 > wine > thunderbird > firefox xserver-xorg-video-intel Missed one! -- 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 no-reply at dropboxmail.com Thu Sep 16 06:25:03 2010 From: no-reply at dropboxmail.com (Dropbox) Date: Thu, 16 Sep 2010 06:25:03 +0000 Subject: Flipe Fr invited you to Dropbox Message-ID: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> Flipe Fr wants you to use Dropbox to sync and share files online and across computers. Get started here: http://www.dropbox.com/link/20.KTqFJu0e5e/NjM0MTg2OTg1Nw - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/0d1e23c4df8c/ubuntu-bugsquad%40lists.ubuntu.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From flyingstar16 at gmail.com Thu Sep 16 06:29:56 2010 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Thu, 16 Sep 2010 08:29:56 +0200 Subject: Flipe Fr invited you to Dropbox In-Reply-To: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> Message-ID: I cannot really believe this. On Thu, Sep 16, 2010 at 08:25, Dropbox wrote: > [cut] > -- > 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 ara at ubuntu.com Thu Sep 16 07:59:37 2010 From: ara at ubuntu.com (Ara Pulido) Date: Thu, 16 Sep 2010 09:59:37 +0200 Subject: Imported Bug Comments In-Reply-To: <20100915224208.GF2958@murraytwins.com> References: <20100915224208.GF2958@murraytwins.com> Message-ID: <4C91CE69.2080606@ubuntu.com> Hello all, On 16/09/10 00:42, Brian Murray wrote: > Launchpad has had the ability to display bug comments from upstream bug > trackers for some time now but it only works with some upstreams. I > thought it would be helpful to have a list of the Ubuntu packages in > Launchpad that are displaying bug comments from upstream bug trackers so > we can focus on forwarding these package's bugs upstream and adding the > bug watches. > > If you'd like an example of what I am talking about see > http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) > bug task linked to an upstream Wine bug report and the comments from the > upstream bug tracker appearing in-line. > > So if we were to make a list of packages it'd include: > > wine1.2 > wine > thunderbird > firefox > > What else? > > I am asking as this is rather hard to determine from Launchpad itself - > at least as far as I can tell. You can find bug mail about imported > comments by looking for mail from "Bug Watch Updater" and with the body > "Launchpad has imported" some number "comments from the remote bug". > When I was filtering "Launchpad has imported" returned no false > positives. > > I think posting to the list is a good way to build an initial list, as > it'll help people learn about the packages, and then we can make a wiki > page with them. I think this is a great idea! I would prefer to start writing the wiki just know, with the packages that we already know, to avoid losing track of this conversation. What do you think? Cheers, Ara. From flipefr at gmail.com Thu Sep 16 12:24:22 2010 From: flipefr at gmail.com (Felipe Franco) Date: Thu, 16 Sep 2010 14:24:22 +0200 Subject: Sorry Message-ID: That was a mistake, i am really sorry Claudio Moretti Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.nielsen81 at gmail.com Thu Sep 16 11:12:14 2010 From: k.nielsen81 at gmail.com (Kenneth Nielsen) Date: Thu, 16 Sep 2010 13:12:14 +0200 Subject: Fwd: [Bug 159400] Re: Some strings improperly i18n'ed In-Reply-To: <20100916005226.20922.21089.launchpad@loganberry.canonical.com> References: <20071101233138.22328.1926.malonedeb@gandwana.ubuntu.com> <20100916005226.20922.21089.launchpad@loganberry.canonical.com> Message-ID: Why is bug watch updater changing the importance of bugs marked as fixed, hence generating e-mails? Regards Kenneth ---------- Forwarded message ---------- From: Bug Watch Updater <159400 at bugs.launchpad.net> Date: 2010/9/16 Subject: [Bug 159400] Re: Some strings improperly i18n'ed To: k.nielsen81 at gmail.com ** Changed in: gnome-games   Importance: Unknown => Low -- Some strings improperly i18n'ed https://bugs.launchpad.net/bugs/159400 You received this bug notification because you are a direct subscriber of the bug. From cjk at teamcharliesangels.com Thu Sep 16 14:05:10 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 16 Sep 2010 08:05:10 -0600 Subject: Imported Bug Comments In-Reply-To: <4C91CE69.2080606@ubuntu.com> References: <20100915224208.GF2958@murraytwins.com> <4C91CE69.2080606@ubuntu.com> Message-ID: <20100916080510.480dfd41@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 16 Sep 2010 09:59:37 +0200 Ara Pulido wrote: > Hello all, > > On 16/09/10 00:42, Brian Murray wrote: > > Launchpad has had the ability to display bug comments from upstream bug > > trackers for some time now but it only works with some upstreams. I > > thought it would be helpful to have a list of the Ubuntu packages in > > Launchpad that are displaying bug comments from upstream bug trackers so > > we can focus on forwarding these package's bugs upstream and adding the > > bug watches. > > > > If you'd like an example of what I am talking about see > > http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) > > bug task linked to an upstream Wine bug report and the comments from the > > upstream bug tracker appearing in-line. > > > > So if we were to make a list of packages it'd include: > > > > wine1.2 > > wine > > thunderbird > > firefox > > > > What else? > > > > I am asking as this is rather hard to determine from Launchpad itself - > > at least as far as I can tell. You can find bug mail about imported > > comments by looking for mail from "Bug Watch Updater" and with the body > > "Launchpad has imported" some number "comments from the remote bug". > > When I was filtering "Launchpad has imported" returned no false > > positives. > > > > I think posting to the list is a good way to build an initial list, as > > it'll help people learn about the packages, and then we can make a wiki > > page with them. > > I think this is a great idea! I would prefer to start writing the wiki > just know, with the packages that we already know, to avoid losing track > of this conversation. What do you think? > > Cheers, > Ara. > +1 This type of information is too easy to lose in the mailing list. It would be great to see it in the wiki, which, if that is the long term plan, should be started. It is just as easy to add to the wiki as send another message. The advantage is that none of the additions get lost when the messages get lost/missing/changed. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMkiQWAAoJEFNEIRz9dxbAGO8H/1QUvNOQISrO9Elt3JTUlKVq YvyE7BRJpo7gYmfcFo0L2QTenHBtd482fKNRJEkfnjMw+ockiI/tPk0QCgtLmvso l+C1lxZGEJYgbtalSyXPI+JPPezFKXBiBWysGFqKyjLskr/X5cvTBKhSwcFgJRus +vZHG3nJkUqAYe9gyZjUz6yzgjxxAtb2TlMRJymMvZLFvvXofI8zJxM3jN6Coi9k mxkymuFOQ+p5Fq4ou09AXhiCD3xY1fY9OVbr7v4HopIsPCpMiZgNvGoCUDb3Ry+j tHmM5pqNQ5QE/KTrben1Sg+qtFjpFvG5w/hk+hUNGlr96z7s2oKBlGApukA6QcA= =mQOj -----END PGP SIGNATURE----- From macoafi at gmail.com Thu Sep 16 14:21:05 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 16 Sep 2010 10:21:05 -0400 Subject: Imported Bug Comments In-Reply-To: <20100915224208.GF2958@murraytwins.com> References: <20100915224208.GF2958@murraytwins.com> Message-ID: <201009161021.06055.macoafi@gmail.com> On Wednesday, September 15, 2010 06:42:08 pm Brian Murray wrote: > What else? All of GNOME? I'd be surprised if the updated Bugzilla Canonical got for them wasn't compatible with this. -- Mackenzie From cjk at teamcharliesangels.com Thu Sep 16 14:27:48 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 16 Sep 2010 08:27:48 -0600 Subject: Imported Bug Comments In-Reply-To: <201009161021.06055.macoafi@gmail.com> References: <20100915224208.GF2958@murraytwins.com> <201009161021.06055.macoafi@gmail.com> Message-ID: <20100916082748.235920a7@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 16 Sep 2010 10:21:05 -0400 Mackenzie Morgan wrote: > On Wednesday, September 15, 2010 06:42:08 pm Brian Murray wrote: > > What else? > > All of GNOME? I'd be surprised if the updated Bugzilla Canonical got for them > wasn't compatible with this. > All the gnumeric updates are not including comments, and it is using gnome bugzilla. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMkilkAAoJEFNEIRz9dxbA9VoH/36okgbhD7ttEEDw3Fz98DJ7 7IHUKqMBoldPnBaVlR4MpNjQs9K5gfKxLGteHvqVl0fVJe11vxaouPvhOvX+xQPL joOUzut0F202fy3bgHJLdlcPz7hWs4VZ1vDa48krxqWXPNBaJJwuB53kGUsul5hG m/cMNEIeL84a6WFb+b9RUIqQd0guzGCGSajBc1wQ/6ofPoL3jNfnGUzH+8GsAMSU N/nlUvQWyZpLMxrJVXFOeLsPbJmf454LO2YlsvW1XEk/tczujbnwaHsol0rYjWgg iqdOOCsDEOP72sWWsoqQK7L4Zev3lmG6UVSwx5Sj6v8mOf7yQMNZwHMkGDWIVXU= =2HYW -----END PGP SIGNATURE----- From macoafi at gmail.com Thu Sep 16 14:30:49 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 16 Sep 2010 10:30:49 -0400 Subject: Fwd: [Bug 159400] Re: Some strings improperly i18n'ed In-Reply-To: References: <20071101233138.22328.1926.malonedeb@gandwana.ubuntu.com> <20100916005226.20922.21089.launchpad@loganberry.canonical.com> Message-ID: <201009161030.49960.macoafi@gmail.com> On Thursday, September 16, 2010 07:12:14 am Kenneth Nielsen wrote: > Why is bug watch updater changing the importance of bugs marked as > fixed, hence generating e-mails? It's updating the status and importance changes along with comments from upstream bugtrackers on bugs that have upstream bugwatches. The switch was just turned on, as announced here: https://lists.ubuntu.com/archives/ubuntu- devel/2010-September/031421.html -- Mackenzie From macoafi at gmail.com Thu Sep 16 15:55:31 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 16 Sep 2010 11:55:31 -0400 Subject: Imported Bug Comments In-Reply-To: <20100916082748.235920a7@teamcharliesangels.com> References: <20100915224208.GF2958@murraytwins.com> <201009161021.06055.macoafi@gmail.com> <20100916082748.235920a7@teamcharliesangels.com> Message-ID: <201009161155.33214.macoafi@gmail.com> On Thursday, September 16, 2010 10:27:48 am Charlie Kravetz wrote: > On Thu, 16 Sep 2010 10:21:05 -0400 > > Mackenzie Morgan wrote: > > On Wednesday, September 15, 2010 06:42:08 pm Brian Murray wrote: > > > What else? > > > > All of GNOME? I'd be surprised if the updated Bugzilla Canonical got for > > them wasn't compatible with this. > > All the gnumeric updates are not including comments, and it is using > gnome bugzilla. They're enabling a new bugzilla install each day, though. So maybe GNOME's day hasn't hit yet? -- Mackenzie From nigelbabu at ubuntu.com Thu Sep 16 16:36:13 2010 From: nigelbabu at ubuntu.com (Nigel Babu) Date: Thu, 16 Sep 2010 22:06:13 +0530 Subject: Imported Bug Comments In-Reply-To: <201009161155.33214.macoafi@gmail.com> References: <20100915224208.GF2958@murraytwins.com> <201009161021.06055.macoafi@gmail.com> <20100916082748.235920a7@teamcharliesangels.com> <201009161155.33214.macoafi@gmail.com> Message-ID: On Thu, Sep 16, 2010 at 9:25 PM, Mackenzie Morgan wrote: > On Thursday, September 16, 2010 10:27:48 am Charlie Kravetz wrote: >> On Thu, 16 Sep 2010 10:21:05 -0400 >> >> Mackenzie Morgan wrote: >> > On Wednesday, September 15, 2010 06:42:08 pm Brian Murray wrote: >> > > What else? >> > >> > All of GNOME?  I'd be surprised if the updated Bugzilla Canonical got for >> > them wasn't compatible with this. >> >> All the gnumeric updates are not including comments, and it is using >> gnome bugzilla. > > They're enabling a new bugzilla install each day, though.  So maybe GNOME's > day hasn't hit yet? > > -- > Mackenzie > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > Hi Folks, If you're confused about not getting what everyone's talking about, there is a bug in LP that lets you see imported comments only if you're a member of https://edge.launchpad.net/~launchpad-beta-testers Warm Regards Nigel Babu From cjk at teamcharliesangels.com Thu Sep 16 16:53:56 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 16 Sep 2010 10:53:56 -0600 Subject: Imported Bug Comments In-Reply-To: <20100915224443.GG2958@murraytwins.com> References: <20100915224208.GF2958@murraytwins.com> <20100915224443.GG2958@murraytwins.com> Message-ID: <20100916105356.178b5f4d@teamcharliesangels.com> On Wed, 15 Sep 2010 15:44:43 -0700 Brian Murray wrote: > On Wed, Sep 15, 2010 at 03:42:08PM -0700, Brian Murray wrote: > > Launchpad has had the ability to display bug comments from upstream bug > > trackers for some time now but it only works with some upstreams. I > > thought it would be helpful to have a list of the Ubuntu packages in > > Launchpad that are displaying bug comments from upstream bug trackers so > > we can focus on forwarding these package's bugs upstream and adding the > > bug watches. > > > > If you'd like an example of what I am talking about see > > http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) > > bug task linked to an upstream Wine bug report and the comments from the > > upstream bug tracker appearing in-line. > > > > So if we were to make a list of packages it'd include: > > > > wine1.2 > > wine > > thunderbird > > firefox > > xserver-xorg-video-intel > > Missed one! > abiword -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: not available URL: From brian at ubuntu.com Thu Sep 16 17:05:49 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 16 Sep 2010 10:05:49 -0700 Subject: Imported Bug Comments In-Reply-To: <4C91CE69.2080606@ubuntu.com> References: <20100915224208.GF2958@murraytwins.com> <4C91CE69.2080606@ubuntu.com> Message-ID: <20100916170549.GK2958@murraytwins.com> On Thu, Sep 16, 2010 at 09:59:37AM +0200, Ara Pulido wrote: > Hello all, > > On 16/09/10 00:42, Brian Murray wrote: > > Launchpad has had the ability to display bug comments from upstream bug > > trackers for some time now but it only works with some upstreams. I > > thought it would be helpful to have a list of the Ubuntu packages in > > Launchpad that are displaying bug comments from upstream bug trackers so > > we can focus on forwarding these package's bugs upstream and adding the > > bug watches. > > > > If you'd like an example of what I am talking about see > > http://launchpad.net/bugs/624386. Here we can see a wine1.2 (Ubuntu) > > bug task linked to an upstream Wine bug report and the comments from the > > upstream bug tracker appearing in-line. > > > > So if we were to make a list of packages it'd include: > > > > wine1.2 > > wine > > thunderbird > > firefox > > > > What else? > > > > I am asking as this is rather hard to determine from Launchpad itself - > > at least as far as I can tell. You can find bug mail about imported > > comments by looking for mail from "Bug Watch Updater" and with the body > > "Launchpad has imported" some number "comments from the remote bug". > > When I was filtering "Launchpad has imported" returned no false > > positives. I'd normally use the ubuntu-bugs mailing list archive to do this but the ubuntu-bugs team is not part of, nor should it be, the launchpad-beta-testers team. Eventually, this will be sorted out but in the meantime I could use your help. > > I think posting to the list is a good way to build an initial list, as > > it'll help people learn about the packages, and then we can make a wiki > > page with them. > > I think this is a great idea! I would prefer to start writing the wiki > just know, with the packages that we already know, to avoid losing track > of this conversation. What do you think? I've added it into http://wiki.ubuntu.com/Bugs/Watches. Thanks again, -- 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 ilidrissiamine at gmail.com Thu Sep 16 17:13:31 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Thu, 16 Sep 2010 17:13:31 +0000 Subject: Flipe Fr invited you to Dropbox In-Reply-To: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> Message-ID: Am I to assume Dropbox wants to triage Ubuntu bugs? :p On Thu, Sep 16, 2010 at 6:25 AM, Dropbox wrote: > > [cut] > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From noreply at ubuntu.com Thu Sep 16 17:03:59 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 16 Sep 2010 17:03:59 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Watches=22_by_brian-murray?= Message-ID: <20100916170359.10133.75162@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/Watches?action=diff&rev1=23&rev2=24 ------------------------------------------------------------------------------ As a part of the bug watching service Launchpad is also able to import comments from the upstream bug tracker and display them in the Launchpad bug report. An example of this can be found in [[http://launchpad.net/bugs/624386|bug 624386]]. A list of the Ubuntu packages that have an upstream bug tracker that will display imported comments follows. || Ubuntu source package || Bug Tracker || + || [[http://bugs.launchpad.net/ubuntu/+source/abiword | abiword]] || || + || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati]] || bugs.freedesktop.org || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel]] || bugs.freedesktop.org || || [[http://bugs.launchpad.net/ubuntu/+source/wine | wine]] || winehq || || [[http://bugs.launchpad.net/ubuntu/+source/wine1.2 | wine]] || winehq || - || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird]] || mozilla.org || - || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox]] || mozilla.org || - || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel]] || bugs.freedesktop.org || - || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati]] || bugs.freedesktop.org || == Also see == Launchpad [[https://help.launchpad.net/FeatureHighlights/MultiProjectBugs|documentation]] regarding this process. From noreply at ubuntu.com Thu Sep 16 17:02:20 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 16 Sep 2010 17:02:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Watches=22_by_brian-murray?= Message-ID: <20100916170220.10133.81632@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/Watches?action=diff&rev1=22&rev2=23 ------------------------------------------------------------------------------ The bug will no longer show up in the reports at https://launchpad.net/bugs/bugtrackers/. + == Imported bug comments == + + As a part of the bug watching service Launchpad is also able to import comments from the upstream bug tracker and display them in the Launchpad bug report. An example of this can be found in [[http://launchpad.net/bugs/624386|bug 624386]]. A list of the Ubuntu packages that have an upstream bug tracker that will display imported comments follows. + + || Ubuntu source package || Bug Tracker || + || [[http://bugs.launchpad.net/ubuntu/+source/wine | wine]] || winehq || + || [[http://bugs.launchpad.net/ubuntu/+source/wine1.2 | wine]] || winehq || + || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel]] || bugs.freedesktop.org || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati]] || bugs.freedesktop.org || == Also see == Launchpad [[https://help.launchpad.net/FeatureHighlights/MultiProjectBugs|documentation]] regarding this process. From cjk at teamcharliesangels.com Thu Sep 16 17:21:04 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 16 Sep 2010 11:21:04 -0600 Subject: Flipe Fr invited you to Dropbox In-Reply-To: References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> Message-ID: <20100916112104.4dc734bc@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 16 Sep 2010 17:13:31 +0000 Mohamed Amine IL Idrissi wrote: > Am I to assume Dropbox wants to triage Ubuntu bugs? :p > > On Thu, Sep 16, 2010 at 6:25 AM, Dropbox wrote: > > > > [cut] > > Better to assume dropbox, like so many other sites now, grabs the address book and issues the invites when told, "sure, invite my friends". They don't usually give you a chance to edit who to invite. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMklIAAAoJEFNEIRz9dxbA3eQH/0dnw72/Mbs4jLb6ojXT139s /pZ44Jq5IonZYjn/0PLEu8GI4BwcPuti9PP0pER87MCfphogy0DDSSvrkYJoZAAM Sfti6c76Tx8pyKuEk/WUfQx65oTDZWuXXXq46s3r5JPxMp/2rW45Dyb7PsHUXTMR mSC95XfSbhv+fpGffQx/xeRPmRslhAWuU97IxZ/4HLXOg2aENoCiwdcBknb7qcVE r3FOzLxHl3sW8tT3j/MLCTGJKr9agbRyvHqcu9yXjJRRT6fIukNeUBJzG7ylvSCB tCEKyvfVPlLXpFuki8RmO613d1031z3+BjEfCYphUJWnKcQ6YTn48rrCRnAqxhU= =QMco -----END PGP SIGNATURE----- From macoafi at gmail.com Thu Sep 16 17:34:20 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 16 Sep 2010 13:34:20 -0400 Subject: Flipe Fr invited you to Dropbox In-Reply-To: <20100916112104.4dc734bc@teamcharliesangels.com> References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> <20100916112104.4dc734bc@teamcharliesangels.com> Message-ID: <201009161334.21755.macoafi@gmail.com> On Thursday, September 16, 2010 01:21:04 pm Charlie Kravetz wrote: > On Thu, 16 Sep 2010 17:13:31 +0000 > > Mohamed Amine IL Idrissi wrote: > > Am I to assume Dropbox wants to triage Ubuntu bugs? :p > > > > On Thu, Sep 16, 2010 at 6:25 AM, Dropbox wrote: > > > [cut] > > Better to assume dropbox, like so many other sites now, grabs the > address book and issues the invites when told, "sure, invite my > friends". They don't usually give you a chance to edit who to invite. I've never seen one that didn't...but they do tend to start with *every* checkbox checked so you have to uncheck everyone. -- Mackenzie From flyingstar16 at gmail.com Thu Sep 16 18:09:35 2010 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Thu, 16 Sep 2010 20:09:35 +0200 Subject: Flipe Fr invited you to Dropbox In-Reply-To: <201009161334.21755.macoafi@gmail.com> References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> <20100916112104.4dc734bc@teamcharliesangels.com> <201009161334.21755.macoafi@gmail.com> Message-ID: On Thu, Sep 16, 2010 at 19:34, Mackenzie Morgan wrote: > On Thursday, September 16, 2010 01:21:04 pm Charlie Kravetz wrote: > > On Thu, 16 Sep 2010 17:13:31 +0000 > > > > Mohamed Amine IL Idrissi wrote: > > > Am I to assume Dropbox wants to triage Ubuntu bugs? :p > > > > > > On Thu, Sep 16, 2010 at 6:25 AM, Dropbox > wrote: > > > > [cut] > > > > Better to assume dropbox, like so many other sites now, grabs the > > address book and issues the invites when told, "sure, invite my > > friends". They don't usually give you a chance to edit who to invite. > > I've never seen one that didn't...but they do tend to start with *every* > checkbox checked so you have to uncheck everyone. > > javascript: for(i=0; i From braiamp at gmail.com Thu Sep 16 22:35:48 2010 From: braiamp at gmail.com (Braiam Peguero) Date: Thu, 16 Sep 2010 18:35:48 -0400 Subject: Flipe Fr invited you to Dropbox In-Reply-To: References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> <20100916112104.4dc734bc@teamcharliesangels.com> <201009161334.21755.macoafi@gmail.com> Message-ID: <010201cb55ef$874b8810$95e29830$@gmail.com> I'm not sure if Facebook or only some applications do it. De: ubuntu-bugsquad-bounces at lists.ubuntu.com [mailto:ubuntu-bugsquad-bounces at lists.ubuntu.com] En nombre de Claudio Moretti Enviado el: jueves, 16 de septiembre de 2010 02:10 p.m. Para: macoafi at gmail.com CC: ubuntu-bugsquad at lists.ubuntu.com Asunto: Re: Flipe Fr invited you to Dropbox On Thu, Sep 16, 2010 at 19:34, Mackenzie Morgan < macoafi at gmail.com> wrote: On Thursday, September 16, 2010 01:21:04 pm Charlie Kravetz wrote: > On Thu, 16 Sep 2010 17:13:31 +0000 > > Mohamed Amine IL Idrissi < ilidrissiamine at gmail.com> wrote: > > Am I to assume Dropbox wants to triage Ubuntu bugs? :p > > > > On Thu, Sep 16, 2010 at 6:25 AM, Dropbox < no-reply at dropboxmail.com> wrote: > > > [cut] > > Better to assume dropbox, like so many other sites now, grabs the > address book and issues the invites when told, "sure, invite my > friends". They don't usually give you a chance to edit who to invite. I've never seen one that didn't...but they do tend to start with *every* checkbox checked so you have to uncheck everyone. javascript: for(i=0; i From flyingstar16 at gmail.com Thu Sep 16 23:37:39 2010 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Fri, 17 Sep 2010 01:37:39 +0200 Subject: Flipe Fr invited you to Dropbox In-Reply-To: <010201cb55ef$874b8810$95e29830$@gmail.com> References: <20100916062503.3A2AA673CFC@mailman-2.dropboxmail.com> <20100916112104.4dc734bc@teamcharliesangels.com> <201009161334.21755.macoafi@gmail.com> <010201cb55ef$874b8810$95e29830$@gmail.com> Message-ID: On Fri, Sep 17, 2010 at 00:35, Braiam Peguero wrote: > I’m not sure if Facebook or only some applications do it. > I can call this an on-the-fly-developed code; it should work (if it works) on any browser, as it uses the document.getElementsByTagName("tagname") function, which is a DOM core function. ( http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html) Aren't we a little bit off topic? lol -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcopple at kcopensource.org Fri Sep 17 01:23:15 2010 From: mcopple at kcopensource.org (Matthew Copple) Date: Thu, 16 Sep 2010 20:23:15 -0500 Subject: faulty driver rt2870sta In-Reply-To: <4C8F87D1.5010707@gmail.com> References: <4C8F87D1.5010707@gmail.com> Message-ID: I actually had both drivers listed -- the problem seemed to be that they were conflicting with one another. Once I blacklisted the rt2800 it picked up the rt2870sta fine. I'm running Lucid with all the latest updates. Matthew Copple mcopple at kcopensource.org 2010/9/14 Asbjørn Gabrielsen : > Hi > I've come across a problem with the Ralink RT2870 (rt2870sta) wifi > driver in lucid. My adapter is wrongly recognized as an rt2800 chipset > and lucid loads the rt2800usb driver, instead of the rt2870sta. The > 2800-driver doesn't work with my adapter. > > After 13 hours of googling and trying different approaches, I've got the > adapter to work. I had to blacklist the rt2800-driver and download the > latest driver from the Ralink website. I then had to modify the driver's > device list for the new driver to include my adaptor and the config.mk > file to activate WPA encryption. This should be an easy fix for the > maverick release. > > The new driver is found here: http://www.ralinktech.com/support.php?s=2 > (RT2870 chipset) > The missing device in the list (/common/rtusb_dev_id.c) is the Gigabyte > AirCruiser N300, GN-WB31N-RH, usb id 1044:800C > WPA-support can be activated in the file /os/linux/config.mk > > Best regards > Asbjørn Gabrielsen > Oslo, Norway > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Matthew G. Copple mcopple at kcopensource.org From cyan.spam at gmail.com Mon Sep 20 23:06:40 2010 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 20 Sep 2010 19:06:40 -0400 Subject: faulty driver rt2870sta In-Reply-To: References: <4C8F87D1.5010707@gmail.com> Message-ID: <4C97E900.8010800@gmail.com> On 09/16/2010 09:23 PM, Matthew Copple wrote: > I actually had both drivers listed -- the problem seemed to be that > they were conflicting with one another. Once I blacklisted the rt2800 > it picked up the rt2870sta fine. > Please submit a bug report with "ubuntu-bug linux". (Or find an existing duplicate.) Thanks, David From jw+debian at jameswestby.net Wed Sep 22 14:51:53 2010 From: jw+debian at jameswestby.net (James Westby) Date: Wed, 22 Sep 2010 10:51:53 -0400 Subject: Ubuntu Branch reviewers In-Reply-To: <1278344866.1938.3.camel@bilal-laptop> References: <1278344866.1938.3.camel@bilal-laptop> Message-ID: <87fwx1rfue.fsf@jameswestby.net> On Mon, 05 Jul 2010 18:47:46 +0300, Bilal Akhtar wrote: > Hi all, > I think it would be a *lot* better to set the reviewer of all ubuntu > branches to ubuntu-sponsors. This would prevent confusion among people > who wish to fix bugs in Ubuntu or merge packages. Such people propose a > merge and the value of reviewer is set to ubuntu-branches, while, > according to https://wiki.ubuntu.com/Bugs/HowToFix and others, the > reviewer should be ubuntu-sponsors. A merge proposal that has this > mistake is > https://code.edge.launchpad.net/~joel-auterson/ubuntu/maverick/shotwell/menu_rename/+merge/28598 where I had to comment in order to get this change done. > > What are your opinions? The default reviewer for all branches is now set to ~ubuntu-dev as discussed in this thread: https://lists.ubuntu.com/archives/ubuntu-devel/2009-December/029694.html Thanks, James From noreply at ubuntu.com Wed Sep 22 17:28:44 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 22 Sep 2010 17:28:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Watches=22_by_brian-murray?= Message-ID: <20100922172844.32418.46021@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/Watches?action=diff&rev1=26&rev2=27 ------------------------------------------------------------------------------ || Ubuntu source package || Bug Tracker || || [[http://bugs.launchpad.net/ubuntu/+source/abiword | abiword]] || http://bugzilla.abisource.com/ || || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/moon | moon ]] || moonlight plugin mozilla - bugzilla.novel.com || || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird]] || mozilla.org || || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati]] || bugs.freedesktop.org || || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel]] || bugs.freedesktop.org || From noreply at ubuntu.com Wed Sep 22 19:19:13 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 22 Sep 2010 19:19:13 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Watches=22_by_brian-murray?= Message-ID: <20100922191913.29084.67043@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/Watches?action=diff&rev1=27&rev2=28 The comment on the change is: Found a way to get the bug trackers with sync'ed comments ------------------------------------------------------------------------------ || Ubuntu source package || Bug Tracker || || [[http://bugs.launchpad.net/ubuntu/+source/abiword | abiword]] || http://bugzilla.abisource.com/ || + || [[http://bugs.launchpad.net/ubuntu/+source/amarok | amarok ]] || Amarok || + || [[http://bugs.launchpad.net/ubuntu/+source/cairo | cairo ]] || Poppler || + || [[http://bugs.launchpad.net/ubuntu/+source/consolekit | consolekit ]] || ConsoleKit || + || [[http://bugs.launchpad.net/ubuntu/+source/dbus | dbus ]] || D-Bus || + || [[http://bugs.launchpad.net/ubuntu/+source/dbus-python | dbus-python ]] || D-Bus || + || [[http://bugs.launchpad.net/ubuntu/+source/devicekit-disks | devicekit-disks ]] || gnome-desktop || + || [[http://bugs.launchpad.net/ubuntu/+source/devicekit-power | devicekit-power ]] || DeviceKit-Power || + || [[http://bugs.launchpad.net/ubuntu/+source/emacs23 | emacs23 ]] || GNU Emacs || + || [[http://bugs.launchpad.net/ubuntu/+source/empathy | empathy ]] || telepathy-gabble || + || [[http://bugs.launchpad.net/ubuntu/+source/evince | evince ]] || Evince || + || [[http://bugs.launchpad.net/ubuntu/+source/fast-user-switch-applet | fast-user-switch-applet ]] || D-Bus || + || [[http://bugs.launchpad.net/ubuntu/+source/fglrx-installer | fglrx-installer ]] || xf86-video-ati || + || [[http://bugs.launchpad.net/ubuntu/+source/firefox-3.0 | firefox-3.0 ]] || Mozilla Firefox || + || [[http://bugs.launchpad.net/ubuntu/+source/firefox-3.5 | firefox-3.5 ]] || Mozilla Firefox || - || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/firefox | firefox ]] || Mozilla Firefox || + || [[http://bugs.launchpad.net/ubuntu/+source/fontconfig | fontconfig ]] || Wine || + || [[http://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility | gnome-disk-utility ]] || gnome-desktop || + || [[http://bugs.launchpad.net/ubuntu/+source/hal | hal ]] || HAL || + || [[http://bugs.launchpad.net/ubuntu/+source/hal-info | hal-info ]] || HAL || + || [[http://bugs.launchpad.net/ubuntu/+source/libatasmart | libatasmart ]] || libatasmart || + || [[http://bugs.launchpad.net/ubuntu/+source/libcairo | libcairo ]] || libcairo || + || [[http://bugs.launchpad.net/ubuntu/+source/lightning-sunbird | lightning-sunbird ]] || Sunbird || + || [[http://bugs.launchpad.net/ubuntu/+source/linux-firmware | linux-firmware ]] || Linux || + || [[http://bugs.launchpad.net/ubuntu/+source/linux | linux ]] || Linux || + || [[http://bugs.launchpad.net/ubuntu/+source/media-player-info | media-player-info ]] || media-player-info || + || [[http://bugs.launchpad.net/ubuntu/+source/mesa | mesa ]] || Mesa || + || [[http://bugs.launchpad.net/ubuntu/+source/mono | mono ]] || mono || - || [[http://bugs.launchpad.net/ubuntu/+source/moon | moon ]] || moonlight plugin mozilla - bugzilla.novel.com || + || [[http://bugs.launchpad.net/ubuntu/+source/moon | moon ]] || Moonlight Plugin Mozilla || + || [[http://bugs.launchpad.net/ubuntu/+source/mozilla-thunderbird | mozilla-thunderbird ]] || Mozilla Thunderbird || + || [[http://bugs.launchpad.net/ubuntu/+source/openoffice.org | openoffice.org ]] || OpenOffice || + || [[http://bugs.launchpad.net/ubuntu/+source/openssh | openssh ]] || portable OpenSSH || + || [[http://bugs.launchpad.net/ubuntu/+source/papyon | papyon ]] || papyon || + || [[http://bugs.launchpad.net/ubuntu/+source/policykit-1 | policykit-1 ]] || PolicyKit || + || [[http://bugs.launchpad.net/ubuntu/+source/poppler | poppler ]] || Poppler || + || [[http://bugs.launchpad.net/ubuntu/+source/pymsn | pymsn ]] || pymsn || + || [[http://bugs.launchpad.net/ubuntu/+source/rarian | rarian ]] || Rarian || + || [[http://bugs.launchpad.net/ubuntu/+source/shared-mime-info | shared-mime-info ]] || shared-mime-info || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly | telepathy-butterfly ]] || telepathy-butterfly || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-gabble | telepathy-gabble ]] || telepathy-gabble || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-glib | telepathy-glib ]] || Telepathy Glib || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-haze | telepathy-haze ]] || Telepathy Haze || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-idle | telepathy-idle ]] || telepathy-idle || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5 | telepathy-mission-control-5 ]] || Telepathy Mission Control 5 || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-salut | telepathy-salut ]] || telepathy-salut || + || [[http://bugs.launchpad.net/ubuntu/+source/telepathy-sofiasip | telepathy-sofiasip ]] || telepathy-sofiasip || - || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird]] || mozilla.org || + || [[http://bugs.launchpad.net/ubuntu/+source/thunderbird | thunderbird ]] || Mozilla Thunderbird || - || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati]] || bugs.freedesktop.org || - || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel]] || bugs.freedesktop.org || + || [[http://bugs.launchpad.net/ubuntu/+source/ttf-dejavu | ttf-dejavu ]] || DejaVu Fonts || + || [[http://bugs.launchpad.net/ubuntu/+source/udisks | udisks ]] || udisks || - || [[http://bugs.launchpad.net/ubuntu/+source/wine | wine]] || winehq || + || [[http://bugs.launchpad.net/ubuntu/+source/weave | weave ]] || Firefox Sync || - || [[http://bugs.launchpad.net/ubuntu/+source/wine1.2 | wine1.2]] || winehq || + || [[http://bugs.launchpad.net/ubuntu/+source/wine1.2 | wine1.2 ]] || Wine || + || [[http://bugs.launchpad.net/ubuntu/+source/wine | wine ]] || Wine || + || [[http://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils | x11-xserver-utils ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xdg-utils | xdg-utils ]] || Xdg-utils || + || [[http://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom | xf86-input-wacom ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xkeyboard-config | xkeyboard-config ]] || xkeyboard-config || + || [[http://bugs.launchpad.net/ubuntu/+source/xorg-server | xorg-server ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xorg | xorg ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-aiptek | xserver-xorg-input-aiptek ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev | xserver-xorg-input-evdev ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev | xserver-xorg-input-evdev ]] || xserver-xorg-input-evdev || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics | xserver-xorg-input-synaptics ]] || XOrg-Driver-Synaptics || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati | xserver-xorg-video-ati ]] || xserver-xorg-driver-ati || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-i128 | xserver-xorg-video-i128 ]] || xorg xf86-video-i128 || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel | xserver-xorg-video-intel ]] || xf86-video-intel || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau | xserver-xorg-video-nouveau ]] || Nouveau Xorg driver || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv | xserver-xorg-video-nv ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-radeonhd | xserver-xorg-video-radeonhd ]] || xf86-video-radeonhd || + || [[http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vesa | xserver-xorg-video-vesa ]] || X.Org X server || + || [[http://bugs.launchpad.net/ubuntu/+source/xulrunner-1.9.1 | xulrunner-1.9.1 ]] || Mozilla Firefox || == Also see == Launchpad [[https://help.launchpad.net/FeatureHighlights/MultiProjectBugs|documentation]] regarding this process. From brian at ubuntu.com Thu Sep 23 19:18:08 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 23 Sep 2010 12:18:08 -0700 Subject: Packages importing bug comments Message-ID: <20100923191808.GF2958@murraytwins.com> I found a way to determine bugs and subsequently packages that have imported bug comments from an upstream bug tracker and have updated the Imported Bug Comments[1] table on the bug watches wiki page. It'd be interesting to have a bug day for one of the packages listed there and specifically focus on forwarding bug reports upstream. [1] https://wiki.ubuntu.com/Bugs/Watches#Imported%20bug%20comments -- 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 webmaster at ubuntu.com Thu Sep 23 19:03:36 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Thu, 23 Sep 2010 19:03:36 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_ilidrissi=2Eamine?= Message-ID: <20100923190336.10471.89378@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 ilidrissi.amine: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=146&rev2=147 The comment on the change is: Complete rewrite of the ReportingBugs page. Discussed by the BugSquad/BugControl teams extensively. - Mohamed Amine IL Idrissi ------------------------------------------------------------------------------ <> - '''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.''' + = How to report bugs = - = Reporting bugs = + ||<>|| - ||<>|| + Ubuntu uses Launchpad to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report. - Ubuntu uses Launchpad to keep track of bugs and their fixes. To file a bug you first need to [[ https://help.launchpad.net/YourAccount/NewAccount | create an account ]]. Once you have an account you can use the tools we've provided you on your Ubuntu system to file bug reports. + == Using Kubuntu? == - Note 1: If you use Kubuntu, please see the Kubuntu variant of this page [[https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting|here]]. + If you use Kubuntu, please see the Kubuntu variant of this page [[https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting|here]]. - 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]]). + == 1. Create a Launchpad account == - == Filing a bug with ubuntu-bug == + If you don't already have one - you need to [[https://help.launchpad.net/YourAccount/NewAccount|create a Launchpad account]]. This will allow you to file new bugs and comment on existing ones. - === Ubuntu 8.10 and later === + == 2. Determine if your bug is really a bug == - ||{{attachment:ubuntu-bug.png|Filing a bug with the "Run Application" window}}|| + You should not file a bug if you are: + * '''Requesting new software:''' you should follow the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages + * '''Requesting support:''' there are a multitude of ways you can get support, such as the [[https://answers.launchpad.net/ubuntu|Launchpad answer tracker]], the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list, and the [[http://ubuntu.stackexchange.com|Ubuntu Stack Exchange]] site. + * '''Discussing features and existing policy:''' this belongs to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. + * '''Proposing features and ideas:''' you should submit your idea to [[http://brainstorm.ubuntu.com/|Ubuntu Brainstorm]] or to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. + * '''Filing a bug against a program not provided by an Ubuntu package:''' You should file a bug in that program's bug tracking interface. Instructions are generally available on the program's web site. + + /!\ If you want to file a translation or misspelling bug, follow the instructions [[#translation|here]]. + + == 3. Make sure your bug hasn't already been reported == + + When filing a bug, please make sure it has not already been reported by searching through the [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]] and the release notes for your version of Ubuntu: + * [[https://wiki.ubuntu.com/DapperReleaseNotes| Ubuntu 6.06 LTS (Dapper Drake)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/804|Ubuntu 8.04 LTS (Hardy Heron)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/904|Ubuntu 9.04 (Jaunty Jackalope)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/910|Ubuntu 9.10 (Karmic Koala)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/1004|Ubuntu 10.04 LTS (Lucid Lynx)]] + + If 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 your bug will not be addressed. + + [[#Top|Back to top]] + + == 4. Collect information about the bug == + + The method of reporting bugs in Ubuntu is by using the tool "ubuntu-bug", otherwise known as '''Apport'''. When reporting a bug, you must tell Apport which program or [[https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?|package]] is at fault. + + === Collecting information from a specific package === + + ||{{attachment:ubuntu-bug.png|Filing a bug with the "Run Application" window}}|| + - Press Alt+F2 to open the "Run Application" window, pictured above. Type `ubuntu-bug `''``'' and click ''Run''. Server Edition users should use a terminal instead. If you're not sure which package has a problem, + Press Alt+F2 to open the "Run Application" window, pictured above. Type `ubuntu-bug `''``'' and click ''Run''. If you're not sure which package has the problem, refer to the instructions for [[https://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]. - To file a bug against a program that is currently running, go to '''System > Administration > System Monitor''', and find the ID of the process. Server Edition users should use `ps aux`. + === Collecting information from a currently running program === + To file a bug against a program that is currently running, go to '''System > Administration > System Monitor''', and find the ID of the process. + - {{attachment:system-monitor-id.png | System Monitor Processes tab }} + ||{{attachment:system-monitor-id.png | System Monitor Processes tab }}|| Then type the process ID instead of the package name into the "Run Application" window. - {{attachment:ubuntu-bug-pid.png | Filing a bug with the "Run Application" window and a process ID}} + ||{{attachment:ubuntu-bug-pid.png | Filing a bug with the "Run Application" window and a process ID}}|| - === Ubuntu 8.04 LTS to Ubuntu 9.04 === + === Filing a general bug against no particular package === - In Ubuntu 8.04 LTS, you need to type `ubuntu-bug -p` (lowercase `p`) when reporting a bug about a package, or `ubuntu-bug -P` (capital `P`) when reporting a bug about a process ID. Instructions are otherwise identical to the above. + If you're not sure which package is affected by the bug, type `ubuntu-bug` in the "Run Application" window and click ''Run''. This will guide you through a series of questions to gather more information about your bug. - === Ubuntu 9.10 and Later === + [[#Top|Back to top]] - You only need to type `ubuntu-bug PKGNAME` when reporting against a package, or `ubuntu-bug PID` when reporting a bug about a process ID. Instructions are otherwise identical to the above. + == 5. Complete the bug filing process == + + After running one of the above commands, Apport (the Ubuntu bug reporter) will gather information about your bug. + + ||{{attachment:apport-1.png | Apport collecting information about the bug}}|| + + A window will then pop up, asking you if you want to report the bug. Click "Send Report" if you wish to proceed, or click "Content of the report" if you want to review the information Apport collected. + + ||{{attachment:send-problem-question.png | Apport asking you to send the report}}|| + + Apport will then upload the problem information to Launchpad, and a new browser window will then open to inform you that the bug is being processed. + + ||{{attachment:information-upload.png | Apport uploading the problem information}}|| + + ||{{attachment:process-data.png | Launchpad processing the bug data}}|| + + After the bug data has been processed, a new page will open that will ask you for the bug's title. When you're done, click "Next". + + ||{{attachment:bug-title.png | Launchpad asking for a bug title}}|| + + A search will then occur based on the title you gave to the bug, and will show potentially similar ones. If one of these seems to be the exact bug you're reporting, click its title, then "Yes, this is the bug I'm trying to report". If not, click "No, I need to report a new bug". + + ||{{attachment:bug-search.png | Launchpad search results about the bug title}}|| + + Launchpad will then ask you for further information. It's important that you specify three things: + + 1. What you expected to happen + 1. What actually happened + 1. The minimal series of steps necessary to make it happen, where step 1 is "start the program" + + Fill in the description field with as much information as you can, including the release of Ubuntu you are using and steps for someone else to recreate the bug. It is better to have too much information in the description than not enough. + + ||{{attachment:more-informations.png | Launchpad asking for further information}}|| + + At then bottom of the page, there is 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?) + * '''Tags:''' You can add here [[http://wiki.ubuntu.com/Bugs/Tags|tags]] that pertain to your bug report. The predefined values are fine most of the time. + * '''Include an attachment:''' Using this option, you can add supporting attachments to explain or help others reproduce your 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. + + ||{{attachment:extra-options.png | Launchpad presenting extra options}}|| + + When you're done, click "Submit bug report". + + = Tips and tricks = == Filing bugs when off-line == - In the event that you have a bug with your internet connection or want to file a bug for another system you can still do this using apport. Using the command `apport-cli -f -p` ''``'' on the target system will collect information and provide you with an option to "K: Keep report file for sending later or copying to somewhere else". The report is then saved on the target system, in your ''/tmp'' directory which is cleared out on reboot, with a .apport extension. After copying it to a different system you can file that report using `ubuntu-bug ` ''``''. + In the event that you have an issue with your internet connection or want to file a bug for another system you can still do this using apport. Using the command `apport-cli -f -p` ''``'' on the target system will collect information and provide you with an option to "K: Keep report file for sending later or copying to somewhere else". The report is then saved on the target system, in your ''/tmp'' directory which is cleared out on reboot, with a .apport extension. After copying it to a different system you can file that report using `ubuntu-bug ` ''``''. == Filing bugs at Launchpad.net == - If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 ]]. + If for some reason you cannot file a bug using the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpads own bug report form]]. When doing so it is best if 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 you can also use a URL like 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 ]]. + where PACKAGENAME is the name of the source package about which you want to file the bug. - == Using the help menu in the affected application == + 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 ]]. - '''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.) + == Using the help menu in the affected application (development releases only) == 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'''. @@ -68, +145 @@ 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}} + ||{{attachment:apport-1.png}}|| + == Adding Apport Debug Information to an Existing Launchpad Bug == - == Filing translation bugs == + If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. - All translation issues should be filed against the [[https://bugs.launchpad.net/ubuntu-translations | Ubuntu Translations project]] (ubuntu-translations). From there the bugs will be triaged and assigned to the right person and package. + <> + == Filing a translation bug == - Here is a non-exhaustive list of problems that are appropriate for the Ubuntu Translations project: + You should file a translation bug if you are experiencing one of the following issues: - * Wrong translations or spelling mistakes in applications + * Wrong translations or spelling mistakes for languages other than English in applications * Errors in spellcheckers or language support - * A string from an application is not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * A string from an application not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * An application from the Ubuntu main repository is not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * An application from the Ubuntu main repository not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * A translation made in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] is not updated in the Ubuntu language packs + * A translation made in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] and not updated in the Ubuntu language packs - * There is a duplicate translation template (the same application can be translated in two different places) in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * A duplicate translation template (the same application can be translated in two different places) in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * A template/translation is no longer used in Ubuntu and should be disabled from [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * A template/translation no longer used in Ubuntu and that should be disabled from [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + In case of doubt, you can always [[http://wiki.ubuntu.com/Translations/Contact|contact the Translations team]]. + All translation issues should be filed against the [[https://bugs.launchpad.net/ubuntu-translations | Ubuntu Translations project]]. From there the bugs will be triaged and assigned to the right person and package. - You can also consult the [[https://bugs.launchpad.net/ubuntu-translations|current bugs]] to see the big picture. In case of doubt, you can always [[http://wiki.ubuntu.com/Translations/Contact|contact the Translations team]]. - - === Adding Apport Debug Information to an Existing Launchpad Bug === - - If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. If this fails then run `apport-collect -p bug_number`. - - [[#Top|Back to top]] - = Writing a useful report = - - When a developer fixes a bug, they will test that the bug occurs, make a small change to the program, then see if the bug has gone away. Depending on the bug, they might need to run the same test dozens or hundreds of times. When you submit a bug report, it's important to specify three things: - - 1. What you expected to happen - 1. What actually happened - 1. The minimal series of steps necessary to make it happen, where step 1 is "start the program" - - Fill in the description field with as much information as you can, including the release of Ubuntu you are using and steps for someone else to recreate the bug. It is better to have too much information in the description than not enough. - - Only describe a single problem per bug report so that each can be followed up on in detail. If you experience several issues file separate reports. - - Add supporting attachments to explain or help others reproduce your bug. This might include a screenshot or video capture of the problem or a sample document that triggers the fault. To add an attachment to the bug use the '''Include an attachment''' section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. - - For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vvnn" and "dmesg", after a fresh boot, will help a lot. - - = When not to file a bug = - - * '''Requesting new software''' you should follow the guidelines in https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages - * '''Support requests''' should go to [[https://answers.launchpad.net/ubuntu|support requests in Launchpad]], the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, or the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list. - * '''Feature and policy discussions''' (including suggestions to change defaults) should be discussed on the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. - * '''Development ideas''' should be posted to http://brainstorm.ubuntu.com/ or discussed on the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. - * '''Already filed''' - Please check if it has already been reported by searching through the [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]] and the release notes for your release of Ubuntu: [[http://wiki.ubuntu.com/DapperReleaseNotes|6.06 (Dapper Drake)]], [[http://www.ubuntu.com/getubuntu/releasenotes/804|8.04 (Hardy Heron)]], [[http://www.ubuntu.com/getubuntu/releasenotes/810|8.10 (Intrepid Ibex)]], [[http://www.ubuntu.com/getubuntu/releasenotes/904|9.04 (Jaunty Jackalope)]], [[http://www.ubuntu.com/getubuntu/releasenotes/910|9.10 (Karmic Koala)]],[[http://www.ubuntu.com/getubuntu/releasenotes/1004|10.04 (Lucid Lynx)]] . If you have further information about an already reported bug, add this information to the existing reported bug, instead of opening a new one. [[#Top|Back to top]] + = Getting advice = - If you need help in finding the right package or providing appropriate information ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]]. + Still have doubts about the bug filing process? You can ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]]. [[#Top|Back to top]] + = Other languages = * [[ReportingBugs_es|Spanish]] * [[http://www.ubuntu.ro/documentatie/comunitate/RaportareErori | Romanian]] [[#Top|Back to top]] + = See Also = - * [[ http://screencasts.ubuntu.com/2009/09/16/Reporting_Bugs | A screencast on using these tools ]] by Daniel Holbach + * [[http://screencasts.ubuntu.com/2009/09/16/Reporting_Bugs|A screencast on using these tools]] by Daniel Holbach * [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to Report Bugs Effectively]], by Simon Tatham * [[Ubuntu:DebuggingProcedures|Debugging Procedures]] - [[#Top|Back to top]] - From ara at ubuntu.com Fri Sep 24 07:05:42 2010 From: ara at ubuntu.com (Ara Pulido) Date: Fri, 24 Sep 2010 09:05:42 +0200 Subject: Packages importing bug comments In-Reply-To: <20100923191808.GF2958@murraytwins.com> References: <20100923191808.GF2958@murraytwins.com> Message-ID: <4C9C4DC6.9080802@ubuntu.com> On 23/09/10 21:18, Brian Murray wrote: > I found a way to determine bugs and subsequently packages that have > imported bug comments from an upstream bug tracker and have updated the > Imported Bug Comments[1] table on the bug watches wiki page. Great! Can you tell us how? Thanks! Ara. From noreply at ubuntu.com Fri Sep 24 10:14:35 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 24 Sep 2010 10:14:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingMouseDetection=22_by_An?= =?utf-8?q?ibal_Sanchez?= Message-ID: <20100924101435.6712.75329@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 Anibal Sanchez: http://wiki.ubuntu.com/DebuggingMouseDetection?action=diff&rev1=14&rev2=15 ------------------------------------------------------------------------------ == In case your mouse stops working after a while == + 1. Test if your mouse works in a second computer. Several issues are related to your specific Bios configuration, try to disable ACPI. 1. Provide the [[#generalinfo|general information]]. 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ $ dmesg > ~/dmesg_boot From brian at ubuntu.com Fri Sep 24 16:28:14 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 24 Sep 2010 09:28:14 -0700 Subject: Packages importing bug comments In-Reply-To: <4C9C4DC6.9080802@ubuntu.com> References: <20100923191808.GF2958@murraytwins.com> <4C9C4DC6.9080802@ubuntu.com> Message-ID: <20100924162814.GK2958@murraytwins.com> On Fri, Sep 24, 2010 at 09:05:42AM +0200, Ara Pulido wrote: > > > On 23/09/10 21:18, Brian Murray wrote: > > I found a way to determine bugs and subsequently packages that have > > imported bug comments from an upstream bug tracker and have updated the > > Imported Bug Comments[1] table on the bug watches wiki page. > > Great! Can you tell us how? Well, it was really rather messy. It started with a database query to find Ubuntu bug reports with comments from the Bug Watch Updater. Then since I didn't want to write the SQL to sort out all the bug tasks I then fed those bug numbers to a python-launchpadlib script to find the bug tasks. This was really just a hack to do an initial population of the list. Going forward I'd use the ubuntu-bugs mailing list but a Launchpad bug needs to be resolved before the imported comments will appear there. -- 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 Fri Sep 24 17:36:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 24 Sep 2010 17:36:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_ilidrissi=2Eam?= =?utf-8?q?ine?= Message-ID: <20100924173634.27540.55854@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 ilidrissi.amine: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=238&rev2=239 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100930| Jaunty bugs]] || hugday-20100930 || || [[UbuntuBugDay/20100916| brasero]] || hugday-20100916 || || [[UbuntuBugDay/20100914| upgrades]] || hugday-20100914 || || [[UbuntuBugDay/20100909| apt]] || hugday-20100909 || From yofel at gmx.net Sat Sep 25 19:26:46 2010 From: yofel at gmx.net (Philip Muskovac) Date: Sat, 25 Sep 2010 21:26:46 +0200 Subject: Imported Bug Comments In-Reply-To: <20100915224208.GF2958@murraytwins.com> References: <20100915224208.GF2958@murraytwins.com> Message-ID: <1285442806.1559.3.camel@Nokia-N900-02-8> ----- Ursprüngliche Mitteilung ----- > Launchpad has had the ability to display bug comments from upstream bug > trackers for some time now but it only works with some upstreams.  I > thought it would be helpful to have a list of the Ubuntu packages in > Launchpad that are displaying bug comments from upstream bug trackers so > we can focus on forwarding these package's bugs upstream and adding the > bug watches. > > If you'd like an example of what I am talking about see > http://launchpad.net/bugs/624386.  Here we can see a wine1.2 (Ubuntu) > bug task linked to an upstream Wine bug report and the comments from the > upstream bug tracker appearing in-line. > > So if we were to make a list of packages it'd include: > > wine1.2 > wine > thunderbird > firefox > > What else? > > I am asking as this is rather hard to determine from Launchpad itself - > at least as far as I can tell.  You can find bug mail about imported > comments by looking for mail from "Bug Watch Updater" and with the body > "Launchpad has imported" some number "comments from the remote bug". > When I was filtering "Launchpad has imported" returned no false > positives. > > I think posting to the list is a good way to build an initial list, as > it'll help people learn about the packages, and then we can make a wiki > page with them. > > Thanks! > > -- > Brian Murray > Ubuntu Bug Master The initial synchronization phase seems to have passed, but I'm still gettin quite a few bugwatcher updates. Is there a way to disable those mails? As I follow upstream reports that I'm interested in directly those mails only fill up my mailbox without having any value to me. And just because I subscribe to an Ubuntu bug doesn't mean I want to have the whole upstream discussion pushed onto me. It might be a nice feature for most members, but not for me. Regards, Philip. From noreply at ubuntu.com Mon Sep 27 15:38:03 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 27 Sep 2010 15:38:03 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_hggd?= =?utf-8?q?h2?= Message-ID: <20100927153803.11735.80961@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/DebuggingProgramCrash?action=diff&rev1=105&rev2=106 The comment on the change is: updated list-symbol-packages.sh (work in progress) ------------------------------------------------------------------------------ }}} You can also use the Synaptic Package Manager to search for 'yelp-dbgsym' and install it from there. - The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace. You can download the [[attachment:list-dbgsym-packages.sh]] shell script and run it (after a chmod a+x list-symbols-packages.sh) this way: + The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace. You can download the [[attachment:list-dbgsym-packages-v2.sh]] shell script and run it (after a chmod a+x list-symbols-packages-v2.sh) this way: + + /!\ we updated [[attachment:list-dbgsym-packages-v2.sh]] to list-symbols-packages-v2.sh. This is the first change to make it compatible with newer GDB (which does not, by default, load all libraries at start anymore). -v2 is currently only working if you run it against a currently-executing binary (i.e., with '-p $(pidof '). + {{{ - bash list-symbols-packages.sh yelp + bash list-symbols-packages-v2.sh yelp }}} in order to obtain a more complete list of symbol packages to install. The script may also attach to a running process and in this case it gives an even more complete list of symbol packages to install, and this is recommended if the problem you are having does not prevent you from running the program. You can usually get the process ID of a running process using pidof, so while you have yelp running you might run: {{{ - bash list-symbols-packages.sh -p $(pidof -s yelp) + bash list-symbols-packages-v2.sh -p $(pidof -s yelp) }}} to get a list of packages that should be installed for best debug information. If the running process is a server (daemon), you might have to run 'list-symbols-packages.sh' with sudo. From brian at ubuntu.com Tue Sep 28 19:12:07 2010 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Sep 2010 12:12:07 -0700 Subject: Imported Bug Comments In-Reply-To: <1285442806.1559.3.camel@Nokia-N900-02-8> References: <20100915224208.GF2958@murraytwins.com> <1285442806.1559.3.camel@Nokia-N900-02-8> Message-ID: <20100928191207.GO2958@murraytwins.com> On Sat, Sep 25, 2010 at 09:26:46PM +0200, Philip Muskovac wrote: > > ----- Ursprüngliche Mitteilung ----- > > Launchpad has had the ability to display bug comments from upstream bug > > trackers for some time now but it only works with some upstreams.  I > > thought it would be helpful to have a list of the Ubuntu packages in > > Launchpad that are displaying bug comments from upstream bug trackers so > > we can focus on forwarding these package's bugs upstream and adding the > > bug watches. > > > > If you'd like an example of what I am talking about see > > http://launchpad.net/bugs/624386.  Here we can see a wine1.2 (Ubuntu) > > bug task linked to an upstream Wine bug report and the comments from the > > upstream bug tracker appearing in-line. > > > > So if we were to make a list of packages it'd include: > > > > wine1.2 > > wine > > thunderbird > > firefox > > > > What else? > > > > I am asking as this is rather hard to determine from Launchpad itself - > > at least as far as I can tell.  You can find bug mail about imported > > comments by looking for mail from "Bug Watch Updater" and with the body > > "Launchpad has imported" some number "comments from the remote bug". > > When I was filtering "Launchpad has imported" returned no false > > positives. > > > > I think posting to the list is a good way to build an initial list, as > > it'll help people learn about the packages, and then we can make a wiki > > page with them. > > > > Thanks! > > > > -- > > Brian Murray > > Ubuntu Bug Master > > The initial synchronization phase seems to have passed, but I'm still > gettin quite a few bugwatcher updates. Is there a way to disable those > mails? As I follow upstream reports that I'm interested in directly > those mails only fill up my mailbox without having any value to me. > And just because I subscribe to an Ubuntu bug doesn't mean I want to > have the whole upstream discussion pushed onto me. It might be a nice > feature for most members, but not for me. No, there is not a way to disable just those mails on the server, Launchpad, side. You might want to report a bug about this. -- 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 ilidrissiamine at gmail.com Tue Sep 28 19:41:16 2010 From: ilidrissiamine at gmail.com (Mohamed Amine IL Idrissi) Date: Tue, 28 Sep 2010 19:41:16 +0000 Subject: Announcing the Next Ubuntu Bug Day! - 20100930 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Jaunty bugs! * 100 New bugs need a hug * 100 Incomplete bugs need a status check * 99 Confirmed bugs need a review Jaunty will go EOL soon, and as you may have noticed, lots of bugs pertaining to it are still not properly triaged. Some tidying (and testing, of course!) will be great :) Bookmark it, add it to your calendars, turn over those egg-timers! * 20100930 * http://wiki.ubuntu.com/UbuntuBugDay/20100930 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, head to http://wiki.ubuntu.com/Bugs Have a nice day, Mohamed Amine IL Idrissi [From the BugSquad] From jeremy.foshee at canonical.com Wed Sep 29 14:53:10 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Wed, 29 Sep 2010 10:53:10 -0400 Subject: Kernel Community Bug Day Tuesday 5 October 2010 Message-ID: <20100929145310.GB12047@nightcrawler> Kernel Community Bug Day Tuesday 5 October 2010 Hi Folks! The Kernel Team is pleased to announce our next bug day for Tuesday the 5th of October.[0] We will be addressing bugs in the New state that have been incorrectly set to New whether by well-meaning bug reporters or individuals incorrectly reopening a previously expired bug to the new status. In some cases the proper state is Triaged or confirmed. We will be attempting to correct the status mismatches as well as properly tagging bugs with the appropriate subsystems.[1] All triagers are welcome to assist us on this day. Any questions as to the state of a bug or any general questions can be directed to me in the #ubuntu-kernel channel on the FreeNode IRC server. You may also find useful information in the Kernel Wiki. [2] Thanks! ~JFo [0]https://wiki.ubuntu.com/Kernel/BugDay [1] https://wiki.ubuntu.com/Kernel/Tagging [2]https://wiki.ubuntu.com/Kernel/BugTriage From noreply at ubuntu.com Thu Sep 30 07:48:35 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 30 Sep 2010 07:48:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_vish?= Message-ID: <20100930074835.20126.80570@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/Importance?action=diff&rev1=22&rev2=23 The comment on the change is: Mention ubuntu-bugs channel as a hub for non-BC members to request setting bug importance ------------------------------------------------------------------------------ <> Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs. - In order to set the Importance field in [[Malone| Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. + In order to set the Importance field in [[Malone| Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. The importance of a bug report can be modified by clicking on the current Status or Importance, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new importance in the drop down box. + + ''{{{ If you're not yet an UbuntuBugControl member, you'll have to ask someone who is to do it for you. }}} + Paste the bug number in {{{#ubuntu-bugs}}} channel at FreeNode and say you think the bug should be set to importance 'Wishlist/Low/Medium/High/Critical'. Someone will notice your comment and set it for you, although not necessarily immediately. '' Below is a list of the bug importances and when to use them: