[00:23] bryceh, are you able to reproduce bug #780961? [00:23] Launchpad bug 780961 in xorg-server (Ubuntu Precise) (and 3 other projects) "Xorg crash in PlayReleasedEvents with Sawfish when using keyboard-based window management (affects: 13) (dups: 2) (heat: 78)" [High,Triaged] https://launchpad.net/bugs/780961 [00:23] or have you tried? [00:29] hmm, I can't get sawfish to come up [00:30] at least not on a guest session [00:30] cnd, no [00:32] cnd, I'll try to set up something to reproduce it, but for now just wanted to see if you could spot anything obvious just from the report, or if you had suggestions of further analysis that could be done [00:33] my thoughts are to figure out how to reproduce it :) [00:33] that may mean running sawfish, opening a terminal, and playing back a device recording [00:33] but I can't even get sawfish to run [00:33] at least, I don't think it's running [00:33] maybe sawfish is one of those environments where there's nothing on screen by default? [00:38] cnd, yeah it's pretty minimal. maybe try on console DISPLAY=:0 xterm ? [00:39] yeah, got an xterm up with decorations [00:42] ok, I can switch between workspaces with super-L/R [00:42] but no crash [00:45] trying it here... [00:46] I can't seem to figure out how to get the keybinding for moving windows with C-Left and C-Right to work === soreau_ is now known as soreau [00:46] it just sits there... [00:48] yeah, wiggling windows here isn't crashing either [00:49] http://sawfish.wikia.com/wiki/Run-application [00:49] ~/.sawfishrc [00:51] I think the next step is to create test packages with more debug output [00:51] check when enqueueing events that the device is set (since it appears to be qe->device == NULL) [00:52] a core dump might not be a bad idea either [00:53] it could tell us if there's memory corruption [00:56] ah good idea [00:58] oh man, I just read on the X/Backtracing wiki page that -dumbSched fixes that annoying scheduler issue! [01:01] :-) [01:13] I just throw in the towel when that happens and reattach with gdb [01:13] losing all my state... [01:13] bryceh, I'm building a test server [01:42] bryceh: how do you add a package to ubuntu-x-swat bug mail and your versions-current? would like to get https://launchpad.net/ubuntu/+source/xf86-input-mtrack on there [01:44] is the package list defined in an arsenal script? i seem to remember it scraping that info from launchpad instead [01:45] oo armhf builds started showing up [01:48] Sarvatt, nope, just subscribe the ubuntu-x-swat to the package [01:49] er, the ubuntu-x-swat *team* to the package [01:49] ah cool, thanks [01:50] whoops, can't do it, not admin [01:51] ok, I've done it [01:51] now, to fix the admin thing... [01:51] hmm nice, never seen the subscribe a team dialog thing before [01:51] you can filter it or make it so you don't get comments [01:52] yep, the LP guys have done a lot for subscription management configurability [01:52] Sarvatt, ok you're admin now [01:54] bryceh: thanks for the help! I use that driver a ton and am interested in tracking/fixing it up when needed [01:54] sounds good [01:55] btw, if you see packages on the versions-current page that you know we no longer care of, you can drop the ubuntu-x-swat package subscription and that should get it off the list [01:56] * Sarvatt nods [01:56] hasn't been up for awhile though [01:57] playing with your server? :P [02:00] it hasn't? [02:00] hmm, you're right [02:00] and yes, I have been fiddling with things recently, but this shouldn't have broken [02:08] ok, think it's running properly now, hopefully new page should be up within the hour [02:13] even sooner [02:13] http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/versions-current.html [02:13] Sarvatt, ^^ [02:14] and it shows xf86-input-mtrack, 0.2.0-2 :-) [02:16] I've jacked up it's refresh to every 20 minutes instead of every 4 hours [03:34] out of curiosity, /usr/share/doc/xorg/howto/configure-input.html says that i can trigger a change event on --subsystem-match=input to get X to pick up changes in /etc/default/keyboard [03:34] that doesn't seem to be working for me at the moment, but i'm wondering if that could be because i had previously changed my keyboard layout with the capplet [03:34] (i see X noticing the events in the Xorg.log, including the new layout settings) [03:44] I'd expect the GNOME keyboard configuration to override whatever X sets up. [03:44] that makes sense === dzan|away is now known as dzan === yofel_ is now known as yofel === dzan is now known as dzan|away === dzan|away is now known as dzan [14:48] good afternoon === soreau_ is now known as soreau === dzan is now known as dzan|away === dzan|away is now known as dzan === dzan is now known as dzan|away === dzan|away is now known as dzan === dzan is now known as dzan|away [18:08] Hi, can someone take a look at this report: https://launchpad.net/bugs/873482 [18:08] Launchpad bug 873482 in xserver-xorg-input-synaptics (Ubuntu) "elantech: Touchpad always reports 3 finger tap as 1 finger tap (affects: 17) (heat: 94)" [Medium,Confirmed] === soreau_ is now known as soreau === dzan|away is now known as dzan === dzan is now known as dzan|away