[07:55]  * abogani waves!
[08:07] <smb> morning
[08:08] <jj-afk> morning
[08:30]  * apw yawns
[08:30]  * smb wonders whether he should give apw virtual coffee. :)
[08:31]  * apw looks blearily at his real tea
[08:31] <RAOF> See, there's your problem.
[08:31] <jk-> RAOF: lol
[08:31] <RAOF> Tea is very sensitive; looking blearily at it can only result in tears!
[08:40] <apw> the trade off is the risk of dropping the tea in my lap due to tiredness induced incompetance against the restorative effects of the contents ...
[08:41] <smb> At least you would be awake then
[08:41] <RAOF> Dropping tea in your lap would certainly provide a temporary buff to attentiveness.
[08:41] <jk-> apw: on the other hand, that would wake you up
[08:41] <jk-> snap * 2
[08:41] <smb> three minds one thought
[08:41] <apw> thats not the kind of awake i approve of
[08:42] <jk-> it's the kind of slapstick we approve of, though
[08:42] <RAOF> You haven't been fitted with the special Canonical underwear I take it then?
[08:45] <smb> Actually, wasn't that fortified on the opposite side only? :-P
[09:02] <apw> heheh
[09:43] <JFo> apw, should I be showing you guys any kino bugs or do we care about those?
[09:43] <apw> kino ?
[09:44] <JFo> yeah...
[09:44] <JFo> one sec.
[09:44] <JFo> bug 6290
[09:44] <ubot2> Launchpad bug 6290 in baltix (and 1 other project) "DV capture over Firewire is broken (no rights for /dev/raw1394) (affects: 41) (dups: 10) (heat: 306)" [Undecided,New] https://launchpad.net/bugs/6290
[09:45] <JFo> doubt it has to do with us but there was a legacy team group subscribed to the bug
[09:45] <JFo> I've unsubscribed it
[09:45] <JFo> but I have no clue what kino is
[09:46] <apw> JFo, i would guess its a codename ... but given the age of that bug we are not interested anyhow, its like dapper time isn't it ?
[09:46] <JFo> yeah, I think they need to open a new bug
[09:46] <apw> oh its an app, but the age is the key here i ithink
[09:46] <JFo> k
[09:47] <apw> if they are reporting on that one ... i'd get a fresh one opened
[09:47] <JFo> will read through it then and decide what is needed
[09:47] <JFo> cool
[09:47] <ogra> it the typical DV capture tool 
[09:47] <JFo> thanks :)
[09:47] <ogra> and is the one app that always exposed the brokeness of the FW stack
[09:48] <ogra> JFo, given that there are recent comments from users that it is fixed for them, i'd set it to fix released no matter how old it is
[09:49] <JFo> k, that was what I was thinking too
[09:50] <apw> JFo, i think that bug can just be left alone
[09:50] <apw> its mostly (in this year timeframe) about switching to the new firewire stack and that being a good thing
[09:50] <JFo> apw, ok
[09:50] <JFo> yeah saw that
[09:50] <apw> as we have done that in maverick i suspect it is fixed in maverick from the user perspective, but not 100% sure how to be sure
[09:50] <JFo> just not sure who is responsible for kino
[09:50] <apw> as if it was we could close it there
[09:51] <apw> JFo, as it seems to be an app, not us :)
[09:51] <JFo> heh
[09:51] <JFo> my thoughts exactly
[09:51] <ogra> apw, its a kernel prob
[09:51] <JFo> it was the reason I had no issue removing that group subscribe
[09:52] <apw> ogra, if its a kernel problem then it should be filed against the kernel
[09:52] <apw> ogra, can you elucidate on the problem? as noone in the bug seems to be helping me
[09:52] <ogra> apw, and if the new firewire stack fixes it i'D close it, else it stays open forever
[09:52] <ogra> apw, its the permissins of the firewire device
[09:52] <ogra> *permissions
[09:53] <ogra> which i thought the new firewire stack fixes
[09:53] <apw> as in the the unix permissions or something deeper
[09:53] <ogra> unix permissions and something deeper :)
[09:53] <apw> so it might be worth asking for testing on maverick as the stacks are switched
[09:53] <ogra> the permissins are only set that way because its the only safe way
[09:54] <ogra> (by design)
[09:54] <apw> and if its a kernel problem it should have a kernel task so we can close that Fix Released on Maverick, and Won't Fix (you have a workaround) on Lucid
[09:55] <ogra> i would ask the last three commenters if they use maverick
[09:55] <ogra> and if so, close it
[10:09] <apw> JFo, ok read the whole bug and it does seem to be a case of, old kernel stack has no sane permissions model, new stack does.  old stack therefore is prevents access without being root, new should not
[10:09] <apw> therefore .... will add linux tasks for lucid and maverick and close this in maverick kernel side
[10:10] <JFo> ok
[10:10] <JFo> sounds god to me
[10:10] <JFo> good*
[10:10] <apw> and actually in lucid too, as we are not going to change the default there
[10:10] <JFo> right
[10:10] <JFo> since the new stack is Mav only yes?
[10:10] <apw> will close that won't fix, but wth the appropriate comments about the workaround to switch the stack
[10:11] <diwic> Out of curiousity, I run Lucid on one machine here but with the Maverick backport kernel, am I running 1) the old FW stack 2) the new FW stack 3) some weird combination
[10:12] <JFo> diwic, the maverick backport kernel is not supported on desktpo ;)
[10:12] <JFo> heh
[10:12] <JFo> desktop*
[10:12] <JFo> what is with my spelling to day?
[10:12] <diwic> JFo, it does exist in the generic flavour though
[10:12] <JFo> exist yes....:)
[10:13] <diwic> JFo, and so far it has been working better than the Lucid one, graphics-wise
[10:13]  * JFo picks on diwic 
[10:47] <jk-> hey JFo
[10:48] <JFo> heya jk- 
[10:50] <jk-> JFo: saw your update on 584812; just waiting for feedback from Jerone..
[10:51]  * JFo goes to look
[10:51] <JFo> ah yeah
[10:51] <JFo> wanted to get the guys to take a look at it too during the weekly chat
[10:52] <JFo> would you rather I wait on that jk- ?
[10:52] <jk-> apw knows about it, once it's been tested I'll forward the config change to k-t for review
[10:52] <JFo> since I see that you have a test build that may take care of it
[10:52] <JFo> coolness
[10:52] <JFo> may just want to put on the hot list
[10:52] <JFo> good deal :)
[10:56] <apw> bug #584812
[10:56] <ubot2> Launchpad bug 584812 in linux (Ubuntu Maverick) (and 4 other projects) "uinput kernel module is not loaded automatically (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/584812
[10:57]  * apw has seen that yes
[11:00] <JFo> :)
[15:03]  * smb needs to run some errands. bb later
[15:24] <bjf> ##
[15:24] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:24] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[15:24] <bjf> ##
[15:52] <pgraner> tgardner, lag: call in 10...
[15:52] <lag> pgraner: ack
[15:52] <lag> pgraner: Mumble?
[15:52] <pgraner> lag, yep
[15:53] <JFo> pgraner, I completely forgot to schedule myself
[15:53] <pgraner> JFo, dooh!
[15:53] <JFo> heh
[15:53] <tgardner> pgraner, ack
[15:54] <pgraner> JFo, we can do it next week when your back
[15:54] <JFo> k
[16:24] <JFo> apw, you still around?
[16:24] <apw> yep
[16:30] <JFo> smb are you around?
[16:32] <JFo> in the event that you are. would you have a look at bug 546091
[16:32] <ubot2> Launchpad bug 546091 in linux (Ubuntu) "10.04 Installer doesn't properly detect 9240 MegaRaid SAS Controlers (affects: 8) (heat: 72)" [Undecided,New] https://launchpad.net/bugs/546091
[16:33] <JFo> think that could be caused by an old driver?
[16:37] <smb> JFo, Now yes
[16:40] <JFo> heh
[16:40] <ogasawara> JFo: around for much longer today?
[16:41] <JFo> a bit yes :)
[16:41] <JFo> want me to try to attend the meeting?
[16:41] <ogasawara> JFo: nah, was hoping you could spam a small set of bugs for me
[16:41] <JFo> I may be able to indeed :)
[16:41] <ogasawara> JFo: which would then clear off one of your work items... "post CFT to lp bugs using an ubuntu/ driver"
[16:41] <ogasawara> JFo: https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=rtl8192se
[16:42] <JFo> interesting
[16:42] <JFo> I don't remember that one
[16:42] <JFo> but I'd be happy to
[16:42] <ogasawara> JFo: In the most recent Maverick kernel I uploaded yesterday (linux-2.6.35-16.22) I'd updated rtl8192se
[16:42]  * JFo worries he  missed subscribing to the BP
[16:43] <JFo> ogasawara, cool
[16:43] <ogasawara> JFo: so if you could just spam those bugs asking if they could test with the latest 26.35-16.22 kernel that'd be awesome
[16:43] <JFo> will do
[16:43] <JFo> what BP is that item in?
[16:43] <JFo> misc?
[16:44] <ogasawara> JFo: https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-ubuntu-delta-review
[16:44] <JFo> yep, I missed subscribing to that one
[16:44] <JFo> fixed now
[16:44] <JFo> thank you :)
[16:45] <ogasawara> JFo: that last bug in that last might not be relevant, so you could maybe skip that one
[16:45] <JFo> k
[16:49] <smb> JFo, scanning through that bug sounds like they would need a completely updated driver, yes. I would say its would be a candidate for lbm but they need that for installation. tgardner, pgraner anyone of you got hw that uses the megaraid_sas driver?
[16:49] <tgardner> smb, not me
[16:50] <tgardner> smb, is this a regression, or just a new version of the card ?
[16:50] <smb> tgardner, I would say a new version
[16:50] <smb> yep
[16:50] <smb> Three newer cards
[16:51] <JFo> sm, thanks for looking
[16:51] <tgardner> smb, I wonder if "we" are smart enough to build an ISO with the LTS backported kernel on it for testing. bjf?
[16:52]  * smb really feels like sm today :)
[16:52] <bjf> tgardner: "we" should be able to do that, yes
[16:52] <tgardner> bjf, how is the alternate kernel selected? do you just replace the Lucid kernel?
[16:52] <bjf> tgardner: yes
[16:53] <bjf> tgardner: desktop is what i've been doing, not sure about server
[16:53] <tgardner> bjf, smb: maybe we should get them to try the Maverick daily first in order to make sire its going to be a solution
[16:53] <tgardner> sure*
[16:53] <smb> tgardner, There is a comment about Maverick a2 or 3 working
[16:54] <tgardner> smb, ok. then they are going to have to wait until we have a Lucid point release with the Maverick kernel as an option
[16:55]  * tgardner goes to snatch some breakfast
[16:55] <smb> Yeah, someone mentioned 9.10 drivers from the vendor. Have not followed that but could be an option too if they have something newer
[16:57] <smb> hm probably not. looks a bit hackish
[16:58] <tgardner> smb, it also won't solve their install problem, will it?
[16:59] <JFo> ogasawara, spam complete
[16:59] <JFo> smb :)
[16:59] <ogasawara> JFo: awesome, thanks.  I'll mark it off the blueprint.
[16:59] <JFo> k, thank you :)
[16:59] <smb> tgardner, Only very sort of. Basically I think thy provide initrd and kernel plus modules for KArmic
[17:01] <ogasawara> ##
[17:01] <ogasawara> ## Kernel team meeting in one hour in #ubuntu-meeting
[17:01] <ogasawara> ##
[17:03] <smb> tgardner, The difference between maverick and lucid is just a mere 1100 lines. If we get the right person the right hw we can sru it by rule #5 :-P
[17:09] <pgraner> smb, I don't have any hw for that
[17:10] <smb> pgraner, ack, yeah its probably rather high end server stuff
[17:11] <pgraner> smb, yea I'm more low rent lol
[17:11] <smb> heh
[17:12] <apw> smb, i wonder if they could make a USB stick with the updated kernel
[17:13] <smb> apw, Well if the installation offers the maverick lts backport they should be fine
[17:13] <apw> well ... no as they can't see the disk to install it ... right ?
[17:13] <smb> Right, would require that kernel to be there for install... :/
[17:14] <tgardner> apw, thats an interesting point
[17:14] <apw> they'd need an image with that kernel actually on it, as a boot option
[17:14] <tgardner> we'll have to ask cjwatson if thats an option on the alternate installer
[17:15] <apw> might be on the DVD images for instance
[17:16] <ogasawara> cnd: you've got a generic work item to "Work with Rafi and Stephane to import any post 2.6.35 multitouch driver code" is that still ongoing or can I mark it done?
[17:21] <smb> apw, The only other solution would be some sort of override mechanism to pull in certain lbm packages from the cd or dvd. But I guess thats even more not implemented
[17:22] <apw> presumably they could make a USB stick on another machine, and chroot into it, and install the updated kernel
[17:22] <apw> so perhaps its a 'write a proceedure for it' problem ?
[17:24] <apw> smb ^^
[17:25] <smb> apw, Hm its probably the same or similar to making some of our test cds. 
[17:32] <JFo> odd that the alternate CD worked but not the regular
[17:32] <JFo> well, it may not be that odd
[17:32] <JFo> hmm
[17:32] <jjohansen> ogasawara: I've updated my work items let me know if I missed anything
[17:33] <ogasawara> jjohansen: will do, thanks
[17:55] <ogasawara> ##
[17:55] <ogasawara> ## Kernel team meeting in 5 minutes in #ubuntu-meeting
[17:55] <ogasawara> ##
[18:01] <cnd> ogasawara, you can mark it done
[18:01] <ogasawara> cnd: yep, thanks
[18:01] <cnd> that work item became utouch :)
[18:01] <cnd> its spawned way too many other work items...
[19:30]  * tgardner lunches
[20:14]  * jjohansen -> lunch
[20:15]  * smb -> out
[20:59] <bjf> ogasawara: thanks for handling the meeting, 15 minutes, nice!
[21:00] <ogasawara> bjf: np, was short and sweet today.
[21:00] <ogasawara> bjf: I sent you the mootbot bits, not sure if you really needed it or not
[21:00] <bjf> ogasawara: thanks, don't use them but thanks anyways
[21:22]  * ogasawara lunch
[23:11] <jj-afk> back on in a bit