2008/02/21/#ubuntu-bugs.txt

[00:00] <jcastro> looking
[00:00] <bdmurray> I thought it was awesome but that might just be me. ;)
[00:00] <jcastro> wow, that is /neat/
[00:01] <bdmurray> Yeah, I like that you filter using regexs too
[00:02] <bdmurray> I added it to Bugs/ReportingToDebian
[00:02] <jcastro> nice
[00:07] <bdmurray> I can't update the wiki either
[00:28] <CarlFK> where do I report this: http://packages.ubuntu.com/gutsy/all/graphicsmagick-libmagick-dev-compat/filelist
[00:28] <CarlFK> which would be the same place I reprt the lack of place where it says "Please report any problems."
[00:29] <bdmurray> CarlFK: I see an e-mail address right in the footer there
[00:31] <CarlFK> whacky.  thanks
[00:32] <bdmurray> no problem
=== calc__ is now known as calc
[04:38] <macd> bug #45842 in server seems to be fine, can anyone else confirm?
[04:38] <ubotu> Launchpad bug 45842 in sysvinit "nfs shares not mounted at startup" [Medium,Confirmed] https://launchpad.net/bugs/45842
[05:14] <bdmurray> macd: seems fine how?
[05:19] <macd> bdmurray: as in it doesnt seem to exist now, in gutsy or feisty.
[05:19] <bdmurray> which it?
[05:22] <macd> someone mentioned 'nfs4' being missing from the mount command in mountall.sh, it exists now, and nfs shares are mounted fine at boot time
[05:24] <bdmurray> mountall.sh is only supposed to mount local filesystems and the 'no' bit in that line excludes proc *and* everything after it
[05:24] <bdmurray> So that bit is a red herring
[05:26] <macd> Then I guess, I just can't reproduce it, on multiple systems.
[05:27] <bdmurray> I believe they should be mounted by /etc/network/if-up.d/mountnfs
[05:27] <bdmurray> macd: Are you the last commenter on that report?
[05:28] <macd> Yes
[05:29] <bdmurray> Are all your systems server installs?
[05:29] <macd> Someone else mentions linking mountnfs within rcS.d/ , but I think it better to not try to mount remote filesystems when the network might be down
[05:29] <macd> Yes, the systems I tried are all server installs
[05:31] <bdmurray> That'd be worth noting as network-manager isn't included in the server install and it may have affected some of the other reporters.  Additionally this bug is on the server team's list for Hardy so someone will be looking at it soon.
[05:32] <macd> Thats the reason I checked it out, I saw it come up on the qa list for hardy-server, so I'll include some additional notes
[05:32] <bdmurray> That'd be very helpful.  Thanks!  I've got to run for now.
=== bdmurray changed the topic of #ubuntu-bugs to: GPM Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20080221 | Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ - http://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
[05:35] <macd> thanks :)
[06:29] <secretlondon> Ah! 198 power management bugs!
[06:42] <CarlFK> I did a crash report thing, it took me to lp, found the bug, asked me if I wanted to subscribe.
[06:42] <CarlFK> if I say yes, I don't think it appends my report
[06:42] <CarlFK> is that expected ?
[06:43] <secretlondon> yes thats normal
[06:43] <secretlondon> I think it should attach IF the bug you subscribe to doesn't have the apport info
[06:43] <CarlFK> so one is enough?
[06:44] <secretlondon> I had a bug on tuesday and I had to make a new bug to get my apport info, and then mark the original bug a duplicate of mine
[06:44] <secretlondon> I don't know - we don't need millions certainly.
[06:46] <techno_freak> CarlFK, you can comment on the same bug, crash reports are also saved so you can manually attach them if you want
[06:46] <CarlFK> I think that would be better that current
[06:46] <CarlFK> #147721
[06:47] <CarlFK> bug #147721
[06:47] <ubotu> Launchpad bug 147721 in displayconfig-gtk "displayconfig-gtk crashed with IndexError in _syncXorgConfig()" [Medium,Confirmed] https://launchpad.net/bugs/147721
[06:47] <CarlFK> bit of chatter - think it is needed?
[06:48] <secretlondon> that already has one set of crash logs, 5 dupes, lot of ME TOOs
[06:48] <CarlFK> I was more thinking the crash report process needed adjustment
[06:48] <secretlondon> its got enough to be confirmed
[06:48] <secretlondon> can you provide info that isn't already there?
[06:48] <CarlFK> to avoid the " make a new bug to get my apport info... dupe" manual steps
[06:49] <secretlondon> CarlFK yes, but actually in this case we don't need as the original bug is from apport anyway
[06:50] <CarlFK> yes = the process needs adjusting
[06:51] <secretlondon> its a bug on apport I think
[06:51] <CarlFK> I think the web site
[06:52] <CarlFK> but not really sure how it should be handled
[06:52] <secretlondon> i think apport (as apport includes the way it interacts with launchpad)
[06:53] <secretlondon> but it could also be on launchpad bugs
[06:53] <CarlFK> so have apport skip the "is it one of these?" step
[06:54] <secretlondon> no no, we want the minimum dupes.
[06:54]  * secretlondon spent ages on tuesday duping python central bugs
[06:54] <secretlondon> we want it to check when you subscribe to a bug to see if it already has apport info
[06:55] <secretlondon> if it doesn't have apport info it should add yours
[06:55] <techno_freak> that will be good
[06:57] <CarlFK> how about an entry point just for apport
[06:59] <CarlFK> so that it can locate one with the same title, and append to it if found
[06:59] <secretlondon> i think we use tags to identify apport attachments so that the retracing bot can finbd them
[07:11] <CarlFK> so one apport info is always enough?
[07:11]  * secretlondon shrugs
[07:11] <secretlondon> one is` certainly better than none
[07:11] <secretlondon> and lots of the same is annoying
[07:12] <CarlFK> but less annoying that not having enough
[07:12] <secretlondon> yes
[07:13] <secretlondon> i'm only a triager not a developer - I can't fix things that aren't packaging or fixed upstream
[07:13] <secretlondon> so a developer may give a different answer
[07:14] <CarlFK> iv done enough development to ponder this :)
[07:14] <techno_freak> CarlFK, check the existing reports and if you can add anything more it will be useful to fix the bug. mere repeating the same is worth null
[07:14] <secretlondon> in fact useful info can get lost amongst 100 ME TOOs
[07:16] <CarlFK> well, it is either the reporters problem to figure out if they have anything to add, or the person reading the reports problem to filter out the dups
[07:18] <CarlFK> i think if the dupes are already attached to the same bug#, it is easier to look for the useful info than trying to get reporters (users) to make a good choice
[07:18] <secretlondon> true
[07:19] <CarlFK> just now, when I hit the "Is the bug you’re reporting one of these?" step I was tempted to close the browser
[07:20] <CarlFK> I really don't want to subscribe, cuz I don't want to get emails about it
=== doko_ is now known as doko
[07:20] <secretlondon> but we always need to ask the reporter questions
[07:20] <secretlondon> if you just file and leave we'll never get anywhere
[07:21] <CarlFK> don't want to "report a new bug" cuz that would annoy the people reading them
[07:22] <CarlFK> i guess 'new' would get me email too
[07:22] <secretlondon> yes
[07:24] <CarlFK> nuff about this now. I'll examine it next time something crashes
[07:24] <secretlondon> ok :)
[07:25] <CarlFK> on the box that crashed: load average: 0.32, 0.11, 0.06
[07:25] <secretlondon> I think I am going to file something about the lack of apport info added to bugs that don't have - as it annoyed me ;)
[07:25] <CarlFK> I do think there is a problem.  just not sure what to do about it
[07:26] <CarlFK> load - why would it be that high on an idle box?
[07:26] <CarlFK> 98.3%id,
[07:26] <secretlondon> good question
[07:26] <secretlondon> tracker?
[07:26] <CarlFK> oh yeah...
[07:27] <CarlFK> hmm
[07:28] <CarlFK> maybe not.  it went to .01, now is back up to .15 and climbing
[07:28] <CarlFK> .20, falling
[07:30] <CarlFK> wow, closing firefox, 0.55
[07:30] <secretlondon> firefox is lardy..
[07:31] <CarlFK> .60
[07:33] <CarlFK> .06 it seems to be oscillating every 5 min
[07:34] <CarlFK> average: 0.04, 0.15, 0.09
[07:34] <CarlFK> close FF is the only thing I have done since  (12:42:18 AM) CarlFK: I did a crash report thing,
[07:35] <CarlFK> average: 0.01,  it's possessed
[07:37] <secretlondon> 12.42 est? mst?
[07:37] <CarlFK> 45 min ago
[07:37] <secretlondon> ok
[07:37] <secretlondon> its 7.30am here
[07:38] <CarlFK> does the lp page have some ajaxy stuff to update the page as other people add changes?
[07:39] <secretlondon> it updates from upstream bug watches, bugs can be closed from changelogs etc
[07:42] <CarlFK> lookslike it was FF causing the load
[07:43] <CarlFK> obviously a P4 256mb is sub standard... :)
[07:44] <secretlondon> I have xubuntu on a p450 here - nice salvaged file server :)
[07:46] <secretlondon> this is only a celeron 1200
[07:46] <CarlFK> decadence!
[07:46]  * secretlondon nods
[07:47] <secretlondon> desktop slightly higher spec but laptop nicer to work on the sofa
[07:48] <CarlFK> my laptop can almost boil water
[07:49] <CarlFK> I need to put a baking sheet on my lap
[07:49] <secretlondon> eek
[07:49] <secretlondon> mine is just cosy
[07:49] <CarlFK> whats the acpi thing to dump cpu temp?
[07:50] <secretlondon> dunno
[07:50] <CarlFK> "use kelvin as the temperature unit"
[07:51] <CarlFK> acpi --thermal  Thermal 1: active[0], 56.0 degrees C
[07:51] <CarlFK> not so bad.  screen must be off
[07:52] <secretlondon>  Thermal 1: ok, 64.0 degrees C here
[08:01] <techno_freak>  Thermal 1: ok, 58.0 degree
[08:02] <techno_freak> and the a/c is switched off.. not bad then
[08:07] <CarlFK> 2am.  i better get to sleep
[08:08]  * secretlondon nods
[08:09] <secretlondon> the rest of europe will wake up soon. I'm nocturnal and woke at 4am :(
[08:09] <techno_freak> ah
[08:09] <secretlondon> 8am here currently
[08:09] <techno_freak> its 1.40 pm here now
[08:10] <secretlondon> ooh you're on a 0.5+ hour
[08:10] <techno_freak> +5.30hours
[08:10] <secretlondon> India?
[08:10] <techno_freak> yes, Bangalore to be specific
[08:11]  * secretlondon guessed from doing a whois and seeing which channels you were on ;)
[08:11] <techno_freak> hehe
[08:29] <techno_freak> bug #189445 - the upstream bug mentioned seems to have got fixed in 2.20.1, the version in hardy is 2.21.1. so what do i mark this bug (reported for gutsy) as?
[08:29] <ubotu> Launchpad bug 189445 in gnome-power-manager "gnome-power-manager fails to show logout dialog" [Undecided,New] https://launchpad.net/bugs/189445
[08:31] <secretlondon> fix released I think
[08:31] <techno_freak> the bug is on gutsy, the fixed version is on hardy :s
[08:32] <secretlondon> yeah - but chances are it won';t get backported
[08:32] <techno_freak> hmm right
[08:49] <techno_freak> secretlondon, it seems that the hardy version might not be incorporating the fix made in debian upstream. so it might not be appropriate to mark it as "fix released".
[09:03] <secretlondon> ok
[09:40] <techno_freak> urgh, it is actually fix released, the bug got fixed in latest version :)
[09:44] <secretlondon> :)
[09:44]  * secretlondon has had bugs that were fixed in feisty but were still set to new and reported in dapper..
[09:46] <techno_freak> hmm
[09:47] <techno_freak> ;)
[09:47] <secretlondon> I suppose I've actually "fixed" some bugs then ;)
[09:49] <techno_freak> :)
=== wolfger_ is now known as wolfger
[11:07] <pedro_> morning!
[11:08] <joachim-n> hi. could someone reopen https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/34283 for me please?
[11:08] <ubotu> Launchpad bug 34283 in openssh "Prompts for password via ssh-askpass multiple times even if canceled" [Low,Incomplete]
[11:09] <techno_freak> joachim-n, done :)
[11:09] <joachim-n> thank you :)
[11:10] <techno_freak> joachim-n, but look at why it was incomplete and give more details to help us
[11:10] <pedro_> still happening with meld and gnome cvs?
[11:11] <pedro_> oh today is Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20080221 feel free to grab any bug of the list
[11:11] <joachim-n> will do
[11:11] <joachim-n> well, meld and gnome svn now
[11:53] <thekorn> bdmurray, morning! thanks for the class-notes,
[11:54] <thekorn> bdmurray, I updated them with the py-lp-b part,
[11:54] <thekorn> bdmurray, and also added a short introduction on clue-files
[11:55] <ubotu> New bug: #193905 in gnome-panel (main) "Icons on panel are out of order (dup-of: 26246)" [Low,Invalid] https://launchpad.net/bugs/193905
[11:55] <thekorn> bdmurray, sorry for messing up the wiki-page, better have a look at the raw text :)
[11:58] <InsClusoe> seb128: Hi... I would like to assist in assigning the bugs to right package and the right team. But I went wrong a couple of times I think.
[11:58] <Iulian> Hey
[11:58] <seb128> hey InsClusoe
[11:58] <seb128> hi Iulian
[11:58] <InsClusoe> For example, Bug 193902..
[11:58] <ubotu> Launchpad bug 193902 in firefox-3.0 "[Hardy alpha5] Firefox launcher is broken (on the top menu)" [Undecided,New] https://launchpad.net/bugs/193902
[11:58] <pedro_> hug day!
[11:59] <seb128> InsClusoe: not always easy without knowing the code
[11:59]  * seb128 hugs pedro_
[11:59]  * pedro_ hugs seb128 back
[11:59]  * pedro_ hugs andre_
[11:59] <seb128> InsClusoe: gnome-menus is what build the applications menu structure using the .desktop installed
[11:59]  * andre_ hugs pedro and seb128
[11:59] <seb128> hey andre_
[11:59] <andre_> salut seb!
[12:00] <seb128> InsClusoe: the launcher are on the panel
[12:00] <seb128> InsClusoe: and those can't be changed on upgrade since they are in the user configuration
[12:00] <Iulian> Hello seb128, pedro_, InsClusoe and andre_
[12:01] <seb128> InsClusoe: so firefox has to keep shipping a firefox.desktop for compatibility reasons
[12:01] <pedro_> heeey Iulian!
[12:01] <InsClusoe> seb128: ok.. I thought I should assign it to gnome-panel but then I couldn't find similar bugs tagged to it. So I put it to gnome-menus.
[12:01] <InsClusoe> Iulian: Hi there...
[12:03] <seb128> InsClusoe: that's alright, as said that's not always easy, don't worry we reassign those the right place when required
[12:04] <InsClusoe> seb128: Feels good to hear that. I don't want to hinder quick movement of bugs.
=== secretlondo is now known as secretlondon
[12:11] <InsClusoe> Is there a way to perform everyday actions and check a log file to understand execution flow? Sorta like a debug mode which I can toggle.
[12:12] <InsClusoe> That's probably a very basic question. But I do not have the answer to that.
[12:14] <InsClusoe> surely you guys do that all the time..
[12:17] <InsClusoe> Iulian: Any clues?
[12:19] <InsClusoe> ok.. I got some clues  from Google..
[12:24] <seb128> InsClusoe: not sure to understand the question
[12:25] <InsClusoe> InsClusoe: Say, a bug is reported that clicking on a menu item results in error. I want to be able to repeat the actions on my pc and see what it does in the background so that I can ask the right questions to bug reporter.
[12:26] <InsClusoe> seb128: Sorry.. Above msg is intended to you.. :-)
[12:27] <InsClusoe> seb128: That will also make me familiar with the packages and sources. That means I can assign it to the right team or fix it if it's bitesized. ;-)
[12:27] <seb128> InsClusoe: there is no easy way to do that no
[12:27] <seb128> the submitter needs to describe what he does
[12:27] <seb128> and you need to try on your system
[12:28] <seb128> and to know what is to blame you have to know what component are used on the desktop, etc
[12:29] <InsClusoe> seb128: ok.. Guess I was trying to go the reverse way.
[12:29] <pedro_> did i mention that today is hug day?
[12:29] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20080221
[12:29] <pedro_> InsClusoe: want to work on some bugs ? :-)
[12:30] <InsClusoe> pedro_: Yes..
[12:30] <pedro_> feel free to grab any of that list then :-)
[12:30] <pedro_> if you have any question about it ask here in the channel
[12:31] <InsClusoe> I don't even know which source file needs fixing.. That's why I was wondering if I could track my familiar actions behind the scenes and understand code flow.
[12:35] <InsClusoe> Something like this is what I was looking for... https://wiki.ubuntu.com/DebuggingProcedures . :-)
[12:35] <Iulian> InsClusoe: Sorry, I was hugging some bugs.
[12:35] <Iulian> Looks like seb128 has answered your question.
[12:36] <InsClusoe> Iulian: Good..
[12:36] <InsClusoe> Iulian: yeah..
[12:36] <Iulian> InsClusoe: And like pedro_ said, you should try too, that's a lot of fun.
[12:37] <secretlondon> agreed
[12:38] <Iulian> Just ask your questions here if you have any.
[12:38] <InsClusoe> Iulian: hmm... will try.
[12:38] <Iulian> Awesome!
[12:39]  * Iulian hugs InsClusoe 
[12:40]  * InsClusoe hugs Iulian in return...
[12:45] <secretlondon> Iulian - you missed #67986 which you've alreadyy hugged ;)
[12:46]  * Iulian is looking
[12:47] <Iulian> secretlondon: Yea, I don't think it was necessary to give a comment.
[12:48] <secretlondon> pedro is editing the wiki so can't make green for you..
[12:48] <secretlondon> Iulian - but without changing the wiki we don't know its been fixed
[12:49] <secretlondon> when you hug a bug you cross it off the list.
[12:50] <pedro_> secretlondon: I've finished the edition
[12:50] <Iulian> I will make them green now.
[12:52] <Iulian> Just after you finish to edit :)
[13:03] <InsClusoe> Iulian: Have to go now.. Will be back soon... See you soon.
[13:20] <secretlondon> my modem overheated :(
[13:57]  * tedg waves
[13:58] <tedg> How's the debugging document?
[13:58] <tedg> Seems like you guys are making great progress today!
[13:58] <pedro_> it's awesome!
[13:58] <pedro_> thanks a lot tedg
[13:58]  * pedro_ hugs tedg
[13:59] <seb128> hey tedg
[13:59] <seb128> tedg: would be nice to have something for the "suspend or hibernate doesn't work" case
[13:59] <seb128> like an acpi command or something to run
[14:00] <seb128> to figure if that's low in the stack or due to gpm and know where to reassign
[14:00] <tedg> pedro_: Thanks.  I didn't have a lot in the triage section, I guess I wasn't sure what exactly to do, it seems like there are a lot of branches to go down.
[14:00] <tedg> seb128: Like something lower than the gnome-power-command.sh?
[14:01] <tedg> seb128: I guess you'd need root access, but that'd be okay.
[14:02] <seb128> tedg: well, that command is only an another interface to gpm, it doesn't tell you whether the issue is due to gpm or to acpi or linux
[14:09] <tedg> seb128: Are you thinking calling HAL through DBUS would be enough?  Or calling pm-utils?
[14:11] <seb128> tedg: I've no idea how that work, but I would like to learn how to know if gpm or something else is to blame and what is the one to blame? acpi? pm-utils?
[14:21] <nDrewPJ> good day (evening) to all! I have a question about gpm along with powertop utility. On my laptop powertop says that I have approx. 2h40min while gpm shows 1h-50min for about 20 minutes....it seems that gpm is selfteaching.... is this a bug? I have much longer battery life with 2.6.24-8 kernel
[14:22] <tedg> nDrewPJ: It's a bug if HAL is reporting the time agreeing with powertop and GPM is misreporting it.
[14:23] <nDrewPJ> how to see the HAL's report?
[14:24] <tedg> nDrewPJ: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-a8d5bf53ac6011cf0e2301bc55eda548006205cc
[14:24] <tedg> nDrewPJ: You might have to do some math, I think that it gives the discharge rate.
[14:25] <seb128> tedg: could be nice to add the maths to do on the wiki debugging page then ;-)
[14:26] <nDrewPJ> do i have to turn AC off when doing that?
[14:27] <tedg> nDrewPJ: For discharge yes.  Recharge no :)
[14:28] <nDrewPJ> mmmh :)
[14:28] <tedg> seb128: Yeah, probably could do some command-line python thingy.... hmm...
=== norsetto_ is now known as norsetto
=== asac_ is now known as asac
[14:41] <pedro_> folks, today is GPM hug day, join the fun https://wiki.ubuntu.com/UbuntuBugDay/20080221 feel free to squash any bug of the list!
[14:42]  * secretlondon is having a break!
[14:42] <secretlondon> well i'm reading the wiki, so not that much of a break ;)
[14:42] <pedro_> ahaha
[14:42] <Iulian> Heh
[14:43] <pedro_> for those using KDE there's a https://wiki.ubuntu.com/UbuntuBugDay/20080221/KDE kde-guidance page too
=== heno_ is now known as heno
[15:16] <bddebian> Boo
[15:17] <pedro_> buuu
[15:17] <pedro_> bddebian: want to scare a couple of bugs today? https://wiki.ubuntu.com/UbuntuBugDay/20080221 ;-)
[15:18] <bddebian> pedro_: Well I've been working on RC bugs on the Debian side but I'll see what I can do
[15:19] <pedro_> rock!
=== emgent is now known as emgent`work
[15:41] <pedro_> folks the bug season is opened  https://wiki.ubuntu.com/UbuntuBugDay/20080221
[15:42] <pedro_> the graphs are looking really hot https://wiki.ubuntu.com/UbuntuBugDay/20080221#head-88f7adb4ca4a2d5fc365d981613ba2b84a72e149
[15:42]  * pedro_ hugs the bugsquad
[15:44]  * secretlondon hugs pedro_
[15:47] <InsClusoe> pedro_: What should I set the status to if the user has reported that the problem is fixed..
[15:48] <InsClusoe> Shld I set it to invalid?
[15:48] <Pici> Fixed on its own?
[15:48] <pedro_> InsClusoe: if the reported said that it was fixed after an update it should be "fix-released" otherwise invalid is ok
[15:48] <pedro_> ahaha
[15:48] <pedro_> Pici: that's a good state :-P
[15:49] <secretlondon> magically went away
[15:49] <InsClusoe> ok.. then this one goes to invalid.
[15:49] <pedro_> haha! an Hocus Pocus status, tasty
[15:52] <InsClusoe> Pici: Yeah.. It got fixed on its own..
[15:56] <InsClusoe> User has logged a bug in Gutsy beta. Should I ask him to test it with Hardy Alpha and report back?
[15:57] <pedro_> InsClusoe: sure, thanks for helping out
[15:57] <InsClusoe> Yup.. Am happy to be of some help.
=== x-spec-t is now known as Spec
[16:22] <tedg> Added a section on sending PM commands directly to HAL: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-2032a88e3ccaf7bd0f270f78c2871417f4361329
=== tsmithe` is now known as tsmithe
[16:39] <InsClusoe> pedro_: What should be the bug status for duplicates? The original bug has an additional line above the Affects and status fields, containing a link to an upstream bug.
[16:41] <InsClusoe> pedro_: Can I set it to confirmed?
[16:51] <Gnine> #ubuntu-us-ga
[16:52] <afflux> InsClusoe: we usually leave the status, as the bug is hidden from the listings anyway
[16:54] <yuriy> any other KDE people working on hug day today?
[17:04] <Gnine> no crashes on latest hardy update
[17:05] <InsClusoe> afflux: no... the bug is listed on the BugDay page..
[17:05] <yuriy> InsClusoe: a bug that's been filed upstream is not a duplicate, it's still a valid bug
[17:06] <pedro_> InsClusoe: sorry i was having lunch, do you have the bug number ?
[17:06] <yuriy> sometimes you can confirm it based on comments in the upstream bug though. and if it's filed upstream and will be dealt with upstream then you can marc as triaged
[17:06] <InsClusoe> no.... A is a duplicate of B. B, meanwhile, has a pointer to an upstream bug. Now what do I do abt A?
[17:06] <pedro_> bug #number here at the channel
[17:06] <afflux> InsClusoe: thats a completely seperate listing. As this is just for triaging, mark them as lightgreen
[17:06] <InsClusoe> Bug #139282
[17:06] <ubotu> Launchpad bug 139282 in gnome-power-manager "Gnome Power Manager Suspends when computer is in Use" [Undecided,Incomplete] https://launchpad.net/bugs/139282
[17:06] <InsClusoe> oops..
[17:07] <InsClusoe> its Bug #145456
[17:07] <ubotu> Launchpad bug 145456 in gnome-power-manager "gnome-power-manager hibernates computer instead of suspend" [Undecided,New] https://launchpad.net/bugs/145456
[17:07] <InsClusoe> sorry abt that
[17:07] <afflux> InsClusoe: just chooose "mark as duplicate" for 145456, give the bug number of the main bug and mark  145456 off on the bugday list
[17:08] <afflux> maybe post a comment like "thanks, this is really a dupe, marking it as such"
[17:08] <afflux> *dup
[17:08] <pedro_> or using the stock response of duplicates from http://wiki.ubuntu.com/Bugs/Responses
[17:08] <pedro_> either way is totally ok
[17:09]  * afflux is having a break: going for a coffee
[17:09] <InsClusoe> pedro_: The link  doesn't work..
[17:09] <pedro_> https://wiki.ubuntu.com/Bugs/Responses
[17:09] <pedro_> it works here
[17:10] <pedro_> response number #10 is the one for dups
[17:10] <jeromeg> anyone running hardy here ?
[17:11] <Iulian> Woah! the graphs looks awesome!
[17:11] <Iulian> I think everyone from this channel is running hardy :-)
[17:11] <pedro_> Iulian: yes! they're!
[17:12] <pedro_> wow the new bugs are being reduced from ~200 to ~70
[17:12] <InsClusoe> pedro_: the first link is htp.. should be https. :-)
[17:12] <Iulian> pedro_: Yep!
[17:12] <pedro_> InsClusoe: he he yeah but you should be redirected :-)
[17:12] <jeromeg> could anyone try to confirm bug #193856 ?
[17:12] <ubotu> Launchpad bug 193856 in gutsy-backports "transmission 1.0.5 doesn't set window icon properly" [Undecided,New] https://launchpad.net/bugs/193856
[17:13] <Gnine> panel crashes when click on logoff/switch user/shutdown icon - 8.04 - 2.6.24-8
[17:13] <pedro_> come on we can reduce it to less than 50
[17:13] <jeromeg> I would like to know if it also happens in hardy
[17:13] <jeromeg> pedro_: what bugs are supposed to be triaged, I could give a hand
[17:13] <pedro_> Gnine: can you report that with apport ? :-)
[17:13] <pedro_> jeromeg: we have a list here: https://wiki.ubuntu.com/UbuntuBugDay/20080221
[17:14] <Iulian> jeromeg: https://wiki.ubuntu.com/UbuntuBugDay/20080221
[17:14] <Iulian> Ah
[17:14] <jeromeg> thank you both ;)
[17:14] <pedro_> and debugging instructions at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager
[17:18] <pedro_> jeromeg: transmission bug is about not having an icon on the window ?
[17:18] <jeromeg> pedro_: yep
[17:19] <pedro_> confirmed i don't have one
[17:19] <jeromeg> ok, i'll move the bug task from backports to the source package
[17:20] <jeromeg> pedro_: it seems to be a packaging issue because upstream provides one
[17:21] <jeromeg> pedro_: gpm sets multimedia keys ?
[17:23] <secretlondon> https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
[17:23] <pedro_> jeromeg: no at all
[17:23] <jeromeg> pedro_: secretlondon : ok because someone of the bug squad team set a bug without package to gpm
[17:23] <jeromeg> so I wanted to know if gpm had eveolved that much ;)
[17:24] <jeromeg> secretlondon: and the bug should be reported against hotkey-setup ?
[17:24] <jeromeg> it can be forwarded somewhere ?
[17:24] <secretlondon> ooh the new launchpad can now link to savannah bug trackers :)
[17:24] <jeromeg> or the kernel devs take care of it ?
[17:25] <secretlondon> jeromeg: dunno
[17:25] <jeromeg> ok
[17:29] <pedro_> woohoo https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/?field.status=NEW
[17:30] <pedro_> 65 New reports
[17:30] <secretlondon> it's a lot better than when I started this morning :)
[17:31] <pedro_> hehe, great work secretlondon!
[17:31]  * pedro_ hugs secretlondon
[17:31] <pedro_> come on we can reduce them to less than 50, we totally can :-)
[17:32] <InsClusoe> pedro_: When I tried to save my changes to BugDay page,I get a warning that it has been saved by someone else in between. I checked the diff and sourcecito has made some changes
[17:32] <pedro_> InsClusoe: hit on cancel and edit it again
[17:32] <jeromeg> pedro_: is it safe to close this one: bug 152730 ?
[17:32] <ubotu> Launchpad bug 152730 in gnome-power-manager "hibernate.sh & sleep.sh work, but GUI (perhaps gnome-power-manager) does not" [Undecided,New] https://launchpad.net/bugs/152730
[17:32] <InsClusoe> pedro_: ok.. thanks
[17:32] <pedro_> btw folks you can use editmoin for edit the wiki page too
[17:32] <jeromeg> pedro_: the guy fixed it by reinstalling hal
[17:32] <pedro_> it's totally more safe
[17:33] <pedro_> apt-get install editmoin
[17:33] <pedro_> jeromeg: yes that's fine just close it as invalid, thanks!
[17:33] <jeromeg> pedro_: ok
[17:34] <pedro_> in case you're interested on editmoin here's a page that explain how you can configure it: http://www.labix.org/editmoin
[17:38] <jeromeg> can anyone confirm this in hardy ? bug 137961
[17:38] <ubotu> Launchpad bug 137961 in gnome-power-manager "powe-manager's graph legends aren't very visible" [Wishlist,New] https://launchpad.net/bugs/137961
[17:38] <jeromeg> it's about the graph colors
[17:40] <InsClusoe> pedro_: Bug #164677. Seems more like a feature request than a bug.
[17:40] <ubotu> Launchpad bug 164677 in gnome-power-manager "No way to keep backlight off" [Undecided,New] https://launchpad.net/bugs/164677
[17:41] <Iulian> InsClusoe: I was looking at the same bug ;)
[17:41] <Iulian> And yes, it seems like a feature request.
[17:41] <Iulian> What do you think, pedro_ ?
[17:42]  * InsClusoe hugs Iulian
[17:42] <pedro_> jeromeg: makes sense the first part of that report, but i don't see the second one
[17:42] <secretlondon> jeromeg: I don't get graphs at all - maybe connected to the hardware you have
[17:42] <pedro_> Iulian: InsClusoe looking now
[17:43] <jeromeg> pedro_: would like me to forward the first par to bugzilla ?
[17:43] <pedro_> jeromeg: that would be really cool do to, do you have an account there?
[17:43] <jeromeg> pedro_: of course :)
[17:43] <pedro_> rock on! feel free to do it then
[17:44] <jeromeg> pedro_: i used to triage a lot a few moths ago
[17:46] <pedro_> Iulian: InsClusoe this bug is just the opposite to the other. bug 147772
[17:46] <ubotu> Launchpad bug 147772 in gnome-power-manager "possible to lower brightness all the way to off" [Undecided,New] https://launchpad.net/bugs/147772
[17:46] <pedro_> maybe that is laptop independent ?
[17:47] <pedro_> tedg: do you know something about that?
[17:48]  * InsClusoe waits for Iulian to update the bug.
[17:51] <Iulian> InsClusoe: It's yours!
[17:52] <InsClusoe> Iulian: I don't know what status to set it to. You update it.
[17:53] <jeromeg> I'm wondering if bug 138514 is really a problem with gpm
[17:53] <ubotu> Launchpad bug 138514 in gnome-power-manager "Media Keys activate backlight when lid closed" [Undecided,New] https://launchpad.net/bugs/138514
[17:53] <jeromeg> any advise on this ?
[17:53] <tedg> pedro_: I guess, why is it  a problem to be able to shut off the backlight?
=== secretlondo is now known as secretlondon
[17:53]  * tedg was learning about editmoin, very cool.
[17:54] <pedro_> tedg: yes, is that possible to do with all the laptops screens or it's just depend on some special characteristic ?
[17:55] <tedg> pedro_: It is hardware/firmware specific.  It depends on the range of values they provide and what "0" means if they support it.
[17:55] <tedg> pedro_: Basically we just support the full range of values, we don't really know what they mean.
[17:55] <tedg> pedro_: I think most laptops allow you to turn it off (I find this a valuable feature in hotel rooms when I want to leave the computer working but go to sleep)
[17:56] <pedro_> tedg: ah ok i see, thanks you
[17:56] <pedro_> ahaha
[17:56] <pedro_> yeah
[17:57] <afflux> secretlondon: do you want to triage bug 187524 any further? It should be ticked off in the bugday list
[17:57] <ubotu> Launchpad bug 187524 in gnome-power-manager "[hardy] screen lights up when lid is closed" [Undecided,New] https://launchpad.net/bugs/187524
[17:57] <jeromeg> pedro_: shall I suscribe desktop-bugs as for other gnome apckages ?
[17:57] <seb128> jeromeg: no
[17:57] <jeromeg> seb128: ok :)
[17:58] <secretlondon> afflux: i
[17:59] <secretlondon> afflux: i'd forgotten about that. it needs proper triaging
[17:59] <InsClusoe> pedro_: the link to editmoin, http://www.labix.org/editmoin, doesn't work. :-( Something wrong with my connection?
[17:59] <secretlondon> afflux: I'm going to bed very soon so don't have time now
[17:59] <jeromeg> InsClusoe: workforme :)
[18:00] <pedro_> mm works fine for me too
[18:02] <InsClusoe> something wrong with my DNS prolly.
[18:02] <seb128> InsClusoe: sudo apt-get install editmoin?
[18:03] <InsClusoe> seb128: errors out. could not find editmoin.
[18:03] <afflux> secretlondon: okay.. should I just ask the reporter for checking the wiki page about details to add to the bug?
[18:04] <secretlondon> I think we want to handhold more than that - ask them for specific info
[18:05] <jeromeg> seb128: i can confirm bug 164950 in gutsy, do you know if it's link to something specific to Ubuntu ?
[18:05] <ubotu> Launchpad bug 164950 in gnome-power-manager "Gnome Power Preferences partially inaccessible" [Undecided,New] https://launchpad.net/bugs/164950
[18:06] <jeromeg> seb128: or I can forward this upstream ?
[18:07] <seb128> jeromeg: that doesn't really make sense, I don't understand the bug
[18:07] <seb128> jeromeg: gpm is an user service, it's looking to user keys
[18:07] <jeromeg> seb128: yep, i know but there is something broken
[18:07] <seb128> jeromeg: how?
[18:08] <seb128> what do you do to get the bug?
[18:08] <secretlondon> is this the power management applet?
[18:08] <jeromeg> in gutsy I've set my system through the interface to never turn screen off
[18:08] <seb128> using what dialog?
[18:08] <jeromeg> but it turns off every 40 minutes when idle
[18:08] <jeromeg> seb128: gnome-power-preferences
[18:09] <jeromeg> and the root key is set to 40 minutes
[18:09] <jeromeg> if it set it to never
[18:09] <jeromeg> everything works as expected
[18:09] <seb128> what key?
[18:09] <jeromeg> just a moment
[18:10] <jeromeg> mm my menus are in french
[18:10] <jeromeg> you speak french, right ?
[18:10] <seb128> yes
[18:10] <jeromeg> Sur secteur
[18:10] <jeromeg> (tab)
[18:10] <seb128> I understand what preference you are speaking about
[18:11] <seb128> but not what gconf key is not correctly changed
[18:11] <jeromeg> Mettre l'écran en veille si inactif depuis :
[18:11] <jeromeg> ...
[18:11] <Cubitus> I have some problems with my intel wifi pro /wireless 4965 agn. It's working but sometimes it looses the connection and if you use the gnome-network-manager, he doesn't connect after reboot. only modprobe -r iwl4965 works to connect then
[18:11] <jeromeg> if i use gksudo gnome-power-preferences and set this key to never, it works fine
[18:12] <seb128> jeromeg: that is weird
[18:12] <secretlondon> Cubitus: you need to file a bug on launchpad
[18:12] <jeromeg> seb128: yep, it annoyed me for a long time before finding the solution
[18:12] <Cubitus> I'm not sure if this is really a bug or a problem with my notebook only
[18:12] <jeromeg> seb128: and I'm not the reporter of the bug :)
[18:12] <Cubitus> because the intel wifi 4965 often works fine for a lot of users
[18:14] <jeromeg> seb128: you manage to confirm this ?
[18:14] <secretlondon> Cubitus: I don't know.  I would file a bug anyway
[18:14] <Cubitus> secretlondon: ok, thanks
[18:14] <seb128> jeromeg: no, wait
[18:14] <jeromeg> ok
=== emgent`work is now known as emgent
[18:25] <jeromeg> seb128: I added your name for a bug you closed and forgot to add it to the list ;)
[18:28] <jeromeg> can anyone confirm if this is fixed in Hardy: bug 59686 ?
[18:28] <ubotu> Launchpad bug 59686 in ubiquity "ubuntu doesn't automatically set boot options" [Undecided,Invalid] https://launchpad.net/bugs/59686
[18:28] <kaboom> Hello everyone! One question: Is the 5 Bugs a day event only for Ubuntu/GNOME or can users with Kubuntu/Xubuntu also participate?
[18:28] <jeromeg> kaboom: of course you can
[18:28] <kaboom> ok, thanks
[18:28] <jeromeg> jeromeg: i don't think there any restrictions, you can work on whatever packages you like
[18:29] <afflux> the bugs schould be in launchpad, though ;)
[18:29] <jeromeg> afflux: :)
[18:29] <afflux> If I have counted right, there are < 50 bugs left today's list
[18:30] <jeromeg> afflux: could test something for me just a second ?
[18:30] <afflux> maybe :)
[18:30] <InsClusoe> What happened to the graphs on bugday page?
[18:30] <jeromeg> could you launch gnome-power-preferences
[18:30] <jeromeg> go to the second tab
[18:30] <jeromeg> and check if the second field has the option "ASK ME"
[18:31] <afflux> it doesn'T
[18:31] <jeromeg> afflux: thank you !
[18:31] <afflux> not sure if it's intended
[18:32] <afflux> no problem
[18:32] <afflux> InsClusoe: what should've happended to them?
[18:32] <jeromeg> afflux: you are using hardy, don't you ?
[18:32] <afflux> yes
[18:32] <InsClusoe> afflux: I can't see them anymore.
[18:32] <jeromeg> thanks
[18:32] <afflux> oh. I can :)
[18:33]  * InsClusoe curses my ISP.. Damn!
[18:33] <afflux> InsClusoe: http://people.ubuntu.com/~brian/complete-graphs/gnome-power-manager/plots/gnome-power-manager-1day-new.png, does that work?
[18:33] <InsClusoe> nope. HTTP 404.
[18:34] <afflux> huh
[18:34] <afflux> http://91.189.90.132/~brian/complete-graphs/gnome-power-manager/plots/gnome-power-manager-1day-new.png ?
[18:34] <InsClusoe> afflux: I don"t know how IRC and launchpad alone work,
[18:34] <afflux> (which is people.ubuntu.com for me)
[18:34] <InsClusoe> afflux: no... 404 again.
[18:34] <afflux> that's weird
[18:35] <secretlondon> weird dns thing, or possibly filtering?
[18:35] <InsClusoe> afflux: am going crazy.. filtering done by ISP?
[18:36] <pedro_> InsClusoe: install bind!
[18:36] <afflux> probably
=== effie_jayx is now known as keffie_jayx
[18:37] <pedro_> wow only 40 new reports
[18:37] <InsClusoe> These pages work everyday. I dont know whats the big deal today.
[18:37] <kaboom> Does someone know how I could make a backtrace of a total system freeze? (Nothing works anymore, all is totally frozen, I only can press the reset button)
[18:37] <afflux> kaboom: does the mouse move?
[18:38] <kaboom> afflux: nope
[18:39] <secretlondon> kaboom: there is info on debugging system crash about sysreq - I couldn't get it to work here but it may work for you
[18:41] <afflux> kaboom: https://help.ubuntu.com/community/DebuggingSystemCrash may be helpful
[18:41] <afflux> kaboom: if not, I've no idea..  :)
[18:41] <kaboom> How long should I run the memory test?
[18:43] <jeromeg> got go now
[18:43] <jeromeg> *got to go
[18:43] <afflux> kaboom: the wiki says "at least one full pass". I recommend doing two or three, or running it over night if you can. I had some errors in the first pass, but they didn't occur later anymore
[18:43] <secretlondon> kaboom: as long as you can really.
[18:43] <jeromeg> bye all
[18:43] <afflux> bye jeromeg
[18:43] <secretlondon> bye jeromeg
[18:43] <jeromeg> ciao afflux
[18:43] <jeromeg> ciao secretlondon
[18:44] <kaboom> Ok, thanks. What exactly is the SysRq-key on a german keyboard
[18:44] <kaboom> ?
[18:44] <kaboom> Maybe S-Abf?
[18:44] <afflux> kaboom: it's alt+print for me
[18:45] <afflux> kaboom: but it can be alt+s-abf too
[18:45] <kaboom> Yeah, then it's maybe the key labeled Druck and below S-Abf
[18:46] <afflux> kaboom: ah, right. s-abf is below "pause" for me ;)
[18:46] <kaboom> OK, Thx
[18:51] <secretlondon> good night - and` great work!
[18:51]  * secretlondon isn't expecting to see many gpm bugs when she wakes up :)
[18:53] <Iulian> G'night secretlondon!
[18:53] <carat> does anybody want to hear a bug?
[18:53] <Iulian> carat: Shoot
[18:53] <carat> ok
[18:53] <Iulian> That's why we are here.
[18:57] <carat> (iam sorry for my englisch, i hope you understand the most...) I installed ubuntu 7.10 on my fathers notebook "dell xps m1210". the problem is, that the screen doesnt stay black when i close it. it went black some seconds but afterwards the full screen (i dont find the right word :-( ) is there again.
[18:59] <kaboom> I've encountered a bug in Kaffeine/libdvdread which appears in Konsole when I start it from there. It doesn't seem to affect the GUI, for the exact error see http://paste.ubuntu.com/4862/
[19:02] <afflux> carat: what did you set in the powermanagement preferences? Should the screen go black or should the system be suspended?
[19:02] <carat> the screen should go black
[19:04] <carat> and he is using the intel proprietary driver, iam now trying it with the normal open driver, mom pls
[19:05] <afflux> carat: thank you
[19:05] <kaboom> bye everyone, I'll be back soon
[19:05] <guu> can someone help me with my first bug report?
[19:08] <InsClusoe> guu: bug number pls..
[19:08] <carat> same problem with the open driver. i should also say that it works with the kde. i think the bug belongs to the gnome-power-manager i heard from many other bugs
[19:09] <afflux> carat: there are a lot of bugs about the lid not working. I think it's worthless reporting this on launchpad
[19:09] <afflux> carat: but thanks for your research and time
[19:10] <afflux> carat: some of them may be listed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager?field.searchtext=closing+lid&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
[19:10] <afflux> (sorry for that long URL)
[19:10] <carat> iam happy to have a chance to give something back! all in all iam very happy with open source, especially debian and ubuntu
[19:10] <carat> thank you
[19:11] <InsClusoe> carat: I think you can try disabling compiz... I know it breaks quite a few things on my Dell laptop.
[19:12]  * afflux hopes that this bugday results in some more gpm bugs being closed.. 266 open bugs is quite a lot :(
[19:12] <InsClusoe> carat: compiz and intel video driver dont appear to work well together. In fact, I couldn't play movies with compiz enabled.
[19:13]  * InsClusoe shares afflux's concern..
[19:13] <InsClusoe> afflux: I hope many of them can be moved upstream..
[19:23] <carat> so i  tried all possibilities, none is working. now iam looking at launchpad and maybe i add some notes
[19:26] <InsClusoe> carat: ok.. that would be great. Thanks.
[20:03] <yuriy> pedro_: didn't get that in on time. it was more of a "please talk about this" than genuine question anyway
[20:03] <pedro_> aah ok
[20:04] <InsClusoe> pedro_: Can you tell me if I should set Bug #162124 to invalid bug or if it is a wishlist item?
[20:04] <ubotu> Launchpad bug 162124 in gnome-power-manager "Should be able to set power preferences systemwide, eg. sleep on lid closed on gdm login screen" [Undecided,New] https://launchpad.net/bugs/162124
[20:04] <pedro_> InsClusoe: looking
=== nelli is now known as onlinelli
=== ember_ is now known as ember
[20:06] <pedro_> InsClusoe: that's out of the scope of gpm i think, wontfix or invalid sounds ok there
[20:07] <InsClusoe> ok... I could guess it but didn't want to when so many experts are approachable around here.
[20:09] <pedro_> yuriy: we have the desktop bug days (GNOME related) on Thursday and the normal ones on Tuesdays
[20:09] <pedro_> we have a lot of bugs on the desktop side that's why we're doing two bugs days a week
[20:09] <yuriy> pedro_: oh ok sounds good
[20:09] <yuriy> i'll try to keep up with the KDE pages on thursdays then
[20:10] <pedro_> that'd be really nice :-)
[20:10] <yuriy> today's turnout (or lack thereof) is really disappointing though
[20:10] <pedro_> i guess we should just announce it
[20:10] <pedro_> maybe we didn't have a lot of participation there because of that
[20:10] <pedro_> but let's announce it and see how it goes
[20:10] <yuriy> well there was the bugsquad ml announcement, which i replied to with a link
[20:12] <InsClusoe> oh.. I didnt know we had 2 bugdays in  a week. And am unable to check my mail because of the some dns issues.
[20:12] <yuriy> will try to improve things for next week i guess
[20:12] <pedro_> right, but maybe another email instead of a reply would be nice
[20:14] <pedro_> WOW
[20:14] <pedro_> 33 New Reports
[20:14] <pedro_> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/?field.status=NEW
[20:15] <pedro_> you guys really rock!
[20:15]  * pedro_ hugs the bugsquad 
[20:15] <pedro_> we had almost 200, that's really cool
[20:16] <afflux> yep, nice job!
[20:16] <nobody43> wow
[20:17]  * bdmurray claps
[20:17] <pedro_> did everyone submitted the bugs to 5-a-day ?
[20:17] <InsClusoe> cool..
[20:17] <afflux> (but, as I said above, we still have about 260 bugs in gpm, and I guess lot's of them are duplicates)
[20:17]  * afflux did submit them
[20:17] <pedro_> https://wiki.ubuntu.com/5-A-Day
[20:17] <pedro_> if you don't please take a look there and do it!
[20:17] <pedro_> it's fun1
[20:18]  * InsClusoe can't. Curses his ISP again..
[20:18]  * pedro_ kicks InsClusoe's ISP
[20:18] <InsClusoe> pedro_: :-D thanks
[20:18] <pedro_> haha
[20:19] <InsClusoe> pedro_: Hey.. Can I edit my comments to a bug?
[20:19] <afflux> InsClusoe: no, you need to add a new comment
[20:20] <InsClusoe> afflux: ok..
[20:34] <pedro_> see you later guys, great work!
[20:35] <afflux> bdmurray: is bug 147772 still an issue for you in current hardy?
[20:35] <ubotu> Launchpad bug 147772 in gnome-power-manager "possible to lower brightness all the way to off" [Undecided,New] https://launchpad.net/bugs/147772
[20:37] <bdmurray> afflux: Are you harassing me? ;) That's a good question - I'll dig out my laptop
[20:45] <bdmurray> Hmm, it does look like it is still an issue
[20:52] <bdmurray> afflux: it does still seem to be a problem
[20:52] <afflux> *grumble* bad compi
[20:52] <afflux> *compiz
[20:53] <afflux> bdmurray: and you're running hardy on it?
[20:53] <bdmurray> yes, I'm just finishing updating packages
[20:54] <alex-weej> ok so network manager is telling my mum her IP address is 0.0.0.0 when connected to the router, i have to get her to do "dhclient eth0" in a terminal to get an IP address
[20:54] <alex-weej> if she connects directly to our modem, it says her IP address is 192.168.100.3
[20:54] <alex-weej> yet ifconfig says its a proper internet IP address
[20:54] <alex-weej> and indeed, the connection works
[20:54] <alex-weej> any ideas what's going on?
[20:55] <alex-weej> (i should add, the connection just does not work in the case where nm thinks the address is 0.0.0.0)
[20:56] <afflux> bdmurray: okay. I'd like to tick this off the bugday list, so what status should we set for it? Leave it as new? I can't confirm it, since I don't own a laptop (really nice for gpm bugs ;))
[20:56] <InsClusoe> router has DHCP enabled? If ip is 0.0.0.0, you are not connected to the router?
[20:56] <afflux> alex-weej: Is using a static IP an option for you?
[20:57] <bdmurray> afflux: Do you know of anything more useful for me to gather?
[20:58] <bdmurray> tedg_: Do you have any ideas of more useful information for bug 147772?
[20:58] <ubotu> Launchpad bug 147772 in gnome-power-manager "possible to lower brightness all the way to off" [Undecided,New] https://launchpad.net/bugs/147772
[20:58] <afflux> bdmurray: I must admit that I don't know anything specifically for g-p-m
[20:59] <afflux> a package version may be a good thing, for the record
[21:16] <InsCluso1> sourcercito: I just saw your update on bug #136871.
[21:16] <ubotu> Launchpad bug 136871 in gnome-power-manager "Idle/inactive action/autosuspend results in a suspend AND a hibernate" [Low,Incomplete] https://launchpad.net/bugs/136871
[21:17] <InsCluso1> An upstream bug has been logged for it... so, can it still be set to incomplete?
[21:17] <bdmurray> afflux: right I've done that
[21:18] <bdmurray> Can anyone verify 147772?
[21:19] <alex-weej> afflux: not really
[21:19] <InsCluso1> bdmurray: sorry... I dont have hardy on my laptop yet.
[21:22] <bdmurray> ogasawara: Could you?
[21:22] <ogasawara> bdmurray: I'll give it a try
[21:23] <bdmurray> sweet, thanks!
[21:23] <InsCluso1> https://bugs.launchpad.net/ubuntu/+bug/194136 has just been logged. Reports that brightness keys do not work at all.
[21:23] <bdmurray> It's kind of scary but there's a workaround too
[21:23] <ubotu> Launchpad bug 194136 in ubuntu "Brightness Special Buttons doesn't work in a UPI Laptop" [Undecided,New]
[21:26] <ogasawara> bdmurray: hrm, I can't confirm - my brightness is controlled by Fn+down-arrow/up-arrow
[21:26] <ogasawara> bdmurray: I can bring the brightness all the way down and back up just fine
[21:27] <bdmurray> hmm, mine gets pitch black and I can't see anything
[21:27] <bdmurray> thanks for checking
[21:28] <ogasawara> bdmurray: mine never gets pitch black
[21:28] <bdmurray> I'm special it seems
[21:32] <seb128_> who was speaking 3 hours ago about a bug which can be worked around using sudo to run the preferences dialog?
[21:33] <dejv_ntb> bdmurray: what problems with backlight do you have?
[21:33] <afflux> seb128_: suppose that's beem jeromeg
[21:34] <seb128_> afflux: that was him, thanks
[21:34] <afflux> seb128_: with bug 164950
[21:34] <ubotu> Launchpad bug 164950 in gnome-power-manager "Gnome Power Preferences partially inaccessible" [Undecided,New] https://launchpad.net/bugs/164950
[21:34] <seb128_> right
[21:35] <bdmurray> dejv_ntb: I can turn it all the way off and increasing the brightness never brings it back.  I have to switch to tty1 and go back to X
[21:36] <afflux> yay, we've now < 30 NEW bugs left for gpm
[21:37] <afflux> I'm going to bed now. good night
[21:38] <InsCluso1> afflux: same here... good night. bye.
[21:38] <dejv_ntb> bdmurray:  I can't confirm this, but I'm not running up-to-date X ATM
[21:38] <afflux> you too
[21:38] <dejv_ntb> I'll tell you later
[22:08] <tedg_> bdmurray: I guess I don't see why it's a problem that you can turn the backlight off.
[22:09] <bdmurray> tedg_: because there isn't a way to turn it back on?
[22:09] <tedg_> bdmurray: The reality is that we don't have a way to know what the values that are given by the firm/hardware actually mean.
[22:09] <tedg_> Well, the problem is you can't increase the backlight level, not that it goes to zero.
[22:09] <tedg_> If both up and down work, I don't see the problem with zero being an option.
[22:10] <bdmurray> Up doesn't work when brightness is 0, it works the rest of the time.
[22:12] <tedg_> So, that's the problem, not that it goes to 0.
[22:12] <tedg_> I wouldn't know why that would be, did you try killing gpm and getting the verbose messages?
[22:12] <tedg_> seb128 had a weird thing where it was using the wrong backlight value.
[22:13] <tedg_> But it was visible in the verbose output.
[22:13] <bdmurray> tedg_: like "gnome-power-manager --no-daemon --debug power"?
[22:16] <tedg_> bdmurray: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-7d2eb767e44a7231fae6964dcf12bc27fe507c9d
=== ember_ is now known as ember
[22:28] <bdmurray> tedg_: additionally by battery shows is_charging = false and is_discharging = false .  What could it be doing then?
[22:35] <tedg_> Did you check "batter.at_lunch"?
[22:36] <tedg_> Is that a /proc battery or a /sys one?
[22:36] <tedg_> The /sys driver seems to be broken :(
[22:37] <bdmurray> that's linux.sysfs_path?
[22:38] <bdmurray> Or how do I know which it is?
[22:41] <tedg_> If it has a sysfs path it'd be the /sys one.
[22:41] <tedg_> If you do a hal-find-by-capability you should get all the "batteries".
[22:42] <tedg_> One is likely to be /proc and one is likely to be /sys
[22:43] <bdmurray> right hal-find-by-capability finds 1 battery and it has linux.sysfs_path
[22:45] <tedg_> Oh, cool.  I wonder if pitti upgraded HAL.
[22:46] <seb128_> yes, he uploaded yesterday
[22:46] <seb128_> the patch to not listed extra batteries
[22:46] <tedg_> Ah, I didn't upgrade this moring.
[22:46] <tedg_> morning
[22:47] <bdmurray> and now I get a battery out to lunch
[22:53] <stgraber> bdmurray: btw, did you see : bug 194052
[22:53] <ubotu> Launchpad bug 194052 in gnome-power-manager "gpm does not create the correct profiling files" [Undecided,Confirmed] https://launchpad.net/bugs/194052
[22:54] <tedg_> bdmurray: So, I think that now in general we can start to look at the problems with the /sys batteries.
[22:54] <stgraber> bdmurray: situation improved here as I now only see one battery instead of the two I had before, but the one it reports doesn't contain any interesting info (not even the charge seems correct)
[22:55] <tedg_> bdmurray: I don't think that HAL is polling it correctly, it may be that the kernel /sys file system isn't sending the events though.
[22:57] <bdmurray> awesome, I guess I ran out of power :(
[22:58] <bdmurray> my laptop just turned off w/o warning
[23:03] <stgraber> bdmurray: mine does that all the time :) (and g-p-m shows a nice 100% charged a second before it runs out of power)
=== Maskarad239-8 is now known as Maskarad2398
[23:38] <bdmurray> tedg_: I've updated my bug with the debug log
[23:48] <tedg_> bdmurray: Seems like GPM thinks the levels are changing...
[23:49] <bdmurray> tedg_: at which line do you see that?
[23:50] <tedg_> I was watching the lines "Setting x of 95"
[23:50] <tedg_> It seems like it goes down with brightness down.
[23:50] <tedg_> And then goes back up to 95 later.
[23:51] <bdmurray> right, that's when I switch to tty1 and back
[23:51] <bdmurray> shouldn't it slowly go back up from 0?
[23:52] <tedg_> I'm looking at 23:28:51, and it looks like it does.
[23:55] <bdmurray> Hunh, that's wacky.  I waited more than 28 seconds
[23:56] <bdmurray> I was looking at the 23:30:45 area
[23:57] <tedg_> So the jump to VT1 was between 23:28:52 and 23:30:45 -- then what happened in the 23:28:51 timeframe?  Were you hitting the up key?
[23:59] <bdmurray> Nothing.  Shouldn't pressing brightness-up show up as a Button press event?
[23:59] <tedg_> One would think...