[00:13] <jjohansen> hggdh: confirmed
[00:15] <hggdh> jjohansen: should I open a bug for that?
[00:16] <jjohansen> hggdh: no not yet, I'll poke at it or at the least poke smb when he comes on
[00:17] <hggdh> jjohansen: thank you
[00:30] <broder> so now that i've grabbed the stacktrace, is there anything i can do to help with the debugging of bug 784335?
[00:30] <ubot2> Launchpad bug 784335 in linux "Heavy network utilization with r8169 leads to kernel panic" [Undecided,Confirmed] https://launchpad.net/bugs/784335
[00:33] <jj-afk> back on later
[04:37] <bAdGigabit> Dose the current kernel support packet injection?
[04:37] <bAdGigabit> more specific. Will it support it for the ath9k drivers?
[04:49] <bAdGigabit> sorry, did anyone reply?
[05:05] <bAdGigabit> sorry, i kewp getting disconneted
[05:05] <bAdGigabit> any awnsers that i missed?
[08:28]  * apw yawns
[08:30] <jk-> hey apw & smb
[08:30] <apw> moin jk-
[08:31] <smb> morning jk-
[09:04] <eagles0513875> morning apw :D
[09:06] <valorie> hi all, since I upgraded to 11.04, my mic jack no longer works
[09:06] <valorie> I searched the bugs, but didn't find anyone else reporting this
[09:06] <valorie> what do i need to do to report a useful bug?
[09:08] <apw> eagles0513875, hi
[09:08] <eagles0513875> how goes it apw
[09:08] <apw> valorie, thinking
[09:09] <valorie> eagles0513875 suggested I ask here
[09:09] <apw> smb, can you remember what we file sound bugs against, alsa something something
[09:09] <eagles0513875> apw: it was my suggestion to have her ask here as we thought it might be a kernel issue
[09:09] <eagles0513875> me im kinda having a similar issue with usb webcam with mic and pulse audio
[09:09] <valorie> mic doesn't work either, but it never has
[09:09] <smb> apw, Something like that... could it be alsa-driver or so?
[09:09] <valorie> I think
[09:10] <apw> very likely a kernel issue, and reporting it against the right package is the key
[09:10] <apw> and before my first coffee i can't think what its called
[09:10] <eagles0513875> apw: should we have her try the proposed 38-9 kernel
[09:10] <valorie> I'll be around for another hour or so
[09:10] <awilkins> valorie, Do you know what sound hardware you're using?
[09:10]  * valorie serves coffee around the chan
[09:10] <apw> awilkins, i was just going to mention your fix
[09:11]  * awilkins grins
[09:11] <eagles0513875> im wondering if his fix woudl apply to usb webcams that have mics then again im not sure what that fix is
[09:11] <valorie> not off the top of my head
[09:11] <awilkins> Probably not to a USB webcam with integrated mic
[09:11] <valorie> what's the command to find out?
[09:11] <eagles0513875> valorie: a simple lspci should tell ya
[09:11] <eagles0513875> mines a Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
[09:11] <eagles0513875>
[09:11] <eagles0513875> valorie: lspci on command line and find the line that says audio :D
[09:12] <eagles0513875> i think before it worked with my other motherboard which had a realtek audio chipset this has an intel one : (
[09:12] <apw> valorie, i think its "ubuntu-bug audio"
[09:12] <valorie> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
[09:12]  * apw thinks people have been chanigng things on us
[09:12] <valorie> 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
[09:12] <awilkins> Intel HDA... so that might be affected by that fix
[09:13] <awilkins> Intel HDA is an abstraction for a bunch of different chipsets from what I can gather
[09:13] <apw> awilkins, your change was to the codec side wasn't it ?  remember which one?
[09:13] <awilkins> AD1988
[09:13] <awilkins> valorie, Do us a   `dmesg | grep hda`
[09:13] <awilkins> And tell us what the line with hda_codec says
[09:14] <eagles0513875> valorie: did you check ur settings in the bios
[09:14] <eagles0513875> if you dont have it set to use hd you need to
[09:15] <valorie> http://paste.ubuntu.com/612193
[09:15] <valorie> no line with hda_codec
[09:15] <valorie> how do I check the setting in the bios?
[09:16] <valorie> I've done that before, but years ago
[09:16] <awilkins> valorie, You'd have to play that by ear - reboot, watch your power up messages for the key for "setup", and hunt around in your menus
[09:16] <eagles0513875> ya
[09:16] <awilkins> BIOS setup usually requires you to make an affirmative choice to save settings also
[09:17] <eagles0513875> i checked my bios and i dont have any settings in mine
[09:17] <eagles0513875> this is hopefully a temp motherboard i have
[09:17] <eagles0513875> till i rma my higher end motherboard
[09:17] <awilkins> But there are too many nonstandard variants for us to walk you through it, probably in the "PCI devices" area
[09:17] <eagles0513875> actually im thinking my issue is more with skype itself
[09:17] <valorie> well, this is my laptop/work/main computer
[09:17] <eagles0513875> cuz i use mumble
[09:17] <eagles0513875> and my mic works just fine :(
[09:18] <valorie> oh weird
[09:18] <eagles0513875> ya
[09:18] <eagles0513875> i know
[09:18] <valorie> well, skype used to work
[09:18] <eagles0513875> i know
[09:18] <valorie> now the mic doesn't
[09:18] <eagles0513875> valorie: sme issue
[09:18] <eagles0513875> same*
[09:18] <valorie> but I don't remember if that was a different lappy or this one
[09:18] <eagles0513875> apw: who would we need to contact to report this as skype is in the ubuntu partner repo
[09:18] <valorie> BUT: soundrecorder doesn't work either
[09:18] <valorie> eagles0513875: HA!
[09:18] <valorie> like Microsoft will care
[09:18] <eagles0513875> the funny thing
[09:19] <eagles0513875> the older static libs on the skype site work just fine
[09:19] <eagles0513875> even the version in 10.10 worked
[09:19]  * eagles0513875 needs to develop an alternative to skype before it gets destroyed
[09:19] <awilkins> Skype works just fine on pulse now
[09:19] <valorie> skype hasn't worked for me for at least the last 3 versions of kubuntu
[09:19] <eagles0513875> awilkins: i have no mic input
[09:19] <valorie> but I've not had a problems with the headphones for a long, long time
[09:19] <eagles0513875> it works fine but no mic
[09:20] <eagles0513875> awilkins: how did you manage to get it to work
[09:20] <valorie> jack worked until upgrade, and then it didn't
[09:20] <awilkins> eagles0513875, Neither did I - previously suffered from #593018, then from #776964
[09:21] <eagles0513875> skype says to go into the pulseaudio settings and i have no idea where those are
[09:21] <valorie> veromix will do it
[09:21] <awilkins> valorie, I had the same thing - but before I had to flip-flop the input selector to get the mic working, but then it stopped
[09:21] <eagles0513875> awilkins: its saying i have to use the local mixer to adjust settings but kmix doesnt have my cam mic listed
[09:21] <valorie> or pavucontrol
[09:22] <valorie> eagles0513875: does alsamixer have it listed?
[09:22] <awilkins> eagles0513875, Well, it sounds like the driver for your cam mic isn't working, or isn't present
[09:22] <eagles0513875> in kmix my logitech quick cam is listed
[09:22] <valorie> sec
[09:22] <awilkins> valorie, Since your hardware previously worked, more chance of working out what's wrong
[09:24] <eagles0513875> skype is bugged
[09:24] <eagles0513875> i installed pavucontrol and mic is picking up sound there
[09:24] <eagles0513875> skype for some reason isnt
[09:25] <awilkins> Which version of Skype? I'm presuming latest
[09:25] <awilkins> Specifically, I have 2.2 beta and it works fine with GNOME / Pulseaudio.
[09:26] <awilkins> If you can record sound from your mic, eagles0513875, it's not really a kernel problem, and I would suggest you'd have more luck in a channel devoted to userland software.
[09:26] <eagles0513875> ya
[09:26] <eagles0513875> awilkins: version of skype taht is in the partner repo
[09:27] <awilkins> eagles0513875, AFAIK that's the same as the one straight from the skype website. Mine says <IP_ADDRESS> in it's "About" box
[09:27] <eagles0513875> ya
[09:27] <eagles0513875> might uninstall it
[09:28] <eagles0513875> and use the static package from the site
[09:29] <valorie> yay, you got your sound working though!
[09:29] <awilkins> eagles0513875, Try cleaning out it's settings first, move the ~/.Skype folder out of the way, start it up, and try a test call
[09:29] <valorie> I don't have time to restart tonight, but tomorrow when I start up, I'll look in the bios and see if I find anything suspicious
[09:30] <awilkins> valorie, The other tool I found useful was  http://www.alsa-project.org/main/index.php/HDA_Analyzer
[09:30] <awilkins> valorie, That lets you mess directly with the codec parameters
[09:31] <awilkins> valorie, In my case, my mic input pin was not set up right - it needed it's VREF setting to be 80, but the driver wasn't initializing it correctly
[09:31] <awilkins> See : https://bugs.launchpad.net/ubuntu/natty/+source/linux/+bug/776964
[09:31] <ubot2> Launchpad bug 776964 in linux "p5n32e-plus HDA Nvidia AD1988B microphone input not working" [Low,In progress]
[09:32] <eagles0513875> awilkins: still nothing
[09:32] <eagles0513875> i dont have time to hack at this right now
[09:32] <awilkins> valorie, We've not really discovered what your sound hardware is yet - HDA Intel hides a bunch of implementations and your dmesg didn't tell us what it was either
[09:33] <awilkins> That tool will probably be more informative, at least
[09:33] <valorie> any way to dig deeper?
[09:33] <awilkins> http://www.alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA
[09:33] <valorie> oh, hda analyzer
[09:33] <valorie> which is a script to run
[09:33] <awilkins> Yes, you have to run it as root
[09:33]  * eagles0513875 wants my original motherboard back so badly
[09:33] <awilkins> sudo python run.py
[09:33] <valorie> not sure I can make heads or tails of it
[09:33] <eagles0513875> my original motherboard works so much better then this one
[09:34] <eagles0513875> would probably require a linux reinstall though :(
[09:34] <valorie> I'm a writer, not a devel
[09:34] <awilkins> valorie, It just gives you direct access to all those little switches that you see in a recording studio
[09:34] <awilkins> valorie, Instead of one big volume knob
[09:35] <eagles0513875> awilkins: usually i stick with the nvidia nforce chipsets
[09:35] <eagles0513875> those have realtek which i have never had any issues with
[09:35] <eagles0513875> not to mention i can use fully my 5.1 atm down to 2.1 with this motherboard
[09:35] <awilkins> eagles0513875, I have an nforce, but my sound is an Analog Devices
[09:36] <eagles0513875> would love to take advantage of the spdif the other motherboard has
[09:39] <awilkins> valorie, If you have HDAAnalyzer running, what's the name on the first AUD_OUT device?
[09:41] <apw> awilkins, this thing should be packaged and installed by default
[09:42] <awilkins> apw, The HDAAnalyzer thing downloads components of itself, but I suppose you could install the bootstrap script. I would guess that
[09:42] <apw> i think i would be happier if someone packaged the bits
[09:42] <apw> as its a bit scarey to download some random stuff and run it as root
[09:42] <awilkins> I would guess that HDA Intel is probably responsible for quite a few bugs because of the myriad of implementations
[09:43] <awilkins> But the actual implementation inside seems to hide well
[09:44] <awilkins> lspci for me does not reflect that the codec is an AD1988B, neither does HDAAnalyzer either, to be true
[09:44] <awilkins> Apart from some of the node names
[09:44] <diwic> for HDAanalyzer, just download snd-hda-tools from ppa:diwic/ppa and run "sudo hda_analyzer"
[09:45] <awilkins> dmesg reports it, but valorie doesn't seem to have that so maybe there is an inconsistent level of logging in the various codec implementations in the drivers
[09:45] <valorie> oh, rather that wgetting it?
[09:45] <valorie> I was opening the /proc/asound/card0/ and looking at it
[09:45] <diwic> valorie, yeah, I packaged it and a few other hda tools up
[09:45] <diwic> (i e if you were asking me)
[09:46] <awilkins> valorie, The first line of /proc/asound/card0/codec#0 seems to be the information we seek
[09:46] <awilkins> At least, in my case
[09:47] <valorie> Codec: IDT 92HD71B7X
[09:47] <awilkins> On the plus side, that's marvellously specific
[09:47] <awilkins> On the downside, it's not the thing we have recently fixed
[09:48] <valorie> snd-tools is installing
[09:48] <awilkins> So it worked in Maverick but not Natty?
[09:48] <valorie> yes
[09:48] <valorie> ok, what do you need from that analyzer?
[09:49] <awilkins> valorie, I can't think of anything specific... but what you can do is try to find your Mic input pin
[09:49] <awilkins> So you should have a bunch of PIN nodes
[09:49] <valorie> in node editor, or text dump?
[09:49] <awilkins> Node editor
[09:49] <awilkins> On the left in the tree there are a bunch of PIN nodes
[09:50] <valorie> oooh
[09:50] <awilkins> If you look in the Config default section on the right, you will see some description of each node
[09:50] <awilkins> Find the one your Mic is plugged into
[09:50] <valorie> Press Detect
[09:50] <valorie> Headphone Drive
[09:50] <valorie> Output
[09:50] <valorie> first pin
[09:50] <awilkins> I found the "Jack color" and "Jack location" bits helpful locating it
[09:51] <valorie> mic jack is pink!
[09:51] <awilkins> e.g. mine is PIN 0x17  Jack type : Mic  Jack location : Ext Jack location2 : Rear
[09:51] <awilkins> That's the one
[09:51] <awilkins> What's it's Wiget control section say?
[09:52] <valorie> boxes are all unchecked
[09:52] <valorie> VREF HIZ below that
[09:52] <awilkins> Ok, check "IN" and change the VREF to 80
[09:52] <valorie> done
[09:53] <valorie> I think that's the jack for an external mic
[09:53] <awilkins> Now open Sound recorder or something with a VU meter (  `pavumeter --record` ) and try it out
[09:53] <valorie> let me get one
[09:53] <valorie> or I guess I can use my headphones
[09:53] <awilkins> Ah, what' the input for the Mic you are actually using
[09:53] <awilkins> That one was probably not initialized if you weren't using it on purpose
[09:54] <awilkins> Esp. if it has "input sense"
[09:54] <valorie> I was trying to get the internal mic working
[09:54] <awilkins> Probably another pin
[09:54] <valorie> Press Detect
[09:54] <valorie> Input
[09:54] <valorie> VREF_HIZ
[09:54] <valorie> VREF_50
[09:54] <valorie> VREF_GRD
[09:54] <valorie> VREF_80
[09:54] <valorie> but it would be cool to get this one working too
[09:55] <apw> internal mics are sometimes on the same plug as the external and connected when the jack is not
[09:55] <awilkins> True, you might want to try that VU meter anyway
[09:55] <valorie> did, and nothing
[09:56] <valorie> just dead
[09:56] <valorie> ok, another pin
[09:56] <diwic> valorie, btw, regardless if you get somewhere or not, will you file a bug (unless you already did) for it, e g "using ubuntu-bug audio"?
[09:56] <diwic> thanks!
[09:57] <awilkins> Pins are just the start, alas, the whole chain of things has to work.... I found the thing that draws an SVG diagram of your codec useful
[09:57] <valorie> Jack connection: Fixed
[09:57] <valorie> Jack type:       Mic
[09:57] <diwic> awilkins, codecgraph is also packaged in snd-hda-tools
[09:57] <valorie> Jack location:   Ext
[09:57] <valorie> Jack location2:  Top
[09:57] <valorie> Jack connector:  Digital
[09:57] <valorie> Jack color:      Black
[09:57] <valorie> No presence
[09:57] <valorie> is another
[09:57] <awilkins> And I was already reasonably familiar with the control set on my codec because I had to monkey around with the selectors to get it to work with Maverick
[09:57] <valorie> well, I will file one, but I wanted decent details
[09:57] <valorie> "it doesn't work" isn't very helpful
[09:57] <awilkins> valorie, That one is probably an audio out
[09:58] <valorie> Stereo
[09:58] <valorie> Output Amplifier
[09:58] <valorie> you're right
[09:58] <awilkins> You want ones that have the PIN cap "Input"
[09:58] <diwic> valorie, that's great although "ubuntu-bug audio" will include some relevant files that can help us analyze the problem
[09:58] <apw> diwic, do you use hda analyser ?
[09:59] <diwic> apw, sometimes, yes
[09:59] <apw> diwic, next time we are in the same place, you have to show us how to interterpret its output
[09:59] <valorie> Jack connection: Jack
[09:59] <valorie> Jack type:       HP Out
[09:59] <valorie> Jack location:   Ext
[09:59] <valorie> Jack location2:  Front
[09:59] <valorie> Jack connector:  1/8
[09:59] <awilkins> Headphones out
[09:59] <valorie> Jack color:      Green
[09:59] <valorie> is headphones
[10:00] <valorie> Headphone Drive
[10:00] <valorie> Output
[10:00] <diwic> apw, maybe it's time for another audio triaging session
[10:00] <valorie> widget control has nothing selected
[10:00] <diwic> apw, I saw JFo wanted more of that as well
[10:00] <awilkins> valorie, Paste the contents of your /proc/asound/card0/codec#0 file to the pastebin
[10:00] <apw> diwic, yeah i'd like to listen in on one again, there is more tooling now than i remember
[10:01] <diwic> apw, we could do one hda driver specific
[10:01] <apw> yeah, as that is our primary pain point
[10:01] <valorie> http://paste.ubuntu.com/612205
[10:01] <awilkins> valorie, I think node 0x18 is your baby
[10:02] <awilkins> valorie, Select node 0x18 and check the VREF value
[10:02] <valorie> Jack connection: Fixed
[10:02] <valorie> Jack type:       Mic
[10:02] <valorie> Jack location:   Ext
[10:02] <valorie> Jack location2:  Top
[10:02] <valorie> Jack connector:  Digital
[10:02] <valorie> Jack color:      Black
[10:02] <valorie> No presence
[10:02] <valorie> there is none
[10:02] <valorie> in is checked
[10:02] <valorie> but no vref value
[10:03] <awilkins> Hmm, from this file, node 0x18 should be "Internal Mic Capture Volume"
[10:03] <awilkins> But no VREF
[10:03] <valorie> yes, that's the name
[10:03] <awilkins> Bah
[10:03] <valorie> but no vref
[10:03] <diwic> awilkins, digital mics usually don't have VREF_80 and that stuff because the connection between the dmic and the codec is digital
[10:03] <valorie> maybe it never DID work
[10:04] <valorie> sec, gotta take the old dog outside
[10:04] <awilkins> diwic, Thanks... I'm just an amateur
[10:04] <diwic> awilkins, and we need more helpful amateurs :-) and help them become more qualified
[10:05] <awilkins> Gah, I had that codec grapher somewhere
[10:06] <valorie> blind, deaf, and when he's gotta go, he's gotta go
[10:06] <apw> diwic, if you haven't met awilkins hes definatly a potential contributer on the debugging audio side
[10:06] <diwic> nice!
[10:07]  * diwic shakes hands with awilkins
[10:07]  * awilkins shakes hands back
[10:07] <apw> awilkins, meet diwic our sound expert
[10:08] <diwic> awilkins, the codecgraph utility is packaged and ready in the snd-hda-tools package in ppa:diwic/ppa
[10:09] <awilkins> diwic, Yup, installed
[10:09] <diwic> (or ppa:diwic/maverick for 10.10)
[10:09] <diwic> awilkins, so what I would do in this case is to take the codec a ride through hda-emu and see if the automuting does what it should
[10:10] <diwic> auto-switching between int and ext mic
[10:10] <diwic> valorie, when you posted that codec file, was anything plugged into the mic?
[10:10] <diwic> awilkins, potentially try a newer alsa-driver as well
[10:10] <valorie> hmm
[10:11] <valorie> I don't think so
[10:11] <valorie> I plugged in to test
[10:11] <awilkins> I think the relevant nodes are ...  nodes   0x18 (the mic pin)  0x1c (audio selector)  and 0x12  (audio input)
[10:11] <valorie> and then just now, plugged in earphones to test
[10:11] <valorie> earphones are really why I'm here
[10:12] <valorie> as it is unknown whether or not the mic ever worked
[10:12] <valorie> laptop isn't that old, but
[10:12] <valorie> don't know
[10:12] <diwic> awilkins, hmm, I /think/ it is 0x18 - 0x1d - 0x13 because that's stream 0, but better double-check in hda-emu
[10:13] <valorie> so the headphones textdump is at http://paste.ubuntu.com/612209
[10:13] <awilkins> diwic, What's the significance of dotty lines over solid ones - I was tending to follow solid ones when I was debugging my own issue
[10:14] <diwic> awilkins, dotty lines are generally unconnected but could potentially be connected if one changes that in the driver or hda-emu
[10:15] <diwic> awilkins, or in hda-analyzer I mean
[10:15] <valorie> and here is the codec#0 with definitely nothing plugged in: http://paste.ubuntu.com/612210
[10:16] <diwic> awilkins, ok so it is 0x18 - 0x1c - 0x12 actually
[10:17] <diwic> valorie, you don't happen to have an ATI controller, do you?
[10:17] <valorie> yes
[10:17] <diwic> valorie, you might be suffering from bug 741825 then
[10:17] <ubot2> Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825
[10:18] <valorie> gah!
[10:19] <diwic> valorie, and if so the recommended solution is https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules as we think this was finally fixed a few days ago
[10:19] <awilkins> If your first one was plugged and your second one was not, then I would concur
[10:19] <valorie> 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
[10:19] <awilkins> Because they are identical
[10:19] <diwic> apw, we should just see some more testing of this fix and then make it into a Natty SRU
[10:20] <diwic> apw, I think it needs two different commits to fix
[10:20] <apw> diwic, big and ugly ?
[10:21] <diwic> apw, no, but potentially affecting a lot of machines, that's my only hesitation...but in this case I think it's worth it
[10:21] <valorie> ok, installing
[10:21] <valorie> and for this, I will restart
[10:24] <jussi> o/
[10:25] <jussi> I just had a major crash of the whole system, ended up with this: http://wstaw.org/m/2011/05/24/2011-05-24_11-37-17_362_Oulu.jpg
[10:25] <jussi> any help ?
[10:25] <diwic> apw, i e affecting all ATI HDA machines
[10:26] <jussi> is there anything else I can get now (after a restart) that would help diagnose this?
[10:29] <apw> jussi, hmmm another cpuidle_idle_call explosion
[10:29] <apw> what kernel is that?
[10:29] <jussi> jussi@squirrel:~$ uname -a
[10:29] <jussi> Linux squirrel 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
[10:31] <diwic> ok I'll be away for lunch for a while, see you later!
[10:32] <jussi> apw: Im aroundish with this PC for the next ~4 hours. If there is anything else you need, please ask. Ill go file a bug in the meantime.
[10:37] <eagles0513875> jussi: did you have your whole system lock up on u and freeze nastily
[10:38] <eagles0513875> when you maximize konsole or certain other apps?
[10:38] <jussi> eagles0513875: no.
[10:38] <eagles0513875> ok just checking cuz that is a super  nasty bug which boils down to an nvidia driver issue
[10:39] <jussi> eagles0513875: given I dont have nvidia...
[10:39] <eagles0513875> ahh
[10:39]  * eagles0513875 retreats to the amarok channel
[10:40] <jussi> bug 787442
[10:40] <ubot2> Launchpad bug 787442 in linux "Complete machine crash (kernel panic?) " [Undecided,New] https://launchpad.net/bugs/787442
[10:40] <jussi> apw: ^^
[10:42] <eagles0513875> jussi: i was having those with atheros wifi card in my netbook
[10:42] <valorie> here goes nothing, restarting.....
[10:43] <eagles0513875> gd luck valorie
[10:43] <apw> jussi, you had a photo, could you attach that pls
[10:44] <jussi> apw: its attached - first attachment.
[10:44] <apw> stupid launchpad, hiding the important one
[10:44] <jussi> heh
[10:46] <apw> jussi, i've updated the subject.  if this is reproducible you could try the -propsoed kernel which as a heap of stable updates (-9
[10:46] <jussi> apw: I havent managed to reproduce :/
[10:47] <apw> i think i've seen 3 reports of something ismilar, one was put in my hands at UDS, but nothing common about them
[10:47] <eagles0513875> apw: there was my issue with kernel panicing and my atheros wifi card which is fixed in proposed
[10:48] <jussi> apw: I had this bug earlier: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775432 - I put it in someones hands at UDS.
[10:48] <ubot2> Launchpad bug 775432 in linux "rtl8169 kernel panic" [Undecided,Confirmed]
[10:49] <valorie> thank you SO MUCH!
[10:49] <valorie> I now have earphones again
[10:49] <valorie> if you give me that bug report, I'll comment on it if necessary
[10:50] <apw> jussi, that one is definatly different
[10:50] <jussi> apw: yeah.
[10:50] <jussi> apw: it was your hands (and Leann's) that I put it into iirc
[10:51] <jussi> Anywya, If I manage to reproduce, Ill let you know.
[10:51] <apw> jussi, quite likely :)  i had a lot of machines put in my hands over the week its hard to keep anything striaght
[10:51] <jussi> apw: :)
[10:51] <smb> jj-afk, hggdh FYI: I am able to reproduce the maverick ec2 fail locally. The "close blk" is normal though. It seems to be a very early lockup though. As I see 100% cpu usage but no dmesg output at all.
[10:53] <awilkins> valorie, bug 741825
[10:53] <ubot2> Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825
[11:01] <valorie> also, my mic seems to work now
[11:01] <valorie> at least the volume meter is showing activity
[11:01] <valorie> \o/
[11:04] <valorie> and SKYPE WORKS TOO!
[11:04] <valorie> y'all are miracle workers
[11:05] <apw> valorie, one of the many advantages of open source ... one can fix it
[11:06] <valorie> kub. packagers are working on some free alternatives
[11:06] <valorie> I hope we come up with something as good
[11:06] <valorie> or better
[11:09] <eagles0513875> awilkins: could ur fix possibly fix my issue with my webcam mic if it fixed it for valorie
[11:13] <awilkins> eagles0513875, An integrated webcam mic would be a USB driver problem
[11:14] <eagles0513875> ok
[11:14] <awilkins> eagles0513875, Mine didn't fix valories, she had a jack sensing issue, and my issue was a codec initialization issue
[11:14] <eagles0513875> ahh ok
[11:14] <eagles0513875> i guess ill have to take a look at the bios
[11:14] <awilkins> valorie has been fixed by another patch though
[11:14] <eagles0513875> ok
[11:15] <awilkins> I think if you can actually record sound from that mic it's not so much a kernel problem
[11:15] <eagles0513875> ok
[11:15] <eagles0513875> software as in skype issue
[11:17] <awilkins> eagles0513875, Don't know - you might consider trying a GNOME session (or Unity) to see if it works there
[11:17] <awilkins> eagles0513875, I don't know enough about KDE / phonon / whatever to speculate
[11:17] <eagles0513875> ok no worries
[12:37] <diwic> what am I doing wrong if I try to boot from a live Natty USB stick and get the error "Unable to find a medium containing a live file system"?
[12:38] <diwic> and dropped to a busybox shell
[12:42] <diwic> ok; switched usb slot, that helped
[13:32] <htorque> hello everyone! are there known boot problems with oneiric and intel hd graphics? my boot 'fails' 4 out of 5 times (i can ssh into the machine).
[13:32] <htorque> i sometimes see the plymouth text theme (kms problem?), but most of the time it's just a black screen with a blinking cursor. not happening with nvidia on the same notebook.
[14:25] <apw> htorque, nothing known, i use the kernel on my systems here and haven't seen that myself
[14:26] <apw> but i am not using oneiric userspace with them
[14:27] <htorque> apw, thanks. the only weird thing i noticed when ssh'd into the machine, was the short output of lsmod: http://paste.ubuntu.com/612274/
[14:27] <apw> htorque, does lsmod complete ?
[14:28] <htorque> i got a new prompt, so i guess yes (i didn't check the return value)
[14:29] <apw> a prompt is enough for me
[14:29] <apw> so i'd say we're only half booted
[14:32] <htorque> apw, would you say that looks like a kernel issue? i would then try to bisect
[14:33] <apw> very hard to say, i would try with the last natty kerenl on your userspace
[14:33] <apw> and see if the problem is resolved, if so then kernel it is
[14:33] <htorque> apw, thanks, will do.
[14:35] <dmarkey> hmm.. is there a known issue where xen network/block modules arent automatically modprobe'd
[14:35] <dmarkey> in 11.04
[14:39] <apw> dmarkey, in the virtual kernel ?
[14:40] <smb> dmarkey, Hm, not really aware of that. Seemed to have worked for me at least...
[14:40] <smb> (virtual kernel)
[14:41] <dmarkey> i'm using the pae kernel
[14:42] <smb> dmarkey, as domU (just to be sure)
[14:42] <dmarkey> Yes :)
[14:42] <dmarkey> i'll install the virtual kerne
[14:43] <htorque> apw: also happening with the natty kernel
[14:43] <apw> htorque, and you didn't have this i assume on natty itself?  so that implies it is something else
[14:43] <smb> dmarkey, I have not tried generic-pae but at least with the virtual I don't remember any problems when starting an instance
[14:44] <apw> given you have almost nothing running/loaded, i am worried about upstart
[14:44] <htorque> apw: no, natty was working fine
[14:49] <htorque> apw: "init: udev-fallback-graphics main process (...) terminated with status 1" - could this be the cause?
[14:49] <apw> yep, that could easily be the cuase
[14:50] <apw> as things wait for that to complete before starting X
[14:50] <htorque> i just wonder why this doesn't happen with nouveau
[14:50] <dmarkey> smb: do you have a installer initrd with the -virtual kernel
[14:51] <apw> htorque, well that one only does something if the drm driver doesn't load
[14:51] <apw> so its possible its telling you that the drm driver didn't load
[14:51] <apw> and that behaves different for each
[14:51] <apw> now why that has stopped working as normal is another question
[14:52] <apw> from your lsmod you also don't have much of anything else loaded, so it could be a udev issue
[14:52] <smb> dmarkey, not really. I sort of cheat and start of the cloud images (ripping the cloud out) most of the time.
[14:53] <dmarkey> i see. is I assu,e its udev thats dropping the ball here?
[14:53] <dmarkey> assume*
[14:54] <smb> dmarkey, those would be at http://uec-images.ubuntu.com/ (but probably won't help you). Hm, a sec
[14:57] <htorque> apw: "udevd: error binding udev control socket" sounds serious - had to use a camera to capture it, not sure if i get something similar in the nouveau case (it's just scrolling away too fast)
[14:57] <dmarkey> hmm.. how are these bootstrapped?
[14:58] <smb> dmarkey, ah wait. At least for virtual those are built-in... I guess not for the other flavours. So you probably need to add them to /etc/modules
[14:59] <dmarkey> but will that make it into the initrd?
[15:01] <smb> dmarkey, Right, modules, for generic-pae and built-in for virtual. Let me check...
[15:02] <smb> dmarkey, Maybe /etc/initramfs-tools/modules is better
[15:02] <dmarkey> but the modules are in my initrd at the min.. the problem is they're not getting modprobed!
[15:03] <smb> dmarkey, At least the comment in initramfs-tools/modules says that they should get loaded if listed there
[15:03] <dmarkey> ah i see
[15:36] <htorque> apw: it boots fine with natty's udev
[15:36] <apw> htorque, sounds like the place to file a bug then
[15:36] <apw> can you pasge the number here as well
[15:37] <htorque> apw: yeah, thanks! will do.
[15:38]  * ogasawara back in 20
[15:39] <htorque> hm, that's similar to the messages i see: bug 712026 -> comment #14 by smoser
[15:39] <ubot2> Launchpad bug 712026 in udev "cloud-init.conf never runs, instance not reachable via ssh" [High,Fix released] https://launchpad.net/bugs/712026
[15:41] <apw> htorque, that is a very different bug, could you file a new one, and indicate in smosers one that there is a separate bug
[15:46] <apw> htorque, is this a real machine or a VM for you
[15:46] <htorque> apw: real machine
[16:09] <htorque> apw: bug 787610 (sorry, took some time)
[16:09] <ubot2> Launchpad bug 787610 in udev "System fails to boot with Intel HD graphics" [Undecided,New] https://launchpad.net/bugs/787610
[16:32] <hggdh> smb: ping -- maverick ec2
[16:32] <smb> hggdh, pong, yes broken
[16:32] <JFo> heh
[16:32] <JFo> quickest conversation ever
[16:32] <hggdh> smb: will we regen the whole thing? In other words, should we keep on and test maverick on hardware?
[16:33] <hggdh> JFo: but I insist ;-)
[16:33] <JFo> heh, of course :)
[16:35] <smb> hggdh, I'd probably go on while I try to find what broke it
[16:35] <hggdh> smb: roj
[16:35] <smb> hggdh, Maybe start with 32bit to see if it breaks real hw too
[16:36] <hggdh> smb: heh.  Will do
[16:37] <smb> hggdh, I saw the same hang with the current master-next so at least not fixed in there.
[16:37] <hggdh> things get more exciting, I see
[16:38] <smb> hggdh, Now I am trying to bisect or make crash work for me...
[16:42] <herton> smb, ogasawara: bjf told me about Finalise() vim for kernel changelog, where it comes from?
[16:42] <smb> herton, IT some vim file magic
[16:42] <herton> I was using dch on my test builds, but seems more practical to use this directly in vi
[16:43] <ogasawara> herton: smb taught me that bit of magic
[16:43] <smb> Though it needed enabling tings sometimes. If it works for you there is even more magic that came from apw to make it a two keystroke
[16:43] <ogasawara> yah, I've got a vim shortcut for it
[16:44] <smb> herton, can send you the relevant vimrc thing
[16:45] <herton> smb: yes please do
[16:45] <apw> yeah i use a couple of bindings
[16:46] <apw> to those vim functions, which are only loaded when the file is called changelog
[16:52] <smb> herton, file is on the way
[16:53] <herton> received here, thanks, will try it
[16:56] <herton> where you define Finalise(), is it from some plugin like package?
[17:00] <herton> ok seems to come from /usr/share/vim/vimcurrent/ftplugin/debchangelog.vim, just wonder why it didn't find it
[17:01] <smb> herton, As I wrote there is also the plugin enable switch. I remember this had to be turned on at some point
[17:01] <smb> So enable filetype plugins and the file must be named changelog
[17:02] <smb> otherwise it is not there
[17:07] <herton> smb: it is what filetype plugin on is supposed to do right? will figure this out later, lunch here, bbl
[17:08] <ppisati> don't we have the meeting in an hour? i think i didn't see brad email
[17:09] <JFo> yep, we do
[17:09] <apw> sconklin, bjf, FYI the lts-backport-natty is now up to date, and should be included in the matrix
[17:09] <bjf> apw, thanks, we were talking about it just a little while ago
[17:09] <apw> i talked to cjw and we don't need to do anything other than get it copied to -proposed
[17:10] <apw> no process is required.  so i've pulled it forward and uploaded it to ckt PPA, hopefully I did it right :)
[17:10] <bjf> ppetraki, you are correct and i'd completely forgotten about it
[17:10] <apw> the brnaches are all pushed into lucid repo as normal
[17:10] <apw> branch and tag even
[17:10] <bjf> apw, i'll bet you didn't add a tracking bug :-)
[17:10] <JFo> we have a seeming conflict with some app dev board?
[17:10] <JFo> bjf ^^
[17:11] <ppetraki> bjf, what am I right about? (happens alot)
[17:11] <JFo> at 5 in the -meeting room that is
[17:11] <bjf> JFo, looking
[17:11] <JFo> k
[17:11] <JFo> bjf, I'm looking at http://www.ubuntu-news.org/calendars/fridge/
[17:11] <JFo> just FYI
[17:11] <apw> bjf, heh nope, though when i uploaded it i was building it to get it into universe for a MIR, which is not required, so i forgive me ... feel free to blow it up and replace it
[17:12] <bjf> apw, we appreciate any and all help, np
[17:12] <smb> bjf, sconklin Btw, I had been questioned about "when goes lucid from proposed to updates". As the calendar shows this week prep for next cycle I was not really able to answer. ;)
[17:12] <apw> yeah been wondering of those 'yellow' things had been updated since the 2w to 3w transition
[17:12] <sconklin> smb: it is out of our hands.
[17:13] <bjf> smb, basically, qa is behind schedule so we're not sure
[17:13] <bjf> ppetraki, about the meeting
[17:14] <smb> Ah. Somehow I had the illusion for lucid it was done.
[17:14] <JFo> ppetraki, he meant that for ppisati
[17:14] <JFo> :)
[17:15]  * JFo directs traffic
[17:15] <bjf> JFo, i see what you are talking about, any thoughts on who i talk to about it
[17:15] <JFo> no idea
[17:15] <ppetraki> I figured :)
[17:15] <JFo> one sec...
[17:15] <bjf> ppetraki, sorrry for the noise :-)
[17:15] <ppetraki> np
[17:15] <JFo> bjf, looks like allison
[17:15] <JFo> as per https://wiki.ubuntu.com/AppReviewBoard/Agenda
[17:16] <bjf> JFo, thanks, i'll ping her
[17:16] <JFo> k
[17:16]  * JFo is fully caffeinated today. imagine what I coulod accomplish on Jolt Cola ;)
[17:16] <JFo> could*
[17:16] <JFo> I still wouldn't be able to spell all of the time
[17:18] <smb> JFo, Imagine all the trippple keypressses. :)
[17:19] <JFo> heh
[17:19] <JFo> then you could call me JittersFo
[17:20] <smb> JFo, Or "Zip" (If you ever played Fallout 3 ;))
[17:21] <JFo> heh, I do
[17:21] <bjf> JFo, they are moving, thanks for the heads up
[17:21] <JFo> bjf, my pleasure
[17:22] <bjf> ppisati, am going to be looking for you for ARM status from now on, you are on the agenda
[17:22] <JFo> be ready, we hate slow meetings ;-)
[17:22] <bjf> ppisati, i can let it go this time, but be ready next time
[17:22] <ppisati> bjf: ack
[17:24] <apw> bjf, am i on the hook for anything today
[17:24] <bjf> apw, NO! but i can find something if you like :-)
[17:24] <bjf> apw, or if ogasawara would like me to
[17:25] <apw> heh, that'll be just fine, i assume its at now +00:35
[17:25] <JFo> smb, do I need an EC2 item vor my metrics in the meeting?
[17:25] <JFo> for*
[17:26] <bjf> ##
[17:26] <bjf> ## Kernel team meeting in 34 minutes
[17:26] <bjf> ##
[17:26] <smb> JFo, Hm do we do special metrics for any arm stuff?
[17:27] <JFo> I did have items for them in case they were needed
[17:27] <bjf> smb, you are on the hook for one agenda item
[17:27] <JFo> I don't put them unless you guys tell me to
[17:28] <smb> JFo, Yeah, I am not sure (maybe yet) I need one... I'll come and whine whenever I find out I do
[17:28] <JFo> sounds good
[17:28] <JFo> I'll leave it off for now
[17:28] <smb> bjf, Guess I should look at it then...
[17:28] <bjf> jfo, ogasawara, sconklin smb all have agenda items, just a heads-up
[17:28] <smb> ta
[17:53] <JFo> I'm ready
[17:54] <apw> sconklin, did i see you applied both vesafb patches?  i think i was expecting only the first to apply to older releases
[17:55] <sconklin> apw: well, I've deleted the email now, but I thought that the 0/0 listed all the series. Probably my mistake
[17:55] <apw> I am proposing the first patch for Oneiric, Natty, Maverick, and Lucid
[17:55] <apw> as a clear bug fix.  The second sounds like something we could apply in
[17:55] <apw> Oneiric only and see what falls out.
[17:55] <sconklin> They all applied. Whether that's correct or not is a reasonable question
[17:55] <sconklin> I'll redo it after the meeting
[17:56] <apw> sconklin, ack, the risk for the older releases is too high imo
[17:56] <apw> for the small gain its likely to give
[17:56] <sconklin> apw: ack, I trust that judgement
[17:57] <sconklin> at least it's just a one patch reset unless something else has been pushed ;-)
[17:57] <dmarkey> Anyway, i'm going to file a ticket for this xen-blkfront not being modprobe'd
[18:00] <sconklin> apw: all fixed, thanks for letting me know
[18:08] <JFo> wow, my typing skills fail
[18:09]  * ppisati -> gym
[18:10] <jjohansen> ogasawara: agree with doing config review at the sprint, I don't think there are any critically big changes to come out of it
[18:11] <ogasawara> jjohansen: cool, I'll mark your work item as done then :)
[18:11] <jjohansen> hehe :)
[18:11] <ogasawara> jjohansen: and add an item to our agenda for the rally
[18:11] <jjohansen> thanks
[18:14] <JFo> <-need food, back soon
[18:40] <jjohansen> ogasawara, apw, rtg: actually there was one config that I thought worth discussing now.  CONFIG_HZ
[18:40] <jjohansen> for our i386 and ppc kernels it is 250, but for our amd64 kernels it is 100.  I think desktop should be 250
[18:40] <apw> jjohansen, ok whats your reasoning .... (i tend to agree but)
[18:41] <ogasawara> jjohansen: hrm, I thought bjf had sent a patch for that.
[18:41] <jjohansen> apw: well for desktop we would like a better latency, 250 is a nice compromise between 100 and 1000
[18:41] <bjf> ogasawara, no, i bumped the number of cpus
[18:41] <ogasawara> ah, I stand corrected
[18:41] <jjohansen> it also what we settled on for the i386 desktop
[18:42] <apw> jjohansen, i tend to agree its odd they are not consistant
[18:42] <jjohansen> apw: I don't have any figures, I could go and generate some, but that is one difference that really stood out
[18:42] <apw> i think we moved cause NO_HZ was supposed to make the number meaningless anyhow
[18:43] <jjohansen> apw: no NO_HZ is only for tickless sleep
[18:44] <jjohansen> apw: hrm, no I stand corrected, from the current Kconfig
[18:44] <jjohansen>          This option enables a tickless system: timer interrupts will
[18:44] <jjohansen>           only trigger on an as-needed basis both when the system is
[18:44] <jjohansen>           busy and when the system is idle.
[18:45] <jjohansen> so it for busy as well, now I don't remember that change happening
[18:45] <apw> which should mean a higer HZ is cheaper, but cking's number says not ... hrm
[18:45] <apw> i am inclined to agree that without numbers that they should be consistant, 250 desktop, 100 server
[18:45] <apw> and work from there
[18:46] <jjohansen> apw: I think we should add a work item to generate some numbers and review at the sprint
[18:46] <apw> jjohansen, ack, you got time to do the work, or should i finger cking as he is off :)
[18:47] <JFo> heh
[18:47] <jjohansen> apw: since I brought it up, I'll take it as part of my prep for the config review
[18:47] <JFo> also, it would be awesome if you guys could spare me some skills training at platform
[18:47] <JFo> I'm trying to narrow some stuff we could work on in a few blocks
[18:48] <JFo> will send e-mail once I have more written down
[18:48] <JFo> going to see about getting some of graphics/sound/hardware enablement time as well
[19:02] <bjf> ogasawara, should i pull the config review from the meeting agenda until post Rally ?
[19:02] <ogasawara> bjf: sure
[19:05] <apw> jjohansen, if you have time thats great else just assign it to [canonical-kernel-team] and it'll stay on my radar
[19:06] <jjohansen> apw: lets assign it to me for now and if I don't get to it with in the next week or two we will reevaluate
[19:06] <apw> jjohansen, works for me
[19:29]  * apw wanders off to get some dinner ... laters
[19:38] <JFo> ogasawara, are you aware of a change like the one described in bug 787671 ?
[19:38] <ubot2> Launchpad bug 787671 in linux "Starting with 2.6.39, EBS volumes start at /dev/xvde" [Undecided,New] https://launchpad.net/bugs/787671
[19:38] <JFo> seems like something that should be easy to confirm if I had the requisite volumes :)
[19:39] <JFo> and where would I look to determine if there was a change? obviously git log would help, but anything  more than that?
[19:39] <manjo> how do I determine which upstream tree I cloned my tree from ?
[19:40] <manjo> thanks found it
[19:40] <JFo> what was it manjo
[19:40] <JFo> ?
[19:40] <manjo> .git/config has the info
[19:41] <JFo> cool, thanks
[19:42]  * JFo grabs oneiric branch while he is thinking about it
[19:51] <ogasawara> JFo: I'm not aware of changes, maybe smb or jjohansen could confirm?
[19:54] <jjohansen> JFo: I haven't follow the ebs volume changes to closely this last kernel, but there were xen patches that went into to 2.6.39, I have a look
[19:54] <JFo> yeah, I initially thought of smb, but after hours for him. :)
[19:55] <JFo> k, thanks jjohansen
[19:58] <JFo> my oneiric branch fetch is taking longer than I thought
[20:04] <jjohansen> JFo: so there is a patch that affects the xen-blkfront driver device id numbering, I haven't looked at it to much but I suspect it is the cause
[20:04] <bjf> kees, is there a way (other than uploading a package) to see if my upload rights have been granted in LP?
[20:04] <JFo> jjohansen, ok, thanks
[20:05] <kees> bjf: that's an excellent question. I don't know where that information is held, actually. I'll see if cjwatson knows.
[20:09] <kees> bjf: looks like you still don't have it. who else on the team has those rights, just so I can compare?
[20:09] <bjf> ogasawara,
[20:09] <bjf> kees, ogasawara would have them
[20:10] <kees> all these irc nick vs LP nicks ;)
[20:10] <kees> yeah, I see her perms, so it looks like whoever needs to do that hasn't done it.
[20:11] <bjf> kees, thanks for checking
[20:11] <kees> https://launchpad.net/~ubuntu-kernel-uploaders/+members  is it just this list?
[20:12] <kees> bjf: who from the DMB is supposed to update that?
[20:12] <bjf> kees, that looks like the right list, i don't know who is supposed to update it
[20:13] <kees> (for reference, lp:~ubuntu-archive/ubuntu-archive-tools/trunk/ has edit_acl.py which I'm using as "./edit_acl.py query -p brad-figg" and "./edit_acl.py query -p leannogasawara")
[20:15] <kees> bjf: maco says she has added you now.
[20:15] <kees> and the edit_acl.py output seems to agree
[20:16] <bjf> kees, i just popped onto the list
[20:16] <bjf> kees, you want to remove me from ubuntu-drivers ?
[20:16] <kees> bjf: sure, let's try that again....
[20:17] <kees> bjf: okay, I've deactivated you there. can you still do bug task nominations?
[20:18] <bjf> kees, I'll give it a twirl and get back to you if i have any problems, thanks for the help
[20:18] <kees> bjf: okay, cool. thanks for testing! :)
[20:25] <avinashhm> Hi friends , i am trying to compile ubuntu kernel .. got the sources via 'apt-get source linux-image-$(uname -r)' .. i don't want to use fakeroot to compile ... want to use general make with some configs .. was looking on info to build which config .. any pointers will help
[20:28] <bjf> avinashhm, https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel documents how we suggest you do it
[20:29] <bjf> avinashhm, if you want to find another way, google is your friend :-)
[20:29] <hggdh> smb: maverick i386 is OK on KVM
[20:30] <avinashhm> bjf, sure ... ;-) .. i ll go over the link .. thanks buddy ..
[20:41] <JFo> jjohansen, was the one you were thinking it was the "xen-blkfront: handle Xen major numbers other than XENVBD" one?
[20:42] <avinashhm> Hi bjf , just curious ... i need only info abt the config used ... is it 'i386_defconfig' ? which is used for regular ubuntu ...(arch/x86/configs/i386_defconfig ?
[20:48] <manjo> ogasawara, who is looking at Ubuntu delta this cycle ?
[20:49] <ogasawara> manjo: it's been farmed to different individuals
[20:49] <ogasawara> manjo: anything in particular you're interested in?
[20:49] <bjf> avinashhm, cp /boot/config-`uname -r` /usr/src/linux/.config
[20:49] <manjo> ogasawara, omnibook module needs a refresh its been oopsing since natty
[20:49] <ogasawara> manjo: we've disabled it
[20:50] <manjo> ogasawara, ok.. looks like the project is dead ...
[20:50] <ogasawara> manjo: discussed it at UDS and decided to turn it off and see who screams
[20:50] <manjo> ogasawara, Satellite and Tecra and some HP users
[20:50] <manjo> ie tohsiba & HP
[20:50] <manjo> toshiba rather
[20:51] <mjg59> It's really not the right interface for any modern hardware
[20:52] <manjo> sure its a crappy module
[20:54] <manjo> ogasawara, we introduced it in karmic coz some people requested it ... good to know we got rid of it
[20:56] <jjohansen> JFo: yep
[20:56] <JFo> cool, found it here https://patchwork.kernel.org/patch/567891/
[20:56] <JFo> no idea what all is going on, but I understand a large part of it
[20:57] <JFo> going to look at it a bit tomorrow, my brain is almost fried for today
[20:58] <avinashhm> bjf, thanks very much
[20:58] <bjf> avinashhm, you may not want to actually copy it where i indicated, but it shows you where to find it
[20:59] <avinashhm> bjf, correct ... i downloaded src ~/git/ .. i ll copy to this root ..
[20:59] <kees> hmpf, how do I fix the "Author" when working on git patches?
[21:01] <sforshee> kees, git commit --author="..."
[21:01] <ogasawara> kees: git commit --author ?
[21:01] <kees> what if I'm working on a rebase?
[21:03] <ogasawara> kees: hrm, could you use rebase -i, mark the commit as an 'edit', and then use git commit --author ?
[21:04] <kees> ah! good, yes
[21:05] <kees> ogasawara: yes! it worked. :) git commit --amend --author ...; git rebase --continue sweet
[21:05] <ogasawara> kees: nice
[21:15] <sconklin> http://lwn.net/Articles/444336/ Interesting argument against prefetch
[21:16]  * JFo takes notes
[21:20] <JFo> stepping away for a bit. I need to run an errand
[21:22]  * jjohansen steps away for some lunch
[22:11]  * herton --> eod
[22:55] <jjohansen> hallyn: have you seen https://lkml.org/lkml/2011/5/24/502
[23:01] <hallyn> no
[23:05] <hallyn> jjohansen: have you pursued it?
[23:06] <jjohansen> hallyn: just to the apparmor, first poke level, /me is planning to get back to it later tonight
[23:06] <jjohansen> I want to finish up with some other stuff first
[23:06] <hallyn> jjohansen: ok, thanks
[23:08] <hallyn> i dunno, but 'cred' is NULL at cap_capable() too.  THis looks like memory corruption
[23:22] <jjohansen> hallyn: yeah I wasn't sure what was going on there, I want to try replicating myself
[23:22] <hallyn> ditto
[23:23] <hallyn> bbl
[23:23] <hallyn> thanks for the tip


[12:37] <Spock_> amd-64 flash when will it work via install?
[12:37] <Spock_> I know it is proprietary
[12:39] <LaserJock> I don't think there is a 64bit version of flash
[12:40] <Spock_> is adobe losing it?
[12:40] <LaserJock> "losing"?
[12:41] <Spock_> Giving up on good software development?
[12:41] <LaserJock> I have no idea
[12:41] <LaserJock> they've never had a 64bit version that I know of
[12:42] <Spock_> Is there a good linux alternative?
[12:42] <LaserJock> well, there is 32bit flash
[12:42] <Spock_> ok, I will keep using that
[01:37] <pointwood> any ubuntu members in here? counld someone please join #ubuntu-trivia ? thx :)
[01:38] <jrib> lol pointwood beat me to it
[01:38] <apater> gnash is free software flash alternative
[01:38] <pointwood> nm :)
[01:38] <pointwood> evil trivia question :)
[01:49] <apater> OK, as the LoCo session tomorrow is way too early for a saturday morning, are there any people from Vancouver here who would be interested in a local Ubuntu get together?
[02:15] <theCore> who is the expert in packaging here?
[02:41] <Admiral_Chicago> theCore: nobody
[02:41] <Admiral_Chicago> maybe one of the MOTUs :P
[02:41] <theCore> yeah, maybe
[02:58] <poningru> so I thought this would a bit more... crouded
[03:24] <somerville32> Can anyone tell me if I'm ready to apply for membership yet or not? <g>
[03:31] <omgponiezlol> poningru: it was fuller earlier...
[03:31] <somerville32> doh
[03:31] <poningru> err... ok
[03:31] <poningru> nice nick
[03:31] <poningru> I think
[03:33] <somerville32> Slashdot joke
[03:33] <somerville32> :]
[03:34] <omgponiezlol> somerville32: yup
[03:35] <omgponiezlol> poningru: http://fridge.ubuntu.com/files/no-pony-for-you.jpg
[03:35] <somerville32> Can anyone tell me if I'm ready to apply for membership yet or not? <g>
[03:35] <omgponiezlol> somerville32: link to your wiki page please, also your LP page
[03:36] <somerville32> http://launchpad.net/people/cody-somerville
[03:36] <poningru> err I thought it was a php4 joke
[03:37] <poningru> omgponiezlol: who are you really?
[03:38] <poningru> mdke?
[03:38] <poningru> err nm
[03:38] <omgponiezlol> poningru: Admiral_Chicago AKA Freddy Martinez
[03:39] <omgponiezlol> poningru: LP looks good, do you have a wiki page?
[03:39] <omgponiezlol> also a link to the LoCo team
[03:39] <poningru> blargh?
[03:39] <elkbuntu> somerville32, if you have problems getting through with that, i'll be highly surprised
[03:39] <poningru> talking about my wiki page?
[03:40] <poningru> I have one EldoVarghese
[03:40] <poningru> but its not done yet
[03:40] <omgponiezlol> yes you have a very good LP page
[03:40] <omgponiezlol> you should work on your wiki page
[03:41] <omgponiezlol> also, I would look at your goals for Ubuntu, what do you want to do with Ubuntu in the future etc
[03:41] <omgponiezlol> just something to think about
[03:41] <somerville32> omgponizelol: ...
[03:41] <poningru> I have a good lp page?
[03:41] <somerville32> I think you're confused omgponiezlol, lol
[03:43] <somerville32> elkbuntu: But I don
[03:44] <somerville32> 't feel like I've done _enough_
[03:44] <elkbuntu> somerville32, i didnt either
[03:45] <poningru> but elkbuntu you had done a lot
[03:45] <elkbuntu> poningru, it's always easier to say that when you're on the outside
[03:46] <omgponiezlol> somerville32: i'm confused?
[03:47] <omgponiezlol> ah yess wrong person
[03:47] <somerville32> Yeah, we were talking about me.
[03:47] <omgponiezlol> sorry
[03:47] <somerville32> And I have stuff on my wiki page about my future goals
[03:47] <omgponiezlol> poningru: https://launchpad.net/people/freddymartinez9
[03:47] <omgponiezlol> thats who I am IRL
[04:36] <aerugo> Hey
[05:36] <swaby1> hi
[06:14] <yaso> #hurd
[06:14] <yaso> rofl
[06:14] <yaso> sorry ;D
[10:41] <somerville32> I have a question.
[10:41] <somerville32> Where can I join the Scott Remnant fan club?
[10:43] <elkbuntu> lol
[11:13] <dpreacher> hello
[04:00] <zzsimonb> hi there, i was wondering if someone could offer a newbie some help?
[04:00] <zzsimonb>  I am trying to load ubuntu on some laptops, they have no cd, so i am using root-boot and then trying to net install
[04:01] <zzsimonb> i get to running debootstrap --arch etc etc and it resolves dependencies and then just returns to the # prompt
[04:01] <zzsimonb> instead of installing
[04:01] <zzsimonb> anyone got any insight?
[04:02] <juliux> zzsimonb, pls use #ubuntu for support
[04:02] <zzsimonb> oh ok, thanks
[04:02] <zzsimonb> sorry i thought this was the help place for beginners
[06:04] <knight> hi


[02:34] <lfaraone> If for an upload I'm only regenerating debian/control from debian/control.in, can I use "build1" rather than "ubuntu1" since the change can safely be synced over?
[02:35] <lfaraone> (picking up some bug fixes in control generation in the newer versions of CDBS)
[02:35] <micahg> lfaraone: build1 is usually a no source change rebuild
[02:36] <lfaraone> micahg: yeah, but we're basically calling "DEB_MAINTAINER_MODE=1 debian/rules clean; dch -i 'Regenerating debian/control from debian/control.in.'"
[02:37] <lfaraone> micahg: and that's all that's needed to fix a bug.
[02:39] <lfaraone> micahg: I feel silly to have to make a sync request for this bug next time Debian releases something.
[02:41] <micahg> lfaraone: do you have upload rights for it?
[02:41] <lfaraone> micahg: yes.
[02:41] <micahg> lfaraone: you can sync it yourself with the sync script in u-d-t
[02:42] <lfaraone> micahg: yes, but when I do that I feel the death glares of the Archive Admins.
[02:42] <lfaraone> and I keep on reading people in -motu decrying use of the script.
[02:42] <micahg> lfaraone: heh, I think they would've complained more about it going into u-d-t if they didn't want it used
[02:43] <lfaraone> micahg: wonder why it's not installed in the package?
[02:44] <micahg> lfaraone: https://edge.launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.100
[02:44] <lfaraone> micahg: oh, wow. I'll shut up then :)
[02:45] <lfaraone> micahg: now all we need is to get ack-sru in there :)
[02:45] <micahg> lfaraone: being cautious isn't a bad thing especially with uploads :)
[02:47]  * micahg agrees though if there's no rush, just to file the sync
[06:55] <bilalakhtar> tumbleweed: you there ?
[08:26] <huats> morning
[08:40] <Rhonda> I wonder how the iPhone Ubuntu One client is more (or less?) compliant with the license it is put into. From what I understood the Affero GPL would be even more in violation by the appstore?
[08:41] <Rhonda> erm, violated, not in violation
[08:41] <wgrant> They've probably dual-licensed it.
[08:41] <wgrant> But #ubuntuone might know.
[08:42] <Rhonda> Thanks for the pointer - I just didn't know where to mention it otherwise. :)
[08:43] <wgrant> But yes, I wondered that myself.
[08:43] <wgrant> Given the recent Wesnoth business.
[08:43] <Rhonda> cloning the ios client though has a drop of the affero license, which is even more in violation.
[08:43] <Rhonda> I'm very well aware of that, to be honest. ;)
[08:44] <wgrant> How's it even more in violation?
[08:44] <Rhonda> Because of the requirements that Affero has.
[08:44] <wgrant> Canonical owns all the code. They can distribute it under any other license.
[08:44] <Rhonda> It would mean that the appstore itself has to provide the source.
[08:45] <Rhonda> Right, but this is the only license that I see when cloning the ios branch.
[08:45] <Rhonda> If it wouldn't be in the clone of ubuntuone-ios-client, I wouldn't have asked.
[08:45] <wgrant> They never were very good with their license headers.
[08:46] <wgrant> Or licensing.
[09:01] <vish> Rhonda: hi , how do we change the email id when using reportbug?
[09:01]  * vish found channel #ubuntu-debian empty except for gbot ofcourse :)
[09:01] <vish> its seems to pull my old mail id.. need to change that..
[09:02] <hyperair> vish: i believe it uses DEBEMAIL
[09:03] <vish> hyperair: where is that ?
[09:04] <hyperair> vish: in .${SHELL}rc?
[09:04] <hyperair> you can also define it in .reportbugrc by 'email<EMAIL_ADDRESS>[09:04] <hyperair> and 'realname "Chow Loong Jin"'
[09:05] <hyperair> hmm i wonder where my .reportbugrc came from.. it seems like a template of sorts.
[09:05] <hyperair> vish: you can run reportbug --configure
[09:05] <vish> neat!
[09:10] <vish> hyperair: yeah , editing the .reportbugrc did the job... but i still didnt find where the mail id was being pulled from :s
[09:11] <hyperair> vish: DEBEMAIL environment variable?
[09:11] <vish> yeah..
[09:12] <Rhonda> vish: You export DEBEMAIL.
[09:13] <Rhonda> Sorry, I had that in my notes but forgot to mention it in the talk. It's the same environment variable for the bts tool, btw.
[09:24] <vish> Rhonda: ok. but this is my first time using debian or report bug , so I'm not sure where DEBEMAIL is set ..
[09:27] <Rhonda> It's meant to be an environment variable.
[09:27] <Rhonda> Wait, one moment.
[09:28] <Rhonda> What's the shell you use? I suspect it might be bash?
[09:29] <Rhonda> Anyway, what you always can do is<EMAIL_ADDRESS>reportbug $package" - prefix the command with it.
[09:29] <vish> i check the .bashrc and it aint there
[09:29] <vish> checked*
[09:29] <Rhonda> Then simply add it. :)
[09:29] <Rhonda> Add a line like "export<EMAIL_ADDRESS>[09:30] <Rhonda> Also issue that command in your shell to have it for the current running shell, too.
[09:30] <vish> Rhonda: hehe , well , I was able to add it to the .reportbugrc and change it , but am wondering where it was pulling my id from in the first place :)
[09:30] <Rhonda> reportbug tells right ahead as one of its starting message what email address it's going to use. You can always press ctrl-c to stop at that point too, so don't hesitate to just give it a try and check wether it was done properly.
[09:31] <Rhonda> If it can't find anything it defaults to $USER@`honstmae -f`
[09:31] <Rhonda> So uses your login and the full hostname of your system.
[09:32] <vish> yup , thats when i noticed my mail id :)
[09:32] <Rhonda> And I really would have vished for such questions to pop up during the talk. The feedback came only from very few people, which felt a bit discouraging/disappointing. :/
[09:32]  * Rhonda . o O ( pun intended ;) )
[09:33] <vish> Rhonda: haha , it was too late last nite , caught up with logs only now :)
[09:33] <vish> timezones suck fwiw ;)
[09:35] <LucidFox> dholbach, thanks for publishing! o/
[09:40] <dholbach> LucidFox: thanks for sending it in so quickly! :)
[09:40] <dholbach> LucidFox: apart from nigelb, bobbo is also interested
[09:46] <nigelb> vish: this shows you aren't packaging :p
[09:47] <nigelb> LucidFox: time to hunt for next target :p
[09:50] <nigelb> Rhonda: FYI, you're free to be on that channel :)
[09:50] <LucidFox> What channel?
[09:51] <nigelb> #ubuntu-classroom-backstage
[09:54] <Quintasan> \o
[09:59] <Rhonda> nigelb: Way to many windows, have to cut them down to stuff that feels relevant for me for longer than just a few minutes. Still have way too many open.
[10:00] <nigelb> Rhonda: can beat 3 digits?
[10:01] <Rhonda> Almost  %-/
[10:01] <nigelb> heh
[10:29] <bilalakhtar> *CRITICAL* need help with bug #604910
[10:32] <bilalakhtar> tumbleweed: you there?
[10:34] <tumbleweed> bilalakhtar: hi
[10:34] <bilalakhtar> tumbleweed: hi there! bug #604910
[10:34] <bilalakhtar> I cannot figure out why the problem is occuring
[10:35] <tumbleweed> bilalakhtar: have you dealt with the existing delta issues?
[10:36] <bilalakhtar> tumbleweed: which package?
[10:36] <vish> nigelb: well , there is only so much i can do with time available ;)  cant be omnipresent ;)
[10:36] <tumbleweed> bilalakhtar: that one, fabrice_sp's comments
[10:37] <vish> nigelb: btw , why is #ubuntu-debian totally empty?
[10:37] <bilalakhtar> tumbleweed: my problem, will come here after 10 mins
[10:37] <tumbleweed> bilalakhtar:
[10:37] <tumbleweed> $ apt-cache show libsplashy1-dev
[10:37] <tumbleweed> W: Unable to locate package libsplashy1-dev
[10:38] <Laney> vish: because it's #debian-ubuntu
[10:38] <Laney> and it's on oftc.
[10:38] <geser> vish: try #debian-ubuntu @ OFTC
[10:38] <bilalakhtar> tumbleweed: yes, I understand everything over here now
[10:39] <vish> ah cool, was going by Rhonda's session..
[10:42] <Laney> wgrant: Did you get my message about haskell & multidistrotools the other day?
[10:42] <wgrant> Laney: I don't believe so... what's the issue?
[10:42] <Laney> wgrant: The sid details seem out of date
[10:42] <Laney> It thinks that a load of packages are newer in M than sid
[10:43] <wgrant> I wonder if that's because there are multiple versions in Sources...
[10:43] <nigelb> vish: because you probably are on the freenode channel.  the acual one is on oftc.
[10:43] <bilalakhtar> tumbleweed: in the meantime, do you know any core-dev ? I have a bunch of main bug fixes.
[10:43] <wgrant> Hm, no, that's not it.
[10:44] <tumbleweed> bilalakhtar: yes, there are some here, you can ask
[10:44] <vish> nigelb: yeah , in the class session logs its mentioned as  #ubuntu-debian  , so probably we should correct that while adding to wiki
[10:45] <nigelb> vish: hm, true.  I'll add a footnote
[10:48] <bilalakhtar> tumbleweed: we have a lockout here. usplash support doesn't work, and splashy has been removed from Ubuntu archives, as it conflicts with plymouth in lucid. What should we do with uswsusp? get it removed as well ?
[10:49] <tumbleweed> bilalakhtar: disable splashy support in uswsusp
[10:49] <bilalakhtar> tumbleweed: then tell it to use what? it needs one of the two
[10:50] <tumbleweed> bilalakhtar: aah, in that case it isn't usable on ubuntu, yes
[10:50] <bilalakhtar> tumbleweed: wait a minute, I think it can be used without either
[10:51] <bilalakhtar> tumbleweed: BRB in 10 mins
[11:07] <bilalakhtar> tumbleweed: bug #604910
[11:09] <bilalakhtar> uswsusp works without splashy or usplash
[11:17] <bilalakhtar> tumbleweed: you there?
[11:31] <tumbleweed> bilalakhtar: I can only look in a few hours
[11:47] <bilalakhtar> Someone, please sponsor fix for bug #155930
[13:18] <sommer> morning all
[13:19] <Aquina> 'lo
[15:26] <lfaraone> dholbach: if you're looking for more people for Behind MOTU, let me know :)
[15:27] <tkren> Hey there, anyone has some time for reviewing clasp, an answer set solver for logic programs? See http://revu.ubuntuwire.com/p/clasp
[15:27] <dholbach> lfaraone: up until now LucidFox, nigelb and bobbo stepped up to help out :)
[15:47] <lfaraone> If I'm simply rewording a changelog entry from a sponsoree, should I replace his name with mine and credit him using the '[]' syntax, or can I just amke the change and leave his name as the author in the changelog?
[15:55] <geser> would it really be such a difference when you reword the changelog entry and credit him in [] compared to his name as the author of the changelog entry?
[15:56] <Laney> dch --[no]mainttrailer
[16:58] <ari-tczew> slangasek: ping
[17:21] <ari-tczew> who is expierenced with bzr-merge ?
[18:01] <leonel> Hello :  Ubuntu Lucid has cherokee 0.99.39 ,  I maintain the latest cherokee on ppa (https://edge.launchpad.net/~cherokee-webserver/+archive/ppa)  with upstream and with the debian maintainer for cherokee, I'd like to push 1.0.1 to lucid what's the procedure to do this ?
[18:03] <jpds> leonel: https://wiki.ubuntu.com/StableReleaseUpdates
[18:05] <leonel> jpds: I know there are no new versions but for lucid as an LTS I think Would be better to have this 1.0 version instead the 0.99.39
[18:08] <ScottL> leonel, you can try for backport ?
[18:08] <ScottL> !backport | leonel
[18:09] <leonel> Yes I can ..
[18:10] <leonel> with upstream we were taking about keep a stable release  this case 1.0.1 and the devel versions with ppa
[18:10] <leonel> have 2 branches for the package
[18:10] <leonel> since most of the ubuntu users that use cherokee  uses  the ppa version
[18:11] <leonel> and we can doit with ppa packages
[18:11] <leonel> but I think can be better to keep the stable 1.0.1 in Ubuntu replacing the 0.99.39  and keep the lattest version in ppa
[18:12] <lfaraone> micahg: for your mozilla uploaders, do you set the maintainer to ubuntu mozilla uploaders, or to the wider ubuntu mozilla team?
[18:19] <micahg> lfaraone: mozillateam which goes to a ML
[18:20] <lfaraone> micahg: mk, that's what I've been doing with sugarteam.
[18:20] <lfaraone> micahg: think it's worthwhile to modify update-maintainer so it does that automatically?
[18:20] <ari-tczew> tumbleweed: ping
[18:20] <micahg> lfaraone: no, the general consensus is that everything should go to<EMAIL_ADDRESS>[18:21] <micahg> lfaraone: but there are a few exceptions :)
[18:21] <micahg> lfaraone: also, our stuff doesn't go through debian, so it never changes
[18:21] <lfaraone> micahg: well, it should be easy to special-case or have it check against a package list.
[18:21] <lfaraone> micahg: mk. for the sugarteam, we try when possible to always go through debian and only fix what we must in Ubuntu.
[18:22] <micahg> lfaraone: yeah, but I don't think that's wanted in general
[18:22] <micahg> lfaraone: maybe then the maintainer should be set in Debian as the sugarteam?
[18:22] <micahg> lfaraone: if that's feasible
[18:22] <tumbleweed> ari-tczew: hi
[18:22] <micahg> lfaraone: I have to go, I'll be on later, but I'm sure others have an opinion on this :)
[18:23] <lfaraone> micahg: in Debian, we have "Debian OLPC<EMAIL_ADDRESS>[18:23] <micahg> lfaraone: ah, well, then, nothing is really being "maintained" per se in Ubuntu
[18:23] <ari-tczew> tumbleweed: hi, do you know how doing a merge by bzr?
[18:23] <ari-tczew> bzr-merge sucks, too hard to use for me
[18:23] <micahg> lfaraone: I think maintainer is more for the core pacakge than the small changes Ubuntu makes
[18:24] <tumbleweed> ari-tczew: for merging new versions from Debian, don't use UDD, it's more work than MOM
[18:25] <Laney> is it?
[18:25] <micahg> lfaraone: there's probably a thread on ubuntu-devel about this already in the archives
[18:25] <tumbleweed> ari-tczew: if you really want to (but I wrote this for reviewing more than for merging), try my grab-udd-merge: lp:~stefanor/ubuntu-dev-tools/grab-udde-merge
[18:25]  * micahg is out for a but
[18:25] <tumbleweed> Laney: I find it to be more work :)
[18:25] <micahg> *bit
[18:25] <nigelb>  tumbleweed I thought it would be easier doing it via uud
[18:25] <tumbleweed> nigelb: MOM gives you everything you need to see what's going on
[18:25] <ari-tczew> tumbleweed: "new versions from Debian", do you mean new upstream release?
[18:26] <tumbleweed> with UDD you have to know bzr quite well to extract diffs
[18:26] <ari-tczew> hmmm, I think how do a merge to show a debian-ubuntu patch by bzr
[18:26] <tumbleweed> ari-tczew: I mean new versions from debian, not -0ubuntu1
[18:27] <tumbleweed> ari-tczew: err, lp:~stefanor/ubuntu-dev-tools/grab-udd-merge (that was a typo)
[18:28] <hyperair> what's udd?
[18:28] <tumbleweed> !udd | hyperair
[18:28] <tumbleweed> meh, hyperair: wiki.ubuntu.com/UDD
[18:28]  * hyperair waits
[18:28] <hyperair> okay thanks
[18:29] <hyperair> aah distributed development.
[18:29] <hyperair> i know that acronym.
[18:30] <hyperair> i mean i know the term, but not the acronym.
[18:30] <tumbleweed> of course there's also udd.debian.org, which is something completely different
[18:32] <ari-tczew> tumbleweed: my work on merges with bzr is following: prepare a clean and ready for upload a patch debian-ubuntu, then do a debdiff between current -XubuntuY and new merge -XubuntuY, then bzr branch current ubuntu dev, then patch -p1 new merge -
[18:32] <ari-tczew> XubuntuY into bzr dev-release directory
[18:33] <tumbleweed> ari-tczew: so you are saying you use the MOM method, then you apply it to a bzr UDD checkout?
[18:35] <ari-tczew> tumbleweed: yes
[18:36] <ari-tczew> but my procedure is not good, because it's loosing merge log revision
[18:36] <geser> why not directly merge with bzr (if the package branches are up-to-date)?
[18:36] <tumbleweed> geser: that's what the script I pointed ari-tczew does (and it checks that thye are up-to-date)
[18:36] <ari-tczew> because it's giving some errors and I;m looking for help
[18:37] <tumbleweed> ari-tczew: what errors?
[18:39] <geser> tumbleweed: I've mentioned your script in bug #607727. It this branch ready for merging into u-d-t trunk?
[18:39] <tumbleweed> geser: it could use some testing :)
[18:39] <tumbleweed> I use it for reviews
[18:39] <tumbleweed> (because reviewing bzr merges is a nightmare)
[19:13] <ari-tczew> sorry for the late
[19:14] <ari-tczew> tumbleweed: I can test your scirpt
[19:20] <shadeslayer> is it even remotely possible to get pbuilder show the download speeds of packages and remaining time?
[19:20] <shadeslayer> i have a slow connection and would like this info to be displayed....
[19:21] <ari-tczew> tumbleweed: can I copy your script grab-udd-merge to /usr/bin and use script anywhere?
[19:21] <tumbleweed> yes
[19:22] <tumbleweed> (although normally one puts things like that in ~/bin)
[19:25] <ari-tczew> ok, give me 5-10 minutes
[19:27] <ari-tczew> tumbleweed: bzr: ERROR: There are conflicts in the working tree. You must resolve these before building.
[19:27] <tumbleweed> ari-tczew: then you need to do that :)
[19:31] <ari-tczew> tumbleweed: is it your own script?
[19:31] <tumbleweed> ari-tczew: yes, but there's not exactly very much of that. That error you pasted is a normal bzr conflict
[19:32] <ari-tczew> tumbleweed: hmm, is it possible to improve script by patches like in MoM?
[19:33] <tumbleweed> patches like in Mom?
[19:33] <ari-tczew> yes
[19:33] <tumbleweed> I'm not understanding, what do you mean
[19:34] <ari-tczew> tumbleweed: for example, do grab-merge commons-io
[19:34] <ari-tczew> and go to directory downloaded
[19:35] <ari-tczew> you will see patches: commons-io_1.4-3.patch and commons-io_1.4-2ubuntu1.patch
[19:35] <ari-tczew> then I can see what changes are exist in Ubuntu right now
[19:35] <tumbleweed> right. It doesn't generate those, but you can get them out of bzr easily enough
[19:35] <tumbleweed> that's probably the next thing that should be added
[19:35] <ari-tczew> nice
[19:37] <ari-tczew> tumbleweed: ok, what's directory called "build-area"?
[19:37] <tumbleweed> that's where the merge is
[19:38] <ari-tczew> tumbleweed: files are repeated in main directory and in build-area
[19:38] <ari-tczew> is it correct?
[19:38] <tumbleweed> I don't know what you mean
[19:41] <ari-tczew> tumbleweed: ok, I've commons-io by your script
[19:41] <ari-tczew> I go to commons-io directory
[19:42] <ari-tczew> e.g. I see file commons-io_1.4.orig.tar.gz in head directory (commons-io) and in build-area
[19:42] <tumbleweed>  oh, build area, sorry I thought you said merge-area
[19:42] <tumbleweed> yes, that's normal bzr-buildpackage behaviour
[19:42] <tumbleweed> it does the build in build-area, and then puts the result in ..
[19:43] <ari-tczew> ok tumbleweed, I put command: bzr diff
[19:44] <tumbleweed> in the merge area, bzr diff will give you the diff to the previous ubuntu version.
[19:44] <tumbleweed> if you want the diff to debian, do bzr diff -rbranch:../debian
[19:46] <ari-tczew> ehh, Stefano, I promise that I'll come back to your script. Now I'll prepare some merges in clasic method :P
[19:47] <tumbleweed> cool, then I can go out (it's friday night) :)
[20:10] <geser> shadeslayer: doesn't the apt inside pbuilder show you that info?
[20:10] <shadeslayer> geser: no :(
[20:10] <shadeslayer> only the file its downloading
[20:11] <shadeslayer> geser: does it show you the info?
[20:11] <shadeslayer> ( im usinge pdebuild )
[20:11] <geser> I never used pdebuild so can't tell about it, but pbuilder shows it for me (more precisely apt shows it)
[20:12] <shadeslayer> hmm
[20:12] <geser> and I don't remember configuring something for it
[20:13] <geser> using apt in your normal system does show it or not?
[20:14] <shadeslayer> it does
[20:14] <shadeslayer> but in pdebuild it just shows the size of the file and the name of the file
[20:15] <geser> hmm, I don't currently something to test with
[20:16] <geser> and I cache the debs with apt-cacher-ng so I can re-use the debs for my updating my maverick and my maverick pbuilder, so it's pretty fast if they are in the cache
[20:21] <shadeslayer> hmm
[20:22] <geser> it sometimes takes some time till the download speed and remaining time show up
[20:22] <geser> especially with many small debs
[20:23] <shadeslayer> geser: btw will you be around for another 45 mins?
[20:24] <geser> sure, I should be around for the next 2-3 hours before I head to bed
[20:24] <shadeslayer> ok good.. :D
[20:24] <shadeslayer> then you can sponsor some stuff for me ^_^
[20:25] <shadeslayer> geser: https://edge.launchpad.net/ubuntu/+source/kdevplatform <<
[20:25] <shadeslayer> there was a new release...
[20:26] <ari-tczew> which package should exist in B-D? python2.6 or python2.6-dev ?
[20:26] <geser> ari-tczew: depends on the package
[20:28] <shadeslayer> geser: can you upload to main too?
[20:28] <geser> shadeslayer: no, I'm not a core-dev
[20:29] <shadeslayer> aww... :(
[20:30] <vish> geser: hi , you maintain cheese in debian , right?
[20:31] <geser> vish: no, why should I?
[20:31] <vish> geser: oh ,nvm then..  I'v mixed up the maintainer name :)
[20:34] <ari-tczew> geser: package miro, now ubuntu depends on python2.6 but debian on python2.6-dev. can I use depend from Debian?
[20:35] <micahg> ari-tczew: don't worry about miro
[20:36] <micahg> ari-tczew: it needs to be redone w/webkit
[20:36] <micahg> ari-tczew: unless you want to update it to use webkit w/3.0.2 :)
[20:37] <ari-tczew> micahg: I want to merge it
[20:37] <ari-tczew> after merge I think you can do a transition
[20:37] <micahg> ari-tczew: I'm saying use your time more productively
[20:37] <micahg> ari-tczew: the package needs an update first
[20:37] <micahg> ari-tczew: and it might not happen in Debian in time
[20:38] <micahg> ari-tczew: are you familiar with webkit packaging?
[20:38] <shadeslayer> geser: kdevplatform will appear here https://edge.launchpad.net/~rohangarg/+archive/experimental
[20:38] <ari-tczew> micahg: no.
[20:39] <shadeslayer> geser: let it build first tho ^_^
[20:39] <shadeslayer> so that i can confirm it builds on buildd as well
[20:40]  * micahg should update MOM for miro
[20:40] <micahg> ari-tczew: I just added a message
[20:41]  * micahg should really file a bug and link that...
[20:41] <geser> shadeslayer: have you tried to find a sponsor in the kubuntu channels? As I don't anything about KDE and its packaging I try to avoid uploading KDE packages (if it's more than a simple change)
[20:41] <micahg> maybe blueyed would be kind enough to do the update :)
[20:41] <shadeslayer> geser: nope.. ill ask there then :D
[20:42] <ari-tczew> micahg: injury that scarcely right now
[20:42] <micahg> ari-tczew: ?
[20:42] <micahg> ari-tczew: I'd rather turn your merge request into an update request (which would turn into a sync request if it happens in Debian)
[20:44] <micahg> ari-tczew: It's currently a xul rdepend and I don't want to keep it that way for maverick
[20:47] <micahg> ari-tczew: is that ok with you if I hijack your merge bug to become an update (hopefully sync) bug?
[20:47] <micahg> ari-tczew: or did you already do the work?
[20:48] <ari-tczew> micahg: I have a ready patch to upload for merge.
[20:49] <micahg> ari-tczew: ok, go ahead and attach and I'll review and upload this weekend
[20:49] <ari-tczew> micahg: so merge is possible?
[20:49] <micahg> ari-tczew: possible, yes, worth the time, no, but if you did it, that's moot :)
[20:50] <ari-tczew> micahg: do you have upload permissions for miro?
[20:50] <micahg> ari-tczew: yes
[20:50] <ari-tczew> as mozilla management?
[20:50] <micahg> ari-tczew: yeah, since it's a xul rdepend
[20:51] <ari-tczew> nice!
[20:51] <micahg> ari-tczew: but that's why I want it updated, so I don't have to wrory about it :)
[20:51] <micahg> or rather, don't have to worry about porting mid-cycle to a new xulrunner
[20:51] <ari-tczew> micahg: I'm pedantic and I'd like to have a clear situation - fresh package merged, then do a necessary changes like webkit transition
[20:52] <micahg> ari-tczew: heh, I think I'm more pragmatic, if an update is coming, save the merge and work on something else
[20:52] <micahg> to each his/her own :)
[21:00] <ari-tczew> micahg: debdiff attached
[21:03] <micahg> ari-tczew: k, it'll probably get uploaded sometime UTC Sunday
[21:03] <micahg> ari-tczew: thanks :)
[21:04] <ari-tczew> micahg: np
[21:13] <kelelsai> I'm brand new to developing here and will be starting in the papercuts section of programming and was wondering what you guys recommended for an IDE or text editor
[21:14] <kelelsai> im familiar with eclipse and emacs
[21:14] <kelelsai> but was wondering what else you guys use
[21:15]  * iulian uses vim.
[21:16]  * hyperair uses emacs.
[21:16] <hyperair> debian-changelog-mode is really awesome.
[21:17] <kelelsai> I've used vim quite a bit. I like it as well
[21:17] <kelelsai> thanks for the recommendations guys
[21:17] <kelelsai> or gals
[21:17] <kelelsai> either way
[21:22]  * directhex uses monodevelop
[23:10] <ari-tczew> jdong: could you review bug 464175 it's a sru
[23:20] <ari-tczew> does ubuntu has got configured variable PYTHON_VERSION ?
[23:31] <km0r3> ari-tczew: an environment variable, you mean?
[23:32] <ari-tczew> km0r3: yea
[23:33] <km0r3> ari-tczew: printenv | grep -i python
[23:33] <km0r3> ari-tczew: this yields only my Python path
[23:33] <km0r3> s/Python path/PYTHONPATH
[23:33] <km0r3> means: no
[23:34] <km0r3> ari-tczew: perhpas you were seeking something else?
[23:35] <ari-tczew> km0r3: qcake package has got in code: unix:PYTHON_VERSION=
[23:36] <km0r3> ari-tczew: what is qcake?
[23:36] <km0r3> (url)
[23:37] <ari-tczew> km0r3: https://launchpad.net/ubuntu/+source/qcake/+changelog
[23:37] <km0r3> ari-tczew: I'll look into it
[23:40] <km0r3> ari-tczew: show me where exactly in the code
[23:40] <km0r3> ari-tczew: you gave me a changelog
[23:41] <ari-tczew> km0r3: get the debian package (pull-lp-source qcake)
[23:41] <ari-tczew> go to downlaoded directory
[23:41] <ari-tczew> debian/patches/05_use-default-python
[23:42] <km0r3> ari-tczew: does this answer your question<EMAIL_ADDRESS>[23:42] <km0r3> sorry
[23:42] <km0r3><EMAIL_ADDRESS>[23:43] <ari-tczew> km0r3: hmm in above link Jakub Wilk has attached a patch with: + unix:PYTHON_VERSION=$$(PYTHON_VERSION)
[23:44] <ari-tczew> but Debian's patch has got: + unix:PYTHON_VERSION=
[23:44] <ari-tczew> in Ubuntu we have + unix:PYTHON_VERSION=2.6
[23:45] <km0r3> ari-tczew: I think you should ask the qcake devs, because I cannot tell you that for sure.
[23:46] <ari-tczew> km0r3: anyway, thanks for help
[23:46] <km0r3> ari-tczew: you're welcome :)


[12:34] <gasbag> Pricey: hi.  No help needed here tnx.  I have an #ubuntu-ops tab because I got kicked awhile back due to my router.  Tnx anyway!
[03:36] <capiCrimm> can I be tested?
[03:41] <nalioth> sure
[03:41] <capiCrimm> am I good?
[03:42] <nalioth> capiCrimm: test complete, you can rejoin #ubuntu now, and thanks for your patience  :)
[03:42] <capiCrimm> thank you.
[03:46] <capiCrimm> I still can't join #ubuntu, getting redirected. :\
[03:46] <nalioth> interesting
[03:47] <nalioth> i don't see any bans against you.  where are you being redirected to?
[03:47] <capiCrimm>  #ubuntu-read-topic
[03:47] <nalioth> i removed the ban in #ubuntu
[03:47] <nalioth> and don't see any others
[03:48] <capiCrimm> sounds like fun. I'll try reconnecting.
[03:49] <capiCrimm> nope
[03:50] <nalioth> i'm not seeing any other bans against you
[03:53] <capiCrimm> I asked in #freenode
[03:54] <nalioth> really none of their business in there
[04:08] <mneptok> capiCrimm: one moment
[04:09] <mneptok> capiCrimm: try again, please
[04:09] <capiCrimm> fixed, thanks
[04:10] <mneptok> np np. thanks for being patient.
[04:10] <nalioth> aha! that tonyyarusso again
[04:49] <mneptok> city sky comes down like rain from all the alleys to the sea. i hear her footsteps getting louder, i'm drowning in my sleep. painted lies on painted lips promise "heaven tastes like this." i don't believe that i believed in you. all that money wants.
[05:29] <ubotu> bruenig called the ops in #ubuntu
[05:33] <nalioth> klined
[05:33] <nixternal> thank you
[05:34] <tonyyarusso> I'll remove those after my shower then.
[05:37] <ubotu> bruenig called the ops in #ubuntu
[05:37] <tonyyarusso> nalioth: more
[05:37] <nixternal> nalioth: they are back
[05:37] <nixternal> damn, I am slow
[05:37] <tonyyarusso> lol
[05:39] <nixternal> hehe, I got up to grab some cashews
[05:39] <mneptok> tonyyarusso: cleaned your old bans
[05:39] <tonyyarusso> mneptok: ty
[05:39] <mneptok> more towel time for you!
[05:39] <mneptok> snd pix kthx
[05:40] <tonyyarusso> gaaaaaaah
[05:41] <mneptok> and i thought we shared something special :(
[05:41] <nixternal> mneptok: you made me swallow my own vommit wth that one :)
[05:43] <mneptok> nixternal: at least it's your own.
[05:43] <nixternal> true
[05:45] <mneptok> http://www.youtube.com/watch?v=fKxbpo433Kk
[05:46] <nixternal> you know what is scary? I remember seeing that interview on VH1/MTV when it came out
[05:47] <mneptok> heh. i was 19 years old in 1984.
[05:48] <nixternal> I was a whopping 10 :)
[06:40] <ubotu> Jordan_U called the ops in #ubuntu
[08:29] <mneptok> http://tinyurl.com/36596d
[08:41] <Madpilot> mneptok, wonderfully tasteless. I dare you to wear one to the next Ubuntu con
[08:44] <mneptok> Madpilot: it would give someone a chance to kill me, and there are too many craving the opportunity
[09:05] <elkbuntu> mneptok, many of us had the chance in mt view and we didn't take the opportunity
[09:55] <ubotu> In #ubuntu, nomic said: ubotu stuff is so silly now can't even find the ibm install instructions for linux on their website
[11:51] <ubotu> Frogzoo called the ops in #ubuntu
[11:53] <ubotu> defrysk called the ops in #ubuntu
[11:53] <crdlb> :/
[01:35] <togr--> please test me for DCC exploit
[01:37] <togr_> please test me for DCC exploit
[01:37] <togr--> hmm, I guess freenode and ubuntu servers are on the same network
[01:38] <crdlb> yup :)
[01:38] <togr_> good to know
[01:43] <PriceChild> Hey togr
[01:44] <togr> looks like it was blocked
[01:44] <PriceChild> You may now rejoin #ubuntu, thanks for your patience :)
[01:44] <togr> "Received a malformed DCC request from PriceChild."
[01:45] <togr> thanks!
[03:02] <elkbuntu> well that was odd... hald-addon-stor just took my cpu hostage
[03:02] <elkbuntu> had to very slowly ssh in and kill it
[03:03] <Seeker`> elkbuntu: Do you mean ssh was slow, or you had to take a long time typing it in :P
[03:04] <elkbuntu> Seeker`, well... since 99% of the cpu was stolen by hald-addon-stor, both
[03:04] <elkbuntu> i dont even know what hald-addon-stor is
[03:04] <elkbuntu> but when the machine woke up, it said it could not eject something...
[03:22] <PriceChild> elkbuntu, better?
[03:23] <elkbuntu> PriceChild, the past 30 seconds have been fine, yes.
[03:23] <PriceChild> :)
[03:23] <elkbuntu> PriceChild, i think the problem started with update manager actually. it kinda disappeared whilst doing upgrades before, and the computer kinda went downhill from there
[03:23] <elkbuntu> it seems to be working fine now
[03:29] <ubotu> In #ubuntu-offtopic, invisiblepinkuni said: ubotu where is gobuntu?
[04:11] <effie_jayx> elkbuntu,  :D
[04:14] <elkbuntu> effie_jayx, :)
[04:16] <effie_jayx> Hobbsee,  leave him... don't wake him up
[04:16] <Hobbsee> awww
[04:17] <mc44> pah, you and your over branded pokey devices
[04:19] <Hobbsee> heh
[04:21] <Pici> better than branding you with a pokey device
[04:23] <Hobbsee> ooh, what an idea...
[04:29] <jussi01> lol
[05:52] <cachola> ola
[06:39] <ubotu> In #kubuntu-devel, jhutchins_lt said: !ops ubotu is missing in action on #kubuntu.  Thanks.
[06:40] <nalioth> ruh roh
[06:40] <fdoving> i was about to ask about that.
[06:40] <jussi01> me too
[06:40] <jussi01> lol
[06:40] <elkbuntu> accidental ban?
[06:40] <nalioth> not only that, but ubotu is not identified
[06:40] <nalioth> i suspect ubotu is not functioning normally
[06:41] <mc44> imposter ubotu!
[06:41] <elkbuntu> seveas needs to come back already
[06:41] <lamalex> there was just a bit netsplit
[06:41] <lamalex> that might be part of the problem
[06:41] <crdlb> I like that capitalization better :)
[06:41] <crdlb> "uBOTu"
[06:41] <elkbuntu> well, i dare say ubotu is in more than 20 channels, which one needs to be identified to overcome
[06:42] <fdoving> there should be a backup bot. or more than one, using the same DB.
[06:42] <crdlb> doesn't seem to be
[06:42] <crdlb> fdoving, there is
[06:42] <lamalex> whois ubotu only says hes in 2 channels
[06:42] <nalioth> fdoving: we have two backups
[06:42] <fdoving> nalioth: none in #kubuntu :)
[06:42] <elkbuntu> fdoving, there are a couple of backups, just a matter of keeping them separated, or they fight over factoids
[06:43] <nalioth> lamalex: you can't see all his info
[06:43] <lamalex> k
[06:43] <nalioth> i do not have control over ubotu
[06:43] <elkbuntu> nalioth, bring ubot3 in?
[06:44] <nalioth> it won't join all the channels ubotu is missing from
[06:44] <elkbuntu> it will join the essential ones though, right?
[06:44] <nalioth> no
[06:44] <elkbuntu> :-/
[06:44] <elkbuntu> what gives?
[06:44] <nalioth> earlier, it was found that ubotu was lagging while serving 5000 folks, so ubot3 took up the slack
[06:45] <nalioth> seveas has since rewritten it
[06:45] <nalioth> unfortunately, we don't know what channels ubotu is supposed to be in
[06:45] <fdoving> shouldn't it be easy to write a bot that will answer requests if ubotu is not present in the channel?
[06:46] <Pici> it should...
[06:46] <fdoving> that would be ubotu + two lines of code that checks if ubotu is present.
[06:46] <elkbuntu> nalioth, have you dispatched an email to seveas?
[06:47] <nalioth> i have not
[06:53] <nalioth> i've forgotten how to start a supybot
[06:54] <atoponce> anyone using Seveas' chanserv helper script?
[06:54] <elkbuntu> atoponce, most ops that use xchat do, why?
[06:55] <atoponce> i'm curious about the channel forward on a nick. how does that work? is it just an invite?
[06:55] <atoponce> /cs f
[06:55] <crdlb> it's a banforward
[06:56] <elkbuntu> otherwise we'd play pingpong with trolls
[06:56] <crdlb> so when they try to join the channel, they get sent to the channel you forwarded them too
[06:56] <atoponce> what's the syntax without the helper script? i'm writing some irssi aliases, mimicking his helper script
[06:56] <crdlb>  /mode +b hostmask!#channel
[06:56] <crdlb> err left out hte channel
[06:57] <nalioth> interesting.
[06:57] <nalioth> my upgrade to feisty didn't bring supybot with it
[06:57] <crdlb>  /mode #channel +b hostmask!#forwardchannel
[06:57] <atoponce> crdlb: ahh. ok. channel modes. perfect. thx
[06:57] <elkbuntu> nalioth, wouldnt that be fun, playing pingpong with neoxan :D
[06:58] <nalioth> atoponce: why mimic it? i have a link to the irssi script he based his chanserv.py on
[06:59] <atoponce> really? ahh. even better. i didn't know such a script existed
[06:59] <atoponce> link?
[07:00] <nalioth> http://rzlab.ucr.edu/debian/auto_bleh.pl_  atoponce
[07:00] <nalioth> atoponce: one should ask  :)
[07:01] <atoponce> heh
[07:01] <atoponce> nalioth: thx
[07:03] <Pici> I have a supybot... with encyclopedia running.  I'm not sure it could handle the load of all the ubuntu- channels though
[07:03] <gnomefreak> nalioth: whos bot is nnh_bot?
[07:03] <atoponce> looks like the auto_bleh script just creates a number of aliases anyway, rather than one dynamic alias. no?
[07:05] <nalioth> atoponce: i'm not sure
[07:05] <PriceChild> gnomefreak, i've seen that running around a bit, but doesn't speak so i left it alone :)
[07:06] <gnomefreak> well if you find out that nnh_bot is a bot and not one of ours you might want to get rid of it from #ubuntu. im gone again
[07:06] <PriceChild> atoponce, yes "i think"
[07:06] <nalioth> gnomefreak: no such nick
[07:06] <gnomefreak>  nnh-bot<EMAIL_ADDRESS>[07:06] <nalioth> ahh
[07:06] <gnomefreak> there better be
[07:06] <nalioth> you used an underscore
[07:06] <gnomefreak> ah
[07:06] <gnomefreak> sorry
[07:08] <nalioth> i no longer have control over ubot3
[07:09] <PriceChild> :S
[07:09] <PriceChild> *could sort something temporary out*
[07:14] <atoponce> crdlb: how can i get just the host from the nick?
[07:14] <crdlb> well chanserv.py uses /whois and /whowas
[07:15] <atoponce> irssi has special vars with $X, but that returns the user@host. for example:
[07:15] <atoponce> n=aaron@oalug/member/atoponce
[07:15] <atoponce> although that changed recently... odd
[07:17] <elkbuntu> yay nalioth!
[07:21] <nalioth> ubot3 now in #kubuntu and other channels
[07:21] <ubot3> nalioth: Error: I am only a bot, please don't think I'm intelligent :)
[07:23] <PriceChild> nalioth, and #ubuntu :)
[07:24] <elkbuntu> nalioth, let me guess, he doesnt have access to the fun stuff like larts?
[07:26] <PriceChild> those are seperate plugins aren't they...?
[07:27] <Pici> yes
[07:37] <nalioth> no fun stuff
[07:37] <nalioth> %join #ubuntu
[07:42] <Pici> nalioth: psst, its not there
[07:42] <PriceChild> wth was with that mas 104 error disconnect by them all...
[07:44] <nalioth> PriceChild: i'm looking into it (answer is: someone used ctcp to drop em all)
[07:45] <PriceChild> hehe yeah, I was just wondering where from, as i'm in most of the bigger channels so was wierd.
[07:51] <Pici> Thanks for ubot3 in #ubuntu
[07:52] <nalioth> let's hope it holds out
[07:56] <PriceChild> did you find out about that ctcp?
[07:57] <crdlb> Omnipresence
[07:58] <PriceChild> ubotu's resetting I think...
[08:01] <PriceChild> managed 5 channels...
[08:01] <Pici> Weird. I can't seem to whois it.
[08:02] <nalioth> it's reconnected but is in less channels than before
[08:05] <PriceChild> its going into more now...
[08:07] <Pici> uh
[08:07] <PriceChild> argh... excess flood
[08:07] <PriceChild> And now he has to start all over again :_)
[08:14] <PriceChild> freenode's not doing very well lately :S
[08:29] <Pici> ubotu seems to have recovered, perhaps ubot3 should be removed?
[08:30] <nalioth> perhaps a highlight, Pici
[08:30] <Pici> perhaps nalioth
[12:10] <ubotu> astro76 called the ops in #ubuntu
[12:18] <tomaw> Figured that if I am going to respond to !ops calls in #ubuntu it's perhaps polite to be here
[12:18] <nalioth> get out!
[12:18] <PriceChild> hehe :)
[12:18] <nalioth> :D
[12:19] <tomaw> haha


[00:25] <pochu> asac:  liferea (1.6.0~rc6-1) unstable; urgency=low
[00:39] <pochu> asac: there are a whole bunch of bugs to close in Ubuntu once 1.6~rc is uploaded
[00:39] <pochu> asac: they are all marked as fix committed, should be easy to close them all :)
[00:40] <pochu> asac: I haven't figured out what to do with the hildon patch yet... so I guess the package still needs merging
[01:19] <asac> pochu: drop it
[15:51] <maxb> Since the last karmic update to gtk+ (new upstream version 2.17.3), firefox's bookmarks sidebar is misbehaving for me during drag and drop
[15:51] <maxb> The drop target appears several rows above the actual position of the mouse pointer
[15:51] <maxb> Rolling back gtk+ fixes the issue
[15:51] <maxb> Anyone have any debugging hints for me?
[15:52] <artir> I think that's because the new client-side windows stuff
[15:52] <maxb> hmm?
[15:53] <artir> I saw a similar issue on a webpage, but i don't remember where
[18:09] <jagez> hello, I've written a patch for gdm that allows you to echo a command to .gdmfifo to make gdm login, and was wondering if ubuntu devs might like it to maybe go in ubuntu?
[18:25] <pochu> jagez: you echo a command to that file, and then gdm logins?
[18:25] <jagez> yes
[18:35] <jagez> then again, it could be pretty useless. I developed it against jaunty, and gdm in karmic looks very different
[18:39] <pochu> jagez: what's the rationale?
[18:42] <chrisccoulson> yes, gdm in karmic is a complete re-write
[18:42] <chrisccoulson> any features like that should probably be done via a DBus interface
[18:48] <jagez> pochu, 2 computers on a desk with only 1 mouse + keyboard, using synergy. I only need the keyboard to log the second machine in. Or... It could be used in a classroom to log all the stations in. KDM can do it, so whatever rationales it has :)
[18:48] <jagez> I'll hang on to it and err, learn dbus I guess
[19:04] <pochu> jagez: I'd propose such a change upstream


[18:14] <sgclark> wxl: ping, sorry to bother but two days out, one really. I need to know if I am going or not, folks want me to take stuff down for them.
[18:20] <wxl> sgclark: yes, you are.


[14:25]  * M_aD wonders why the volume buttons don't work on the lenovo thinkpad T410 with Studio. Tested a Xubuntu 19.04 live session and there was no problem with them.
[14:26] <M_aD> doh... was meant for the support channel... sorry
[14:38] <Eickmeyer> M_aD: There's a weird, known bug with xfce4-volumed. If you type "killall -9 xfce4-volumed && xfce4-volumed" it should fix that.
[14:40] <M_aD> Eickmeyer: thanks, that did it
[14:40] <Eickmeyer> I have a script that does that on login.
[14:58] <Eickmeyer> sakrecoer: Is there any chance we'll be able to have you help with testing your firewire devices so that OvenWerks can get the firewire settings right in Controls? Right now, you're the only person we have that can help with that. Neither OvenWerks nor I have Firewire.
[14:58] <Eickmeyer> That might be why it got neglected in Controls.
[15:01] <sakrecoer> sure! i suppose we would have to set a date :)
[15:01] <Eickmeyer> I'll leave that up to you two.
[15:04] <OvenWerks> "might be" he says...
[15:05] <Eickmeyer> OvenWerks: would "is" be a better term?
[15:06] <OvenWerks> It is also why when there is only USB devices things don't work quite right
[15:07] <OvenWerks> there are a coulple of things like that. Another is that pulse output device default to  hw:0 rather than jack master
[15:08] <OvenWerks> (which is not even right for my system)
[15:08] <Eickmeyer> OvenWerks: Are you seeing what sakrecoer is talking about in #ubuntustudio?
[15:09] <Eickmeyer> You might want to read some backlogs.
[15:11]  * Eickmeyer has to get his son ready for school, and then he has Linux Fest Northwest prep
[15:11] <OvenWerks> I just started... it looks about like I would expect so far.
[15:48] <sakrecoer> let me know whenever it works for you OvenWerks i'lldo my best to be available.
[15:48] <sakrecoer> Fridays and sundays are the best
[17:08]  * OvenWerks is off to breakfast with wife... back later
[17:09] <OvenWerks> Eickmeyer: the crash bug is what I will look for next
[17:09] <Eickmeyer> OvenWerks: Ok
[17:10] <OvenWerks> It may be enough to send dev as dev=",0,0"
[17:22] <Eickmeyer> We might need to make some sort of defaults file to keep qjackctl from autostopping Jack at close.
[17:22] <Eickmeyer> (probably a separate bug)
[20:10] <OvenWerks> Eickmeyer: I don't know how we would do that. It may be better to have autojack check if jack is running... nope, it generally kills jack before it starts it. The bigger problem is qjackctl killing jackdbus on close.
[20:12] <OvenWerks> Rosco2: can you check if changing line 367 from start_slave(dev) to start_slave(dev+",0,0")
[20:12] <OvenWerks> will fix your crash problem?
[20:13] <OvenWerks> Rosco2: sorry, that file is /usr/bin/autojack (you will need sudo)
[20:19] <OvenWerks> That is not a real fix BTW, just a hack for testing :)
[20:19] <OvenWerks> It may cause trouble somewhere else
[20:27] <Eickmeyer> OvenWerks: I'll look into whatever config files can be made. Something in ~/.config should be telling. Sadly, I can't do that at present as I'm packing for Linux Fest Northwest.
[20:32] <Rosco2> Sorry OvenWerks, I stopped for a gin an tonic - and it was a bit strong!
[20:33] <Eickmeyer> Whoops! Rosco2 is getting tipsy!
[20:33] <Rosco2> I just tried reproducing the crash before making the suggested changes and I couldn't.
[20:34] <Rosco2> I might try again tomorrow when I am less tipsy :-)
[20:34] <Eickmeyer> hehehe
[20:34] <Eickmeyer> Good to see you in the chats, Rosco2. :)
[20:35] <Eickmeyer> Wow, we've had Rosco2 and sakrecoer in IRC within 24 hours of each other!
[20:35]  * Eickmeyer is putting the band back together. On a mission from God. *wears shades and a suit*
[20:35] <Rosco2> You think it is staring jack with controls, opening Qjaclkctl, then quitting Qjackctl which stops Jack?
[20:36] <Eickmeyer> Rosco2: It might be, and then autojack is getting confused as it's looking at the configuration last left by Controls.
[20:36] <Eickmeyer> That's just speculation, though.
[20:36] <Rosco2> EIther I am dislexic - or drunk!
[20:37] <Eickmeyer> Or both? XD
[20:37] <Rosco2> One more try to crash it
[20:51] <Rosco2> Baah. Why is it you only crash when you don't want to crash?
[20:51] <Rosco2> I will sty the code tomorrow and try and work out how to crash it properly.
[20:51] <Rosco2> study
[20:52] <Rosco2> Nighty night!
[20:52] <Eickmeyer> Good night! o/
[20:59]  * Eickmeyer is out for the weekend, available sporadically
[20:59] <Eickmeyer> OvenWerks: If you need me, just ping me with a @ in front of my name and it'll ping me on Telegram.


[00:18] <jcastro> mhall119: ok so I found a lug
[00:58] <mhall119> jcastro: we have a loco team too
[00:58] <jcastro> yeah
[00:58] <jcastro> but nothing local to me afaict.
[00:59] <jcastro> maybe I can start the boca branch
[00:59] <mhall119> there's a few in the Miami area, though we've lost track of some of them
[00:59] <mhall119> RoAkSoAx is down there somewhere
[01:00] <jcastro> it's like 10 degrees cooler here than michigan
[01:00] <mhall119> yeah, I was just commenting to my wife about how weird it is for us to be cooler than the rest of the country at the end of July
[17:13] <mhall119> itnet7: what geocaching app do you use on Android?
[18:26] <DammitJim> what is geocaching?
[18:37] <mhall119> hide and seek with little containers and a GPS
[21:45] <jamalta> Hii
[21:55] <mhall119> hey jamalta
[21:55] <jamalta> mhall119: hey, how's it going?
[21:57] <mhall119> going good, how about you?
[21:57] <jamalta> not too bad
[21:58] <mhall119> how're things at Flickr?
[22:36] <jamalta> sorry, just saw this
[22:36] <jamalta> they're going good
[23:58] <jamalta> how are things at canonical? :)