=== bladernr_afk is now known as bladernr_ === bladernr_ is now known as bladernr_afk === philipballew is now known as philipballew_ === philipballew_ is now known as philipballew === smb` is now known as smb [08:20] are there plans to add drm+1 for 3.2 again? [08:25] thinking of various improvement with mesa 8.0 [08:27] maks, Not as far as I know. [08:31] * apw yawns [08:39] smb: I see, hmpf bad news for rc6 param. [08:39] maks, how so ? [08:41] I am trying to find out if speakup is also in the ubuntu server kernls [08:41] IMO rc6 is indipendant of moving to a completely new drm [08:42] Fudge, Likelyhood should be there as those are the same kernels for precise [08:42] Fudge, as far as i know they are modules which are enabled [08:42] thank you very much, server installs dont actually load a desktop for install, its a text installer? [08:42] as far as I know that is [08:43] Fudge, It is the same text installer like alternates. But you asked about the kernel [08:43] yep, thanx loads [08:46] smb: well it is a great battery life improvement and afaik still needed some fixes after 3.2 (even not turned on by default in 3.3 :|) [08:46] maks, right and we have an ongoing effort to get those fixes working and enabled in precise [08:46] maks, I know. And there is some testing going on about that. But one does not want to pull a whole new drm for that. ;) [08:48] cool, been watching with a bit of distance due to personal thesis constraints. [08:48] that is cool news, hope that we can coordinate that with debian again too. [08:49] (now that 3.2 is official there too) [08:49] we are likely to have the same kernel base version so that the patches ought to be as applicable there if we get them working and applied [08:49] of course that relies on patches which appeared in the last two days being perfect and covering all the cases [08:49] which isn't very likely really [08:52] right they need to settle a bit didn't knew they were that fresh. [08:57] they have only just figured out what they want to do, whether that is valid, and whether the patches do that are both in doubt at the moment [08:59] apw: so I am not pushing the AA patches today, I hit a kitten killer with the rebase and missed feature freeze so the plan is to do some more testing and push early next week [08:59] poor animals [09:00] smb: indeed, /me is now living in fear of peta or alf finding out [09:01] jjohansen, Alf should not be a problem as long as you got ketchup and fries... ;) [09:02] anyway /me is going to bed for at least a couple of hours [09:02] jjohansen, That sounds like a very sensible plan. :) G'night! [09:02] smb: hehe, I forgot about him [09:02] g'night smb [11:04] * cking reboots [11:56] * ppisati -> lunch === bladernr_afk is now known as bladernr_ [14:29] bjf i take it you saw all teh shankbot moaning about universe etc [14:31] apw, pitti has already responded [14:32] tgardner, thanks [14:39] apw, tgardner: I'm gonna start prepping the upload. Do you guys have anything else that needs to go in? [14:40] ogasawara, nothing thats ready no [14:40] ogasawara, serge has a bug report about headers not being right, but I don't think it should be an upload stopper. [14:40] tgardner, got a reference to that ? [14:41] I guess it causes some lxc build issues. I'll have to back and look. One of my unity crashes happened before I wrote it down. [14:41] tgardner, if you find it ... pass it over [14:41] apw, I'm pretty its assigned to hallyn [14:42] not that launchpad can do that search without timing out [14:42] tgardner, indeed [14:43] apw, but it will be a bug against linux or linux-meta [14:43] apw, just sitting down, sigh [14:44] * apw hopes for linux-meta [14:44] bug 933045 [14:44] Launchpad bug 933045 in linux "headers incompatible with eglibc" [Medium,Triaged] https://launchpad.net/bugs/933045 [14:44] ogasawara, thats the one [14:45] bjf, didn't we have an arsenal script to pick up new linux-meta bugs and shove them to linux [14:45] bjf, seems to have stopped working me thinks [14:45] jsalisbury, https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bugs?orderby=-id&start=0 [14:45] yeah, was just gonna ask jsalisbury about that [14:46] jsalisbury, we have a bunch of bugs on linux-meta ... often they are real linux bugs and we should be checking them and pulling them over [14:46] jsalisbury, i thought we had a script which did it for New ones (real ones had to be moved Confirmed and shoved back) [14:46] but ... otherwise we need to keep an eye on it [14:47] apw, i i'll look into it. not sure we run that all the time, but can't remember [14:47] bjf, we did when i ran them, when they moved to jfo things got less clear [14:49] bjf, it is quite likely we don't get enough to care if jo just keeps an eye on them [14:50] bjf we can hear you [14:52] tgardner, apw, yeah, I've been manually moving bugs to the linux package when they are marked as linux-meta by mistake. [14:52] apw, thanks for that link. I'll review all of them. [14:52] jsalisbury, well, there are 20+ new linux-meta bugs tat look like they should be linux [14:56] jsalisbury, we do have a script to find them all and move them, i'll get with you in a bit about it [14:56] bjf, great, thanks. [15:15] * ogasawara back in 20 [16:11] sforshee, has your MB Air stopped suspending when you close the lid ? pm-suspend works OK. [16:13] tgardner, yes. I found the problem, see bug 933710 [16:13] Launchpad bug 933710 in gnome-desktop3 "MacBook Air 4,1 does not suspend when lid closed" [Undecided,New] https://launchpad.net/bugs/933710 [16:14] ah, user space [16:14] yeah, now gsd doesn't suspend if it thinks you have an external monitor attached [16:14] but it's treating eDP as an external monitor [16:15] sforshee, so, this is a recent change to gsd, right ? [16:15] must have been within the last week or so, but I didn't check [16:15] and likely impacts a number of laptops ? [16:15] anything using eDP [16:16] and intel graphics at least [16:16] sforshee, ok, I'll put some whammy on the bug (like its release critical, etc) [16:16] tgardner, thanks [16:18] sforshee, change the description to be more generic as this impacts more then just Macs [16:18] tgardner, done [16:20] sforshee, good catch by the way. [16:21] tgardner, that was really bugging me. I use that machine a lot, and I hate having to use the menu to suspend it [16:21] sforshee, have you played with the clickpad support from chase ? [16:22] tgardner, I didn't realize there was new clickpad support available [16:22] how do I get it? [16:22] ah, it came on the desk top list. I'll forward it to you [16:23] tgardner, thanks. I've been looking forward to getting better clickpad support [16:24] sforshee, i got it on the 11th. I guess I should have looked at the recipient list [16:43] cnd, do you know why 52965cc "Input: bcm5974 - set BUTTONPAD property" hasn't been submitted for precise? [16:49] sforshee, it applies cleanly. shall I just push it ? [16:49] tgardner, up to you. I'm building a kernel now to test it. [16:50] sforshee, ok, lemme know [16:51] * smb thinks this week has been going on for long enough... [16:52] CU next one [16:52] ogra_, is there a page somewhere that describes how to create a Lucid ARM rootfs ? I'm messing around with a dreamplug and their default debian rootfs is kind of crufty. [16:57] tgardner, dreamplug is armv6 [16:57] wont run ubunt [16:57] u [16:57] ogra_, it should run Lucid, right ? [16:58] karmic would run [16:59] ogra_, hmm, well maybe I'll stick with Lenny. the update from their distribution to Lenny 6.0.4 didn't go well. [16:59] maybe I should just start with a Lenny rootfs [17:01] ogra_, I thought we didn't abandon v6 until after Lucid [17:03] other way round [17:03] jaunty was v5, karmic was v6 [17:03] lucid v7 [17:03] ogra_, dang, thats not very handy. [17:04] not my choice [17:05] ogra_, does debian keep an armv6 rootfs tarballed somewhere, or do I have to debootstrap it ? [17:05] i think you need to debootstrap [17:06] ok, thanks [17:12] sforshee, because I haven't had a chance yet :) [17:12] cnd, its a clean cherry pick. any reason not to ? [17:13] tgardner, no, I literally haven't had time yet [17:13] I sent it a few days ago [17:14] and I've been in transit to the gtk hackfest and other feature freeze stuff [17:14] cnd, just pushed it, so its in precise [17:14] tgardner, thanks :) [17:14] the other reason I was waiting was there are three other patches [17:14] one for hid-magicmouse [17:14] ogasawara, added some cruft on to your tree [17:14] and two for synaptics [17:14] but one of them I'm not sure of yet [17:14] tgardner: ack [17:14] so I want to get some feedback first [17:14] cnd, are those upstream ? [17:15] tgardner, not yet, as far as I am aware [17:15] I didn't even know bcm5974 was upstream yet [17:15] ok, we can get 'em later === kamalmostafa is now known as kamal [17:50] cnd, I tried your clickpad stuff on the macbook air, and when I've depressed the clickpad with one finger, each time I place a second finger on the surface the cursor jumps. Is that a known problem? [17:50] cnd, the pointer jumps rather [17:54] sforshee, it shouldn't... [17:54] sforshee, you enabled clickpad mode, right? [17:54] and you don't have the bottom area masked off? [17:55] cnd, I updated from the ppa and ran both of the scripts you sent [17:55] that's all [17:55] sforshee, can you pastebin the output of "xinput listprops "? [17:55] you can get the device from running xinput [17:56] * cnd has to leave though... :( [17:56] okay [17:56] basically it's working, except for the jumpy cursor [17:56] sforshee, please file a bug against xserver-xorg-input-synaptics [17:56] with a tag of "clickpad" [17:56] cnd, ack [17:56] and attach your xinput list-prop output [17:56] and assign it to me [17:56] thanks1 [17:56] ! [17:59] sforshee, https://bugs.launchpad.net/ubuntu/+filebug [18:28] * tgardner -> lunch [18:33] * sforshee -> also lunches [18:49] apw, I know you're upset, Im just genuinely trying to help [18:49] apw, can you just confirm if you are still getting the stuck super keys after upgrading and restarting your session [18:49] I need to know if I should put a freeze on trunk [18:51] DBO not upset, just demotiviated from bothering to report issues [18:51] as three of my team have tried today and got various handy handles added to them [18:52] when all they wanted to do was tell you somethign was really brokted [18:52] Im sorry your team has been given the run-around, thats really not appropriate [18:53] s'ok we'll just file bugs from now on and leave it at that [18:53] the stuck super keys though, can you please answer that [18:53] its quite important to me [18:54] DBO, erm what was the question ? [18:54] if you press super+num [18:54] does your launcher get stuck [18:55] as if the super key is still pressed [18:55] DBO no that one seems fixed, but i have seen two cases of the numbers getting stuck on without the associated loss of ability to work on the desktop that it had before -0ubuntu4 [18:55] so there is something new in there. i'll try and get a piccy of it [18:56] you have seen the numbers stuck without continuing to hold the super key? [18:56] yep, twice since i updated to -0ubuntu4, which would have been perhaps 3.5 hours ago [18:57] they just stayed on until i moved to a differnt viewport thingy (the thing on the lay [18:57] c [18:57] launcher with 4 tiles [18:57] does your launcher autohide? [18:58] DBO yep normally, and when the get stuck it does not hide either [18:59] * cking reboots [19:00] apw, I know Im asking a dumb question, you did restart your session after upgrading compiz yes? [19:01] DBO, i did a lightdm restart cause my compiz died when i tried to compiz --replace it [19:02] okay [19:02] if you find a reproducible or semi-reproducible way to cause the issue [19:02] please let me know immediately [19:06] DBO, yep will do, am playing with various emulations of my workflow to see if i can, but no luck right now [19:07] apw, once again, sorry about the disrespectful way you were treated, its not cool, I'll be looking into this race condition today with my team [19:08] i'll let you know if we manage to repro any of them [19:13] apw, while Im here [19:13] who can I talk to about learning how to make my multi-touch keys work? [19:13] erm, multi-media keys [19:14] some of them are not even reported by the kernel, so things like udev keymaps dont help [19:15] sforshee, ^^ [19:15] DBO there is a wiki guide on how to work out where the issue is [19:15] https://wiki.ubuntu.com/Hotkeys/Troubleshooting [19:16] though i an not sure how up to date the info is these days [19:16] DBO cirtainly we should try and work out if the keys are being emitted from the kernel or not [19:16] normally they either come out of one of your input channels, which you can find with input-events [19:17] or via acpi which acpi_listen thingy will show you if there are events there [19:19] apw, they come out neither acpi_listen nor from xev (with gnome-settings-daemon killed) [19:19] apw, I went through this from the X side with RAOF one time [19:19] and his conclusion was the kernel was not emitting anything when I press the keys [19:20] DBO, what machine is this btw [19:20] apw, evtest either [19:20] DBO, there is a command input-events, and a sibling command lsinputs. the next thing to try is getting those installed [19:21] and then use lsinputs to get a list of all your input streams [19:21] apw, actually its an external keyboard [19:21] logitech wave [19:21] then for each of them use input-events 0, then input-events 1 etc [19:21] and while each is running hit the key and see if it comes out [19:21] can do [19:22] if so then we'd want to see what came out, so do file a bug with all the things you have tried [19:22] and get the bug number to jsalisbury [19:23] apw, if I unplug the wireless receiver [19:24] apw, then I plug it in [19:24] and see the diff in the inputs [19:24] would it be safe to only test those inputs? [19:24] (it creates 2 inputs, one for the mouse, one for the keyboard, but some of the MM keys show up on neither) [19:24] DBO hmm, well in theory yes, though i have seen some internal devices emit them on the internal keyboard for instance [19:25] i woudl think for this one, its mostlikely the new ones [19:25] and i would start with those, as if something is emitted its as likely to be [19:25] there as anywhere [19:25] yeah they dont emit on those [19:25] I'll go through them all [19:25] DBO, about your multimedia keys, is this on a laptop? [19:27] sforshee, it is a laptop [19:27] but on an external keyboard [19:27] I dock the laptop [19:28] apw, sforshee, none of the inputs emit an event when I press the button [19:29] DBO, what model of keyboard? [19:29] sforshee, brand new Logitech Wave [19:31] I gotta go for about 10 or 15, Im sorry [19:38] * apw calls it a day [19:49] * cking does a clean install, wish me luck [19:57] sforshee, back, anything i can do to help make this work? :) [20:03] DBO, how were you checking for scancodes? [20:03] sforshee, evtest [20:06] DBO, it's not always the case that drivers report the scancode when they don't have a keycode to go with it, unfortunately [20:06] do you know what driver is handling the keyboard? usbhid maybe? [20:07] usbhid [20:07] and hid_logitech_dj are loaded [20:07] sforshee, ^^ :) [20:09] DBO, what's the output of 'lsusb | grep 046d' ? [20:10] Bus 003 Device 002: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX [20:10] Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver [20:10] the quickcam is a webcam I have sitting on the external monitor [20:10] sforshee, I did hack my udev rules at one point to make it match the Unifying Receiver [20:10] since the current wave rules dont look for that [20:10] but that didn't fix it [20:11] you mean to load a keymap? [20:11] yes [20:12] DBO, anything in dmesg when you press those keys? [20:13] no [20:14] sforshee: can i piggyback on this and get some assistance with my touchpad disable key later? :] [20:18] DBO, I haven't worked with hid devices before so I'll have to do some digging. Probably best to file a bug and assign it to me. [20:18] sforshee, Im willing to do some hacking of my own [20:18] sforshee, if you point me in a direction and say go [20:19] I really just would like a brief lay of the land [20:19] DBO, well drivers/hid/hid-logitech-dh.c is the driver matching your USB id [20:19] that's where I'll start [20:20] I need to survey the landscape though, and if you file the bug with 'ubuntu-bug linux' I'll have the hw information readily available [20:20] okie dokie [20:20] I'll do that :) [20:20] ohsix, I'd say the same to you. If you file the bug I won't have to keep asking questions about your hw :) [20:21] well i filed a bug already, nobody had any pointers or troubleshooting steps when i kept flogging it either, let me dig it up [20:27] sforshee: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/739922 i've since changed my motherboard so the having ran .37 isn't important now, if it ever was [20:27] Launchpad bug 739922 in xserver-xorg-input-synaptics "touchpad disable key does not work (acts as if no key was pressed, no event in xev)" [Undecided,Expired] [20:27] i don't know if that was even the right place to report it, but nobody pointed me elsewhere, shrug [20:28] i did go through the troubleshooting guides that i could find on the wiki but none were very relavant or revealing [20:29] ohsix, did you try https://wiki.ubuntu.com/Hotkeys/Troubleshooting ? [20:29] yes, but i can go through it again [20:29] iirc the conclusion i came up with is that the event device showed the presses, but xev didn't (like x changed its input selection criteria) [20:30] okay, go through it again and post what you find on the bug. It may just need a keymap. [20:31] should i reopen it or just post a new one? and against synaptics again or something else? [20:32] synaptics is definitely wrong, but reopen it and post what you find and we'll figure out what package is correct [20:32] okie dokie, thanks [20:33] i'm still on natty, i can try oneiric sometime next week though [20:33] ohsix, okay, even testing a live CD should be enough [20:33] sforshee, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/934480 [20:33] Launchpad bug 934480 in linux "Logitech Wave keyboard multi-media keys don't all work" [Undecided,New] [20:33] I tried to add everything I could about it [20:34] that's what it will be :] [20:34] and now its assigned to you sforshee :) [20:34] DBO, ack. I'll look at it as soon as I can manage. [20:35] ohsix, there's two devices you're keypress could be coming from. One is name "HP WMI hotkeys" and the other "AT Translated Set 2 keyboard" [20:35] be sure to check both [20:36] will do, i do recall it coming on a different device than the AT one, but not which [20:36] bbiab, nose running] [20:41] * tgardner -> EOD [21:06] sforshee: hm it's different now getting this on _deactivation_ twice, and nothing on activation, still going through article: keycode 146 = (keysym 0xff6a, Help), state = 0x10 [21:08] ohsix, sending press and release events on button release isn't unusual for hotkeys [21:08] it's the same message twice, wouldn't the keycode or the flags be different? [21:09] it's weird it used to work ages ago, i didn't see if there was a keymap for it back then though [21:10] I'm not sure what everything in your output represents -- what are you using to see the events ? [21:11] oh, just the first step in that wiki article, killing g-s-d and the xev oneliner [21:11] i'll just carry on :] [21:20] yay, unity3d now working - clean install and nuking ~/.gconf/apps/compiz* fixed it === bjf is now known as bjf[afk]