Linuxwacom 0.7.9-6 is now available. Included is a fix for this issue, it is
the easiest place to change to avoid the crash it seems. I had a look at the
place in the xserver source where the crash happened, but I could not see any
recent changes that should cause the crash only in Xserver
On tisdag 18 december 2007, Magnus Vigerlöf wrote:
[...]
I've got even more for you, maybe you can forward it to the appropriate
thread. Further up, Magnus Vigerlöf mentioned:
| In XkbIndicatorsToUpdate (./xkb/xkbLEDs.c:56) the call to
| XkbFindSrvLedInfo can potentially return
On Tue, Dec 18, 2007 at 10:38:53PM +0100, Magnus Vigerlöf wrote:
My session starts up with numlock enabled. When using my workaround of
switching to console during session startup, I noticed that the numlock
LED on the keyboard is inverted. Apparantly the unavailability of the
On måndag 17 december 2007, Ron wrote:
[...]
I've got even more for you, maybe you can forward it to the appropriate
thread. Further up, Magnus Vigerlöf mentioned:
| In XkbIndicatorsToUpdate (./xkb/xkbLEDs.c:56) the call to
| XkbFindSrvLedInfo can potentially return NULL, which is not an
On Sun, Dec 16, 2007 at 07:57:23PM +1030, Ron wrote:
Andreas, have you seen the discussion that was cc'd to the bts from
linuxwacom-discuss about this? Is what you are seeing the same
issue, or is this something else we should also be discussing there
as well?
It should be the same issue,
I'm not sure why the discussion on linuxwacom-discuss isn't visible
in the archive there too, I definitely got two copies of everything,
one from the list and one from the CC to the bts. I don't think much
missed going to the bts though.
I've forwarded this there now, in case this does point at
Andreas, have you seen the discussion that was cc'd to the bts from
linuxwacom-discuss about this? Is what you are seeing the same
issue, or is this something else we should also be discussing there
as well?
Cheers,
Ron
On Sun, Dec 16, 2007 at 02:53:26AM +0100, Andreas Bombe wrote:
On Tue,
On Tue, Dec 11, 2007 at 11:43:03PM +0100, Andreas Bombe wrote:
However it works when I start X from the console and later
gnome-session from the console like this:
$ X :1
[ wait for X to come up ]
$ DISPLAY=:1 gnome-session
*However* again, it crashes the same way when I start X and
Package: xserver-xorg-input-wacom
Version: 0.7.9.3-2
Followup-For: Bug #454568
I have the same problem when trying to start a GNOME session from gdm
with pretty much the same backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c660e]
1: [0xe420]
2: /usr/bin/X(ProcXkbLatchLockState+0x23d)
9 matches
Mail list logo
