← Back to team overview

ubuntu-sdk-bugs team mailing list archive

[Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

 

I tested this in bug #1536669 on krillin and Unity 8 desktop on
Chromebook, and it worked fine with the example apps, the QML of which
called:

    InputDeviceModel {
        id: deviceModel
        filter: InputInfo.Keyboard | InputInfo.Mouse | InputInfo.TouchScreen
        onCountChanged: {
         console.log("new count of filtered devices: " + devices)
        }
    }

It doesn't say it there but I believe I did test with my Bluetooth mouse
too. But maybe indeed there's some case either arale specific or related
to the mouse+keyboard combo.

** Changed in: qtsystems-opensource-src (Ubuntu)
       Status: New => Confirmed

** Changed in: qtsystems-opensource-src (Ubuntu)
     Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtsystems-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions


References