Cannot click icons when using pen on my Fujitsu t730 tablet

[zottelmann]

Hello!

I hope you guys/girls can help me here. As stated above i'm using a FS t730 Lifebook. Everything runs smoothly, but when i use my digitizer, after some time im not able to use the UI anymore. On Xournal i still can wirte one the paper, but any icon on the interface or the system do not work anymore. The solution is to relog, which is not very comfortable in my opinion. the problem exists on 13.04 and 13.10. i didnt tested it on 12.xx.
I use the lifebook for writing in my classes. So its important for me to get it working.
Any sugestions?
Thanks alot!

[Favux]

Hi zottelmann,

What you are describing does not make much sense. A log out and in is kind of a hotplug I guess.

I assume the t730 has a Wacom digitizer? Post the output of xinput list in a terminal to check.

The no left click would probably occur if a Wacom active pen/digitizer was on the evdev X driver instead of the Wacom X driver. But I do not see how that could happen if the 50-wacom.conf in xorg.conf.d matches to the digitizer to begin with. Your Xorg.0.log in /var/log would tell you what driver it is on and if it switched drivers. But the connection to the digitizer from the motherboard should be internal. If the connection was loose and it essentially performed a hotplug the wacom.conf should still match it to the Wacom X driver, i.e. take it away from the evdev X driver.

You don't state what Desktop you are using in 13.04 or 13.10. Maybe the problem is the Desktop? If Unity perhaps some bug is causing it to become unresponsive which is fixed with a log out and in.

[zottelmann]

Hi Favux!
Sorry for the delay
I'm using indeed Unity

this is my xinput:

Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ PS/2 Mouse                                  id=14    [slave  pointer  (2)]
⎜   ↳ AlpsPS/2 ALPS GlidePoint                    id=15    [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet stylus                  id=16    [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet eraser                  id=17    [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet touch                   id=18    [slave  pointer  (2)]

And here's the log(only looking for stylus):

[    23.687] (II) Serial Wacom Tablet: type not specified, assuming 'stylus'.
[    23.687] (II) Serial Wacom Tablet: other types will be automatically added.
[    24.198] (II) Serial Wacom Tablet stylus: serial tablet id 0xE3.
[    24.198] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
[    24.199] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=26312 maxY=16520 maxZ=255 resX=100000 resY=100000  tilt=disabled
[    24.199] (II) Serial Wacom Tablet stylus: hotplugging dependent devices.
[    24.199] (EE) Serial Wacom Tablet stylus: Invalid type 'cursor' for this device.
[    24.199] (EE) Serial Wacom Tablet stylus: Invalid type 'pad' for this device.
[    24.199] (II) Serial Wacom Tablet stylus: hotplugging completed.
[    24.199] (**) Option "config_info" "udev:/sys/devices/pnp0/00:0b/tty/ttyS4"
[    24.199] (II) XINPUT: Adding extended input device "Serial Wacom Tablet stylus" (type: STYLUS, id 16)
[    24.199] (**) Serial Wacom Tablet stylus: (accel) keeping acceleration scheme 1
[    24.199] (**) Serial Wacom Tablet stylus: (accel) acceleration profile 0
[    24.199] (**) Serial Wacom Tablet stylus: (accel) acceleration factor: 2.000
[    24.199] (**) Serial Wacom Tablet stylus: (accel) acceleration threshold: 4

Many thanks for your help!

Zottel

[Favux]

Alright, Unity and your xinput list shows the Wacom digitizer/stylus is on the Wacom X driver because we see stylus, eraser, and touch appended to the parent device name of "Serial Wacom Tablet".

The key line in Xorg.0.log is:

[    24.199] (II) XINPUT: Adding extended input device "Serial Wacom Tablet stylus" (type: STYLUS, id 16)

That tells us the digitizer has been successfully hot plugged onto a X driver. Above the part you showed would be a line(s) with snippet identifier labels in them. The Identifier is a line added to each .conf file "InputClass" snippet in xorg.conf.d to produce a human readable label for the snippet in the logs. The last line you see is the snippet in charge. In this case it should have said something like "Wacom serial class". Which tells you that snippet is trying to match the device to the Wacom X driver.

If further down in Xorg.0.log you suddenly see the device going through another hotplug but this time it is identified as an evdev snippet from the evdev.conf that would explain what you are seeing. But since it matches the Wacom snippet the first time why wouldn't it match it again? So I really doubt this is the problem.

It could be a problem with Unity I suppose. But the early problems with Compiz are pretty much gone at this point. Besides I gather your other pointing devices, a trackpad and/or mouse are still doing left clicks, so it isn't a general pointer issue.

I wonder if this is a hardware problem. The stylus may be going bad. I can't recall but I think tablet PC styli have replaceable nibs too. Have you tried extracting and replacing the nib (tip) of your stylus and checked if that made a difference? The nib has to be about 4 years old or some such If it has never been replaced. An extractor tool and replacement nibs should have been included.

[zottelmann]

Wow, you seem to have an awesome insight to Ubuntu

I'm sorry i forgot to tell, that only Keyboard is working when the bug happens. Left/right clicking doesn't on the other devices. But there another thing i discovered, when i looked closer to my stylus to see how the nib was surviving: i saw a little "HP" logo. So if this is not the original Stylus, can it cause so much trouble to Xinput? To explain: the Lifebook is a refurbished Model from Ebay from a private seller. Maybe it was mixed up or something.

Windows on the other hand works well, even with wrong stylus as i now know. But i dont want to use it

[Favux]

Well there is a difference between pens/styli and they will only work on "their" model Wacom digitizer. But tablet PC styli are most likely interchangeable because their digitizers are pretty much of the same type. The fact that it does work, at least initially, suggests the HP pen is compatible with the Thinkpad's digitizer.

only Keyboard is working when the bug happens. Left/right clicking doesn't on the other devices.

That suggests to me that you do have some sort of system bug. Most likely with Unity. Something is probably crashing. That may be in your Xorg.0.log too. Open it in gedit and use Find with keywords like error, crash, seg fault, and so on. It might be a video driver problem I suppose. What video chipset do you have?

lspci | grep VGA

[zottelmann]

Hi!

Thank you for hanging on
lspci tells this:

 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

On the paper the t730 has a intel i5 560m.

the only thing i found on the logfile was:

 5974.091] (II) Failed to load module "intel" (already loaded, 32698)
[  5974.091] (II) LoadModule: "vesa"
[  5974.091] (WW) Warning, couldn't open module vesa
[  5974.091] (II) UnloadModule: "vesa"
[  5974.091] (II) Unloading vesa
[  5974.091] (EE) Failed to load module "vesa" (module does not exist, 0)
[  5974.091] (II) LoadModule: "modesetting"
[  5974.091] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  5974.091] (II) Module modesetting: vendor="X.Org Foundation"
[  5974.091]     compiled for 1.14.1, module version = 0.8.0
[  5974.091]     Module class: X.Org Video Driver
[  5974.091]     ABI class: X.Org Video Driver, version 14.1
[  5974.091] (II) UnloadModule: "modesetting"
[  5974.091] (II) Unloading modesetting
[  5974.091] (II) Failed to load module "modesetting" (already loaded, 0)
[  5974.091] (II) LoadModule: "fbdev"
[  5974.091] (WW) Warning, couldn't open module fbdev
[  5974.091] (II) UnloadModule: "fbdev"
[  5974.091] (II) Unloading fbdev
[  5974.091] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  5974.091] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
    HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
    HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
    HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
    HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[  5974.092] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  5974.092] (++) using VT number 7

wich suggesting some problems with the graphics?

but later it seems to find something:

[  5974.092] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 (Timo Aaltonen <tjaalton@ubuntu.com>)
[  5974.092] (WW) Falling back to old probe method for modesetting
[  5974.092] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[  5974.092] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[  5974.093] (==) intel(0): RGB weight 888
[  5974.093] (==) intel(0): Default visual is TrueColor
[  5974.093] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics

what does this tell us? working as intended?

[Favux]

I'm not a video guru but it does look like there is a problem but it eventually gets sorted out. I was wondering if you had Nvidia because there has been a real increase in the rate of freezes/crashes with the OSS nouveau drivers. But if you aren't seeing any problems reported in the log when you lose left click I don't know. Another source of information would be dmesg (in a terminal). But I don't know what you would grep to find out what is happening. The output is pretty large. You'd have to write it to a text file and open that in gedit and then look at it and use Find and guess some key words to see if you can spot something. So after you lose left click run in a terminal:

dmesg > ~/Desktop/dmesg.txt

to create the file dmesg.txt on the Desktop. Presumably the problem should be reported somewhere near the end of the file, which is about a thousand lines long.

[zottelmann]

Hello!

Again my apologies for the delay. I was able to create the Dmsge.txt and there was one thin at the end wich seems to be related to my problems:

[ 6770.305704] psmouse serio4: bad data from KBC - bad parity
[ 6770.307619] psmouse serio4: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 6770.312224] psmouse serio4: GlidePoint at isa0060/serio4/input0 - driver resynced.
[ 6770.313560] psmouse serio4: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 6770.315366] psmouse serio4: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 6770.316905] psmouse serio4: GlidePoint at isa0060/serio4/input0 lost sync at byte 1
[ 6770.329534] psmouse serio4: GlidePoint at isa0060/serio4/input0 - driver resynced.

But im not sure what it exactly means.

regards

[Favux]

[ 6770.305704] psmouse serio4: bad data from KBC - bad parity

Likely means the data stream from the mouse is dropping out. The serio probably refers to a serio kernel module. That's the new way of handling serial devices. Instead of an X driver reading them directly off a serial port a serio kernel module reads them and feeds them to the X driver analogous to how a usb device works.

Hmm. I wonder if your PS/2 mouse, or its connection, is going bad. Check that the connections are good, especially with the adaptor if it requires one. Otherwise I'd substitute a usb mouse for it and see if that fixes the problem.