After the update from stable xorg-server-1.3.0-r6 to stable xorg-server-1.5.3-r5 inlcuding hal and evdev, my Wacom Graphire tablet didn't work as expected anymore. I changed the configuration according to the xorg-1.5 upgrade guide (http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.5-upgrade-guide.xml) using fdi-files for configuration and I only got one working type (either stylus, eraser or cursor). This behavior is also explained in the provided fdi-file: <!-- Wacom isn't yet suited well for hotplugging, as we need three devices off one kernel device, but HAL only reports this device once. This needs fixing in the driver. Use stylus by default for this single device, if you want erasor or cursor, specify in the line below. --> This occurs with the latest stable linuxwacom (x11-drivers/linuxwacom-0.8.2) aswell as the testing version (x11-drivers/linuxwacom-0.8.2_p2) I now found that in Rawhide (perhaps already fedora), this behavior seems to be corrected with the following patch: http://cvs.fedoraproject.org/viewvc/rpms/linuxwacom/devel/linuxwacom-0.8.2.2-hal-setup.patch?revision=1.1&view=markup As far as I understood the general problem, HAL has a problem making the (three) devices out of one kernel device. But with this patch, HAL should be able to manage this. Therefore I was wondering if this behavior could be included into the next x11-drivers/linuxwacom, as this would only be a consequent measure in migrating to HAL. WORKAROUND: configuration traditionally in xorg.conf and _not_ in a fdi-file. Reproducible: Always Steps to Reproduce: 1.update to xorg-server-1.5.3-r5 with hal-support (USE=hal) 2.use fdi-file instead of configuration in xorg.conf Actual Results: Only one type (etiher stylus, eraer or cursor) is working at a time. Appending additional types (e.g. <merge key="wacom.types" type="strlist">eraser,cursor,pad</merge>) doesn't work. Expected Results: Stylus, eraser and cursor should all work at the same time. For a simple hardware configuration (just one tablet attached and the system is recognizing it correctly) no fdi-file should be required as HAL should do the configuration automatically. Portage 2.1.6.7 (default/linux/amd64/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.29-gentoo_dyno x86_64) ================================================================= System uname: Linux-2.6.29-gentoo_dyno-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q6600_@_2.40GHz-with-glibc2.2.5 Timestamp of tree: Fri, 10 Apr 2009 09:15:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7-r1, 2.1.7 dev-lang/python: 2.4.4-r6, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 dev-util/cmake: 2.6.2-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/tmp/distfiles" EMERGE_DEFAULT_OPTS="--with-bdeps y" FEATURES="ccache distlocks fixpackages grc parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo " LANG="de_DE@euro" LDFLAGS="-Wl,-O1" LINGUAS="de" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X a52 aac aalib alsa amd64 amr amrnb amrwb apache2 apm arts avi bash-completion beep berkdb bitmap-fonts bzip2 cairo cdr chroot cjk crypt cups curl d dbus directfb divx4linux dri dts dvd dvdr dvdread encode esd fbsplash firefox font-server foomaticdb fortran gdbm gif gimp glade gpm gtk gtk2 hal ieee1394 imagemagick imlib ipv6 java jpeg jpeg2k junit kde kdeenablefinal libclamav libg++ libwww mad midi mjpeg mmx motif mozilla mozsvg mp3 mpeg mpeg2 mpeg4 mplayer multilib ncurses nls nptl nptlonly nsplugin odbc ogg oggvorbis opengl oss pam pdf pdflib perl plotutils png posix postgres ppds python qt3 qt4 quicktime readline samba sdl slang sse sse2 ssl ssse3 subversion svg tcl tcpd tetex tga tiff tk truetype truetype-fonts type1-fonts unicode usb vim vim-with-x visualization vorbis wmf wxwindows xcomposite xine xinerama xml xml2 xorg xosd xpm xprint xv xvid xvm zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="dmix asym empty plug null adpcm alaw copy dshare dsnoop extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev wacom" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Thanks for your bug report Cedric. I've bumped the linxuwacom ebuild in my overlay (ikelos) to linuxwacom-0.8.3_p2, which is the latest development version available from upstream. This already features HAL support, and I've just tried it now, it seems to be doing very well. One thing to note is that after you've installed this, you'll need to restart the HAL service (or send it some appropriate signal) so that it rereads the .fdi files available in the shared directory. Once that's done (and X restarts), everything should just work... 5:) Please let me know here if you run into any trouble with it, otherwise it will get pushed to the main tree in the next couple of weeks (and feel free to give me a prod should I forget). Thanks! 5:)
(In reply to comment #1) > Thanks for your bug report Cedric. I've bumped the linxuwacom ebuild in my > overlay (ikelos) to linuxwacom-0.8.3_p2, which is the latest development > version available from upstream. This already features HAL support, and I've > just tried it now, it seems to be doing very well. > > One thing to note is that after you've installed this, you'll need to restart > the HAL service (or send it some appropriate signal) so that it rereads the > .fdi files available in the shared directory. Once that's done (and X > restarts), everything should just work... 5:) > > Please let me know here if you run into any trouble with it, otherwise it will > get pushed to the main tree in the next couple of weeks (and feel free to give > me a prod should I forget). Thanks! 5:) > Thank you for providing the package. Unfortunately it fails to compile with the follwing error: /bin/sh ../../libtool --mode=install /usr/bin/install -c 'xsetwacom' '/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/image//usr/bin/xsetwacom' /usr/bin/install -c .libs/xsetwacom /var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/image//usr/bin/xsetwacom make[3]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/util' make[2]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/util' Making install in xdrv make[2]: Entering directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/xdrv' make[3]: Entering directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/xdrv' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib64/xorg/modules/input" || /bin/mkdir -p "/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/image//usr/lib64/xorg/modules/input" /usr/bin/install -c -m 644 'wacom_drv.so' '/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/image//usr/lib64/xorg/modules/input/wacom_drv.so' make[3]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/xdrv' make[2]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/xdrv' Making install in 2.6.28 make[2]: Entering directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/2.6.28' make[2]: Nothing to be done for `install'. make[2]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src/2.6.28' make[1]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2/src' make[1]: Entering directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2' make[2]: Entering directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2' make[1]: Leaving directory `/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/work/linuxwacom-0.8.3-2' * Installing wacom module * * ERROR: x11-drivers/linuxwacom-0.8.3_p2 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 3804: Called die * The specific snippet of code: * die "Double check" * The die message: * Double check * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/linuxwacom-0.8.3_p2/temp/environment'. * This ebuild is from a repository named 'ikelos' * >>> Failed to emerge x11-drivers/linuxwacom-0.8.3_p2, Log file: If you need more of the emerge log, please let me know.
Sorry about that Cedric, I left a "die" in right at the end whilst I was testing the fdi file installation, and forgot to take it out. It's now been removed, please try again (sorry!)...
(In reply to comment #3) > Sorry about that Cedric, I left a "die" in right at the end whilst I was > testing the fdi file installation, and forgot to take it out. It's now been > removed, please try again (sorry!)... > Never mind :) After all, where all human ;) Great, thank you, also for you fast response, it works now out-of-the-box! However, there is a problem when using mouse _and_ stylus/eraser in GIMP. I shows the following behavior and the mentioned workarounds work also, Unfortunately only until the next use of the stylus/eraser. This means, the use of mouse and stylus/eraser can _not_ be arbitrarily mixed, which is undesired IMHO. http://groups.google.com/group/comp.graphics.apps.gimp/browse_thread/thread/e57fd940ccd37770 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463772 http://bugzilla.gnome.org/show_bug.cgi?id=406440 As stated there also, Inkscape has no problems with mixed input. Therefore I tried to setup my xorg.conf of the stylus and eraser as fdi-files and ran into the next problem: KDE is starting up, but all of a sudden, it dies and brings me back to the login-screen of xdm/kdm. So apparently, either it doesn' work to configure manually with the new linuxwacom version or one has to be very careful with the configuration. I only tried some of the possible combinations. This problem seems GIMP related as in Inkscape it works and stylus/eraser work great under KDE also, thus I think it's rather unrelated to this bug. However, it might help someone when encountering the same problem.
(In reply to comment #4) > Never mind :) After all, where all human ;) > Great, thank you, also for you fast response, it works now out-of-the-box! > > However, there is a problem when using mouse _and_ stylus/eraser in GIMP. > I shows the following behavior and the mentioned workarounds work also, > Unfortunately only until the next use of the stylus/eraser. This means, the use > of mouse and stylus/eraser can _not_ be arbitrarily mixed, which is undesired > IMHO. > http://groups.google.com/group/comp.graphics.apps.gimp/browse_thread/thread/e57fd940ccd37770 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463772 > http://bugzilla.gnome.org/show_bug.cgi?id=406440 > > As stated there also, Inkscape has no problems with mixed input. > > Therefore I tried to setup my xorg.conf of the stylus and eraser as fdi-files > and ran into the next problem: KDE is starting up, but all of a sudden, it dies > and brings me back to the login-screen of xdm/kdm. > So apparently, either it doesn' work to configure manually with the new > linuxwacom version or one has to be very careful with the configuration. I only > tried some of the possible combinations. > > This problem seems GIMP related as in Inkscape it works and stylus/eraser work > great under KDE also, thus I think it's rather unrelated to this bug. However, > it might help someone when encountering the same problem. > Sorry for this mess, but after writing the post I thought about recompiling GIMP as it also seems to have some HAL-relation (USE=hal). And tadaaa, I can now mix everything as I want! The only thing I need to do when wanting to use the mouse is to move the cursor out of the drawing window and then I can go back in it and draw with the mouse aswell. For me, all issues are now solved. Thanks again Mike!
*** Bug 266176 has been marked as a duplicate of this bug. ***
Ok, this has just been pushed to the tree, so I'm going to mark this as FIXED. If you have any issues with the driver, please open them as new bugs. Thanks... 5:)
