From andrew.conkling at gmail.com Tue Mar 4 15:09:38 2008 From: andrew.conkling at gmail.com (Andrew Conkling) Date: Tue, 4 Mar 2008 10:09:38 -0500 Subject: Interpreting stacktraces Message-ID: <616971f10803040709o1207d124l194a16e8bfc522de@mail.gmail.com> (Forgive me if this information is available on the wiki; I was unable to find anything specifically useful.) I've become more involved in triage for a few packages and have often come across stacktraces. Often I'm fairly sure I'm looking at duplicates of other bugs, but it can be really hard to tell. Rather than continue to stare at these bugs and traces blankly, I'm reaching out to see if there's any way I can learn to interpret them. I'm looking for general info (this would be useful on GNOME's bugzilla, for example), but understanding what Apport is doing would certainly be useful too. ;) Thanks in advance, Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From leann.ogasawara at canonical.com Wed Mar 5 03:45:50 2008 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Tue, 04 Mar 2008 19:45:50 -0800 Subject: Hug Day - 06 March 2008 Message-ID: <1204688750.9292.12.camel@emiko> Hi Everyone, On Thursday, March 6th, the bug squad will be tackling kernel bug reports. The focus will be migrating older kernel bugs to the current Hardy kernel. We'll be following up with reporters, confirming bug reports and assigning bug reports to the kernel team. The event will be held in #ubuntu-bugs on Freenode (irc.freenode.net). Our goal is to deal with all of the bugs listed at: https://wiki.ubuntu.com/UbuntuBugDay/20080306 While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, Leann Ogasawara From tom.berger at canonical.com Wed Mar 5 19:03:50 2008 From: tom.berger at canonical.com (Tom Berger) Date: Wed, 5 Mar 2008 19:03:50 +0000 Subject: Bug mail catch-up Message-ID: Hi, Tomorrow (6th March), we're going to send to ubuntu-bugs at lists.ubuntu.com bug notifications for Ubuntu dating from the 23rd and 24th of February. You may notice a much higher volume of bug notifications when we send these delayed emails. When we released the most recent version of Launchpad, we changed the way that bug contacts receive bug mail. Now, anyone can subscribe to receive bug notifications about a particular project, milestone, package or distribution. Unfortunately, we made a mistake during the upgrade and Ubuntu's bug contact was not immediately made into a subscriber to Ubuntu's bugs. We're sorry that you didn't receive these bug notifications on time and we hope that they're still going to be useful to you. You can find out more about bug subscriptions in our guide: https://help.launchpad.net/BugSubscriptions If you have any questions, please feel free to email me. Thanks, Tom Berger Launchpad Bug Tracker team. From brian at ubuntu.com Wed Mar 5 21:23:31 2008 From: brian at ubuntu.com (Brian Murray) Date: Wed, 5 Mar 2008 13:23:31 -0800 Subject: ubotu and bug announcements Message-ID: <20080305212331.GK8918@murraytwins.com> The bug bot in #ubuntu-bugs, ubotu, has stopped announcing new bug reports in the channel. This was done since a consensus seemed to be reached that ubotu was making it hard to work as a team in the channel. Hopefully, this will allow us to work more productively and make the irclogs[1] of ubuntu-bugs more useful. If you'd like to see the new bug announcements they are still happening in the #ubuntu-bugs-announce channel on Freenode. I'd also like to say thanks to Dennis 'Seveas' Kaarsemaker, ubotu's owner, for making this happen. [1] http://irclogs.ubuntu.com/ -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From oponek at gmail.com Mon Mar 10 15:29:49 2008 From: oponek at gmail.com (Piotr Zaryk) Date: Mon, 10 Mar 2008 16:29:49 +0100 Subject: Ubuntu Hardy black screen Message-ID: <87988a970803100829u5d87b103n4c0401e60a6fb4ba@mail.gmail.com> Hello, I reported this bug long time ago with no respond. Could someone help with it? https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/179472 -- Regards, Zaryk -------------- next part -------------- An HTML attachment was scrubbed... URL: From esimonmd at gmail.com Tue Mar 11 15:49:33 2008 From: esimonmd at gmail.com (Edwin Simon) Date: Tue, 11 Mar 2008 10:49:33 -0500 Subject: Realtek 8187b WLAN Message-ID: <25c450f90803110849k53423411h83e66ea180c3ef90@mail.gmail.com> I am have no wireless on Hardy Heron (64bit). The driver is from realtek and it has been difficult to compile it. Ed -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedro at ubuntu.com Tue Mar 11 18:20:32 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 11 Mar 2008 15:20:32 -0300 Subject: Hug Day - 13 March 2008 Message-ID: <1205259632.6481.12.camel@thylacine> Hello Ubuntu Lovers, Following with the Desktop Hug Days, Next Thursday, March 13th we'll be celebrating a Rhythmbox & Totem Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080313 Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday, March 13th, 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, pedro. From yuriy-kozlov at kubuntu.org Wed Mar 12 01:31:28 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Tue, 11 Mar 2008 21:31:28 -0400 Subject: Kubuntu Hug Day - 13 March 2008 Message-ID: <714626160803111831g268ac888o64d8b41bc2e9db5e@mail.gmail.com> Hello Kubuntu Lovers, Following with the Desktop Hug Days, Next Thursday, March 13th we'll be celebrating an Amarok Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080313/KDE Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday, March 13th, 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno, yuriy and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, ~ Yuriy From brian at ubuntu.com Sun Mar 16 23:06:14 2008 From: brian at ubuntu.com (Brian Murray) Date: Sun, 16 Mar 2008 16:06:14 -0700 Subject: Hug Day - 18 March 2008 Message-ID: <20080316230614.GC11040@murraytwins.com> With the imminent release of the Hardy Heron Beta we want to ensure that everyone will be able to upgrade to it. Subsequently, we'll be reviewing bugs about update-manager - the application that provides users the ability to upgrade from release to release in addition to standard package updates. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs and tasks is posted at: https://wiki.ubuntu.com/UbuntuBugDay/20080318 Our goal is to deal with all of the bugs on that list. So on 18 March 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From brian at ubuntu.com Mon Mar 17 00:07:47 2008 From: brian at ubuntu.com (Brian Murray) Date: Sun, 16 Mar 2008 17:07:47 -0700 Subject: Yesterday's Bugs Message-ID: <20080317000747.GE11040@murraytwins.com> I've setup a report[1] that shows yesterday's bug reports that are still in a New status. I thought this would be an interesting starting point for finding untriaged bug reports and that it would be a good way for us to find out if we are staying on top of new bug reports. The report is sorted in descending order by bug number and contains information about the bug number, package affected and the bug's summary. You might notice older bug numbers appearing on the list, this because they were set to affect another package yesterday. The report is updated every 15 minutes. Let me know if there are any ways the report can be improved. [1] http://people.ubuntu.com/~brian/reports/yesterday/ Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From thekorn at gmx.de Mon Mar 17 16:56:00 2008 From: thekorn at gmx.de (markus korn) Date: Mon, 17 Mar 2008 17:56:00 +0100 Subject: hugday-tools Message-ID: <1205772960.8180.42.camel@thekorn> Hi Everybody, I recently created a new project call 'hugday-tools' [0] to simplify participation on ubuntu hug days. There a currently a few tools available: * 'hugday list-days' - returns a list of all hugdays * 'hugday list' - returns a list of bugs for the current hugday * 'hugday close ' - mark the given bug as closed on the wiki-page Let me give you a briefer introduction on how to use this tools: First of all, get the current version from launchpad: $ bzr branch lp:hugday-tools $ cd hugday-tools You also need to install 'python-libxml2'. If you are interested in a list of all hug days ever announced run: $ ./hugday list-days To get a list of all bugs of the last announced hug day run $ ./hugday list You can filter the list by open/done bugs: $ ./hugday list --filter open  $ ./hugday list --filter done You might be interested in a former hug day, run $ ./hugday list --day 20080228 to get a list of all bugs for 28th february 2008. If there was also a hug day for KDE you can use the '--category' switch: $ ./hugday list --day 20080313 --category kde So far we did not change anythink on the wiki-page, lets mark some bugs as done. First you have to create a config file (~/.hugday_config) with your user name and your moin-id. 'hugday init' creates this file for you, just run: $ ./hugday init --email= --password= where and are your wiki.ubuntu.com login data. You can add "--user foobar" to change the name shown in the 'Triager' column from your wiki.ubuntu.com-username to 'foobar'. As a side note, it is also possible to extract your moin-id out of a mozilla cookie-file (tested with epiphany, FF2 and FF3): $ ./hugday init --cookie=path/to/cookie --user=thekorn To mark a bug as triaged you can run: $ ./hugday close 123456 Or to mark a set of bugs: $ ./hugday close 123456 2345 89659 My next idea is to create an applet similar to the five-a-day-applet. I hope this tools are useful, if you have any ideas, suggestions or you find any bugs, feel free to ping me. Markus [0] https://edge.launchpad.net/hugday-tools/ From pedro at ubuntu.com Tue Mar 18 19:37:28 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 18 Mar 2008 16:37:28 -0300 Subject: Celebrating Hug Day - 20 March 2008 Message-ID: <1205869048.14738.25.camel@thylacine> Hello Ubuntu Lovers, Following with Thursdays Hug Days, the March 20 we'll be celebrating a NetworkManager Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080320 Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday, March 20, 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, pedro. From yuriy-kozlov at kubuntu.org Wed Mar 19 01:50:20 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Tue, 18 Mar 2008 21:50:20 -0400 Subject: Kubuntu Hug Day - 20 March 2008 Message-ID: <714626160803181850gfe3dde5qeb9018fc71aee0d9@mail.gmail.com> Hello Kubuntu Lovers, Following with the Thursdays Hug Days, this Thursday, March 20th we'll be celebrating a KNetworkManager Hug Day: https://wiki.kubuntu.org/UbuntuBugDay/20080320/KDE Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bug reports, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday, March 20th, 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.kubuntu.org/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno, yuriy and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, ~ Yuriy From brian at ubuntu.com Wed Mar 19 04:29:52 2008 From: brian at ubuntu.com (Brian Murray) Date: Tue, 18 Mar 2008 21:29:52 -0700 Subject: Interpreting stacktraces In-Reply-To: <616971f10803040709o1207d124l194a16e8bfc522de@mail.gmail.com> References: <616971f10803040709o1207d124l194a16e8bfc522de@mail.gmail.com> Message-ID: <20080319042952.GP11040@murraytwins.com> On Tue, Mar 04, 2008 at 10:09:38AM -0500, Andrew Conkling wrote: > (Forgive me if this information is available on the wiki; I was unable to > find anything specifically useful.) There is a wiki page about apport at https://wiki.ubuntu.com/Apport but I am not sure it goes into the depth you want. > I've become more involved in triage for a few packages and have often come > across stacktraces. Often I'm fairly sure I'm looking at duplicates of other > bugs, but it can be really hard to tell. Rather than continue to stare at > these bugs and traces blankly, I'm reaching out to see if there's any way I > can learn to interpret them. Emmet Hickory (persia) gave a class in November on interpreting stack traces to in #ubuntu-classroom. I found the irc log at http://irclogs.ubuntu.com/2007/11/17/%23ubuntu-classroom.html but it may also be typed up better somewhere else. Is this the type of information you are looking for? Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From andrew.conkling at gmail.com Wed Mar 19 12:00:06 2008 From: andrew.conkling at gmail.com (Andrew Conkling) Date: Wed, 19 Mar 2008 08:00:06 -0400 Subject: Interpreting stacktraces In-Reply-To: <20080319042952.GP11040@murraytwins.com> References: <616971f10803040709o1207d124l194a16e8bfc522de@mail.gmail.com> <20080319042952.GP11040@murraytwins.com> Message-ID: <616971f10803190500n715db001p829ae7fbf15e9ed@mail.gmail.com> On Wed, Mar 19, 2008 at 12:29 AM, Brian Murray wrote: > On Tue, Mar 04, 2008 at 10:09:38AM -0500, Andrew Conkling wrote: > > I've become more involved in triage for a few packages and have often > come > > across stacktraces. Often I'm fairly sure I'm looking at duplicates of > other > > bugs, but it can be really hard to tell. Rather than continue to stare > at > > these bugs and traces blankly, I'm reaching out to see if there's any > way I > > can learn to interpret them. > > Emmet Hickory (persia) gave a class in November on interpreting stack > traces to in #ubuntu-classroom. I found the irc log at > http://irclogs.ubuntu.com/2007/11/17/%23ubuntu-classroom.html but it may > also be typed up better somewhere else. > > Is this the type of information you are looking for? > Hi Brian, Thanks for the reply; I was just thinking about this yesterday as I came across another bug with which I wasn't sure what to do. :) Skimming that IRC log you linked to, that does indeed look like exactly the info I need. Seems really interesting. I wish I could actually attend a lot of these sessions, but they're always scheduled while I'm at work. :) Offhand, do you know if any of the techniques change when I'm working with non-C (Python, Mono) applications? Thanks very much! Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From leann.ogasawara at canonical.com Mon Mar 24 21:00:41 2008 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Mon, 24 Mar 2008 14:00:41 -0700 Subject: Hug Day - 25 March 2008 Message-ID: <1206392441.10431.42.camel@emiko> Hi Everyone, Sorry for the late reminder. I just wanted to let you know we are going to have a Ubiquity Bug Day Tuesday March 25th. One of the first applications new Ubuntu users interact with is ubiquity - the Live CD installer. Since Hardy Beta was recently released, we felt it would be a good idea to focus on ubiquity bugs. The event will be held in #ubuntu-bugs on Freenode. Our goal is to deal with all of the bugs listed at: https://wiki.ubuntu.com/UbuntuBugDay/20080325 While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. Feel free to ask bdmurray, ogasawara, pedro, and heno of the QA Team as well as evand of the Installer team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, Leann Ogasawara From pedro at ubuntu.com Tue Mar 25 19:12:00 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 25 Mar 2008 16:12:00 -0300 Subject: Celebrating Hug Day! - 27 March 2008 Message-ID: <1206472320.6524.3.camel@thylacine> Hello Ubuntu Lovers, Following with the Desktop Hug Days of Thursdays, the March 27 of 2008 we'll be celebrating a GDM and GNOME Screensaver Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080327 Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on March 27 of 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask pedro, ogasawara, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, pedro. From sense.pc at gmail.com Sat Mar 22 18:31:09 2008 From: sense.pc at gmail.com (Sense Hofstede) Date: Sat, 22 Mar 2008 19:31:09 +0100 Subject: An idea Message-ID: <47E5506D.4010706@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In order to improve the bug reports forwarded upstream I think it would be a good idea to mail all upstream projects to ask what they'd like to have included in bug reports. E.g. what error logs and commands and other information. But also things we should watch. We could bundle this in one wiki page, maybe a new version of https://wiki.ubuntu.com/DebuggingProcedures. I'm willing to lead this project if I'm allowed too. ;) I think that if we can improve the reporting upstream things will get fixed a lot faster and better, so I think this project could really improve Ubuntu a lot. Any thoughts? Sense Hofstede (qense) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH5VBtxft9JZoh5JwRAjJHAJ9lcIuXdjl0CtEsqbUgGghhEpyTgACeL42d L9chj1kFMg7HlXa/0ylzPnk= =syQO -----END PGP SIGNATURE----- From wolfger at gmail.com Wed Mar 26 01:00:49 2008 From: wolfger at gmail.com (Wolfger) Date: Tue, 25 Mar 2008 21:00:49 -0400 Subject: An idea In-Reply-To: <47E5506D.4010706@gmail.com> References: <47E5506D.4010706@gmail.com> Message-ID: <3b00b3330803251800m7a3ba063v33cf8317c247a0b@mail.gmail.com> On Sat, Mar 22, 2008 at 2:31 PM, Sense Hofstede wrote: > > In order to improve the bug reports forwarded upstream I think it would > be a good idea to mail all upstream projects to ask what they'd like to > have included in bug reports. E.g. what error logs and commands and > other information. But also things we should watch. We could bundle this > in one wiki page, maybe a new version of > https://wiki.ubuntu.com/DebuggingProcedures. > I'm willing to lead this project if I'm allowed too. ;) Well, I think it's a good idea, and I am all in favor of whoever is willing to do the work doing it. -- Wolfger http://wolfger.wordpress.com/ AOL IM: wolf4coyot Yahoo!Messenger: wolfgersilberbaer -------------- next part -------------- An HTML attachment was scrubbed... URL: From ubuntu+lists at thequod.de Wed Mar 26 01:47:36 2008 From: ubuntu+lists at thequod.de (Daniel Hahler) Date: Wed, 26 Mar 2008 02:47:36 +0100 Subject: An idea: ask upstream about what they need in bug reports In-Reply-To: <47E5506D.4010706@gmail.com> References: <47E5506D.4010706@gmail.com> Message-ID: <200803260247.44496.ubuntu+lists@thequod.de> On Saturday 22 March 2008 19:31:09 Sense Hofstede wrote: > In order to improve the bug reports forwarded upstream I think it would > be a good idea to mail all upstream projects to ask what they'd like to > have included in bug reports. E.g. what error logs and commands and > other information. But also things we should watch. We could bundle this > in one wiki page, maybe a new version of > https://wiki.ubuntu.com/DebuggingProcedures. > I'm willing to lead this project if I'm allowed too. ;) > I think that if we can improve the reporting upstream things will get > fixed a lot faster and better, so I think this project could really > improve Ubuntu a lot. > > Any thoughts? Great idea! As far as I know, this could even be included in apport (through package-hooks), so that e.g. special files and information will be included in automatically reported bugs. Cheers, Daniel. -- http://daniel.hahler.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From yuriy-kozlov at kubuntu.org Wed Mar 26 01:49:33 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Tue, 25 Mar 2008 21:49:33 -0400 Subject: Celebrating Kubuntu Hug Day! 27 March 2008 Message-ID: <714626160803251849m3d7cc8c9i2846beee53f04547@mail.gmail.com> Hello Kubuntu Lovers, Following with the Desktop Hug Days of Thursdays, the March 27 of 2008 we'll be celebrating a Konqueror Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080327/KDE Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on March 27 of 2008 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask pedro, ogasawara, heno, yuriy and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, ~ Yuriy From fnord at pentabarf.de Wed Mar 26 21:26:14 2008 From: fnord at pentabarf.de (Kjell Braden) Date: Wed, 26 Mar 2008 22:26:14 +0100 Subject: script for mass-editing duplicates Message-ID: <1206566774.7227.23.camel@hegg> Hi, some weeks ago Brian and I had a talk about mass-moving duplicates, e.g. when apport is wrong multiple times and you get lots of false positives, and he recommended to write a script using python-lp-bugs for that. I've attached the result, as I think it might be somewhat useful for the bugsquad. It's working like this: $ ./move-duplicates -m 1 123 456 789 ...marks bug 123, bug 456, bug 789 and their duplicates and their duplicates as duplicate of bug 1, regardless of their former masterbugs. If you want to move the former masterbugs and other duplicates of them too, use: $ ./move-duplicates --also-move-masterbugs -m 1 123 456 789 I hope it'll be useful, feel free to ask questions, make suggestions or report bugs :) (duh, forgot one thing: you will need to adjust the cookies variable in the script to match your authentication file) Kjell -------------- next part -------------- A non-text attachment was scrubbed... Name: move-duplicates Type: text/x-python Size: 2220 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From henrik at canonical.com Thu Mar 27 11:00:39 2008 From: henrik at canonical.com (Henrik Nilsen Omma) Date: Thu, 27 Mar 2008 11:00:39 +0000 Subject: An idea In-Reply-To: <47E5506D.4010706@gmail.com> References: <47E5506D.4010706@gmail.com> Message-ID: <47EB7E57.2010600@canonical.com> Sense Hofstede wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In order to improve the bug reports forwarded upstream I think it would > be a good idea to mail all upstream projects to ask what they'd like to > have included in bug reports. E.g. what error logs and commands and > other information. But also things we should watch. We could bundle this > in one wiki page, maybe a new version of > https://wiki.ubuntu.com/DebuggingProcedures. > I'm willing to lead this project if I'm allowed too. ;) > I think that if we can improve the reporting upstream things will get > fixed a lot faster and better, so I think this project could really > improve Ubuntu a lot. > Hi Sense, I agree this work is very much needed. In order to make out bug reports more useful to upstream they need to a) be of generally good quality, including all relevant information, and b) we need to have an understanding of how the upstream bug trackers and workflow around bugs works. I've started on a set of tutorial pages for upstream bug trackers that will make it easier for our triage teams to file good bugs upstream. These pages still need lots of work, and should include details not just on the bug trackers but also on the general culture around bugs in the upstream project. Please help flesh these out! https://wiki.ubuntu.com/Bugs/Upstream We have invited a few upstream bugmasters to FOSSCamp in Prague and hope to have a good exchange of ideas there. One example of where upstream involvement on bugs worked really well was the Amarok bug day, which led the Amarok folks to do a second bug day in the upstream tracker. http://blog.lydiapintscher.de/2008/03/14/hug-the-bugs-2/ We should figure out how to expand this to other projects too. Sense, thanks for stepping up to start this work :) Henrik From fnord at pentabarf.de Thu Mar 27 22:29:31 2008 From: fnord at pentabarf.de (Kjell Braden) Date: Thu, 27 Mar 2008 23:29:31 +0100 Subject: Do 5 a day - every day! In-Reply-To: <47BD90AE.60108@ubuntu.com> References: <47BD90AE.60108@ubuntu.com> Message-ID: <1206656971.7191.23.camel@hegg> On Do, 2008-02-21 at 15:54 +0100, Daniel Holbach wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello everybody, > > What is 5-A-Day? > We, that means everybody, will do 5 bugs a day - every day. With only > five bugs that everybody looks at every day, we will cover a lot of ground. > > What you can do? That's up to you, your interests and your abilities. > - If you're a developer, you can help out reviewing patches and getting > them uploaded. > - If you want to just confirm new bugs, you can do that. > - If you have experience with a certain package and want to triage bugs > you can do that and forward them upstream if necessary. > - If you know your way around Ubuntu quite well, you can help assign > bugs to the right package. > > What you need to do to participate? > - Do it! Follow the instructions on the 5-A-Day homepage [0] > - Spread the word by adding your 5 a day to your mailing list posts [1] > - Add them to your blog posts (join http://ubuntuweblogs.org/ [2] if > you're interested) > > [0] https://wiki.ubuntu.com/5-A-Day > [1] https://wiki.ubuntu.com/5-A-Day#Log > [2] (follow the instructions on http://ubuntuweblogs.org/submit.html) > > This is your chance to make a difference. > > Have a great day, > Daniel > > - -- > My 5 today: #193823 (alsa-utils), #86235 (gstreamer0.10-ffmpeg), #193920 > (mlocate), #181860 (console-setup), #190744 (libgdamm3.0) > Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHvZCuRjrlnQWd1esRAkcpAJ437++eKWpPoqANvqKKvpau6UNtagCfbY/m > 9bzYPD9sc/cyF1RR1PKAsS8= > =H2Jc > -----END PGP SIGNATURE----- > Me again :) Posted a question regarding a similar issue, but didn't know I can't subscribe people to questions (yet): https://answers.launchpad.net/5-a-day-data/+question/28167 Daniel, may you have a look please? Thanks a lot, -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From thekorn at gmx.de Fri Mar 28 07:00:29 2008 From: thekorn at gmx.de (markus korn) Date: Fri, 28 Mar 2008 08:00:29 +0100 Subject: Do 5 a day - every day! In-Reply-To: <7533d3600803271634y5e3252c6l9e83a85a6cbf9925@mail.gmail.com> References: <47BD90AE.60108@ubuntu.com> <1206656971.7191.23.camel@hegg> <7533d3600803271634y5e3252c6l9e83a85a6cbf9925@mail.gmail.com> Message-ID: <7533d3600803280000v776dc9caw30961c73aafd4de9@mail.gmail.com> Sorry for resending this, but I send my first mail with the wrong account. > > Me again :) > > Posted a question regarding a similar issue, but didn't know I can't > subscribe people to questions (yet): > https://answers.launchpad.net/5-a-day-data/+question/28167 > Daniel, may you have a look please? Thanks a lot, > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Hi, without knowing the code which creates the stats-page, i think I know what causes this diff: 1.) about 10 bugs in Kjell's list are private, like 176450. 2.) ~30 bugs in his list have more than one task, so e.g. getting the status of such an bug raises an AttributeError in py-lp-bugs ("There is no row of the info-table linked to this bugreport") There is a diff between the number of bugs in the data file and the number of bugs on the stats page for almost all people. Markus From daniel.holbach at ubuntu.com Fri Mar 28 08:16:18 2008 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Fri, 28 Mar 2008 09:16:18 +0100 Subject: Do 5 a day - every day! In-Reply-To: <7533d3600803280000v776dc9caw30961c73aafd4de9@mail.gmail.com> References: <47BD90AE.60108@ubuntu.com> <1206656971.7191.23.camel@hegg> <7533d3600803271634y5e3252c6l9e83a85a6cbf9925@mail.gmail.com> <7533d3600803280000v776dc9caw30961c73aafd4de9@mail.gmail.com> Message-ID: <47ECA952.30904@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 markus korn schrieb: > without knowing the code which creates the stats-page, i think I know > what causes this diff: > 1.) about 10 bugs in Kjell's list are private, like 176450. > 2.) ~30 bugs in his list have more than one task, so e.g. getting > the status of such an bug raises an AttributeError in py-lp-bugs > ("There is no row of the info-table linked to this bugreport") > > There is a diff between the number of bugs in the data file and the > number of bugs on the stats page for almost all people. The "is valid Ubuntu bug" check was broken and I disabled it for now. For one it did not consider duplicates. The next cron run should fix it. Have a nice day, Daniel - -- My 5 today: #207863 (qt4-x11), #195806 (purrr), #207705 (meep), #204341 (gchempaint), #207683 (illuminator) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH7KlSRjrlnQWd1esRApQ/AJwNVzHXvasdjWWkk3SgnYjzoBv0JACdFUdJ V+lWn5UdAsT8KsZijCytW8E= =XjEZ -----END PGP SIGNATURE----- From markus.korn at htp-tel.de Thu Mar 27 23:34:05 2008 From: markus.korn at htp-tel.de (markus korn) Date: Fri, 28 Mar 2008 00:34:05 +0100 Subject: Do 5 a day - every day! In-Reply-To: <1206656971.7191.23.camel@hegg> References: <47BD90AE.60108@ubuntu.com> <1206656971.7191.23.camel@hegg> Message-ID: <7533d3600803271634y5e3252c6l9e83a85a6cbf9925@mail.gmail.com> > > Me again :) > > Posted a question regarding a similar issue, but didn't know I can't > subscribe people to questions (yet): > https://answers.launchpad.net/5-a-day-data/+question/28167 > Daniel, may you have a look please? Thanks a lot, > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Hi, without knowing the code which creates the stats-page, i think I know what causes this diff: 1.) about 10 bugs in Kjell's list are private, like 176450. 2.) ~30 bugs in his list have more than one task, so e.g. getting the status of such an bug raises an AttributeError in py-lp-bugs ("There is no row of the info-table linked to this bugreport") There is a diff between the number of bugs in the data file and the number of bugs on the stats page for almost all people. Markus From brian at ubuntu.com Mon Mar 31 22:06:06 2008 From: brian at ubuntu.com (Brian Murray) Date: Mon, 31 Mar 2008 15:06:06 -0700 Subject: Bug Day - 01 April 2008 Message-ID: <20080331220606.GC11040@murraytwins.com> It's no joke our next bug day is Tuesday, April 1st! In Launchpad it is possible to monitor upstream bug reports by adding a bug watch and sometimes Launchpad users will add a comment mentioning a url associated with an upstream bug tracker but not add the bug watch. We'll be looking at bug reports with comments regarding the GNOME bug tracker and adding the upstream watch where appropriate. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs and tasks is posted at: https://wiki.ubuntu.com/UbuntuBugDay/20080401 Our goal is to deal with all of the bugs on that list. So on 01 April 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno, jcastro and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From sense.pc at gmail.com Thu Mar 27 15:23:44 2008 From: sense.pc at gmail.com (Sense Hofstede) Date: Thu, 27 Mar 2008 16:23:44 +0100 Subject: Gaining triaging information about packages Message-ID: <47EBBC00.8040000@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've started the first page of the information database. The main way of gaining data is now not by mailing all the maintainers but by looking at the websites of the packages for information. If there isn't enough provided we can always email them. The page is is located at http://wiki.ubuntu.com/Bugs/Triaging If you want to help, please do. Don't hesitate to edit pages if you feel you've got something useful to add. At the moment the plan is to use the already existing pages of http://wiki.ubuntu.com/DebuggingProcedures by including them in pages with the name Bugs/Triaging/Name But what naming should we use exactly? Bugs/Triaging/Group/Name (e.g. Bugs/Triaging/Mozilla/Firefox) or Bugs/Triaging/Name (e.g. Bugs/Triaging/Firefox)? Sense Hofstede (qense) PS: This email comes from another email address as the initial idea. That was accidentiatly send from my Dutch email address. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH67wAxft9JZoh5JwRAoDMAKC1/p2EiWbB2yi9/LE9H1NUz1c+BwCaA4IX wfCvw75tzJliRymtrD40w+k= =KIhD -----END PGP SIGNATURE----- From brian at ubuntu.com Mon Mar 31 22:40:55 2008 From: brian at ubuntu.com (Brian Murray) Date: Mon, 31 Mar 2008 15:40:55 -0700 Subject: Gaining triaging information about packages In-Reply-To: <47EBBC00.8040000@gmail.com> References: <47EBBC00.8040000@gmail.com> Message-ID: <20080331224055.GD11040@murraytwins.com> On Thu, Mar 27, 2008 at 04:23:44PM +0100, Sense Hofstede wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've started the first page of the information database. The main way of > gaining data is now not by mailing all the maintainers but by looking at > the websites of the packages for information. If there isn't enough > provided we can always email them. The page is is located at > http://wiki.ubuntu.com/Bugs/Triaging > If you want to help, please do. Don't hesitate to edit pages if you feel > you've got something useful to add. At the moment the plan is to use the > already existing pages of http://wiki.ubuntu.com/DebuggingProcedures by > including them in pages with the name Bugs/Triaging/Name > But what naming should we use exactly? Bugs/Triaging/Group/Name (e.g. > Bugs/Triaging/Mozilla/Firefox) or Bugs/Triaging/Name (e.g. > Bugs/Triaging/Firefox)? I think gathering this information is a great idea and it will help us create better quality bug reports. There does seem to be a fair bit of overlap with the existing Debugging Procedures page though. Is there some reason a "How to Forward" section wouldn't work in a package's debugging page? It was my thought that a package's Debugging page would be its main page if you will. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: