[09:51] <tjaalton> right, so g-s-d doesn't distinguish tablets with touch support from touchsreens when it's resetting the touch device to relative mode
[11:22] <tjaalton> oh gee, one guy wanted nvidia-173 so bad he downgraded X to 11.10
[11:22] <tjaalton> and posted the instructions on the bug report
[11:22] <tjaalton> ..
[11:50] <c10ud> so, this might be slightly OT here but: did anyone try Precise with an AMD APU? i'm considering in upgrading my workstation but i fear fglrx drivers and stuff
[11:50] <c10ud> btw, hello ;)
[14:35] <tjaalton> bryceh: pushed g-s-d to my ppa, so once it's built please test :)
[14:35] <tjaalton> tested that my intuos5 is still in relative mode after update..
[14:35] <tjaalton> dinner ->
[19:47] <seb128> tjaalton, still there?
[20:02] <tjaalton> seb128: on an off
[20:03] <tjaalton> *and
[20:04] <seb128> tjaalton, g-s-d, do you want your fix uploaded?
[20:04] <seb128> tjaalton, I'm about to do an upload
[20:06] <tjaalton> seb128: well, does it fix things? :)
[20:06] <seb128> tjaalton, dunno, I will upload http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d07807ca68e7d3f0b94fdce9bc2a88a71d4324ef
[20:07] <seb128> tjaalton, which is another touchpad devices issue
[20:07] <seb128> tjaalton, so I was just wondering if you want extra testing through the archive, we can always revert next week if it's not good
[20:08] <tjaalton> seb128: ah yeah in that case why not
[20:08] <seb128> tjaalton, ok, can you push it to the vcs?
[20:08] <seb128> tjaalton, I will add my patch on top
[20:08] <tjaalton> i did test that it didn't break touch capable tablet support
[20:09] <tjaalton> but the touchscreen part is still a mystery, but the logic should be right now
[20:10] <seb128> tjaalton, ok, let's get extra archive testing during the w.e
[20:11] <tjaalton> upstream probably would like to add a new class for those, so the condition would be more like (type != SCREEN) or such
[20:11] <seb128> well until they do your patch might be better than what we have ;-)
[20:12] <tjaalton> yeah, hope so :)
[20:25] <seb128> tjaalton, can you push your changes then? ;-)
[20:32] <tjaalton> seb128: to the bzr branch?
[20:33] <seb128> tjaalton, yes
[20:33] <seb128> tjaalton, lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu
[20:34] <tjaalton> ok let me get off the phone irc then :)
[20:41] <tjaalton> hmm, can't login to my laptop
[20:43] <FernandoMiguel> ahahhaha
[20:48] <tjaalton> last message on lightdm.log is "user foo authorized"
[20:51] <tjaalton> seb128: ^ ideas? I upgraded it this evening, noticed there was a new lightdm too
[20:51] <tjaalton> just in time for the long weekend :)
[20:51] <seb128> tjaalton, no, is there anything special on your pam or login?
[20:52] <seb128> tjaalton, is there any session process started?
[20:53] <tjaalton> auth.log looks ok
[20:53] <tjaalton> no user processes started
[20:53] <tjaalton> i mean, owned by the user
[20:54] <tjaalton> greeter.log says auth complete
[20:54] <bryceh> tjaalton, I've tested your g-s-d
[20:54] <tjaalton> bryceh: works?
[20:54] <bryceh> tjaalton, here's what I did
[20:54] <tjaalton> *bites fingernails*
[20:54] <bryceh> I re-set the gsettings active property back(?) to true
[20:54] <Sarvatt> guessing no since its a story :)
[20:54] <bryceh> then I added your ppa, updated, upgraded
[20:55] <bryceh> rebooted
[20:55] <tjaalton> Sarvatt: yeah :)
[20:55] <bryceh> now, on the *login* screen, it does work great
[20:55] <bryceh> but after logged in, same behavior
[20:55] <tjaalton> meh
[20:55] <bryceh> but
[20:55] <bryceh> what I'm wondering is that since I set it to true specifically, does that override your changes?
[20:55] <bryceh> maybe I need to UNset it?
[20:56] <bryceh> or should it matter?
[20:56] <tjaalton> bryceh: no it's just the setting for the plugin, use it or not
[20:56] <tjaalton> true is the default
[20:56] <bryceh> gnome-settings-daemon:
[20:56] <bryceh>   Installed: 3.4.0-0ubuntu3.1
[20:56] <tjaalton> so the plugin does it's own thing, and the relative/absolute for the touch functionality is not configurable by gsettings
[20:56] <bryceh>  *** 3.4.0-0ubuntu3.1 0
[20:56] <bryceh>         500 http://ppa.launchpad.net/tjaalton/ppa/ubuntu/ precise/main i386 Packages
[20:56] <tjaalton> yeah, so it's not complete, bah
[20:57] <tjaalton> either the logic is all wrong after me looking at it for too long :) or it can't be called from there. compiles fine though and doesn't break my setup
[20:58] <seb128> tjaalton, ok, so pre-release freeze is in 3 minutes, do you want to commit your stuff or should I upload my patch without it?
[20:59] <bryceh> tjaalton, I can mess around with the patch locally if you'd like.  get some more data on what's going on, etc...
[20:59] <tjaalton> seb128: withouth, bryce tested and it's flawed in some way
[20:59] <seb128> tjaalton, bryceh: we aware of http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d07807ca68e7d3f0b94fdce9bc2a88a71d4324ef as well
[21:00] <seb128> we->be
[21:00] <seb128> not sure if that could impact on what you are testing
[21:00] <seb128> that's the patch I want to update, but now I'm late, it's freeze time, I shouldn't have waited for tjaalton :p
[21:01] <tjaalton> what prerelease freeze?
[21:01] <tjaalton> seb128: sorry :)
[21:01] <seb128> tjaalton, the one starting at 21utc today
[21:01] <seb128> i.e now
[21:02] <seb128> which also suprised me, they were discussing it today on #ubuntu-release, from now one archive should be frozen again and uploads will be approved
[21:02] <tjaalton> i thought it was next week
[21:02] <seb128> skaet argued that previous cycle we didn't unfreeze after beta2
[21:02] <tjaalton> ok then
[21:02] <seb128> release freeze is next week
[21:02] <seb128> bug fixes should still be ok meanwhile
[21:03] <seb128> they just need to be approved
[21:03] <tjaalton> right
[21:03] <seb128> not sure there will be lot of approvers during the long w.e though
[21:03] <tjaalton> guess I should get uploads rolling and not fight with silly sponsors who question my skills to package a source package for debian :)
[21:03] <tjaalton> and then merge those
[21:04] <seb128> ;-)
[21:04] <seb128> tjaalton, btw while you are there
[21:04] <seb128> tjaalton,  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/comments/19
[21:04] <seb128> tjaalton, what do you think about that?
[21:05] <seb128> tjaalton, it's a workaround until g-s-d learns to not get unhappy on unknown devices but seems it could still be worth to ship with libwacom until then?
[21:05] <tjaalton> seb128: can't check the details, but there are some fixes in the driver git which might help there
[21:08] <tjaalton> meh, i'll switch to the desktop so I'll have a browser
[21:17] <tjaalton> seb128: checking the code
[21:20] <tjaalton> seb128: yeah, the device-id is the same, so adding the new stylus id should be ok
[21:20] <tjaalton> adding it to the same data file that is
[21:21] <seb128> tjaalton, can you do it in the next upload?
[21:21] <tjaalton> seb128: sure thing
[21:21] <seb128> tjaalton, thanks
[21:24] <tjaalton> hmm, I could upload it to debian now, and sync
[21:27] <bdmurray> bryceh: you said something about a disconnect between where you touch on your screen and the cursor location?  I've noticed the same thing
[21:27] <tjaalton> I think it's the same with my intuos too
[21:27] <tjaalton> Sarvatt: so it would cover your n-trig woes as well
[21:29] <bryceh> bdmurray, yep
[21:29] <bryceh> bdmurray, doesn't seem to affect the stylus, just touch
[21:29] <bdmurray> bryceh: yeah same thing with the stylus
[21:30] <bryceh> bdmurray, you see the same misbehavior with the stylus?  odd, I don't
[21:30] <bryceh> tjaalton, would it be worthwhile for me to tinker with the patch locally? 
[21:31] <bdmurray> bryceh: I meant yeah the stylus works for me too
[21:31] <bryceh> bdmurray, aha
[21:31] <tjaalton> bryceh: if you have the time then yes. you've seen what it tried to do, so it shouldn't be that hard to fix :)
[21:32] <bryceh> alright, adding to the todo stack for today
[21:32] <Sarvatt> tjaalton: WACOM_TYPE_TOUCH is only for actual touchpad capable wacoms
[21:32] <Sarvatt> aka bamboo touch
[21:32] <tjaalton> bryceh: the gsd plugin has the logic to check if the device is a screen tablet, so set_absolute should be true for those
[21:33] <tjaalton> Sarvatt: well that has been proven wrong now? :)
[21:33] <Sarvatt> ?
[21:33] <Sarvatt> guess i should read scrollback, i've been looking at g-s-d
[21:33] <tjaalton> the gsd code touches every device with the touch property
[21:33] <Sarvatt> yeah which serial wacoms dont have
[21:33] <Sarvatt> in libwacom
[21:34] <Sarvatt> unless i missed something
[21:34] <tjaalton> http://git.gnome.org/browse/gnome-settings-daemon/commit/plugins/wacom/gsd-wacom-manager.c?id=5dd89a267e7c539e681851017b18261dc2e092f0
[21:34] <tjaalton> this is where it broke
[21:34] <tjaalton> not libwacom
[21:34] <Sarvatt> tjaalton: oh they dont have Touch=false in the serial tablet definitions either
[21:35] <Sarvatt> tjaalton: most everything else has Touch=false if its not usable as a touchpad, serial wacom definitions in libwacom dont
[21:35] <tjaalton> well I changed that bit to use TRUE, and it turned my intuos to absolute mode, so I figured the condition was wrong
[21:36] <Sarvatt> ./isdv4-e3.tablet:# this is for the Wacom pen + touchscreen as found in the HP Touchsmart tm2 laptop.
[21:36] <Sarvatt> bdmurray's laptop is covered by a different set of definitions than generic serial wacom tablets
[21:36] <tjaalton> let me finish this changelog entry first :)
[21:36] <Sarvatt> so might explain why he sees different behavior
[21:37] <Sarvatt> oh nevermind, i'm gonna stop talking without reading the scrollback fully
[21:37] <tjaalton> bdmurray: so do you have the touch set in relative ("touchpad") or absolute ("pen tablet") mode?
[21:38] <Sarvatt> hell it'd be better to just revert that commit
[21:38] <bdmurray> Sarvatt: this is on an x201 tablet
[21:38] <tjaalton> Sarvatt: no, then all bamboos would be set in absolute mode..
[21:39] <tjaalton> or would they
[21:39] <bdmurray> tjaalton: either way I set it the behavior is the same
[21:39] <Sarvatt> i think there might be more laptops with touchscreens than bamboo tablets
[21:39] <tjaalton> if only I could login to my laptop I could test it :)
[21:40] <tjaalton> bdmurray: which is what? :)
[21:40] <Sarvatt> and they can change it in the gui if they prefer it the other way :P
[21:40] <tjaalton> Sarvatt: alas, no they can't :) it's not exposed for the touch
[21:40] <tjaalton> only for the pad
[21:42] <tjaalton> because of http://git.gnome.org/browse/gnome-settings-daemon/commit/plugins/wacom/gsd-wacom-manager.c?id=389276ef566342c3c61547326c070a0d6914622a
[21:45] <tjaalton> bdmurray: I mean, is the touchscreen functionality in absolute mode on both the login screen _and_ in the session, or just the login screen
[21:46] <tjaalton> the latter is what everyone else is seeing
[21:46] <Sarvatt> ok touch is a weird thing here, some people are referring to it for touchscreens where you want absolute, other people are referring to it for touchpads where you want relative.. you'd only want relative on tablets with a touchpad on them which is a smallllllllll minority of them
[21:47] <Sarvatt> like the definitions for the touchsmart tm2 have it listed as a touch device
[21:47] <Sarvatt> when its just the screen
[21:47] <tjaalton> well the only one complaining about it upstream is a bamboo user/dev
[21:48] <tjaalton> ie jason gerecke, the wacom dude :)
[21:48] <bdmurray> tjaalton: ah at the login screen it is 'absolute mode' if that means the cursor follows my finger
[21:48] <tjaalton> bdmurray: yess, and that's what it should always have
[21:50] <tjaalton> a lazy person would just reopen gnome bug 670655 and let them know that touchscreens are broken, but why not try to create a patch in the meantime
[21:54] <Sarvatt> bryceh, bdmurray: if you have a moment, can you add Touch=false to the bottom of /usr/share/libwacom/serial-wacf004.tablet and try logging in again?
[21:54] <tjaalton> that would just disable the touch part?
[21:55] <bryceh> sure
[21:55] <Sarvatt> there is no touch part
[21:55] <tjaalton> huh?
[21:55] <Sarvatt> its a friggin touch screen not a touchpad
[21:55] <tjaalton> yes, touch screen with finger + pen touch
[21:55] <Sarvatt> the touch detection i see in g-s-d is only for wacom touchpads built into tablets to put them in relative mode..
[21:56] <bryceh> Sarvatt, alright done.  what am I looking for?
[21:56] <Sarvatt> just if its absolute after logging in
[21:57] <bryceh> nope, same misbehavior as before
[21:57] <Sarvatt> ok cool, thanks for checking it wasn't something that easy
[21:58] <bryceh> that was added to the [Features] section fwiw
[21:58] <Sarvatt> bryceh: wait, one more? Pad=false ?
[21:58] <bryceh> okie
[21:58] <Sarvatt> i'm just thinking maybe its assuming things if its not explicitly defined
[21:58] <tjaalton> doesn't that only change the configurator?
[22:00] <Sarvatt> tjaalton: what a headache :)
[22:00] <bryceh> nope, 
[22:00] <tjaalton> hmm
[22:01] <bryceh> btw in that file I see a DeviceMatch for serial:0000:0000
[22:01] <bryceh> are there pci ids to be checked?
[22:01] <Sarvatt> nope its serial
[22:01] <tjaalton> gsd_wacom_device_is_screen_tablet() does seem to ask stuff from libwacom
[22:01] <tjaalton> so looks like both need an update
[22:01] <tjaalton> libwacom_is_builtin
[22:02] <Sarvatt> /usr/share/libwacom/isdv4-e3.tablet is what blows my mind
[22:02] <Sarvatt> Touch=true for touchscreen, its only wacom for the touchscreen..
[22:02] <Sarvatt> libwacom is a ton of bug reports waiting to happen
[22:03] <tjaalton> what do you mean "its only wacom for the touchscreen"?
[22:03] <Sarvatt> tjaalton: oh wait a second here
[22:03] <tjaalton> surely isn't, there's Stylus etc there
[22:03] <Sarvatt> Builtin means it doesn't parse the external files doesnt it..
[22:04] <Sarvatt> ah nope
[22:04] <Sarvatt> so maybe you can make g-s-d not apply relative if BuiltIn=true
[22:04] <Sarvatt> since those are all touchscreens
[22:05] <Sarvatt> tjaalton: BuiltIn=false + Touch=true is ok for relative, just people using the pad surface with touch as a touchpad
[22:06] <tjaalton> yes, that's bamboo
[22:06] <Sarvatt> should be able to use the BuiltIn definition to separate out touchscreens where you'd want absolute from touchpads where you'd want relative
[22:09] <Sarvatt> ah yea libwacom_is_builtin like you found earlier
[22:10] <tjaalton> right
[22:10] <tjaalton> and it should work..
[22:11] <tjaalton> I mean, libwacom should be ok
[22:11] <Sarvatt> yeah
[22:11] <Sarvatt> its already used elsewhere to determine what graphics are shown in the ui
[22:11] <tjaalton> yep
[22:27] <Sarvatt> nifty, fedoras actually generating wacom udev rules from libwacom
[22:27] <Sarvatt> thats a great idea
[22:27] <tjaalton> yep
[22:28] <Sarvatt> bryce is going to try http://kernel.ubuntu.com/~sarvatt/wacom-touch-fix.patch out
[22:32] <tjaalton> alright :)
[22:32] <bryceh> also got some debuggery folded in with that in case it doesn't work
[22:37] <bryceh> btw, I see BuiltIn=true in the .tablet file if that matters...
[22:38] <tjaalton> yes, as should be
[22:38] <bryceh> bingo sarvatt
[22:39] <bryceh> http://paste.ubuntu.com/916692/
[22:39] <bryceh> (gnome-settings-daemon:7808): wacom-plugin-WARNING **: gsd_wacom_device_is_screen_tablet = 0
[22:39] <bryceh> (gnome-settings-daemon:7808): wacom-plugin-WARNING **: libwacom_is_builtin = 1
[22:40] <tjaalton> wth?
[22:40] <Sarvatt> my thoughts exactly...
[22:42] <Sarvatt> oh
[22:42] <Sarvatt> gsd_wacom_device_is_screen_tablet
[22:42] <Sarvatt> that might just check if its assigned to a screen tjaalton
[22:43] <Sarvatt> since you can bind the tablet to specific screens
[22:44] <tjaalton> hum, ok
[22:44] <bryceh> ftr this is the patch I used - http://paste.ubuntu.com/916697/
[22:48] <tjaalton> Sarvatt: or maybe device->priv->is_screen_tablet isn't initialized yet?
[22:53] <tjaalton> oh well, I don't care :) bryceh thanks for checking that out!
[22:55] <tjaalton> btw, downgrading to lightdm 1.1.9 didn't help my laptop
[22:56] <tjaalton> still can't login to the X session
[22:56] <tjaalton> the greeter seems stuck
[22:56] <tjaalton> doesn't bail out
[22:59] <bryceh> tjaalton, sure thing
[22:59] <bryceh> so, do we have a pushable patch?
[22:59] <tjaalton> bryceh: uploaded an update to the ppa
[22:59] <bryceh> great
[22:59] <tjaalton> likely so, but I'm not sure if seb pushed something already
[23:00] <tjaalton> so maybe it's best to let people test the ppa version and upload the fix to the distro after easter
[23:00]  * bryceh nods
[23:00] <bryceh> bdmurray, ^^
[23:02] <bdmurray> what ppa and package?
[23:02] <tjaalton> ppa:tjaalton/ppa
[23:02] <tjaalton> gnome-settings-daemon
[23:02] <tjaalton> 3.4.0-0ubuntu3.2
[23:03] <tjaalton> takes some time to build
[23:31]  * bryceh uploads xdiagnose 2.4
[23:34] <bryceh> I added a script xpci
[23:34] <bryceh> humber:~/src/xdiagnose/xdiagnose$ xpci
[23:34] <bryceh> RV770 (1002:9442) xserver-xorg-video-ati
[23:34] <bryceh> humber:~/src/xdiagnose/xdiagnose$ xpci 10de:0604
[23:34] <bryceh> G92 (10de:0604) GeForce 9800 GX2 xserver-xorg-video-nouveau,nvidia-graphics-drivers
[23:35] <bryceh> humber:~/src/xdiagnose/xdiagnose$ grep 'VGA ' /tmp/lspci_vvnn.txt | xargs xpci
[23:35] <bryceh> gm45 (8086:2a42) cantiga xserver-xorg-video-intel
[23:38] <bryceh> * skaet not feeling that comfortable about libwacom though....
[23:43] <tjaalton> bah :)
[23:44] <Sarvatt> bryceh: the libwacom change is so straight forward it isnt funny, i'm sure it'll pass review :)
[23:44] <tjaalton> me mentioning the "merge" probably scared her off
[23:44] <Sarvatt> then again there is this nasty change: +DM-Upload-Allowed: yes
[23:45] <tjaalton> doesn't affect ubuntu at all
[23:45] <Sarvatt> yeah was a joke
[23:45] <tjaalton> hah, ok