[00:09] <cupped> euler
[00:09] <cupped> whoops
[00:43] <is_> Hey guys, I found what seems to be a minor security issue, but I'm not entirely sure if it is or not, and I don't really know where to report either
[15:32] <drcooper> Any member of Ubuntu Bug Control please set https://bugs.launchpad.net/unity/+bug/666768 to wishlist
[15:32] <ubot2> Launchpad bug 666768 in unity "Make sidebar translucent (affects: 1) (heat: 6)" [Undecided,New]
[15:34] <hggdh> drcooper: this is not an Ubuntu bug (yes, it is Unity, but the *upstream* Unity. We cannot deal with it, sorry
[15:35] <drcooper> hggdh: ok..
[15:51] <drcooper> https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/666746
[15:51] <ubot2> Launchpad bug 666746 in gnome-screensaver (Ubuntu) "Screen locked after hibernate (affects: 1) (heat: 6)" [Undecided,New]
[15:51] <drcooper> which package should this bug be associated to
[16:01] <drcooper> which package should the 666746 bug be associated to? new to bug squad pls help
[16:01] <rusivi> bug 666746
[16:01] <ubot2> Launchpad bug 666746 in gnome-screensaver (Ubuntu) "Screen locked after hibernate (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/666746
[16:04] <rusivi> drcooper: You nailed it for now. I'll quickly test to get it confirmed.
[16:05] <drcooper> rusivi: it was not reported by me...i doubt if it should be reported as a gnome-screensaver bug
[16:06] <drcooper> rusivi: i think it affects pm-utils package or something like that
[16:06] <micahg> bug #?
[16:07] <rusivi> bug 666746
[16:07] <ubot2> Launchpad bug 666746 in gnome-screensaver (Ubuntu) "Screen locked after hibernate (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/666746
[16:08] <rusivi> micahg / drcooper: I already found?! another bug in Maverick -> System -> Admin -> Login Settings, I did not have the opportunity to auto-login as my originally created user account :D
[16:08] <micahg> rusivi: I think that should stay in gnome-screensaver since the settings aren't being honored
[16:09] <rusivi> micahg: Agreed.
[16:09] <rusivi> micahg: What do you think about the Login Settings "bug" is that intentional or buggable?
[16:10] <micahg> rusivi: the setting might have moved, maybe check in #ubuntu before filing
[16:10] <drcooper> micahg: rusivi but how would hibernation be related to screensaver settings
[16:11] <micahg> drcooper: I've actually been experiencing a bug where my screensaver is activated after resume as well, but I actually use the lock feature, if the setting says don't require a password ever, then that should be respected, there might be 2 bugs in fact
[16:12]  * micahg seems to recall a setting for no password on resume as well
[16:12] <drcooper> micahg: thats debatable as u set LOCK screen to be enabled
[16:13] <drcooper> micahg: there should be some lock
[16:13] <drcooper> :D
[16:16] <drcooper> micahg: rusivi i think its apt to confirm the bug
[16:16]  * micahg would suggest someone reproducing it :)
[16:17] <drcooper> micahg: yes it does happen that way
[16:17] <drcooper> micahg: i tried
[16:18] <micahg> drcooper: feel free to confirm then explaining what you did
[16:20] <rusivi> drcooper: you beat me to the punch :P hehe
[16:20]  * micahg found an upstream bug
[16:20] <drcooper> rusivi: ?
[16:20] <rusivi> drcooper: jk
[16:20] <drcooper> rusivi: again ?
[16:20] <rusivi> drcooper: I'm a jokster don't mind me.
[16:21] <micahg> are you both using the same version of gnome-screensaver as the reporter?
[16:23] <drcooper> micahg: yes
[16:25] <micahg> drcooper: does the gconf key mentioned in the upstream bug help?
[16:27] <drcooper> micahg: sorry, did not get you
[16:27] <micahg> drcooper: I linked an upstream bug to the LP bug, can you read that and see if the gconf key helps
[16:34] <micahg> rusivi: can you try the gconf key?
[16:36] <drcooper> micahg: setting the key fixed it !!
[16:36] <drcooper> micahg: so what shud be done with the bug
[16:36] <micahg> drcooper: :), well that's good news, I'll post to the upstream bug, maybe it can be fixed
[16:36] <micahg> drcooper: thanks
[16:37] <micahg> drcooper: this one? /desktop/gnome/lockdown/disable_lock_screen=true
[16:37] <rusivi> micahg: Let me check it out
[16:37] <drcooper> micahg: yaes
[16:37] <micahg> rusivi: 'tis ok
[16:37] <micahg> drcooper: thanks
[16:39] <rusivi> micahg: Regarding /desktop/gnome/lockdown that's a little over my head, where do I go to find that file/folder?!
[16:39] <micahg> rusivi: you need to use gconf-editor, it's already been confirmed, so you don't need to do it unless you want the fix
[16:45] <drcooper> micahg: so thats how a bug is triaged !! :D
[16:45] <micahg> drcooper: one way :)
[16:46] <drcooper> micahg: turns out to be my first experience
[16:46] <micahg> drcooper: cool, well thank you for confirming
[16:47] <micahg> drcooper: generally, it makes it to triaged where there is enough information to reproduce and it's a confirmed bug (upstream bug link almost always makes a bug triaged)
[16:47] <drcooper> micahg: ohhk..
[17:22] <mreiter> Hi, I filed a bug about failing hibernation on Thinkpads in 10.10 and I think it is ready to be triaged according to the wiki (https://wiki.ubuntu.com/Bugs/HowToTriage/). Could some Bug Control member maybe have a look and triage it? Here's the bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/661711
[17:22] <ubot2> Launchpad bug 661711 in linux (Ubuntu) "Hibernate fails on Thinkpads (affects: 9) (heat: 54)" [Undecided,Confirmed]
[17:27] <mreiter> I really did everything I could to make the report as complete as possible and according to the criteria in the wiki, the report is ready to be triaged. I can't do it, because I'm not a member of Bug Control. The wiki says to ask here in this case. It would be really awesome if this get fixed and it shouldn't be difficult, because I am not able to reproduce the bug with a newer kernel version...
[17:39] <micahg> drcooper: duplicate bug? bug
[17:39] <micahg> bug 599783
[17:39] <ubot2> Launchpad bug 599783 in gnome-control-center (Ubuntu) (and 1 other project) "proxy capplet is not IPv6 aware (affects: 1) (heat: 32)" [Low,Triaged] https://launchpad.net/bugs/599783
[17:42] <sense> drcooper: Seems indeed duplicate
[17:42] <drcooper> yup
[17:42] <micahg> drcooper: you can mark it a duplicate, please use the response on the responses page
[17:43] <sense> drcooper: Do you know how to mark a bug as a duplicate?
[17:43] <drcooper> sense mark as dulicate right?
[17:43] <sense> drcooper: THere is a list of stock responses at <http://wiki.ubuntu.com/Bugs/Responses> you can use when responding to bug reports, it saves you some time.
[17:43] <sense> drcooper: yes.
[17:52] <micahg> drcooper: it's good to make a comment when marking as a duplicate using the response from the responses page sense gave you
[17:52] <drcooper> micahg: as a comment before marking as duplicate?
[17:52] <micahg> drcooper: yes
[17:52] <drcooper> micahg: can i add it now
[17:52] <micahg> drcooper: yes
[17:53]  * micahg will be back later
[19:19] <BUGa_badmood> o/
[19:26] <JimmyJohn> Hey, I think this bug has been reported before but I'm not sure. I'm on a toshiba satellite e205 s1904 and can't finish installing. gives me a "child_rip" error and just halts, reading 0x0 0x20
[19:26] <JimmyJohn> I got it to go farther and actually got ubuntu to boot once by turning off acpi but it won't work again
[19:26] <JimmyJohn> it crashed after that anyway
[19:28] <JimmyJohn> Anybody know anything about this?
[19:30] <mrand> JimmyJohn: Google turns this up: http://ubuntuforums.org/showthread.php?t=1496796, which seems to imply it isn't a bug with Ubuntu.
[19:32] <JimmyJohn> but it also turns this up
[19:32] <JimmyJohn> http://ubuntuforums.org/showthread.php?t=1445892
[19:32] <JimmyJohn> and the OP isn't even on a toshiba. not to mention i've checked the site, no bios updates
[19:37] <mrand> Many computer vendors use the same chipsets and BIOS, so I don't think it much matters that it isn't toshiba specific.  The first thread links to a bug which then points to a work-around (kernel patch)
[19:40] <JimmyJohn> would you mind telling me what I'm supposed to do with that? I'm at the link from the first thread.
[19:46] <mrand> JimmyJohn: short of compiling your own kernel with that patch and/or continuing going down the  acpi route, unfortunately the answer appears to be that the bug in the BIOS is blocking your computer, and many like it, from properly using Linux.
[19:46] <mrand> down the non-acpi, that is.
[19:47] <JimmyJohn> I think i just got a kernel from a guy. He posted it in one of the linked threads, after compiling it, so now i have a .deb and a .patch, i just don't know what to do with them. Others are saying this fixed it though
[19:50] <JimmyJohn> ?
[19:52] <mrand> JimmyJohn: .deb are normally installed with dpkg.  Not sure what you would do with the .patch.  You might try asking on #Ubuntu.  this channel is more discussing the process and processing of bugs rather than debugging.
[20:27] <guntbert> what is the meaning of "One Hundred Paper Cuts" ?
[20:28] <BUGa_badmood> quick fixes
[20:30] <guntbert> BUGa_badmood: thx -- if your nick is "true" I won't bother you any more :-)
[20:32] <BUGa_badmood> guntbert: in a bad mood, cause I missed the delivery guy
[20:32] <BUGa_badmood> now will have to wait another day to get my hands on my new Desire HD
[20:32] <hggdh> heh
[20:32] <RedSingularity> lol HATE when that happens!
[20:32] <guntbert> BUGa_badmood: sorry to hear - no neighbors around to take it for you?
[20:33] <BUGa_badmood> they don't do that
[20:33] <BUGa_badmood> its a 500+€ piece
[20:33] <BUGa_badmood> no leaving on the neibour
[20:34] <guntbert> understandable
[20:34] <guntbert> but back to my question: is there anyplace to read up on the "One Hundred Paper Cuts"?
[20:37] <rusivi> guntbert: https://wiki.ubuntu.com/PaperCut
[20:37] <guntbert> rusivi: thx
[21:08] <guntbert> about https://wiki.ubuntu.com/Bugs/CommonTasks  : there is stated about kernel bugs that "For Hardy (8.04) - Lucid (10.04) the correct package is linux". I guess that is/will be true for current and future releases as well. I f no one objects I'm going to change that to "For Hardy (8.04) and later releases the correct ..."
[21:13] <rusivi> guntbert: Sounds good.
[21:18] <guntbert> rusivi: done
[21:22] <njin> hello, there's a finnish here to triage this ? https://bugs.launchpad.net/ubuntu/+bug/431922
[21:22] <ubot2> Launchpad bug 431922 in ubuntu "dead_stroke broken in some applications (affects: 1) (heat: 8)" [Undecided,Incomplete]
[21:38] <MoLE_> Quiet in here - everyone must be at UDS
[21:38] <MoLE_> any suggestions on how to advance bug 558431 ?
[21:38] <ubot2> Launchpad bug 558431 in parted (Ubuntu) (and 3 other projects) "gparted crashes at startup - Assertion failed (affects: 20) (dups: 3) (heat: 100)" [Undecided,Confirmed] https://launchpad.net/bugs/558431
[22:37] <RedSingularity> micahg:  are you going to address bug 643736 or should i move my comment about wish-listing there?
[22:37] <ubot2> Launchpad bug 643736 in thunderbird (Ubuntu) ""What's new in Thunderbird 3" reappears on minor upgrades (affects: 1) (heat: 102)" [Undecided,New] https://launchpad.net/bugs/643736
[22:38] <micahg> RedSingularity: yes, I think I'll mark it won't fix though
[22:39] <RedSingularity> micahg: for which bug?
[22:39] <micahg> RedSingularity: the one you just said
[22:40] <RedSingularity> micahg:  your going to handle the other one about 2.0 migration?
[22:40] <micahg> RedSingularity: yes, when the user replies
[22:40] <RedSingularity> micahg: ok
[22:43] <micahg> RedSingularity: nm, I found an upstream bug
[22:44] <micahg> RedSingularity: why did you post an apport-collect message on bug 643736?
[22:44] <ubot2> Launchpad bug 643736 in thunderbird (Ubuntu) (and 1 other project) ""What's new in Thunderbird 3" reappears on minor upgrades (affects: 1) (heat: 8)" [Wishlist,Triaged] https://launchpad.net/bugs/643736
[22:44] <RedSingularity> micahg:  get more info about the system
[22:44] <micahg> RedSingularity: there is no more information
[22:45] <RedSingularity> micahg:  damn, i didnt even notice he used apport to report it at first.
[22:46] <RedSingularity> micahg:  telling him to disregard
[22:48] <RedSingularity> micahg:  you notified mozilla team?
[22:48] <micahg> RedSingularity: huh?
[22:48] <RedSingularity> micahg:  it says assigned to mozilla bugs
[22:48] <micahg> RedSingularity: that means it's linked to an upstream bug
[22:49] <RedSingularity> micahg: alright
[22:49] <RedSingularity> micahg: marking as "wont fix"?
[22:49] <micahg> RedSingularity: huh?
[22:49] <micahg> RedSingularity: I changed my mind as I noted above
[22:50] <RedSingularity> micahg: oh you did link it....ok