[14:35] cnd: hi, any ideas on bug #804109 ? [14:43] bug #804109 [14:43] no bot, I guess [14:53] Sarvatt: remember when you had those keyboard-doesn't-work-with-lightdm problems? What was the resolution to that? udev update? [14:54] cnd is seeing keyboard failures (keypress events not coming through) when using lightdm [14:56] i actually dont remember exactly what it was, but i did have to downgrade udev to natty's for a month or so to work around it [14:57] dont think thats an option anymore with the /run transition though [15:00] tseliot, hello, just curious, what is the purpose of nvidia-graphics-drivers-updates? [15:00] ricotz: pulls new nvidia drivers from ppa:ubuntu-x-swat/x-updates i believe [15:00] as i would suspect for ("unstable") upcoming updates? [15:00] ricotz: it's the package we're going to keep updated during the stable release cycle [15:01] Sarvatt: yeah found in google where we discussed all this with cnd before [15:01] tseliot, ok [15:01] about 5 weeks ok [15:01] s/ok/ago/ [15:01] bryceh2: oh digging through irclogs then, maybe it'll refresh my memory [15:01] tseliot, so it might be apropriate to follow the beta cycle already there [15:01] as in updating it to 285.03 [15:01] why? [15:02] it seems to fix issues with gnome-shell for instance [15:02] ricotz: is it a stable driver? [15:02] tseliot, no, a beta one [15:03] ricotz: then it's not a candidate for -updates. Only stable drivers will go there [15:03] they'll probably drop a 285.1x.yy soon and mark it stable not long after [15:03] and that would be a good candidate [15:03] yeah that is what i am hoping [15:04] so updating it already shouldnt do no harm, it seems just a bit weird to ship the same driver twice [15:04] sarvart: http://irclogs.ubuntu.com/2011/07/07/%23ubuntu-x.txt [15:07] Sarvatt: http://irclogs.ubuntu.com/2011/07/07/%23ubuntu-x.txt [15:11] cnd: what if you restart lightdm, does input work then? [15:11] tjaalton: no, but if he runs startx with no lightdm it will work [15:12] bryceh2: ah, ok [15:13] bryceh2: those ones were udev choking on the /run transition and not adding the input devices and was already fixed, cnd has had the problem since oneiric opened so pretty sure its something different [15:16] maybe it's starting the wrong X with no input drivers? :) (if there's a local build around) [15:16] though gdm worked.. [15:17] the logfile from a failing one would show [15:17] tjaalton: happen to know a dpkg invocation that would return a list of installed packages not from main/universe? [15:19] bryceh2: hmm no, but I thought he might have a hand-built xserver in /usr/local or so [15:20] no, /usr/bin/X is showing in ps output [15:20] ok [15:32] he's currently stepping through xserver code in gdm [15:32] er. gdb [15:40] bryceh2, can you have a quick look: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/815978. Should I submit the bug with kernel.org? [15:41] looking [15:45] diverse_izzue: yes that would be a good step [15:45] ok, will do [15:45] diverse_izzue: fwiw I also have a tv that seems to have similarly regressed - no idea if it's the same problem [15:46] actually the symptom behaviors were different but it was also due to edid not getting read from the device [15:46] may well be. i'll give you a link to the kernel bug once submitted [15:47] sigh, when will the day come where connecting a second screen doesn't involve praying? [15:47] I suspect that when modesetting moved from X to kernel, something resulted in tv edid extraction not working (at least for my tv) [15:47] oh damn, kernel.org is still down! [15:49] diverse_izzue: for me, I saw different results from different outputs from the tv [15:49] I found that a particular output would work ok with the -nvidia driver, so that's what i ended up with [15:50] when you say output, do you mean connector, or resolution? [15:50] connector [15:50] diverse_izzue: instead of kernel.org, you could try filing against the intel X driver at bugs.freedesktop.org [15:51] it's the same guys that look at both bug trackers [15:52] okay, will do [15:53] what xorg version are we at in oneiric? [15:56] bryceh2, https://bugs.freedesktop.org/show_bug.cgi?id=40841 [15:59] xserver 1.10.4. [15:59] diverse_izzue: but for this it's more the kernel version that matters [16:00] diverse_izzue: I see from your dmesg log there's a failure with the displayport connector - which connector was your tv connected to? [16:00] the analog VGA port [16:01] there's also a line [ 3.595121] [drm:intel_tv_init], Integrated TV is not present. [16:02] whatever that means... [16:03] yeah, dunno [16:03] [ 3.930672] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:VGA-1] [ 3.950050] [drm:intel_crt_detect], CRT not detected via hotplug [ 3.950055] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:VGA-1] disconnected [16:03] so it's not seeing anything connected to VGA [16:04] bryceh2, iirc hotplug is working, it does realise something is connected, it just doesn't offer me the right resolution [16:07] ah yes you're hotplugging it later in the log [16:07] [ 1693.636443] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:VGA-1] [ 1693.660245] [drm:intel_crt_detect], CRT detected via hotplug [ 1693.680424] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:VGA-1] probed modes : [ 1693.680427] [drm:drm_mode_debug_printmodeline], Modeline 36:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa [ 1693.680430] [drm:drm_mode_debug_printmodeline], Modeline 34: [16:08] diverse_izzue: have you tried disabling the LVDS? [16:09] ala xrandr --output LVDS1 --off [16:09] that's my internal screen? [16:09] right [16:09] I think it won't help to turn it off, though. [16:10] neither do i... but i will give it a try [16:10] diverse_izzue: also, what happens if you have the tv connected while you boot it? [16:11] good point, will try also [16:12] will be sporadically away now, cooking fooooood === chrisccoulson_ is now known as chrisccoulson