> Thanks for the quick feedback, I think I need to look at the touch driver as
> well.
You're welcome. I think you won't need to do this anymore.
Screens/kernel/drivers are probably fine.
I could eventually reproduce both issues in KWin and 1) was an Onboard
thing. Wrong order of initialization, that apparently had no ill effect
in compiz, where I did most of the touch testing. Trunk has a fix and I
don't get the fall-back mouse-events mode anymore in KWin, meaning you'd
likely have multi-touch available too. It works with either XInput or
GTK event source here, but I'd suggest you return to "XInput", because a
few of Onboard's features require/work better with this.
Still working on 2), though I expect you won't hit this anymore with
default settings. Others might, wacom touch-screen people in particular
(on KWin).
> AttributeError: 'X11DeviceXI2' object has no attribute 'touch_active'
Thank you, should be fixed too now.
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Confirmed
** Changed in: onboard (Ubuntu)
Status: New => Confirmed
** Changed in: onboard
Importance: Undecided => High
--
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 on-screen keyboard:
Confirmed
Status in onboard package in Ubuntu:
Confirmed
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/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
