I have an issue I don't seem to find any explanation for. My issue seems
not to be directly related to the LinuxWacom driver, but I'd like other
users of either Xorg 1.3 (7.2.99 / 7.3) and/or GDM 2.18.3 or newer to
confirm this. If the Wacom tablet is configured in Xorg and working
regularly, GDM works just "fine" (well, maybe you are unable to move the
mouse pointer while in the greeter screen, cursor moves to lower right
corner). At any rate, the issue I'm experiencing in such a configuration
(Fedora 7) is that if I detach the tablet from the computer and restart
X (or simply log out) GDM won't start again, X is fine, a message may
appear stating that there has been a problem running the login manager,
and then restarts... in cycles. I've narrowed the problem to a
correlation in Xorg and GDM log files. Xorg will be unable to find and
initialize the /dev/input/wacom device (obviously, as it is detached
from the computer), GDM will catch this error from X and will also print
it out to its own log as the reason why it is not able to start...
=== GDM log ===
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux Blackhawk 2.6.22.1-27.fc7 #1 SMP Tue Jul
17 17:19:58 EDT 2007 x86_64
Build Date: 11 June 2007
Build ID: xorg-x11-server 1.3.0.0-9.fc7
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 25 12:38:41 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
FATAL: Module evdev not found.
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
=== Xorg.0.log ===
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Success
In my Xorg.conf file there's an exception for the mice devices to allow
X to start even in failure to initialize the device...
=== Xorg.conf - ServerFlags ==
Section "ServerFlags"
Option "AllowMouseOpenFail" "yes"
Option "AIGLX" "on"
EndSection
Looks like the Wacom InputDevice entries are not being treated as mice
devices at all, but other serial devices. I wonder if other users with
similar configurations in other distributions have the same issue with
GDM or in even Fedora 7 (but with KDM for example), or if this might in
any way be imputable to the LinuxWacom driver (which I highly doubt).
This poses problem for me, as in the environment I need this working
there are more computers than tablets available, and the tablets are
constantly moved from one system to another, however, for obvious
reasons, a situation like this is a rather serious problem. I wouldn't
want to move the whole lab to another distribution, currently we're
using FC6 for the production environment, but if this wouldn't be a
problem in another distribution with the same features set as Fedora 7,
I'd be willing to take my chances...
Do you think there might be a workaround for this? Thus far I've been
unable to find any.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
