Hi Thomas. Could you please first make sure that you are running an X11 session? You can check your current session type by running echo $XDG_SESSION_TYPE inside a terminal. If it prints out "wayland", then you'll need to switch the session type. If you use the GNOME desktop, you should be able to do this by logging out, clicking the "gear" icon next to the login button, slecting "GNOME on Xorg", and then logging back in. Afterwards, run the echo command again to double-check that you've indeed started an X11 session.
Once you're running an X11 session, please run our sysinfo.sh script and attach the generated tarball to this bug. That will give us a bit more information about your particular system and its devices.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Thomas. The sysinfo script didn't detect a pen sensor either; it shows a touchscreen from ELAN rather than Wacom but no pen.
Are you sure your device supports the PN556W stylus? Searching for info on the XPS 15 9550 it sounds like it only has a traditional capacitive touchscreen. If that's the case, you'll only be able to make use of purely-capacitive pens. An "active pen" like the PN556W requires special support from the touchscreen controller to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for looking into this for me. My understanding of how the pens
work is weak, so I suspect you are correct and that my computer doesn't
support an active pen. Sorry for the noise.
Thanks Thomas. The sysinfo script didn't detect a pen sensor either; it
shows a touchscreen from ELAN rather than Wacom but no pen.
Are you sure your device supports the PN556W stylus? Searching for info on
the XPS 15 9550 it sounds like it only has a traditional capacitive
touchscreen. If that's the case, you'll only be able to make use of
purely-capacitive pens. An "active pen" like the PN556W requires special
support from the touchscreen controller to work.
I have a brand new Dell XPS 15. I have a brand new Dell PN556W Stylus. I would like my laptop to recognize the Stylus. Here is my uname:
If I look at Bluetooth, it shows the Pen there, but it says "not setup".
The ID of the wacom tablet which is the lapto screen is WACf004:
I downloaded the latest drivers (and rebooted) a few minutes ago:
~~~
modinfo wacom | grep version
version: v2.00-0.42.0
~~~
The command:
xsetwacom --list
doesn't return any devices.
Can anyone help?
thank you,
tpmeyer
Last edit: Thomas Meyer 2019-01-18
Hi Thomas. Could you please first make sure that you are running an X11 session? You can check your current session type by running
echo $XDG_SESSION_TYPE
inside a terminal. If it prints out "wayland", then you'll need to switch the session type. If you use the GNOME desktop, you should be able to do this by logging out, clicking the "gear" icon next to the login button, slecting "GNOME on Xorg", and then logging back in. Afterwards, run the echo command again to double-check that you've indeed started an X11 session.Once you're running an X11 session, please run our sysinfo.sh script and attach the generated tarball to this bug. That will give us a bit more information about your particular system and its devices.
Sorry it's taken so long to respond. The requested tarball is attached. Any help you could provide would be greatly appreciated.
Thanks Thomas. The sysinfo script didn't detect a pen sensor either; it shows a touchscreen from ELAN rather than Wacom but no pen.
Are you sure your device supports the PN556W stylus? Searching for info on the XPS 15 9550 it sounds like it only has a traditional capacitive touchscreen. If that's the case, you'll only be able to make use of purely-capacitive pens. An "active pen" like the PN556W requires special support from the touchscreen controller to work.
Hi Jason,
Thanks for looking into this for me. My understanding of how the pens
work is weak, so I suspect you are correct and that my computer doesn't
support an active pen. Sorry for the noise.
Tom
On Fri, Feb 8, 2019, 10:18 AM Jason Gerecke comp_nerd@users.sourceforge.net
wrote: