Intuos4 and pointer jitter

View: New views
17 Messages — Rating Filter:   Alert me  

Intuos4 and pointer jitter

by SHIRAKAWA Akira :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello everybody.

I hope somebody can help me solve this rather annoying problem I have
with my Intuos4 Medium tablet and Ubuntu. Because of it I'm forced to
use Windows.

On some areas on the corners of the tablet (screen) the pointer tends to
  shake lightly but visibly even though the pen is perfectly still
(pointer jitter). On the central area of the tablet the pointer appears
instead to behave normally.

This happens under Gnome on Ubuntu 9.04 and 9.10 RC (latest version at
the time I'm writing). I tried to change USB ports, switch PC, and also
change my Intuos4 pen, but with no luck.
If I increase the Suppress value to higher values than default (30-40)
this issue is somewhat mitigated, but at the cost of a sluggish cursor
response, and when the pointer starts moving it still shakes a little
anyway: it's not really a viable solution.
Setting Suppress to 0 makes the pointer shake lightly but annoyingly
almost everywhere on the screen. Oddly enough, with my previous Bamboo
Fun tablet I didn't have any problem at all. Xidump reveals that on some
areas around the corners of the tablet X and Y coordinates vary randomly
  and constantly back and forth by a maximum 25-30 units.

I tried to install the new 0.8.5 development linuxwacom drivers, but
with no luck. This problem appears to be occurring only on Linux: on
Windows (Vista and Seven) on the same PC with the official Wacom drivers
my Intuos4 tablet works flawlessly, and the pointer is perfectly stable
everywhere on the screen.

Does anybody else have this rather annoying problem under Linux with the
Intuos4 tablet? I'm not really sure if this issue is due to a driver or
a hardware problem. But again, the tablet works perfectly on Windows.

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by Eric Honaker :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Well, I can say that I don't have this issue at all.  I am also running Ubuntu 9.04 with an Intuos 4 medium.  Not helpful to you, but it's a data point.

On Fri, Oct 23, 2009 at 10:19 AM, SHIRAKAWA Akira <shirakawa.akira@...> wrote:
Hello everybody.

I hope somebody can help me solve this rather annoying problem I have
with my Intuos4 Medium tablet and Ubuntu. Because of it I'm forced to
use Windows.

On some areas on the corners of the tablet (screen) the pointer tends to
 shake lightly but visibly even though the pen is perfectly still
(pointer jitter). On the central area of the tablet the pointer appears
instead to behave normally.

This happens under Gnome on Ubuntu 9.04 and 9.10 RC (latest version at
the time I'm writing). I tried to change USB ports, switch PC, and also
change my Intuos4 pen, but with no luck.
If I increase the Suppress value to higher values than default (30-40)
this issue is somewhat mitigated, but at the cost of a sluggish cursor
response, and when the pointer starts moving it still shakes a little
anyway: it's not really a viable solution.
Setting Suppress to 0 makes the pointer shake lightly but annoyingly
almost everywhere on the screen. Oddly enough, with my previous Bamboo
Fun tablet I didn't have any problem at all. Xidump reveals that on some
areas around the corners of the tablet X and Y coordinates vary randomly
 and constantly back and forth by a maximum 25-30 units.

I tried to install the new 0.8.5 development linuxwacom drivers, but
with no luck. This problem appears to be occurring only on Linux: on
Windows (Vista and Seven) on the same PC with the official Wacom drivers
my Intuos4 tablet works flawlessly, and the pointer is perfectly stable
everywhere on the screen.

Does anybody else have this rather annoying problem under Linux with the
Intuos4 tablet? I'm not really sure if this issue is due to a driver or
a hardware problem. But again, the tablet works perfectly on Windows.

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss



--
Eric Honaker
Dragonsept Arts and Publishing
http://www.dragonseptarts.com/

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by SHIRAKAWA Akira :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Eric Honaker wrote:
> Well, I can say that I don't have this issue at all.  I am also running
> Ubuntu 9.04 with an Intuos 4 medium.  Not helpful to you, but it's a
> data point.

Thanks anyway. At least it's a start. I hope it doesn't turn out I have
a hardware problem as I have experienced the same issue on two different
PCs. Once again, I have absolutely no problems under Windows (which I'm
using right now).

I must add that the jitter in my case occurs most noticeably when I
hover the pointer slowly vertically on the extreme right and left
corners of the tablet (roughly where the scrolling bars usually are, at
least on the right side). When I do the same by touching the tablet with
the tip of the pen it seems to jitter a bit less. Have you tried?

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Does moving your I4 away from your monitor or laptop or just moving a bit around make a difference?  The noise may be caused by the frequency of some other electronics. Not so sure.  Just a guess....
 
Ping 
On Fri, Oct 23, 2009 at 8:19 AM, SHIRAKAWA Akira <shirakawa.akira@...> wrote:
Hello everybody.

I hope somebody can help me solve this rather annoying problem I have
with my Intuos4 Medium tablet and Ubuntu. Because of it I'm forced to
use Windows.

On some areas on the corners of the tablet (screen) the pointer tends to
 shake lightly but visibly even though the pen is perfectly still
(pointer jitter). On the central area of the tablet the pointer appears
instead to behave normally.

This happens under Gnome on Ubuntu 9.04 and 9.10 RC (latest version at
the time I'm writing). I tried to change USB ports, switch PC, and also
change my Intuos4 pen, but with no luck.
If I increase the Suppress value to higher values than default (30-40)
this issue is somewhat mitigated, but at the cost of a sluggish cursor
response, and when the pointer starts moving it still shakes a little
anyway: it's not really a viable solution.
Setting Suppress to 0 makes the pointer shake lightly but annoyingly
almost everywhere on the screen. Oddly enough, with my previous Bamboo
Fun tablet I didn't have any problem at all. Xidump reveals that on some
areas around the corners of the tablet X and Y coordinates vary randomly
 and constantly back and forth by a maximum 25-30 units.

I tried to install the new 0.8.5 development linuxwacom drivers, but
with no luck. This problem appears to be occurring only on Linux: on
Windows (Vista and Seven) on the same PC with the official Wacom drivers
my Intuos4 tablet works flawlessly, and the pointer is perfectly stable
everywhere on the screen.

Does anybody else have this rather annoying problem under Linux with the
Intuos4 tablet? I'm not really sure if this issue is due to a driver or
a hardware problem. But again, the tablet works perfectly on Windows.

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by SHIRAKAWA Akira :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ping wrote:
> Does moving your I4 away from your monitor or laptop or just moving a
> bit around make a difference?  The noise may be caused by the frequency
> of some other electronics. Not so sure.  Just a guess....

I tried moving the tablet as far as one meter away from both my monitor
and pc (it's a desktop pc, by the way), but with no changes. Please note
that I do not have any wireless equipment around my workstation and that
both the power outlet and the pc power cable are properly grounded.

In the end to solve this problem (back in June, when I bought my I4) I
had to switch back to Windows. Today I tried again my tablet on another
PC with the recently released Ubuntu 9.10 RC, but I have exactly the
same problem, no matter what is the USB port or the driver I use.

I thought this could be a hardware problem (within the tablet, it can't
be the pen as I got it exchanged under warranty for other reasons, and
it didn't change anything), but if it was really so, wouldn't the same
issue occur on Windows too?

If you need me to do other testing, please do tell me.

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

If it works all right on Windows, it is not a hardware issue.  Email me your Xorg.0.log and xorg.conf (if you have one, if not the output of "xinput list").  I hope it is not a driver issue either :).
 
Ping
 
On Fri, Oct 23, 2009 at 8:55 AM, SHIRAKAWA Akira <shirakawa.akira@...> wrote:
Ping wrote:
Does moving your I4 away from your monitor or laptop or just moving a bit around make a difference?  The noise may be caused by the frequency of some other electronics. Not so sure.  Just a guess....

I tried moving the tablet as far as one meter away from both my monitor and pc (it's a desktop pc, by the way), but with no changes. Please note that I do not have any wireless equipment around my workstation and that both the power outlet and the pc power cable are properly grounded.

In the end to solve this problem (back in June, when I bought my I4) I had to switch back to Windows. Today I tried again my tablet on another PC with the recently released Ubuntu 9.10 RC, but I have exactly the same problem, no matter what is the USB port or the driver I use.

I thought this could be a hardware problem (within the tablet, it can't be the pen as I got it exchanged under warranty for other reasons, and it didn't change anything), but if it was really so, wouldn't the same issue occur on Windows too?

If you need me to do other testing, please do tell me.

--
SHIRAKAWA Akira


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by Emil Assarsson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,
I have this small jitter with a Cintiq 21UX but it's not that apperent
when I use program that uses the "high-resolution" data like Gimp. The
jitter is all over the screen but only when it jumps between the
screen pixel boundaries.
I don't know that much about the windows driver but they maybe uses
some kind of reduction of the jitter for the pointer. it might be an
idea to add some kind of "sluggishness" that average the last 10 ms
position data to the xorg driver for the pointer.
Do anyone know how the windows driver solves this? Can we find out?

--
Emil Assarsson



On Fri, Oct 23, 2009 at 5:59 PM, Ping <pinglinux@...> wrote:

> If it works all right on Windows, it is not a hardware issue.  Email me your
> Xorg.0.log and xorg.conf (if you have one, if not the output of "xinput
> list").  I hope it is not a driver issue either :).
>
> Ping
>
> On Fri, Oct 23, 2009 at 8:55 AM, SHIRAKAWA Akira <shirakawa.akira@...>
> wrote:
>>
>> Ping wrote:
>>>
>>> Does moving your I4 away from your monitor or laptop or just moving a bit
>>> around make a difference?  The noise may be caused by the frequency of some
>>> other electronics. Not so sure.  Just a guess....
>>
>> I tried moving the tablet as far as one meter away from both my monitor
>> and pc (it's a desktop pc, by the way), but with no changes. Please note
>> that I do not have any wireless equipment around my workstation and that
>> both the power outlet and the pc power cable are properly grounded.
>>
>> In the end to solve this problem (back in June, when I bought my I4) I had
>> to switch back to Windows. Today I tried again my tablet on another PC with
>> the recently released Ubuntu 9.10 RC, but I have exactly the same problem,
>> no matter what is the USB port or the driver I use.
>>
>> I thought this could be a hardware problem (within the tablet, it can't be
>> the pen as I got it exchanged under warranty for other reasons, and it
>> didn't change anything), but if it was really so, wouldn't the same issue
>> occur on Windows too?
>>
>> If you need me to do other testing, please do tell me.
>>
>> --
>> SHIRAKAWA Akira
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>



--
Emil

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by SHIRAKAWA Akira :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Emil Assarsson wrote:
> I don't know that much about the windows driver but they maybe uses
> some kind of reduction of the jitter for the pointer. it might be an
> idea to add some kind of "sluggishness" that average the last 10 ms
> position data to the xorg driver for the pointer.

Well, in Linux drivers there's already a "RawSample" setting which
averages the last N pointer position samples. Most Wacom tablets have a
133 Hz sample rate, so a RawSample of 4 samples (the default value)
already averages about 30 milliseconds of data (1000/133*4). Ramping up
this setting doesn't bring appreciable changes on jitter unless high
values are used (15 and up), which introduce in my opinion excessive
pointer lag.

Windows drivers work perfectly with no lag, so if they have some jitter
reduction feature, it's probably not just by averaging the last few data
samples.

By the way, if on Linux Wacom drivers we had an option to use on Intuos4
tablets the special 200 Hz sampling rate mode, a higher "RawSample"
setting could be used without adding more pointer lag (for a target of
30 ms, we could use a RawSample value of 6 with no difference compared
to the 133 Hz mode). To the developers reading this: are there any plans
to introduce this option in the near future? It's rather useful (not
only to raise RawSample, of course).

--
SHIRAKAWA Akira

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Two quick Questions

by Kory Prince :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Okay I have two quick questions about the 0.8.5 release:

1. What happened to the 64bit prebuilt folder?
2. What happened to the 2.6.31 kernel folder? Building now builds in the
2.6.28 folder. Is this okay? And will the module work for the a 2.6.31
kernel?

Thanks!
Kory


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Two quick Questions

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Quick answers inline.

Ping

On Sat, Oct 24, 2009 at 5:34 PM, Kory Prince <korylprince@...> wrote:
Okay I have two quick questions about the 0.8.5 release:

1. What happened to the 64bit prebuilt folder?

Did I miss to fill the prebuilt driver there (I can not access my system now)?  If that is the case, I'll make a new one soon.

2. What happened to the 2.6.31 kernel folder? Building now builds in the
2.6.28 folder. Is this okay? And will the module work for the a 2.6.31
kernel?

2.6.31 path was intended for Graphire BlueTooth support (the code for other models are exactly the same as in 2.6.28). I found Graphire BlueTooth has been supported in 2.6.31 kernel.org. So there is no need to duplicate the work here.

Ping

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Two quick Questions

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi group,

I am afraid I can not keep my promise this time - I am very busy testing a new release.  This release makes the two major features, "avoid duplicated devices and validate device type before adding it" that we included in 0.8.5, more reliable and user-friendly.  If the lack of 64 path doesn't cause too much issue in the next few days, please bear with me.  So, I can post one that is better than 0.8.5.

Thank you for your patience.

Ping

On Sat, Oct 24, 2009 at 10:20 PM, Ping <pinglinux@...> wrote:
Quick answers inline.

Ping

On Sat, Oct 24, 2009 at 5:34 PM, Kory Prince <korylprince@...> wrote:
Okay I have two quick questions about the 0.8.5 release:

1. What happened to the 64bit prebuilt folder?

Did I miss to fill the prebuilt driver there (I can not access my system now)?  If that is the case, I'll make a new one soon.

2. What happened to the 2.6.31 kernel folder? Building now builds in the
2.6.28 folder. Is this okay? And will the module work for the a 2.6.31
kernel?

2.6.31 path was intended for Graphire BlueTooth support (the code for other models are exactly the same as in 2.6.28). I found Graphire BlueTooth has been supported in 2.6.31 kernel.org. So there is no need to duplicate the work here.

Ping


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 and pointer jitter

by SHIRAKAWA Akira :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ping wrote:
> If it works all right on Windows, it is not a hardware issue.  Email me
> your Xorg.0.log and xorg.conf (if you have one, if not the output of
> "xinput list").  I hope it is not a driver issue either :).

Today I tried installing 0.8.5-1 Linux drivers on my Ubuntu machine, but
they didn't solve my problem. If it helps, I found out that this jitter
becomes VERY evident (the pointer becomes very shaky, impossible to not
notice it) when mapping the screen area to a very small area of the
tablet (for example 1x1 inches). I propose this as a test for other
Intuos4 users. Please set the mapping to a very small portion of the
tablet and see what happens.

By using a very small portion of the tablet I noticed also that
increasing the suppress value while mitigates this problem makes the
pointer move not very precisely, like if it was on a grid. On Windows
even if i select a very small area of the tablet the pointer moves very
smoothly with great precision, without shaking of course.

So Windows drivers:
- Don't appear to use a high suppress value, if at all
- Must set smoothness to a low value, as there is no perceived lag

I've read on the official Wacom forums that Intuos4 pens are
individually calibrated. I wonder if tablets too have some sort of
individual calibration and pass this information to Windows drivers in
order to provide smooth operation.

This problem I'm having (on two different PCs with different CPU/chipset
in the same place, but ONLY under Linux) must be either caused by
something missing in Linuxwacom drivers or in some other subsystem
(Xorg/Gnome/etc).

Yesterday I tried a 32 bit version of Ubuntu and I had the same problem.
In the following days I'll try different Linux distributions and desktop
managers and check what happens.

--
SHIRAKAWA Akira


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

xsetwacom segfaulting when setting Twinview

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello all

I am getting some weird behavior, that I was wondering if someone could
help me out?

I have compiled and installed 0.8.4-3 and it seems to be woring fine. I
can set the TwinView option in the xorg.conf file but I cannot set it
via xsetwacom because it segfaults.
eg /var/log/messages
Nov  3 16:07:25 crate kernel: xsetwacom[10076]: segfault at
0000000010000000 rip 00000030ace7b300 rsp 00007fff32b52638 error 4

other xsetwacom options work flawlessly

attached is my xorg file

I noticed that a previous thread referred to this and the suggested
solution was to remove
Option "ForceDevice" "ISDV4" # Tablet PC ONLY

But I don't have a line like that.

Any thoughts?

Grant

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildmeister@builder58)  Wed Jul 22 23:41:57 PDT 2009

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder58)  Wed Jul 22 23:41:13 PDT 2009
# Xorg configuration created by system-config-display
# This section added by Cfengine

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "stylus" "SendCoreEvents"
    InputDevice    "eraser" "SendCoreEvents"
    InputDevice    "cursor" "SendCoreEvents"
    InputDevice    "pad"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier     "stylus"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "stylus"
    Option         "USB" "on"
    Option         "Mode" "Absolute"
#    Option         "TwinView" "Horizontal"
EndSection

Section "InputDevice"
    Identifier     "eraser"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "eraser"
    Option         "USB" "on"
    Option         "Mode" "Absolute"
EndSection

Section "InputDevice"
    Identifier     "cursor"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "cursor"
    Option         "USB" "on"
    Option         "Mode" "Absolute"
EndSection

Section "InputDevice"
    Identifier     "pad"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "pad"
    Option         "USB" "on"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "HP LP2465"
    HorizSync       30.0 - 94.0
    VertRefresh     48.0 - 85.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "CIOverlay" "on"
    Option         "TwinView" "1"
    Option         "TwinViewXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "DFP-0: nvidia-auto-select +1920+0, DFP-1: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Parent Message unknown Re: xsetwacom segfaulting when setting Twinview

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

FYI
Attached is a backtrace and the Xorg.log after running the xsetwacom

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/crate:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-53.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux crate 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64
Build Date: 21 January 2009
Build ID: xorg-x11-server 1.1.1-48.52.el5
        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 Nov  4 16:12:45 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Device0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "stylus"
(**) |-->Input Device "eraser"
(**) |-->Input Device "cursor"
(**) |-->Input Device "pad"
(==) No FontPath specified.  Using compiled-in default.
(==) FontPath set to:
        unix/:7100,
        built-ins
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib64/xorg/modules"
(**) Option "Xinerama" "0"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.3
        X.Org Video Driver: 1.0
        X.Org XInput driver : 0.6
        X.Org Server Extension : 0.3
        X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib64/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib64/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org Video Driver, version 1.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,4003 card 103c,1307 rev 20 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,4021 card 0000,0000 rev 20 class 06,04,00 hdr 01
(II) PCI: 00:05:0: chip 8086,4025 card 0000,0000 rev 20 class 06,04,00 hdr 01
(II) PCI: 00:09:0: chip 8086,4029 card 0000,0000 rev 20 class 06,04,00 hdr 01
(II) PCI: 00:10:0: chip 8086,4030 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:10:1: chip 8086,4030 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:10:2: chip 8086,4030 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:10:3: chip 8086,4030 card 8086,8086 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:10:4: chip 8086,4030 card 8086,8086 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:11:0: chip 8086,4031 card 103c,1307 rev 20 class 06,00,00 hdr 00
(II) PCI: 00:15:0: chip 8086,4035 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:15:1: chip 8086,4035 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:16:0: chip 8086,4036 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:16:1: chip 8086,4036 card 103c,1307 rev 20 class 06,00,00 hdr 80
(II) PCI: 00:1b:0: chip 8086,269a card 103c,1307 rev 09 class 04,03,00 hdr 00
(II) PCI: 00:1c:0: chip 8086,2690 card 0000,0000 rev 09 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,2688 card 103c,1307 rev 09 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2689 card 103c,1307 rev 09 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,268a card 103c,1307 rev 09 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,268b card 103c,1307 rev 09 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,268c card 103c,1307 rev 09 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev d9 class 06,04,01 hdr 01
(II) PCI: 00:1f:0: chip 8086,2670 card 103c,1307 rev 09 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,269e card 103c,1307 rev 09 class 01,01,8a hdr 00
(II) PCI: 00:1f:2: chip 8086,2680 card 103c,1307 rev 09 class 01,01,8f hdr 00
(II) PCI: 10:00:0: chip 8086,3500 card 0000,0000 rev 01 class 06,04,00 hdr 81
(II) PCI: 10:00:3: chip 8086,350c card 0000,0000 rev 01 class 06,04,00 hdr 81
(II) PCI: 1e:00:0: chip 8086,3510 card 0000,0000 rev 01 class 06,04,00 hdr 01
(II) PCI: 1e:01:0: chip 8086,3514 card 0000,0000 rev 01 class 06,04,00 hdr 01
(II) PCI: 60:00:0: chip 10de,040f card 10de,049a rev a1 class 03,00,00 hdr 00
(II) PCI: 80:00:0: chip 8086,10b9 card 8086,1093 rev 06 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,128), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
        [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
        [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(II) Bus 0 prefetchable memory range:
        [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 128: bridge is at (0:1:0), (0,128,128), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 128 I/O range:
        [0] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
        [1] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
        [2] -1 0 0x00001800 - 0x000018ff (0x100) IX[B]
        [3] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]
(II) Bus 128 non-prefetchable memory range:
        [0] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[B]
(II) Bus 128 prefetchable memory range:
        [0] -1 0 0xf3300000 - 0xf33fffff (0x100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 96: bridge is at (0:5:0), (0,96,96), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 96 I/O range:
        [0] -1 0 0x00002000 - 0x00002fff (0x1000) IX[B]
(II) Bus 96 non-prefetchable memory range:
        [0] -1 0 0xf0000000 - 0xf2ffffff (0x3000000) MX[B]
(II) Bus 96 prefetchable memory range:
        [0] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 16: bridge is at (0:9:0), (0,16,64), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 16 non-prefetchable memory range:
        [0] -1 0 0xf3200000 - 0xf32fffff (0x100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 14: bridge is at (0:28:0), (0,14,14), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0006 (VGA_EN is cleared)
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-PCI bridge:
(II) Bus 30: bridge is at (16:0:0), (16,30,64), BCTRL: 0x0006 (VGA_EN is cleared)
(II) PCI-to-PCI bridge:
(II) Bus 17: bridge is at (16:0:3), (16,17,29), BCTRL: 0x0006 (VGA_EN is cleared)
(II) PCI-to-PCI bridge:
(II) Bus 32: bridge is at (30:0:0), (30,32,32), BCTRL: 0x0006 (VGA_EN is cleared)
(II) PCI-to-PCI bridge:
(II) Bus 64: bridge is at (30:1:0), (30,64,64), BCTRL: 0x0006 (VGA_EN is cleared)
(--) PCI:*(96:0:0) nVidia Corporation unknown chipset (0x040f) rev 161, Mem @ 0xf2000000/24, 0xc0000000/29, 0xf0000000/25, I/O @ 0x2000/7
(II) Addressable bus resource ranges are
        [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
        [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
        [0] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [1] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [2] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [3] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [4] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [5] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [6] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [7] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [8] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [9] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [10] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [11] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [12] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [13] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [14] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [15] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [16] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [17] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [18] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [19] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [20] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [21] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [22] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [23] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
        [0] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [1] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [2] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [3] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [4] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [5] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [6] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [7] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [8] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [9] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [10] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [11] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [12] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [13] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [14] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [15] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [16] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [17] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [18] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [19] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [20] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [21] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [22] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [23] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [5] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [6] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [7] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [8] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [9] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [10] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [11] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
        [14] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [15] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [16] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [17] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [18] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [19] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [20] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [21] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [22] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [23] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [24] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [25] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [26] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [27] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [28] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [29] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
        compiled for 4.0.2, module version = 1.0.0
        Module class: X.Org Server Extension
(II) NVIDIA GLX Module  185.18.29  Wed Jul 22 23:36:31 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib64/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
        compiled for 7.1.1, module version = 2.1.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "type1"
(II) Loading /usr/lib64/xorg/modules/fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.2
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "record"
(II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.13.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib64/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
        compiled for 4.0.2, module version = 1.0.0
        Module class: X.Org Video Driver
(II) LoadModule: "mouse"
(II) Loading /usr/lib64/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.1.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "kbd"
(II) Loading /usr/lib64/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.1.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "wacom"
(II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.6
(II) Wacom driver level: 47-0.8.4-3 $
(II) NVIDIA dlloader X Driver  185.18.29  Wed Jul 22 23:11:04 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 60:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib64/xorg/modules/libwfb.so
(II) Module wfb: vendor="NVIDIA Corporation"
        compiled for 7.1.99.2, module version = 1.0.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib64/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 0.1.0
        ABI class: X.Org Video Driver, version 1.0
(II) resource ranges after xf86ClaimFixedResources() call:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [5] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [6] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [7] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [8] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [9] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [10] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [11] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
        [14] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [15] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [16] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [17] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [18] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [19] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [20] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [21] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [22] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [23] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [24] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [25] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [26] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [27] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [28] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [29] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
(II) resource ranges after probing:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [5] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [6] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [7] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [8] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [9] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [10] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [11] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [12] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
        [13] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [14] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
        [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
        [17] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [18] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [19] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [20] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [21] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [22] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [23] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [24] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [25] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [26] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [27] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [28] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [29] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [30] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [31] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [32] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
        [33] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
        [34] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "1"
(**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select +1920+0, DFP-1: nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-1"
(**) NVIDIA(0): Option "CIOverlay" "on"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0):     enabled.
(II) NVIDIA(0): NVIDIA GPU Quadro FX 1700 (G84GL) at PCI:96:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 60.84.6a.00.12
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on Quadro FX 1700 at PCI:96:0:0:
(--) NVIDIA(0):     HP LP2465 (DFP-0)
(--) NVIDIA(0):     HP LP2465 (DFP-1)
(--) NVIDIA(0): HP LP2465 (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): HP LP2465 (DFP-0): Internal Dual Link TMDS
(--) NVIDIA(0): HP LP2465 (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): HP LP2465 (DFP-1): Internal Dual Link TMDS
(**) NVIDIA(0): TwinView enabled
(II) NVIDIA(0): Display Devices found referenced in MetaMode: DFP-0, DFP-1
(II) NVIDIA(0): Assigned Display Devices: DFP-0, DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):    
(II) NVIDIA(0):     "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 3840 x 1200
(--) NVIDIA(0): DPI set to (93, 92); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(WW) NVIDIA(0): UBB is incompatible with the Composite extension.  Disabling
(WW) NVIDIA(0):     UBB.
(WW) NVIDIA(0): Workstation overlay visuals are incompatible with the
(WW) NVIDIA(0):     Composite extension
(II) NVIDIA(0): Disabling overlays
(==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
        [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1 0 0xf3020000 - 0xf303ffff (0x20000) MX[B]
        [5] -1 0 0xf3000000 - 0xf301ffff (0x20000) MX[B]
        [6] -1 0 0xf3104400 - 0xf31047ff (0x400) MX[B]
        [7] -1 0 0xf3104000 - 0xf31043ff (0x400) MX[B]
        [8] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[B]
        [9] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B](B)
        [10] -1 0 0xc0000000 - 0xdfffffff (0x20000000) MX[B](B)
        [11] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B)
        [12] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
        [13] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [14] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
        [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
        [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
        [17] -1 0 0x00001000 - 0x0000101f (0x20) IX[B]
        [18] -1 0 0x000030b0 - 0x000030bf (0x10) IX[B]
        [19] -1 0 0x000030ec - 0x000030ef (0x4) IX[B]
        [20] -1 0 0x000030d8 - 0x000030df (0x8) IX[B]
        [21] -1 0 0x000030e8 - 0x000030eb (0x4) IX[B]
        [22] -1 0 0x000030d0 - 0x000030d7 (0x8) IX[B]
        [23] -1 0 0x000030a0 - 0x000030af (0x10) IX[B]
        [24] -1 0 0x000030e4 - 0x000030e4 (0x1) IX[B]
        [25] -1 0 0x000030c8 - 0x000030c8 (0x1) IX[B]
        [26] -1 0 0x000030e0 - 0x000030e0 (0x1) IX[B]
        [27] -1 0 0x000030c0 - 0x000030c0 (0x1) IX[B]
        [28] -1 0 0x00003060 - 0x0000307f (0x20) IX[B]
        [29] -1 0 0x00003040 - 0x0000305f (0x20) IX[B]
        [30] -1 0 0x00003020 - 0x0000303f (0x20) IX[B]
        [31] -1 0 0x00003000 - 0x0000301f (0x20) IX[B]
        [32] -1 0 0x00002000 - 0x0000207f (0x80) IX[B](B)
        [33] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
        [34] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode
(II) NVIDIA(0):     "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/input/mice"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) stylus: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) eraser: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/wacom
(**) cursor is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) cursor: reading USB link
(**) Option "BaudRate" "9600"
(**) pad device is /dev/input/wacom
(**) pad is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) pad: reading USB link
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 245 for button 1
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940 maxZ=2047 resX=5080 resY=5080  tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940 resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940 resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940 resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940 resol X=5080 resol Y=5080
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?

14:44 grants@crate: ~ 105 >gdb xsetwacom
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) r set stylus TwinView horizontal
Starting program: /usr/bin/xsetwacom set stylus TwinView horizontal

Program received signal SIGSEGV, Segmentation fault.
0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
(gdb) bt
#0  0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
#1  0x0000000000402336 in DoCommand (cmd=<value optimized out>,
    argv=<value optimized out>) at xsetwacom.c:882
#2  0x00000030ace1d974 in __libc_start_main () from /lib64/libc.so.6
#3  0x0000000000400ed9 in _start ()
(gdb)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: xsetwacom segfaulting when setting Twinview

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I guess somewhere the string was broken.  If you try:

xsetwacom set stylus TwinView 3

It should work.  I'll take a look into the code to see what is going.

Ping

On Wed, Nov 4, 2009 at 9:28 PM, Grant Street <grants@...> wrote:
FYI

Attached is a backtrace and the Xorg.log after running the xsetwacom

14:44 grants@crate: ~ 105 >gdb xsetwacom
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) r set stylus TwinView horizontal
Starting program: /usr/bin/xsetwacom set stylus TwinView horizontal

Program received signal SIGSEGV, Segmentation fault.
0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
(gdb) bt
#0  0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
#1  0x0000000000402336 in DoCommand (cmd=<value optimized out>,
   argv=<value optimized out>) at xsetwacom.c:882
#2  0x00000030ace1d974 in __libc_start_main () from /lib64/libc.so.6
#3  0x0000000000400ed9 in _start ()
(gdb)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: xsetwacom segfaulting when setting Twinview

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I found the root cause of this issue.  The fix will be in 0.8.5-2, which will be posted next week.

Thank you for reporting the problem

Ping

On Thu, Nov 5, 2009 at 9:02 PM, Ping <pinglinux@...> wrote:
I guess somewhere the string was broken.  If you try:

xsetwacom set stylus TwinView 3

It should work.  I'll take a look into the code to see what is going.

Ping

On Wed, Nov 4, 2009 at 9:28 PM, Grant Street <grants@...> wrote:
FYI

Attached is a backtrace and the Xorg.log after running the xsetwacom

14:44 grants@crate: ~ 105 >gdb xsetwacom
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) r set stylus TwinView horizontal
Starting program: /usr/bin/xsetwacom set stylus TwinView horizontal

Program received signal SIGSEGV, Segmentation fault.
0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
(gdb) bt
#0  0x00000030ace7b300 in strcasecmp () from /lib64/libc.so.6
#1  0x0000000000402336 in DoCommand (cmd=<value optimized out>,
   argv=<value optimized out>) at xsetwacom.c:882
#2  0x00000030ace1d974 in __libc_start_main () from /lib64/libc.so.6
#3  0x0000000000400ed9 in _start ()
(gdb)





------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

wacomcpl config file

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello

I noticed that previously wacomcpl updated a file called ~/.wacomcplrc
and this has changed at some point.

I also noticed there are two Feture requests about where wacomcpl writes
it's config files. ID: 1964221 and ID: 2767291

A default user in CentOS will not get a ~/.xinitrc nor a ~/.xsession. So
0.8.4 of wacomcpl will create a ~/.xinitrc.

I also noticed two things on CentOS and hence RHEL.
1 ~/.xinitrc is not loaded by default.
2 If I do put the generated one into the login flow the
/etc/X11/xinit/xinitrc would be run twice.

Background
We have a large number of linux desktops. I would like a sane default
config in the xorg.conf and I want the user's tablet preferences to
float with the user. The home directories are NFS mounted so putting
them in there is ideal. The users are not/should not have to be, power
users. I would like to give them wacomcpl and let them go nuts, safe in
the knowledge that they can't break anything too bad.

I understand that the current wacomcpl works for other people/OS's etc
but I would like to submit a patch that would at least make it more
flexible. I have made some fairly simple changes and happy to get some
feedback/corrections etc. essentially a config file can be passed as an
argument otherwise .xinitrc is used.

below is a diff not sure exactly how to make a patch... if someone could
let me know how, I'm happy to submit this as a patch.

Grant

diff -r linuxwacom-0.8.4-3/src/wacomxi/wacomcpl
linuxwacom-0.8.4-3.1/src/wacomxi/wacomcpl
20c20
< $WACOMXI_BINDIR/wacomcpl-exec
---
 > $WACOMXI_BINDIR/wacomcpl-exec $@
diff -r linuxwacom-0.8.4-3/src/wacomxi/wacomcpl-exec
linuxwacom-0.8.4-3.1/src/wacomxi/wacomcpl-exec
59a60,75
 > # Get wacom config file
 > set config_file "~/.xinitrc"
 > puts "Program: $argv0"
 > puts "Number of arguments: $argc"
 >
 > # May want to define other options for the moment keep it simple
 > foreach arg $argv {
 >    switch -exact -- $arg {
 >      -f { puts "-f is not needed"}
 >      default    {set config_file $arg }
 >    }
 > }
 >
 > puts "Config file $config_file"
 >
 >
102c118
<     if { ![ file exists ~/.xinitrc ] } {
---
 >     if { ![ file exists $config_file ] } {
111,113c127,129
<           exec echo "xsetwacom set $device $option \"$value\"" >
~/.xinitrc
<           exec echo "# run the primary system script" >> ~/.xinitrc
<           exec echo ". /etc/X11/xinit/xinitrc" >> ~/.xinitrc
---
 >           exec echo "# File created by wacomcpl" > $config_file
 >           exec echo "xsetwacom set $device $option \"$value\"" >>
$config_file
 >             exec chmod +x $config_file
116,121c132,137
<       file copy -force ~/.xinitrc ~/.xinitrc.bak
<       file copy -force ~/.xinitrc /tmp/xinitrc1
<       exec sed -e "/xsetwacom set $device $option /d" /tmp/xinitrc1 >
/tmp/wacom
<       exec echo "xsetwacom set $device $option \"$value\"" > ~/.xinitrc
<       exec cat /tmp/wacom >> ~/.xinitrc
<       file delete -force /tmp/wacom /tmp/xinitrc1
---
 >       file copy -force $config_file $config_file.bak
 >       file copy -force $config_file /tmp/config_file
 >       exec sed -e "/xsetwacom set $device $option /d"
/tmp/config_file > /tmp/wacom
 >       exec echo "xsetwacom set $device $option \"$value\"" > $config_file
 >       exec cat /tmp/wacom >> $config_file
 >       file delete -force /tmp/wacom /tmp/config_file
diff -r linuxwacom-0.8.4-3/src/wacomxi/wacomcpl.in
linuxwacom-0.8.4-3.1/src/wacomxi/wacomcpl.in
20c20
< $WACOMXI_BINDIR/wacomcpl-exec
---
 > $WACOMXI_BINDIR/wacomcpl-exec $@

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss