GNOME Bugzilla – Bug 720722
Wacom settings GUI doesn't work for multi-monitor setup with Nvidia proprietary driver
Last modified: 2014-02-14 09:56:13 UTC
Hi, The Wacom settings GUI doesn't work for multi-monitor setup with Nvidia proprietary driver, on dual-monitor setup ( a widely used setup by Cintiq users, Wacom user, and graphist in General ; ex, all machines at Blender Institute ). * This affect : =============== - Mapping a tablet to a single screen ( with or without proportions kept ) - Doing a calibration to a single screen - Switch screen feature * Workaround : ============== Load at startup a custom wacom.sh script to map the screen to a single monitor, using Nvidia Twinview "HEAD-1" or "HEAD-0", and the right device ( found with 'xsetwacom --list devices' ) : | #! /bin/bash | xsetwacom set "Wacom Cintiq 21UX stylus" MapToOutput "HEAD-1" | xsetwacom set "Wacom Cintiq 21UX eraser" MapToOutput "HEAD-1" | xsetwacom set "Wacom Cintiq 21UX pad" MapToOutput "HEAD-1" The workaround doesn't solve 'Switch screen' feature, but at least user can do calibration, and got screen mapped correctly at startup ( and so, use his device ).
Thanks for the bug report, not a bad timing given I'm working on improving device mapping :). I however need some more information to know what's going wrong at the time of mapping devices on that setup: 1) You mention it's nvidia twinview, has it 2 wacom devices attached or is it 1 wacom device and 1 regular monitor? xinput --list and xrandr outputs would be handy here 2) From your description it seems that the tablet is left mapped to the whole span of monitors, although it's not entirely clear to me. Or is it other symptoms you're seeing, such as the wrong monitor being picked?. Also, this happens with stylus/eraser, right? 3) It'd be very appreciated if you could run g-s-d in a terminal through G_MESSAGES_DEBUG=all /usr/libexec/gnome-settings-daemon --debug -r, I'm specially interested in the output at the time of plugging the cintiq, first the graphics cable and then the usb one
Oh, one more thing... "switch screen" feature isn't quite meant to work on tablets attached to a display like cintiqs, I was tending to think on purpose... Are you regularly using the tablet as a displayless one?
Hi Carlos, thanks for working on it ( and good work ! I enjoy all other parts ). 1) >> has it 2 wacom devices attached or is it 1 wacom device and 1 regular monitor? It is one 'tablet' device ( the Cintiq 21ux ), and two screens : a 1600x1200 on left ( Cintiq 4:3 ratio ) and a 1920x1200 on right ( Asus ProArt 16:10 ratio ). a) xinput --list : ================== ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Wacom Cintiq 21UX stylus id=8 [slave pointer (2)] ⎜ ↳ Razer Razer DeathAdder id=9 [slave pointer (2)] ⎜ ↳ Wacom Cintiq 21UX eraser id=13 [slave pointer (2)] ⎜ ↳ Wacom Cintiq 21UX pad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ NOVATEK USB Keyboard id=10 [slave keyboard (3)] ↳ NOVATEK USB Keyboard id=11 [slave keyboard (3)] ↳ DELL Dell QuietKey Keyboard id=12 [slave keyboard (3)] b) xrandr ================== Screen 0: minimum 8 x 8, current 3520 x 1200, maximum 8192 x 8192 DVI-I-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.0 70.1 60.0 800x600 85.1 75.0 72.2 60.3 56.2 640x480 85.0 75.0 72.8 59.9 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1200+1600+0 (normal left inverted right x axis y axis) 546mm x 352mm 1920x1200 60.0*+ 1920x1080 60.0 60.0 59.9 50.0 60.1 60.0 50.0 1680x1050 60.0 1600x1200 60.0 1440x900 59.9 1366x768 59.8 1280x1024 75.0 60.0 1280x960 60.0 1280x720 60.0 59.9 50.0 1152x864 75.0 1024x768 75.0 70.1 60.0 800x600 75.0 72.2 60.3 56.2 720x576 50.0 720x480 59.9 640x480 75.0 72.8 59.9 59.9 2) >> From your description it seems that the tablet is left mapped to the whole span of monitors, although it's not entirely clear to me. Or is it other symptoms you're seeing, such as the wrong monitor being picked?. Also, this happens with stylus/eraser, right? Right, with vanilla configuration out-of-the-box ; the Cintiq is mapped to both screen. When I try with the Gnome-setting Wacom panel a first calibration; I can't even hit the 'target/aim' displayed ; because the 'target/aim' displayed appear only on my Cintiq screen device. So, I have to hit 'cancel'. 3) >> It'd be very appreciated if you could run g-s-d in a terminal through G_MESSAGES_DEBUG=all /usr/libexec/gnome-settings-daemon --debug -r, I'm specially interested in the output at the time of plugging the cintiq, first the graphics cable and then the usb one I can do it, but I need to find 2 big hours for it. I would need reset my startup script, restart computer after unconnecting totally Cintiq. And run the test, then refixing my config. As I'm on a production machine, with daily artwork to commit it's not easy. I'll see on week-end. 4) >> Oh, one more thing... "switch screen" feature isn't quite meant to work on tablets attached to a display like cintiqs, I was tending to think on purpose... Are you regularly using the tablet as a displayless one? When having a big one as me ( 21' inch ) switching is a nice gadget. Its not practical to really 'paint' on the second display ; but more to change song, focus the right reference image, click to read an email , etc... For smaller Cintiq as 12WX or newer ; it is a must-have feature ; they paint mostly on external screen as a traditional tablet ; and use embedded small screen for painting details, or sketching. It's sort of hybrid work-flow.
I forgot to say here, thanks for that information. I've been working on improving device mapping on bug #709600 with this and other usecases in mind. Now the patches there have been pushed to git master, and I'm closing this bug as a duplicate of that one. *** This bug has been marked as a duplicate of bug 709600 ***
Oh very cool ! Thank you very much for your time on solving this issue !