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