[01:25] <Anon783> hello?
[01:25] <Anon783> ANybody there?/
[01:25] <Anon783> Who likes movies?
[10:52] <ppisati> cking: did you ever use sshfs with any of our builders?
[11:14] <cking> ppisati, nope
[11:18]  * cking slips offline- really feeling rough today
[12:39] <diwic> tgardner, hi there, would you mind doing me a favour and install "nano" on tangerine? Still haven't got accustomed to vi ;-)
[12:40] <diwic> tgardner, ah wait, it's just in the chroots there are no nanos
[12:40]  * diwic takes back the previous question.
[12:41] <tgardner> diwic, well, I just installed nano in the normal login. does that work for you?
[12:42] <diwic> tgardner, it seems to work now at least, so thanks!
[15:00] <tgardner> bouncing tangerine in 5
[15:25] <htorque> diwic: hi! what's new in your latest jack detection kernel (i.e., should we re-test)? and: what's the default value for 'model' parameter? if i don't set it to 'auto', jack detection doesn't work on my thinkpad.
[15:26] <diwic> htorque, hi! thanks for testing the jack detection kernel!
[15:26] <htorque> diwic: thanks for providing one ;-)
[15:27] <diwic> htorque, in short, do you notice any regressions of any input/output when you use the model=auto approach?
[15:27] <diwic> htorque, in short, model=auto is the future, so we would like to move as many machines as possible over to using model=auto
[15:28] <diwic> htorque, there are news for realtek machines, but you were having a conexant IIRC, so for you it does not matter
[15:28] <htorque> diwic: no, but i don't use any fancy stuff like audio over hdmi and alike. mic works, sound from the speakers work, sound from the headphone works, PA is not acting up - i'm happy with it. :)
[15:29]  * diwic looks at htorque's alsa-info
[15:29] <htorque> yeah, it's conexant
[15:31] <diwic> htorque, cool, I'll submit a patch upstream to move your machine over to model=auto. How would you like to be credited in the patch (something like Tested-by: John Doe <john@doe.com> )
[15:32] <htorque> diwic: do i need to show up at all? i'd prefer not to. ;-)
[15:32] <diwic> htorque, that's ok as well.
[15:33] <htorque> great, thanks for your efforts, jack detection is a really useful feature! :-)
[15:40] <diwic> htorque, sent. http://mailman.alsa-project.org/pipermail/alsa-devel/2012-January/048315.html
[15:40] <htorque> \o/
[16:07] <tgardner> apw, see /var/run/nm-dns-dnsmasq.conf
[16:08] <apw> tgardner, ok for me it contains ipv4 DNS from my local router, and ipv6 from my tunnel
[16:09] <tgardner> apw, right. I guess my point is that its NM thats doing all this.
[16:09] <apw> tgardner, yeah it used to run /etc/resolv.conf and now does this new file ... hmmm
[16:10] <tgardner> apw, well, it still uses /etc/resolv.conf 'cause thats a libresolv thing, right? 
[16:10] <apw> tgardner, i meant it used to write over /etc/resolv.conf and now it writes over this new one
[16:11] <tgardner> apw, it still writes the default domain info into /etc/resolv.conf (as I would expect)
[16:11] <apw> tgardner, ahh i don't have that in mine, but i prolly don't have one
[16:12] <tgardner> no matter. I think the reason for the change must be for ipv6 support (as you said earlier).
[16:12] <apw> yeah perhaps so
[16:28] <vanhoof> tgardner: any idea if there are plans for cw-3.2 in oneiric?  digging around I found a bug filed against lucid
[16:28] <tgardner> vanhoof, no plan. leann has only done Lucid LBM. Is there a need ?
[16:30] <vanhoof> tgardner: there is, new uCode just landed for the 6235, 2200, 2230, 105, and 135 series cards, which are all supported in 3.2 
[16:30] <tgardner> vanhoof, I am coincidentally looking at the ucode updates
[16:30] <vanhoof> tgardner: would a new bug be preferred or just a series nomination on the existing lucid bug
[16:30] <vanhoof> tgardner: yeah just saw they were posted friday evening
[16:31] <tgardner> vanhoof, new bug I think
[16:31] <brendand> bjf - hi
[16:31] <bjf> brendand: hi
[16:31] <tgardner> vanhoof, do you have a need for Maverick or Natty ?
[16:32] <vanhoof> tgardner: nope, none
[16:32] <tgardner> k
[16:32] <brendand> bjf - is the next oneiric kernel in the pipeline soon?
[16:32] <bjf> brendand: yes, why
[16:33] <brendand> bjf - trying to get a rough idea of when we need to test it
[16:33] <brendand> bjf - it's being prepared?
[16:34] <bjf> brendand: if you look at the interlock schedule, it shows that this week is a "prep" week, next week will be verification and the following regression testing
[17:42] <borudev> Hello, how is everyone? I had a quick question troubleshooting my ubuntu 11.10 server installation. I installed the same OS on 2 different servers and I'm experiencing the same problem. What happens is I turn on the server, it's ok for few hours, and then when I try to SSH to it, it get a time out, when I plug in the keyboard, and type something then I can connect to it again. Seems that 
[17:42] <borudev> it's going to some kind of sleep mode. Note, no desktop was installed just pure server OS. Anyone had this issue before? what could cause it? Thanks
[19:07]  * tgardner --> lunch
[19:21] <apw> bjf, ok oneiric should be all sorted out
[19:22] <bjf> apw, thanks
[19:23] <apw> borudev, i have not seen that on any of my servers.  the default for suspend after a bit did change due to the fixing of a bug somewhere, but i thought that was in gnome somewhere
[19:45] <ogasawara> tgardner: want me to do cw-3.2 for oneiric? or have you already started.
[19:46] <tgardner> ogasawara, that would would be great. I just uploaded linux-firmware for precise, so we need to think about getting those firmware bits into oneiric.
[19:47] <tgardner> I'm gonna ask if dropping Precise linux-firmware into Lucid/Oneiric -backports is appropriate. if so, then I'll have you add an install dependency on CW-3.2
[19:47] <ogasawara> tgardner: ack
[19:48] <ogasawara> tgardner: I also saw 3.3-rc1 is out.  I started prepping the Q repo on thursday before I bailed, so I'll try and get that finished up in the next day or so as well.
[19:49] <tgardner> ogasawara, cool. I also messed with a bit, but lost interest after grinding through a bazillion new config options
[19:49]  * ogasawara twitches at the thought of more config review
[19:50] <tgardner> I did more then twitch. it was more of a violent recoil...
[19:55] <lamont> did we possibly mess around with tickspersec or other time related stuff in lucid?  I have some wierd ntp behavior that I'm seeing
[19:59] <tgardner> lamont, IIRC there was a stable update patch that prevents div by 0 after 200+ days. herton ?
[20:00] <tgardner> bjf, herton doesn't seem to be around. do you remember that one ?
[20:00] <bjf> tgardner: no, i don't remember that
[20:00] <bjf> tgardner: herton is on a swap day
[20:01] <tgardner> lamont, is it frequent enough that you can determine when it began ?
[20:01] <lamont> http://paste.ubuntu.com/814622/ <-- tgardner, using  2.6.32-37-server #81-Ubuntu
[20:02] <lamont> next you'll want to know what the kernel rev was before it was rebooted, huh?
[20:02] <tgardner> lamont, uh huh
[20:03] <lamont> that'll take a bit more digging
[20:03] <tgardner> gaining 2 secs every few minutes seems like a bad thing
[20:27] <tgardner> lamont, please start a bug using 'ubuntu-bug linux' and I'll get the stable team looking at it.
[20:28] <lamont> tgardner: let me see how well that works there
[20:28] <tgardner> lamont, I suppose its so firewalled it doesn't even know the outside world exists
[20:29] <lamont> The program 'ubuntu-bug' is currently not installed.  To run 'ubuntu-bug' please ask your administrator to install the package 'apport'
[20:31] <tgardner> lamont, well, we really need the HW and BIOS info, as well as http://paste.ubuntu.com/814622/ attached to the bug.
[20:31] <lamont> tgardner: cool.  I'll grab that pile.  front end of lshw for the hw/bios info, I expect?
[20:32] <lamont> and then marked as affecting lucid? or just filed against linux/lucid?
[20:40] <lamont> tgardner: bug 920649
[20:40] <ubot2> Launchpad bug 920649 in linux "ntp keeps resetting system time, losing sync" [Undecided,New] https://launchpad.net/bugs/920649
[20:40] <tgardner> lamont, ack
[20:42] <jsalisbury> lamont, you'll probably be asked to run the following from our bug bot: apport-collect 920649
[20:42] <lamont> jsalisbury: yeah, trying to avoid actually installing apport on that machine.
[20:43] <lamont> so I may need to dig into apport enough to find what that command would actually gather
[20:43] <jsalisbury> lamont, ahh, ok.
[20:43] <jsalisbury> lamont, The following would be helpful if you can't run apport:
[20:43] <jsalisbury> 1) uname -a > uname-a.log 
[20:43] <jsalisbury> 2) dmesg > dmesg.log 
[20:43] <jsalisbury> 3) sudo lspci -vvnn > lspci-vvnn.log 
[20:43] <jsalisbury> 4) cat /proc/version_signature > version.log 
[21:07]  * tgardner -> EOD
[22:01] <hallyn> is it possible to use /etc/apport/blacklist.d/ to blacklist kernel oopses?  (i get a ton of in_atomic ones.  apport won't let me report them anyway. sick of popups)
[22:01] <hallyn> according to teh readme i'd need to do it by executable name...