[07:09] bryce_: pong2 [07:13] heya [07:14] tjaalton: Could you take a look at bug 267682? [07:14] Launchpad bug 267682 in ubuntu "Hotkeys no longer working in Intrepid (evdev?)" [Critical,Triaged] https://launchpad.net/bugs/267682 [07:14] seems I had another question for you... hm [07:15] eh can't think of it [07:16] I looked at that yesterday, and I think g-p-m should catch those [07:16] regardless of the driver X uses. but that's easy to test too [07:16] today I decided to go downstairs and only take broken test hardware with me. It's been a good challenge, just staying online ;-) [07:17] I've fleshed out https://wiki.ubuntu.com/X/Quirks a good bit more [07:17] hehe, I bet [07:17] ^^ that was for the previous comment ;) [07:18] I'll test my laptop once it reboots (damn dpms) [07:18] lenovo X61, those hotkeys [07:22] are you seeing freezes when the screensaver comes on too? [07:23] it's when the display is put to sleep [07:23] normal screensavers work [07:23] I'm waiting for the new kernel.. [07:30] hmm, I had a couple systems that were locking up (or blanking at least) when either the screensaver or power savings came on [07:30] I switched off screensaver, and the lockups/blanks went away [07:30] I just disabled the power-off [07:31] however maybe disabling the screensaver also affected the dpms settings; not sure [07:31] in power settings there's the slider "set the monitor in power save mode" or something like that [07:31] put that in "never" [07:32] yeah I may play around with that more later this week; I've got quite a laundry list of bugs for all this hardware... [07:36] humm, I tried without input-hotplug, and my battery and hibernate hotkeys started working [08:03] huh... Jaunty Jackalope [08:03] well g'nite [08:03] night:) [08:18] seb128: about the nvidia-glx-173, update-manager is trying to install it here as well [08:18] tjaalton: ahah! [08:18] something really is broken [08:18] tjaalton: does apt-get dist-upgrade do that too? [08:18] let's see [08:18] grab mvo when he is around [08:19] yes it does [08:19] good ;-) [08:19] ok I won't upgrade before he shows up :) [08:19] thanks [08:46] tjaalton: mvo is here ;-) [08:46] seb128__: yeah! [08:47] mvo: so, somehow we get nvidia-glx-173 installed, which breaks if you have intel, for instance [08:47] um, breaks 3D [08:47] mvo: same thing with update-manager and apt-get [08:48] hello! [08:48] what is the bugnumber? [08:48] mvo: what is the apt magic to have the reason of why packages are installed displayed? [08:48] -o debug::pkgDepCache::AutoInstall=true [08:48] mvo: no bug number, just apt-get dist-upgrade on intrepid and note it in the list [08:49] tjaalton: sudo apt-get -o debug::pkgDepCache::AutoInstall=true dist-upgrade and look in the log then I guess === seb128__ is now known as seb128 [08:53] tjaalton: there is also -o Debug::pkgProblemResolver=true if the autoinst doesn't give a hint [08:56] mvo: I think I found the problem already.. nvidia-kernel-common Recommends nvidia-kernel-source, which pulls in nvidia-173-kernel-source, which pulls in nvidia-glx-173.. [08:56] and I did the upload :) [08:56] but I'm not sure if that Recommends was added there, will check [08:57] tjaalton: why is nvidia-kernel-common installed? [08:58] seb128: l-r-m [08:58] and yes, that Recommends was added in the latest version [08:59] but not mentioned on the changelog [09:00] I tend to use aptitude to find out why a package is installed [09:02] mvo: where are those debug options listed again? I tried the apt-get and apt.conf man but only the resolver option was listed there [09:02] seb128: its not well documented, it should probably be added to the man-page (or to a new apt.debug page). its in /usr/share/doc/apt/examples/configuration-index [09:03] mvo: ah, I looked at the apt.conf example but not this one, thanks [09:07] I'm surprised that there are no bugs reported about this.. it basically breaks 3D for everyone [09:07] and the change was made in Debian, so tseliot is not to blame [09:08] uh no [09:08] tjaalton: the change is recent and it breaks intel for intrepid users who updated since yesterday basically, that's probably not that many [09:09] the Recommends has been there forever in debian, and dropped from our package in 16th Aug 06 [09:09] so the merge is busted [09:09] who did it? [09:09] tseliot [09:09] I'll re-merge it [09:09] thanks [09:10] but I kinda reviewed it :/ [09:11] ah, there's a new debian version that removes the recommends [09:24] tseliot: hey, the nvidi-kernel-common merge was broken.. it didn't include all our previous changes, most importantly it Recommends nvidia-kernel-source, which basically pulls nvidia-glx-173 for everyone and breaks 3D [09:24] but, I missed that so I'll re-merge it [09:25] tjaalton: it wasn't finished. I wanted you to have a look at the merge. I have removed the recommends and completed the merge but I'm still not sure as to whether we still need that package in Ubuntu. [09:25] therefore I'm waiting a bit [09:26] tseliot: ok, well it _was_ uploaded in saturday.. [09:26] tjaalton: what??? [09:26] I'd prefer to review packages that are ready.. [09:26] I thought it was [09:26] sorry about this [09:27] no worries, I'll upload a new one shortly [09:27] next time I'll ask you explicitly to upload a new package if I wish you to do so [09:27] yeah :) [11:19] wgrant: I've uploaded a new synaptics to my PPA: http://ppa.launchpad.net/tjaalton/ubuntu/pool/main/x/xfree86-driver-synaptics/ [11:19] wgrant: please test once it's built [11:28] tjaalton: Will do. [11:28] Has 0.15.1 actually been released? I saw that the version in git was bumped. [11:29] yes, tarball was available [11:29] Ah. [11:29] so I think it's released then :) [11:29] Have you dropped 101_ubuntu.diff? [11:29] yes [11:29] Good. [11:29] So we should be almost syncable. [11:29] Brb, restarting X. [11:30] it also has a couple of patches that should fix appletouch and ALPS [11:30] slowness and narrow scrollregions [11:33] Hmm. [11:33] Edges are different. [11:33] Yep, I suggested that you look at them IIRC. [11:33] But otherwise this is pretty boring. [11:33] It all works :( [11:33] heh [11:33] the patches were directly from whot [11:34] so they are not upstream yet [11:34] they are in rawhide too [11:34] Oh, I thought the scrollregions one was. [11:35] I think my right scroll region might be slightly less ridiculously thin than it was with 1.5. [11:36] hmm maybe the patches weren't for regions, but edges and some preprobe stuff [11:36] anyway, nice that it works [11:37] could you add something to bug 268071? [11:37] Launchpad bug 268071 in xserver-xorg-input-synaptics "Please accept xfree86-driver-synaptics 0.15.1-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/268071 [11:37] Props seem to work fine. It's all fine. [11:37] Sure. [11:37] great, thanks [12:49] tjaalton: Multi-finger tapping strangeness regression, possible due to the two-finger disentangling patch. [12:49] It seems to just make the cursor jump occasionally now. And two-finger tapping has ceased. [12:50] drat.. [12:55] I can occasionally get it to work. But not often. [12:56] Hm. [12:56] I could depatch that commit [12:57] It's definitely related to the MaxTapMove default change. [12:57] or unpatch, whatever [12:57] As if I increase that it becomes a bit more likely to work. [12:57] But still nothing like it used to be. [12:57] I'll work out which commit/patch it was. [12:57] cool, thanks [12:57] I'll scratch my head with xkb-data again.. [12:58] fails to build [12:58] Fun. [12:59] update-po fails [13:00] ah right, autoreconfig needed [13:17] tjaalton: Reverting 9f0da9 (the two-finger scrolling disentanglement commit) fixes it. [13:18] wgrant: thanks, I'll add that to the package [13:21] I'm not sure how exactly that patch was going to help anything. [13:22] I do wish that the huge switch in HandleTapProcessing was commented at least slightly. [13:32] tjaalton: Which variety of synaptics-driven hardware do you have? [13:33] wgrant: none :) [13:33] Oh. That is rather unfortunate. [13:34] tell me about it.. although I could get a lenovo keyboard with a trackpad if I wanted to [13:34] it's rather pricey though [13:34] Well, I'm generally available for testing if you need it. [13:37] yep, good to know === mvo__ is now known as mvo [18:07] morning [18:07] hey bryce [18:08] could you confirm bug 268055 and bug 268071 [18:08] Launchpad bug 268055 in xorg-server "Please accept xorg-server 1.5.0-1ubuntu1" [Undecided,New] https://launchpad.net/bugs/268055 [18:08] Launchpad bug 268071 in xserver-xorg-input-synaptics "Please accept xfree86-driver-synaptics 0.15.1-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/268071 [18:09] sure, sec [18:10] bryce_: I've now nearly finished the keyboard stuff, only gnome-settings-daemon left to be uploaded. it should be done last since otherwise people might have broken layouts for a while [18:10] but in an hour or so [18:10] hum, actually it takes a while for the publisher to catch up, so I'll upload it now [18:11] tjaalton: excellent [18:11] I skipped the paperwork with xkeyboard-config and didn't create a new tarball for it.. [18:12] but for evdev I only pulled one commit, so no support for properties yet [18:12] ok cool [18:13] we don't even have 2.0.4, so having master versioned as 2.0.3 sounds a bit strange ;) [18:13] but there should be 2.1 released this week [18:13] I went through -intel quirks last night and will be pushing a bunch in today. Thinking about probably merging 2.4.2 too [18:13] we have that already, only the version string is missing from 2.4.2 [18:14] ahh, ok then; I'll just put my patches in [18:14] just need to test to make sure quirking lvds does what it's supposed to do [18:16] did you get a chance to upload xorg? If not I could tackle that. [18:16] not before xorg-server is uploaded and all drivers rebuilt [18:17] at least it's not usable before that [18:17] because people couldn't upgrade [18:18] I need to head home.. it's dark and wet, so will be a pleasant 10km ride with my bike [18:18] later-> [18:18] ok cya [21:52] hey there [21:53] keyboard layout detection seems to be broken [21:53] nice [21:53] AZERTY became QWERTY [21:53] did you dist-upgrade? [21:54] I used PackageKit to update [21:54] the gnome applet reports USA layout [21:54] what versions do you have of xkb-data, hal, xserver-xorg-input-evdev and gnome-settings-daemon? [21:56] 1.3-1ubuntu2 - hal_0.5.11-3~ubuntu8_i386.deb - 1:2.0.3-2ubuntu1 - 2.23.92-0ubuntu1 [21:57] hmh, xkb-data should've been updated [21:58] also g-s-d is too old [21:58] okay [22:00] should be available at least on a.u.c [22:00] tjaalton: I'm upgrading [22:00] hoz Xorg detect keyboard layout? [22:01] hm? [22:01] tjaalton: z -> w :) [22:01] crevette: it doesn't [22:01] heh, right [22:01] crevette: see /etc/default/console-setup [22:02] qh okay [22:02] and /usr/lib/hal/debian-setup-keyboard [22:02] i guess what happened there is that because of the older xkb-data, xkbcomp fails to create the map, so you get the default us [22:03] yeah, I was just writing that :) [22:03] let's restart X [22:03] I couldn't decide which package needed to depend on which, so hoped that they'd get published in the correct order [22:03] but since the first xkeyboard-config upload FTBFS'd [22:03] .. [22:04] maybe new evdev Breaks old xkb-data, and new xkb-data Breaks old evdev, would work? [22:04] by which component /usr/lib/hal/debian-setup-keyboard is executed ? [22:04] crevette: by hal, when it starts [22:04] /usr/share/hal/fdi/policy/10osvendor/10-x11-keymap.fdi [22:05] okaym so I need to restart hal also [22:05] no hal should be ok now [22:05] already [22:05] that's what broke it :) [22:06] but running lshal |grep xkb should show you something like xkb.rules = 'evdev' [22:06] restarting hal doesn't hurt though [22:08] jcristau: yeah that would probably work. we'll see if I care enough to fix those :) [22:09] don't think people would backport these [22:09] if you don't care about partial upgrades it's ok [22:10] oh you mean if someone would only pull the new evdev? yeah, that would break [22:10] hum