From kamusin at gmail.com Tue Sep 1 21:25:13 2009 From: kamusin at gmail.com (Kamus) Date: Tue, 1 Sep 2009 17:25:13 -0400 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 03 September 2009 Message-ID: Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* Network Manager! * 200 New bugs need a hug. * 100 Incomplete bugs need a status check. * 80 Confirmed bugs need a review. * 12 Bugs that need to be send upstream. Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 03 of September 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090903 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) 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! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Victor Vargas(irc kamusin, aka "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 Thu Sep 3 21:26:39 2009 From: brian at ubuntu.com (Brian Murray) Date: Thu, 3 Sep 2009 14:26:39 -0700 Subject: Packages without bug subscribers Message-ID: <20090903212639.GM6386@murraytwins.com> Recently there was some discussion about packages that might have no one looking after bugs reported about them. One way to monitor bugs about a package, in Launchpad, is to subscribe to all of the package's bug mail. This can be done by going to http://launchpad.net/ubuntu/+source/acpid and clicking "Subscribe to bug mail". (Of course replacing apcid with the package you are interested in.) I went looking for these packages and have compiled a wiki page[1] with some of them. (A complete csv file is also attached to that page.) There are approximately 850 of these packages in main, and not having people subscribed to a package's bug reports may make sense in some cases. However, there are still clearly some packages that need monitoring and some bug cleanup done. The cleanup[2] can be fairly easy with the right tools too! How can you help? If there is a package that you or a team you are member of cares for - subscribe to the bug mail. Some teams, like ubuntu-x and desktop-bugs, have mailing lists specifically setup for their bug mail. Alternatively, review and triage a package's existing bug reports. [1] https://wiki.ubuntu.com/QATeam/MainPackagesWithoutBugSubscribers [2] http://www.murraytwins.com/blog/?p=45 -- 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 pedro at ubuntu.com Wed Sep 9 14:57:45 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Wed, 09 Sep 2009 10:57:45 -0400 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 10 September 2009 Message-ID: <1252508265.4644.15.camel@wombat> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Firefox-3.5! * 39 New bugs need a hug * 33 Incomplete bugs need a status check * 13 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 10 September 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090910 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From soeren.b.c at gmail.com Sun Sep 13 14:49:21 2009 From: soeren.b.c at gmail.com (=?ISO-8859-1?Q?S=F8ren_Bredlund_Caspersen?=) Date: Sun, 13 Sep 2009 16:49:21 +0200 Subject: Network and wifi bugs Message-ID: Hi everyone I'm trying to triage a few bugs (from the EasyTasks list) using the info at this wiki page: https://wiki.ubuntu.com/Bugs/FindRightPackage However I can't seem to find any info of what packages to assign bugs that are about network connections or wifi. One example could be: https://bugs.launchpad.net/ubuntu/+bug/428276 I hope some of you can help me. Cheers Søren From soeren.b.c at gmail.com Mon Sep 14 07:38:18 2009 From: soeren.b.c at gmail.com (=?ISO-8859-1?Q?S=F8ren_Bredlund_Caspersen?=) Date: Mon, 14 Sep 2009 09:38:18 +0200 Subject: Dead links Message-ID: Hi all! While reading up on bug triaging I have stumbled upon some dead links on the wiki pages. The following links look dead: http://people.canonical.com/~brian/reports/gt5subscribers/no-package.html http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html They can be found at these two pages: https://wiki.ubuntu.com/5-A-Day https://wiki.ubuntu.com/Bugs/EasyTasks Cheers Søren From brian at ubuntu.com Mon Sep 14 17:52:05 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 14 Sep 2009 10:52:05 -0700 Subject: Dead links In-Reply-To: References: Message-ID: <20090914175205.GG5102@murraytwins.com> On Mon, Sep 14, 2009 at 09:38:18AM +0200, Søren Bredlund Caspersen wrote: > Hi all! > > While reading up on bug triaging I have stumbled upon some dead links > on the wiki pages. Thanks for bringing this up I've fixed the ones you've pointed out and am including the active links in case anyone is interested. > The following links look dead: > http://people.canonical.com/~brian/reports/gt5subscribers/no-package.html http://qa.ubuntu.com/reports/package/gt5subscribers/no-package.html > http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html > http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html -- 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 leann.ogasawara at canonical.com Mon Sep 14 19:02:16 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Mon, 14 Sep 2009 12:02:16 -0700 Subject: Kernel Bug Day - Tues 15 Sept, 2009 Message-ID: <1252954936.4063.186.camel@emiko> Hi Everyone, Just another friendly reminder that the next kernel bug day will be held Tues. the 15th of Sept, 2009 [1]. The focus of the bug day will be kernel oopses/panics. Each kernel team member is responsible for a specific subset of bugs however community involvement is also greatly appreciated. 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/20090915 From brian at ubuntu.com Mon Sep 14 19:36:42 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 14 Sep 2009 12:36:42 -0700 Subject: Network and wifi bugs In-Reply-To: References: Message-ID: <20090914193642.GH5102@murraytwins.com> On Sun, Sep 13, 2009 at 04:49:21PM +0200, Søren Bredlund Caspersen wrote: > Hi everyone > > I'm trying to triage a few bugs (from the EasyTasks list) using the > info at this wiki page: > https://wiki.ubuntu.com/Bugs/FindRightPackage > > However I can't seem to find any info of what packages to assign bugs > that are about network connections or wifi. > One example could be: > https://bugs.launchpad.net/ubuntu/+bug/428276 Your specific example is hardware related as the device was not being detected my network manager (indicated by the reporter) and there was not a driver for it (see lspci -vvnn output). In that case the correct package is linux. You might also be interested in http://wiki.ubuntu.com/DebuggingNetworkManager. -- 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 tixu at numericable.fr Sat Sep 12 12:21:38 2009 From: tixu at numericable.fr (tixu at numericable.fr) Date: Sat, 12 Sep 2009 14:21:38 +0200 (CEST) Subject: Creative zen crashes when pluged on ubuntu 9.04 Message-ID: An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Sep 15 17:53:19 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 15 Sep 2009 10:53:19 -0700 Subject: Launchpad Bug Filing Changes for Ubuntu Message-ID: <20090915175319.GA6455@murraytwins.com> 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. In order to make the transition for our users smoother, we'd like to ask you to help out with a few things: 1) If you take care of a high-profile package, consider adding it to https://wiki.ubuntu.com/Bugs/FindRightPackage which is linked to from https://help.ubuntu.com/community/ReportingBugs. 2) Please consider writing an apport hook for the packages you take care of, if you need special information in bug reports - it's REALLY easy: https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks 3) If the area of Ubuntu that you take care of is better suited by symptom based bug reporting ("storage", "boot", "install", "sound", etc.), consider contributing to the apport-symptoms package - it too is REALLY easy: https://wiki.ubuntu.com/Apport/DeveloperHowTo#Symptoms By helping us receive higher quality bug reports, we will help to help make Ubuntu even better! [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption (*) There will be a +filebug?no-redirect if you really really need it. -- Brian Murray On behalf of the Ubuntu QA Team -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From macoafi at gmail.com Tue Sep 15 19:05:09 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 15 Sep 2009 15:05:09 -0400 Subject: Creative zen crashes when pluged on ubuntu 9.04 In-Reply-To: References: Message-ID: <200909151505.09858.macoafi@gmail.com> On Saturday 12 September 2009 8:21:38 am tixu at numericable.fr wrote: > Hello, > > On a Compaq presario 2500 the player crashes about 10s after being plugged > under "gnome" or after a program attempt to access the player under > "fluxbox" (like the command "mtpfs" or "gnomad2"). I've tried with another > version of ubuntu but I've the same problem and before I updated the > firmware it worked well. This new firmware is for Europe only, on this > page you'll see it : http://support.creative.com/downloads/?h=7 > (1.21.03e). So the problem is not the version of Ubuntu or my computer but > the new firmware that works under Windows but crashes under linux. > > Thanks for help me to let the developpers know this bug. Sounds like you ought to be reporting this to Creative. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo From yuriy-kozlov at kubuntu.org Tue Sep 15 19:13:28 2009 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Tue, 15 Sep 2009 15:13:28 -0400 Subject: Launchpad Bug Filing Changes for Ubuntu In-Reply-To: <20090915175319.GA6455@murraytwins.com> References: <20090915175319.GA6455@murraytwins.com> Message-ID: <714626160909151213u6767d083tee27e69b78e3f22b@mail.gmail.com> On Tue, Sep 15, 2009 at 1:53 PM, 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. > > In order to make the transition for our users smoother, we'd like to ask > you to help out with a few things: > > 1) If you take care of a high-profile package, consider adding it to > https://wiki.ubuntu.com/Bugs/FindRightPackage which is linked to from > https://help.ubuntu.com/community/ReportingBugs. > > 2) Please consider writing an apport hook for the packages you take care > of, if you need special information in bug reports - it's REALLY easy: > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks > > 3) If the area of Ubuntu that you take care of is better suited by > symptom based bug reporting ("storage", "boot", "install", "sound", > etc.), consider contributing to the apport-symptoms package - it too is > REALLY easy: > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Symptoms > > By helping us receive higher quality bug reports, we will help to help > make Ubuntu even better! > > [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption > (*) There will be a +filebug?no-redirect if you really really need it. > > -- > Brian Murray > On behalf of the Ubuntu QA Team Hi Brian, Would it be possible to direct to a different page for some packages? In particular, I would like to see Kubuntu screenshots on the page for the relevant packages. There is currently such a page here: https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting but it needs some updating. Kubuntu Karmic enables apport-bug for everything, so the normal ReportingBugs page is accurate except for the screenshots and the system monitor instructions. ~ Yuriy From brian at ubuntu.com Tue Sep 15 23:37:15 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 15 Sep 2009 16:37:15 -0700 Subject: Launchpad Bug Filing Changes for Ubuntu In-Reply-To: <714626160909151213u6767d083tee27e69b78e3f22b@mail.gmail.com> References: <20090915175319.GA6455@murraytwins.com> <714626160909151213u6767d083tee27e69b78e3f22b@mail.gmail.com> Message-ID: <20090915233715.GC6455@murraytwins.com> On Tue, Sep 15, 2009 at 03:13:28PM -0400, Yuriy Kozlov wrote: > On Tue, Sep 15, 2009 at 1:53 PM, 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. > > > > In order to make the transition for our users smoother, we'd like to ask > > you to help out with a few things: > > > > 1) If you take care of a high-profile package, consider adding it to > > https://wiki.ubuntu.com/Bugs/FindRightPackage which is linked to from > > https://help.ubuntu.com/community/ReportingBugs. > > > > 2) Please consider writing an apport hook for the packages you take care > > of, if you need special information in bug reports - it's REALLY easy: > > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks > > > > 3) If the area of Ubuntu that you take care of is better suited by > > symptom based bug reporting ("storage", "boot", "install", "sound", > > etc.), consider contributing to the apport-symptoms package - it too is > > REALLY easy: > > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Symptoms > > > > By helping us receive higher quality bug reports, we will help to help > > make Ubuntu even better! > > > > [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption > > (*) There will be a +filebug?no-redirect if you really really need it. > > > > -- > > Brian Murray > > On behalf of the Ubuntu QA Team > > Hi Brian, > > Would it be possible to direct to a different page for some packages? No, the way the Launchpad code is written the redirect is done for every package related to the Ubuntu distribution - not on a per package basis. > In particular, I would like to see Kubuntu screenshots on the page for > the relevant packages. There is currently such a page here: > https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting but it needs some > updating. Kubuntu Karmic enables apport-bug for everything, so the > normal ReportingBugs page is accurate except for the screenshots and > the system monitor instructions. I hadn't see that wiki page before it looks very nice! Perhaps close to the very top of the ReportingBugs wiki page we should have a link for Kubuntu users to the page you indicated? -- 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 Wed Sep 16 22:33:04 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 16 Sep 2009 15:33:04 -0700 Subject: Ubuntu Bug Day - 20090917 Message-ID: <20090916223304.GE6455@murraytwins.com> I've just finished setting up the next Bug Day wiki page[1] dealing with bugs with out a package. Since there are quite a few of these, approximately 2300, and they are all in the new state I thought it'd be interesting to populate the target list with some unique criteria. So there are categories for bugs with attachments, which may be a good hint as to the package, and ones with certain numbers of subscribers, comments and duplicates. Hopefully, we can drive the number of bugs without a package down and the +filebug changes will prevent more of them from being reported. [1] https://wiki.ubuntu.com/UbuntuBugDay/20090917 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 cyan.spam at gmail.com Thu Sep 17 17:51:56 2009 From: cyan.spam at gmail.com (David Tombs) Date: Thu, 17 Sep 2009 13:51:56 -0400 Subject: FindRightPackage improvements Message-ID: <4AB2773C.9080409@gmail.com> 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? Regards, David Tombs From brian at ubuntu.com Fri Sep 18 16:23:21 2009 From: brian at ubuntu.com (Brian Murray) Date: Fri, 18 Sep 2009 09:23:21 -0700 Subject: FindRightPackage improvements In-Reply-To: <4AB2773C.9080409@gmail.com> References: <4AB2773C.9080409@gmail.com> Message-ID: <20090918162321.GO6455@murraytwins.com> 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. -- 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 caroline.ford.work at googlemail.com Sun Sep 20 18:53:00 2009 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Sun, 20 Sep 2009 19:53:00 +0100 Subject: filing bugs Message-ID: So there's no way of filing a bug from launchpad now? What do you do if: Ubuntu-bug is broken and causes firefox to crash? (like the current karmic). The bug causes problems with networking? The bug causes problems with firefox? The bug causes problems with X? (no X = no firefox) The bug causes a problem with apport? -------------- next part -------------- An HTML attachment was scrubbed... URL: From caroline.ford.work at googlemail.com Sun Sep 20 19:09:43 2009 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Sun, 20 Sep 2009 20:09:43 +0100 Subject: filing bugs In-Reply-To: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: > >> > Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? > > The link is still on the Bug tab for Ubuntu in launchpad. > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which tells you to use a menu or ubuntu-bug! (this is on edge) Apport has just called gdb which is stuck using 100% of my CPU. Iff apport gets past this it then calls Firefox which breaks due to another bug in karmic with firefox 3.5. https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/425555 is a dupe but is the same bug. Can we reverse this decision to make everyone use apport, at least until it works? Caroline -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik at ubuntu.com Sun Sep 20 19:26:35 2009 From: rafik at ubuntu.com (Rafik Ouerchefani) Date: Sun, 20 Sep 2009 20:26:35 +0100 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: Hello, Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? >> >> The link is still on the Bug tab for Ubuntu in launchpad. >> > > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which > tells you to use a menu or ubuntu-bug! (this is on edge) > You can add ?no-redirect to the link => https://bugs.launchpad.net/ubuntu/+filebug?no-redirect More info about the changes : http://fridge.ubuntu.com/node/1908 -- Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From brunogirin at gmail.com Sun Sep 20 19:38:28 2009 From: brunogirin at gmail.com (Bruno Girin) Date: Sun, 20 Sep 2009 20:38:28 +0100 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> 2009/9/20 Caroline Ford : > > Can we reverse this decision to make everyone use apport, at least until it > works? > Irrespective of whether apport works or not, I think we need to keep a way to report bugs manually through Launchpad. There are hundreds of reason why you could be in a situation where you just can't use apport. For example, if you are in a corporate environment on a machine that doesn't have access to the Internet, you may want to report the bug from another machine (which may not be running Ubuntu at all). Or it may be that a bug only occurs when you are disconnected from the net. 2009/9/20 Rafik Ouerchefani : > You can add ?no-redirect to the link => > https://bugs.launchpad.net/ubuntu/+filebug?no-redirect > More info about the changes : http://fridge.ubuntu.com/node/1908 Then there should probably be a paragraph about this on https://help.ubuntu.com/community/ReportingBugs so that people who have no other option than reporting manually can do so. A feature that could mitigate this would be if apport was able to export a crash report to a file and Launchpad was able to file a bug by uploading such a crash report. This way you could save the report on the machine that shows the bug and upload it later or from a different machine. Bruno From cyan.spam at gmail.com Sun Sep 20 19:45:00 2009 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 20 Sep 2009 15:45:00 -0400 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: <4AB6863C.3000401@gmail.com> Hi Caroline (and all), The ReportingBugs page does actually have instructions (under "Filing bugs at launchpad.net" to use the no-redirect option. However, I think bugs.edge.launchpad.net is really lacking in that it has no "report a bug" link at all. If I wasn't subscribed to this mailing list I would have no idea what to do. I see in that keeping the button but redirecting to the wiki page is also an option, and I think that would be far more helpful. Not sure if this is the right venue for talking about that, though. Regards, David Caroline Ford wrote: > > > > Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? > > The link is still on the Bug tab for Ubuntu in launchpad. > > > No - it redirects to https://help.ubuntu.com/community/ReportingBugs > which tells you to use a menu or ubuntu-bug! (this is on edge) > > Apport has just called gdb which is stuck using 100% of my CPU. Iff > apport gets past this it then calls Firefox which breaks due to > another bug in karmic with firefox 3.5. > > https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/425555 is a > dupe but is the same bug. > > Can we reverse this decision to make everyone use apport, at least > until it works? > > Caroline > > From brian at ubuntu.com Mon Sep 21 04:20:04 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:20:04 -0700 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: <20090921042004.GQ6455@murraytwins.com> On Sun, Sep 20, 2009 at 08:26:35PM +0100, Rafik Ouerchefani wrote: > Hello, > > Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? > >> > >> The link is still on the Bug tab for Ubuntu in launchpad. > >> > > > > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which > > tells you to use a menu or ubuntu-bug! (this is on edge) > > > > You can add ?no-redirect to the link => > https://bugs.launchpad.net/ubuntu/+filebug?no-redirect Yes, you can do that however I'd prefer that this link not receive wide publication as bug reporters really should be using apport. -- 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 Mon Sep 21 04:26:55 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:26:55 -0700 Subject: filing bugs In-Reply-To: <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> Message-ID: <20090921042655.GR6455@murraytwins.com> On Sun, Sep 20, 2009 at 08:38:28PM +0100, Bruno Girin wrote: > 2009/9/20 Caroline Ford : > > > > Can we reverse this decision to make everyone use apport, at least until it > > works? > > > > Irrespective of whether apport works or not, I think we need to keep a > way to report bugs manually through Launchpad. There are hundreds of > reason why you could be in a situation where you just can't use > apport. For example, if you are in a corporate environment on a > machine that doesn't have access to the Internet, you may want to > report the bug from another machine (which may not be running Ubuntu > at all). Or it may be that a bug only occurs when you are disconnected > from the net. > > 2009/9/20 Rafik Ouerchefani : > > You can add ?no-redirect to the link => > > https://bugs.launchpad.net/ubuntu/+filebug?no-redirect > > More info about the changes : http://fridge.ubuntu.com/node/1908 > > Then there should probably be a paragraph about this on > https://help.ubuntu.com/community/ReportingBugs so that people who > have no other option than reporting manually can do so. There is not a paragraph on that wiki page but rather a sentence that indicates how one could use the no-redirect parameter. I purposefully did not put a direct link in there as I didn't want it spread around a lot. > A feature that could mitigate this would be if apport was able to > export a crash report to a file and Launchpad was able to file a bug > by uploading such a crash report. This way you could save the report > on the machine that shows the bug and upload it later or from a > different machine. You can save bug reports for later use by using the command apport-cli. "What would you like to do? Your options are: S: Send report (1.3 KiB) V: View report K: Keep report file for sending later or copying to somewhere else C: Cancel" I'll be adding this to the ReportingBugs page this week. -- 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 Mon Sep 21 04:32:51 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:32:51 -0700 Subject: filing bugs In-Reply-To: <4AB6863C.3000401@gmail.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> <4AB6863C.3000401@gmail.com> Message-ID: <20090921043251.GS6455@murraytwins.com> On Sun, Sep 20, 2009 at 03:45:00PM -0400, David Tombs wrote: > Hi Caroline (and all), > > The ReportingBugs page does actually have instructions (under "Filing > bugs at launchpad.net" to use the no-redirect option. > > However, I think bugs.edge.launchpad.net is really lacking in that it > has no "report a bug" link at all. If you are referring to the "report a bug" link at the top level page http://bugs.launchpad.net this was purposefully removed because there is no context, a project or distribution, for filing a bug report. When people are looking at bugs in a project or distribution the "report a bug" link does appear. We are trying to address the tremendous problem we have with bugs without a package and bugs with little to no information in them. > If I wasn't subscribed to this mailing list I would have no idea what > to do. I see in > that > keeping the button but redirecting to the wiki page is also an option, > and I think that would be far more helpful. Not sure if this is the > right venue for talking about that, though. The "report a bug" link does exist at http://bugs.launchpad.net/ubuntu/. -- 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 alsuren at gmail.com Fri Sep 25 16:07:04 2009 From: alsuren at gmail.com (David Laban) Date: Fri, 25 Sep 2009 17:07:04 +0100 Subject: Empathy/Telepathy bugs process clarification. Message-ID: <200909251707.05233.alsuren@gmail.com> A few of us at Collabora were trying to work out how bugs are supposed to get from launchpad to us. I think it's important that we get this right if empathy is going to suddenly gain thousands of extra users in karmic. I will try to outline the process as I understand it. 1) User finds a bug, and submits it to launchpad under the empathy product. Those of us in https://launchpad.net/~telepathy get notified (?) but aren't expected to do anything about it until it is triaged. 2) Someone else comes along and triages this bug, and reports it to (or finds it in) Empathy in the GNOME Bugzilla https://bugzilla.gnome.org/browse.cgi?product=empathy or a specific connection manager in the FreeDesktop Bugzilla http://bugs.freedesktop.org/describecomponents.cgi?product=Telepathy . This is when the person who can actually fix the bug takes notice. 3) They then select the "also affects project" link, as described in https://wiki.ubuntu.com/Bugs/Watches and enter the bug they just reported/found. 4) When a fix makes it into our git repo (using our review process) your system notices this, and someone from ubuntu will try to backport it if necessary. This seems fine, but I'm not very sure who that "Someone" in step 2 should be. I think that it should be Ubuntu-Bugsquad people, as that's the most efficient use of resources. When browsing around launchpad, a few things jump out at me: 1) https://wiki.ubuntu.com/Bugs/Upstream/GNOME points at https://wiki.ubuntu.com/Bugs/Upstream/GNOME/UniverseList which contains Empathy, but it also points at https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs which doesn't. Does this mean that empathy is getting ignored by your desktop team? If so, does this need to be changed? 2) https://wiki.ubuntu.com/Bugs/Upstream/Freedesktop also lists Empathy. While empathy depends on telepathy, which is a freedesktop project, Empathy is now officially a GNOME project, which uses the GNOME Bugzilla. Should there be a note in here to clarify? (Feel free to use the contents of this email as the skeleton of a wiki page if that's the best way to do this.) David From bcurtiswx at ubuntu.com Fri Sep 25 17:16:24 2009 From: bcurtiswx at ubuntu.com (Brian Curtis) Date: Fri, 25 Sep 2009 13:16:24 -0400 Subject: Empathy/Telepathy bugs process clarification. In-Reply-To: <200909251707.05233.alsuren@gmail.com> References: <200909251707.05233.alsuren@gmail.com> Message-ID: David, You have the right general idea for our triage process. I have adopted the Empathy package as a Bug Control member, and I have been trying my best to triage empathy bugs. Unfortunately since it's not a one man job, I have been slacking due to work related jobs taking priority lately. I'm not sure if there is a list of Bug Control members and which packages they have adopted. This may be of importance to show others which packages need more people. (Brian Murray: good idea?). My point would be that although we have a great triage process, there aren't enough people yet to keep up the slack when others are short on time here and there and if developers only got involved after the triaged state, we may be in trouble at times. To answer your two questions: 1) the desktop team recently has been tackling a ton of empathy bugs, so although it may not appear on wikis that canonicals desktop team recognizes empathy, I believe their efforts recently show otherwise. 2) the wikis always need fine tuning here and there and since empathy is just now becoming default in ubuntu, the part of the wikis that mention empathy are outdated. Don't hesitate to fix them, as they can be edited by anyone. (Brian Murray: This may be something that needs to be focused on as empathy finishes its transition to default) Hope this helps! ~Brian Curtis BCurtisWX (IRC Freenode/Launchpad) On Fri, Sep 25, 2009 at 12:07 PM, David Laban wrote: > A few of us at Collabora were trying to work out how bugs are supposed to get > from launchpad to us. I think it's important that we get this right if empathy > is going to suddenly gain thousands of extra users in karmic. > > > I will try to outline the process as I understand it. > > 1) User finds a bug, and submits it to launchpad under the empathy product. > Those of us in https://launchpad.net/~telepathy get notified (?) but aren't > expected to do anything about it until it is triaged. > > 2) Someone else comes along and triages this bug, and reports it to (or finds > it in) Empathy in the GNOME Bugzilla > https://bugzilla.gnome.org/browse.cgi?product=empathy  or a specific connection > manager in the FreeDesktop Bugzilla > http://bugs.freedesktop.org/describecomponents.cgi?product=Telepathy . This is > when the person who can actually fix the bug takes notice. > > 3) They then select the "also affects project" link, as described in > https://wiki.ubuntu.com/Bugs/Watches and enter the bug they just > reported/found. > > 4) When a fix makes it into our git repo (using our review process) your system > notices this, and someone from ubuntu will try to backport it if necessary. > > This seems fine, but I'm not very sure who that "Someone" in step 2 should be. > I think that it should be Ubuntu-Bugsquad people, as that's the most efficient > use of resources. > > When browsing around launchpad, a few things jump out at me: > > 1) https://wiki.ubuntu.com/Bugs/Upstream/GNOME points at > https://wiki.ubuntu.com/Bugs/Upstream/GNOME/UniverseList > which contains Empathy, but it also points at > https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs which doesn't. Does > this mean that empathy is getting ignored by your desktop team? If so, does > this need to be changed? > > 2) https://wiki.ubuntu.com/Bugs/Upstream/Freedesktop also lists Empathy. While > empathy depends on telepathy, which is a freedesktop project, Empathy is now > officially a GNOME project, which uses the GNOME Bugzilla. Should there be a > note in here to clarify? (Feel free to use the contents of this email as the > skeleton of a wiki page if that's the best way to do this.) > > David > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" ---------------------------------------------------------------- The Statement Below is True The Statement Above is False ---------------------------------------------------------------- From komputes at gmail.com Fri Sep 25 22:56:09 2009 From: komputes at gmail.com (komputes) Date: Fri, 25 Sep 2009 18:56:09 -0400 Subject: Empathy/Telepathy bugs process clarification. In-Reply-To: References: <200909251707.05233.alsuren@gmail.com> Message-ID: <4ABD4A89.30806@gmail.com> Brian Curtis wrote: > David, > > You have the right general idea for our triage process. > > I have adopted the Empathy package as a Bug Control member, and I have > been trying my best to triage empathy bugs. Unfortunately since it's > not a one man job, I have been slacking due to work related jobs > taking priority lately. > > I'm not sure if there is a list of Bug Control members and which > packages they have adopted. This may be of importance to show others > which packages need more people. (Brian Murray: good idea?). > > My point would be that although we have a great triage process, there > aren't enough people yet to keep up the slack when others are short on > time here and there and if developers only got involved after the > triaged state, we may be in trouble at times. > > To answer your two questions: > 1) the desktop team recently has been tackling a ton of empathy bugs, > so although it may not appear on wikis that canonicals desktop team > recognizes empathy, I believe their efforts recently show otherwise. > > 2) the wikis always need fine tuning here and there and since empathy > is just now becoming default in ubuntu, the part of the wikis that > mention empathy are outdated. Don't hesitate to fix them, as they can > be edited by anyone. > (Brian Murray: This may be something that needs to be focused on as > empathy finishes its transition to default) > > Hope this helps! > ~Brian Curtis > BCurtisWX (IRC Freenode/Launchpad) > > On Fri, Sep 25, 2009 at 12:07 PM, David Laban wrote: > >> A few of us at Collabora were trying to work out how bugs are supposed to get >> from launchpad to us. I think it's important that we get this right if empathy >> is going to suddenly gain thousands of extra users in karmic. >> >> >> I will try to outline the process as I understand it. >> >> 1) User finds a bug, and submits it to launchpad under the empathy product. >> Those of us in https://launchpad.net/~telepathy get notified (?) but aren't >> expected to do anything about it until it is triaged. >> >> 2) Someone else comes along and triages this bug, and reports it to (or finds >> it in) Empathy in the GNOME Bugzilla >> https://bugzilla.gnome.org/browse.cgi?product=empathy or a specific connection >> manager in the FreeDesktop Bugzilla >> http://bugs.freedesktop.org/describecomponents.cgi?product=Telepathy . This is >> when the person who can actually fix the bug takes notice. >> >> 3) They then select the "also affects project" link, as described in >> https://wiki.ubuntu.com/Bugs/Watches and enter the bug they just >> reported/found. >> >> 4) When a fix makes it into our git repo (using our review process) your system >> notices this, and someone from ubuntu will try to backport it if necessary. >> >> This seems fine, but I'm not very sure who that "Someone" in step 2 should be. >> I think that it should be Ubuntu-Bugsquad people, as that's the most efficient >> use of resources. >> >> When browsing around launchpad, a few things jump out at me: >> >> 1) https://wiki.ubuntu.com/Bugs/Upstream/GNOME points at >> https://wiki.ubuntu.com/Bugs/Upstream/GNOME/UniverseList >> which contains Empathy, but it also points at >> https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs which doesn't. Does >> this mean that empathy is getting ignored by your desktop team? If so, does >> this need to be changed? >> >> 2) https://wiki.ubuntu.com/Bugs/Upstream/Freedesktop also lists Empathy. While >> empathy depends on telepathy, which is a freedesktop project, Empathy is now >> officially a GNOME project, which uses the GNOME Bugzilla. Should there be a >> note in here to clarify? (Feel free to use the contents of this email as the >> skeleton of a wiki page if that's the best way to do this.) >> >> David >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> > > > > Hi David, First off I'd like to thank Collabora for sponsoring GStreamer and Pitivi and Telepathy as these are great projects. Secondly, you may want to join to the telepathy team on Launchpad by clicking here: https://launchpad.net/~telepathy/+join I believe you will get notifications for all new bugs, bug comments, and status changes. From there you can create filters to see the reports you are interested in. As I can see Guillaume and Sumana are currently on the team. >From what I understand there is no way yet to only be notified of bugs which have status changed to "Status==Triaged" other than being creative with email filters or using the advanced search in Launchpad. The Launchpad advanced search allows you to filter by Status, Importance and even if there is an upstream link. To break down the process of reporting a bug: Bug is submitted Someone can confirm the bug (Status==Confirmed) All information is collected to make bug useful to developers Bug is reported upstream Upstream bug is linked to Launchpad bug (if upstream has its own bug tracker) Bug Control member sets Importance and marks Status==Triaged Ball is in the developers hands. My best guess as to why telepathy is not listed on https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs is that telepathy is not shipped in the current release of ubuntu (i.e. part of ubuntu). All the packages listed on this page come with ubuntu's current release (Jaunty). I think this list will change to include telepathy, and telepathy will be removed from this list ( https://wiki.ubuntu.com/Bugs/Upstream/GNOME/UniverseList ) when karmic is released. I have modified https://wiki.ubuntu.com/Bugs/Upstream/Freedesktop as you requested to show that Telepathy is a Freedesktop project, not to be confused with Empathy which requires Telepathy but is a GNOME project. Keep on rockin' in the free world, -komputes From leann.ogasawara at canonical.com Mon Sep 28 03:00:14 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Sun, 27 Sep 2009 23:00:14 -0400 Subject: Kernel Bug Day - Tues 29 Sept, 2009 Message-ID: <1254106814.3738.23.camel@emiko> Hi Everyone, Just another friendly reminder that the next kernel bug day will be held Tues. the 29th of Sept, 2009 [1]. As we approach Karmic's final release, we want to ensure any release critical bugs will not go unnoticed. As a result we will be focusing on newly reported kernel bugs. Each kernel team member is responsible for a specific subset of bugs however community involvement is also greatly appreciated. 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/20090929 From hawat.thufir at gmail.com Sat Sep 26 17:08:44 2009 From: hawat.thufir at gmail.com (Thufir) Date: Sat, 26 Sep 2009 17:08:44 +0000 (UTC) Subject: filing bugs References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> <20090921042655.GR6455@murraytwins.com> Message-ID: On Sun, 20 Sep 2009 21:26:55 -0700, Brian Murray wrote: > There is not a paragraph on that wiki page but rather a sentence that > indicates how one could use the no-redirect parameter. I purposefully > did not put a direct link in there as I didn't want it spread around a > lot. Perhaps this should be filed as a bug? ;) -Thufir From m.fletcher at theplanet.ca Wed Sep 30 14:17:30 2009 From: m.fletcher at theplanet.ca (Michael Fletcher) Date: Wed, 30 Sep 2009 08:17:30 -0600 Subject: When A Bug Is Not Fixed Message-ID: Hi. I have reported a bug (434769), it was confirmed, assigned and is now in Fix Released status. I tested and the problem still exists. How should I proceed now? Set the status back to confirmed with a comment? I searched through wiki.ubuntu.com and I couldn't find any mention of what you are supposed to do. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From macoafi at gmail.com Wed Sep 30 14:53:14 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 30 Sep 2009 10:53:14 -0400 Subject: When A Bug Is Not Fixed In-Reply-To: References: Message-ID: <200909301053.14609.macoafi@gmail.com> On Wednesday 30 September 2009 10:17:30 am Michael Fletcher wrote: > Hi. > > I have reported a bug (434769), it was confirmed, assigned and is now in > Fix Released status. I tested and the problem still exists. > > How should I proceed now? Set the status back to confirmed with a comment? > I searched through wiki.ubuntu.com and I couldn't find any mention of what > you are supposed to do. Was a comment left on the bug saying what version it's fixed in? Usually bugs are fixed in current development version, so test with Karmic before writing it off as not fixed. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo From hggdh2 at ubuntu.com Wed Sep 30 15:33:43 2009 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 30 Sep 2009 10:33:43 -0500 Subject: When A Bug Is Not Fixed In-Reply-To: <200909301053.14609.macoafi@gmail.com> References: <200909301053.14609.macoafi@gmail.com> Message-ID: <20090930103343.6ab6fc30@xango2> On Wed, 30 Sep 2009 10:53:14 -0400 Mackenzie Morgan wrote: > On Wednesday 30 September 2009 10:17:30 am Michael Fletcher wrote: > > Hi. > > > > I have reported a bug (434769), it was confirmed, assigned and is > > now in Fix Released status. I tested and the problem still exists. > > > > How should I proceed now? Set the status back to confirmed with a > > comment? I searched through wiki.ubuntu.com and I couldn't find any > > mention of what you are supposed to do. > > Was a comment left on the bug saying what version it's fixed in? > Usually bugs are fixed in current development version, so test with > Karmic before writing it off as not fixed. > The bug (https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/434769) states you were testing the daily ISO. It does not necessarily follow that the daily ISO will have casper 1.195. Have you checked it? Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From ara at ubuntu.com Wed Sep 30 15:44:46 2009 From: ara at ubuntu.com (Ara Pulido) Date: Wed, 30 Sep 2009 17:44:46 +0200 Subject: When A Bug Is Not Fixed In-Reply-To: <20090930103343.6ab6fc30@xango2> References: <200909301053.14609.macoafi@gmail.com> <20090930103343.6ab6fc30@xango2> Message-ID: <4AC37CEE.4040908@ubuntu.com> On 30/09/09 17:33, C de-Avillez wrote: > It does not necessarily follow that the daily ISO will have casper > 1.195. > Well, candidate version is 1.196 and that package is up to date in the ISOs (http://qa.ubuntu.com/reports/ogasawara/weatherreport/iso_pkg_diffs/ubuntu-i386-desktop.html) So I think that we can conclude that casper 1.196 is in the daily ISOs. Regards, Ara. From hggdh2 at ubuntu.com Wed Sep 30 15:58:18 2009 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 30 Sep 2009 10:58:18 -0500 Subject: When A Bug Is Not Fixed In-Reply-To: <4AC37CEE.4040908@ubuntu.com> References: <200909301053.14609.macoafi@gmail.com> <20090930103343.6ab6fc30@xango2> <4AC37CEE.4040908@ubuntu.com> Message-ID: <20090930105818.58148f4c@xango2> On Wed, 30 Sep 2009 17:44:46 +0200 Ara Pulido wrote: > On 30/09/09 17:33, C de-Avillez wrote: > > It does not necessarily follow that the daily ISO will have casper > > 1.195. > > > Well, candidate version is 1.196 and that package is up to date in > the ISOs > (http://qa.ubuntu.com/reports/ogasawara/weatherreport/iso_pkg_diffs/ubuntu-i386-desktop.html) > > So I think that we can conclude that casper 1.196 is in the daily > ISOs. In this case -- to Michael: if you tested the current daily, and you still have the issue, please reopen the bug, and provide your findings there. Cheers, -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From m.fletcher at theplanet.ca Wed Sep 30 16:12:36 2009 From: m.fletcher at theplanet.ca (Michael Fletcher) Date: Wed, 30 Sep 2009 10:12:36 -0600 Subject: When A Bug Is Not Fixed In-Reply-To: <20090930103343.6ab6fc30@xango2> References: <200909301053.14609.macoafi@gmail.com> <20090930103343.6ab6fc30@xango2> Message-ID: On Wed, Sep 30, 2009 at 9:33 AM, C de-Avillez wrote: > The bug > (https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/434769) states > you were testing the daily ISO. > > It does not necessarily follow that the daily ISO will have casper > 1.195. > > Have you checked it? > No. I assumed the ISO would contain the latest package for Karmic if the package was uploaded before the daily was generated. What does the daily ISO contain? Anyways I spoke with cjwatson and he said the problem is being tracked under another bug and it won't be fixed until after the beta is out. He gave me a workaround to boot the machine into a console. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kamusin at gmail.com Tue Sep 1 21:25:14 2009 From: kamusin at gmail.com (Kamus) Date: Tue, 01 Sep 2009 21:25:14 -0000 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 03 September 2009 Message-ID: Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* Network Manager! * 200 New bugs need a hug. * 100 Incomplete bugs need a status check. * 80 Confirmed bugs need a review. * 12 Bugs that need to be send upstream. Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 03 of September 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090903 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) 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! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Victor Vargas(irc kamusin, aka "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 Thu Sep 3 21:26:43 2009 From: brian at ubuntu.com (Brian Murray) Date: Thu, 03 Sep 2009 21:26:43 -0000 Subject: Packages without bug subscribers Message-ID: <20090903212639.GM6386@murraytwins.com> Recently there was some discussion about packages that might have no one looking after bugs reported about them. One way to monitor bugs about a package, in Launchpad, is to subscribe to all of the package's bug mail. This can be done by going to http://launchpad.net/ubuntu/+source/acpid and clicking "Subscribe to bug mail". (Of course replacing apcid with the package you are interested in.) I went looking for these packages and have compiled a wiki page[1] with some of them. (A complete csv file is also attached to that page.) There are approximately 850 of these packages in main, and not having people subscribed to a package's bug reports may make sense in some cases. However, there are still clearly some packages that need monitoring and some bug cleanup done. The cleanup[2] can be fairly easy with the right tools too! How can you help? If there is a package that you or a team you are member of cares for - subscribe to the bug mail. Some teams, like ubuntu-x and desktop-bugs, have mailing lists specifically setup for their bug mail. Alternatively, review and triage a package's existing bug reports. [1] https://wiki.ubuntu.com/QATeam/MainPackagesWithoutBugSubscribers [2] http://www.murraytwins.com/blog/?p=45 -- 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 Mon Sep 14 17:52:08 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 14 Sep 2009 17:52:08 -0000 Subject: Dead links In-Reply-To: References: Message-ID: <20090914175205.GG5102@murraytwins.com> On Mon, Sep 14, 2009 at 09:38:18AM +0200, Søren Bredlund Caspersen wrote: > Hi all! > > While reading up on bug triaging I have stumbled upon some dead links > on the wiki pages. Thanks for bringing this up I've fixed the ones you've pointed out and am including the active links in case anyone is interested. > The following links look dead: > http://people.canonical.com/~brian/reports/gt5subscribers/no-package.html http://qa.ubuntu.com/reports/package/gt5subscribers/no-package.html > http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html > http://people.canonical.com/~brian/reports/database/unlinked-bugwatch.html http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html -- 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 Mon Sep 14 19:36:46 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 14 Sep 2009 19:36:46 -0000 Subject: Network and wifi bugs In-Reply-To: References: Message-ID: <20090914193642.GH5102@murraytwins.com> On Sun, Sep 13, 2009 at 04:49:21PM +0200, Søren Bredlund Caspersen wrote: > Hi everyone > > I'm trying to triage a few bugs (from the EasyTasks list) using the > info at this wiki page: > https://wiki.ubuntu.com/Bugs/FindRightPackage > > However I can't seem to find any info of what packages to assign bugs > that are about network connections or wifi. > One example could be: > https://bugs.launchpad.net/ubuntu/+bug/428276 Your specific example is hardware related as the device was not being detected my network manager (indicated by the reporter) and there was not a driver for it (see lspci -vvnn output). In that case the correct package is linux. You might also be interested in http://wiki.ubuntu.com/DebuggingNetworkManager. -- 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 Tue Sep 15 17:53:23 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 15 Sep 2009 17:53:23 -0000 Subject: Launchpad Bug Filing Changes for Ubuntu Message-ID: <20090915175319.GA6455@murraytwins.com> 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. In order to make the transition for our users smoother, we'd like to ask you to help out with a few things: 1) If you take care of a high-profile package, consider adding it to https://wiki.ubuntu.com/Bugs/FindRightPackage which is linked to from https://help.ubuntu.com/community/ReportingBugs. 2) Please consider writing an apport hook for the packages you take care of, if you need special information in bug reports - it's REALLY easy: https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks 3) If the area of Ubuntu that you take care of is better suited by symptom based bug reporting ("storage", "boot", "install", "sound", etc.), consider contributing to the apport-symptoms package - it too is REALLY easy: https://wiki.ubuntu.com/Apport/DeveloperHowTo#Symptoms By helping us receive higher quality bug reports, we will help to help make Ubuntu even better! [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption (*) There will be a +filebug?no-redirect if you really really need it. -- Brian Murray On behalf of the Ubuntu QA Team -------------- 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 Tue Sep 15 23:37:19 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 15 Sep 2009 23:37:19 -0000 Subject: Launchpad Bug Filing Changes for Ubuntu In-Reply-To: <714626160909151213u6767d083tee27e69b78e3f22b@mail.gmail.com> References: <20090915175319.GA6455@murraytwins.com> <714626160909151213u6767d083tee27e69b78e3f22b@mail.gmail.com> Message-ID: <20090915233715.GC6455@murraytwins.com> On Tue, Sep 15, 2009 at 03:13:28PM -0400, Yuriy Kozlov wrote: > On Tue, Sep 15, 2009 at 1:53 PM, 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. > > > > In order to make the transition for our users smoother, we'd like to ask > > you to help out with a few things: > > > > 1) If you take care of a high-profile package, consider adding it to > > https://wiki.ubuntu.com/Bugs/FindRightPackage which is linked to from > > https://help.ubuntu.com/community/ReportingBugs. > > > > 2) Please consider writing an apport hook for the packages you take care > > of, if you need special information in bug reports - it's REALLY easy: > > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks > > > > 3) If the area of Ubuntu that you take care of is better suited by > > symptom based bug reporting ("storage", "boot", "install", "sound", > > etc.), consider contributing to the apport-symptoms package - it too is > > REALLY easy: > > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Symptoms > > > > By helping us receive higher quality bug reports, we will help to help > > make Ubuntu even better! > > > > [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption > > (*) There will be a +filebug?no-redirect if you really really need it. > > > > -- > > Brian Murray > > On behalf of the Ubuntu QA Team > > Hi Brian, > > Would it be possible to direct to a different page for some packages? No, the way the Launchpad code is written the redirect is done for every package related to the Ubuntu distribution - not on a per package basis. > In particular, I would like to see Kubuntu screenshots on the page for > the relevant packages. There is currently such a page here: > https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting but it needs some > updating. Kubuntu Karmic enables apport-bug for everything, so the > normal ReportingBugs page is accurate except for the screenshots and > the system monitor instructions. I hadn't see that wiki page before it looks very nice! Perhaps close to the very top of the ReportingBugs wiki page we should have a link for Kubuntu users to the page you indicated? -- 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 Wed Sep 16 22:33:04 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 16 Sep 2009 15:33:04 -0700 Subject: Ubuntu Bug Day - 20090917 Message-ID: <20090916223304.GE6455@murraytwins.com> I've just finished setting up the next Bug Day wiki page[1] dealing with bugs with out a package. Since there are quite a few of these, approximately 2300, and they are all in the new state I thought it'd be interesting to populate the target list with some unique criteria. So there are categories for bugs with attachments, which may be a good hint as to the package, and ones with certain numbers of subscribers, comments and duplicates. Hopefully, we can drive the number of bugs without a package down and the +filebug changes will prevent more of them from being reported. [1] https://wiki.ubuntu.com/UbuntuBugDay/20090917 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 brian at ubuntu.com Fri Sep 18 16:23:21 2009 From: brian at ubuntu.com (Brian Murray) Date: Fri, 18 Sep 2009 09:23:21 -0700 Subject: FindRightPackage improvements In-Reply-To: <4AB2773C.9080409@gmail.com> References: <4AB2773C.9080409@gmail.com> Message-ID: <20090918162321.GO6455@murraytwins.com> 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. -- 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 caroline.ford.work at googlemail.com Sun Sep 20 18:53:00 2009 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Sun, 20 Sep 2009 19:53:00 +0100 Subject: filing bugs Message-ID: So there's no way of filing a bug from launchpad now? What do you do if: Ubuntu-bug is broken and causes firefox to crash? (like the current karmic). The bug causes problems with networking? The bug causes problems with firefox? The bug causes problems with X? (no X = no firefox) The bug causes a problem with apport? -------------- next part -------------- An HTML attachment was scrubbed... URL: From caroline.ford.work at googlemail.com Sun Sep 20 19:09:43 2009 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Sun, 20 Sep 2009 20:09:43 +0100 Subject: filing bugs In-Reply-To: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: > >> > Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? > > The link is still on the Bug tab for Ubuntu in launchpad. > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which tells you to use a menu or ubuntu-bug! (this is on edge) Apport has just called gdb which is stuck using 100% of my CPU. Iff apport gets past this it then calls Firefox which breaks due to another bug in karmic with firefox 3.5. https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/425555 is a dupe but is the same bug. Can we reverse this decision to make everyone use apport, at least until it works? Caroline -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik at ubuntu.com Sun Sep 20 19:26:35 2009 From: rafik at ubuntu.com (Rafik Ouerchefani) Date: Sun, 20 Sep 2009 20:26:35 +0100 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: Hello, Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? >> >> The link is still on the Bug tab for Ubuntu in launchpad. >> > > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which > tells you to use a menu or ubuntu-bug! (this is on edge) > You can add ?no-redirect to the link => https://bugs.launchpad.net/ubuntu/+filebug?no-redirect More info about the changes : http://fridge.ubuntu.com/node/1908 -- Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Mon Sep 21 04:20:04 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:20:04 -0700 Subject: filing bugs In-Reply-To: References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> Message-ID: <20090921042004.GQ6455@murraytwins.com> On Sun, Sep 20, 2009 at 08:26:35PM +0100, Rafik Ouerchefani wrote: > Hello, > > Does https://bugs.launchpad.net/ubuntu/+filebug not work anymore? > >> > >> The link is still on the Bug tab for Ubuntu in launchpad. > >> > > > > No - it redirects to https://help.ubuntu.com/community/ReportingBugs which > > tells you to use a menu or ubuntu-bug! (this is on edge) > > > > You can add ?no-redirect to the link => > https://bugs.launchpad.net/ubuntu/+filebug?no-redirect Yes, you can do that however I'd prefer that this link not receive wide publication as bug reporters really should be using apport. -- 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 Mon Sep 21 04:26:55 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:26:55 -0700 Subject: filing bugs In-Reply-To: <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> <6cad31400909201238k5f69814fs983ffb269eea8ed6@mail.gmail.com> Message-ID: <20090921042655.GR6455@murraytwins.com> On Sun, Sep 20, 2009 at 08:38:28PM +0100, Bruno Girin wrote: > 2009/9/20 Caroline Ford : > > > > Can we reverse this decision to make everyone use apport, at least until it > > works? > > > > Irrespective of whether apport works or not, I think we need to keep a > way to report bugs manually through Launchpad. There are hundreds of > reason why you could be in a situation where you just can't use > apport. For example, if you are in a corporate environment on a > machine that doesn't have access to the Internet, you may want to > report the bug from another machine (which may not be running Ubuntu > at all). Or it may be that a bug only occurs when you are disconnected > from the net. > > 2009/9/20 Rafik Ouerchefani : > > You can add ?no-redirect to the link => > > https://bugs.launchpad.net/ubuntu/+filebug?no-redirect > > More info about the changes : http://fridge.ubuntu.com/node/1908 > > Then there should probably be a paragraph about this on > https://help.ubuntu.com/community/ReportingBugs so that people who > have no other option than reporting manually can do so. There is not a paragraph on that wiki page but rather a sentence that indicates how one could use the no-redirect parameter. I purposefully did not put a direct link in there as I didn't want it spread around a lot. > A feature that could mitigate this would be if apport was able to > export a crash report to a file and Launchpad was able to file a bug > by uploading such a crash report. This way you could save the report > on the machine that shows the bug and upload it later or from a > different machine. You can save bug reports for later use by using the command apport-cli. "What would you like to do? Your options are: S: Send report (1.3 KiB) V: View report K: Keep report file for sending later or copying to somewhere else C: Cancel" I'll be adding this to the ReportingBugs page this week. -- 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 Mon Sep 21 04:32:51 2009 From: brian at ubuntu.com (Brian Murray) Date: Sun, 20 Sep 2009 21:32:51 -0700 Subject: filing bugs In-Reply-To: <4AB6863C.3000401@gmail.com> References: <7701BC48-24B1-41FD-B220-2CCDC4B6B4CB@me.com> <4AB6863C.3000401@gmail.com> Message-ID: <20090921043251.GS6455@murraytwins.com> On Sun, Sep 20, 2009 at 03:45:00PM -0400, David Tombs wrote: > Hi Caroline (and all), > > The ReportingBugs page does actually have instructions (under "Filing > bugs at launchpad.net" to use the no-redirect option. > > However, I think bugs.edge.launchpad.net is really lacking in that it > has no "report a bug" link at all. If you are referring to the "report a bug" link at the top level page http://bugs.launchpad.net this was purposefully removed because there is no context, a project or distribution, for filing a bug report. When people are looking at bugs in a project or distribution the "report a bug" link does appear. We are trying to address the tremendous problem we have with bugs without a package and bugs with little to no information in them. > If I wasn't subscribed to this mailing list I would have no idea what > to do. I see in > that > keeping the button but redirecting to the wiki page is also an option, > and I think that would be far more helpful. Not sure if this is the > right venue for talking about that, though. The "report a bug" link does exist at http://bugs.launchpad.net/ubuntu/. -- 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 lars at canonical.com Wed Sep 30 14:25:21 2009 From: lars at canonical.com (Lars Wirzenius) Date: Wed, 30 Sep 2009 17:25:21 +0300 Subject: When A Bug Is Not Fixed In-Reply-To: References: Message-ID: <1254320721.4139.81.camel@havelock> ke, 2009-09-30 kello 08:17 -0600, Michael Fletcher kirjoitti: > Hi. > > I have reported a bug (434769), it was confirmed, assigned and is now > in Fix Released status. I tested and the problem still exists. > > How should I proceed now? Set the status back to confirmed with a > comment? I searched through wiki.ubuntu.com and I couldn't find any > mention of what you are supposed to do. > Are you testing the version that has the fix? There is time window between a bug being set as "Fix Released" and until the fixed package is widely available on all mirrors. From Simeon_A_Layne_Jr at sbcglobal.net Tue Sep 29 13:29:43 2009 From: Simeon_A_Layne_Jr at sbcglobal.net (Simeon A Layne Jr) Date: Tue, 29 Sep 2009 08:29:43 -0500 Subject: karmic 9.10 Alpha 6 - grub issue Message-ID: <1254230983.3093.23.camel@8thdaydev-LINUX> I have been testing the alpha code for 2 weeks and this issue is one that i haven;t seen mentioned or maybe i didn't perform the proper search. Here is the problem, at boot time from the laptop i have the software installed on, i get this message: Invalid environment block Grub will not boot the karmic install, but it will boot my Vista partition. I currently do the following to use the system but this is getting old, I boot from a Jaunty 9.04 usb drive where i had already modified the boot menu to include the laptop's karmic OS partition. The karmic partition is obviously functional but the grub 2.0? is not pleased with something in the environment? Attempts to fix this have not resulted in success. I have run the following: 1st try... sudo -s update-grub reboot Nope 2nd try... Reinstalled all grub components from synapetic... sudo -s update-grub reboot Nope 3rd try sudo -s grub-install /dev/sda update-grub update-initramfs -k all -u reboot No luck on resolving this issue. Ant suggestions? System info: fomr uname -a Linux 8thdaydev-LINUX 2.6.31-11-generic #36-Ubuntu SMP Fri Sep 25 06:37:23 UTC 2009 x86_64 GNU/Linux I usually update the system at least twice a day as updates are fast and furious. I really love the look and feel of karmic and the performance is sweet, but i do understand alpha as I write code for other stuff at some other place. I really don't know the best way to report this to the karmic team, i figured you could advise. Included is the dmesg log if that might help... -------------- next part -------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.31-11-generic (buildd at yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu3) ) #36-Ubuntu SMP Fri Sep 25 06:37:23 UTC 2009 (Ubuntu 2.6.31-11.36-generic) [ 0.000000] Command line: root=UUID=70b72463-0c65-4f0e-b715-8f74aa174b9e ro quiet splash [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 00000000afed0000 (usable) [ 0.000000] BIOS-e820: 00000000afed0000 - 00000000afee5000 (ACPI data) [ 0.000000] BIOS-e820: 00000000afee5000 - 00000000afee6000 (ACPI NVS) [ 0.000000] BIOS-e820: 00000000afee6000 - 00000000c0000000 (reserved) [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) [ 0.000000] DMI present. [ 0.000000] last_pfn = 0xafed0 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: uncachable [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-BFFFF uncachable [ 0.000000] C0000-CFFFF write-protect [ 0.000000] D0000-DBFFF uncachable [ 0.000000] DC000-DFFFF write-protect [ 0.000000] E0000-E3FFF uncachable [ 0.000000] E4000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 0000000000 mask FF80000000 write-back [ 0.000000] 1 base 0080000000 mask FFE0000000 write-back [ 0.000000] 2 base 00A0000000 mask FFF0000000 write-back [ 0.000000] 3 disabled [ 0.000000] 4 disabled [ 0.000000] 5 disabled [ 0.000000] 6 disabled [ 0.000000] 7 disabled [ 0.000000] e820 update range: 0000000000001000 - 0000000000006000 (usable) ==> (reserved) [ 0.000000] Scanning 1 areas for low memory corruption [ 0.000000] modified physical RAM map: [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable) [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved) [ 0.000000] modified: 0000000000006000 - 000000000009e000 (usable) [ 0.000000] modified: 000000000009e000 - 00000000000a0000 (reserved) [ 0.000000] modified: 00000000000d0000 - 0000000000100000 (reserved) [ 0.000000] modified: 0000000000100000 - 00000000afed0000 (usable) [ 0.000000] modified: 00000000afed0000 - 00000000afee5000 (ACPI data) [ 0.000000] modified: 00000000afee5000 - 00000000afee6000 (ACPI NVS) [ 0.000000] modified: 00000000afee6000 - 00000000c0000000 (reserved) [ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] modified: 00000000fec00000 - 00000000fec10000 (reserved) [ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] modified: 00000000fff80000 - 0000000100000000 (reserved) [ 0.000000] initial memory mapped : 0 - 20000000 [ 0.000000] init_memory_mapping: 0000000000000000-00000000afed0000 [ 0.000000] Using x86 segment limits to approximate NX protection [ 0.000000] 0000000000 - 00afe00000 page 2M [ 0.000000] 00afe00000 - 00afed0000 page 4k [ 0.000000] kernel direct mapping tables up to afed0000 @ 8000-d000 [ 0.000000] RAMDISK: 37926000 - 37fef7bf [ 0.000000] ACPI: RSDP 00000000000f7f30 00024 (v03 HPQOEM) [ 0.000000] ACPI: XSDT 00000000afedde73 0005C (v01 HPQOEM SLIC-MPC 06040000 LTP 00000000) [ 0.000000] ACPI: FACP 00000000afee49d3 000F4 (v03 HPQOEM SLIC-MPC 06040000 PTL_ 000F4240) [ 0.000000] ACPI: DSDT 00000000afeddecf 06A90 (v01 HPQOEM SLIC-MPC 06040000 MSFT 03000000) [ 0.000000] ACPI: FACS 00000000afee5fc0 00040 [ 0.000000] ACPI: SLIC 00000000afee4ac7 00176 (v01 HPQOEM SLIC-MPC 06040000 HPQ 00000001) [ 0.000000] ACPI: MCFG 00000000afee4c3d 0003C (v01 HPQOEM SLIC-MPC 06040000 LTP 00000000) [ 0.000000] ACPI: HPET 00000000afee4c79 00038 (v01 HPQOEM SLIC-MPC 06040000 LTP 00000001) [ 0.000000] ACPI: APIC 00000000afee4cb1 00072 (v01 HPQOEM SLIC-MPC 06040000 LTP 00000000) [ 0.000000] ACPI: BOOT 00000000afee4d23 00028 (v01 HPQOEM SLIC-MPC 06040000 LTP 00000001) [ 0.000000] ACPI: SSDT 00000000afee4d4b 002B5 (v01 HPQOEM SLIC-MP 06040000 00000150) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] Scanning NUMA topology in Northbridge 24 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-00000000afed0000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000000afed0000 [ 0.000000] NODE_DATA [000000000000b000 - 000000000000ffff] [ 0.000000] bootmap [0000000000010000 - 0000000000025fdf] pages 16 [ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 00afed0000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #2 [0001000000 - 00019b9bcc] TEXT DATA BSS ==> [0001000000 - 00019b9bcc] [ 0.000000] #3 [0037926000 - 0037fef7bf] RAMDISK ==> [0037926000 - 0037fef7bf] [ 0.000000] #4 [000009e000 - 0000100000] BIOS reserved ==> [000009e000 - 0000100000] [ 0.000000] #5 [00019ba000 - 00019ba18c] BRK ==> [00019ba000 - 00019ba18c] [ 0.000000] #6 [0000008000 - 000000b000] PGTABLE ==> [0000008000 - 000000b000] [ 0.000000] found SMP MP-table at [ffff8800000f7ff0] f7ff0 [ 0.000000] [ffffea0000000000-ffffea00027fffff] PMD -> [ffff880001e00000-ffff8800045fffff] on node 0 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x00000001 [ 0.000000] 0: 0x00000006 -> 0x0000009e [ 0.000000] 0: 0x00000100 -> 0x000afed0 [ 0.000000] On node 0 totalpages: 720489 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 104 pages reserved [ 0.000000] DMA zone: 3833 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 9796 pages used for memmap [ 0.000000] DMA32 zone: 706700 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x1008 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x10de8201 base: 0xfed00000 [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 24 [ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000 [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 00000000000a0000 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000d0000 [ 0.000000] PM: Registered nosave memory: 00000000000d0000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:20000000) [ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 29 pages at ffff8800019d7000, static data 89952 bytes [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 710533 [ 0.000000] Policy zone: DMA32 [ 0.000000] Kernel command line: root=UUID=70b72463-0c65-4f0e-b715-8f74aa174b9e ro quiet splash [ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 0.000000] Initializing CPU#0 [ 0.000000] Checking aperture... [ 0.000000] No AGP bridge found [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.000000] Memory: 2823628k/2882368k available (5290k kernel code, 412k absent, 58328k reserved, 2997k data, 660k init) [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] NR_IRQS:4352 nr_irqs:424 [ 0.000000] Extended CMOS year: 2000 [ 0.000000] Fast TSC calibration using PIT [ 0.000000] Detected 1900.008 MHz processor. [ 0.000025] spurious 8259A interrupt: IRQ7. [ 0.002804] Console: colour VGA+ 80x25 [ 0.002807] console [tty0] enabled [ 0.004000] allocated 28835840 bytes of page_cgroup [ 0.004000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.004000] hpet clockevent registered [ 0.004000] HPET: 3 timers in total, 0 timers will be used for per-cpu timer [ 0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 3800.01 BogoMIPS (lpj=7600020) [ 0.004000] Security Framework initialized [ 0.004000] AppArmor: AppArmor initialized [ 0.004000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.004000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.004498] Mount-cache hash table entries: 256 [ 0.004677] Initializing cgroup subsys ns [ 0.004682] Initializing cgroup subsys cpuacct [ 0.004686] Initializing cgroup subsys memory [ 0.004695] Initializing cgroup subsys freezer [ 0.004698] Initializing cgroup subsys net_cls [ 0.004714] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.004716] CPU: L2 Cache: 512K (64 bytes/line) [ 0.004720] CPU 0/0x0 -> Node 0 [ 0.004723] tseg: 00aff00000 [ 0.004725] CPU: Physical Processor ID: 0 [ 0.004727] CPU: Processor Core ID: 0 [ 0.004730] using C1E aware idle routine [ 0.004733] Performance Counters: AMD PMU driver. [ 0.004738] ... version: 0 [ 0.004740] ... bit width: 48 [ 0.004742] ... generic counters: 4 [ 0.004744] ... value mask: 0000ffffffffffff [ 0.004746] ... max period: 00007fffffffffff [ 0.004748] ... fixed-purpose counters: 0 [ 0.004750] ... counter mask: 000000000000000f [ 0.007192] ACPI: Core revision 20090521 [ 0.016080] Setting APIC routing to flat [ 0.016515] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0 [ 0.059631] CPU0: AMD Athlon Dual-Core QL-60 stepping 01 [ 0.060001] Booting processor 1 APIC 0x1 ip 0x6000 [ 0.004000] Initializing CPU#1 [ 0.004000] Calibrating delay using timer specific routine.. 3800.10 BogoMIPS (lpj=7600214) [ 0.004000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.004000] CPU: L2 Cache: 512K (64 bytes/line) [ 0.004000] CPU 1/0x1 -> Node 0 [ 0.004000] CPU: Physical Processor ID: 0 [ 0.004000] CPU: Processor Core ID: 1 [ 0.144227] CPU1: AMD Athlon Dual-Core QL-60 stepping 01 [ 0.144240] checking TSC synchronization [CPU#0 -> CPU#1]: [ 0.148001] Measured 1066312971 cycles TSC warp between CPUs, turning off TSC clock. [ 0.148001] Marking TSC unstable due to check_tsc_sync_source failed [ 0.148016] Brought up 2 CPUs [ 0.148018] Total of 2 processors activated (7600.11 BogoMIPS). [ 0.148122] CPU0 attaching sched-domain: [ 0.148126] domain 0: span 0-1 level MC [ 0.148129] groups: 0 1 [ 0.148135] CPU1 attaching sched-domain: [ 0.148138] domain 0: span 0-1 level MC [ 0.148140] groups: 1 0 [ 0.148220] Booting paravirtualized kernel on bare hardware [ 0.148220] regulator: core version 0.5 [ 0.148220] Time: 7:15:31 Date: 09/29/09 [ 0.148220] NET: Registered protocol family 16 [ 0.148303] TOM: 00000000c0000000 aka 3072M [ 0.148306] Fam 10h mmconf [e0000000, efffffff] [ 0.148323] ACPI: bus type pci registered [ 0.148408] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 7 [ 0.148412] PCI: MCFG area at e0000000 reserved in E820 [ 0.148538] PCI: Using MMCONFIG at e0000000 - e07fffff [ 0.148540] PCI: Using configuration type 1 for base access [ 0.149422] bio: create slab at 0 [ 0.149422] ACPI: EC: Enabling special treatment for EC from MSI. [ 0.149422] ACPI: EC: Look up EC in DSDT [ 0.154726] ACPI: BIOS _OSI(Linux) query ignored [ 0.155876] ACPI: EC: non-query interrupt received, switching to interrupt mode [ 0.181732] ACPI: Interpreter enabled [ 0.181732] ACPI: (supports S0 S3 S4 S5) [ 0.181732] ACPI: Using IOAPIC for interrupt routing [ 0.222600] ACPI: EC: GPE = 0x2a, I/O: command/status = 0x66, data = 0x62 [ 0.222603] ACPI: EC: driver started in interrupt mode [ 0.222862] ACPI: No dock devices found. [ 0.223202] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 0.223510] pci 0000:00:01.0: reg 10 io port: [0x1a00-0x1aff] [ 0.223567] pci 0000:00:01.1: reg 10 io port: [0x3080-0x30bf] [ 0.223584] pci 0000:00:01.1: reg 20 io port: [0x3040-0x307f] [ 0.223590] pci 0000:00:01.1: reg 24 io port: [0x3000-0x303f] [ 0.223616] pci 0000:00:01.1: PME# supported from D3hot D3cold [ 0.223623] pci 0000:00:01.1: PME# disabled [ 0.223659] pci 0000:00:01.3: reg 10 32bit mmio: [0xc0080000-0xc00fffff] [ 0.223819] pci 0000:00:02.0: reg 10 32bit mmio: [0xc0006000-0xc0006fff] [ 0.223854] pci 0000:00:02.0: supports D1 D2 [ 0.223857] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.223861] pci 0000:00:02.0: PME# disabled [ 0.223898] pci 0000:00:02.1: reg 10 32bit mmio: [0xc0007000-0xc00070ff] [ 0.223940] pci 0000:00:02.1: supports D1 D2 [ 0.223942] pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold [ 0.223947] pci 0000:00:02.1: PME# disabled [ 0.223985] pci 0000:00:04.0: reg 10 32bit mmio: [0xc0008000-0xc0008fff] [ 0.224031] pci 0000:00:04.0: supports D1 D2 [ 0.224033] pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.224038] pci 0000:00:04.0: PME# disabled [ 0.224072] pci 0000:00:04.1: reg 10 32bit mmio: [0xc0007400-0xc00074ff] [ 0.224114] pci 0000:00:04.1: supports D1 D2 [ 0.224116] pci 0000:00:04.1: PME# supported from D0 D1 D2 D3hot D3cold [ 0.224120] pci 0000:00:04.1: PME# disabled [ 0.224171] pci 0000:00:06.0: reg 20 io port: [0x30c0-0x30cf] [ 0.224229] pci 0000:00:07.0: reg 10 32bit mmio: [0xc0000000-0xc0003fff] [ 0.224272] pci 0000:00:07.0: PME# supported from D3hot D3cold [ 0.224276] pci 0000:00:07.0: PME# disabled [ 0.224364] pci 0000:00:09.0: reg 10 io port: [0x30f0-0x30f7] [ 0.224370] pci 0000:00:09.0: reg 14 io port: [0x30e4-0x30e7] [ 0.224376] pci 0000:00:09.0: reg 18 io port: [0x30e8-0x30ef] [ 0.224381] pci 0000:00:09.0: reg 1c io port: [0x30e0-0x30e3] [ 0.224387] pci 0000:00:09.0: reg 20 io port: [0x30d0-0x30df] [ 0.224392] pci 0000:00:09.0: reg 24 32bit mmio: [0xc0004000-0xc0005fff] [ 0.224455] pci 0000:00:0a.0: reg 10 32bit mmio: [0xc0009000-0xc0009fff] [ 0.224461] pci 0000:00:0a.0: reg 14 io port: [0x30f8-0x30ff] [ 0.224467] pci 0000:00:0a.0: reg 18 32bit mmio: [0xc0007c00-0xc0007cff] [ 0.224473] pci 0000:00:0a.0: reg 1c 32bit mmio: [0xc0007800-0xc000780f] [ 0.224504] pci 0000:00:0a.0: supports D1 D2 [ 0.224507] pci 0000:00:0a.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.224512] pci 0000:00:0a.0: PME# disabled [ 0.224565] pci 0000:00:0b.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.224569] pci 0000:00:0b.0: PME# disabled [ 0.224809] pci 0000:00:14.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.224817] pci 0000:00:14.0: PME# disabled [ 0.225061] pci 0000:00:08.0: transparent bridge [ 0.225096] pci 0000:02:00.0: reg 10 32bit mmio: [0xc1000000-0xc1ffffff] [ 0.225104] pci 0000:02:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff] [ 0.225113] pci 0000:02:00.0: reg 1c 64bit mmio: [0xc4000000-0xc5ffffff] [ 0.225119] pci 0000:02:00.0: reg 24 io port: [0x4000-0x407f] [ 0.225124] pci 0000:02:00.0: reg 30 32bit mmio: [0x000000-0x01ffff] [ 0.225172] pci 0000:00:0b.0: bridge io port: [0x4000-0x4fff] [ 0.225176] pci 0000:00:0b.0: bridge 32bit mmio: [0xc1000000-0xc1ffffff] [ 0.225181] pci 0000:00:0b.0: bridge 64bit mmio pref: [0xc4000000-0xdfffffff] [ 0.225240] pci 0000:07:00.0: reg 10 64bit mmio: [0xc2000000-0xc200ffff] [ 0.225376] pci 0000:00:14.0: bridge 32bit mmio: [0xc2000000-0xc20fffff] [ 0.225416] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 0.225536] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT] [ 0.225643] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IXVE._PRT] [ 0.246141] ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 10 11 14 15) *0, disabled. [ 0.246331] ACPI: PCI Interrupt Link [LNK2] (IRQs 5 7 10 11 14 15) *0, disabled. [ 0.246517] ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 10 11 14 15) *0, disabled. [ 0.246703] ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 10 11 14 15) *0, disabled. [ 0.246890] ACPI: PCI Interrupt Link [Z012] (IRQs 19 20 21 22 23) *10 [ 0.247075] ACPI: PCI Interrupt Link [Z013] (IRQs 19 20 21 22 23) *0, disabled. [ 0.247261] ACPI: PCI Interrupt Link [Z014] (IRQs 19 20 21 22 23) *0, disabled. [ 0.247447] ACPI: PCI Interrupt Link [Z015] (IRQs 19 20 21 22 23) *0, disabled. [ 0.247634] ACPI: PCI Interrupt Link [LSMB] (IRQs 18) *10 [ 0.247816] ACPI: PCI Interrupt Link [LUS0] (IRQs 17) *11 [ 0.248010] ACPI: PCI Interrupt Link [LUS2] (IRQs 17) *7 [ 0.248202] ACPI: PCI Interrupt Link [LMAC] (IRQs 19 20 21 22 23) *11 [ 0.248387] ACPI: PCI Interrupt Link [LAZA] (IRQs 19 20 21 22 23) *10 [ 0.248577] ACPI: PCI Interrupt Link [LGPU] (IRQs 19 20 21 22 23) *10 [ 0.248762] ACPI: PCI Interrupt Link [LPID] (IRQs 19 20 21 22 23) *0, disabled. [ 0.248948] ACPI: PCI Interrupt Link [LSI0] (IRQs 19 20 21 22 23) *11 [ 0.249133] ACPI: PCI Interrupt Link [LSI1] (IRQs 19 20 21 22 23) *0, disabled. [ 0.249323] ACPI: PCI Interrupt Link [Z010] (IRQs 16) *5 [ 0.249513] ACPI: PCI Interrupt Link [Z011] (IRQs 16) *10 [ 0.249696] ACPI: PCI Interrupt Link [LPMU] (IRQs 18) *11 [ 0.249903] SCSI subsystem initialized [ 0.250211] libata version 3.00 loaded. [ 0.250211] usbcore: registered new interface driver usbfs [ 0.250211] usbcore: registered new interface driver hub [ 0.250211] usbcore: registered new device driver usb [ 0.250211] ACPI: WMI: Mapper loaded [ 0.250211] PCI: Using ACPI for IRQ routing [ 0.264009] Bluetooth: Core ver 2.15 [ 0.264736] NET: Registered protocol family 31 [ 0.264736] Bluetooth: HCI device and connection manager initialized [ 0.264736] Bluetooth: HCI socket layer initialized [ 0.264736] NetLabel: Initializing [ 0.264736] NetLabel: domain hash size = 128 [ 0.264736] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.264736] NetLabel: unlabeled traffic allowed by default [ 0.264736] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31 [ 0.264736] hpet0: 3 comparators, 32-bit 25.000000 MHz counter [ 0.276017] Switched to high resolution mode on CPU 0 [ 0.276029] Switched to high resolution mode on CPU 1 [ 0.285099] pnp: PnP ACPI init [ 0.285127] ACPI: bus type pnp registered [ 0.296261] pnp: PnP ACPI: found 12 devices [ 0.296264] ACPI: ACPI bus type pnp unregistered [ 0.296278] system 00:02: iomem range 0xe0000000-0xefffffff has been reserved [ 0.296286] system 00:03: ioport range 0x360-0x361 has been reserved [ 0.296290] system 00:03: ioport range 0x4d0-0x4d1 has been reserved [ 0.296293] system 00:03: iomem range 0xff800000-0xff800fff has been reserved [ 0.296301] system 00:0a: ioport range 0x1000-0x107f has been reserved [ 0.296304] system 00:0a: ioport range 0x1080-0x10ff has been reserved [ 0.296308] system 00:0a: ioport range 0x1200-0x127f has been reserved [ 0.296312] system 00:0a: ioport range 0x1280-0x12ff has been reserved [ 0.296315] system 00:0a: ioport range 0x1400-0x147f has been reserved [ 0.296319] system 00:0a: ioport range 0x1480-0x14ff has been reserved [ 0.296325] system 00:0b: iomem range 0xffc00000-0xffffffff could not be reserved [ 0.296329] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved [ 0.296333] system 00:0b: iomem range 0xfee00000-0xfeefffff could not be reserved [ 0.296336] system 00:0b: iomem range 0xfed00000-0xfed00fff has been reserved [ 0.296340] system 00:0b: iomem range 0xfef00000-0xfef00fff has been reserved [ 0.301030] AppArmor: AppArmor Filesystem Enabled [ 0.301086] pci 0000:00:08.0: PCI bridge, secondary bus 0000:01 [ 0.301089] pci 0000:00:08.0: IO window: disabled [ 0.301094] pci 0000:00:08.0: MEM window: disabled [ 0.301098] pci 0000:00:08.0: PREFETCH window: disabled [ 0.301106] pci 0000:00:0b.0: PCI bridge, secondary bus 0000:02 [ 0.301109] pci 0000:00:0b.0: IO window: 0x4000-0x4fff [ 0.301114] pci 0000:00:0b.0: MEM window: 0xc1000000-0xc1ffffff [ 0.301119] pci 0000:00:0b.0: PREFETCH window: 0x000000c4000000-0x000000dfffffff [ 0.301362] pci 0000:00:14.0: PCI bridge, secondary bus 0000:07 [ 0.301365] pci 0000:00:14.0: IO window: disabled [ 0.301377] pci 0000:00:14.0: MEM window: 0xc2000000-0xc20fffff [ 0.301385] pci 0000:00:14.0: PREFETCH window: disabled [ 0.301401] pci 0000:00:08.0: setting latency timer to 64 [ 0.301409] pci 0000:00:0b.0: setting latency timer to 64 [ 0.301725] ACPI: PCI Interrupt Link [Z012] enabled at IRQ 23 [ 0.301730] alloc irq_desc for 23 on node -1 [ 0.301733] alloc kstat_irqs on node -1 [ 0.301743] pci 0000:00:14.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23 [ 0.301752] pci 0000:00:14.0: setting latency timer to 64 [ 0.301760] pci_bus 0000:00: resource 0 io: [0x00-0xffff] [ 0.301764] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] [ 0.301767] pci_bus 0000:01: resource 3 io: [0x00-0xffff] [ 0.301770] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffffffffffff] [ 0.301773] pci_bus 0000:02: resource 0 io: [0x4000-0x4fff] [ 0.301776] pci_bus 0000:02: resource 1 mem: [0xc1000000-0xc1ffffff] [ 0.301779] pci_bus 0000:02: resource 2 pref mem [0xc4000000-0xdfffffff] [ 0.301782] pci_bus 0000:07: resource 1 mem: [0xc2000000-0xc20fffff] [ 0.301829] NET: Registered protocol family 2 [ 0.302022] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.303775] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 0.309019] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.309678] TCP: Hash tables configured (established 524288 bind 65536) [ 0.309681] TCP reno registered [ 0.309807] NET: Registered protocol family 1 [ 0.309886] Trying to unpack rootfs image as initramfs... [ 0.496586] Freeing initrd memory: 6949k freed [ 0.500880] Simple Boot Flag at 0x38 set to 0x1 [ 0.501061] Scanning for low memory corruption every 60 seconds [ 0.501248] audit: initializing netlink socket (disabled) [ 0.501268] type=2000 audit(1254208530.500:1): initialized [ 0.511353] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.512959] VFS: Disk quotas dquot_6.5.2 [ 0.513037] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.513727] fuse init (API version 7.12) [ 0.513819] msgmni has been set to 5528 [ 0.514204] alg: No test for stdrng (krng) [ 0.514223] io scheduler noop registered [ 0.514225] io scheduler anticipatory registered [ 0.514228] io scheduler deadline registered (default) [ 0.514276] io scheduler cfq registered [ 0.514528] pci 0000:00:07.0: Enabling HT MSI Mapping [ 0.514654] pci 0000:00:08.0: Enabling HT MSI Mapping [ 0.514792] pci 0000:00:09.0: Enabling HT MSI Mapping [ 0.514938] pci 0000:00:0a.0: Enabling HT MSI Mapping [ 0.515086] pci 0000:00:0b.0: Enabling HT MSI Mapping [ 0.515167] pci 0000:02:00.0: Boot video device [ 0.515500] alloc irq_desc for 24 on node -1 [ 0.515503] alloc kstat_irqs on node -1 [ 0.515526] pcieport-driver 0000:00:14.0: irq 24 for MSI/MSI-X [ 0.515549] pcieport-driver 0000:00:14.0: setting latency timer to 64 [ 0.515726] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.515751] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.519197] ACPI: AC Adapter [ADP1] (on-line) [ 0.519287] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 0.519292] ACPI: Power Button [PWRF] [ 0.519350] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1 [ 0.522234] ACPI: Lid Switch [LID0] [ 0.522285] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [ 0.522292] ACPI: Sleep Button [SLPB] [ 0.522351] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 [ 0.522354] ACPI: Power Button [PWRB] [ 0.522664] processor LNXCPU:00: registered as cooling_device0 [ 0.522702] processor LNXCPU:01: registered as cooling_device1 [ 0.562481] thermal LNXTHERM:01: registered as thermal_zone0 [ 0.562490] ACPI: Thermal Zone [TZS0] (61 C) [ 0.575727] thermal LNXTHERM:02: registered as thermal_zone1 [ 0.575737] ACPI: Thermal Zone [TZS1] (61 C) [ 0.577199] Linux agpgart interface v0.103 [ 0.577204] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.578627] brd: module loaded [ 0.579091] loop: module loaded [ 0.579192] input: Macintosh mouse button emulation as /devices/virtual/input/input4 [ 0.579289] ahci 0000:00:09.0: version 3.0 [ 0.579716] ACPI: PCI Interrupt Link [LSI0] enabled at IRQ 22 [ 0.579721] alloc irq_desc for 22 on node -1 [ 0.579724] alloc kstat_irqs on node -1 [ 0.579736] ahci 0000:00:09.0: PCI INT A -> Link[LSI0] -> GSI 22 (level, low) -> IRQ 22 [ 0.579782] alloc irq_desc for 25 on node -1 [ 0.579784] alloc kstat_irqs on node -1 [ 0.579793] ahci 0000:00:09.0: irq 25 for MSI/MSI-X [ 0.579845] ahci 0000:00:09.0: AHCI 0001.0200 32 slots 2 ports 3 Gbps 0x3 impl IDE mode [ 0.579849] ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio slum part [ 0.579854] ahci 0000:00:09.0: setting latency timer to 64 [ 0.580132] scsi0 : ahci [ 0.580275] scsi1 : ahci [ 0.580360] ata1: SATA max UDMA/133 abar m8192 at 0xc0004000 port 0xc0004100 irq 25 [ 0.580422] ata2: SATA max UDMA/133 abar m8192 at 0xc0004000 port 0xc0004180 irq 25 [ 0.580702] pata_amd 0000:00:06.0: version 0.4.1 [ 0.580749] pata_amd 0000:00:06.0: setting latency timer to 64 [ 0.581384] scsi2 : pata_amd [ 0.581460] scsi3 : pata_amd [ 0.581491] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x30c0 irq 14 [ 0.581494] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30c8 irq 15 [ 0.582264] Fixed MDIO Bus: probed [ 0.582302] PPP generic driver version 2.4.2 [ 0.582435] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.582861] ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 17 [ 0.582866] alloc irq_desc for 17 on node -1 [ 0.582869] alloc kstat_irqs on node -1 [ 0.582880] ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17 [ 0.582899] ehci_hcd 0000:00:02.1: setting latency timer to 64 [ 0.582903] ehci_hcd 0000:00:02.1: EHCI Host Controller [ 0.582965] ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1 [ 0.583003] ehci_hcd 0000:00:02.1: debug port 1 [ 0.583009] ehci_hcd 0000:00:02.1: cache line size of 64 is not supported [ 0.583031] ehci_hcd 0000:00:02.1: irq 17, io mem 0xc0007000 [ 0.593313] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00 [ 0.593395] usb usb1: configuration #1 chosen from 1 choice [ 0.593432] hub 1-0:1.0: USB hub found [ 0.593441] hub 1-0:1.0: 3 ports detected [ 0.593938] ACPI: PCI Interrupt Link [Z011] enabled at IRQ 16 [ 0.593942] alloc irq_desc for 16 on node -1 [ 0.593944] alloc kstat_irqs on node -1 [ 0.593952] ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16 [ 0.593960] ehci_hcd 0000:00:04.1: setting latency timer to 64 [ 0.593964] ehci_hcd 0000:00:04.1: EHCI Host Controller [ 0.594008] ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 2 [ 0.594040] ehci_hcd 0000:00:04.1: debug port 1 [ 0.594045] ehci_hcd 0000:00:04.1: cache line size of 64 is not supported [ 0.594065] ehci_hcd 0000:00:04.1: irq 16, io mem 0xc0007400 [ 0.605477] ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00 [ 0.605540] usb usb2: configuration #1 chosen from 1 choice [ 0.605572] hub 2-0:1.0: USB hub found [ 0.605579] hub 2-0:1.0: 4 ports detected [ 0.605636] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.606511] ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 17 [ 0.606515] ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17 [ 0.606525] ohci_hcd 0000:00:02.0: setting latency timer to 64 [ 0.606529] ohci_hcd 0000:00:02.0: OHCI Host Controller [ 0.606563] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3 [ 0.606630] ohci_hcd 0000:00:02.0: irq 17, io mem 0xc0006000 [ 0.664074] usb usb3: configuration #1 chosen from 1 choice [ 0.664104] hub 3-0:1.0: USB hub found [ 0.664116] hub 3-0:1.0: 3 ports detected [ 0.665034] ACPI: PCI Interrupt Link [Z010] enabled at IRQ 16 [ 0.665038] ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16 [ 0.665048] ohci_hcd 0000:00:04.0: setting latency timer to 64 [ 0.665052] ohci_hcd 0000:00:04.0: OHCI Host Controller [ 0.665085] ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4 [ 0.665098] ohci_hcd 0000:00:04.0: irq 16, io mem 0xc0008000 [ 0.723668] usb usb4: configuration #1 chosen from 1 choice [ 0.723695] hub 4-0:1.0: USB hub found [ 0.723704] hub 4-0:1.0: 4 ports detected [ 0.723761] uhci_hcd: USB Universal Host Controller Interface driver [ 0.724475] PNP: PS/2 Controller [PNP0303:KBD0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [ 0.745532] i8042.c: Detected active multiplexing controller, rev 1.1. [ 0.760168] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.760175] serio: i8042 AUX0 port at 0x60,0x64 irq 12 [ 0.760179] serio: i8042 AUX1 port at 0x60,0x64 irq 12 [ 0.760182] serio: i8042 AUX2 port at 0x60,0x64 irq 12 [ 0.760185] serio: i8042 AUX3 port at 0x60,0x64 irq 12 [ 0.760254] mice: PS/2 mouse device common for all mice [ 0.760386] rtc_cmos 00:06: RTC can wake from S4 [ 0.760431] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0 [ 0.760490] rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs [ 0.760595] device-mapper: uevent: version 1.0.3 [ 0.761181] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel at redhat.com [ 0.761359] device-mapper: multipath: version 1.1.0 loaded [ 0.761363] device-mapper: multipath round-robin: version 1.0.0 loaded [ 0.761684] cpuidle: using governor ladder [ 0.761687] cpuidle: using governor menu [ 0.762210] TCP cubic registered [ 0.762352] NET: Registered protocol family 10 [ 0.762821] lo: Disabled Privacy Extensions [ 0.763128] NET: Registered protocol family 17 [ 0.763152] Bluetooth: L2CAP ver 2.13 [ 0.763154] Bluetooth: L2CAP socket layer initialized [ 0.763158] Bluetooth: SCO (Voice Link) ver 0.6 [ 0.763159] Bluetooth: SCO socket layer initialized [ 0.763209] Bluetooth: RFCOMM TTY layer initialized [ 0.763212] Bluetooth: RFCOMM socket layer initialized [ 0.763214] Bluetooth: RFCOMM ver 1.11 [ 0.763226] powernow-k8: Found 1 AMD Athlon Dual-Core QL-60 processors (2 cpu cores) (version 2.20.00) [ 0.763273] powernow-k8: 0 : pstate 0 (1900 MHz) [ 0.763275] powernow-k8: 1 : pstate 1 (950 MHz) [ 0.763908] PM: Resume from disk failed. [ 0.763922] registered taskstats version 1 [ 0.764084] Magic number: 9:657:269 [ 0.764233] rtc_cmos 00:06: setting system clock to 2009-09-29 07:15:32 UTC (1254208532) [ 0.764237] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 0.764239] EDD information not available. [ 0.783943] ACPI: Battery Slot [BAT0] (battery present) [ 0.787897] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5 [ 1.032019] usb 2-3: new high speed USB device using ehci_hcd and address 3 [ 1.042523] Clocksource tsc unstable (delta = 4397485293811 ns) [ 1.064111] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.064127] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.064861] ata2.00: ATA-8: TOSHIBA MK1652GSX, LV011C, max UDMA/100 [ 1.064864] ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.066138] ata2.00: configured for UDMA/100 [ 1.080870] ata1.00: ATAPI: Slimtype DVD A DS8A2S-A, 6H63, max UDMA/100 [ 1.097545] ata1.00: configured for UDMA/100 [ 1.102185] scsi 0:0:0:0: CD-ROM Slimtype DVD A DS8A2S-A 6H63 PQ: 0 ANSI: 5 [ 1.118194] sr0: scsi3-mmc drive: 24x/6x writer dvd-ram cd/rw xa/form2 cdda pop-up [ 1.118198] Uniform CD-ROM driver Revision: 3.20 [ 1.118308] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 1.118359] sr 0:0:0:0: Attached scsi generic sg0 type 5 [ 1.118448] scsi 1:0:0:0: Direct-Access ATA TOSHIBA MK1652GS LV01 PQ: 0 ANSI: 5 [ 1.118597] sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) [ 1.118606] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 1.118653] sd 1:0:0:0: [sda] Write Protect is off [ 1.118656] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.118659] ata4: port disabled. ignoring. [ 1.118684] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.118816] sda: [ 1.167121] usb 2-3: configuration #1 chosen from 1 choice [ 1.204132] sda1 sda2 sda3 sda4 < sda5 sda6 sda7 > [ 1.255515] sd 1:0:0:0: [sda] Attached SCSI disk [ 1.255545] Freeing unused kernel memory: 660k freed [ 1.255916] Write protecting the kernel read-only data: 7544k [ 1.481032] usb 4-1: new full speed USB device using ohci_hcd and address 2 [ 1.553380] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64. [ 1.553775] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21 [ 1.553782] alloc irq_desc for 21 on node -1 [ 1.553784] alloc kstat_irqs on node -1 [ 1.553797] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 21 (level, low) -> IRQ 21 [ 1.553803] forcedeth 0000:00:0a.0: setting latency timer to 64 [ 1.634709] Initializing USB Mass Storage driver... [ 1.635054] scsi4 : SCSI emulation for USB Mass Storage devices [ 1.635270] usbcore: registered new interface driver usb-storage [ 1.635371] USB Mass Storage support registered. [ 1.637691] usb-storage: device found at 3 [ 1.637695] usb-storage: waiting for device to settle before scanning [ 1.644674] xor: automatically using best checksumming function: generic_sse [ 1.661005] generic_sse: 5818.000 MB/sec [ 1.661008] xor: using function: generic_sse (5818.000 MB/sec) [ 1.664108] device-mapper: dm-raid45: initialized v0.2594b [ 1.684257] usb 4-1: configuration #1 chosen from 1 choice [ 1.687225] hub 4-1:1.0: USB hub found [ 1.690148] hub 4-1:1.0: 4 ports detected [ 1.999155] usb 4-1.1: new low speed USB device using ohci_hcd and address 3 [ 2.074675] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1f:16:45:bc:43 [ 2.074681] forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt lnktim msi desc-v3 [ 2.146240] usb 4-1.1: configuration #1 chosen from 1 choice [ 2.155764] usbcore: registered new interface driver hiddev [ 2.169596] input: Generic Wired USB Keyboard as /devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1.1/4-1.1:1.0/input/input6 [ 2.169684] generic-usb 0003:0D62:0171.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic Wired USB Keyboard] on usb-0000:00:04.0-1.1/input0 [ 2.205247] input: Generic Wired USB Keyboard as /devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1.1/4-1.1:1.1/input/input7 [ 2.205376] generic-usb 0003:0D62:0171.0002: input,hiddev96,hidraw1: USB HID v1.10 Device [Generic Wired USB Keyboard] on usb-0000:00:04.0-1.1/input1 [ 2.220489] input: Generic Wired USB Keyboard as /devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1.1/4-1.1:1.2/input/input8 [ 2.220593] generic-usb 0003:0D62:0171.0003: input,hidraw2: USB HID v1.10 Mouse [Generic Wired USB Keyboard] on usb-0000:00:04.0-1.1/input2 [ 2.220615] usbcore: registered new interface driver usbhid [ 2.220619] usbhid: v2.6:USB HID core driver [ 2.230152] usb 4-1.2: new low speed USB device using ohci_hcd and address 4 [ 2.357245] usb 4-1.2: configuration #1 chosen from 1 choice [ 2.371568] input: Microsoft Microsoft Trackball Explorer® as /devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1.2/4-1.2:1.0/input/input9 [ 2.371667] generic-usb 0003:045E:0024.0004: input,hidraw3: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Explorer®] on usb-0000:00:04.0-1.2/input0 [ 2.455495] PM: Starting manual resume from disk [ 2.455502] PM: Resume from partition 8:7 [ 2.455504] PM: Checking hibernation image. [ 2.455819] PM: Resume from disk failed. [ 2.497349] EXT4-fs (sda3): barriers enabled [ 2.508968] kjournald2 starting: pid 362, dev sda3:8, commit interval 5 seconds [ 2.508983] EXT4-fs (sda3): delayed allocation enabled [ 2.508987] EXT4-fs: file extents enabled [ 2.510633] EXT4-fs: mballoc enabled [ 2.510652] EXT4-fs (sda3): mounted filesystem with ordered data mode [ 3.286545] type=1505 audit(1254208535.020:2): operation="profile_load" pid=382 name=/usr/share/gdm/guest-session/Xsession [ 3.317900] type=1505 audit(1254208535.052:3): operation="profile_load" pid=383 name=/usr/bin/evince [ 3.322407] type=1505 audit(1254208535.056:4): operation="profile_load" pid=383 name=/usr/bin/evince-previewer [ 3.325124] type=1505 audit(1254208535.060:5): operation="profile_load" pid=383 name=/usr/bin/evince-thumbnailer [ 3.342149] type=1505 audit(1254208535.077:6): operation="profile_load" pid=384 name=/usr/lib/cups/backend/cups-pdf [ 3.342545] type=1505 audit(1254208535.077:7): operation="profile_load" pid=384 name=/usr/sbin/cupsd [ 3.347642] type=1505 audit(1254208535.080:8): operation="profile_load" pid=386 name=/sbin/dhclient3 [ 3.347949] type=1505 audit(1254208535.080:9): operation="profile_load" pid=386 name=/usr/lib/NetworkManager/nm-dhcp-client.action [ 6.636172] usb-storage: device scan complete [ 6.638367] scsi 4:0:0:0: Direct-Access WD 10EAVS External 1.65 PQ: 0 ANSI: 4 [ 6.638976] sd 4:0:0:0: Attached scsi generic sg2 type 0 [ 6.639611] sd 4:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 6.641232] sd 4:0:0:0: [sdb] Write Protect is off [ 6.641235] sd 4:0:0:0: [sdb] Mode Sense: 21 00 00 00 [ 6.641239] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 6.644230] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 6.644311] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 > [ 6.749229] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 6.749311] sd 4:0:0:0: [sdb] Attached SCSI disk [ 10.431430] udev: starting version 147 [ 11.091114] EDAC MC: Ver: 2.1.0 Sep 25 2009 [ 11.094516] EDAC amd64_edac: Ver: 3.2.0 Sep 25 2009 [ 11.094597] EDAC amd64: This node reports that Memory ECC is currently disabled. [ 11.094601] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled [ 11.094605] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded. [ 11.094607] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter. [ 11.094608] Might be a BIOS bug, if BIOS says ECC is enabled [ 11.094609] Use of the override can cause unknown side effects. [ 11.094620] amd64_edac: probe of 0000:00:18.2 failed with error -22 [ 11.110339] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x3040 [ 11.110367] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x3000 [ 11.187658] cfg80211: Calling CRDA to update world regulatory domain [ 11.619577] acpi device:0d: registered as cooling_device2 [ 11.619871] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/device:0b/input/input10 [ 11.619958] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 11.790754] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 11.797818] lp: driver loaded but no devices found [ 11.851694] nvidia: module license 'NVIDIA' taints kernel. [ 11.851701] Disabling lock debugging due to kernel taint [ 11.950610] ip_tables: (C) 2000-2006 Netfilter Core Team [ 12.108355] ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 20 [ 12.108364] alloc irq_desc for 20 on node -1 [ 12.108366] alloc kstat_irqs on node -1 [ 12.108380] nvidia 0000:02:00.0: PCI INT A -> Link[LGPU] -> GSI 20 (level, low) -> IRQ 20 [ 12.108390] nvidia 0000:02:00.0: setting latency timer to 64 [ 12.108831] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.36 Fri Aug 14 17:35:21 PDT 2009 [ 12.330576] Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1a0b1, caps: 0xd04711/0xa00000 [ 12.391670] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input11 [ 12.624805] cfg80211: World regulatory domain updated: [ 12.624809] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 12.624814] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 12.624817] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 12.624820] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 12.624823] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 12.624826] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 13.592678] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 19 [ 13.592686] alloc irq_desc for 19 on node -1 [ 13.592689] alloc kstat_irqs on node -1 [ 13.592703] HDA Intel 0000:00:07.0: PCI INT A -> Link[LAZA] -> GSI 19 (level, low) -> IRQ 19 [ 13.592760] HDA Intel 0000:00:07.0: setting latency timer to 64 [ 13.616544] ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23 [ 13.616558] ath5k 0000:07:00.0: setting latency timer to 64 [ 13.616613] ath5k 0000:07:00.0: registered as 'phy0' [ 13.691139] ath: EEPROM regdomain: 0x64 [ 13.691143] ath: EEPROM indicates we should expect a direct regpair map [ 13.691149] ath: Country alpha2 being used: 00 [ 13.691151] ath: Regpair used: 0x64 [ 13.910140] usb 4-1.2: USB disconnect, address 4 [ 13.928029] phy0: Selected rate control algorithm 'minstrel' [ 13.928851] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [ 15.393020] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x304f0d00 [ 15.393144] input: HDA NVidia Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input12 [ 15.393252] input: HDA NVidia Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input13 [ 15.393326] input: HDA NVidia Headphone as /devices/pci0000:00/0000:00:07.0/sound/card0/input14 [ 23.187533] Adding 2040212k swap on /dev/sda7. Priority:-1 extents:1 across:2040212k [ 23.299990] EXT4-fs (sda3): internal journal on sda3:8 [ 23.553647] EXT4-fs (sda5): barriers enabled [ 23.554286] kjournald2 starting: pid 893, dev sda5:8, commit interval 5 seconds [ 23.554873] EXT4-fs (sda5): internal journal on sda5:8 [ 23.554877] EXT4-fs (sda5): delayed allocation enabled [ 23.554881] EXT4-fs: file extents enabled [ 23.555021] EXT4-fs: mballoc enabled [ 23.555046] EXT4-fs (sda5): mounted filesystem with ordered data mode [ 24.253174] __ratelimit: 9 callbacks suppressed [ 24.253178] type=1505 audit(1254226555.988:13): operation="profile_replace" pid=963 name=/usr/share/gdm/guest-session/Xsession [ 24.258370] type=1505 audit(1254226555.992:14): operation="profile_replace" pid=964 name=/usr/bin/evince [ 24.262935] type=1505 audit(1254226555.996:15): operation="profile_replace" pid=964 name=/usr/bin/evince-previewer [ 24.265704] type=1505 audit(1254226556.000:16): operation="profile_replace" pid=964 name=/usr/bin/evince-thumbnailer [ 24.271644] type=1505 audit(1254226556.004:17): operation="profile_replace" pid=967 name=/usr/lib/cups/backend/cups-pdf [ 24.272085] type=1505 audit(1254226556.004:18): operation="profile_replace" pid=967 name=/usr/sbin/cupsd [ 24.276850] type=1505 audit(1254226556.008:19): operation="profile_replace" pid=969 name=/sbin/dhclient3 [ 24.277163] type=1505 audit(1254226556.012:20): operation="profile_replace" pid=969 name=/usr/lib/NetworkManager/nm-dhcp-client.action [ 24.277352] type=1505 audit(1254226556.012:21): operation="profile_replace" pid=969 name=/usr/lib/connman/scripts/dhclient-script [ 24.279623] type=1505 audit(1254226556.012:22): operation="profile_replace" pid=970 name=/usr/sbin/tcpdump [ 24.793584] alloc irq_desc for 26 on node -1 [ 24.793589] alloc kstat_irqs on node -1 [ 24.793602] forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X [ 24.845871] ADDRCONF(NETDEV_UP): wlan0: link is not ready