=== jrib1 is now known as jrib [02:44] ugh: why do people set their bug status as new once they respond to questions.. lol [04:34] dtchen: when you have a moment to aid a willing learner in debugging a sound problem, could you take a look at a bug I just reported? bug 344057 [04:34] Launchpad bug 344057 in pulseaudio "cpulimit.c: Received request to terminate due to CPU overload." [Undecided,New] https://launchpad.net/bugs/344057 === sdh_ is now known as sdh [05:19] hi all [05:20] anybody here? [05:21] bdmurray, r u there? [05:21] bdmurray, I need help. my ubuntu-bugs membership is expiring [05:40] dtchen: disregard that last comment on the bug for a member, I messed (forgot to uncomment that line) [05:40] s/member/moment [05:43] dtchen: now disregard my above statement, I uncommented that line and the same thing happened [05:44] dtchen: go by the bug report, it is now (back to being) right [06:31] good morning [07:04] good morning [08:42] good morning [09:09] guud morning === pedro__ is now known as pedro_ [14:17] Boo [14:31] fooooo [14:32] * BUGabundo makes smoke signals: puff puff puffff puff [15:05] hi [15:06] if someone has submitted a bug that has been fixed upstream, how should i triage the bug? Do is set confirmed and then add a link to the upstream dist showing it as fixed? [15:07] If it is not fixed in ubuntu yet, it should be fix-committed, and a comment that it is fixed upstream [15:09] per https://wiki.ubuntu.com/Bugs/Status [15:11] ok will do that. it's fixed in debian, so will this situation either require a package sync from debian or a patch to the ubuntu package? [15:15] If it is a package in use, it should sync automatically, I think. I am not sure, though [15:16] Most of the time, as a triager, you don't have to request the sync, it just happens, to the best of my knowledge [15:17] ok thanks. new to all this stuff so just trying to understand the processes. [15:19] charlie-tca: aren't we past auto syncs? [15:25] i know we are past DebianFreeze and FeatureFreeze, but i am guessing you can get a sync done at this point for bug fixes? [15:26] BUGabundo: autosyncs, yes. But we can do manual sync [15:26] mcnicholls: yeah, generally yes. [15:26] I am less familiar with the sync process and would have to read the wiki pages myself. [15:27] https://wiki.ubuntu.com/SyncRequestProcess [15:27] mcnicholls: that will help ^ [16:20] greg-g: thanks for that. will have a read. === fader is now known as fader|lunch === tcole1 is now known as tcole === fader|lunch is now known as fader === bcurtiswx1 is now known as bcurtiswx-mini === warp10 is now known as gaspa2 === gaspa2 is now known as warp10 [18:28] seb128: do you know the dupe for bug 344424? I can't seem to find it [18:28] Launchpad bug 344424 in nautilus "new nautilus windows don't take focus" [Low,Invalid] https://launchpad.net/bugs/344424 [18:28] partly because going to a bug listing on LP causes Xorg to consume 100% cpu for me [18:29] mrooney: bug #333366 [18:29] Launchpad bug 333366 in nautilus "new nautilus window stays in background" [Unknown,Confirmed] https://launchpad.net/bugs/333366 [18:29] seb128: thank you sir! [18:29] you're welcome [19:01] mrooney - just seen your response in bug 344385 [19:01] Launchpad bug 344385 in notify-osd "Brightness notification works only with Human Icons " [Medium,Confirmed] https://launchpad.net/bugs/344385 [19:01] I've got a problem and I don't know where to drop it, but Intrepid for amd64 has a memory leak [19:02] ... and it's most-likely a kernel leak [19:02] would you mind copying the icons from the Human theme in to /usr/share/notify-osd/icons, just to see if it works then (with a non human theme)? [19:02] remember to back up the directory first [19:02] don't want you breaking your system ;) [19:03] Depending on the size of the block being allocated, the system will consume all RAM and swap. It also refuses to shut down properly. [19:05] I first noticed the problem while running VBox. The host system ram and swap would be all but completely consumed in under 3 hours. [19:05] Shutting down Vbox would leave a zombie. Even killing the parent process didn't help as init is unable to kill this zombie either. [19:06] Not running VB, it takes about a day to consume all of RAM and 1/2 of swap just using regular applications. [19:07] But the end result is the same, the system cannot be shut down properly. Even X will not completely close down. You're left with wallpaper and a mouse that doesn't move, and a frozen keyboard. [19:09] anyone got any idea how to work around this? It is really hindering my workflow (not to mention ruining a perfectly good uptime). [19:19] chrisccoulson: okay, back now, I'll try that [19:23] Hello, had a question about bug status: If a bug has been confirmed by a person other than the reporter, should I change the status to confirmed? [19:25] adelie42: which bug? [19:26] Arkain: I would first look for an existing bug, then if you can't find one, file it [19:26] further, in attempting to hunt down new bugs, I keep coming by many reports marked as 'new' and have patches uploaded. I don't know how this would work otherwise, but of there are several patches for a package, would it be useful to branch, apply, test, and merge? [19:26] Arkain: if you think it has a fair amount of info, you could link to it in #ubuntu-devel and see if anyone has an idea [19:26] Just in general, but I can find one in just a moment... [19:27] adelie42: well if you can't confirm the bug it won't help to test the patch [19:27] chrisccoulson: where ARE the human theme icons? [19:27] adelie42: refer to https://wiki.ubuntu.com/Bugs/PatchTesting [19:27] good question [19:28] mrooney: I am looking for new bugs I think I can fix, but I keep coming by bugs that are marked as 'new' but confirmed and contain patches in the comments. Is there something I can do more useful than ignore these threads [19:28] in /usr/share/icons/Human/scalable/status, is suspect [19:28] adelie42: typically if there are confirmations from other users then the poster, we mark as confirmed [19:29] adelie42: if someone else confirms it and it actually seems like a real confirmation (not a bug saying, my system freezes and someone else saying me too, that probably isn't the same issue :) then I would Confirm it, and you can ask if they'd be willing to test a patched version [19:29] 'we' being the collective...? [19:29] adelie42: and if they say yes you could patch it and put up a PPA [19:30] adelie42: we are the ubuntu, you will be assimilated, resistance if futile [19:30] is* [19:31] ok, that 'patchtesting' page looks like it answers the questions I had. [19:31] adelie42: great!, anything else we can help you with today? [19:32] mrooney: and no, I wasn't thinking comments like 'yeah, me too', more like "I saw the same thing, heres a screen shot, why hasn't this been fixed yet?" kind of comments followed by a patch. [19:33] adelie42: yeah those are good to confirm, and get a confirmation that the patch works [19:33] bcurtiswx-mini: Well, how about you give yourself a pat on the back because I was just a lowly solo hobby programmer in love with Ubuntu a week ago, and now feeling mire fully assimilated, so THANK YOU! [19:34] more* [19:34] bdmurray: would the eventual formation of a patch-testing team be possible? [19:35] adelie42: are you interested in helping to test patches posted in launchpad? [19:35] Does anyone else feel that maybe the reason there isn't a lot of demand for video games on Linux is because it is too much fun hunting and patching bugs, or is it just me? [19:35] adelie42: haha [19:35] bcurtiswx-mini: very muh so, my first merge was approved this morning from my work all weekend, and a second still pending approval [19:36] adelie42: you would be a very beneficial addition to the team (once i can get one set up) [19:36] chrisccoulson: hmm there is notification-display-brightness-* and notification-keyboard-brightness-* [19:37] are there notifications for pidgin on the notify-osd yet? [19:37] I am still getting used to the code guidelines / format of things, so I have been mostly handling spelling and translation errors to have something useful to do while reading through code and getting more comfortable with the bzr way of doing things [19:37] bcurtiswx-mini: eventually but I rather see it start off being part of the bugsquad and talked about there [19:38] bdmurray: sounds great to me ! [19:38] perhaps it is the keyboard-brightness ones that are missing mrooney? [19:39] chrisccoulson: hmm nothing seems to be working [19:39] I shouldn't have to restart anything right? [19:40] i'm not sure then. i don't know the notify-osd code well enough. you could try restarting perhaps [19:40] the notifications definately work with human theme don't they? [19:40] bcurtiswx-mini: but I look forward to joining a team in the near future as I become more comfortable with things. Thanks for the patchtesting link. I think I got my work cut out for me today. Thanks again. [19:40] chrisccoulson: let me right click and "change desktop background" to tell you :) [19:40] what a poorly named thing [19:40] adelie42: glad i was of some help [19:41] chrisccoulson: yeah switching icons to Human works instantly [19:41] i see on the wiki that pidgin does link with the notify-osd, but its not working on my machine... is there a special package i have to dl? [19:41] i'm not so sure then. i can maybe take another look later, but i have to disappear for dinner shortly [19:46] chrisccoulson: okay, I'll add a comment with what I've done === erhesrhsrtb54vyh is now known as Elbrus [22:38] Launchpad should really make you super confirm filing a bug with an identical title as one you submitted less than 5 minutes ago [22:39] super confirm? [22:39] confirm again I suppose [22:40] are you sure? really sure? I mean.. ... Really sure? [22:41] greg-g: your comments are a bit confusing [22:42] greg-g: should i deem your comments in bug 344057 valid or not? [22:42] Launchpad bug 344057 in pulseaudio "cpulimit.c: Received request to terminate due to CPU overload." [Undecided,Confirmed] https://launchpad.net/bugs/344057 === asac_ is now known as asac