From linda.halligan at gmail.com Tue Dec 1 01:03:24 2009 From: linda.halligan at gmail.com (Linda Halligan) Date: Mon, 30 Nov 2009 17:03:24 -0800 Subject: Seattle Bug Triage Demo Volunteer Needed Message-ID: <4B146B5C.6010904@gmail.com> I'm coordinating an ubuntu bug triaging demo for those of us that are visual/hands on learners at one of the upcoming Greater Seattle Linux User Group meetings. If there are any experienced bug triagers in the Seattle area who would be willing to do a 10 minute hands on demo with a short Q & A session please email me at linda.halligan at gmail.com. Thanks, -Linda From david.planella at ubuntu.com Tue Dec 1 13:22:45 2009 From: david.planella at ubuntu.com (David Planella) Date: Tue, 01 Dec 2009 14:22:45 +0100 Subject: Proposed HugDay target: language packs In-Reply-To: <1259067017.21537.54.camel@lenovo> References: <1259067017.21537.54.camel@lenovo> Message-ID: <1259673765.30592.96.camel@lenovo> El dt 24 de 11 de 2009 a les 13:50 +0100, en/na David Planella va escriure: > Am Samstag, den 21.11.2009, 11:34 +0100 schrieb Sense Hofstede: > > Hello, > > > > I would like to propose to held a BugDay for language packs. > > Localisation is an important part of Ubuntu and many users wouldn't > > even be able to use it without the translations. Therefore it is > > important that the language packages and the translations are in good > > shape. > > Holding a BugDay about language packs would be a good way to do this. > > Since there are usually not that many bugs reported against the > > language packs, it makes sense to have one BugDay for all. > > > > I've added the idea to the proposed planning on > > https://wiki.ubuntu.com/UbuntuBugDay/Planning (which probably needs to > > be updated, Nautilus' BugDay has already passed). > > > > Regards, > > -- > > Sense Hofstede > > /ˈsen.sɜː ˈhɒf.steɪdɜː/ > > > > Hi Sense, > > I cannot agree more on this. The translations team already started > running a "Kubuntu Translations Day" last cycle, which was essentially a > hug day targeted to Kubuntu translations. However, it might make sense > to make it more general and make translations a more or less regular > target for Hug Days. > > Regarding the proposal on language packs, just a couple of notes: > > * Ubuntu Translations project. We generally do not (or encourage > to) report bugs on language packs, unless a bug affects a > particular one of them. We report all translations-related bugs > against the ubuntu-translations project in Launchpad, which > would be a better target for the Hug Day: > https://bugs.launchpad.net/ubuntu-translations/ > > * Reporting translation bugs. Some time ago, a member of the > translation team added general instructions on how to report > translation bugs to the ReportingBugs page at > https://help.ubuntu.com/community/ReportingBugs#Filing% > 20translation%20bugs. This has worked well so far in terms of > filed reports, but I'd like to ask the bugsquad whether you > think that is appropriate and to review the text we used, since > that page is very visible to users. > > * Date. You were proposing the 26th Nov (in two days time), but > since it has been a very hectic period coming from UDS, I'd > rather propose it for the Thursday of the coming week (3rd Dec), > so that there is time for the announcement as well - I could > imagine that some translators would be interested in > participating. I went ahead and changed the proposed date - let > me know what you think. > > That's all, I'll be looking forward to your comments and thanks for your > interest on translations! > > Regards, > David. > Hi all, Has anyone had the chance to consider this proposal? Thanks! Regards, David. -- David Planella Ubuntu Translations Coordinator david(dot)planella(at)ubuntu(dot)com www.ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 489 bytes Desc: Això és una part d'un missatge signada digitalment URL: From pedro at ubuntu.com Tue Dec 1 14:20:11 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 01 Dec 2009 11:20:11 -0300 Subject: Proposed HugDay target: language packs In-Reply-To: <1259673765.30592.96.camel@lenovo> References: <1259067017.21537.54.camel@lenovo> <1259673765.30592.96.camel@lenovo> Message-ID: <1259677211.8291.3.camel@wombat> Hola David, On Tue, 2009-12-01 at 14:22 +0100, David Planella wrote: > Hi all, > > Has anyone had the chance to consider this proposal? Yes, we'll have the bug day this Thursday (Dec 03), right now Victor Vargas (aka Kamusin) is setting up the page for it , will send it to you for comments as soon as everything is done there. Have a nice day!, pedro. From kamusin at gmail.com Tue Dec 1 18:43:15 2009 From: kamusin at gmail.com (Kamus) Date: Tue, 1 Dec 2009 15:43:15 -0300 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 03 December 2009 Message-ID: Announcing the Next Ubuntu Bug Day! - Thursday 03 December 2009 Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Ubuntu Translations! * 7 New bugs need a hug * 14 Incomplete bugs need a status check * 71 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 03 December 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20091203 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 (like me), head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud: -33.439177,-70.625267 Santiago, Chile. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Dec 1 20:22:26 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 1 Dec 2009 12:22:26 -0800 Subject: Translation help Message-ID: <20091201202226.GO5381@murraytwins.com> Occasionally, we receive bugs reported about Ubuntu in a foreign language and while I don't want to encourage this widely I also feel like we should attempt to help the reporter. Additionally, there are frequently log files, like in apport-package bug reports, that are in a foreign language. While we could ask the reporter to translate both of these themselves I wonder if there is some way Ubuntu translators can help us out? If so how can we get assistance with these bug reports? Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrooney at gmail.com Tue Dec 1 20:34:05 2009 From: mrooney at gmail.com (Mike Rooney) Date: Tue, 1 Dec 2009 12:34:05 -0800 Subject: New tag for bugs that have bounties on them In-Reply-To: References: Message-ID: <4f4806ee0912011234i73f3146bt33b5ab14dd87e8ea@mail.gmail.com> On Sun, Nov 29, 2009 at 10:08 AM, Shahar Or wrote: > Dear BugSquad, > > I'm beginning now to add the 'bounty' tag to bugs which have bounties on them. > > May I add this to the official list of tags in > https://wiki.ubuntu.com/Bugs/Tags ? > Being able to search by bugs with bounties is fairly interesting, though I'm not sure what the official stance is on making a new "official" tag. It seems like we would want to have specific guildelines on which bugs have a bounty, ie a bug which has a bounty listed on an official website (such as FOSS Factory), and not just someone saying, "I'll pay $100 to whoever fixes this!" and then having that person disappear when the bug is fixed. It seems like in the ideal world this is really something for Launchpad, where it would have support for linking to bounties from bugs/tasks, with integration for certain bounty sites, like you can do today with upstream bug reports. Does anyone else have any thoughts? -- Michael Rooney mrooney at gmail.com From mrooney at gmail.com Tue Dec 1 20:44:56 2009 From: mrooney at gmail.com (Mike Rooney) Date: Tue, 1 Dec 2009 12:44:56 -0800 Subject: Translation help In-Reply-To: <20091201202226.GO5381@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> Message-ID: <4f4806ee0912011244j2824818escfcdc41d074ec01e@mail.gmail.com> On Tue, Dec 1, 2009 at 12:22 PM, Brian Murray wrote: > Occasionally, we receive bugs reported about Ubuntu in a foreign > language and while I don't want to encourage this widely I also feel > like we should attempt to help the reporter.  Additionally, there are > frequently log files, like in apport-package bug reports, that are in a > foreign language. > > While we could ask the reporter to translate both of these themselves I > wonder if there is some way Ubuntu translators can help us out?  If so > how can we get assistance with these bug reports? > I thought at one point we had tags for this, something like needs-translation that we were using, though I don't remember if they were language specific or not. Ideally it would be integrated into the Ubuntu Translators workflow so it wasn't something extra for them to remember to have to do. -- Michael Rooney mrooney at ubuntu.com Sent from San Mateo, CA, United States From ben.root at ou.edu Tue Dec 1 20:47:02 2009 From: ben.root at ou.edu (Benjamin Root) Date: Tue, 1 Dec 2009 14:47:02 -0600 Subject: New tag for bugs that have bounties on them In-Reply-To: <4f4806ee0912011234i73f3146bt33b5ab14dd87e8ea@mail.gmail.com> References: <4f4806ee0912011234i73f3146bt33b5ab14dd87e8ea@mail.gmail.com> Message-ID: <6a7d07ce0912011247j56ff3efr4c4af371b371691d@mail.gmail.com> Quite honestly, I am very hesitant to see a bounty approach done to bug fixing. First of all, true bounty work should probably involve an escrow-like service like PayPal. Even then, I wonder what determines success for a bug fix? And what if the bug resurfaces? Does the person who place the bounty get to request a "return"? Also, would this encourage 'quick fixes' instead of proper patches? Just my two cents... WeatherGod On Tue, Dec 1, 2009 at 2:34 PM, Mike Rooney wrote: > On Sun, Nov 29, 2009 at 10:08 AM, Shahar Or > wrote: > > Dear BugSquad, > > > > I'm beginning now to add the 'bounty' tag to bugs which have bounties on > them. > > > > May I add this to the official list of tags in > > https://wiki.ubuntu.com/Bugs/Tags ? > > > > > Being able to search by bugs with bounties is fairly interesting, > though I'm not sure what the official stance is on making a new > "official" tag. > > It seems like we would want to have specific guildelines on which bugs > have a bounty, ie a bug which has a bounty listed on an official > website (such as FOSS Factory), and not just someone saying, "I'll pay > $100 to whoever fixes this!" and then having that person disappear > when the bug is fixed. > > It seems like in the ideal world this is really something for > Launchpad, where it would have support for linking to bounties from > bugs/tasks, with integration for certain bounty sites, like you can do > today with upstream bug reports. > > Does anyone else have any thoughts? > > -- > Michael Rooney > mrooney at gmail.com > > -- > 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 ben.root at ou.edu Tue Dec 1 20:49:57 2009 From: ben.root at ou.edu (Benjamin Root) Date: Tue, 1 Dec 2009 14:49:57 -0600 Subject: Translation help In-Reply-To: <4f4806ee0912011244j2824818escfcdc41d074ec01e@mail.gmail.com> References: <20091201202226.GO5381@murraytwins.com> <4f4806ee0912011244j2824818escfcdc41d074ec01e@mail.gmail.com> Message-ID: <6a7d07ce0912011249p2aa20b50m577e20ff876f4b44@mail.gmail.com> For me, I have had a lot of success with highlighting the text and using Google to do the translation. Usually, I can then get enough of an idea to send a reply back verifying my interpretation of the problem. At that point, the conversation usually continues in English. WeatherGod On Tue, Dec 1, 2009 at 2:44 PM, Mike Rooney wrote: > On Tue, Dec 1, 2009 at 12:22 PM, Brian Murray wrote: > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > language and while I don't want to encourage this widely I also feel > > like we should attempt to help the reporter. Additionally, there are > > frequently log files, like in apport-package bug reports, that are in a > > foreign language. > > > > While we could ask the reporter to translate both of these themselves I > > wonder if there is some way Ubuntu translators can help us out? If so > > how can we get assistance with these bug reports? > > > > I thought at one point we had tags for this, something like > needs-translation that we were using, though I don't remember if they > were language specific or not. > > Ideally it would be integrated into the Ubuntu Translators workflow so > it wasn't something extra for them to remember to have to do. > > -- > Michael Rooney > mrooney at ubuntu.com > Sent from San Mateo, CA, United States > > -- > 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 ubuntu.bugsquad at micahscomputing.com Tue Dec 1 20:50:44 2009 From: ubuntu.bugsquad at micahscomputing.com (Micah Gersten) Date: Tue, 01 Dec 2009 14:50:44 -0600 Subject: New tag for bugs that have bounties on them In-Reply-To: <4f4806ee0912011234i73f3146bt33b5ab14dd87e8ea@mail.gmail.com> References: <4f4806ee0912011234i73f3146bt33b5ab14dd87e8ea@mail.gmail.com> Message-ID: <4B1581A4.9030804@micahscomputing.com> Mike Rooney wrote: > On Sun, Nov 29, 2009 at 10:08 AM, Shahar Or wrote: >> Dear BugSquad, >> >> I'm beginning now to add the 'bounty' tag to bugs which have bounties on them. >> >> May I add this to the official list of tags in >> https://wiki.ubuntu.com/Bugs/Tags ? >> > > > Being able to search by bugs with bounties is fairly interesting, > though I'm not sure what the official stance is on making a new > "official" tag. > > It seems like we would want to have specific guildelines on which bugs > have a bounty, ie a bug which has a bounty listed on an official > website (such as FOSS Factory), and not just someone saying, "I'll pay > $100 to whoever fixes this!" and then having that person disappear > when the bug is fixed. > > It seems like in the ideal world this is really something for > Launchpad, where it would have support for linking to bounties from > bugs/tasks, with integration for certain bounty sites, like you can do > today with upstream bug reports. > > Does anyone else have any thoughts? > I agree. I think this would have to be done by Launchpad, if at all. I think both Sourceforge and Mantis support this, but I don't know how useful it is. From sense at qense.nl Tue Dec 1 20:54:13 2009 From: sense at qense.nl (Sense Hofstede) Date: Tue, 1 Dec 2009 21:54:13 +0100 Subject: Translation help In-Reply-To: <20091201202226.GO5381@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> Message-ID: 2009/12/1 Brian Murray : > Occasionally, we receive bugs reported about Ubuntu in a foreign > language and while I don't want to encourage this widely I also feel > like we should attempt to help the reporter.  Additionally, there are > frequently log files, like in apport-package bug reports, that are in a > foreign language. > > While we could ask the reporter to translate both of these themselves I > wonder if there is some way Ubuntu translators can help us out?  If so > how can we get assistance with these bug reports? > > Thanks, > -- > Brian Murray                                                 @ubuntu.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAksVewIACgkQDTAwc5ER+zVHjACgjvCi5B4ezY4WWHZe40BtsOli > +wAAoNjzlnwH5kM9+3ug28DhlWor3fbu > =xAyP > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Is it possible to subscribe to tags? In that case you could make it an extra, small task you can help the Bug Squad with. Translators and triagers could then subscribe to the tags of the languages they speak and are willing to translate bug descriptions from. If not, I think we should just use IRC and personal memory of languages other triagers can speak. We don't receive non-English bug reports that often, so it is not our greatest problem. Although Google Translate can be useful if you just want to know what's being said, I wouldn't advice to use it when communicating. Instead we should encourage people who speak the language reasonably well to handle these kinds of bugs. Regards, -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ From ubuntu.bugsquad at micahscomputing.com Tue Dec 1 20:58:45 2009 From: ubuntu.bugsquad at micahscomputing.com (Micah Gersten) Date: Tue, 01 Dec 2009 14:58:45 -0600 Subject: Translation help Message-ID: <4B158385.3020303@micahscomputing.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sense Hofstede wrote: > Is it possible to subscribe to tags? In that case you could make it an > extra, small task you can help the Bug Squad with. Translators and > triagers could then subscribe to the tags of the languages they speak > and are willing to translate bug descriptions from. > If not, I think we should just use IRC and personal memory of > languages other triagers can speak. We don't receive non-English bug > reports that often, so it is not our greatest problem. > > Although Google Translate can be useful if you just want to know > what's being said, I wouldn't advice to use it when communicating. > Instead we should encourage people who speak the language reasonably > well to handle these kinds of bugs. > > Regards, https://bugs.launchpad.net/malone/+bug/151129 is the bug open about subscribing to tags. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAksVg4UACgkQTniv4aqX/VmsdQCfW9f6hORHnxyk15p3HMyhaWXl XnYAn1S1/stCxTVB2Gx1zPBmXyvyq8M3 =229L -----END PGP SIGNATURE----- From shahar at shahar-or.co.il Tue Dec 1 21:18:00 2009 From: shahar at shahar-or.co.il (Shahar Or) Date: Tue, 1 Dec 2009 23:18:00 +0200 Subject: New tag for bugs that have bounties on them In-Reply-To: References: Message-ID: In the mean-time, look: https://launchpad.net/ubuntu/+bugs?field.tag=bounty From cyan.spam at gmail.com Tue Dec 1 23:02:01 2009 From: cyan.spam at gmail.com (David Tombs) Date: Tue, 01 Dec 2009 18:02:01 -0500 Subject: Launchpad Bug Filing Changes for Ubuntu + reporter's thoughts In-Reply-To: <4B030BAA.1050200@ulg.ac.be> References: <20090915175319.GA6455@murraytwins.com> <4B030BAA.1050200@ulg.ac.be> Message-ID: <4B15A069.7080404@gmail.com> Hi André, Unfortunately, I don't think your report is very clear. It would be helpful to triagers to edit the bug report to include information listed in , especially steps to reproduce the problem. If you want to be really helpful in finding the source of the problem, try getting a crash backtrace as described on . Thanks, David André Pirard wrote: > On 2009-09-15 19:53, Brian Murray wrote : >> Hello everybody, >> >> As a part of the Increase Apport Adoption specification[1] we are going >> to kick off an experiment and redirect all of Ubuntu's /+filebug links >> in Launchpad to https://help.ubuntu.com/community/ReportingBugs. This >> change has been tested on staging.launchpad.net already and will be >> landing shortly on edge.launchpad.net(*). >> >> If you review the specification and the documentation bug reporters will >> be redirected to, you will notice that we spent a lot of time and energy >> on ensuring that we improve the quality of bugs when they are reported. >> The time many of us spend on triaging very incomplete bugs is not >> sustainable given the volume of bug reports. Having reporters use >> ubuntu-bug (apport more specifically) to report bugs will reduce many of >> these problems for us. >> ... > Hello, > > Before trying to improve the quality of bug reports, I would wonder > what happens to bugs that are perfectly reported already. > > Among many, an example of a developer's dream of a report is : Bug > #233990 > . > Instead of simply forwarding it to development, instead of these > possibly asking the reporter for one more detail and/or test, and > instead of its being a thing done, I was asked "What is a bare > linefeed?", "Where is it?" (in the message file I uploaded), "What > happens if you erase your config?" and "What happens if you pull your > socks off before sending?". > Every answer is in the message file. > After 1.5 year, the report is said to be incomplete, marked for > expiration 47 days ago, the bug is still well alive, and, of course, > the reporter is frustrated and less a reporter. > > Even more so because many sites implement OpenID server but not > client, a plain user cannot conceivably subscribe to tens of upstream > sites and learn their specifics each time. Ubuntu's specialized > people should cope with those administrative details, each in their > specialized field, so that Launchpad be the single interface through > which the user can dialog with the developer (or the other way round > if you prefer :-)) > Automatic peering(1) of messages between local and upstream case would > do wonders. > When that's not feasible, and if OpenID client were implemented in > Launchpad, it would be easier for a developer to subscribe to > Launchpad than for Ubuntu users to go there. > Because any Ubuntu user meeting a problem can use Launchpad as a means > of direct workaround and promise(2), it's better to have the problems > documented in Launchpad than to have fed-up-with-it reporters go to > other places directly. > > It's a silent thanks how many times hunting for any Linux information > lands on the word Ubuntu. What you all are doing is amazing and it's > my pleasure to [try to] be helpful. > > Thanks for your attention too. > > André. > > Text optimized for 17 to 190 characters wide display. > > (1) Never trust spelling checkers, I've had to add a "r" :-) > (2) Many times my answer to "there are more bugs than in Window" was > "maybe, but look how fast you find the solution". Once, Microsoft had > changed their so-called MSN server's behavior 3 days before to pest > the world and some Ubuntu had found hours later than an alternative > plugin for Pidgin was cocking a snook. > From jtniehof at gmail.com Tue Dec 1 23:36:56 2009 From: jtniehof at gmail.com (Jonathan Niehof) Date: Tue, 1 Dec 2009 18:36:56 -0500 Subject: Bug #489474 Message-ID: <1d23eef00912011536na2a58a5gde77dbbaa8c370a@mail.gmail.com> Could I get a second opinion on bug #489474, basically "Do something smart if mount -a fails"? https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/489474 I think this is an important idea but probably requires some scoping and choice between alternatives, a little outside the scope of a simple bug. Submitter disagrees :) If a third party could help triage this issue, in either direction, I'd appreciate it. Thanks! --Jon From dan.buhrman at gmail.com Tue Dec 1 23:50:12 2009 From: dan.buhrman at gmail.com (Dan Buhrman) Date: Tue, 1 Dec 2009 18:50:12 -0500 Subject: Need help with internet connection....... In-Reply-To: <52255ea30911142001s59c76812k5c7891e186d41ab2@mail.gmail.com> References: <52255ea30911142001s59c76812k5c7891e186d41ab2@mail.gmail.com> Message-ID: <9bac04310912011550x71a47af2y534148bdf078da4b@mail.gmail.com> Hi Varad, Debian-based operating systems (like Ubuntu) use apt-get instead of yum. yum is used only in RedHat-based distros. Brief overview: *sudo apt-get update* -- updates your package list -- typically, you should run this before any other command *sudo apt-get upgrade* -- updates all packages on your system to the newest version *sudo apt-get install [package_name]* -- installs a package *sudo apt-get uninstall [package_name]* -- removes a package *sudo apt-get purge [package_name]* -- removes a package and all configuration files associated with that package Also, if you prefer, you can do this all graphically with Synaptics. (System -> Administrator -> Synaptics package manager) Since it appears you are coming from a RedHat distro, I'd recommend reading through this guide, it may have some tips to help you become acclimated with Ubuntu. https://help.ubuntu.com/community/SwitchingToUbuntu/FromLinux For your Internet connection, you may want to post something on the forums. That is a great community for helping you with support issues. http://www.ubuntuforums.org/ Best Regards! Dan Buhrman On Sat, Nov 14, 2009 at 11:01 PM, Varad Mudgal wrote: > Hi ! > > I'm a greenhorn at Linux. Just installed Ubuntu 9.10 over Windows 7(using > Wubi) from the cd i received after subscribing it online. i'm facing a very > serious problem. I'm not able to access the internet. The net just doesn't > connect even if I try several times. There's no problem with my modem or > internet connection because the internet is working perfectly fine with my > windows 7. I'm using a broadband connection(BSNL) in India. I've tried a few > advices that others gave me - > > 1. I verified the IP address of the interface using the command 'ifconfig > -a'. > 2. I checked the nameservers listed in '/etc/resolv.conf' file. > > Any attempt to open a website on Mozilla Firefox brings up a 'Server not > found' error. > > Now, I'm also unable to run the 'yum' command. When I type it on the > terminal, it asks me to install the yum command giving another command and > also lists that the yum command is not found. When I try to install using > the command, an error message stating that the 'yum' package has not been > installed shows up. Perhaps I feel that some packages that come preinstalled > with any linux have not been installed with Ubuntu 9.10, hence I'm not able > to use the internet on my Ubuntu. > > Please help me out. > > Thanks in advance. > > Awaiting reply, > > Varad > > -- > 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 mrooney at gmail.com Wed Dec 2 01:13:06 2009 From: mrooney at gmail.com (Mike Rooney) Date: Tue, 1 Dec 2009 17:13:06 -0800 Subject: Bug #489474 In-Reply-To: <1d23eef00912011536na2a58a5gde77dbbaa8c370a@mail.gmail.com> References: <1d23eef00912011536na2a58a5gde77dbbaa8c370a@mail.gmail.com> Message-ID: <4f4806ee0912011713p88fc4b6h8c097fa3c645f22d@mail.gmail.com> On Tue, Dec 1, 2009 at 3:36 PM, Jonathan Niehof wrote: > Could I get a second opinion on bug #489474, basically "Do something > smart if mount -a fails"? > https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/489474 > > I think this is an important idea but probably requires some scoping > and choice between alternatives, a little outside the scope of a > simple bug. Submitter disagrees :) If a third party could help triage > this issue, in either direction, I'd appreciate it. > I've updated the bug, thanks for bringing it to our attention! -- Michael Rooney mrooney at ubuntu.com Sent from San Mateo, CA, United States From david.planella at ubuntu.com Wed Dec 2 09:09:24 2009 From: david.planella at ubuntu.com (David Planella) Date: Wed, 02 Dec 2009 10:09:24 +0100 Subject: Translation help In-Reply-To: <20091201202226.GO5381@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> Message-ID: <1259744965.30592.155.camel@lenovo> Hi all, El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va escriure: > Occasionally, we receive bugs reported about Ubuntu in a foreign > language and while I don't want to encourage this widely I also feel > like we should attempt to help the reporter. Additionally, there are > frequently log files, like in apport-package bug reports, that are in a > foreign language. > Regarding the log files, if they come from apport, I agree with Arne in the sense that ideally apport should generate them in the English (C) locale. But if I understand it correctly, that's also about logs generated by the applications themselves prior to the bug report, so that might not be that simple and they might need to be translated once they are included in the bug report anyway. > While we could ask the reporter to translate both of these themselves I > wonder if there is some way Ubuntu translators can help us out? If so > how can we get assistance with these bug reports? > > Thanks, If there is not a massive amount of such bugs, you could also forward them to the ubuntu-translators list, where you'd surely find someone speaking the language and willing to help either translating the bug or directly assisting the reporter. This has been done occasionally for Answers request in the past and IIRC worked quite well. Alternatively, you could even open a bug task against the ubuntu-translations project, and those subscribed to bugmail would forward it to the list. That said though, I think directly forwarding the bugs to the list might be a better approach. Regards, David. -- David Planella Ubuntu Translations Coordinator david(dot)planella(at)ubuntu(dot)com www.ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 489 bytes Desc: Això és una part d'un missatge signada digitalment URL: From ben.root at ou.edu Wed Dec 2 15:38:18 2009 From: ben.root at ou.edu (Benjamin Root) Date: Wed, 2 Dec 2009 09:38:18 -0600 Subject: Translation help In-Reply-To: <1259744965.30592.155.camel@lenovo> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> Message-ID: <6a7d07ce0912020738me9a3462t326bb0a1b6f11ef2@mail.gmail.com> Another reason why automatic translations of bug reports would probably be a bad idea is that you (most likely) don't want the translation to change things like filenames that are in the logs. Quite honestly, I am so used to seeing the logs of some programs that I usually know what I am looking for anyway even if they are in other languages. If the translation people think that they can handle the occasional request for a translation, I think that might be the best approach rather than changing the behavior of apport. WeatherGod 2009/12/2 David Planella > Hi all, > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > escriure: > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > language and while I don't want to encourage this widely I also feel > > like we should attempt to help the reporter. Additionally, there are > > frequently log files, like in apport-package bug reports, that are in a > > foreign language. > > > > Regarding the log files, if they come from apport, I agree with Arne in > the sense that ideally apport should generate them in the English (C) > locale. But if I understand it correctly, that's also about logs > generated by the applications themselves prior to the bug report, so > that might not be that simple and they might need to be translated once > they are included in the bug report anyway. > > > While we could ask the reporter to translate both of these themselves I > > wonder if there is some way Ubuntu translators can help us out? If so > > how can we get assistance with these bug reports? > > > > Thanks, > > If there is not a massive amount of such bugs, you could also forward > them to the ubuntu-translators list, where you'd surely find someone > speaking the language and willing to help either translating the bug or > directly assisting the reporter. This has been done occasionally for > Answers request in the past and IIRC worked quite well. Alternatively, > you could even open a bug task against the ubuntu-translations project, > and those subscribed to bugmail would forward it to the list. That said > though, I think directly forwarding the bugs to the list might be a > better approach. > > Regards, > David. > > -- > David Planella > Ubuntu Translations Coordinator > david(dot)planella(at)ubuntu(dot)com > www.ubuntu.com > > > > > -- > 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 cyan.spam at gmail.com Wed Dec 2 16:13:31 2009 From: cyan.spam at gmail.com (David Tombs) Date: Wed, 02 Dec 2009 11:13:31 -0500 Subject: mouse bug In-Reply-To: <559613.45048.qm@web45806.mail.sp1.yahoo.com> References: <559613.45048.qm@web45806.mail.sp1.yahoo.com> Message-ID: <4B16922B.3070704@gmail.com> Hi Jordan, Thanks for your report, but this mailing list is not actually for reporting bugs, just discussing them. :) Please follow the instructions at to report your problem. Thanks, David Jordan Oconnor wrote: > after about 20 to 25 minutes of using ubuntu my mouse will freeze and > in order to get it to work i would have to restart the entire > computer. i have a wireless intellimouse explorer 2.0 > From cyan.spam at gmail.com Wed Dec 2 16:14:31 2009 From: cyan.spam at gmail.com (David Tombs) Date: Wed, 02 Dec 2009 11:14:31 -0500 Subject: Proposed changes to Bugs/HowToTriage In-Reply-To: <4AF1C04C.20800@gmail.com> References: <4AF1C04C.20800@gmail.com> Message-ID: <4B169267.2030906@gmail.com> Hi again, Since I didn't receive a reply regarding this, I'll go ahead and make the changes myself in a couple hours. Is that OK with everyone? Thanks, David David Tombs wrote: > Hi Sense, > > I just noticed this email rotting in my inbox and realized no one ever > replied to you! > > I took a look at your changes and think they're fantastic. The page is > much easier to comprehend when it's more organized. I'm not in charge > here, but since no one said "no", I'd suggest going ahead and making the > changes. > > Thanks for your help! > > David > > Sense Hofstede wrote: >> Hello, >> >> The HowToTriage page is vital for new the Bugsquad because a lot of >> new people use it as base resource for their work. However, because it >> is so important and read by everyone, it is adapted frequently. This >> resulted in a full page, and makes it hard to find the right >> information and the right section for adding new information. >> I've restructured the whole page and rewritten some sections to make >> it easier to read and extend. Because this page is so important I >> didn't submit it right away but first want to ask if it's okay and >> what you think of it. >> >> The wiki source is attached. >> >> Regards, >> -- >> Sense Hofstede >> /ˈsen.sɜː ˈhɒf.steɪdɜː/ > From sense at qense.nl Wed Dec 2 18:12:25 2009 From: sense at qense.nl (Sense Hofstede) Date: Wed, 2 Dec 2009 19:12:25 +0100 Subject: Translation help In-Reply-To: <1259744965.30592.155.camel@lenovo> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> Message-ID: 2009/12/2 David Planella : > Hi all, > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > escriure: >> Occasionally, we receive bugs reported about Ubuntu in a foreign >> language and while I don't want to encourage this widely I also feel >> like we should attempt to help the reporter.  Additionally, there are >> frequently log files, like in apport-package bug reports, that are in a >> foreign language. >> > > Regarding the log files, if they come from apport, I agree with Arne in > the sense that ideally apport should generate them in the English (C) > locale. But if I understand it correctly, that's also about logs > generated by the applications themselves prior to the bug report, so > that might not be that simple and they might need to be translated once > they are included in the bug report anyway. > >> While we could ask the reporter to translate both of these themselves I >> wonder if there is some way Ubuntu translators can help us out?  If so >> how can we get assistance with these bug reports? >> >> Thanks, > > If there is not a massive amount of such bugs, you could also forward > them to the ubuntu-translators list, where you'd surely find someone > speaking the language and willing to help either translating the bug or > directly assisting the reporter. This has been done occasionally for > Answers request in the past and IIRC worked quite well. Alternatively, > you could even open a bug task against the ubuntu-translations project, > and those subscribed to bugmail would forward it to the list. That said > though, I think directly forwarding the bugs to the list might be a > better approach. > > Regards, > David. > > -- > David Planella > Ubuntu Translations Coordinator > david(dot)planella(at)ubuntu(dot)com > www.ubuntu.com > > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Isn't there something like inverse gettext that Apport could use to translate the error messages? -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ From brian at ubuntu.com Wed Dec 2 18:58:51 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 Dec 2009 10:58:51 -0800 Subject: Translation help In-Reply-To: <1259744965.30592.155.camel@lenovo> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> Message-ID: <20091202185851.GY5381@murraytwins.com> On Wed, Dec 02, 2009 at 10:09:24AM +0100, David Planella wrote: > Hi all, > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > escriure: > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > language and while I don't want to encourage this widely I also feel > > like we should attempt to help the reporter. Additionally, there are > > frequently log files, like in apport-package bug reports, that are in a > > foreign language. > > > > Regarding the log files, if they come from apport, I agree with Arne in > the sense that ideally apport should generate them in the English (C) > locale. This does in fact happen. > But if I understand it correctly, that's also about logs generated by > the applications themselves prior to the bug report, so that might not > be that simple and they might need to be translated once they are > included in the bug report anyway. Yes, that is correct, for example consider http://launchpad.net/bugs/491387 where the DpkgTerminalLog.txt is not in English. > > While we could ask the reporter to translate both of these themselves I > > wonder if there is some way Ubuntu translators can help us out? If so > > how can we get assistance with these bug reports? > > > > Thanks, > > If there is not a massive amount of such bugs, you could also forward > them to the ubuntu-translators list, where you'd surely find someone > speaking the language and willing to help either translating the bug or > directly assisting the reporter. This has been done occasionally for > Answers request in the past and IIRC worked quite well. Alternatively, > you could even open a bug task against the ubuntu-translations project, > and those subscribed to bugmail would forward it to the list. That said > though, I think directly forwarding the bugs to the list might be a > better approach. Hmm, this seems a bit unwieldy to me - I was hoping for a solution with in Launchpad. Using my example from above presumably the translations for the messages in DpkgTerminaLog exist in Launchpad. Is there some way to search for them and find out the English equivalent? Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrooney at gmail.com Wed Dec 2 19:52:46 2009 From: mrooney at gmail.com (Mike Rooney) Date: Wed, 2 Dec 2009 11:52:46 -0800 Subject: Proposed changes to Bugs/HowToTriage In-Reply-To: <4B169267.2030906@gmail.com> References: <4AF1C04C.20800@gmail.com> <4B169267.2030906@gmail.com> Message-ID: <4f4806ee0912021152m3e688274id48cb46116d71a45@mail.gmail.com> On Wed, Dec 2, 2009 at 8:14 AM, David Tombs wrote: > Since I didn't receive a reply regarding this, I'll go ahead and make > the changes myself in a couple hours. Is that OK with everyone? Sounds good to me! -- Michael Rooney mrooney at ubuntu.com Sent from San Mateo, CA, United States From cyan.spam at gmail.com Wed Dec 2 23:32:51 2009 From: cyan.spam at gmail.com (David Tombs) Date: Wed, 02 Dec 2009 18:32:51 -0500 Subject: Proposed changes to Bugs/HowToTriage In-Reply-To: <4f4806ee0912021152m3e688274id48cb46116d71a45@mail.gmail.com> References: <4AF1C04C.20800@gmail.com> <4B169267.2030906@gmail.com> <4f4806ee0912021152m3e688274id48cb46116d71a45@mail.gmail.com> Message-ID: <4B16F923.7010207@gmail.com> Done! I included updates to the page since Sense wrote the revised version. Thank you, Sense! David Mike Rooney wrote: > On Wed, Dec 2, 2009 at 8:14 AM, David Tombs wrote: > >> Since I didn't receive a reply regarding this, I'll go ahead and make >> the changes myself in a couple hours. Is that OK with everyone? >> > > Sounds good to me! > > From A.Pirard at ulg.ac.be Wed Dec 2 07:23:33 2009 From: A.Pirard at ulg.ac.be (=?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=) Date: Wed, 02 Dec 2009 08:23:33 +0100 Subject: Launchpad Bug Filing Changes for Ubuntu + reporter's thoughts In-Reply-To: <4B15A069.7080404@gmail.com> References: <20090915175319.GA6455@murraytwins.com> <4B030BAA.1050200@ulg.ac.be> <4B15A069.7080404@gmail.com> Message-ID: <4B1615F5.7030007@ulg.ac.be> On 2009-12-02 00:02, David Tombs wrote : > Hi André, > > Unfortunately, I don't think your report is very clear. It would be > helpful to triagers to edit the bug report to include information > listed in > , > especially steps to reproduce the problem. > > If you want to be really helpful in finding the source of the problem, > try getting a crash backtrace as described on > . > > Thanks, > David David, Click here in case of any problem reading my xmglish. Thanks for your reply, David, but, after reading this reply **carefully**, please wonder if the problem isn't that ... (below) 1. the main point of my message below was more than this particular example (rest of this message to be read in parallel with https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/233990) 2. Regarding this particular bug report, *no, I'm afraid the report couldn't be any clearer :* * The problem is that Qmail refuses a Receipt reply sent by Thunderbird because it contains a bare lf. * What better or more could I have included than o the version of Thunderbird and Qmail o the Alert message from Thunderbird quoting a message from Qmail o the URL explaining what Qmail's complaint is all about o the contents of the e-mail that was being sent, showing : + the Bare lf + the whole of the Receipt + hence, the header of the original message being acknowledged o and a developer may of course ask me any unforeseen detail of my environment (providers used etc...) * The problem with the report is that they asked : o "what is the bare lf in the example you attached?" + the full explanation is for everyone to see in # mdnmsg, # Screenshot-alert # and http://cr.yp.to/docs/smtplf.html o "http://cr.yp.to/docs/smtplf.html does not show a dialog box. can you please give us a screenshot of the problem." + of course, it doesn't, smtplf.html is D. J. Bernstein's words, all about Qmail + Thunderbird's screenshot is in Screenshot-alert.png, of course o "Does this happen if you make a new profile with thunderbird-2.0.0.21?" + I usually upgrade with much caution and that's time consuming + So, no I didn't check every other release all along this one and a half year + I suppose i's safer and much quicker to # check bug reports and release notes # or simply report them + After clicking Help/Release Notes, I have been unable to find the usual list of fixes for R2 + so, I don't blame anyone for not having found them either + Yes it most probably still happens. This is what usually happens, plus one more inconvenience or two, after such a just-in-case test. o "Here is a list of upstream bugs that may be related to yours. Can you please take a look and make sure none are yours https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=mdn + None is (looking up with /mdn/). + But searching for /bare/ shows that Thunderbird does have several issues with bare things that they call CR, linefeed and newline (how can a /newline/ be a CR, a LF or a CRLF and be /bare/ ???) # *Bug 383565* # *Bug 441260* # *Bug 301010* # but nothing like our problem* * ** + BTW, compare the contents of this report (esp. URL) with mine and your requirements. # I've just sent a email to two attached images in it and it sent ok, but it was unable to copy to the sent folder. I've seen this a couple of times before. Now i've got a IMAP log of it. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070606 Thunderbird/3.0a1pre ID:2007060603 [cairo] log can be found here: http://gemal.dk/test/imapmaillog.txt 3. Now you speak of * the crash, which is not the point of the report o I changed the bug's title and description to dissipate this new confusion * following standard bug reporting methods : o BTW, if Thunderbird's report were like Firefoxes' /Help/Report a problem/ + it would attach data that # it doesn't show me # I will not be able to remove # may contain private data # I won't send for that reason (without checking it first) # is probably irrelevant beside version # in this case anyway # will not contain any of the essential stuff that I attached o what your https://help.ubuntu.com/community/ReportingBugs#Writing%20a%20useful%20report is asking : Please note that it's most often easier to first describe what happened and then pinpoint what should've been. I wonder why those instructions are not in that order. So please read my answers in 2-1-3 order, else you won't understand 1 1. What you expected to happen + obviously, Thunderbird not doing that 2. What actually happened + obviously, according to my # "Thunderbird 2.0.0.14 sends the attached Receipt message", # file mdnmsg Thunderbird was trying to send a Receipt + contained in mdnmsg obviously, this was in reply to the message whose header is within the same file + obviously, "qmail... complains that it contains a "bare lf" and Screenshot-alert show that # Qmail didn't like the bare lf and refused to sens the message # because of not respecting 822bis, that is sending bare linefeeds + "Receipt never arrives" means that the requested Receipt was not sent at that time + "and Thunderbird forgets about it" is, I believe, an English expression (sorry, not my language) saying that TB will behave as if Receipt had been sent (that is, never try to send it again) 3. The minimal series of steps necessary to make it happen + obviously, receive a similar message and allow sending the Receipt, + however, # the contents and events may depend on specifics of my setup, for example * my receiving the message from one provider and sending Receipt through another # but only a developer can have such guesses based on his code and my example # so, I've been sitting here for one and a half year waiting for their possible questions # which didn't happen ... that one didn't read carefully the few lines that were sufficient to precisely describe this problem entirely. OK, mea culpa, mea maxima culpa, I have mentioned (or not removed) the crash (2 problems in 1). But you're the first one (well, second beside me) to mention the crash. I just made changes to prevent another one. And, popping the stack down to the *MAIN* problem : * do you figure all the stuff I had to write o in a foreign language o just for this VERY SIMPLE bug alone o (in launchpad and in here) * can you imagine the number of reports for which the same happened? * do you think that it encourages large-hearted people to cooperate with Ubuntu Open Software? Once again, * I do like it very much when a Google search finds its top answers coming from the Ubuntu community * I do like it very much less when, for example, reading o "This bug is a duplicate" (all done for me) but closing without setting "of which one" (where to continue reading) o "Problem solved", but without any practical, precise explanation of what the user must do correct the problem except abandoning his LTS choice and waiting for the next release in 3 months. o 1 1/2 yo, ... * I'm doing my best to help. Thanks for your attention, and, again : What you all are doing is amazing and it's my pleasure to [try to] be helpful. Or rather : * What you all are doing is amazing and it's my pleasure to [try to] be helpful. * Thank you ;-) André. PS : Coincidence? * I just saw the following moves to Bug #233990 : o Matthew Paul Thomas : incomplete -> new o Aaron C. de Bruyn : new -> confirmed * good luck, bug * and I wish our speech could be as structured as our words * ;-) > André Pirard wrote: >> On 2009-09-15 19:53, Brian Murray wrote : >>> Hello everybody, >>> >>> As a part of the Increase Apport Adoption specification[1] we are going >>> to kick off an experiment and redirect all of Ubuntu's /+filebug links >>> in Launchpad to https://help.ubuntu.com/community/ReportingBugs. This >>> change has been tested on staging.launchpad.net already and will be >>> landing shortly on edge.launchpad.net(*). >>> >>> If you review the specification and the documentation bug reporters >>> will >>> be redirected to, you will notice that we spent a lot of time and >>> energy >>> on ensuring that we improve the quality of bugs when they are reported. >>> The time many of us spend on triaging very incomplete bugs is not >>> sustainable given the volume of bug reports. Having reporters use >>> ubuntu-bug (apport more specifically) to report bugs will reduce >>> many of >>> these problems for us. >>> ... >> Hello, >> >> Before trying to improve the quality of bug reports, I would wonder >> what happens to bugs that are perfectly reported already. >> >> Among many, an example of a developer's dream of a report is : Bug >> #233990 >> . >> () >> Instead of simply forwarding it to development, instead of these >> possibly asking the reporter for one more detail and/or test, and >> instead of its being a thing done, I was asked "What is a bare >> linefeed?", "Where is it?" (in the message file I uploaded), "What >> happens if you erase your config?" and "What happens if you pull your >> socks off before sending?". >> Every answer is in the message file. >> After 1.5 year, the report is said to be incomplete, marked for >> expiration 47 days ago, the bug is still well alive, and, of course, >> the reporter is frustrated and less a reporter. >> >> Even more so because many sites implement OpenID server but not >> client, a plain user cannot conceivably subscribe to tens of upstream >> sites and learn their specifics each time. Ubuntu's specialized >> people should cope with those administrative details, each in their >> specialized field, so that Launchpad be the single interface through >> which the user can dialog with the developer (or the other way round >> if you prefer :-)) >> Automatic peering(1) of messages between local and upstream case >> would do wonders. >> When that's not feasible, and if OpenID client were implemented in >> Launchpad, it would be easier for a developer to subscribe to >> Launchpad than for Ubuntu users to go there. >> Because any Ubuntu user meeting a problem can use Launchpad as a >> means of direct workaround and promise(2), it's better to have the >> problems documented in Launchpad than to have fed-up-with-it >> reporters go to other places directly. >> >> It's a silent thanks how many times hunting for any Linux information >> lands on the word Ubuntu. What you all are doing is amazing and it's >> my pleasure to [try to] be helpful. >> >> Thanks for your attention too. >> >> André. >> >> Text optimized for 17 to 190 characters wide display. >> >> (1) Never trust spelling checkers, I've had to add a "r" :-) >> (2) Many times my answer to "there are more bugs than in Window" was >> "maybe, but look how fast you find the solution". Once, Microsoft >> had changed their so-called MSN server's behavior 3 days before to >> pest the world and some Ubuntu had found hours later than an >> alternative plugin for Pidgin was cocking a snook. >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From arne.goetje at canonical.com Wed Dec 2 01:09:45 2009 From: arne.goetje at canonical.com (Arne Goetje) Date: Wed, 02 Dec 2009 09:09:45 +0800 Subject: Translation help In-Reply-To: <20091201202226.GO5381@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> Message-ID: <4B15BE59.6070508@canonical.com> Brian Murray wrote: > Occasionally, we receive bugs reported about Ubuntu in a foreign > language and while I don't want to encourage this widely I also feel > like we should attempt to help the reporter. Additionally, there are > frequently log files, like in apport-package bug reports, that are in a > foreign language. > > While we could ask the reporter to translate both of these themselves I > wonder if there is some way Ubuntu translators can help us out? If so > how can we get assistance with these bug reports? I think what we really want is apport to always collect information using the C locale. So, shouldn't this be a feature request/bug report for apport? Cheers Arne -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From sense at qense.nl Thu Dec 3 19:27:54 2009 From: sense at qense.nl (Sense Hofstede) Date: Thu, 3 Dec 2009 20:27:54 +0100 Subject: Ubuntu Translation bug handling process Message-ID: Hello, Browsing the BugDay of this day[1] I can't help but feel that a lot of these bugs have appeared on the list because the ubuntu-translators project doesn't want to use or cannot set importance and the Triaged status. I suspect the latest. This means that the status of the bug reports that are mainly handled by Ubuntu Translators will continue to pop up on search results like the one used for the lists of this BugDay. The triaging process for translation bugs is further complicated by the requirement to report it both against the source package of the affected application and the ubuntu-translations project. This forces us to maintain two sets of statuses, each subject to the rule of a different team. This causes confusion. Then there is the problem of the difference between translations made at Launchpad and translations made upstream. Some bugs have to be fixed here, some have to be forwarded upstream. I suggest to make the process of reporting more clear by implementing the following changes: 1. The starting point of all translation bugs -- unless you know better already -- can still be the source package of the affected application. 2. No extra tasks for bugs in upstream translations, this only adds extra clutter to the overview, generates extra mail noise and generates more work and confusion. 3. Bugs in translations done at Launchpad should be reported against ubuntu-translations and keep the source package task, because: 4. The source package task is for maintaining the status of the bug concerning the system -- i.e. if the bug has been Triaged(=reported properly upstream or at ubuntu-translations) or if the Fix is Released -- the ubuntu-translations task should be for the status of the fix in Rosetta or the team only 4b. This means that translation bugs always need to be 'forwarded upstream', be it to real upstreams or to ubuntu-translations. This is what the triagers should focus on when triaging these bugs. 5. Responsible for setting the status in ubuntu-translations are their (appointed?) members, responsible for the source package task is Bug Control (and the Bugsquad). Some members of ubuntu-translations that are very active on Launchpad/Malone could be granted membership of Ubuntu Bugcontrol -- if they don't already are a member -- to make it easier for them to manage the source package tasks. 6. Use the Triaged status for the source package when the Bugsquad doesn't need to do any work on it anymore! These points don't add a lot of new stuff, but things would be a bit clearer if both teams would agree on them and integrate them into the documentation. [1] https://wiki.ubuntu.com/UbuntuBugDay/20091203 Regards, -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ From robertwlt10 at aol.com Thu Dec 3 20:46:01 2009 From: robertwlt10 at aol.com (Robert W. Walthers Jr.) Date: Thu, 03 Dec 2009 15:46:01 -0500 Subject: No subject Message-ID: <1259873161.15727.0.camel@rob0917-desktop> From leann.ogasawara at canonical.com Thu Dec 3 23:32:25 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Thu, 03 Dec 2009 15:32:25 -0800 Subject: Kernel Bug Day - Tues 08 Dec, 2009 Message-ID: <1259883145.4629.178.camel@emiko> Hi Everyone, This is a friendly reminder that we're starting up Kernel Bug Day's again for the Lucid cycle. Don't know what a Kernel Bug Day is [1]? This is the perfect opportunity to find out what it's all about! The next Kernel Bug Day will be held Tues. 08 Dec, 2009 [2]. We've had a few requests for kernel bug day topics and have decided to target bugs with patches attached. Lets focus on getting these bugs fixed early in the Lucid 10.04 LTS development cycle. Please join us Tuesday in the #ubuntu-kernel IRC channel on FreeNode as we tackle this list of bugs together. Thanks in advance, Leann [1] https://wiki.ubuntu.com/KernelTeam/BugDay [2] https://wiki.ubuntu.com/KernelTeam/BugDay/20091208 From david.planella at ubuntu.com Fri Dec 4 08:23:48 2009 From: david.planella at ubuntu.com (David Planella) Date: Fri, 04 Dec 2009 09:23:48 +0100 Subject: Translation help In-Reply-To: <20091202185851.GY5381@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> <20091202185851.GY5381@murraytwins.com> Message-ID: <1259915028.15968.56.camel@lenovo> Hi Brian, El dc 02 de 12 de 2009 a les 10:58 -0800, en/na Brian Murray va escriure: > On Wed, Dec 02, 2009 at 10:09:24AM +0100, David Planella wrote: > > Hi all, > > > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > > escriure: > > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > > language and while I don't want to encourage this widely I also feel > > > like we should attempt to help the reporter. Additionally, there are > > > frequently log files, like in apport-package bug reports, that are in a > > > foreign language. > > > > > > > Regarding the log files, if they come from apport, I agree with Arne in > > the sense that ideally apport should generate them in the English (C) > > locale. > > This does in fact happen. > > > But if I understand it correctly, that's also about logs generated by > > the applications themselves prior to the bug report, so that might not > > be that simple and they might need to be translated once they are > > included in the bug report anyway. > > Yes, that is correct, for example consider > http://launchpad.net/bugs/491387 where the DpkgTerminalLog.txt is not in > English. > > > > While we could ask the reporter to translate both of these themselves I > > > wonder if there is some way Ubuntu translators can help us out? If so > > > how can we get assistance with these bug reports? > > > > > > Thanks, > > > > If there is not a massive amount of such bugs, you could also forward > > them to the ubuntu-translators list, where you'd surely find someone > > speaking the language and willing to help either translating the bug or > > directly assisting the reporter. This has been done occasionally for > > Answers request in the past and IIRC worked quite well. Alternatively, > > you could even open a bug task against the ubuntu-translations project, > > and those subscribed to bugmail would forward it to the list. That said > > though, I think directly forwarding the bugs to the list might be a > > better approach. > > Hmm, this seems a bit unwieldy to me - I was hoping for a solution with > in Launchpad. Using my example from above presumably the translations > for the messages in DpkgTerminaLog exist in Launchpad. Is there some > way to search for them and find out the English equivalent? > > Thanks, If you know the source package, you can search for the string in the package's translations. For the dpkg example above: https://translations.launchpad.net/ubuntu/karmic/+source/dpkg/+pots/dpkg/it/+translate?batch=10&show=all&search=Lettura+del+database If you don't know the actual package where translations come from (they might come e.g. from a library the package in the bug report is using), you can use the global search feature: https://launchpad.net/+search?field.text=Lettura+del+database In any case, both of these options might require some manual work (there is no Launchpad Translations API yet), and I'm not sure that was what you were looking for. If that'd be too time consuming to include in the bug workflow and these reports are indeed occasional, I think pointing them out in the ubuntu-translators list would still be valid (I can also ask translators if they'd be ok with that). Regards, David. -- David Planella Ubuntu Translations Coordinator david(dot)planella(at)ubuntu(dot)com www.ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 489 bytes Desc: Això és una part d'un missatge signada digitalment URL: From ericdrayer at wildblue.net Sat Dec 5 17:44:36 2009 From: ericdrayer at wildblue.net (eric) Date: Sat, 05 Dec 2009 11:44:36 -0600 Subject: right package for what might be a mother board problem Message-ID: <1260035076.4855.16.camel@eric-desktop> operating system ubuntu 9.04 amd64 video card radeon 9000 pci mother board intel dp43tf bug: The mouse icon is a white rectangle 1 inch long .5 inch tall. There are small speckles above below and in the rectangle. I have attempted to change the mouse pointer icon using the gnome tool in appearances to no effect. The mouse works but it is difficult to use as the pointer does not make it clear where the activation spot is. I just installed this mother board to replace an abit intel ip35v. the old board did not have this problem. I have debian 5 on this hard drive and it has the same problem ...the kernel is older. From david.planella at ubuntu.com Mon Dec 7 10:21:37 2009 From: david.planella at ubuntu.com (David Planella) Date: Mon, 07 Dec 2009 11:21:37 +0100 Subject: Ubuntu Translation bug handling process In-Reply-To: References: Message-ID: <1260181297.3621.103.camel@lenovo> Hi Sense, First of all, thanks a lot for the feedback. We really appreciate this, since bug handling is a new process for the translations team and any comments, especially from experienced bug squad members, are really useful to us. Let me give some background on the purpose of the ubuntu-translations project for translations bug reporting. As you probably know, unlike other teams (e.g. kernel), translations cannot be reported against a single package (not even language packs (*)). This, and the facts that a) knowledge on how to handle or fix translations is currently scarce and b) translations has been an aspect traditionally not too well looked after, lead to the situation that many translations bugs were simply forgotten in the past, although many members of the translations community would have been willing to actively triage them and in some cases also fix them. In the past, the i18n or l10n tags had been used on an occasional basis, but as in Launchpad you cannot subscribe to a tag, it was not possible for those interested in monitoring and acting upon translations bugs to have an overview of the whole picture. With the ubuntu-translations project we've now got a hub for translations bugs: this allows those interested in them to get an overview of currently open bugs, having a team (the Ubuntu Translations Coordinators) behind it -both actively triaging and fixing them and acting as a point of contact- and permitting further community participation subscribing to bug mail. Another compelling reason for using it was to decouple bugs related to Ubuntu translations from bugs in the Launchpad Translations component. Very often bugs in the distro were reported against Rosetta, and there was not a clear path for the Rosetta developers to bring them back to the distro. Now they only have to move them to ubuntu-translations, and if necessary we open tasks for the appropriate packages. We are still learning about the bug triaging process for translations, and in that respect we've been documenting it and asking for feedback from the bugs team: https://help.ubuntu.com/community/ReportingBugs#Filing%20translation% 20bugs https://wiki.ubuntu.com/Translations/KnowledgeBase/ReportingBugs https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs Note that this is still work in progress, e.g. the last two documents should probably be merged into HandlingBugs, which is currently a brainstorm page for defining the process. That's one of the reasons (not having a defined process) we hadn't widely announced the project yet, but after the experience from the last cycle and your original suggestion on a Hug Day on language packs, I thought it might be time to move this forward, give it a road test during the Hug Day and get some more feedback. Needless to say, we are open to suggestions and willing to follow the standard practices of the bug squad. I feel that this has worked extremely well for the Karmic cycle. I do not have statistics at hand other than [1], but judging by the number of bugs we've processed and the status of the release (also comparing it to previous ones), I think this has been one of the main achievements of last cycle in terms of better translations QA. El dj 03 de 12 de 2009 a les 20:27 +0100, en/na Sense Hofstede va escriure: > Hello, > > Browsing the BugDay of this day[1] I can't help but feel that a lot of > these bugs have appeared on the list because the ubuntu-translators > project doesn't want to use or cannot set importance and the Triaged > status. I suspect the latest. Neither of those, it's because we (well, at least me) didn't quite know the difference between Confirmed and Triaged. I'd be more than happy to use the same convention from https://wiki.ubuntu.com/Bugs/Status for the ubuntu-translations project, and start marking the current Confirmed bugs to Triaged as appropriate. > This means that the status of the bug reports that are mainly handled > by Ubuntu Translators will continue to pop up on search results like > the one used for the lists of this BugDay. > Another thing I noticed in the Hug Day is that only members of the ubuntu-translations-coordinators team can change the status to triaged - is there a way we could give this ability to the bugsquad team as well? Would that be desirable? > The triaging process for translation bugs is further complicated by > the requirement to report it both against the source package of the > affected application and the ubuntu-translations project. This forces > us to maintain two sets of statuses, each subject to the rule of a > different team. This causes confusion. > Although we do not make it a requirement, it is true that in most of the cases there is a separate task for the package. While I see some of the disadvantages in that, I cannot think of any other way of keeping track of translation bugs as a whole and at the same time have the bugs reported or fixed in the package. > Then there is the problem of the difference between translations made > at Launchpad and translations made upstream. Some bugs have to be > fixed here, some have to be forwarded upstream. > If there is a fix in a particular translation to be forwarded upstream, it should be the responsibility of the local Ubuntu translation team subscribed to the bug to do that. While the ubuntu-translations-coordinators team encourages that, we do not have the resources for forwarding these particular fixes ourselves. > I suggest to make the process of reporting more clear by implementing > the following changes: > > 1. The starting point of all translation bugs -- unless you know > better already -- can still be the source package of the affected > application. Ideally, it should work like this, but experience has shown that such bugs never make it to the translations team or those interested/knowledgeable in translations, so they tend to remain open. > 2. No extra tasks for bugs in upstream translations, this only adds > extra clutter to the overview, generates extra mail noise and > generates more work and confusion. I'm still in favour of using the ubuntu-translations project for the reasons stated above, but I (and I believe I can speak for the rest of team members) am open to any suggestions or improvements. > 3. Bugs in translations done at Launchpad should be reported against > ubuntu-translations and keep the source package task, because: > 4. The source package task is for maintaining the status of the bug > concerning the system -- i.e. if the bug has been Triaged(=reported > properly upstream or at ubuntu-translations) or if the Fix is Released > -- the ubuntu-translations task should be for the status of the fix in > Rosetta or the team only > 4b. This means that translation bugs always need to be 'forwarded > upstream', be it to real upstreams or to ubuntu-translations. This is > what the triagers should focus on when triaging these bugs. While I basically agree on this, I think you are talking of the process of forwarding translations upstream in general, and not translation bug fixes, which is a task that has never been done through bug reports. I think > 5. Responsible for setting the status in ubuntu-translations are their > (appointed?) members, responsible for the source package task is Bug > Control (and the Bugsquad). Some members of ubuntu-translations that > are very active on Launchpad/Malone could be granted membership of > Ubuntu Bugcontrol -- if they don't already are a member -- to make it > easier for them to manage the source package tasks. That's a very good point, and might address the question I was asking above about bugsquad members not being able to change the ubuntu-translations statuses to Triaged. > 6. Use the Triaged status for the source package when the Bugsquad > doesn't need to do any work on it anymore! > We'll do it for ubuntu-translations from now on! :) > These points don't add a lot of new stuff, but things would be a bit > clearer if both teams would agree on them and integrate them into the > documentation. Again, thanks a lot for the feedback, which is really appreciated. I hope this generates further discussion and helps us improving the quality in native language support in Ubuntu. Regards, David. (*) Language pack packages are usually not a good target for bug reports. Unless the bug is localized to a particular language pack, in which case it is valid to report it there and then assign it to the local translation team if necessary, there are lots of translation issues which have nothing to do with language packs (e.g. untranslated strings in an application, translations not loaded, etc.). Furthermore, the Ubuntu Translations Coordinators team is not the bug contact for language packs, so unless actively searching for reports against language packs, these usually fall out of the translations team radar. [1] https://bugs.launchpad.net/ubuntu-translations/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&search=Search -- David Planella Ubuntu Translations Coordinator david(dot)planella(at)ubuntu(dot)com www.ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 489 bytes Desc: Això és una part d'un missatge signada digitalment URL: From sense at qense.nl Mon Dec 7 16:17:06 2009 From: sense at qense.nl (Sense Hofstede) Date: Mon, 7 Dec 2009 17:17:06 +0100 Subject: Ubuntu Translation bug handling process In-Reply-To: <1260181297.3621.103.camel@lenovo> References: <1260181297.3621.103.camel@lenovo> Message-ID: 2009/12/7 David Planella : > Hi Sense, > > First of all, thanks a lot for the feedback. We really appreciate this, > since bug handling is a new process for the translations team and any > comments, especially from experienced bug squad members, are really > useful to us. > > Let me give some background on the purpose of the ubuntu-translations > project for translations bug reporting. As you probably know, unlike > other teams (e.g. kernel), translations cannot be reported against a > single package (not even language packs (*)). This, and the facts that > a) knowledge on how to handle or fix translations is currently scarce > and b) translations has been an aspect traditionally not too well looked > after, lead to the situation that many translations bugs were simply > forgotten in the past, although many members of the translations > community would have been willing to actively triage them and in some > cases also fix them. > > In the past, the i18n or l10n tags had been used on an occasional basis, > but as in Launchpad you cannot subscribe to a tag, it was not possible > for those interested in monitoring and acting upon translations bugs to > have an overview of the whole picture. > > With the ubuntu-translations project we've now got a hub for > translations bugs: this allows those interested in them to get an > overview of currently open bugs, having a team (the Ubuntu Translations > Coordinators) behind it -both actively triaging and fixing them and > acting as a point of contact- and permitting further community > participation subscribing to bug mail. Another compelling reason for > using it was to decouple bugs related to Ubuntu translations from bugs > in the Launchpad Translations component. Very often bugs in the distro > were reported against Rosetta, and there was not a clear path for the > Rosetta developers to bring them back to the distro. Now they only have > to move them to ubuntu-translations, and if necessary we open tasks for > the appropriate packages. > > We are still learning about the bug triaging process for translations, > and in that respect we've been documenting it and asking for feedback > from the bugs team: > > https://help.ubuntu.com/community/ReportingBugs#Filing%20translation% > 20bugs > https://wiki.ubuntu.com/Translations/KnowledgeBase/ReportingBugs > https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs > > Note that this is still work in progress, e.g. the last two documents > should probably be merged into HandlingBugs, which is currently a > brainstorm page for defining the process. > > That's one of the reasons (not having a defined process) we hadn't > widely announced the project yet, but after the experience from the last > cycle and your original suggestion on a Hug Day on language packs, I > thought it might be time to move this forward, give it a road test > during the Hug Day and get some more feedback. > > Needless to say, we are open to suggestions and willing to follow the > standard practices of the bug squad. > > I feel that this has worked extremely well for the Karmic cycle. I do > not have statistics at hand other than [1], but judging by the number of > bugs we've processed and the status of the release (also comparing it to > previous ones), I think this has been one of the main achievements of > last cycle in terms of better translations QA. > > El dj 03 de 12 de 2009 a les 20:27 +0100, en/na Sense Hofstede va > escriure: >> Hello, >> >> Browsing the BugDay of this day[1] I can't help but feel that a lot of >> these bugs have appeared on the list because the ubuntu-translators >> project doesn't want to use or cannot set importance and the Triaged >> status. I suspect the latest. > > Neither of those, it's because we (well, at least me) didn't quite know > the difference between Confirmed and Triaged. I'd be more than happy to > use the same convention from > > https://wiki.ubuntu.com/Bugs/Status > > for the ubuntu-translations project, and start marking the current > Confirmed bugs to Triaged as appropriate. > >> This means that the status of the bug reports that are mainly handled >> by Ubuntu Translators will continue to pop up on search results like >> the one used for the lists of this BugDay. >> > > Another thing I noticed in the Hug Day is that only members of the > ubuntu-translations-coordinators team can change the status to triaged - > is there a way we could give this ability to the bugsquad team as well? > Would that be desirable? > >> The triaging process for translation bugs is further complicated by >> the requirement to report it both against the source package of the >> affected application and the ubuntu-translations project. This forces >> us to maintain two sets of statuses, each subject to the rule of a >> different team. This causes confusion. >> > > Although we do not make it a requirement, it is true that in most of the > cases there is a separate task for the package. While I see some of the > disadvantages in that, I cannot think of any other way of keeping track > of translation bugs as a whole and at the same time have the bugs > reported or fixed in the package. > >> Then there is the problem of the difference between translations made >> at Launchpad and translations made upstream. Some bugs have to be >> fixed here, some have to be forwarded upstream. >> > > If there is a fix in a particular translation to be forwarded upstream, > it should be the responsibility of the local Ubuntu translation team > subscribed to the bug to do that. While the > ubuntu-translations-coordinators team encourages that, we do not have > the resources for forwarding these particular fixes ourselves. > >> I suggest to make the process of reporting more clear by implementing >> the following changes: >> >> 1. The starting point of all translation bugs -- unless you know >> better already -- can still be the source package of the affected >> application. > > Ideally, it should work like this, but experience has shown that such > bugs never make it to the translations team or those > interested/knowledgeable in translations, so they tend to remain open. > >> 2. No extra tasks for bugs in upstream translations, this only adds >> extra clutter to the overview, generates extra mail noise and >> generates more work and confusion. > > I'm still in favour of using the ubuntu-translations project for the > reasons stated above, but I (and I believe I can speak for the rest of > team members) am open to any suggestions or improvements. > >> 3. Bugs in translations done at Launchpad should be reported against >> ubuntu-translations and keep the source package task, because: >> 4. The source package task is for maintaining the status of the bug >> concerning the system -- i.e. if the bug has been Triaged(=reported >> properly upstream or at ubuntu-translations) or if the Fix is Released >> -- the ubuntu-translations task should be for the status of the fix in >> Rosetta or the team only >> 4b. This means that translation bugs always need to be 'forwarded >> upstream', be it to real upstreams or to ubuntu-translations. This is >> what the triagers should focus on when triaging these bugs. > > While I basically agree on this, I think you are talking of the process > of forwarding translations upstream in general, and not translation bug > fixes, which is a task that has never been done through bug reports. I > think > >> 5. Responsible for setting the status in ubuntu-translations are their >> (appointed?) members, responsible for the source package task is Bug >> Control (and the Bugsquad). Some members of ubuntu-translations that >> are very active on Launchpad/Malone could be granted membership of >> Ubuntu Bugcontrol -- if they don't already are a member -- to make it >> easier for them to manage the source package tasks. > > That's a very good point, and might address the question I was asking > above about bugsquad members not being able to change the > ubuntu-translations statuses to Triaged. > >> 6. Use the Triaged status for the source package when the Bugsquad >> doesn't need to do any work on it anymore! >> > > We'll do it for ubuntu-translations from now on! :) > >> These points don't add a lot of new stuff, but things would be a bit >> clearer if both teams would agree on them and integrate them into the >> documentation. > > Again, thanks a lot for the feedback, which is really appreciated. I > hope this generates further discussion and helps us improving the > quality in native language support in Ubuntu. > > Regards, > David. > > (*) Language pack packages are usually not a good target for bug > reports. Unless the bug is localized to a particular language pack, in > which case it is valid to report it there and then assign it to the > local translation team if necessary, there are lots of translation > issues which have nothing to do with language packs (e.g. untranslated > strings in an application, translations not loaded, etc.). Furthermore, > the Ubuntu Translations Coordinators team is not the bug contact for > language packs, so unless actively searching for reports against > language packs, these usually fall out of the translations team radar. > > [1] > https://bugs.launchpad.net/ubuntu-translations/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&search=Search > > -- > David Planella > Ubuntu Translations Coordinator > david(dot)planella(at)ubuntu(dot)com > www.ubuntu.com > > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Thank you for your lengthy reply. You explained the way the team works really well. Merging the last of the two wiki pages you named is probably indeed the best thing to do. I reckon it would be good to also link to them in the Bugsquad documentation so the triagers also learn how to handle these kind of bugs. I'm not so sure if the approach recommended by the community documentation is the best way. If an application doesn't call gettext on a string, is that something you want an 'ubuntu-translations' task for as well? A supportive argument would be that in order to solve all symptoms of the bug completely the string needs to be translated as well, but that would also mean a task for the language-packs would be justified since they have to be updated as well; and that would cause a lot of clutter. The most important thing of the points 3,4 and 4b was that I wanted to suggest to look at 'ubuntu-translations' as an upstream as well and handle it like that. Which means that all incoming bugs are channelled through the 'ubuntu' project, handled by the Bugsquad _there_, and, if necessary, forwared 'upstream' to the project that's responsible for translating Ubuntu. This does makes the different roles more clear -- Bugsquad categorises the bugs and determines the cause, Translations does translations -- but of course would mean a small decrease in the usefulness of 'ubuntu-translations' as pool of all translation bugs. I think it would be of a great benefit to Translations and Bugsquad if we'd sit down with each other and clearly define the roles and divide the tasks, to get rid of the last few bumps on the road. Do you feel the same? Regards, -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ From brian at ubuntu.com Mon Dec 7 18:03:22 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 7 Dec 2009 10:03:22 -0800 Subject: right package for what might be a mother board problem In-Reply-To: <1260035076.4855.16.camel@eric-desktop> References: <1260035076.4855.16.camel@eric-desktop> Message-ID: <20091207180322.GF5381@murraytwins.com> On Sat, Dec 05, 2009 at 11:44:36AM -0600, eric wrote: > operating system ubuntu 9.04 amd64 > video card radeon 9000 pci > mother board intel dp43tf > > bug: > The mouse icon is a white rectangle 1 inch long .5 inch tall. > There are small speckles above below and in the rectangle. > I have attempted to change the mouse pointer icon using the gnome tool > in appearances to no effect. > The mouse works but it is difficult to use as the pointer does not make > it clear where the activation spot is. > > > I just installed this mother board to replace an abit intel ip35v. > the old board did not have this problem. > I have debian 5 on this hard drive and it has the same problem ...the > kernel is older. Were you using the same video card with both motherboards? -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From kamusin at gmail.com Wed Dec 9 13:33:19 2009 From: kamusin at gmail.com (Kamus) Date: Wed, 9 Dec 2009 10:33:19 -0300 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 10 December 2009 Message-ID: Announcing the Next Ubuntu Bug Day! - Thursday 10 December 2009 Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Compiz! * 120 New bugs need a hug * 112 Incomplete bugs need a status check * 61 Confirmed bugs need a review * 2 bugs that need forward to upstream Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 10 December 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20091210 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 (like me!) and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud: -33.439177,-70.625267 Santiago, Chile. From hggdh2 at ubuntu.com Wed Dec 9 19:16:53 2009 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 09 Dec 2009 13:16:53 -0600 Subject: [Ubuntu-bugcontrol] Bugs Wiki changes and the bugControl team In-Reply-To: <20091209190425.GO5381@murraytwins.com> References: <4B1EF461.3040604@ubuntu.com> <20091209190425.GO5381@murraytwins.com> Message-ID: <4B1FF7A5.4030700@ubuntu.com> Brian Murray wrote: > On Tue, Dec 08, 2009 at 06:50:41PM -0600, C de-Avillez wrote: >> All >> >> We are considering making the BugControl LP team subscribed to Wiki changes >> for our pages. We understand this will create more email traffic but: >> >> * you can easily set up a filter for these emails; >> >> * you *will* receive a warning that something has changed, and will be able >> to take action if you think it is needed; >> * you will be aware of changes in procedures >> >> I have been subscribed to some of these pages for a while, and the amount >> or email I receive re. changes is quite small. >> >> So. We intend to set it up for a *test*. Feedback is appreciated. > > I'd thought it would be the Bug Squad mailing list that would be > subscribed to wiki pages, not Ubuntu Bug Control. > Well, well. Indeed. I stand corrected. Sorry. Forwarding to Ubuntu-bugsquad. Thank you for spotting this. ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From brian at ubuntu.com Thu Dec 10 22:10:06 2009 From: brian at ubuntu.com (Brian Murray) Date: Thu, 10 Dec 2009 14:10:06 -0800 Subject: Finding bug duplicates Message-ID: <20091210221006.GH8450@murraytwins.com> During the UDS Lucid meeting regarding "Making duplicate bug detection and consolidation easier" it was mentioned that it would be helpful to have a script that uses the Launchpad's duplicate finder to search for duplicates of a bug report. I've written such a script, find-similar-bugs.py, which uses launchpadlib and put it in the ubuntu-qa-tools bzr branch[1]. I've used it with mixed success and hope that you might find it useful. One interesting thing to do would be going through the karmic-changes[2] mailing list and looking for fixed bugs (indicated by LP: #465619) and using the script to find potential duplicates. [1] https://code.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master [2] https://lists.ubuntu.com/archives/karmic-changes/ -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From brian at ubuntu.com Fri Dec 11 00:05:33 2009 From: brian at ubuntu.com (Brian Murray) Date: Thu, 10 Dec 2009 16:05:33 -0800 Subject: Translation help In-Reply-To: <1259915028.15968.56.camel@lenovo> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> <20091202185851.GY5381@murraytwins.com> <1259915028.15968.56.camel@lenovo> Message-ID: <20091211000533.GI8450@murraytwins.com> On Fri, Dec 04, 2009 at 09:23:48AM +0100, David Planella wrote: > Hi Brian, > > El dc 02 de 12 de 2009 a les 10:58 -0800, en/na Brian Murray va > escriure: > > On Wed, Dec 02, 2009 at 10:09:24AM +0100, David Planella wrote: > > > Hi all, > > > > > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > > > escriure: > > > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > > > language and while I don't want to encourage this widely I also feel > > > > like we should attempt to help the reporter. Additionally, there are > > > > frequently log files, like in apport-package bug reports, that are in a > > > > foreign language. > > > > > > > > > > Regarding the log files, if they come from apport, I agree with Arne in > > > the sense that ideally apport should generate them in the English (C) > > > locale. > > > > This does in fact happen. > > > > > But if I understand it correctly, that's also about logs generated by > > > the applications themselves prior to the bug report, so that might not > > > be that simple and they might need to be translated once they are > > > included in the bug report anyway. > > > > Yes, that is correct, for example consider > > http://launchpad.net/bugs/491387 where the DpkgTerminalLog.txt is not in > > English. > > > > > > While we could ask the reporter to translate both of these themselves I > > > > wonder if there is some way Ubuntu translators can help us out? If so > > > > how can we get assistance with these bug reports? > > > > > > > > Thanks, > > > > > > If there is not a massive amount of such bugs, you could also forward > > > them to the ubuntu-translators list, where you'd surely find someone > > > speaking the language and willing to help either translating the bug or > > > directly assisting the reporter. This has been done occasionally for > > > Answers request in the past and IIRC worked quite well. Alternatively, > > > you could even open a bug task against the ubuntu-translations project, > > > and those subscribed to bugmail would forward it to the list. That said > > > though, I think directly forwarding the bugs to the list might be a > > > better approach. > > > > Hmm, this seems a bit unwieldy to me - I was hoping for a solution with > > in Launchpad. Using my example from above presumably the translations > > for the messages in DpkgTerminaLog exist in Launchpad. Is there some > > way to search for them and find out the English equivalent? > > > > Thanks, > > If you know the source package, you can search for the string in the > package's translations. For the dpkg example above: > > https://translations.launchpad.net/ubuntu/karmic/+source/dpkg/+pots/dpkg/it/+translate?batch=10&show=all&search=Lettura+del+database This is really interesting but it is not clear to me how to perform a search that ends up with that result. What url did you start out with to get this? Is it dependant on the triager determining the language the messages are in? > If you don't know the actual package where translations come from (they > might come e.g. from a library the package in the bug report is using), > you can use the global search feature: > > https://launchpad.net/+search?field.text=Lettura+del+database > > In any case, both of these options might require some manual work (there > is no Launchpad Translations API yet), and I'm not sure that was what > you were looking for. > > If that'd be too time consuming to include in the bug workflow and these > reports are indeed occasional, I think pointing them out in the > ubuntu-translators list would still be valid (I can also ask translators > if they'd be ok with that). I think either searching Launchpad for the message or asking the reporter to translate it themselves should be the first approach. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From david.planella at ubuntu.com Fri Dec 11 11:27:48 2009 From: david.planella at ubuntu.com (David Planella) Date: Fri, 11 Dec 2009 12:27:48 +0100 Subject: Translation help In-Reply-To: <20091211000533.GI8450@murraytwins.com> References: <20091201202226.GO5381@murraytwins.com> <1259744965.30592.155.camel@lenovo> <20091202185851.GY5381@murraytwins.com> <1259915028.15968.56.camel@lenovo> <20091211000533.GI8450@murraytwins.com> Message-ID: <1260530868.8558.44.camel@lenovo> El dj 10 de 12 de 2009 a les 16:05 -0800, en/na Brian Murray va escriure: > On Fri, Dec 04, 2009 at 09:23:48AM +0100, David Planella wrote: > > Hi Brian, > > > > El dc 02 de 12 de 2009 a les 10:58 -0800, en/na Brian Murray va > > escriure: > > > On Wed, Dec 02, 2009 at 10:09:24AM +0100, David Planella wrote: > > > > Hi all, > > > > > > > > El dt 01 de 12 de 2009 a les 12:22 -0800, en/na Brian Murray va > > > > escriure: > > > > > Occasionally, we receive bugs reported about Ubuntu in a foreign > > > > > language and while I don't want to encourage this widely I also feel > > > > > like we should attempt to help the reporter. Additionally, there are > > > > > frequently log files, like in apport-package bug reports, that are in a > > > > > foreign language. > > > > > > > > > > > > > Regarding the log files, if they come from apport, I agree with Arne in > > > > the sense that ideally apport should generate them in the English (C) > > > > locale. > > > > > > This does in fact happen. > > > > > > > But if I understand it correctly, that's also about logs generated by > > > > the applications themselves prior to the bug report, so that might not > > > > be that simple and they might need to be translated once they are > > > > included in the bug report anyway. > > > > > > Yes, that is correct, for example consider > > > http://launchpad.net/bugs/491387 where the DpkgTerminalLog.txt is not in > > > English. > > > > > > > > While we could ask the reporter to translate both of these themselves I > > > > > wonder if there is some way Ubuntu translators can help us out? If so > > > > > how can we get assistance with these bug reports? > > > > > > > > > > Thanks, > > > > > > > > If there is not a massive amount of such bugs, you could also forward > > > > them to the ubuntu-translators list, where you'd surely find someone > > > > speaking the language and willing to help either translating the bug or > > > > directly assisting the reporter. This has been done occasionally for > > > > Answers request in the past and IIRC worked quite well. Alternatively, > > > > you could even open a bug task against the ubuntu-translations project, > > > > and those subscribed to bugmail would forward it to the list. That said > > > > though, I think directly forwarding the bugs to the list might be a > > > > better approach. > > > > > > Hmm, this seems a bit unwieldy to me - I was hoping for a solution with > > > in Launchpad. Using my example from above presumably the translations > > > for the messages in DpkgTerminaLog exist in Launchpad. Is there some > > > way to search for them and find out the English equivalent? > > > > > > Thanks, > > > > If you know the source package, you can search for the string in the > > package's translations. For the dpkg example above: > > > > https://translations.launchpad.net/ubuntu/karmic/+source/dpkg/+pots/dpkg/it/+translate?batch=10&show=all&search=Lettura+del+database > > This is really interesting but it is not clear to me how to perform a > search that ends up with that result. What url did you start out with > to get this? Is it dependant on the triager determining the language > the messages are in? > If you are using the web UI, the first place you'd go to would be https://translations.launchpad.net/ubuntu/karmic/+source/, in this case https://translations.launchpad.net/ubuntu/karmic/+source/dpkg/, then you'd click on the appropriate translation template and would be taken to the list of languages, where you'd finally click on the language you are interested in and it would take you to the translation page (where the searchbox also is) at https://translations.launchpad.net/ubuntu/karmic/+source/dpkg/+pots/dpkg/it/+translate in this particular case. So in terms of building the URL (I assume you were thinking of automating this with e.g. an script), the triager should know: 1. Source package and distro 2. Translation template 3. Language (ISO 639-1 two letter code or ISO 639-2 three letter code in most cases) 4. String to look for (searches are case-insensitive and work for both English and the given language) https://translations.launchpad.net/ubuntu//+source//+pots///+translate?batch=10&show=all&search=String+to+search+for While 1. and 4. will be trivial to find out, the other variables in building the URL will be not. Especially the translation template, since although it can be guessed to be the same name as the source package, quite often it is not. Furthermore, a source package can have multiple templates and all should be searched for, and finally, it can be that the translation actually comes from a different source package (e.g. most GNOME applications use "stock" translations from GTK). So this makes it a bit difficult to search for those strings in Launchpad in a script, although it can still be done (albeit less efficiently) by manually browsing through the Launchpad web UI. > > If you don't know the actual package where translations come from (they > > might come e.g. from a library the package in the bug report is using), > > you can use the global search feature: > > > > https://launchpad.net/+search?field.text=Lettura+del+database > > > > In any case, both of these options might require some manual work (there > > is no Launchpad Translations API yet), and I'm not sure that was what > > you were looking for. > > > > If that'd be too time consuming to include in the bug workflow and these > > reports are indeed occasional, I think pointing them out in the > > ubuntu-translators list would still be valid (I can also ask translators > > if they'd be ok with that). > > I think either searching Launchpad for the message or asking the > reporter to translate it themselves should be the first approach. > Sounds fine by me. If you need help from the translations team we'll always be willing to give a hand or two! Regards, David. -- David Planella Ubuntu Translations Coordinator david(dot)planella(at)ubuntu(dot)com www.ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 489 bytes Desc: Això és una part d'un missatge signada digitalment URL: From adi at roiban.ro Sat Dec 12 10:16:17 2009 From: adi at roiban.ro (Adi Roiban) Date: Sat, 12 Dec 2009 12:16:17 +0200 Subject: Ubuntu Translation bug handling process In-Reply-To: References: <1260181297.3621.103.camel@lenovo> Message-ID: <1260612977.7276.54.camel@adi-laptop> Just my 2 cents and I try to be brief and concise.... but I failed I think that all Ubuntu Translators will be happy to make ubuntu-translators less useful by not having to do bug triaging. The bughandling wikipage was just a brainstorming page. I would be happy to delete it and have all info on bugsquad wiki. Ubuntu Translations bugs are something special from the following points of view: * They can be fixed without having someone patching and uploading a new package * Most of them can be fixed in less than 2 minutes, just from the web UI. You only need to read the bug, to to Launchpad translation, fix the translation and then come back and mark that bug as fixed. * Many translators are not technical persons. We can channel all bug to Ubuntu and make them use apport, but I think that this will stop them from reporting bugs. ------------- I like to keep things simple and this is why I went for a divide and conquer approach for handling Ubuntu translations bugs. I think that reporting a bug in Ubuntu is ok when you don't know exactly what component is affected and who can fix it. For translations bug we know they affect ubuntu-translation and they can be fixed by the ubuntu-l10n-CC (replace CC with your language) team. The triaging process can be done by the bug reporter at the time they report the bug. No need to add extra work to other persons. ------------ My goal is to have ubuntu-translation bugs fixed. Fast. Without stepping on others feet. What are the drawbacks of the current process? Right now, in Ubuntu we have 39668 new bugs. What do we gain if we put Ubuntu Translation bugs together? --------- I think we should add this topic on the next team meeting agenda. Next for translations is 7 Jan, bugsquad 12. I am available for both. Kindest regards, -- Adi Roiban From kamusin at gmail.com Tue Dec 15 20:07:43 2009 From: kamusin at gmail.com (Kamus) Date: Tue, 15 Dec 2009 17:07:43 -0300 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 17 December 2009 Message-ID: Announcing the Next Ubuntu Bug Day! - Thursday 17 December 2009 Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Bugs without a package!  * 100 New bugs need a hug  * 100 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers!  * Thursday 17 December 2009  * https://wiki.ubuntu.com/UbuntuBugDay/20091217 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 (like me!), you want receive a nice present from santa and you want to know more about ubuntu?, head to  http://wiki.ubuntu.com/Bugs Have a nice day,   Kamus [From the BugSquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From leann.ogasawara at canonical.com Thu Dec 17 17:48:06 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Thu, 17 Dec 2009 09:48:06 -0800 Subject: Kernel Bug Day - Tues 22 Dec, 2009 Message-ID: <1261072086.2880.1440.camel@emiko> Hi All, This is just a friendly reminder that the next Kernel Bug Day will be held Tues. 22 Dec, 2009 [1]. We'll again be focusing on bugs with patches attached. Don't know what a Kernel Bug Day is [2]? This is the perfect opportunity to find out what it's all about! You'll notice this particular bug day lands in close proximity to the Christmas holiday. We anticipate many might be away on holiday and unable to participate which is why we again chose to target bugs with patches attached. Please join us Tuesday in the #ubuntu-kernel IRC channel on FreeNode as we tackle this list of bugs together. Thanks in advance, Leann [1] https://wiki.ubuntu.com/KernelTeam/BugDay/20091222 [2] https://wiki.ubuntu.com/KernelTeam/BugDay From sense at qense.nl Tue Dec 22 12:07:31 2009 From: sense at qense.nl (Sense Hofstede) Date: Tue, 22 Dec 2009 13:07:31 +0100 Subject: Adopting Nautilus Message-ID: Hello, Last UDS we discussed the idea of adopting a package. Some people already were watching specific packages, but unfortunately the Adopt-a-Package project seems a bit silent until now. I had already adopted a few tiny packages, but I wanted to contribute to the shape of a more important package. Therefore I added myself as 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy to tell you that currently all bugs reported against Nautilus that were marked as 'Confirmed' have now been processed, leaving no bugs in that state. Now I can start on the bugs still marked as New. However, this it is a lot of work, not only to get in shape, but also to keep in shape. I would like to ask this maillist if there are any people interested in becoming a godfather or godmother of Nautilus as well. Because we would be the first group adopting a package it will probably be a valuable learning exercise. Our group could be the pioneer, uncovering difficulties and showing the benefits of adopting a package. What would you need to do? Well, that would be something we could discuss. Not everyone can or wants to spend the same amount of time on bug triaging, so we would have to take that into account. We could assign one or more people to just forwarding bugs upstream -- others would just have to open upstream tasks when they encounter bugs that need forwarding upstream. A different group could focus on incoming New bug reports, and so on. Of course you don't have to limit yourself strictly to one task, or join the forwarders group if you forward a bug upstream once. If you're interested, please reply. Regards, -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ PS: I realise I'm not the only one working on Nautilus bug reports here. If you are doing that already as well, please consider formally adopting the package as well and joining this coordination effort. In a group we can work much more efficiently. From cyprian at ymail.com Thu Dec 17 21:54:41 2009 From: cyprian at ymail.com (David Crook) Date: Thu, 17 Dec 2009 13:54:41 -0800 (PST) Subject: New to Bugsquad Message-ID: <412546.65818.qm@web65302.mail.ac2.yahoo.com> Hello: My name is Dave Crook and I am requesting a mentor as I just joined the bugsquad. I am new user I have had  Ubuntu on my laptop for about 60 days. I would very much like to contribute to this wonderful project. I live in the USA new York State which is  Eastern time zone -5 GMT. I am normally available and on line  in the evenings after 18:00 hours. I have no area of specialization, but I am a quick study and eager to learn. Thank you Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From sense at qense.nl Tue Dec 22 18:27:50 2009 From: sense at qense.nl (Sense Hofstede) Date: Tue, 22 Dec 2009 19:27:50 +0100 Subject: Adopting Nautilus In-Reply-To: <4cfc0be70912221009l79b0a0d5s6b70453de7b971d@mail.gmail.com> References: <4cfc0be70912221009l79b0a0d5s6b70453de7b971d@mail.gmail.com> Message-ID: 2009/12/22 Marcos Vanetta : > Hi Qense, > I'm going in! But I warn you, I'm really new in the world of bugs, I've been > here for two weeks only! But I think this is gonna be huge! > Also, my english is not perfect :D > Where can I submit my name to the list? > Regards > malev > > 2009/12/22 Sense Hofstede >> >> Hello, >> >> Last UDS we discussed the idea of adopting a package. Some people >> already were watching specific packages, but unfortunately the >> Adopt-a-Package project seems a bit silent until now. >> I had already adopted a few tiny packages, but I wanted to contribute >> to the shape of a more important package. Therefore I added myself as >> 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy >> to tell you that currently all bugs reported against Nautilus that >> were marked as 'Confirmed' have now been processed, leaving no bugs in >> that state. Now I can start on the bugs still marked as New. >> >> However, this it is a lot of work, not only to get in shape, but also >> to keep in shape. I would like to ask this maillist if there are any >> people interested in becoming a godfather or godmother of Nautilus as >> well. Because we would be the first group adopting a package it will >> probably be a valuable learning exercise. Our group could be the >> pioneer, uncovering difficulties and showing the benefits of adopting >> a package. >> >> What would you need to do? Well, that would be something we could >> discuss. Not everyone can or wants to spend the same amount of time on >> bug triaging, so we would have to take that into account. We could >> assign one or more people to just forwarding bugs upstream -- others >> would just have to open upstream tasks when they encounter bugs that >> need forwarding upstream. A different group could focus on incoming >> New bug reports, and so on. Of course you don't have to limit yourself >> strictly to one task, or join the forwarders group if you forward a >> bug upstream once. >> >> If you're interested, please reply. >> >> Regards, >> -- >> Sense Hofstede >> /ˈsen.sɜː ˈhɒf.steɪdɜː/ >> >> PS: I realise I'm not the only one working on Nautilus bug reports >> here. If you are doing that already as well, please consider formally >> adopting the package as well and joining this coordination effort. In >> a group we can work much more efficiently. >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > -- > Ing. Marcos Vanetta > http://blog.malev.com.ar > twitter: @malev > Hello, To both you and Yazen: Thank you for your reply! I'm happy you are interested in helping with Nautilus. However, there is not really a list, unless you mean the one at . Actually that really is a list, but so far the Adopt-a-Package project is not launched, so it is more for letting others know who is working on what package. (Am I correct?) Since you both said that you were not very experienced in bug triaging I think it would be best if you would particularly focus on New bug reports. [1] You don't have to wait until some official start since there won't really be an official start and nothing should stop someone from triaging a bug. ;) [1] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bugs?search=Search&field.status=New Regards, -- Sense Hofstede /ˈsen.sɜː ˈhɒf.steɪdɜː/ From brunogirin at gmail.com Tue Dec 22 18:43:10 2009 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 22 Dec 2009 18:43:10 +0000 Subject: Adopting Nautilus In-Reply-To: References: Message-ID: <1261507390.2382.107.camel@nuuk> On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: > What would you need to do? Well, that would be something we could > discuss. Not everyone can or wants to spend the same amount of time on > bug triaging, so we would have to take that into account. We could > assign one or more people to just forwarding bugs upstream -- others > would just have to open upstream tasks when they encounter bugs that > need forwarding upstream. A different group could focus on incoming > New bug reports, and so on. Of course you don't have to limit yourself > strictly to one task, or join the forwarders group if you forward a > bug upstream once. > > If you're interested, please reply. Hi Sense, Count me in. I have some experience of triaging bugs (at least up to getting them to the "Confirmed" state) and I would like to gain experience in other areas of the bug process so hopefully I can take on other tasks in the long run. My available time varies a lot but I'll try to do a minimum to help. Cheers, Bruno From yghannam7388 at gmail.com Tue Dec 22 19:00:26 2009 From: yghannam7388 at gmail.com (Yazen Ghannam) Date: Tue, 22 Dec 2009 14:00:26 -0500 Subject: Adopting Nautilus In-Reply-To: <1261507390.2382.107.camel@nuuk> References: <1261507390.2382.107.camel@nuuk> Message-ID: <4B31174A.6000900@gmail.com> Hello Everyone, I was just wondering, is it appropriate to mark a Wishlist action as Confirmed if you can confirm the action yourself? Or is Confirmed only used for Bugs? Thank you. Yazen Ghannam Bruno Girin wrote: > On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: > >> What would you need to do? Well, that would be something we could >> discuss. Not everyone can or wants to spend the same amount of time on >> bug triaging, so we would have to take that into account. We could >> assign one or more people to just forwarding bugs upstream -- others >> would just have to open upstream tasks when they encounter bugs that >> need forwarding upstream. A different group could focus on incoming >> New bug reports, and so on. Of course you don't have to limit yourself >> strictly to one task, or join the forwarders group if you forward a >> bug upstream once. >> >> If you're interested, please reply. >> > > Hi Sense, > > Count me in. I have some experience of triaging bugs (at least up to > getting them to the "Confirmed" state) and I would like to gain > experience in other areas of the bug process so hopefully I can take on > other tasks in the long run. My available time varies a lot but I'll try > to do a minimum to help. > > Cheers, > > Bruno > > > > From brian at ubuntu.com Tue Dec 22 21:36:38 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 22 Dec 2009 13:36:38 -0800 Subject: Invalid Apport Crashes Message-ID: <20091222213638.GD25065@murraytwins.com> Apport until very recently[1] was reporting crashes that ended with a signal of 24. However, a crash of this type is a normal behavior as such apport is now ignoring them. What this means is that existing bugs reported in Launchpad with a "Signal: 24" in the description can be closed as Invalid. I've compiled a list of these bug reports, which includes duplicates, and it is attached. These should all be double checked to ensure they aren't being worked on or something else is going on but if not they can be closed with a comment like the following: "Thank you for taking the time to report this crash and helping to make Ubuntu better. We've discovered that apport was inappropriately reporting signal 24 crashes. These reports are a result of an application exceeding limits set on CPU time which is normal behavior. Subsequently, we are closing this bug report as Invalid. We apologize for any inconvenience this has caused. Please report any future bugs or crashes that you may have." Please also tag them as 'signal-24' so we can find them again more easily - without a database query! [1] http://launchpad.net/bugs/498074 Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- LP: #475512 LP: #475491 LP: #475298 LP: #474521 LP: #474266 LP: #473499 LP: #473491 LP: #473104 LP: #472876 LP: #472438 LP: #472423 LP: #472277 LP: #471701 LP: #471693 LP: #470088 LP: #469621 LP: #469337 LP: #469291 LP: #469274 LP: #469219 LP: #469095 LP: #469086 LP: #469073 LP: #468522 LP: #468471 LP: #468311 LP: #468085 LP: #467828 LP: #467699 LP: #467088 LP: #467081 LP: #466586 LP: #466549 LP: #466455 LP: #466122 LP: #466081 LP: #466038 LP: #465984 LP: #465972 LP: #465953 LP: #465875 LP: #465683 LP: #465566 LP: #465024 LP: #464937 LP: #464325 LP: #463745 LP: #463446 LP: #463442 LP: #462053 LP: #461597 LP: #460963 LP: #460324 LP: #459791 LP: #458813 LP: #458296 LP: #458294 LP: #456928 LP: #455851 LP: #455473 LP: #454561 LP: #454555 LP: #453299 LP: #453184 LP: #453183 LP: #452071 LP: #451455 LP: #451255 LP: #451112 LP: #450829 LP: #450790 LP: #450399 LP: #450362 LP: #449197 LP: #447352 LP: #447331 LP: #447164 LP: #445834 LP: #445833 LP: #445671 LP: #445465 LP: #445393 LP: #445383 LP: #444809 LP: #444805 LP: #444410 LP: #443103 LP: #442946 LP: #442817 LP: #442816 LP: #441532 LP: #438587 LP: #438582 LP: #437133 LP: #436380 LP: #432496 LP: #430446 LP: #429646 LP: #424954 LP: #424418 LP: #419653 LP: #418297 LP: #417963 LP: #417962 LP: #414554 LP: #413897 LP: #411623 LP: #403368 LP: #403239 LP: #396065 LP: #395982 LP: #395586 LP: #395585 LP: #395584 LP: #395569 LP: #393497 LP: #393466 LP: #392594 LP: #380180 LP: #380179 LP: #377431 LP: #376799 LP: #356550 LP: #355773 LP: #349876 LP: #312963 LP: #311950 LP: #311795 LP: #306479 LP: #301348 LP: #292709 LP: #286657 LP: #286104 LP: #285139 LP: #283913 LP: #282608 LP: #282125 LP: #282012 LP: #281942 LP: #281331 LP: #279771 LP: #277983 LP: #274703 LP: #272327 LP: #271402 LP: #269371 LP: #266998 LP: #264702 LP: #223165 LP: #221753 LP: #218802 LP: #217190 LP: #216363 LP: #214963 LP: #214600 LP: #213198 LP: #212998 LP: #210730 LP: #210329 LP: #209877 LP: #207574 LP: #207469 LP: #203076 LP: #195910 LP: #194197 LP: #192903 LP: #192696 LP: #190569 LP: #189857 LP: #189588 LP: #187487 LP: #185073 LP: #184896 LP: #183676 LP: #182029 LP: #176118 LP: #155345 LP: #155344 LP: #151958 LP: #150789 LP: #148883 LP: #148359 LP: #148250 LP: #148245 LP: #148186 LP: #147877 LP: #147650 LP: #147558 LP: #147212 LP: #147044 LP: #145802 LP: #145797 LP: #144960 LP: #134388 LP: #132586 LP: #130775 LP: #130760 LP: #102339 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From komputes at gmail.com Tue Dec 22 22:06:29 2009 From: komputes at gmail.com (komputes) Date: Tue, 22 Dec 2009 17:06:29 -0500 Subject: New to Bugsquad In-Reply-To: <412546.65818.qm@web65302.mail.ac2.yahoo.com> References: <412546.65818.qm@web65302.mail.ac2.yahoo.com> Message-ID: <4B3142E5.6070009@gmail.com> David Crook wrote: > Hello: > > My name is Dave Crook and I am requesting a mentor as I just joined the bugsquad. I am new user I have had Ubuntu on my laptop for about 60 days. I would very much like to contribute to this wonderful project. > > I live in the USA new York State which is Eastern time zone -5 GMT. I am normally available and on line in the evenings after 18:00 hours. I have no area of specialization, but I am a quick study and eager to learn. > > Thank you > Dave > > > > > > > Hi Dave, I would suggest starting by registering a Launchpad account. After that, I would recommend going on IRC to go to the #ubuntu-bugs channel on the Freenode IRC server. Feel free to contact me once on IRC should you have any questions. -komputes (]( -. .- )[) From komputes at gmail.com Tue Dec 22 22:16:13 2009 From: komputes at gmail.com (komputes) Date: Tue, 22 Dec 2009 17:16:13 -0500 Subject: Adopting Nautilus In-Reply-To: <4B31174A.6000900@gmail.com> References: <1261507390.2382.107.camel@nuuk> <4B31174A.6000900@gmail.com> Message-ID: <4B31452D.4080700@gmail.com> Yazen Ghannam wrote: > Hello Everyone, > > I was just wondering, is it appropriate to mark a Wishlist action as > Confirmed if you can confirm the action yourself? Or is Confirmed only > used for Bugs? Thank you. > > Yazen Ghannam Using common sense and past experience, I would say that if you can confirm a bug or a feature request, mark the bug as confirmed and click on the "This affects me" link. If the status is not "New" and you want to mark it confirmed, please post the bug number so that it can be reviewed. -komputes (]( -. .- )[) From marcosvanetta at gmail.com Tue Dec 22 22:39:28 2009 From: marcosvanetta at gmail.com (Marcos Vanetta) Date: Tue, 22 Dec 2009 19:39:28 -0300 Subject: AdoptPackage Message-ID: <4cfc0be70912221439q3579340cx608a70e16950c6dd@mail.gmail.com> Hi! I've found about this [1] after an email from qense. Then I've found this [2] As you probably know, I'm new at the bugsquad, and I think this could be more educational in the road of learning triagging bugs. So I wonder? How can I do to singn me up in this? should I edit the wiki? or there is a list. I don't know. Nothing more for now. regards malev [1] https://wiki.ubuntu.com/BugSquad/AdoptPackage [2] https://wiki.ubuntu.com/QATeam/MainPackagesWithoutBugSubscribers -- Eng. Marcos Vanetta http://blog.malev.com.ar twitter: @malev -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Dec 22 23:35:06 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 22 Dec 2009 15:35:06 -0800 Subject: Adopting Nautilus In-Reply-To: <4B31452D.4080700@gmail.com> References: <1261507390.2382.107.camel@nuuk> <4B31174A.6000900@gmail.com> <4B31452D.4080700@gmail.com> Message-ID: <20091222233506.GE25065@murraytwins.com> On Tue, Dec 22, 2009 at 05:16:13PM -0500, komputes wrote: > Yazen Ghannam wrote: > > Hello Everyone, > > > > I was just wondering, is it appropriate to mark a Wishlist action as > > Confirmed if you can confirm the action yourself? Or is Confirmed only > > used for Bugs? Thank you. > > > > Yazen Ghannam > Using common sense and past experience, I would say that if you can > confirm a bug or a feature request, mark the bug as confirmed and click > on the "This affects me" link. Setting a bug to a status of Confirmed is correct. I'd only use "Does this bug affect you?" link if you really want to see the feature though. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From dave.crook68 at gmail.com Wed Dec 23 14:03:28 2009 From: dave.crook68 at gmail.com (David Crook) Date: Wed, 23 Dec 2009 09:03:28 -0500 Subject: Ubuntu-bugsquad Digest, Vol 42, Issue 15 In-Reply-To: References: Message-ID: Hello komputes: I have registered on launchpad, user name flash, I have been monitoring the IRC freenode chat room just out of curiosity. I am going to reread the ho to triage bugs and start with earnest after the first of the year. any direction would be appreciated. thanks To all: I would certainly would be interested in adopting the nautilus bug reports thanks Hope I am more of an asset than a liability but I am looking forward to the challenge Happy Holidays to all On Tue, Dec 22, 2009 at 5:39 PM, wrote: > Send Ubuntu-bugsquad mailing list submissions to >        ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit >        https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to >        ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at >        ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > > Today's Topics: > >   1. Adopting Nautilus (Sense Hofstede) >   2. New to Bugsquad (David Crook) >   3. Re: Adopting Nautilus (Sense Hofstede) >   4. Re: Adopting Nautilus (Bruno Girin) >   5. Re: Adopting Nautilus (Yazen Ghannam) >   6. Invalid Apport Crashes (Brian Murray) >   7. Re: New to Bugsquad (komputes) >   8. Re: Adopting Nautilus (komputes) >   9. AdoptPackage (Marcos Vanetta) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 Dec 2009 13:07:31 +0100 > From: Sense Hofstede > Subject: Adopting Nautilus > To: Ubuntu Bugsquad > Message-ID: >         > Content-Type: text/plain; charset=UTF-8 > > Hello, > > Last UDS we discussed the idea of adopting a package. Some people > already were watching specific packages, but unfortunately the > Adopt-a-Package project seems a bit silent until now. > I had already adopted a few tiny packages, but I wanted to contribute > to the shape of a more important package. Therefore I added myself as > 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy > to tell you that currently all bugs reported against Nautilus that > were marked as 'Confirmed' have now been processed, leaving no bugs in > that state. Now I can start on the bugs still marked as New. > > However, this it is a lot of work, not only to get in shape, but also > to keep in shape. I would like to ask this maillist if there are any > people interested in becoming a godfather or godmother of Nautilus as > well. Because we would be the first group adopting a package it will > probably be a valuable learning exercise. Our group could be the > pioneer, uncovering difficulties and showing the benefits of adopting > a package. > > What would you need to do? Well, that would be something we could > discuss. Not everyone can or wants to spend the same amount of time on > bug triaging, so we would have to take that into account. We could > assign one or more people to just forwarding bugs upstream -- others > would just have to open upstream tasks when they encounter bugs that > need forwarding upstream. A different group could focus on incoming > New bug reports, and so on. Of course you don't have to limit yourself > strictly to one task, or join the forwarders group if you forward a > bug upstream once. > > If you're interested, please reply. > > Regards, > -- > Sense Hofstede > /?sen.s?? ?h?f.ste?d??/ > > PS: I realise I'm not the only one working on Nautilus bug reports > here. If you are doing that already as well, please consider formally > adopting the package as well and joining this coordination effort. In > a group we can work much more efficiently. > > > > ------------------------------ > > Message: 2 > Date: Thu, 17 Dec 2009 13:54:41 -0800 (PST) > From: David Crook > Subject: New to Bugsquad > To: ubuntu-bugsquad at lists.ubuntu.com > Message-ID: <412546.65818.qm at web65302.mail.ac2.yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hello: > > My name is Dave Crook and I am requesting a mentor as I just joined the bugsquad. I am new user I have had? Ubuntu on my laptop for about 60 days. I would very much like to contribute to this wonderful project. > > I live in the USA new York State which is? Eastern time zone -5 GMT. I am normally available and on line? in the evenings after 18:00 hours. I have no area of specialization, but I am a quick study and eager to learn. > > Thank you > Dave > > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091217/bf2cd2eb/attachment-0001.htm > > ------------------------------ > > Message: 3 > Date: Tue, 22 Dec 2009 19:27:50 +0100 > From: Sense Hofstede > Subject: Re: Adopting Nautilus > To: Marcos Vanetta ,   Yazen Ghannam >        ,       Ubuntu Bugsquad >         > Message-ID: >         > Content-Type: text/plain; charset=UTF-8 > > 2009/12/22 Marcos Vanetta : >> Hi Qense, >> I'm going in! But I warn you, I'm really new in the world of bugs, I've been >> here for two weeks only! But I think this is gonna be huge! >> Also, my english is not perfect :D >> Where can I submit my name to the list? >> Regards >> malev >> >> 2009/12/22 Sense Hofstede >>> >>> Hello, >>> >>> Last UDS we discussed the idea of adopting a package. Some people >>> already were watching specific packages, but unfortunately the >>> Adopt-a-Package project seems a bit silent until now. >>> I had already adopted a few tiny packages, but I wanted to contribute >>> to the shape of a more important package. Therefore I added myself as >>> 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy >>> to tell you that currently all bugs reported against Nautilus that >>> were marked as 'Confirmed' have now been processed, leaving no bugs in >>> that state. Now I can start on the bugs still marked as New. >>> >>> However, this it is a lot of work, not only to get in shape, but also >>> to keep in shape. I would like to ask this maillist if there are any >>> people interested in becoming a godfather or godmother of Nautilus as >>> well. Because we would be the first group adopting a package it will >>> probably be a valuable learning exercise. Our group could be the >>> pioneer, uncovering difficulties and showing the benefits of adopting >>> a package. >>> >>> What would you need to do? Well, that would be something we could >>> discuss. Not everyone can or wants to spend the same amount of time on >>> bug triaging, so we would have to take that into account. We could >>> assign one or more people to just forwarding bugs upstream -- others >>> would just have to open upstream tasks when they encounter bugs that >>> need forwarding upstream. A different group could focus on incoming >>> New bug reports, and so on. Of course you don't have to limit yourself >>> strictly to one task, or join the forwarders group if you forward a >>> bug upstream once. >>> >>> If you're interested, please reply. >>> >>> Regards, >>> -- >>> Sense Hofstede >>> /?sen.s?? ?h?f.ste?d??/ >>> >>> PS: I realise I'm not the only one working on Nautilus bug reports >>> here. If you are doing that already as well, please consider formally >>> adopting the package as well and joining this coordination effort. In >>> a group we can work much more efficiently. >>> >>> -- >>> Ubuntu-bugsquad mailing list >>> Ubuntu-bugsquad at lists.ubuntu.com >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> >> >> -- >> Ing. Marcos Vanetta >> http://blog.malev.com.ar >> twitter: @malev >> > Hello, > > To both you and Yazen: > Thank you for your reply! I'm happy you are interested in helping with Nautilus. > However, there is not really a list, unless you mean the one at > . Actually that really > is a list, but so far the Adopt-a-Package project is not launched, so > it is more for letting others know who is working on what package. (Am > I correct?) > > Since you both said that you were not very experienced in bug triaging > I think it would be best if you would particularly focus on New bug > reports. [1] You don't have to wait until some official start since > there won't really be an official start and nothing should stop > someone from triaging a bug. ;) > > [1] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bugs?search=Search&field.status=New > > Regards, > -- > Sense Hofstede > /?sen.s?? ?h?f.ste?d??/ > > > > ------------------------------ > > Message: 4 > Date: Tue, 22 Dec 2009 18:43:10 +0000 > From: Bruno Girin > Subject: Re: Adopting Nautilus > To: Sense Hofstede > Cc: Ubuntu Bugsquad > Message-ID: <1261507390.2382.107.camel at nuuk> > Content-Type: text/plain; charset="UTF-8" > > On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: >> What would you need to do? Well, that would be something we could >> discuss. Not everyone can or wants to spend the same amount of time on >> bug triaging, so we would have to take that into account. We could >> assign one or more people to just forwarding bugs upstream -- others >> would just have to open upstream tasks when they encounter bugs that >> need forwarding upstream. A different group could focus on incoming >> New bug reports, and so on. Of course you don't have to limit yourself >> strictly to one task, or join the forwarders group if you forward a >> bug upstream once. >> >> If you're interested, please reply. > > Hi Sense, > > Count me in. I have some experience of triaging bugs (at least up to > getting them to the "Confirmed" state) and I would like to gain > experience in other areas of the bug process so hopefully I can take on > other tasks in the long run. My available time varies a lot but I'll try > to do a minimum to help. > > Cheers, > > Bruno > > > > > > ------------------------------ > > Message: 5 > Date: Tue, 22 Dec 2009 14:00:26 -0500 > From: Yazen Ghannam > Subject: Re: Adopting Nautilus > To: Bruno Girin > Cc: Ubuntu Bugsquad > Message-ID: <4B31174A.6000900 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello Everyone, > > I was just wondering, is it appropriate to mark a Wishlist action as > Confirmed if you can confirm the action yourself? Or is Confirmed only > used for Bugs? Thank you. > > Yazen Ghannam > > Bruno Girin wrote: >> On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: >> >>> What would you need to do? Well, that would be something we could >>> discuss. Not everyone can or wants to spend the same amount of time on >>> bug triaging, so we would have to take that into account. We could >>> assign one or more people to just forwarding bugs upstream -- others >>> would just have to open upstream tasks when they encounter bugs that >>> need forwarding upstream. A different group could focus on incoming >>> New bug reports, and so on. Of course you don't have to limit yourself >>> strictly to one task, or join the forwarders group if you forward a >>> bug upstream once. >>> >>> If you're interested, please reply. >>> >> >> Hi Sense, >> >> Count me in. I have some experience of triaging bugs (at least up to >> getting them to the "Confirmed" state) and I would like to gain >> experience in other areas of the bug process so hopefully I can take on >> other tasks in the long run. My available time varies a lot but I'll try >> to do a minimum to help. >> >> Cheers, >> >> Bruno >> >> >> >> > > > > ------------------------------ > > Message: 6 > Date: Tue, 22 Dec 2009 13:36:38 -0800 > From: Brian Murray > Subject: Invalid Apport Crashes > To: Ubuntu BugSquad > Message-ID: <20091222213638.GD25065 at murraytwins.com> > Content-Type: text/plain; charset="us-ascii" > > Apport until very recently[1] was reporting crashes that ended with a > signal of 24.  However, a crash of this type is a normal behavior as > such apport is now ignoring them.  What this means is that existing bugs > reported in Launchpad with a "Signal: 24" in the description can be > closed as Invalid.  I've compiled a list of these bug reports, which > includes duplicates, and it is attached. > > These should all be double checked to ensure they aren't being worked on > or something else is going on but if not they can be closed with a > comment like the following: > > "Thank you for taking the time to report this crash and helping to make > Ubuntu better.  We've discovered that apport was inappropriately > reporting signal 24 crashes.  These reports are a result of an > application exceeding limits set on CPU time which is normal behavior. > Subsequently, we are closing this bug report as Invalid.  We apologize > for any inconvenience this has caused.  Please report any future bugs or > crashes that you may have." > > Please also tag them as 'signal-24' so we can find them again more > easily - without a database query! > > [1] http://launchpad.net/bugs/498074 > > Thanks, > -- > Brian Murray                                                 @ubuntu.com > -------------- next part -------------- > LP: #475512 > LP: #475491 > LP: #475298 > LP: #474521 > LP: #474266 > LP: #473499 > LP: #473491 > LP: #473104 > LP: #472876 > LP: #472438 > LP: #472423 > LP: #472277 > LP: #471701 > LP: #471693 > LP: #470088 > LP: #469621 > LP: #469337 > LP: #469291 > LP: #469274 > LP: #469219 > LP: #469095 > LP: #469086 > LP: #469073 > LP: #468522 > LP: #468471 > LP: #468311 > LP: #468085 > LP: #467828 > LP: #467699 > LP: #467088 > LP: #467081 > LP: #466586 > LP: #466549 > LP: #466455 > LP: #466122 > LP: #466081 > LP: #466038 > LP: #465984 > LP: #465972 > LP: #465953 > LP: #465875 > LP: #465683 > LP: #465566 > LP: #465024 > LP: #464937 > LP: #464325 > LP: #463745 > LP: #463446 > LP: #463442 > LP: #462053 > LP: #461597 > LP: #460963 > LP: #460324 > LP: #459791 > LP: #458813 > LP: #458296 > LP: #458294 > LP: #456928 > LP: #455851 > LP: #455473 > LP: #454561 > LP: #454555 > LP: #453299 > LP: #453184 > LP: #453183 > LP: #452071 > LP: #451455 > LP: #451255 > LP: #451112 > LP: #450829 > LP: #450790 > LP: #450399 > LP: #450362 > LP: #449197 > LP: #447352 > LP: #447331 > LP: #447164 > LP: #445834 > LP: #445833 > LP: #445671 > LP: #445465 > LP: #445393 > LP: #445383 > LP: #444809 > LP: #444805 > LP: #444410 > LP: #443103 > LP: #442946 > LP: #442817 > LP: #442816 > LP: #441532 > LP: #438587 > LP: #438582 > LP: #437133 > LP: #436380 > LP: #432496 > LP: #430446 > LP: #429646 > LP: #424954 > LP: #424418 > LP: #419653 > LP: #418297 > LP: #417963 > LP: #417962 > LP: #414554 > LP: #413897 > LP: #411623 > LP: #403368 > LP: #403239 > LP: #396065 > LP: #395982 > LP: #395586 > LP: #395585 > LP: #395584 > LP: #395569 > LP: #393497 > LP: #393466 > LP: #392594 > LP: #380180 > LP: #380179 > LP: #377431 > LP: #376799 > LP: #356550 > LP: #355773 > LP: #349876 > LP: #312963 > LP: #311950 > LP: #311795 > LP: #306479 > LP: #301348 > LP: #292709 > LP: #286657 > LP: #286104 > LP: #285139 > LP: #283913 > LP: #282608 > LP: #282125 > LP: #282012 > LP: #281942 > LP: #281331 > LP: #279771 > LP: #277983 > LP: #274703 > LP: #272327 > LP: #271402 > LP: #269371 > LP: #266998 > LP: #264702 > LP: #223165 > LP: #221753 > LP: #218802 > LP: #217190 > LP: #216363 > LP: #214963 > LP: #214600 > LP: #213198 > LP: #212998 > LP: #210730 > LP: #210329 > LP: #209877 > LP: #207574 > LP: #207469 > LP: #203076 > LP: #195910 > LP: #194197 > LP: #192903 > LP: #192696 > LP: #190569 > LP: #189857 > LP: #189588 > LP: #187487 > LP: #185073 > LP: #184896 > LP: #183676 > LP: #182029 > LP: #176118 > LP: #155345 > LP: #155344 > LP: #151958 > LP: #150789 > LP: #148883 > LP: #148359 > LP: #148250 > LP: #148245 > LP: #148186 > LP: #147877 > LP: #147650 > LP: #147558 > LP: #147212 > LP: #147044 > LP: #145802 > LP: #145797 > LP: #144960 > LP: #134388 > LP: #132586 > LP: #130775 > LP: #130760 > LP: #102339 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 197 bytes > Desc: Digital signature > Url : https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091222/6eaa9888/attachment-0001.pgp > > ------------------------------ > > Message: 7 > Date: Tue, 22 Dec 2009 17:06:29 -0500 > From: komputes > Subject: Re: New to Bugsquad > To: David Crook > Cc: ubuntu-bugsquad at lists.ubuntu.com > Message-ID: <4B3142E5.6070009 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > David Crook wrote: >> Hello: >> >> My name is Dave Crook and I am requesting a mentor as I just joined the bugsquad. I am new user I have had  Ubuntu on my laptop for about 60 days. I would very much like to contribute to this wonderful project. >> >> I live in the USA new York State which is  Eastern time zone -5 GMT. I am normally available and on line  in the evenings after 18:00 hours. I have no area of specialization, but I am a quick study and eager to learn. >> >> Thank you >> Dave >> >> >> >> >> >> >> > Hi Dave, > > I would suggest starting by registering a Launchpad account. After that, > I would recommend going on IRC to go to the #ubuntu-bugs channel on the > Freenode IRC server. Feel free to contact me once on IRC should you have > any questions. > > -komputes > >  (]( -. .- )[) > > > > ------------------------------ > > Message: 8 > Date: Tue, 22 Dec 2009 17:16:13 -0500 > From: komputes > Subject: Re: Adopting Nautilus > To: Yazen Ghannam > Cc: Ubuntu Bugsquad > Message-ID: <4B31452D.4080700 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Yazen Ghannam wrote: >> Hello Everyone, >> >> I was just wondering, is it appropriate to mark a Wishlist action as >> Confirmed if you can confirm the action yourself? Or is Confirmed only >> used for Bugs? Thank you. >> >> Yazen Ghannam > Using common sense and past experience, I would say that if you can > confirm a bug or a feature request, mark the bug as confirmed and click > on the "This affects me" link. If the status is not "New" and you want > to mark it confirmed, please post the bug number so that it can be reviewed. > > -komputes > >  (]( -. .- )[) > > > > ------------------------------ > > Message: 9 > Date: Tue, 22 Dec 2009 19:39:28 -0300 > From: Marcos Vanetta > Subject: AdoptPackage > To: ubuntu-bugsquad at lists.ubuntu.com > Message-ID: >        <4cfc0be70912221439q3579340cx608a70e16950c6dd at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi! > I've found about this [1] after an email from qense. Then I've found this > [2] > As you probably know, I'm new at the bugsquad, and I think this could be > more educational in the road of learning triagging bugs. > So I wonder? > How can I do to singn me up in this? should I edit the wiki? or there is a > list. I don't know. > Nothing more for now. > regards > malev > > > [1] https://wiki.ubuntu.com/BugSquad/AdoptPackage > [2] https://wiki.ubuntu.com/QATeam/MainPackagesWithoutBugSubscribers > -- > Eng. Marcos Vanetta > http://blog.malev.com.ar > twitter: @malev > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091222/fa0fc810/attachment.htm > > ------------------------------ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > End of Ubuntu-bugsquad Digest, Vol 42, Issue 15 > *********************************************** > From ebouza at gmail.com Mon Dec 28 04:39:14 2009 From: ebouza at gmail.com (erick bouza) Date: Sun, 27 Dec 2009 23:39:14 -0500 Subject: Ubuntu-bugsquad Digest, Vol 42, Issue 17 In-Reply-To: References: Message-ID: <241ed31b0912272039i10bfafa0u304841eeb6874e81@mail.gmail.com> Happy Holidays to all, My name is Erick Bouza and I am also new to the Ubuntu bug squad. I would like to participate in the Nautilus package. I also would like a mentor to get me up to speed with the processes and different actions needed when a new bug report is reported. Sense Hofstede if you would like to contact me you can at ebouza at gmail.com. Regards, Big E On Thu, Dec 24, 2009 at 7:00 AM, wrote: > Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > Today's Topics: > > 1. Re: Ubuntu-bugsquad Digest, Vol 42, Issue 15 (David Crook) > > > ---------- Forwarded message ---------- > From: David Crook > To: ubuntu-bugsquad at lists.ubuntu.com > Date: Wed, 23 Dec 2009 09:03:28 -0500 > Subject: Re: Ubuntu-bugsquad Digest, Vol 42, Issue 15 > Hello komputes: > > I have registered on launchpad, user name flash, I have been > monitoring the IRC freenode chat room just out of curiosity. I am > going to reread the ho to triage bugs and start with earnest after > the first of the year. any direction would be appreciated. > > thanks > > To all: I would certainly would be interested in adopting the > nautilus bug reports > > > thanks > > Hope I am more of an asset than a liability but I am looking forward > to the challenge > > Happy Holidays to all > > On Tue, Dec 22, 2009 at 5:39 PM, > wrote: > > Send Ubuntu-bugsquad mailing list submissions to > > ubuntu-bugsquad at lists.ubuntu.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > or, via email, send a message with subject or body 'help' to > > ubuntu-bugsquad-request at lists.ubuntu.com > > > > You can reach the person managing the list at > > ubuntu-bugsquad-owner at lists.ubuntu.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Ubuntu-bugsquad digest..." > > > > > > Today's Topics: > > > > 1. Adopting Nautilus (Sense Hofstede) > > 2. New to Bugsquad (David Crook) > > 3. Re: Adopting Nautilus (Sense Hofstede) > > 4. Re: Adopting Nautilus (Bruno Girin) > > 5. Re: Adopting Nautilus (Yazen Ghannam) > > 6. Invalid Apport Crashes (Brian Murray) > > 7. Re: New to Bugsquad (komputes) > > 8. Re: Adopting Nautilus (komputes) > > 9. AdoptPackage (Marcos Vanetta) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 22 Dec 2009 13:07:31 +0100 > > From: Sense Hofstede > > Subject: Adopting Nautilus > > To: Ubuntu Bugsquad > > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8 > > > > Hello, > > > > Last UDS we discussed the idea of adopting a package. Some people > > already were watching specific packages, but unfortunately the > > Adopt-a-Package project seems a bit silent until now. > > I had already adopted a few tiny packages, but I wanted to contribute > > to the shape of a more important package. Therefore I added myself as > > 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy > > to tell you that currently all bugs reported against Nautilus that > > were marked as 'Confirmed' have now been processed, leaving no bugs in > > that state. Now I can start on the bugs still marked as New. > > > > However, this it is a lot of work, not only to get in shape, but also > > to keep in shape. I would like to ask this maillist if there are any > > people interested in becoming a godfather or godmother of Nautilus as > > well. Because we would be the first group adopting a package it will > > probably be a valuable learning exercise. Our group could be the > > pioneer, uncovering difficulties and showing the benefits of adopting > > a package. > > > > What would you need to do? Well, that would be something we could > > discuss. Not everyone can or wants to spend the same amount of time on > > bug triaging, so we would have to take that into account. We could > > assign one or more people to just forwarding bugs upstream -- others > > would just have to open upstream tasks when they encounter bugs that > > need forwarding upstream. A different group could focus on incoming > > New bug reports, and so on. Of course you don't have to limit yourself > > strictly to one task, or join the forwarders group if you forward a > > bug upstream once. > > > > If you're interested, please reply. > > > > Regards, > > -- > > Sense Hofstede > > /?sen.s?? ?h?f.ste?d??/ > > > > PS: I realise I'm not the only one working on Nautilus bug reports > > here. If you are doing that already as well, please consider formally > > adopting the package as well and joining this coordination effort. In > > a group we can work much more efficiently. > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Thu, 17 Dec 2009 13:54:41 -0800 (PST) > > From: David Crook > > Subject: New to Bugsquad > > To: ubuntu-bugsquad at lists.ubuntu.com > > Message-ID: <412546.65818.qm at web65302.mail.ac2.yahoo.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > Hello: > > > > My name is Dave Crook and I am requesting a mentor as I just joined the > bugsquad. I am new user I have had? Ubuntu on my laptop for about 60 days. I > would very much like to contribute to this wonderful project. > > > > I live in the USA new York State which is? Eastern time zone -5 GMT. I am > normally available and on line? in the evenings after 18:00 hours. I have no > area of specialization, but I am a quick study and eager to learn. > > > > Thank you > > Dave > > > > > > > > > > > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091217/bf2cd2eb/attachment-0001.htm > > > > ------------------------------ > > > > Message: 3 > > Date: Tue, 22 Dec 2009 19:27:50 +0100 > > From: Sense Hofstede > > Subject: Re: Adopting Nautilus > > To: Marcos Vanetta , Yazen Ghannam > > , Ubuntu Bugsquad > > > > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8 > > > > 2009/12/22 Marcos Vanetta : > >> Hi Qense, > >> I'm going in! But I warn you, I'm really new in the world of bugs, I've > been > >> here for two weeks only! But I think this is gonna be huge! > >> Also, my english is not perfect :D > >> Where can I submit my name to the list? > >> Regards > >> malev > >> > >> 2009/12/22 Sense Hofstede > >>> > >>> Hello, > >>> > >>> Last UDS we discussed the idea of adopting a package. Some people > >>> already were watching specific packages, but unfortunately the > >>> Adopt-a-Package project seems a bit silent until now. > >>> I had already adopted a few tiny packages, but I wanted to contribute > >>> to the shape of a more important package. Therefore I added myself as > >>> 'godfather' of Nautilus on the Bugs/AdoptPackage wiki page. I'm happy > >>> to tell you that currently all bugs reported against Nautilus that > >>> were marked as 'Confirmed' have now been processed, leaving no bugs in > >>> that state. Now I can start on the bugs still marked as New. > >>> > >>> However, this it is a lot of work, not only to get in shape, but also > >>> to keep in shape. I would like to ask this maillist if there are any > >>> people interested in becoming a godfather or godmother of Nautilus as > >>> well. Because we would be the first group adopting a package it will > >>> probably be a valuable learning exercise. Our group could be the > >>> pioneer, uncovering difficulties and showing the benefits of adopting > >>> a package. > >>> > >>> What would you need to do? Well, that would be something we could > >>> discuss. Not everyone can or wants to spend the same amount of time on > >>> bug triaging, so we would have to take that into account. We could > >>> assign one or more people to just forwarding bugs upstream -- others > >>> would just have to open upstream tasks when they encounter bugs that > >>> need forwarding upstream. A different group could focus on incoming > >>> New bug reports, and so on. Of course you don't have to limit yourself > >>> strictly to one task, or join the forwarders group if you forward a > >>> bug upstream once. > >>> > >>> If you're interested, please reply. > >>> > >>> Regards, > >>> -- > >>> Sense Hofstede > >>> /?sen.s?? ?h?f.ste?d??/ > >>> > >>> PS: I realise I'm not the only one working on Nautilus bug reports > >>> here. If you are doing that already as well, please consider formally > >>> adopting the package as well and joining this coordination effort. In > >>> a group we can work much more efficiently. > >>> > >>> -- > >>> Ubuntu-bugsquad mailing list > >>> Ubuntu-bugsquad at lists.ubuntu.com > >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >> > >> > >> > >> -- > >> Ing. Marcos Vanetta > >> http://blog.malev.com.ar > >> twitter: @malev > >> > > Hello, > > > > To both you and Yazen: > > Thank you for your reply! I'm happy you are interested in helping with > Nautilus. > > However, there is not really a list, unless you mean the one at > > . Actually that really > > is a list, but so far the Adopt-a-Package project is not launched, so > > it is more for letting others know who is working on what package. (Am > > I correct?) > > > > Since you both said that you were not very experienced in bug triaging > > I think it would be best if you would particularly focus on New bug > > reports. [1] You don't have to wait until some official start since > > there won't really be an official start and nothing should stop > > someone from triaging a bug. ;) > > > > [1] > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bugs?search=Search&field.status=New > > > > Regards, > > -- > > Sense Hofstede > > /?sen.s?? ?h?f.ste?d??/ > > > > > > > > ------------------------------ > > > > Message: 4 > > Date: Tue, 22 Dec 2009 18:43:10 +0000 > > From: Bruno Girin > > Subject: Re: Adopting Nautilus > > To: Sense Hofstede > > Cc: Ubuntu Bugsquad > > Message-ID: <1261507390.2382.107.camel at nuuk> > > Content-Type: text/plain; charset="UTF-8" > > > > On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: > >> What would you need to do? Well, that would be something we could > >> discuss. Not everyone can or wants to spend the same amount of time on > >> bug triaging, so we would have to take that into account. We could > >> assign one or more people to just forwarding bugs upstream -- others > >> would just have to open upstream tasks when they encounter bugs that > >> need forwarding upstream. A different group could focus on incoming > >> New bug reports, and so on. Of course you don't have to limit yourself > >> strictly to one task, or join the forwarders group if you forward a > >> bug upstream once. > >> > >> If you're interested, please reply. > > > > Hi Sense, > > > > Count me in. I have some experience of triaging bugs (at least up to > > getting them to the "Confirmed" state) and I would like to gain > > experience in other areas of the bug process so hopefully I can take on > > other tasks in the long run. My available time varies a lot but I'll try > > to do a minimum to help. > > > > Cheers, > > > > Bruno > > > > > > > > > > > > ------------------------------ > > > > Message: 5 > > Date: Tue, 22 Dec 2009 14:00:26 -0500 > > From: Yazen Ghannam > > Subject: Re: Adopting Nautilus > > To: Bruno Girin > > Cc: Ubuntu Bugsquad > > Message-ID: <4B31174A.6000900 at gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Hello Everyone, > > > > I was just wondering, is it appropriate to mark a Wishlist action as > > Confirmed if you can confirm the action yourself? Or is Confirmed only > > used for Bugs? Thank you. > > > > Yazen Ghannam > > > > Bruno Girin wrote: > >> On Tue, 2009-12-22 at 13:07 +0100, Sense Hofstede wrote: > >> > >>> What would you need to do? Well, that would be something we could > >>> discuss. Not everyone can or wants to spend the same amount of time on > >>> bug triaging, so we would have to take that into account. We could > >>> assign one or more people to just forwarding bugs upstream -- others > >>> would just have to open upstream tasks when they encounter bugs that > >>> need forwarding upstream. A different group could focus on incoming > >>> New bug reports, and so on. Of course you don't have to limit yourself > >>> strictly to one task, or join the forwarders group if you forward a > >>> bug upstream once. > >>> > >>> If you're interested, please reply. > >>> > >> > >> Hi Sense, > >> > >> Count me in. I have some experience of triaging bugs (at least up to > >> getting them to the "Confirmed" state) and I would like to gain > >> experience in other areas of the bug process so hopefully I can take on > >> other tasks in the long run. My available time varies a lot but I'll try > >> to do a minimum to help. > >> > >> Cheers, > >> > >> Bruno > >> > >> > >> > >> > > > > > > > > ------------------------------ > > > > Message: 6 > > Date: Tue, 22 Dec 2009 13:36:38 -0800 > > From: Brian Murray > > Subject: Invalid Apport Crashes > > To: Ubuntu BugSquad > > Message-ID: <20091222213638.GD25065 at murraytwins.com> > > Content-Type: text/plain; charset="us-ascii" > > > > Apport until very recently[1] was reporting crashes that ended with a > > signal of 24. However, a crash of this type is a normal behavior as > > such apport is now ignoring them. What this means is that existing bugs > > reported in Launchpad with a "Signal: 24" in the description can be > > closed as Invalid. I've compiled a list of these bug reports, which > > includes duplicates, and it is attached. > > > > These should all be double checked to ensure they aren't being worked on > > or something else is going on but if not they can be closed with a > > comment like the following: > > > > "Thank you for taking the time to report this crash and helping to make > > Ubuntu better. We've discovered that apport was inappropriately > > reporting signal 24 crashes. These reports are a result of an > > application exceeding limits set on CPU time which is normal behavior. > > Subsequently, we are closing this bug report as Invalid. We apologize > > for any inconvenience this has caused. Please report any future bugs or > > crashes that you may have." > > > > Please also tag them as 'signal-24' so we can find them again more > > easily - without a database query! > > > > [1] http://launchpad.net/bugs/498074 > > > > Thanks, > > -- > > Brian Murray @ubuntu.com > > -------------- next part -------------- > > LP: #475512 > > LP: #475491 > > LP: #475298 > > LP: #474521 > > LP: #474266 > > LP: #473499 > > LP: #473491 > > LP: #473104 > > LP: #472876 > > LP: #472438 > > LP: #472423 > > LP: #472277 > > LP: #471701 > > LP: #471693 > > LP: #470088 > > LP: #469621 > > LP: #469337 > > LP: #469291 > > LP: #469274 > > LP: #469219 > > LP: #469095 > > LP: #469086 > > LP: #469073 > > LP: #468522 > > LP: #468471 > > LP: #468311 > > LP: #468085 > > LP: #467828 > > LP: #467699 > > LP: #467088 > > LP: #467081 > > LP: #466586 > > LP: #466549 > > LP: #466455 > > LP: #466122 > > LP: #466081 > > LP: #466038 > > LP: #465984 > > LP: #465972 > > LP: #465953 > > LP: #465875 > > LP: #465683 > > LP: #465566 > > LP: #465024 > > LP: #464937 > > LP: #464325 > > LP: #463745 > > LP: #463446 > > LP: #463442 > > LP: #462053 > > LP: #461597 > > LP: #460963 > > LP: #460324 > > LP: #459791 > > LP: #458813 > > LP: #458296 > > LP: #458294 > > LP: #456928 > > LP: #455851 > > LP: #455473 > > LP: #454561 > > LP: #454555 > > LP: #453299 > > LP: #453184 > > LP: #453183 > > LP: #452071 > > LP: #451455 > > LP: #451255 > > LP: #451112 > > LP: #450829 > > LP: #450790 > > LP: #450399 > > LP: #450362 > > LP: #449197 > > LP: #447352 > > LP: #447331 > > LP: #447164 > > LP: #445834 > > LP: #445833 > > LP: #445671 > > LP: #445465 > > LP: #445393 > > LP: #445383 > > LP: #444809 > > LP: #444805 > > LP: #444410 > > LP: #443103 > > LP: #442946 > > LP: #442817 > > LP: #442816 > > LP: #441532 > > LP: #438587 > > LP: #438582 > > LP: #437133 > > LP: #436380 > > LP: #432496 > > LP: #430446 > > LP: #429646 > > LP: #424954 > > LP: #424418 > > LP: #419653 > > LP: #418297 > > LP: #417963 > > LP: #417962 > > LP: #414554 > > LP: #413897 > > LP: #411623 > > LP: #403368 > > LP: #403239 > > LP: #396065 > > LP: #395982 > > LP: #395586 > > LP: #395585 > > LP: #395584 > > LP: #395569 > > LP: #393497 > > LP: #393466 > > LP: #392594 > > LP: #380180 > > LP: #380179 > > LP: #377431 > > LP: #376799 > > LP: #356550 > > LP: #355773 > > LP: #349876 > > LP: #312963 > > LP: #311950 > > LP: #311795 > > LP: #306479 > > LP: #301348 > > LP: #292709 > > LP: #286657 > > LP: #286104 > > LP: #285139 > > LP: #283913 > > LP: #282608 > > LP: #282125 > > LP: #282012 > > LP: #281942 > > LP: #281331 > > LP: #279771 > > LP: #277983 > > LP: #274703 > > LP: #272327 > > LP: #271402 > > LP: #269371 > > LP: #266998 > > LP: #264702 > > LP: #223165 > > LP: #221753 > > LP: #218802 > > LP: #217190 > > LP: #216363 > > LP: #214963 > > LP: #214600 > > LP: #213198 > > LP: #212998 > > LP: #210730 > > LP: #210329 > > LP: #209877 > > LP: #207574 > > LP: #207469 > > LP: #203076 > > LP: #195910 > > LP: #194197 > > LP: #192903 > > LP: #192696 > > LP: #190569 > > LP: #189857 > > LP: #189588 > > LP: #187487 > > LP: #185073 > > LP: #184896 > > LP: #183676 > > LP: #182029 > > LP: #176118 > > LP: #155345 > > LP: #155344 > > LP: #151958 > > LP: #150789 > > LP: #148883 > > LP: #148359 > > LP: #148250 > > LP: #148245 > > LP: #148186 > > LP: #147877 > > LP: #147650 > > LP: #147558 > > LP: #147212 > > LP: #147044 > > LP: #145802 > > LP: #145797 > > LP: #144960 > > LP: #134388 > > LP: #132586 > > LP: #130775 > > LP: #130760 > > LP: #102339 > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: not available > > Type: application/pgp-signature > > Size: 197 bytes > > Desc: Digital signature > > Url : > https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091222/6eaa9888/attachment-0001.pgp > > > > ------------------------------ > > > > Message: 7 > > Date: Tue, 22 Dec 2009 17:06:29 -0500 > > From: komputes > > Subject: Re: New to Bugsquad > > To: David Crook > > Cc: ubuntu-bugsquad at lists.ubuntu.com > > Message-ID: <4B3142E5.6070009 at gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > David Crook wrote: > >> Hello: > >> > >> My name is Dave Crook and I am requesting a mentor as I just joined the > bugsquad. I am new user I have had Ubuntu on my laptop for about 60 days. I > would very much like to contribute to this wonderful project. > >> > >> I live in the USA new York State which is Eastern time zone -5 GMT. I > am normally available and on line in the evenings after 18:00 hours. I have > no area of specialization, but I am a quick study and eager to learn. > >> > >> Thank you > >> Dave > >> > >> > >> > >> > >> > >> > >> > > Hi Dave, > > > > I would suggest starting by registering a Launchpad account. After that, > > I would recommend going on IRC to go to the #ubuntu-bugs channel on the > > Freenode IRC server. Feel free to contact me once on IRC should you have > > any questions. > > > > -komputes > > > > (]( -. .- )[) > > > > > > > > ------------------------------ > > > > Message: 8 > > Date: Tue, 22 Dec 2009 17:16:13 -0500 > > From: komputes > > Subject: Re: Adopting Nautilus > > To: Yazen Ghannam > > Cc: Ubuntu Bugsquad > > Message-ID: <4B31452D.4080700 at gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Yazen Ghannam wrote: > >> Hello Everyone, > >> > >> I was just wondering, is it appropriate to mark a Wishlist action as > >> Confirmed if you can confirm the action yourself? Or is Confirmed only > >> used for Bugs? Thank you. > >> > >> Yazen Ghannam > > Using common sense and past experience, I would say that if you can > > confirm a bug or a feature request, mark the bug as confirmed and click > > on the "This affects me" link. If the status is not "New" and you want > > to mark it confirmed, please post the bug number so that it can be > reviewed. > > > > -komputes > > > > (]( -. .- )[) > > > > > > > > ------------------------------ > > > > Message: 9 > > Date: Tue, 22 Dec 2009 19:39:28 -0300 > > From: Marcos Vanetta > > Subject: AdoptPackage > > To: ubuntu-bugsquad at lists.ubuntu.com > > Message-ID: > > <4cfc0be70912221439q3579340cx608a70e16950c6dd at mail.gmail.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > Hi! > > I've found about this [1] after an email from qense. Then I've found this > > [2] > > As you probably know, I'm new at the bugsquad, and I think this could be > > more educational in the road of learning triagging bugs. > > So I wonder? > > How can I do to singn me up in this? should I edit the wiki? or there is > a > > list. I don't know. > > Nothing more for now. > > regards > > malev > > > > > > [1] https://wiki.ubuntu.com/BugSquad/AdoptPackage > > [2] https://wiki.ubuntu.com/QATeam/MainPackagesWithoutBugSubscribers > > -- > > Eng. Marcos Vanetta > > http://blog.malev.com.ar > > twitter: @malev > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20091222/fa0fc810/attachment.htm > > > > ------------------------------ > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > > > End of Ubuntu-bugsquad Digest, Vol 42, Issue 15 > > *********************************************** > > > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Erick Bouza Microsoft Certified Systems Engineer MCSE Certified -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Thu Dec 31 05:00:02 2009 From: cyan.spam at gmail.com (David Tombs) Date: Thu, 31 Dec 2009 00:00:02 -0500 Subject: FindRightPackage improvements In-Reply-To: <20090918162321.GO6455@murraytwins.com> References: <4AB2773C.9080409@gmail.com> <20090918162321.GO6455@murraytwins.com> Message-ID: <4B3C2FD2.4090609@gmail.com> Brian Murray wrote: > On Thu, Sep 17, 2009 at 01:51:56PM -0400, David Tombs wrote: >> Hello fellow bug squad members, >> >> I think the idea of changing bug reporting to only come via apport is a >> great idea. It is essential, however, that instructions for using apport >> are clear--and not only to technical users. I personally feel that our >> documentation is not clear at all, and would probably result in the vast >> majority of users giving up or assigning a random, incorrect package if >> forced to do so. >> >> The biggest problem to me seems to be >> . The page is pretty >> disorganized (with general instructions and lists of specific packages >> interspersed) and inconsistent in the technical level of the language. >> For example, "If you encounter a bug when booting the Live CD..." is >> pretty clear, but "Most distribution upgrades are performed with the >> package update-manager." is not so much (what is a distribution upgrade? >> FC -> Ubuntu? ;) ) >> >> So, I think some effort at streamlining the page, especially thinking >> through steps as though one has just started using Ubuntu, is in order. >> Specifically, categorizing the page into general instructions v. >> "scenarios" and toning down some of the Ubuntu lingo and technical >> language would be most helpful. Though I don't have much time to spare, >> I'd be glad to rewrite some parts of it I'm not sure what the policy is >> for that, however. >> >> What do you all think? > > I think this would be quite helpful for people and welcome any help you > can provide. With regards to the policy for rewriting it - I'd first > outline how you would like to specifically reorganize the page, in case > you don't get to all of it and so others can help, and then just dive > right in! I'm happy to help too. > Well, I totally forgot about this email so I just wrote up a new draft of the page, which I have attached. To summarize, I made the following significant changes: * Organized page into "Scenarios" and "Package-Specific" sections to improve navigation. * Removed all example ubuntu-bug command-lines, as I think this is irrelevant to the page. * Removed some advanced info on finding the executable name for an application, such as using ps or top. * Added specific symptoms that point to X bugs. * Removed instructions to gather info from .xsession-errors, since that has nothing to do with finding the right package, but instead is debugging information. Please let me know what ya'll think of the new page, especially if you think I degraded it at all! I want my work to make everyone's lives easier. Cheers, David -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: FindRightPackage.txt URL: