[08:07] <ppisati> moin
[08:25]  * smb climbs out of morning mail swamp
[08:25] <smb> morning
[08:28] <apw> moin ...
[10:00] <diwic> apw, hey, I remember you saying your USB mic sometimes showing up as an SPDIF device, is that correct?
[10:01] <diwic> apw, (as well as the ordinary device) in the new sound settings UI
[10:02] <apw> diwic, i suspect you are referring to the snowball i have showing up as two items ...
[10:02] <apw> typically, i am not in the same place as it today :)
[10:02] <diwic> apw hrm
[10:03] <diwic> apw, do you have an alsa-info around where this mic is plugged in?
[10:04]  * smb reminds apw of hassle job... probably too early though. :)
[10:10] <diwic> apw, ok; I'll take the headsets today and when you have it ready, file a bug using "ubuntu-bug audio" and point me to it.
[10:17] <apw> diwic, sorry no, that machine is off at the mo so can't even get to it remotly
[10:18] <apw> diwic, poke me in the morning if i don't get it to you
[10:18] <apw> smb, poking in progress
[10:34]  * ppisati -> brb
[11:59] <ppisati> guys, is there a way to move an archive from one of the builders to zinc?
[12:29]  * ppisati -> out for lunch
[12:47] <kki313> Hi, my notebook (Thinkpad X60) wakes up from suspend2ram while I carry it around (since 11.10, now with 12.04). Its getting pretty hot in its case. Should I file a bug or is this a known bug?
[14:03] <apw> kki313, so the machine definatly sleeps in the first place, and then wakes some time later?  thats unexpectd.  not heard of it, so yes file a bug
[14:12] <herton> ppisati, your Ubuntu-2.6.31-612.34 tag is signed with the wrong key (old key)
[14:14] <herton> smb, ping
[14:14] <smb> herton, what did I wrong?
[14:14] <herton> smb, no, everything is fine :), it's another thing
[14:15] <smb> he ok
[14:15] <smb> shoot
[14:16] <herton> smb, bjf was talking yesterday to me, we will have soon to take 3.2 stable maintenance, we want to see what you're doing with 2.6.32, we could leverage your work with 3.2
[14:17] <ppisati> herton: let me check
[14:18] <smb> herton, Ah ok. Though there is probably not the right things there which you need. Since I basically only followed another stable tree, there was no need to monitor the stable mailing list (actually that was not even possible back then)
[14:19] <smb> herton, So potentially you can re-use the scripts for the mail announcements (need to find out how tightly those are tight into the special work flow)
[14:20] <herton> smb, yes, it'll be different for this case. but there are some common things, we will need a place to hold a 3.2 stable too, and a place for the announcements, perhaps do the same as you do with 2.6.32+drm
[14:21] <ppisati> herton: you are right, repushed
[14:21] <ppisati> herton: check it out
[14:22] <herton> ppisati, cool thanks
[14:23] <smb> herton, Sure, I can let you have a look at the announcment scripts. They will need some tweakign but should be somehow usable. And the tree, it could be on kernel.ubuntu.com or kernel.org. I could host it but I have no doubts that someone of you may also get an account
[14:24] <tgardner> smb, herton: given that the maintenance duties will rotate, lets host it on kernel.ubuntu.com
[14:25] <smb> tgardner, Makes sense and really any place that is public is as good as the other
[14:25] <tgardner> in fact, it could just be a branch in the ubuntu-precise repo
[14:26] <herton> tgardner, hmm, but the branch would track 3.2 pristine, not our master, correct?
[14:26] <tgardner> herton, correct
[14:26] <smb> tgardner, I would probably make it a separate tree just to pointout its independancy
[14:27] <tgardner> smb, actually, making it a branch in ubuntu-precise is a subtle advertisement, hmm?
[14:28] <smb> tgardner, Well I would rather not tread into the same tracks as some other person. :-P
[14:29] <smb> herton, I copied my notify-* scripts (2) to chinstrap as examples. The notify for a release will need some work because it is trying to be smart about a drm33 part.
[14:29] <tgardner> smb, we're gonna get shit whatever we do.
[14:29] <tgardner> so lets do what is most convenient for us
[14:30] <smb> tgardner, Sure thing. I just would like to not act in a certain way just to proof we are ... too.
[14:31] <arges> sforshee, hello
[14:31] <sforshee> arges, hi
[14:31] <arges> sforshee, i see that you fixed something in gnome-desktop3 : [GnomeRR] - Consider Embedded Display Port outputs as the laptop's built-in display
[14:32] <arges> sforshee, how did you hit that bug?
[14:32] <sforshee> arges, yep, that was causing macbook airs to not suspend when the lid was closed
[14:32] <sforshee> you have to have a machine that uses eDP for the internal panel
[14:32] <sforshee> then you just close the lid
[14:33] <arges> sforshee, ok cool. wondering if it was similar to an issue i was seeing
[14:33] <arges> thanks
[14:33] <sforshee> arges, eve if it isn't identical it could be similar
[14:33] <arges> true
[14:33] <sforshee> gnome-settings-daemon was changed to not suspend if it thinks an external display is connected when the lid is closed
[14:34] <sforshee> if that same logic is failing in some other way, you'll get the same results
[14:34] <arges> sforshee, i'm getting some wierd errors when Fn-F7ing on thinkpads on natty, but I know it works on oneiric. I've ruled out the kernel, so I'm thinking gnome-settings-daemon or gnome-desktop
[14:34] <sforshee> Fn-F7 is the suspend hotkey?
[14:35] <arges> swap displays
[14:35] <sforshee> oh
[14:35] <sforshee> have you tried natty kernel to see if it fixes it?
[14:36] <sforshee> i really have no idea what in userspace is handling that hotkey
[14:38] <arges> yea i'll figure it out. I used the same kernel on both natty/oneiric and the oneiric one passed, and the natty one failed. so i'm thinking its a userspace gnome issue
[14:38] <arges> i traced through the i915.debug stuff and found that its actually trying to pass the wrong resolution, so it looks like the kernel is doing what its being told
[14:39] <arges> so i was going through the gnome-desktop3 changelog and saw your name : )
[14:43] <kki313> apw, ok. Do you need special logs?
[14:45] <cking> pgraner, https://wiki.ubuntu.com/Kernel/PowerManagement/PowerSavingTweaks
[15:45]  * ogasawara back in 20
[16:04] <jMCg> http://dpaste.com/713065/
[16:04] <jMCg> This is great.
[16:07] <jMCg> Looks like my PCI thingy is b0rked.
[16:16] <jsalisbury> herton, bjf possible lucid 2.6.32-39.86 regression: bug 949080
[16:16] <ubot2`> Launchpad bug 949080 in linux "sending ioctl 1261 to a partition!" [Medium,Confirmed] https://launchpad.net/bugs/949080
[16:17] <tgardner> jsalisbury, not a regression. its a known (benign) issue
[16:17] <jsalisbury> tgardner, cool, thanks.
[16:20] <jsalisbury> tgardner, thanks, I just found details that they are just probing ioctls.  Updated the bug.
[16:20] <tgardner> jsalisbury, yeah, I get them all the time, especially on dm sets.
[16:55] <tgardner> jsalisbury, why do you think bug #946134 is a kernel issue ?
[16:55] <ubot2`> Launchpad bug 946134 in linux "2.20.1-1ubuntu2 : renice crashed with SIGSEGV in __libc_start_main()" [Medium,Incomplete] https://launchpad.net/bugs/946134
[16:58] <jsalisbury> tgardner, I saw "Crash on cold boot" in the description.  Should it belong in util-linux?
[16:58] <tgardner> jsalisbury, dpkg -S /usr/bin/renice
[16:58] <tgardner> bsdutils: /usr/bin/renice
[16:59] <tgardner> jsalisbury, its a segfault in an application. its not clear that it is a kernel bug, so until then....
[16:59] <jsalisbury> tgardner, ahh, ok.  I'll update the package.
[17:00] <tgardner> jsalisbury, you mean, update the bug with the correct package name ?
[17:00] <jsalisbury> tgardner, yes
[17:02] <jsalisbury> tgardner, I updated the package name in the bug.  Thanks for the info.
[18:12]  * ppisati -> EOD
[18:30] <tgardner> bjf, herton: I pushed a patch Monday to ubuntu-oneiric-meta that needs packaging and uploading.
[18:30] <bjf> tgardner: ack
[18:31] <tgardner> ogasawara, I added the same patch to ubuntu-precise-meta. OK if I just upload it ?
[18:31] <ogasawara> tgardner: yep, go for it
[18:58]  * tgardner -> lunch
[21:15]  * tgardner -> EOD
[21:25] <ohsix> herton: that package showed up as an update a few hours later, i forgot that the index for the releases/types were separate from the files themselves, any idea how often (if periodic) the Packages.gz or whatever is regenerated on ddebs? i suspect that was the only issue
[21:27] <herton> ohsix, I have no Idea as well on the frequency of it, an archive admin may have the answer to it (eg. you can ask pitti on #ubuntu-devel)
[21:28] <ohsix> ah ok, thanks again! :D