Comment 17 for bug 405800

0.8.4.2-0.1 breaks my Twinview again. My cintiq is now stretched across both its own screen and the monitor.
I tried all variations of 'xsetwacom set stylus TwinView "[0-5]" ' and none of them had any effect. Well Mode 5 sort of had the effect that 'wacomcpl' would crash whenever I clicked the 'Screen Mapping' button.

the reported issue:

child killed: segmentation violation
child killed: segmentation violation
    while executing
"exec xsetwacom get $dev $Option($j) "
    (procedure "getDeviceOptionProc" line 7)
    invoked from within
"getDeviceOptionProc $device 3"
    (procedure "initialSet" line 11)
    invoked from within
"$initial"
    (procedure "displaySubWindow" line 32)
    invoked from within
"displaySubWindow updateSet defaultSet initialSet 4 0 0"
    invoked from within
".panel.advanced invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tk::ButtonUp" line 22)
    invoked from within
"tk::ButtonUp .panel.advanced"
    (command bound to event)

Once set to left of (5) 'xsetwacom get stylus TwinView' would only return a 'segmentation fault'. Maybe wacomcpl is mapping the modes wrong. i.e. from 1 to 6 instead of 0-5 so that 'left of' is 6 and what we get is an 'out of range' issue but I have no clue what's going on. It's really just frustrating right now.