=== elmo_ is now known as Guest53104 [01:25] hello? [01:25] ANybody there?/ [01:25] Who likes movies? === panda is now known as Guest71075 === smb` is now known as smb === chrisccoulson_ is now known as chrisccoulson [10:52] cking: did you ever use sshfs with any of our builders? [11:14] ppisati, nope [11:18] * cking slips offline- really feeling rough today [12:39] tgardner, hi there, would you mind doing me a favour and install "nano" on tangerine? Still haven't got accustomed to vi ;-) [12:40] tgardner, ah wait, it's just in the chroots there are no nanos [12:40] * diwic takes back the previous question. [12:41] diwic, well, I just installed nano in the normal login. does that work for you? [12:42] tgardner, it seems to work now at least, so thanks! === Guest53104 is now known as elmo === yofel_ is now known as yofel [15:00] bouncing tangerine in 5 [15:25] 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] htorque, hi! thanks for testing the jack detection kernel! [15:26] diwic: thanks for providing one ;-) [15:27] htorque, in short, do you notice any regressions of any input/output when you use the model=auto approach? [15:27] 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] htorque, there are news for realtek machines, but you were having a conexant IIRC, so for you it does not matter [15:28] 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] yeah, it's conexant [15:31] 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 ) [15:32] diwic: do i need to show up at all? i'd prefer not to. ;-) [15:32] htorque, that's ok as well. [15:33] great, thanks for your efforts, jack detection is a really useful feature! :-) [15:40] htorque, sent. http://mailman.alsa-project.org/pipermail/alsa-devel/2012-January/048315.html [15:40] \o/ === bladernr_ is now known as bladernr_afk [16:07] apw, see /var/run/nm-dns-dnsmasq.conf [16:08] tgardner, ok for me it contains ipv4 DNS from my local router, and ipv6 from my tunnel [16:09] apw, right. I guess my point is that its NM thats doing all this. [16:09] tgardner, yeah it used to run /etc/resolv.conf and now does this new file ... hmmm [16:10] apw, well, it still uses /etc/resolv.conf 'cause thats a libresolv thing, right? [16:10] tgardner, i meant it used to write over /etc/resolv.conf and now it writes over this new one [16:11] apw, it still writes the default domain info into /etc/resolv.conf (as I would expect) [16:11] tgardner, ahh i don't have that in mine, but i prolly don't have one [16:12] no matter. I think the reason for the change must be for ipv6 support (as you said earlier). [16:12] yeah perhaps so [16:28] tgardner: any idea if there are plans for cw-3.2 in oneiric? digging around I found a bug filed against lucid [16:28] vanhoof, no plan. leann has only done Lucid LBM. Is there a need ? [16:30] 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] vanhoof, I am coincidentally looking at the ucode updates [16:30] tgardner: would a new bug be preferred or just a series nomination on the existing lucid bug [16:30] tgardner: yeah just saw they were posted friday evening [16:31] vanhoof, new bug I think [16:31] bjf - hi [16:31] brendand: hi [16:31] vanhoof, do you have a need for Maverick or Natty ? [16:32] tgardner: nope, none [16:32] k [16:32] bjf - is the next oneiric kernel in the pipeline soon? [16:32] brendand: yes, why [16:33] bjf - trying to get a rough idea of when we need to test it [16:33] bjf - it's being prepared? [16:34] 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 === bjf is now known as bjf[afk] === bigbash is now known as zz_bigbash === bladernr_afk is now known as bladernr_ [17:42] 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] 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 === bjf[afk] is now known as bjf [19:07] * tgardner --> lunch [19:21] bjf, ok oneiric should be all sorted out [19:22] apw, thanks [19:23] 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] tgardner: want me to do cw-3.2 for oneiric? or have you already started. [19:46] 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] 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] tgardner: ack [19:48] 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] 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] I did more then twitch. it was more of a violent recoil... [19:55] 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] lamont, IIRC there was a stable update patch that prevents div by 0 after 200+ days. herton ? [20:00] bjf, herton doesn't seem to be around. do you remember that one ? [20:00] tgardner: no, i don't remember that [20:00] tgardner: herton is on a swap day [20:01] lamont, is it frequent enough that you can determine when it began ? [20:01] http://paste.ubuntu.com/814622/ <-- tgardner, using 2.6.32-37-server #81-Ubuntu [20:02] next you'll want to know what the kernel rev was before it was rebooted, huh? [20:02] lamont, uh huh [20:03] that'll take a bit more digging [20:03] gaining 2 secs every few minutes seems like a bad thing [20:27] lamont, please start a bug using 'ubuntu-bug linux' and I'll get the stable team looking at it. [20:28] tgardner: let me see how well that works there [20:28] lamont, I suppose its so firewalled it doesn't even know the outside world exists [20:29] The program 'ubuntu-bug' is currently not installed. To run 'ubuntu-bug' please ask your administrator to install the package 'apport' [20:31] lamont, well, we really need the HW and BIOS info, as well as http://paste.ubuntu.com/814622/ attached to the bug. [20:31] tgardner: cool. I'll grab that pile. front end of lshw for the hw/bios info, I expect? [20:32] and then marked as affecting lucid? or just filed against linux/lucid? [20:40] tgardner: bug 920649 [20:40] Launchpad bug 920649 in linux "ntp keeps resetting system time, losing sync" [Undecided,New] https://launchpad.net/bugs/920649 [20:40] lamont, ack [20:42] lamont, you'll probably be asked to run the following from our bug bot: apport-collect 920649 [20:42] jsalisbury: yeah, trying to avoid actually installing apport on that machine. [20:43] so I may need to dig into apport enough to find what that command would actually gather [20:43] lamont, ahh, ok. [20:43] lamont, The following would be helpful if you can't run apport: [20:43] 1) uname -a > uname-a.log [20:43] 2) dmesg > dmesg.log [20:43] 3) sudo lspci -vvnn > lspci-vvnn.log [20:43] 4) cat /proc/version_signature > version.log [21:07] * tgardner -> EOD [22:01] 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] according to teh readme i'd need to do it by executable name... === emma is now known as em