[00:00] looking [00:00] I thought it was awesome but that might just be me. ;) [00:00] wow, that is /neat/ [00:01] Yeah, I like that you filter using regexs too [00:02] I added it to Bugs/ReportingToDebian [00:02] nice [00:07] I can't update the wiki either [00:28] where do I report this: http://packages.ubuntu.com/gutsy/all/graphicsmagick-libmagick-dev-compat/filelist [00:28] which would be the same place I reprt the lack of place where it says "Please report any problems." [00:29] CarlFK: I see an e-mail address right in the footer there [00:31] whacky. thanks [00:32] no problem === calc__ is now known as calc [04:38] bug #45842 in server seems to be fine, can anyone else confirm? [04:38] Launchpad bug 45842 in sysvinit "nfs shares not mounted at startup" [Medium,Confirmed] https://launchpad.net/bugs/45842 [05:14] macd: seems fine how? [05:19] bdmurray: as in it doesnt seem to exist now, in gutsy or feisty. [05:19] which it? [05:22] 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] mountall.sh is only supposed to mount local filesystems and the 'no' bit in that line excludes proc *and* everything after it [05:24] So that bit is a red herring [05:26] Then I guess, I just can't reproduce it, on multiple systems. [05:27] I believe they should be mounted by /etc/network/if-up.d/mountnfs [05:27] macd: Are you the last commenter on that report? [05:28] Yes [05:29] Are all your systems server installs? [05:29] 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] Yes, the systems I tried are all server installs [05:31] 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] 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] 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] thanks :) [06:29] Ah! 198 power management bugs! [06:42] I did a crash report thing, it took me to lp, found the bug, asked me if I wanted to subscribe. [06:42] if I say yes, I don't think it appends my report [06:42] is that expected ? [06:43] yes thats normal [06:43] I think it should attach IF the bug you subscribe to doesn't have the apport info [06:43] so one is enough? [06:44] 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] I don't know - we don't need millions certainly. [06:46] CarlFK, you can comment on the same bug, crash reports are also saved so you can manually attach them if you want [06:46] I think that would be better that current [06:46] #147721 [06:47] bug #147721 [06:47] Launchpad bug 147721 in displayconfig-gtk "displayconfig-gtk crashed with IndexError in _syncXorgConfig()" [Medium,Confirmed] https://launchpad.net/bugs/147721 [06:47] bit of chatter - think it is needed? [06:48] that already has one set of crash logs, 5 dupes, lot of ME TOOs [06:48] I was more thinking the crash report process needed adjustment [06:48] its got enough to be confirmed [06:48] can you provide info that isn't already there? [06:48] to avoid the " make a new bug to get my apport info... dupe" manual steps [06:49] CarlFK yes, but actually in this case we don't need as the original bug is from apport anyway [06:50] yes = the process needs adjusting [06:51] its a bug on apport I think [06:51] I think the web site [06:52] but not really sure how it should be handled [06:52] i think apport (as apport includes the way it interacts with launchpad) [06:53] but it could also be on launchpad bugs [06:53] so have apport skip the "is it one of these?" step [06:54] no no, we want the minimum dupes. [06:54] * secretlondon spent ages on tuesday duping python central bugs [06:54] we want it to check when you subscribe to a bug to see if it already has apport info [06:55] if it doesn't have apport info it should add yours [06:55] that will be good [06:57] how about an entry point just for apport [06:59] so that it can locate one with the same title, and append to it if found [06:59] i think we use tags to identify apport attachments so that the retracing bot can finbd them [07:11] so one apport info is always enough? [07:11] * secretlondon shrugs [07:11] one is` certainly better than none [07:11] and lots of the same is annoying [07:12] but less annoying that not having enough [07:12] yes [07:13] i'm only a triager not a developer - I can't fix things that aren't packaging or fixed upstream [07:13] so a developer may give a different answer [07:14] iv done enough development to ponder this :) [07:14] 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] in fact useful info can get lost amongst 100 ME TOOs [07:16] 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] 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] true [07:19] 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] 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] but we always need to ask the reporter questions [07:20] if you just file and leave we'll never get anywhere [07:21] don't want to "report a new bug" cuz that would annoy the people reading them [07:22] i guess 'new' would get me email too [07:22] yes [07:24] nuff about this now. I'll examine it next time something crashes [07:24] ok :) [07:25] on the box that crashed: load average: 0.32, 0.11, 0.06 [07:25] 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] I do think there is a problem. just not sure what to do about it [07:26] load - why would it be that high on an idle box? [07:26] 98.3%id, [07:26] good question [07:26] tracker? [07:26] oh yeah... [07:27] hmm [07:28] maybe not. it went to .01, now is back up to .15 and climbing [07:28] .20, falling [07:30] wow, closing firefox, 0.55 [07:30] firefox is lardy.. [07:31] .60 [07:33] .06 it seems to be oscillating every 5 min [07:34] average: 0.04, 0.15, 0.09 [07:34] close FF is the only thing I have done since (12:42:18 AM) CarlFK: I did a crash report thing, [07:35] average: 0.01, it's possessed [07:37] 12.42 est? mst? [07:37] 45 min ago [07:37] ok [07:37] its 7.30am here [07:38] does the lp page have some ajaxy stuff to update the page as other people add changes? [07:39] it updates from upstream bug watches, bugs can be closed from changelogs etc [07:42] lookslike it was FF causing the load [07:43] obviously a P4 256mb is sub standard... :) [07:44] I have xubuntu on a p450 here - nice salvaged file server :) [07:46] this is only a celeron 1200 [07:46] decadence! [07:46] * secretlondon nods [07:47] desktop slightly higher spec but laptop nicer to work on the sofa [07:48] my laptop can almost boil water [07:49] I need to put a baking sheet on my lap [07:49] eek [07:49] mine is just cosy [07:49] whats the acpi thing to dump cpu temp? [07:50] dunno [07:50] "use kelvin as the temperature unit" [07:51] acpi --thermal Thermal 1: active[0], 56.0 degrees C [07:51] not so bad. screen must be off [07:52] Thermal 1: ok, 64.0 degrees C here [08:01] Thermal 1: ok, 58.0 degree [08:02] and the a/c is switched off.. not bad then [08:07] 2am. i better get to sleep [08:08] * secretlondon nods [08:09] the rest of europe will wake up soon. I'm nocturnal and woke at 4am :( [08:09] ah [08:09] 8am here currently [08:09] its 1.40 pm here now [08:10] ooh you're on a 0.5+ hour [08:10] +5.30hours [08:10] India? [08:10] yes, Bangalore to be specific [08:11] * secretlondon guessed from doing a whois and seeing which channels you were on ;) [08:11] hehe [08:29] 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] Launchpad bug 189445 in gnome-power-manager "gnome-power-manager fails to show logout dialog" [Undecided,New] https://launchpad.net/bugs/189445 [08:31] fix released I think [08:31] the bug is on gutsy, the fixed version is on hardy :s [08:32] yeah - but chances are it won';t get backported [08:32] hmm right [08:49] 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] ok [09:40] urgh, it is actually fix released, the bug got fixed in latest version :) [09:44] :) [09:44] * secretlondon has had bugs that were fixed in feisty but were still set to new and reported in dapper.. [09:46] hmm [09:47] ;) [09:47] I suppose I've actually "fixed" some bugs then ;) [09:49] :) === wolfger_ is now known as wolfger [11:07] morning! [11:08] hi. could someone reopen https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/34283 for me please? [11:08] Launchpad bug 34283 in openssh "Prompts for password via ssh-askpass multiple times even if canceled" [Low,Incomplete] [11:09] joachim-n, done :) [11:09] thank you :) [11:10] joachim-n, but look at why it was incomplete and give more details to help us [11:10] still happening with meld and gnome cvs? [11:11] oh today is Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20080221 feel free to grab any bug of the list [11:11] will do [11:11] well, meld and gnome svn now [11:53] bdmurray, morning! thanks for the class-notes, [11:54] bdmurray, I updated them with the py-lp-b part, [11:54] bdmurray, and also added a short introduction on clue-files [11:55] 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] bdmurray, sorry for messing up the wiki-page, better have a look at the raw text :) [11:58] 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] Hey [11:58] hey InsClusoe [11:58] hi Iulian [11:58] For example, Bug 193902.. [11:58] 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] hug day! [11:59] 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] InsClusoe: gnome-menus is what build the applications menu structure using the .desktop installed [11:59] * andre_ hugs pedro and seb128 [11:59] hey andre_ [11:59] salut seb! [12:00] InsClusoe: the launcher are on the panel [12:00] InsClusoe: and those can't be changed on upgrade since they are in the user configuration [12:00] Hello seb128, pedro_, InsClusoe and andre_ [12:01] InsClusoe: so firefox has to keep shipping a firefox.desktop for compatibility reasons [12:01] heeey Iulian! [12:01] 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] Iulian: Hi there... [12:03] InsClusoe: that's alright, as said that's not always easy, don't worry we reassign those the right place when required [12:04] seb128: Feels good to hear that. I don't want to hinder quick movement of bugs. === secretlondo is now known as secretlondon [12:11] 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] That's probably a very basic question. But I do not have the answer to that. [12:14] surely you guys do that all the time.. [12:17] Iulian: Any clues? [12:19] ok.. I got some clues from Google.. [12:24] InsClusoe: not sure to understand the question [12:25] 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] seb128: Sorry.. Above msg is intended to you.. :-) [12:27] 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] InsClusoe: there is no easy way to do that no [12:27] the submitter needs to describe what he does [12:27] and you need to try on your system [12:28] and to know what is to blame you have to know what component are used on the desktop, etc [12:29] seb128: ok.. Guess I was trying to go the reverse way. [12:29] did i mention that today is hug day? [12:29] https://wiki.ubuntu.com/UbuntuBugDay/20080221 [12:29] InsClusoe: want to work on some bugs ? :-) [12:30] pedro_: Yes.. [12:30] feel free to grab any of that list then :-) [12:30] if you have any question about it ask here in the channel [12:31] 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] Something like this is what I was looking for... https://wiki.ubuntu.com/DebuggingProcedures . :-) [12:35] InsClusoe: Sorry, I was hugging some bugs. [12:35] Looks like seb128 has answered your question. [12:36] Iulian: Good.. [12:36] Iulian: yeah.. [12:36] InsClusoe: And like pedro_ said, you should try too, that's a lot of fun. [12:37] agreed [12:38] Just ask your questions here if you have any. [12:38] Iulian: hmm... will try. [12:38] Awesome! [12:39] * Iulian hugs InsClusoe [12:40] * InsClusoe hugs Iulian in return... [12:45] Iulian - you missed #67986 which you've alreadyy hugged ;) [12:46] * Iulian is looking [12:47] secretlondon: Yea, I don't think it was necessary to give a comment. [12:48] pedro is editing the wiki so can't make green for you.. [12:48] Iulian - but without changing the wiki we don't know its been fixed [12:49] when you hug a bug you cross it off the list. [12:50] secretlondon: I've finished the edition [12:50] I will make them green now. [12:52] Just after you finish to edit :) [13:03] Iulian: Have to go now.. Will be back soon... See you soon. [13:20] my modem overheated :( [13:57] * tedg waves [13:58] How's the debugging document? [13:58] Seems like you guys are making great progress today! [13:58] it's awesome! [13:58] thanks a lot tedg [13:58] * pedro_ hugs tedg [13:59] hey tedg [13:59] tedg: would be nice to have something for the "suspend or hibernate doesn't work" case [13:59] like an acpi command or something to run [14:00] to figure if that's low in the stack or due to gpm and know where to reassign [14:00] 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] seb128: Like something lower than the gnome-power-command.sh? [14:01] seb128: I guess you'd need root access, but that'd be okay. [14:02] 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] seb128: Are you thinking calling HAL through DBUS would be enough? Or calling pm-utils? [14:11] 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] 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] nDrewPJ: It's a bug if HAL is reporting the time agreeing with powertop and GPM is misreporting it. [14:23] how to see the HAL's report? [14:24] nDrewPJ: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-a8d5bf53ac6011cf0e2301bc55eda548006205cc [14:24] nDrewPJ: You might have to do some math, I think that it gives the discharge rate. [14:25] tedg: could be nice to add the maths to do on the wiki debugging page then ;-) [14:26] do i have to turn AC off when doing that? [14:27] nDrewPJ: For discharge yes. Recharge no :) [14:28] mmmh :) [14:28] 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] 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] well i'm reading the wiki, so not that much of a break ;) [14:42] ahaha [14:42] Heh [14:43] 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] Boo [15:17] buuu [15:17] bddebian: want to scare a couple of bugs today? https://wiki.ubuntu.com/UbuntuBugDay/20080221 ;-) [15:18] pedro_: Well I've been working on RC bugs on the Debian side but I'll see what I can do [15:19] rock! === emgent is now known as emgent`work [15:41] folks the bug season is opened https://wiki.ubuntu.com/UbuntuBugDay/20080221 [15:42] 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] pedro_: What should I set the status to if the user has reported that the problem is fixed.. [15:48] Shld I set it to invalid? [15:48] Fixed on its own? [15:48] InsClusoe: if the reported said that it was fixed after an update it should be "fix-released" otherwise invalid is ok [15:48] ahaha [15:48] Pici: that's a good state :-P [15:49] magically went away [15:49] ok.. then this one goes to invalid. [15:49] haha! an Hocus Pocus status, tasty [15:52] Pici: Yeah.. It got fixed on its own.. [15:56] User has logged a bug in Gutsy beta. Should I ask him to test it with Hardy Alpha and report back? [15:57] InsClusoe: sure, thanks for helping out [15:57] Yup.. Am happy to be of some help. === x-spec-t is now known as Spec [16:22] 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] 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] pedro_: Can I set it to confirmed? [16:51] #ubuntu-us-ga [16:52] InsClusoe: we usually leave the status, as the bug is hidden from the listings anyway [16:54] any other KDE people working on hug day today? [17:04] no crashes on latest hardy update [17:05] afflux: no... the bug is listed on the BugDay page.. [17:05] InsClusoe: a bug that's been filed upstream is not a duplicate, it's still a valid bug [17:06] InsClusoe: sorry i was having lunch, do you have the bug number ? [17:06] 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] 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] bug #number here at the channel [17:06] InsClusoe: thats a completely seperate listing. As this is just for triaging, mark them as lightgreen [17:06] Bug #139282 [17:06] 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] oops.. [17:07] its Bug #145456 [17:07] Launchpad bug 145456 in gnome-power-manager "gnome-power-manager hibernates computer instead of suspend" [Undecided,New] https://launchpad.net/bugs/145456 [17:07] sorry abt that [17:07] 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] maybe post a comment like "thanks, this is really a dupe, marking it as such" [17:08] *dup [17:08] or using the stock response of duplicates from http://wiki.ubuntu.com/Bugs/Responses [17:08] either way is totally ok [17:09] * afflux is having a break: going for a coffee [17:09] pedro_: The link doesn't work.. [17:09] https://wiki.ubuntu.com/Bugs/Responses [17:09] it works here [17:10] response number #10 is the one for dups [17:10] anyone running hardy here ? [17:11] Woah! the graphs looks awesome! [17:11] I think everyone from this channel is running hardy :-) [17:11] Iulian: yes! they're! [17:12] wow the new bugs are being reduced from ~200 to ~70 [17:12] pedro_: the first link is htp.. should be https. :-) [17:12] pedro_: Yep! [17:12] InsClusoe: he he yeah but you should be redirected :-) [17:12] could anyone try to confirm bug #193856 ? [17:12] 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] panel crashes when click on logoff/switch user/shutdown icon - 8.04 - 2.6.24-8 [17:13] come on we can reduce it to less than 50 [17:13] I would like to know if it also happens in hardy [17:13] pedro_: what bugs are supposed to be triaged, I could give a hand [17:13] Gnine: can you report that with apport ? :-) [17:13] jeromeg: we have a list here: https://wiki.ubuntu.com/UbuntuBugDay/20080221 [17:14] jeromeg: https://wiki.ubuntu.com/UbuntuBugDay/20080221 [17:14] Ah [17:14] thank you both ;) [17:14] and debugging instructions at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager [17:18] jeromeg: transmission bug is about not having an icon on the window ? [17:18] pedro_: yep [17:19] confirmed i don't have one [17:19] ok, i'll move the bug task from backports to the source package [17:20] pedro_: it seems to be a packaging issue because upstream provides one [17:21] pedro_: gpm sets multimedia keys ? [17:23] https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch [17:23] jeromeg: no at all [17:23] pedro_: secretlondon : ok because someone of the bug squad team set a bug without package to gpm [17:23] so I wanted to know if gpm had eveolved that much ;) [17:24] secretlondon: and the bug should be reported against hotkey-setup ? [17:24] it can be forwarded somewhere ? [17:24] ooh the new launchpad can now link to savannah bug trackers :) [17:24] or the kernel devs take care of it ? [17:25] jeromeg: dunno [17:25] ok [17:29] woohoo https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/?field.status=NEW [17:30] 65 New reports [17:30] it's a lot better than when I started this morning :) [17:31] hehe, great work secretlondon! [17:31] * pedro_ hugs secretlondon [17:31] come on we can reduce them to less than 50, we totally can :-) [17:32] 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] InsClusoe: hit on cancel and edit it again [17:32] pedro_: is it safe to close this one: bug 152730 ? [17:32] 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] pedro_: ok.. thanks [17:32] btw folks you can use editmoin for edit the wiki page too [17:32] pedro_: the guy fixed it by reinstalling hal [17:32] it's totally more safe [17:33] apt-get install editmoin [17:33] jeromeg: yes that's fine just close it as invalid, thanks! [17:33] pedro_: ok [17:34] 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] can anyone confirm this in hardy ? bug 137961 [17:38] 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] it's about the graph colors [17:40] pedro_: Bug #164677. Seems more like a feature request than a bug. [17:40] Launchpad bug 164677 in gnome-power-manager "No way to keep backlight off" [Undecided,New] https://launchpad.net/bugs/164677 [17:41] InsClusoe: I was looking at the same bug ;) [17:41] And yes, it seems like a feature request. [17:41] What do you think, pedro_ ? [17:42] * InsClusoe hugs Iulian [17:42] jeromeg: makes sense the first part of that report, but i don't see the second one [17:42] jeromeg: I don't get graphs at all - maybe connected to the hardware you have [17:42] Iulian: InsClusoe looking now [17:43] pedro_: would like me to forward the first par to bugzilla ? [17:43] jeromeg: that would be really cool do to, do you have an account there? [17:43] pedro_: of course :) [17:43] rock on! feel free to do it then [17:44] pedro_: i used to triage a lot a few moths ago [17:46] Iulian: InsClusoe this bug is just the opposite to the other. bug 147772 [17:46] 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] maybe that is laptop independent ? [17:47] tedg: do you know something about that? [17:48] * InsClusoe waits for Iulian to update the bug. [17:51] InsClusoe: It's yours! [17:52] Iulian: I don't know what status to set it to. You update it. [17:53] I'm wondering if bug 138514 is really a problem with gpm [17:53] Launchpad bug 138514 in gnome-power-manager "Media Keys activate backlight when lid closed" [Undecided,New] https://launchpad.net/bugs/138514 [17:53] any advise on this ? [17:53] 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] tedg: yes, is that possible to do with all the laptops screens or it's just depend on some special characteristic ? [17:55] 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] pedro_: Basically we just support the full range of values, we don't really know what they mean. [17:55] 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] tedg: ah ok i see, thanks you [17:56] ahaha [17:56] yeah [17:57] secretlondon: do you want to triage bug 187524 any further? It should be ticked off in the bugday list [17:57] Launchpad bug 187524 in gnome-power-manager "[hardy] screen lights up when lid is closed" [Undecided,New] https://launchpad.net/bugs/187524 [17:57] pedro_: shall I suscribe desktop-bugs as for other gnome apckages ? [17:57] jeromeg: no [17:57] seb128: ok :) [17:58] afflux: i [17:59]