[01:21] <phixxor> hello, I have a problem with wireless that didn't exist in 8.04, but I'm not sure if I should file a bug report, and if so, what under. May I describe the symptoms here?
[01:22] <maco> go ahead
[01:24] <phixxor> All right. I use a linksys wusb54gv2, and in 8.04 I used ndiswrapper and network manager to connect, which worked fine. But when I go to 8.10 (first by update, second time with a fresh install and no custom setup of ndiswrapper), network manager connects to my network automatically, stays connected for a few minutes, and then disconnects unable to reconnect
[01:26] <maco> so support for the device was added, but it's really poor support?
[01:27] <phixxor> yes that describes it
[01:27] <phixxor> but even when I was using ndiswrapper, it had poor support
[01:30] <maco> well ndiswrapper is a hack :P
[01:30] <maco> ideally we have native support that works
[01:31] <phixxor> maco: all right
[01:32] <phixxor> so where should I report this in launchpad?
[01:34] <maco> linux
[01:37] <phixxor> all right, thanks
[01:37] <phixxor> will do
[01:42] <maco> phixxor: oh, please try with a 9.04 alpha 3 live cd as well
[01:43] <phixxor> maco: good idea, I will
[01:43] <phixxor> it might already be fixed :D
[01:44] <maco> phixxor: exactly
[01:46] <andresmujica> hi!!
[03:05] <b52wrangler> good evening, anyone here who can offer help with a problem encountered during an ibex install on a toshiba satellite
[03:16] <tcole1> I'm using Ibex on a satellite
[03:16] <tcole1> what's your problem?
[03:19] <b52wrangler> hi tcole
[03:20] <b52wrangler> just talked my brother into installing ibex on his windoze toshiba satellite and after installing fine, he can boot, surf web for about a minute, then laptop shuts down uncommanded...
[03:21] <tcole> huh
[03:21] <b52wrangler> tcole: i'm thinking a perceived overheat
[03:21] <tcole> yes, that is plausible
[03:22] <b52wrangler> yet he had not problems while running his other OS
[03:22] <b52wrangler> with overheating
[03:22] <Hobbsee> toshiba satelites have been known to report overheating temperatures, iirc.
[03:22] <Hobbsee> whether they are or not
[03:22] <b52wrangler> ic
[03:22]  * Hobbsee had gotten hers up to 90C before, apparently.
[03:22] <b52wrangler> smokin
[03:22] <Hobbsee> otoh, i had smelt parts burning at other times on it,so...
[03:23] <b52wrangler> i'm having him try hardy now
[03:23] <b52wrangler> problem is he's in NC and I'm in VA
[03:24] <b52wrangler> he was impressed with how everything just worked though for the short time he was able to use it
[04:00] <maco> i thought bug-control was supposed to have access to private bugs
[04:03] <Ryan52> it does, tho I think it doesn't have access to private security bugs, maybe.
[04:04] <maco> Ryan52: thats probably it then. i mistyped the bug number i was looking for anyway
[04:34] <cornucopic> I can't seem to find the URL for stock responses..
[04:34] <cornucopic> Anyone care to help?
[04:35] <cornucopic> Uups..got it..I had bookmared it
[04:35] <cornucopic> *bookmarked
[04:35] <greg-g> https://wiki.ubuntu.com/BugSquad/KnowledgeBase for all your bug triaging knowledge needs
[04:35] <greg-g> :)
[04:36] <cornucopic> greg-g, :-)
[04:37] <cornucopic> Once I start triaging- i.e. the first comment is mine, is that bug immediately mine?
[04:37] <cornucopic> Is that automagic? or I will have to something else..
[04:38] <greg-g> cornucopic: no. Although it would be great if you could continue to help traige the bug, it is not "yours" in the since that no one else can work on it
[04:38] <greg-g> cornucopic: just make sure you subscribe to it so you get updates (but don't "Assign" it to yourself. the Assigned To field is for who is working on writing the patch to fix it)
[04:38] <cornucopic> cornucopic, Hmm..
[04:39] <cornucopic> cornucopic, If I comment, i think I am automatically subscribed?
[04:39] <maco> cornucopic: only if you hit the chekbox
[04:39] <maco> why are you talking to yourself?
[04:39] <greg-g> what maco said.
[04:39] <greg-g> x2
[04:39] <cornucopic> maco, mistake
[04:40] <cornucopic> maco, "Email me..." ?
[04:40] <maco> yes that one
[04:40] <cornucopic> cool.
[04:51] <cprofitt> not sure if I got everything that was needed -- https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/322610
[05:08] <cornucopic> Is it okay to mark a bug as invalid if the steps given for reproduction doesn't lead to the behavior?
[05:09] <cornucopic> Eg. https://bugs.launchpad.net/launchpad/+bug/322604
[05:11] <hggdh> cornucopic, not necessarily
[05:12] <cornucopic> hggdh, Eg. https://bugs.launchpad.net/launchpad/+bug/322604
[05:12] <hggdh> yes, I am looking at it right now
[05:13] <hggdh> hum. old *ix implementations were limited to up to 8 characters in a password
[05:14] <cornucopic> mhm..
[05:14] <maco> hggdh: pam fixed that
[05:14] <hggdh> this is controlled by pam
[05:14] <hggdh> maco, yes
[05:14] <maco> oh wait hrm
[05:15] <maco> in 8.04 pam worked right and only entering the first 8 was not sufficient
[05:15] <hggdh> but the description on the bug sort of suggests the reporter is using the old system (i.e., someone changed the default pam-password)
[05:15] <hggdh> I think it was when crypt was used
[05:15] <maco> well in 9.04 that does not work
[05:15] <hggdh> I know AIX had it
[05:15] <maco> i just tried to use sudo and only enter teh first 8 char, and pam works just fine
[05:15] <cornucopic> I couldn't reproduce the behaviour on 8.10
[05:16] <cornucopic> either.
[05:16] <maco> maybe they removed pam in their system>
[05:16] <hggdh> yes, because you are probably using sha512
[05:16] <hggdh> or they removed pam -- but I would expect this to break a lot of other things
[05:17] <cornucopic> Will the authentication mechanism work without pam?
[05:17] <maco> i think itd just fall back to shadow...
[05:17] <maco> er, well that's just a guess
[05:17] <cornucopic> in that case, it will use the first 8 character?
[05:17] <hggdh> yes
[05:18] <hggdh> (at least, it did)
[05:18] <maco> ive never tried removing pam...
[05:18] <maco> got a vm?
[05:18] <hggdh> it would be interesting to find out what is on /etc/pam.d/
[05:18] <hggdh> heh
[05:18] <cornucopic> maci. i got
[05:18] <cornucopic> maco, a debian VM..
[05:19] <cornucopic> maco, planning to setup a Ubuntu one..
[05:19] <maco> i havent gotten around to configuring kvm on here
[05:19] <maco> mostly because i intend to reinstall....um.....soon
[05:19] <maco> i need to get back to 64bit since all my vms are 64bit and i cant run 64bit vms on a 32bit host
[05:20] <cornucopic> maco, not with 'kvm' i guess...
[05:20] <maco> kvm's just what i use for vms
[05:21] <maco> it doesnt allow 64-on-32
[05:21] <maco> if it did, id load my vm up, upgrade it to jaunty and try
[05:21] <maco> er...oh wait this bug is reported on 8.10, i wouldnt even have to update it
[05:21] <cornucopic> Yeah..its on 8.10..
[05:22] <hggdh> I will have to read back on pam. Long time I left it
[05:24] <hggdh> slangasek will know everything about it, anyways
[05:25] <hggdh> but, basically: if the pam configuration was, er, adjusted, they might get this behaviour
[05:25] <cornucopic> I will probably leave that comment on the bug..after a bit of exploring..
[05:26] <hggdh> good idea. Anyway, this is a good example for my "not necessarily"
[05:26] <maco> i commented asking if they'd removed any parts of pam
[05:27]  * hggdh *has* to get back to pam
[05:27] <hggdh> sigh
[05:27] <cornucopic> maco, cool.
[05:38] <cornucopic> hggdh, Any off hand link for PAM- except the Wikipedia entry?
[05:58] <sbeattie> I *think* the password length issue is this bug: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/51551
[05:59] <maco> who named that library?
[05:59] <sbeattie> basically some of the tools fall back to using crypt because pam got updated to default to sha512
[05:59] <maco> liboobs, libsexy....wtf
[05:59] <cornucopic> maco, Sex, Drugs & Linux :-)
[06:00] <sbeattie> at least libiberty was marginally clever, liboobs not so much.
[06:03] <maco> is oobs supposed to stand for something?
[06:06] <cornucopic> maco, Object Oriented Bindings, he he: http://rpmfind.net/linux/RPM/mandriva/2007.1/x86_64/media/contrib/release/lib64oobs-1_3-devel-2.18.0-1mdv2007.1.x86_64.html
[06:06] <cornucopic> maco, just guessing. :-)
[07:06] <dholbach> good morning
[07:06] <maco> dholbach: hi!
[07:06] <dholbach> hi maco
[07:19] <savvas> maco in serbian means "kitty" (cat) :P
[07:20] <savvas> c as "ts" that is heh
[07:20] <maco> yeah, i know how to read serbo-croatian ;)
[07:21] <maco> i used to transliterate serbian-in-cyrillic to latin letters because my bosnian friend could only read latin letters
[07:21] <savvas> hehe
[07:23] <savvas> that's nothing, the harder part is to read their written cyrillic, all those curls and fancy writing makes my head spin - eventually, at classes, I end up writing my own stuff
[07:23] <maco> yeah, i got a dose of that in russian class, don't worry
[07:24] <maco> "many native russians dont even know how to print. they only write in cursive, so if you print you'll stick out as a foreigner" ...how the heck does one not know how to print? just write it like it looks in a book
[07:30] <savvas> hehehe
[07:34] <thekorn> good morning
[07:35] <maco> hi thekorn
[07:39] <thekorn> hi maco
[08:34] <mangilimic> Hi! Does anybody know how can I handle this bug #275929 ? I understand the problem that the user reported but I think that this sounds like a support request, not really a bug report! Is it correct to close this bug and convert it into a question? Thanks in advance!
[08:36] <davmor2> mangilimic: Does he not just need to switch off the snap to edges option
[08:39] <mangilimic> davmor2: the issue is very easy to solve. As you cab see BarryW wrote that unchecking constraint Y in the Move Window Plugin solves the problem.
[08:41] <mangilimic> Actually I don't know if switching off the snap to edget option, does solve that. But I've tried to switch off the "constraint Y" option and I can move a window wherever I want.
[08:42] <mangilimic> My question is: which is the best way to triage this kind of reports? (very sorry for awful english!)
[08:42] <davmor2> mangilimic: Yes I was thinking of the wrong one :) Could you not set it as a wishlist bug?
[08:43] <mangilimic> davmor2: so in these cases is it better to set the status of the bug to confirmed and importance to whishlist?
[08:44] <mangilimic> (I cannot set it as a whishlist bug because I'm not a member of the bug control group)
[09:01] <davmor2> mangilimic: Just a suggestion.  Being as it is a optional extra and this reporter seems to be the only person with a massive interest in it. Plus it keeps the bug open if more people wish to have it as a default.  You could suggest that the reporter use brainstorm to try and get the defaults for Ubuntu change as the other option.
[09:03] <mangilimic> I understand. Thanks davmor2!
[09:25] <steve555> Hi everyone.
[09:26] <BUGabundo> hi steve555
[09:27] <steve555> Hi BUGabundo. I know today is Hug-Day for compiz,does anybody know if the Hug-Day channel is open now and which it is?
[09:28] <BUGabundo> humm isn't this it ?
[09:30] <steve555> I wasn't sure,the reqason I asked was when I participated in the Hug-Day for Firefox,I was advised to join the Mozilla-Team channel on Freenode.
[09:32] <steve555> Does anybody know of nay good PPA's to get the latest Compiz?I have used it brfore,but I found it a bit slow.
[09:34] <steve555> By the way,I using Kubuntu Jaunty Jackalope Alpha3,with the latest Nouveau drivers and Galluim3d Direct Rendering.
[09:38] <petski> steve555, maybe you can find a good PPA at https://launchpad.net/ubuntu/+ppas?name_filter=compiz
[09:38] <BUGabundo> steve555: if I'm not mistaken, I was the one who redirected you to mozilla team channel
[09:38] <BUGabundo> lol
[09:39] <steve555> I think you was BUGabundo,I just couldn't remember lol!And thank you for the link,I'll check it out.
[11:40] <pedro_> Remember that today is the Compiz Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20090129 there's a bunch of bugs to be triaged, come on squash some!
[12:22] <legate> There is a malfunctioning redirect in https://wiki.ubuntu.com/BugTrackingSystem. https://wiki.ubuntu.com/Bugs/HowToTriage links to this site (first paragraph, "every day through  our BugTrackingSystem.". Is this supposed to lead to https://bugs.launchpad.net/ubuntu?
[12:36] <pedro_> legate: yeah, will look into that now, thanks
[12:36] <legate> pedro_: np
[12:37] <BUGabundo> hi ogasawara
[12:53] <thekorn> happy hugday everybody
[12:53] <pedro_> happy hug day to you too thekorn ;-)
[12:55] <pedro_> mangilimic: ciao!, nice work on the hug day ;-)
[12:55]  * pedro_ hugs mangilimic
[13:04] <mangilimic> pedro_ : I've tried to do my best! ;) Anyway that's all for today! (At the moment I'm studying autotools)
[14:05] <pedro_> Don't forget that today we're celebrating another Hug Day -> https://wiki.ubuntu.com/UbuntuBugDay/20090129
[14:06] <pedro_> charlie-tca: hello!, are you going to join us on the hug day again? ;-)
[14:06] <pedro_> charlie-tca: you're a rockstar come on
[14:06] <charlie-tca> Good morning, pedro_. Yes I expect to join in a little while.
[14:06] <pedro_> charlie-tca: awesome!
[14:06] <charlie-tca> Gotta have coffee first, though
[14:17] <pedro_> hey MrKanister, ready to squash some compiz bugs?
[14:17] <MrKanister> Hi pedro_, sure, but maybe not that much today ;)
[14:18] <pedro_> MrKanister: no problem , any help is always welcome ;-)
[14:20] <MrKanister> pedro_: Wow, you have already triaged a lot
[14:20]  * MrKanister huggs pedro_
[14:21] <pedro_> MrKanister: yeap, I've also cleaned all those apport bugs that were seated from a long while there
[14:21]  * pedro_ hugs MrKanister back
[15:21] <bddebian> Boo
[15:23]  * jgoguen jumps
[15:23] <bddebian> :)
[16:49] <Czubek> Hi all.
[17:00] <Czubek> I have a question: What "Nominate for release" button on launchpad means?
[17:01] <hggdh> that you would like to have the issue resolved on the release you point out
[17:02] <hggdh> Czubek, ^^
[17:05] <Czubek> hggdh: so, when I'm reading bug description, and I know that this bug occurs in supported release, then I should mark those release via "Nominate for release"?
[17:07] <hggdh> not really: "nominate for release" should actually be used only when the issue is serious enough to justify a stable release update (SRU), or inclusing on the current development release
[17:08] <hggdh> Czubek, see above. Usually minor issues do not warrant a SRU
[17:10] <hggdh> Czubek, of course, "serious enough" is a subjective thing. So: if you consider the issue "serious enough", then go ahead and mark it; this will be eventually reviewed, and decided
[17:11] <Czubek> hggdh: You mean this: https://wiki.ubuntu.com/StableReleaseUpdates#When
[17:12] <jgoguen> question about https://launchpad.net/bugs/232340, the Mozilla bug for that was marked as duplicate of another bug that was marked Invalid...should the Thunderbird component of this bug be marked Invalid too, or left as Confirmed?
[17:16] <hggdh> Czubek, yes
[17:16] <Czubek> tnx :)
[17:23] <hggdh> jgoguen, this is a good question. The request makes sense, but the MF has put in place the requirements for CA inclusion, and cacert.org has not yet fulfilled them
[17:24] <hggdh> jgoguen, you can add in a comment summarising what is going on wrt Mozilla Foundation and cacert.org, and keep the Ubuntu task open as wishlist
[17:24] <jgoguen> hggdh: can you change it to Wishlist?  I'm not on bugcontrol
[17:24] <hggdh> jgoguen, will do
[17:25] <jgoguen> hggdh: my other question about that one, since the bug linked was marked as resolved/duplicate should the LP bug be updated to point to the other one, or left to the Mozilla bug it currently points at?
[17:26] <hggdh> jgoguen, in this case I would leave it pointing to the current MF bug -- this gives a summary of the request, and points to why it has been closed as duplicate.
[17:26] <jgoguen> ok, thanks :)
[17:26] <hggdh> jgoguen, most of the times, we would point it to the original upstream bug, though
[17:27] <jgoguen> so in general, if the upstream bug is only marked as a dupe, update to point to the other bug, but if there's explanation in the duplicate then leave it
[17:27] <jgoguen> ok
[17:27] <jgoguen> thanks hggdh
[17:33] <hggdh> jgoguen, I updated the bug. Thank you for your work on it
[17:33] <jgoguen> thanks hggdh :)
[17:34] <hggdh> welcome
[17:35] <mangilimic> I've got a doubt. Bug #289966 . A user reported a problem, and he could find a workaround which fixed his bug. There are also other users which complains about this problem and they state that the workaround solves this issue! Indeed, which is the best status for marking this bug? Confirmed? or Invalid? (as usual I'm sorry for my awful english)
[17:38] <hggdh> mangilimic, a workaround is not a fix, so the bug should not be closed
[17:39] <mangilimic> hggdh: I agree so, is it correct to mark the bug as confirmed?
[17:40] <hggdh> given the others, I guess yes. It would be even better if you yourself could reproduce it.
[17:40] <hggdh> mangilimic, you can set as confirmed, and update the description as shown in https://wiki.ubuntu.com/Bugs/Description.
[17:41] <hggdh> mangilimic, Latest package tested (if you could reproduce) and Workaround in special
[17:42] <mangilimic> ok! :) First of all I'm going to check if this is reproducible!
[17:42] <hggdh> mangilimic, BTW, your English seems pretty good
[17:42] <thekorn> is anybody using editmoin (or other external tools) to edit wikipages on wiki.ubuntu.com?
[17:43] <thekorn> I'm hacking on hugdaytools, and just realized that this wiki is now using OpenID for authentication
[17:43] <mangilimic> hggdh: I'm VERY glad to here that! :) Thanks
[17:43] <thekorn> so this MOIN_ID hack is not working anymore
[17:43] <mangilimic> hggdh: I'm VERY glad to hear that! :) Thanks
[17:44] <pedro_> thekorn: i'm using editmoin
[17:44] <bdmurray> you might need to update you cookie
[17:58] <thekorn> hmm, strange
[18:06] <BuckWild> Hello everyone.  I upgraded my 8.04 installation to the latest set of linux packages, and I get a kernel panic when I try to boot into it.  I'm running an Acer Aspire One netbook.  I believe this problem affects more than just me because I was able to find this link: http://ubuntuforums.org/showthread.php?p=6637549
[18:07] <BuckWild> I think the problem is a bug in one of those packages.  When I boot into 2.6.24-22, I am able to boot the computer fine and everything functions normally.  I just wanted to see if there was a way I could make sure someone is aware of the problem going forward, because it looks like it affects both 8.04 and 8.10 users on the Acer Aspire One
[18:15] <charlie-tca> BuckWild: Is there a bug report on it?
[18:16] <BuckWild> I didn't see one, I just read the page on bug reporting and submitted one
[18:18] <charlie-tca> What is the bug number?
[18:31] <BuckWild> I didn't check
[18:31] <BuckWild> probably shouldn't have closed that browser considering I don't think I have history on it
[18:31] <BuckWild> I tagged it on the image package name
[18:40] <pedro_> BuckWild: http://bugs.launchpad.net/people/+me/+reportedbugs <- check on your lp profile it should be listed there
[18:42] <BuckWild> it's not
[18:42] <BuckWild> I did the reporting through apport, do those get put somewhere else?
[18:43] <maco> and it actually worked?
[18:43] <BuckWild> looked like it did
[18:43] <BuckWild> I can just re-report it if it's not listed or whatever
[18:44] <greg-g> you should have be brought to a launchpad bug report page to describe what happened
[18:44] <BuckWild> yeah maybe it didn't go all the way through then
[18:44] <BuckWild> I'll run it again
[18:48] <BuckWild> the uname command and commands it has listed here are going to generate the wrong version of the kernel because I can't even boot into the other version
[18:51] <charlie-tca> BuckWild: Is that with today's updates or yesterday's updates?
[18:54] <BuckWild> charlie-tca, it might've been yesterday'ss
[18:54] <BuckWild> I installed it today, I didn't have my laptop running yesterday
[18:54] <charlie-tca> Okay, thanks.
[18:57] <BuckWild> np
[19:00] <hggdh> BuckWild, you should also have received an email on your bug. If you did not, it is a good idea to check your LP settings
[19:03] <BuckWild> hggdh, I didn't go all the way through the process last time, I thought I had, but I was being an airhead or something, I'm filing another report.
[19:04] <hggdh> heh
[19:08] <BuckWild> the bug number is 322867 and the link is https://bugs.launchpad.net/bugs/322867
[19:11] <thekorn> argh, it's MOIN_SESSION and not MOIN_ID
[20:07] <thomasdelbeke> Hi there
[20:07] <thomasdelbeke> Is hgddh there?
[20:09] <hggdh> thomasdelbeke, I am here, hi
[20:09] <thomasdelbeke> Hi
[20:09] <thomasdelbeke> You are on two channels now
[20:10] <thomasdelbeke> except the one with your name
[20:10] <thomasdelbeke> Should I close two down?
[20:10] <thomasdelbeke> Anyway
[20:10] <thomasdelbeke> The bug is back
[20:15] <hggdh> !pastebin
[20:50] <score> i'm trying to file a bug for syslog-ng. it exists in the debian package as well. should i file a debian bug and an ubuntu bug, or what?
[20:53] <james_w> score: if you are sure that it affects Debian then filing it in Debian would be great
[20:54] <james_w> if you would like Ubuntu developers to be able to track it as well then file it against Ubuntu too, and link the Debian bug
[21:17] <score> james_w: it's a minor bug. if i file the bug with debian, will if eventually make its way into ubuntu?
[21:18] <james_w> should do
[21:19] <score> does ubuntu mostly pull the diffs from debian, sometimes adding to them.. or do they only do that every 6 months and lose all previous changes?
[21:19] <score> better yet, do you know where i can read up on all this stuff?
[21:20] <james_w> we don't throw it away certainly
[21:21] <james_w> it's an ongoing process, but it peaks every 6 months
[21:21] <james_w> https://wiki.ubuntu.com/UbuntuDevelopment/Merging
[23:12] <thekorn> pedro_, FYI, lp:~thekorn/hugday-tools/reloaded has a new (working) version of the hugday tool
[23:12] <thekorn> it still needs some minor fixes, but it works
[23:12] <pedro_> thekorn: AWESOME!
[23:13]  * pedro_ hugs thekorn
[23:13] <pedro_> thanks dude, will give it a try in a few secs
[23:13] <thekorn> take your time, I need some sleep now,
[23:14] <thekorn> please open bugreports if something is not working
[23:14] <pedro_> ok ;-)
[23:18] <maco> whats the hugday tool?
[23:18] <maco> i havent heard ofthis
[23:21] <pedro_> maco: it allows you to edit the hug day page without using a web browser or editmoin
[23:21] <pedro_> maco: for people that triage more than lets say 20 bugs it becomes really painful to edit the wiki page, you know, find the number , lightgreen blahblah
[23:22] <greg-g> I hated that part of hug day, slowed me down
[23:22] <pedro_> maco: the hugday tools helps you with that, you just pass that numbers to the tool and that's it
[23:22] <pedro_> greg-g: yeah mrkanister was arguing about it the other day
[23:22] <pedro_> he managed to triage like 300 reports during the firefox day and spent more time editing the wiki that actually triaging the bugs
[23:22] <mrooney> couldn't that be integrated into 5-a-day and figure out when to do that via the tag?
[23:23] <greg-g> pedro_: wow
[23:23] <greg-g> mrooney: +1 to integrated tools
[23:23] <greg-g> any help appreciated :)
[23:23] <mrooney> :)
[23:23] <pedro_> I'd *love* to see something like that
[23:23] <greg-g> hell, what bdmurray was thinking about with following the bug mail and doing it all automatically without user input
[23:24] <greg-g> THAT'D be cool.
[23:24] <pedro_> well that'be the perfect situation, automatically get all marked without any user interaction on that
[23:25]  * greg-g nods
[23:42] <cprofitt> does this 'bug' need any more information? https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/322610