[06:24] <Duke`> wow, I got a serious speed improvement after upgrading this morning
[06:25] <Duke`> I hope nothing is broken after those optimisations
[10:46] <virtuald> what package should kms bugs be reported against?
[10:47] <tjaalton> the kernel
[10:48] <tjaalton> = "linux"
[10:48] <virtuald> ok but then do apport include Xorg logs?
[10:55] <tjaalton> probably not
[10:55] <tjaalton> you can file it against the driver too
[10:56] <tjaalton> it'll get reassigned to the kernel if it turns out to be a kernel bug
[11:01] <virtuald> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/388467 how do i use this?
[11:09] <tjaalton> dunno
[11:42] <apw> virtuald, i think you can file it against the kernel and then add X stuff using apport-collect
[11:43] <virtuald> ok
[11:43] <virtuald> yes, thank you
[11:44] <apw> virtuald, whats the kms bug you are seeing ...
[11:44] <apw> i am not sure i'd know a bug was kms related
[11:45] <virtuald> i haven't posted it
[11:46] <virtuald> on rv570 when x gdm starts the screens turn off
[11:46] <virtuald> then they turn on and off with about a minute in between
[11:46] <virtuald> but it's just black
[11:46] <virtuald> once there were some garbled lines before they turned off
[13:23] <tormod> tjaalton: can you have a look at bug 429700?
[13:25] <tjaalton> tormod: sure, my mistake
[13:26] <tormod> thanks
[13:33] <virtuald> Ok so now I'm on my mobile and can login to my gpu hung computer from here
[13:34] <virtuald> But I forgot to check on the Wiki what to en
[13:35] <virtuald> What to do
[13:46] <tseliot> tjaalton: where did you upload the packages mentioned in bug #405800?
[13:49] <tjaalton> tseliot: nowhere yet
[13:54] <tseliot> tjaalton: ok, please let me know if you do it. I have a tablet for testing.
[13:54] <tjaalton> just uploaded it to my ppa
[13:56] <tseliot> ok, thanks
[15:08] <tseliot> tjaalton: my tablet works, xinput mentions it but "xsetwacom list" doesn't return anything
[15:09] <loic-m_> tseliot: I think that's expected with 0.8.4.1
[15:10] <tseliot> loic-m_: is it a feature? :-P
[15:12] <tseliot> AFAIK it's not possible to make the tablet work decently with xinerama without xsetwacom
[15:12] <loic-m_> tseliot: not that I can think of... xsetwacom still work for sending commands, but the list doesn't show any thing anymore (can't find the thread) since one of the 0.8.3 versions at least
[15:13] <loic-m_> tseliot: you should try sending a command and see if it works, the "list" doesn't give much (not sure if it's due to new versions of the driver or new Xorg versions)
[15:14] <tseliot> I'm downloading the source code so as to see what the "list" option does
[15:24] <tseliot> ListDev() must be failing for some reason
[15:26] <loic-m_> From my testing of the previous drivers in Karmic, xsetwacom list didn't show anything either, I had to use xinput list --short
[15:26] <loic-m_> I don't remember for Jaunty, might reboot into it tonight
[15:30] <tseliot> loic-m_: ok, it's important to know that this isn't caused by a regression in the driver
[15:30] <tseliot> in the new driver, I mean
[15:32] <loic-m_> tseliot: you should still test it yourself with 0.8.3 from the repositories, but at least for Intuos3 tablets I tested it didn't work, and some forums threads mentionned it didn't work since 0.8.3 (they're 30 pages long, so hard to remember where it was)
[15:32] <loic-m_> Ill reboot into Jaunty, bbl
[15:57] <loic-m> tseliot: xsetwacom list doesn't work either in Jaunty, just checked, so it could be due to Xorg 1.6
[15:59] <tseliot> loic-m: I'm getting a lot of segfaults from xsetwacom when I try to use the TVResolution0 and TVResolution1 options
[15:59] <tseliot> or the Twinview option
[16:00] <tjaalton> might be fun to try 0.9 how the input properties work
[16:00] <loic-m> I got segfaults with Twinview and 0.8.3.2 in Karmic, never tried the TVResolution# options
[16:01] <loic-m> however, upstream changelog said it fixed a/some bug(s) with Twinview, it's a shame if it still doesn't work
[16:02] <tseliot> tjaalton: can they work worse then the current xsetwacom? Will they format my hard disk? :-P
[16:02] <tjaalton> tseliot: care to find out?-)
[16:03] <loic-m> Nope, I was wrong, it was about Nvidia non-TwinView setting :(
[16:03] <tseliot> tjaalton: maybe wacom-tools should be updated?
[16:03] <loic-m> what's 0.9?
[16:04] <tseliot> tjaalton: actually, I take back what I said
[16:04] <tseliot> loic-m: the next release. whot is working on it
[16:04] <tjaalton> loic-m: the one whot and ping are working on
[16:04] <tseliot> unless I'm wrong
[16:05] <tseliot> ok, I'm not ;)
[16:05] <loic-m> great. Ping say he's going to be busy the next 6 month, I didn't expect next release to be around soon
[16:05] <tjaalton> I'll try this new version with my waltop after the reboot
[16:06] <loic-m> btw, Timo, Upstream just released 0.8.4.2 ;)  - I'm sure you wished you waited one more day...
[16:06] <tjaalton> uh
[16:06] <tjaalton> what changed?
[16:06] <tseliot> \o/
[16:07] <jcristau> "September 16, 2009 - Fixed a mapping issue introduced by non-TwinView support. Label 0.8.4-2. "
[16:08] <loic-m> just a bugfix of a feature that wasn't there pre-0.8.4.2 then
[16:08] <tseliot> ok, this might be interesting
[16:09] <tseliot> it looks more like a regression introduced by the new feature
[16:10]  * tseliot restarts X
[16:24] <tjaalton> still crashes the server when trying to use the crappy waltop
[16:25] <tjaalton> "127f is not supported by linuxwacom"
[16:25] <tjaalton> what a way to tell that
[16:32] <tjaalton> if (sID[1] == 0x056A) { ... } else { ErrorF("%x is not supported by linuxwacom.\n", sID[1]);
[16:32] <tjaalton> great
[16:32] <tseliot> hehe
[16:34] <tjaalton> 056A is the vendor id of wacom
[16:37] <tjaalton> seems like the device was previously detected as a serial tablet
[16:42] <tseliot> so they dropped the support for your tablet?
[16:43] <tjaalton> the code path used to be different for some reason, now it actually knows it is a usb device, and fails because the vendor id doesn't match
[16:47] <tseliot> you could try with if ((sID[1] == 0x056A) || (sID[1] == 0x127f)) {...} etc. just to see whether your tablet is supported or not
[16:47] <tjaalton> yep, trying that now
[16:52]  * tjaalton wants an intuos4 L..
[16:52] <tseliot> heh
[16:57] <loic-m> tjaalton: intuos3 should be cheap now secondhand, and the support should also be better...
[16:57] <loic-m> and for wacom tablets, second hand  = new
[16:58] <loic-m> and you can resell i afterwards (try that with a Waltop...)
[16:58] <loic-m> s/i/it/
[16:59] <tjaalton> but intuos4 looks good :)
[16:59] <tjaalton> this was meant to be a toy for the kids
[17:00] <tjaalton> at least it doesn't crash now, but there's still the same error msg
[17:02] <tseliot> tjaalton: maybe there's some other check you haven't noticed
[17:04] <loic-m> intuos4 sure would be nice, since they reduced the pressure need for registering contact with the tablet, one of my main gripe with Tablets
[17:11] <tjaalton> tseliot: nah, was looking at the wrong logfile..
[17:11] <tseliot> aaah, ok
[17:12] <tjaalton> it sets up the device, but nothing happens when I try to use it
[17:12] <tseliot> so they did drop the support for your tablet
[17:12] <tseliot> :-/
[17:15] <tjaalton> when the driver detected it as a serial device, it worked
[17:16] <tjaalton> doesn't look like the driver changed
[21:04] <pwnguin> im not sure why they ever added support for waltop
[21:06] <tjaalton> who they?
[21:07] <tjaalton> I don't think wacom added anything, it just used to work
[21:08] <tjaalton> out of sheer luck
[21:08] <jcristau> luck is good.
[21:08] <jcristau> :)
[21:08] <tjaalton> if it's not bad
[21:09] <tjaalton> well, evdev works somewhat, but it's detected as a keyboard
[21:10] <pwnguin> right now my tabletPC is angry about a filesystem from the future
[21:11] <tjaalton> should be fixed by the latest kernel