[00:00] <slangasek> Q-FUNK: heh, those are unrelated to the network as well
[00:01] <Q-FUNK> slangasek: that's correct. :)
[01:13] <n0ti0nis> hi everyone
[01:18] <jk-> hey n0ti0nis 
[01:27] <n0ti0nis> im new to ubuntu kernel team :)
[01:27] <n0ti0nis> im new to ubuntu kernel team :)
[06:46] <tkamppeter> Can someone check whether the patch proposed on https://lkml.org/lkml/2011/9/25/57 is in our Oneiric kernel? The bug prevents many USB printers from being detected, see also http://www.cups.org/str.php?L3957.
[07:47] <jk-> tkamppeter: looks not to be applied to oneiric
[07:49] <tkamppeter> jk, can this get applied as an SRU for Oneiric?
[07:49] <tkamppeter> jk, I have even one of these printgers which do not get recognized.
[07:50] <jk-> tkamppeter: are you able to do the SRU proposal?
[07:50] <tkamppeter> jk-, ^^
[07:50] <tkamppeter> jk-, I have never patched the kernel, so it would be better that one of you makes the updated kernel package.
[07:51] <tkamppeter> jk-, I can only report a bug
[07:53] <jk-> tkamppeter: on the phone, just a minute
[07:56] <jk-> tkamppeter: you don't need to update the kernel package; just sending the patch to the kernel team list is sufficient
[07:57] <jk-> there's a doc on what you need to include, just a sec
[07:57] <jk-> tkamppeter: https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
[07:58]  * jk- looks for a good example
[07:58] <jk-> https://lists.ubuntu.com/archives/kernel-team/2011-October/017218.html
[07:59] <jk-> then, if the patch is suitable, the kernel folks will include that change in a -proposed kernel
[07:59] <jk-> they will ask you to test that, and report whether the new build fixes the problem
[08:01] <tkamppeter> jk-, I am preparing an SRU bug report currently. I will attach the patch to it and report the bug number here.
[08:04] <Q-FUNK> tkamppeter: the usb printer loading issue?
[08:05] <tkamppeter> jk-, bug 872711
[08:05] <ubot2> Launchpad bug 872711 in linux "Kernel does not report some USB printers correctly, making them not being detected by CUPS" [High,Incomplete] https://launchpad.net/bugs/872711
[08:06] <tkamppeter> Q-FUNK, yes.
[08:07] <tkamppeter> Q-FUNK, do you have some bug numbers of bugs reported on LP where USB printers did not get detected?
[08:07] <jk-> tkamppeter: great!
[08:08] <Q-FUNK> tkamppeter: I mostly remember repeated issues about this at Debian, sorry. We might have some on LP too, but I'm not monitoring those.
[08:08] <jk-> tkamppeter: I'd still suggest that you send the patch to the kernel-team list
[08:08] <jk-> tkamppeter: if you're able to.
[08:08] <jk-> if not, I'm happy to help you do that.
[08:09] <tkamppeter> Q-FUNK, References to Debian bugs are also OK. You can post directly into bug 872711.
[08:09] <ubot2> Launchpad bug 872711 in linux "Kernel does not report some USB printers correctly, making them not being detected by CUPS" [High,Incomplete] https://launchpad.net/bugs/872711
[08:09] <Q-FUNK> tkamppeter: ok
[08:15] <Q-FUNK> ogasawara: according to http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc9-oneiric/0003-default-configs.patch disabling vesafb was a deliberate change by kernel team. I wonder why.
[08:16] <Q-FUNK> ogasawara: +# CONFIG_FB_BOOT_VESA_SUPPORT is not set
[08:21] <stgraber> tgardner: http://paste.ubuntu.com/706557/
[08:21] <tkamppeter> jk-, mail sent.
[08:22] <jk-> tkamppeter: ^5
[08:22] <stgraber> tgardner: running that as root with arkose installed will give you a shell in a container that has a working network config using veth (point-to-point with the outside in the 169.254.x.x network)
[08:23] <tgardner> stgraber, thanks
[08:57] <Q-FUNK> tgardner: would you know anything about why vesafb is disabled on recent mainline kernels?
[08:59] <tgardner> Q-FUNK, not off hand. maybe its dependent on some config option thats not getting enabled by default.
[09:01] <Q-FUNK> tgardner: ok. it results in this:  [   44.192500] init: udev-fallback-graphics main process (668) terminated with status 1
[09:01] <tgardner> Q-FUNK, apw looks after this stuff. I expect he'll be back tomorrow.
[09:02] <Q-FUNK> tgardner: noted. thanks for the info.
[09:19] <amitk> Q-FUNK: i think it is for the a flicker-free boot
[09:20] <Q-FUNK> amitk: how so?
[09:21] <Q-FUNK> amitk: vesafb is the backup framebuffer, if no KMS-enabled framebuffer that mathces the hardware was found by udev.
[09:23] <amitk> Q-FUNK: right, I misread your comment. I remember reading about flicker-free here: http://web.dodds.net/~vorlon/wiki/blog/Free_as_in_flickers/
[09:25] <Q-FUNK> upstart: udev-fallback-graphics inserts vesafb if no framebuffer claimed the video output yet by the time udev is run during rcS.
[09:49] <tkamppeter> jk-, did my e-mail arrive?
[10:30] <tkamppeter> I have posted on kernel-team@lists.ubuntu.com, and I do not see my mail in the archives of the list (I am not subscribed) and I also did not get any response like that the mail needs to get moderated. Can someone look whether the mail arrived or moderate it through if needed?
[10:31] <tkamppeter> bjf, jk-, ^^
[10:31] <tkamppeter> bjf, jk-, it is about bug 872711.
[10:31] <ubot2> Launchpad bug 872711 in linux "Kernel does not report some USB printers correctly, making them not being detected by CUPS" [High,Confirmed] https://launchpad.net/bugs/872711
[10:46] <tgardner> tkamppeter, I'm moderating...
[10:51] <tkamppeter> tgardner, thanks. Can this get SRUed for Oneiric? Many people cannot print. And the patch seems to be upstream-approved, according to Andy Whitcroft in bug 872711.
[10:51] <ubot2> Launchpad bug 872711 in linux "Kernel does not report some USB printers correctly, making them not being detected by CUPS" [High,Confirmed] https://launchpad.net/bugs/872711
[10:52] <tgardner> tkamppeter, working on it.
[10:52] <tkamppeter> tgardner, thanks in advance.
[11:58] <n0ti0nis> hi everyone
[11:59] <n0ti0nis> 'im a newbie :) I need help, I don't know if I'm in the right place
[12:34] <tgardner> apw, kteam-tools/misc/ubuntu-repo-mirror
[12:39]  * apw looks
[12:47] <apw> tgardner, so why do you delete all the remotes and remake them, doesn't that just cause more downloading for no gain ?
[12:48] <tgardner> apw, nope. by deleteing the remote it also drops all of the branches, which forces the next fetch to get 'em all.
[12:48] <tgardner> plus the new HEADs
[12:49] <apw> but thats what i mean, why do we need to do that, a git fetch would update any changed ones no?
[12:49] <apw> and add any new ones
[12:49] <tgardner> apw, well, oterwise I've got to have some complicated code to decide what branches are new, as well as pull the new HEAD for _every_ branch. this way I get 'em all in one fetch. besides, it doesn't take long.
[12:50] <apw> but git fetch <remote> updates all branches on that remote anyhow including new ones?
[12:50] <apw> and u just push all the ones you have after the fetch right?
[12:51] <apw> so i don't see what you are gaining
[12:51] <tgardner> apw, I think of a local branch already exists with a remote, then your must 'git fetch REMOTE BRANCH' in order to get the branch HEAD updated.
[12:51] <tgardner> s/of/if/
[12:52] <apw> tgardner, you need to remake the local branches yes before you can push
[12:52] <apw> its the removal and readding of teh remote i don't get
[12:52] <apw> but those are separate phases in your script, and unrelated
[12:53] <tgardner> apw, its just a simple way to get all of the branches. besides, its hardly worth optimizing since its already quite fast
[12:54] <apw> if it was remote at my house, it'd not be fast thats for sure, as it would have to download the entire of each repo each time right?
[12:54] <tgardner> apw, oh, heck no. 
[12:54] <tgardner> perhaps if I prunes it might have to.
[12:54] <tgardner> pruned*
[12:54] <apw> we just seem to go to extra effort to remove the remotes
[12:55] <apw> and readd them, then just leaving them alone should do exactly the same thing
[12:55] <apw> yes the local branches need to be zapped and remade but ...
[12:55] <tgardner> apw, removing the remote is a shortcut that allows me to fetch all of the branch HEADS with one step
[12:56] <apw> but git fetch <remote> does that anyhow?
[12:56] <tgardner> not if the branch already exists locally.
[12:56] <tgardner> you have to 'git fetch REMOTE BRANCH'
[12:56] <apw> tgardner, no i do that all the time
[12:57] <tgardner> hmm, perhaps its pn newer versions ? Lucid and Maverick don't seem to
[12:57] <apw> the remote/xxx/foo branches are all updated together if you git fetch remote
[12:57] <apw> tgardner, are you sure?  that semantic seems to have been the same always in my memory
[12:58] <tgardner> apw, I have this problem all the time where I don't get an update unless I specifically fetch the branch
[12:59] <tgardner> apw, anyways, what I was really trying to point out is the combined git repository once you're done.
[13:00] <apw> tgardner, how big is it?
[13:00] <tgardner> apw, 1.7Gb
[13:00] <apw> i wonder if a git gc in there would make any diffference
[13:01] <tgardner> apw, I'll try it. 
[13:16] <tgardner> apw, after all that rust making I saved a whole 100M; 
[13:16] <tgardner> du -sh ../Ubuntu-kernel/
[13:16] <tgardner> 1.6G	../Ubuntu-kernel/
[13:21] <n0ti0nis> hi all, I compiled a version of linux kernel (taken from git repo), I have no .changes file, how can i upload it to my PPA?
[13:50]  * ogasawara back in 20
[13:52] <apw> ppisati, you mentioned on one of your CVE submissions that there were two upstream commit ids mentioned but that one superceeded the other, can you remind me which cve it was so i can correct the tracker
[13:53] <sgs2_usr> i have problem with getting my HP EliteBook 8540w docking station to work on the sound output connected to the back of the docking station, anyone can help?
[13:54] <apw> sgs2_usr, have you filed a bug?  that gets all the info someone needing to look at it requires, i think its ubuntu-bug alsa-driver
[13:54] <sgs2_usr> apw: where do i file the bug? #ubuntu-bug?
[13:55] <apw> in launchpad, but run "ubuntu-bug alsa-driver" in a terminal window
[13:55] <sgs2_usr> apw: launchpad? im using gnome classic
[13:56] <apw> launchpad is the bug tracker
[13:56] <apw> from a terminal run the command "ubuntu-bug alsa-driver"
[13:56] <sgs2_usr> apw: i issued the command and it says "alsa driver not installed"
[13:56] <sgs2_usr> apw: more specifically, it says Package alsa-driver does nto exist
[13:57] <apw> it may be plural, alsa-drivers
[13:58] <sgs2_usr> apw: nope, didn't work
[13:58] <ppisati> apw: http://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-2517.html
[13:58] <ubot2> ppisati: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2517)
[14:10] <tgardner> ogasawara, you gonna push til's patch ?
[14:11] <ogasawara> tgardner: yep i can do it
[14:11] <tgardner> I can do it if you're busy
[14:11] <ogasawara> tgardner: nope should be easy since i already applied it.  was just gonna wait for his test results
[14:12] <tgardner> ogasawara, ack, then I'll go back to CVE patches
[14:13] <apw> sgs2_usr, ok  it seems to have changed to 'ubuntu-bug audio' go figure
[14:13] <sgs2_usr> apw: okay, let me try that :)
[14:14] <sgs2_usr> apw: yes, it's working ,but it prompt with many options, which one do i choose?
[14:14] <sgs2_usr> apw: okay,i think the closest is the first option: Black Headphone Out, Rear, Docking station (internal Audio - HDA Intel)
[14:15] <sgs2_usr> apw: okay, reported the problem...
[14:15] <sgs2_usr> apw: so what do i do next? wait for the bugfix?
[14:16] <apw> that should get it to the people who understand audio routing
[14:16] <apw> hopefully they will ask you more specific questions on the bug once the see it
[14:17] <sgs2_usr> apw: how do they contact me?
[14:17] <apw> they'll update the bug which will email you
[14:17] <sgs2_usr> apw: cool!!!
[15:22] <ppisati> cve 2479: does it really affect hardy|lucid|maverick? we don't even have the hugepage/vm flag VM_HUGEPAGE in those kernels
[15:22] <ppisati> bug 869230
[15:22] <ubot2> Launchpad bug 869230 in linux-lts-backport-natty "CVE-2011-2479" [Medium,Fix committed] https://launchpad.net/bugs/869230
[15:22] <hallyn_> tgardner: tangerine's oneiric-amd64 dchroot no lnoger has ncurses-dev, and doesn't let me sudo apt-get install?
[15:48] <tgardner> hallyn_, shit, I think I forgot to add it to the chroot setup, and the chroot got recreated because of archive inconsistencies awhile ago. gimme a minute.
[15:53] <hallyn_> tgardner: thanks!
[15:54] <tgardner> hallyn_, done
[15:56] <tgardner> sconklin: is something out of sync ?
[15:56] <tgardner> The following packages have been kept back:
[15:56] <tgardner>   linux-image-server-lts-backport-natty
[15:57] <sconklin> tgardner: kept back where?
[15:58] <tgardner> sconklin, I was just trying to update gomeisa. the error means one of the meta packages references a kernel package that does not yet exists
[15:58] <tgardner> I thought all of these packages were copied lock-step from the non-virt PPA
[15:58] <sconklin> I'll check, that's what I thought also
[16:01] <sconklin> tgardner: which version? -proposed or updates? specific version is better :-)
[16:02] <tgardner> sconklin, I pasted the error as it appears. likely from -proposed though. hang on a sec and I'll check.
[16:02] <tgardner> sconklin, yep, -proposed is enabled
[16:03] <sconklin> ack
[16:19] <sconklin> tgardner: it looks like they all made it into the PPA ok, so perhaps it was a copy error
[16:19] <sconklin> there have been a number of those recently
[16:20] <tgardner> sconklin, archive admin scripting ?
[16:21] <sconklin> tgardner: I have no idea, I have zero visibility to how they do their work
[16:21] <tgardner> sconklin, but its definitely an archive admin issue, right ?
[16:22] <sconklin> I am looking now to confirm that the package is not in the archive. I just always have to root around to figure it out
[16:22] <bjf> tgardner: which version is currently installed on that system ?
[16:22] <bjf> tgardner: i guess i could log on and look myself :-)
[16:23] <tgardner> bjf, 2.6.38-11-server
[16:35] <tgardner> jjohansen, do you have a smack down session scheduled for ecryptfs at  UDS ?
[16:35] <kirkland> tgardner: tyhicks does, I know
[16:36] <jjohansen> tgardner: there is a session
[16:36] <kirkland> tgardner: not sure I like the smackdown hashtag though :-P
[16:36] <tgardner> jjohansen, good. you guys _have_ to figure out the long file name design .
[16:36] <kirkland> +1
[16:36] <jjohansen> tgardner: yep
[16:36] <tyhicks> tgardner: https://blueprints.launchpad.net/ubuntu/+spec/security-p-ecryptfs
[16:37] <tgardner> cool, subscribed
[16:50] <sconklin> tgardner: I PM'd you
[17:58] <broder> is bugzilla.kernel.org still down from the compromise? i got a comment on a bug punting me there, but it won't load :)
[18:10] <pmatulis> how come we do not enable kdump by default?
[18:12] <mdeslaur> so...is oneiric's kernel actually 3.0.0 or has it been rebased to 3.0.6 or something?
[18:12] <mdeslaur> ah, 3.0.4 says /proc/version_signature
[18:12] <mdeslaur> ignore me
[18:40] <bjf> ogasawara: are we going to go to 2 digit kernel version for Precise ?
[18:40] <ogasawara> bjf: dunno, probably have to discuss at UDS
[18:40]  * jjohansen -> lunch
[18:40] <ogasawara> bjf: the 3 digit seems to be the less painful route
[18:41] <bjf> ogasawara: but it's sort of confusing because it's different from upstream
[18:57] <Q-FUNK> ogasawara: good evening. would you happen to have found any answer as to why mainline kernels currently don't offer vesafb?
[19:07] <ogasawara> Q-FUNK: sorry, haven't had a chance to look.  I'll have to check with apw tomorrow when he's around.
[19:16] <Q-FUNK> ogasawara: noted. thanks!
[19:37] <popey> uhm, i am trynig to install a mainline kernel as per https://wiki.ubuntu.com/Kernel/MainlineBuilds to debug bug 864750
[19:37] <ubot2> Launchpad bug 864750 in linux "Realtek R8111E not working in Oneiric" [Undecided,Confirmed] https://launchpad.net/bugs/864750
[19:37] <popey> it says I should look at the mapping table at http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
[19:37] <popey> but this doesn't have oneiric in it, 3.0.0-12-generic is my kernel, which one should I get?
[19:44] <bjf> popey, it says "Most likely that you want to download and test against the most current version." and "current" is a link to: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[19:44] <popey> I'm not sure I do want current tbh
[19:44] <popey> but I'll give that a punt, thanks