[00:00] <layn> bdmurray, are often busy with work and databases, but if I can come next year
[00:12] <hggdh> heh. and I got to meet charlie-tca in person this year...
[00:12] <layn> bdmurray, It was a pleasure to meet you here
[00:13] <layn> bdmurray, I think we bring the same haircut :)
[00:18]  * xnox wishes to go to UDS one day......
[00:27] <layn> bye!
=== fenris is now known as Guest14513
[09:25] <ElPasmo> Hi, I think bug 687684 and bug 688857 should set to Triaged with a Low importance. Anyone can take a look and, if I'm right, do the changes for me please?
[09:25] <ubot2> Launchpad bug 687684 in software-center (Ubuntu) "Authentication dialog does not receive focus when clicking the install button (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/687684
[09:25] <ubot2> Launchpad bug 688857 in software-center (Ubuntu Maverick) (and 1 other project) "Keyboard Shortcut for searchbar in the Software Center (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/688857
[10:01] <ElPasmo> !apport
[10:02] <ubot2> Factoid 'apport' not found
[10:02] <ElPasmo> mmm
[10:42] <bartmon> Hello! I an experiencing an issue on my  laptop which uses Ati r300 kms graphics drivers. Whenever the screensaver is active for a few minutes, my computer will hard-lock. No response from input devices, no response via network (so probably a kernel oops). What is the recommended way of diagnosing this issue?
[11:12] <bartmon> Well if anyone has a response, feel free to answer my question above. I have to go offline now but I will check the irclog later today.
=== bilalakhtar_ is now known as cdbs
[13:29] <njin> Hello to all, simply I don't know at wich package assign this bug 690026
[13:29] <ubot2> Launchpad bug 690026 in ubuntu "Ubuntu Multicast packet bug (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/690026
[14:33] <penguin42> I'm not sure it's a bug; the fact his code works on windows doesn't necessarily mean he's doing it the right way for Linux, and I don't know networking to know where it would be broken
[14:34] <penguin42> either way, I'd say it's a kernel issue
[14:44] <CarlFK>  "making my code listen on INADDR_ANY, then only does it work," makes it sounds like a bug
[14:45] <CarlFK>  Bug #672325   seems to be fixed.  should I close it?
[14:45] <ubot2> Launchpad bug 672325 in netkit-tftp (Ubuntu) "tftp assert failure: *** buffer overflow detected ***: tftp terminated (affects: 2) (dups: 1) (heat: 103)" [Medium,New] https://launchpad.net/bugs/672325
[14:57] <crimsun> CarlFK: if it has been fixed, yes
[15:04] <CarlFK> change to "fix released"?
[15:48] <holstein> to 'file a bug against' something is to type the information into the 'in what package did you find this bug?' field?
=== schmidtm_ is now known as schmidtm
[16:00] <holstein> if someone has a second to look
[16:00] <holstein> https://bugs.launchpad.net/ubuntu/+source/rakarrack/+bug/691937
[16:01] <ubot2> Launchpad bug 691937 in rakarrack (Ubuntu) "bug report for backporting (affects: 1) (heat: 6)" [Undecided,In progress]
[16:01] <holstein> and make sure that seems clear and marked properly
=== erhesrhsrtb54vyh is now known as Elbrus
[18:38] <yofel_> holstein: usually you don't open an ubuntu task for backports, other than that, you should refer to https://help.ubuntu.com/community/UbuntuBackports#Backport%20Process
=== yofel_ is now known as yofel
[18:40] <holstein> yofel: thanks
[18:41] <holstein> im not sure i understand what an 'ubuntu task' is
[18:41] <holstein> but im reading :)
[18:42] <yofel> holstein: you opened a task for rakarrack - but what's there to be done on the ubuntu side? meaning: natty and *-updates?
[18:43] <holstein> i should mark it differently then?
[18:43] <holstein> i wanted to put lucid-backports right there
[18:43] <yofel> well, since the ubuntu package itself won't be touched the ubuntu tsk is Invalid, the lucid-backports task is correct
[18:44] <holstein> prolly something to do with the way i started the filing then
[18:44] <holstein> can i get rid of the 'rakarrack' part now?
[18:45] <bartmon> Hi again! Can anyone answer my question above?
[18:45] <yofel> holstein: well, set the task to 'Invalid' since it's impossible to remove it
[18:45] <holstein> yofel: :/
[18:45] <holstein> cool
[18:45] <holstein> i'll do that, and do better next time :)
[18:47] <holstein> 05:42 < bartmon> Hello! I an experiencing an issue on my  laptop which uses Ati r300 kms graphics drivers. Whenever the  screensaver is active for a few minutes, my computer will hard-lock. No response from input devices, no  response via network (so probably a kernel oops). What is the recommended way of diagnosing this issue?
[18:47] <holstein> bartmon: have you tried other kernels?
[18:47] <yofel> holstein: read the 'how to request new packages' section on the backports page, and don't worry, you're not the only one that doesn't find that page at first..
[18:47] <bartmon> Yes, I tried 2.6.36 from the kernel team and the issue exists on it too.
[18:48] <yofel> bartmon: what about 2.6.37?
[18:48] <bartmon> yofel: Haven't tried it yet as it is still in rc
[18:50] <yofel> I don't know much about debugging kernel issues, but maybe you find something useful here: https://wiki.ubuntu.com/Kernel/Debugging
[18:51] <bartmon> yofel: Thanks, I'll check it out.
[18:57] <vish> yofel: did the magic kernel fix land in .37?
[18:57] <vish> the small patch which is supposed to improve life ;p
[19:01] <bartmon> vish: IIRC it was introduced around rc1 or rc2 so we'll have to wait for 2.6.38
[19:01] <vish> bartmon: hmm, if it is in rc1 or rc2, that means it is already in .37
[19:04] <vish> bartmon: or did you mean, patch was sent at the time .37 was in rc1/rc2 ?
[19:04] <bartmon> vish: yes, that was what i meant
[19:04] <vish> eitherway, there was some talk about cherry-picking the patch for Ubuntu..
[19:05] <bartmon> vish: i'm searching for the press coverage to make it clear
[19:09] <bartmon> vish: Found it. The patch hasn't been nominated for pulling by Linus for .37 as it was still undergoing testing.
[19:10] <vish> bartmon: yea, but we wanted to get it into Natty , so we were going to cherry-pick it.. not sure if it has landed or not yet..
[20:25] <yofel> vish: didn't check, but I think it was pretty short for upstream 37 so I would rather say it'll be in 38
[23:19] <layn> Hi
[23:22] <layn> Good evening all