Great log file, thank you. Here's what happens:
...
12:43:42.951 Enter
12:43:42.952 TouchBegin (master, dev_id=2)
12:43:43.066 ButtonRelease (slave, dev_id=13)
12:43:43.067 TouchEnd (master, dev_id=2)
...

Two observations:
1) There are indeed touch events coming in, but only from the master pointer, 
none directly from the touch screen device 13. That's new, I haven't seen that 
happening before. Onboard sticks with mouse events (ButtonPress/ButtonRelease) 
in that case (meaning multi-touch won't be available).
2) The first ButtonPress event is missing, there's only a ButtonRelease. That's 
why there's no reaction to the first touch. When you use the mouse the initial 
ButtonPress event is there.

I've looked into 1) a bit. The screen seems to be USB connected and probably 
uses the hid-multitouch kernel driver and the evdev X driver. Support for the 
SYNA7500 seems relatively sensitive to the kernel version. This thread reports 
mixed results with various kernels and failures in particular with Vivid's 
kernel 3.19:
http://ubuntuforums.org/showthread.php?t=2187204&page=14&s=34cfa4caf159096f7cce745988b1ab59
If everything else fails, trying different kernels may make sense.

No idea what could cause 2) yet. I'm working on some way to reproduce
it. Is there anything I should know about your setup? Is this plain KWin
without any other bits of KDE?

Things you could try:
Set Preferences->Keyboard->Advanced->"Touch input" to "none". If there's no 
change (likely) set Preferences->Keyboard->Advanced->"Input event source" to 
"GTK".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1470825

Title:
  Onboard focus with KWin

Status in onboard package in Ubuntu:
  New

Bug description:
  Customized Ubuntu 15.04, running KWin via an .xsession call. Using
  Onboard for on-screen keyboard. The keyboard won't get focus unless I
  tap on it twice (or unless I drag into the keyboard, and then tap it).
  In my previous environment I used Compiz and didn't have this
  behaviour, nor do I see it with any other window type.

  Turning debugging on for Onboard it seems to be getting the touch
  events so I am not sure why its not getting focus. Its output for
  example would be:

  Code: Select all
  19:23:08.392 EVENT   TouchInput            Source device: XIDevice(id=13 
attachment=2 use=3 touch_mode=1 source=GDK_SOURCE_TOUCHSCREEN name=SYNA7500:00 
06CB:3AF0 vendor=0x06cb product=0x3af0 enabled=1)
  19:23:08.392 EVENT   TouchInput            _on_device_event1
  19:23:08.393 EVENT   TouchInput            _on_device_event2 2 2
  19:23:08.393 EVENT   TouchInput            _on_device_event7 1
  19:23:08.393 EVENT   TouchInput            _on_device_event8 True
  19:23:08.393 EVENT   TouchInput            _on_device_event10 20971528 
20971707
  19:23:08.393 EVENT   TouchInput            _on_device_event11
  19:23:08.394 EVENT   TouchInput            Device event: dev_id=2 src_id=2 
xi_type=7 xid_event=20971528(20971707) x=171.0 y=45.0 x_root=1642.0 
y_root=405.0 button=0 state=0 sequence=0

  
  A little lost and looking for any suggestions!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1470825/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to