[02:28] <bryce> xrandr cleaned out (20 -> 0 bugs)
[02:33] <pwnguin> 20 patches, or 20 "please test again"?
[02:39] <RAOF> Or 20 "not a bug in xrandr", or 20 "this bug is fixed" :)
[02:48] <bryce> mostly "not a bug in xrandr", and moved to the more appropriate package
[02:50] <bryce> http://people.ubuntu.com/~bryce/totals.svg
[06:36] <bryce_> tjaalton, jcristau: what package handles capslock toggling?  Is that -evdev or the server, or ...?  trying to figure out where bugs like 207960 go... I'm figuring xkeyboard-config probably is not the right place
[06:57] <tjaalton> bryce_: I guess it's the server. would be nice to know if it works in jaunty though
[06:58]  * bryce_ nods
[07:01] <bryce_> ok, seems capslock issues are scattered around, I'll pull them into xorg-server and see if some sense can be made of them
[07:02] <tjaalton> did you see the list of deprecated input drivers by whot? what do you think if we should drop those, since I think none of them actually build anymore
[07:02] <tjaalton> or just leave them as is until debian drops them, and fix the build in the meantime if someone needs them
[07:05] <bryce_> yep, I saw the list.  I've been thinking we should deprecate them for quite some time
[07:06] <tjaalton> none of them have any bugs filed, which clearly shows that no-one is using them :)
[07:06] <bryce_> whether to drop them now or wait 'til debian drops them, I'm open.  
[07:06] <bryce_> what's your opinion?
[07:07] <tjaalton> I'll ask them first
[07:07] <bryce_> ok
[07:07] <tjaalton> IIRC it has been discussed before, so probably that's what will happen
[07:13] <bryce_> btw, I'm hoping to continue my bug stomping tour through xserver and -intel before the release is out.  Those are biggies though, so dunno that I'll make it through any other packages
[07:14] <bryce_> if you have any time, it would be great if you could look through -evdev (and maybe -mouse)
[07:14] <tjaalton> ok, I'll see what I can do
[08:49] <Alexia_Death> Does x support any sort of per device mouse acceleration setting? I have a touchpad and an USB mouse I hotplug. the mouse is high DPI and generates a lot of jitter. However, truning aceleration down makes my touchpad unusable.
[09:10] <tjaalton> Alexia_Death: not that I know of
[09:33] <Alexia_Death> tjaalton: :( that sucks.
[09:36] <tjaalton> at least xinput doesn't show any properties
[09:36] <tjaalton> maybe master is better
[09:41] <bryce> heh, after all that capslock work, turns out I think the main bug I was looking at is already fixed (at least it works for me).
[09:41] <bryce> anyway, night.
[09:42] <tjaalton> night :)
[11:20] <Ng> tjaalton: hrm, it feels like the vblank change didn't really change anything
[11:21] <tjaalton> Ng: really?
[11:22] <Ng> tjaalton: workspace switches feel like they get stuck for a fraction of a second and then just redraw the desktop. sometimes it does the smooth swipe, but some/most times it feels like it's jumping
[11:22] <Ng> it's kinda hard to describe ;)
[11:22] <tjaalton> sounds familiar
[11:22] <tjaalton> I need to check it out later
[11:22] <Ng> I suppose, for fairness, I should reset my compiz settings to the defaults
[11:24] <tjaalton> please do, or test with a new user :)
[11:26] <Ng> well that was fun, I switched profile in ccsm and X wedged
[11:26] <Ng> few of these in dmesg: [  648.929470] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
[11:26] <tjaalton> you've rebooted since the new mesa?
[11:27] <Ng> my last reboot was about 15 minutes ago, my last update was within the last couple of hours
[11:27] <tjaalton> ok
[11:27] <Ng> I have mesa 7.3-1ubuntu2
[11:28] <tjaalton> I'm thinking if the patches that are already applied cause some regressions
[11:28] <tjaalton> but since we are not going to use vblank those could probably be dropped
[11:28] <tjaalton> from the kernel
[11:36] <Ng> even with pretty much default compiz settings I'm still seeing it, I guess I'll try a fresh user later
[12:46] <mvo_> I'm seening very strange behaviour sometimes with jaunty X, some mouse actions (like clicking on the panel do not work) and some keys (like alt-tab, alt-f1) do not work. buttons in apps (like thunderbird) can not be clicked. its as if something has a grab on the mouse/keyboard and not letting go of it or something. have you seen bugreports like this?
[12:47] <mvo_> IIRC evan had something similar during the sprint, so I think its not my spooky hardware
[12:48] <tjaalton> I've not seen that
[16:25] <tseliot> tjaalton: did you read this? http://www.phoronix.com/scan.php?page=news_item&px=NzA4Ng
[16:26] <tseliot> weird
[16:30] <tjaalton> tseliot: the nouveau article?
[16:31] <tseliot> yep
[16:31] <tseliot> it looks like they will use it instead of nv
[16:33] <bryce> mvo_, I've seen some reports of weird grabbing behavior, in xserver-xorg-input-evdev iirc
[16:34] <tjaalton> tseliot: what's weird about it? :)
[16:34] <bryce> sounds like very good news to me; we've been needing someone to volunteer to guineapig it, so we can use it in karmic :-)
[16:34] <tseliot> tjaalton: does it mean that it works better than "nv" already? It would be great news
[16:35] <mvo> bryce: I have no idea where to even start debugging this, but I get it every now and than, nothing really unusual in the logs AFAICS 
[16:35] <bryce> tseliot: if it didn't, I'm not sure that would stop fedora ;-)
[16:35] <tseliot> hehe
[16:35] <tseliot> right
[16:35] <tjaalton> tseliot: for some chips it actually works, so
[16:36] <tseliot> even better
[16:36] <tseliot> ;)
[16:36] <bryce> mvo: well, on the theory that it's an -evdev bug, if you have steps to reproduce reliably, an easy start might be to try running an older release of -evdev
[16:36] <bryce> (assuming this is a regression for you)
[16:37] <bryce> another possibility is a bug in the xserver, so reverting that back might be the next step, if it's not too difficult
[16:39] <mvo> bryce: ok, that sounds good. I will start with going back with -evdev . the trouble is that it seems to be not reliable to reporduce (or at least I have no pattern yet)
[16:42] <bryce> mvo: next two times it happens, check what processes are running to see if there are commonalities
[16:43] <bryce> it is possible there is something which is triggering the grab.  There is one bug I'm aware of I looked at yesterday, let me find it again
[16:45] <bryce> tjaalton: thoughts on bug #320632 ?
[16:47] <tjaalton> bryce: tseliot has been working on it recently, but I think there are some related fixes in 2.6.29
[16:48]  * tseliot has a look at the bug report
[16:51] <tseliot> bryce, tjaalton: there are some problems with ALPS touchpads but, since I don't own one yet, there is very little I can do
[16:51] <tseliot> this might change though ;)
[16:53] <bryce> ok, tseliot can I put you in touch with SteveA on 320632?  He has reproduced the issue on a recent upgrade and has some questions about it
[16:53] <tseliot> bryce: ok
[17:41] <thomasdelbeke> Hi there
[17:41] <thomasdelbeke> I was referred to here by seb128
[17:41] <thomasdelbeke> I reported earlier:
[17:42] <thomasdelbeke> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/323694
[17:42] <thomasdelbeke> Now I have a new one:
[17:45] <thomasdelbeke> http://paste.ubuntu.com/122485/
[17:45] <thomasdelbeke> Is it the same?
[21:30] <Laney> http://pastebin.com/f6da02497 is this normal? I'm experiencing incredible slowness on my desktop
[21:48]  * Ng wonders if bug 296167 would be worth an SRU - it's the top bug in a "by number of users affected" search on xorg-xserver, by some margin
[21:48] <Ng> I do like that search mode :)
[21:49] <bryce> Ng: is there a regression-free patch identified?
[21:50] <Ng> I had a quick poke in the linked fedora bug and it doesn't look like they've linked/attached a patch, just pointed at a cause and a build with it fixed :/
[21:50] <bryce> heh, I see I asked someone already to locate the patch, and the responses are just "is it fixed yet?"
[21:50] <bryce> yeah I tried to poke at it myself but couldn't find the patch
[21:50] <bryce> so no SRU until we have a patch
[22:09] <Laney> I just filed bug 334066
[22:09] <Laney> quite welcome to bisect if someone can assist
[22:10] <Laney> s/welcome/willing/
[22:15] <tjaalton> Laney: purge fglrx
[22:16] <Laney> tjaalton: It happens with -ati too though
[22:16] <tjaalton> it doesn't support the new xserver, and having the module loaded means that you get no DRI
[22:16] <Laney> but right, I will do that anyway
[22:17] <maxb> This is a bit perplexing. Many times today, I have: right clicked the update notifier, chosen "install all updates". Waited. Brought the "Untitled window" of synaptic to the front. At this point compiz crashes.
[22:18] <maxb> metacity seems to autostart in its place
[22:18] <maxb> any thoughts on things I could include to make a useful bugreport?
[22:18] <tjaalton> maxb: more in the -desktop territory
[22:18] <maxb> ah, fair enough
[22:30] <Laney> hmm
[22:30] <Laney> actually that bug isn't right
[22:30] <Laney> if I disable the metacity compositor it returns to normal speed
[22:37] <albert23> Ng, bryce: ﻿296167 seems to be http://bugs.freedesktop.org/show_bug.cgi?id=18668. Steven Harms reports the fix works in Intrepid. 
[22:38] <albert23> Pushed as 9fe9b6e4ef669b192ee349e3290db5d2aeea273c and nominated for 1.6
[22:38] <bryce> Laney: see wiki.ubuntu.com/X/Troubleshooting  and the bit about fglrx conflicting with ati and how to fix
[22:39] <bryce> albert23: thanks, can you update the lp bug report?
[22:40] <albert23> bryce: sure, I will
[22:42] <Ng> albert23: win :)
[23:16] <Laney> bryce: It all seems removed (that uninstallation script is nowhere to be found though)
[23:17] <bryce> Laney: ok, and after rebooting is the issue still present?
[23:17] <Laney> bryce: With the metacity compositor off it's mostly fine
[23:17] <Laney> moving/resizing windows is much better
[23:18] <Laney> but scrolling in applications seems pretty sluggish still
[23:21] <bryce> Laney: lspci | grep VGA ?
[23:21] <Laney> 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon X1950 GT
[23:22] <bryce> hmm, that's a r580
[23:23] <bryce> in theory that should be well supported by -ati, however the support is relatively new so there could still be bugs
[23:23] <bryce> Laney: is there anything of interesting note in your Xorg.0.log?  In particular look to see if you're using XAA or EXA acceleration
[23:24] <bryce> also if you're using EXA, test if XAA makes a difference (or vice versa)
[23:24] <bryce> beyond that, please file a bug via `ubuntu-bug xserver-xorg-video-ati` and we can follow up on launchpad.
[23:29] <Laney> roger
[23:29] <Laney> (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
[23:29] <Laney> (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
[23:29] <Laney> is that normal?
[23:29] <Laney> not supported, using it anyway :(
[23:57] <Laney> looks like I should wait for 6.12