[Touch-packages] [Bug 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Andreas Pokorny]

no change needed in mir

** Changed in: mir
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1557634

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix
Status in qtmir package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557634/+subscriptions

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

[Touch-packages] [Bug 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Andreas Pokorny]

I have added qtmir - because I think qtmir could make wiser decisions on
how to handle the error than the mir surface or key mapper.

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1557634

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  New

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557634/+subscriptions

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Andreas Pokorny]

** Changed in: qtmir (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  Triaged
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Andreas Pokorny]

** Changed in: mir/0.26
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  Triaged
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Andreas Pokorny]

** Changed in: mir
   Status: New => In Progress

** Changed in: mir
Milestone: None => 1.0.0

** Also affects: mir/0.26
   Importance: Undecided
   Status: New

** Changed in: mir/0.26
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir/0.26
   Status: New => In Progress

** Changed in: mir/0.26
Milestone: None => 0.26.3

** Changed in: mir/0.26
   Importance: Undecided => High

** Description changed:

  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt
  
  Expected:
  * session is locked, but working
  
  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all
  
  It seems it's "catching up" in some way, maybe with input, maybe frames.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)
  
  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
-   Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.
+   Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.
+ 
+ This applies to all currently pressed buttons. I.e. you can open an edit
+ field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch
+ to another VT. On return 'w' will be repeated indefinitely.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  Triaged
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hu

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Andreas Pokorny]

** Changed in: mir/0.26
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1672955

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions

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

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Andreas Pokorny]

** Changed in: mir/0.26
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1672955

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Andreas Pokorny]

** Description changed:

  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt
  
  Expected:
  * session is locked, but working
  
  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all
- 
  
  It seems it's "catching up" in some way, maybe with input, maybe frames.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)
+ 
+ Causes:
+ The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
+   Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  Triaged
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions

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

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibI

[Andreas Pokorny]

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
- If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.
+ If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 
+ 
+ It seems that the configuration change is requested just a moment before
+ the device gets removed. The change actions are serialized, depending on
+ where there memory of mir::input::DefaultDevice is allocated the
+ segfault either occurs inside the lambda or inside underlying
+ mir::input::LibInputDevice in the platform. The activities on input
+ dispatch device removal and reconfiguration are serialized inside the
+ input thread, so we just need to clean the action queue (or have
+ multiple queues) before removing the devices.

** Changed in: mir
   Status: New => Triaged

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1672955

Title:
  unity-system-compositor crashed with SIGSEV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions

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

[Touch-packages] [Bug 1672956] Re: unity-system-compositor crashed with SIGSEGV in operator() () at ./src/server/input/default_device.cpp:108

[Andreas Pokorny]

*** This bug is a duplicate of bug 1672955 ***
https://bugs.launchpad.net/bugs/1672955

The stack is the same as the other one, the timing is just slightly
different. So the crash just happens a bit later than that.

** This bug has been marked a duplicate of bug 1672955
   unity-system-compositor crashed with SIGSEV in 
libinput_device_config_accel_is_available() from 
libinput_device_config_accel_set_speed() from 
mir::input::evdev::LibInputDevice::apply_settings()

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1672956

Title:
  unity-system-compositor crashed with SIGSEGV in operator() () at
  ./src/server/input/default_device.cpp:108

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.0+17.04.20170127-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/534f8add6680a8cf76ac04d37b0f78561d1d3a6e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672956/+subscriptions

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

[Touch-packages] [Bug 1639745] Re: Mir GL clients never appear at all on VirtualBox

[Andreas Pokorny]

The root cause for this problem was fixed upstream and applied in the
ubuntu packages in virtualbox and the kernel (lp:1669807)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1639745

Title:
  Mir GL clients never appear at all on VirtualBox

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mir GL clients never appear at all on VirtualBox.

  After digging for a while, it appears the issue is that vboxvideo does
  not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly
  Mir is the opposite now: Mir only supports PRIME but not flink names.

  Internally some exceptions are being thrown in Mir at present, but we
  seem to catch and silence them all. So you never see any error
  messages at all. Just Mir GL clients never appear on screen in
  VirtualBox.

  For the record, Wayland supports falling back to flink names in the
  absence of PRIME. We should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1639745/+subscriptions

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

[Andreas Pokorny]

** Changed in: qtmir
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536279

Title:
  Mir does not reset key states when paused or resumed (modifiers get
  stuck after VT switching)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir switches away from the current VT when ALT+FXX is pressed. During
  that key sequence the alt modifier is pressed. While away and mir does
  not receive the alt release. When you switch back to mir there is a
  chance that mir is not receiving the alt release either.

  So switching away and back to mir makes the alt key stick...

  Proposed solution:
  - track regular keys in mir::input::Seat or in SurfaceDispatcher
  - inform client(s) about pause / resume with a focus lost / focus gain event
  - attach key state to focus event or send separate key state event
  - adapt gdk/qt backends
  - fix alt key tracking in unity8 to rely on the provided modifier state

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536279/+subscriptions

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

[Andreas Pokorny]

** Changed in: qtmir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: qtmir
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536279

Title:
  Mir does not reset key states when paused or resumed (modifiers get
  stuck after VT switching)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir switches away from the current VT when ALT+FXX is pressed. During
  that key sequence the alt modifier is pressed. While away and mir does
  not receive the alt release. When you switch back to mir there is a
  chance that mir is not receiving the alt release either.

  So switching away and back to mir makes the alt key stick...

  Proposed solution:
  - track regular keys in mir::input::Seat or in SurfaceDispatcher
  - inform client(s) about pause / resume with a focus lost / focus gain event
  - attach key state to focus event or send separate key state event
  - adapt gdk/qt backends
  - fix alt key tracking in unity8 to rely on the provided modifier state

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536279/+subscriptions

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

[Touch-packages] [Bug 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent

[Andreas Pokorny]

Went for the second approach key entry text is attached to every press
and repeat event.

** Branch linked: lp:~andreas-pokorny/mir/fix-1664610

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir (Ubuntu)
 Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned)

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Package changed: mir (Ubuntu) => mir

** Changed in: mir
Milestone: None => 1.0.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1664610

Title:
  qtubuntu sends wrong text as part of QKeyEvent

Status in Mir:
  Confirmed
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  When using Unity7 or Plasma a key event created by Ctrl+C is
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003")

  But Unity8+ qtubuntu send to the application
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="c")

  This is most likely because QMirClientInput::dispatchKeyEvent is using
  xkb_keysym_to_utf8 to get the text of the event instead of using
  xkb_state_key_get_utf8

  This breaks for example Konsole that expects the correct text to be
  sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1664610/+subscriptions

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

[Touch-packages] [Bug 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent

[Andreas Pokorny]

Mir either has to expose the xkb_state (which we currently do not - and
might be only on the server) or provide the keysym text directly with
the event.

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

** Tags added: input

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1664610

Title:
  qtubuntu sends wrong text as part of QKeyEvent

Status in mir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  When using Unity7 or Plasma a key event created by Ctrl+C is
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003")

  But Unity8+ qtubuntu send to the application
    QKeyEvent(KeyPress, Key_C, ControlModifier, text="c")

  This is most likely because QMirClientInput::dispatchKeyEvent is using
  xkb_keysym_to_utf8 to get the text of the event instead of using
  xkb_state_key_get_utf8

  This breaks for example Konsole that expects the correct text to be
  sent.

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

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

[Touch-packages] [Bug 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

[Andreas Pokorny]

Same problem or a different type of testfail?

19:54:42 [ RUN  ] ClientLatency.dropping_latency_is_closer_to_zero_than_one
19:54:42 [2017-01-31 19:54:42.347490] mirserver: Starting
19:54:42 [2017-01-31 19:54:42.347814] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
19:54:42 [2017-01-31 19:54:42.365959] mirserver: Using software cursor
19:54:42 [2017-01-31 19:54:42.378848] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
19:54:42 [2017-01-31 19:54:42.379166] mirserver: Mir version 0.26.0
19:54:42 [2017-01-31 19:54:42.387115] mirserver: Initial display configuration:
19:54:42 [2017-01-31 19:54:42.387331] mirserver:   Output 1: HDMI-A connected, 
used
19:54:42 [2017-01-31 19:54:42.387422] mirserver:   Physical size 0.0" 0x0mm
19:54:42 [2017-01-31 19:54:42.387506] mirserver:   Power is on
19:54:42 [2017-01-31 19:54:42.387580] mirserver:   Current mode 1920x1080 
60.00Hz
19:54:42 [2017-01-31 19:54:42.387647] mirserver:   Preferred mode 1920x1080 
60.00Hz
19:54:42 [2017-01-31 19:54:42.387710] mirserver:   Orientation normal
19:54:42 [2017-01-31 19:54:42.387786] mirserver:   Logical size 1920x1080
19:54:42 [2017-01-31 19:54:42.387887] mirserver:   Logical position +0+0
19:54:44 
/BUILDDIR/mir-0.26.0+xenial3900bzr3541/tests/acceptance-tests/test_latency.cpp:376:
 Failure
19:54:44 Value of: average_latency
19:54:44 Expected: is  0.5
19:54:44   Actual: 0.50877 (of type float)
19:54:44 [  debug   ] 97 frames sampled, averaging 0.509 frames latency
19:54:44 [  debug   ]  0:  1.00  1.00  0.50  0.50  0.06  0.07  0.07  0.07  0.08 
 0.08
19:54:44 [  debug   ] 10:  0.08  0.08  0.25  0.25  0.12  0.10  0.17  0.08  0.04 
 0.25
19:54:44 [  debug   ] 20:  0.20  0.50  0.09  0.33  1.00  0.50  1.00  1.00  1.00 
 1.00
19:54:44 [  debug   ] 30:  1.00  1.00  1.00  1.00  1.00  0.50  0.12  0.11  3.00 
 0.04
19:54:44 [  debug   ] 40:  0.10  0.14  2.00  1.00  0.17  0.50  0.50  0.33  0.33 
 0.25
19:54:44 [  debug   ] 50:  0.08  0.07  0.07  0.08  0.07  0.08  0.33  0.33  1.00 
 0.20
19:54:44 [  debug   ] 60:  1.00  0.11  0.17  0.33  1.00  0.11  0.06  0.33  0.50 
 0.11
19:54:44 [  debug   ] 70:  0.11  0.04  0.04  0.07  0.04  0.07  0.06  0.04  0.33 
 2.00
19:54:44 [  debug   ] 80:  2.00  0.50  0.50  1.00  1.00  2.00  1.00  1.00  2.00 
 1.00
19:54:44 [  debug   ] 90:  0.14  1.00  0.14  0.50  0.14  0.04  1.00
19:54:44 [2017-01-31 19:54:44.472992] mirserver: Stopping
19:54:44 [  FAILED  ] ClientLatency.dropping_latency_is_closer_to_zero_than_one 
(2234 ms)

in the same run:
19:54:48 [ RUN  ] 
ClientLatency.async_swap_dropping_latency_is_closer_to_zero_than_one
19:54:48 [2017-01-31 19:54:48.485202] mirserver: Starting
19:54:48 [2017-01-31 19:54:48.485592] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
19:54:48 [2017-01-31 19:54:48.507703] mirserver: Using software cursor
19:54:48 [2017-01-31 19:54:48.524831] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
19:54:48 [2017-01-31 19:54:48.525074] mirserver: Mir version 0.26.0
19:54:48 [2017-01-31 19:54:48.535165] mirserver: Initial display configuration:
19:54:48 [2017-01-31 19:54:48.535282] mirserver:   Output 1: HDMI-A connected, 
used
19:54:48 [2017-01-31 19:54:48.535320] mirserver:   Physical size 0.0" 0x0mm
19:54:48 [2017-01-31 19:54:48.535344] mirserver:   Power is on
19:54:48 [2017-01-31 19:54:48.535369] mirserver:   Current mode 1920x1080 
60.00Hz
19:54:48 [2017-01-31 19:54:48.535393] mirserver:   Preferred mode 1920x1080 
60.00Hz
19:54:48 [2017-01-31 19:54:48.535411] mirserver:   Orientation normal
19:54:48 [2017-01-31 19:54:48.535431] mirserver:   Logical size 1920x1080
19:54:48 [2017-01-31 19:54:48.535449] mirserver:   Logical position +0+0
19:54:50 
/BUILDDIR/mir-0.26.0+xenial3900bzr3541/tests/acceptance-tests/test_latency.cpp:451:
 Failure
19:54:50 Value of: average_latency
19:54:50 Expected: is  0.5
19:54:50   Actual: 0.664058 (of type float)
19:54:50 [  debug   ] 98 frames sampled, averaging 0.664 frames latency
19:54:50 [  debug   ]  0:  0.11  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08 
 0.08
19:54:50 [  debug   ] 10:  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08 
 0.08
19:54:50 [  debug   ] 20:  0.08  0.09  0.06  0.08  0.09  0.14  0.50  0.33  0.05 
 0.03
19:54:50 [  debug   ] 30:  1.00  1.00  2.00  1.00  0.33  0.11  0.10  0.14  0.50 
 1.00
19:54:50 [  debug   ] 40:  1.00  1.00  0.50  1.00  2.00  1.00  1.00  1.00  2.00 
 0.14
19:54:50 [  debug   ] 50:  0.11  2.00  1.00  1.00  1.00  1.00  1.00  1.00  1.00 
 2.00
19:54:50 [  debug   ] 60:  1.00  1.00  0.17  0.10  0.50  1.00  2.00  0.33  2.00 
 2.00
19:54:50 [  debug   ] 70:  1.00  0.09  0.17  0.50  1.00  1.00  2.00  1.00  0.33 
 0.06
19:54:50 [  debug   ] 80:  0.50  1.00  2.00  2.00  1.00  0.33  2.00  0.25  0.07 
 0.10
19:54:50 [  debug   ] 90:  1.00  2.00  1.00  0.09  0.17  1.00  1.00  0.33
19:54:50 [2017-01-31 19:54:50.852240] mirserver: Stopping
19:54:50 [  FAILED  ] 

[Touch-packages] [Bug 1626435] Re: Keyboard layout not applied on the shell

[Andreas Pokorny]

** Changed in: mir
Milestone: 0.25.0 => 0.24.1

** Also affects: mir/0.25
   Importance: High
 Assignee: Andreas Pokorny (andreas-pokorny)
   Status: Fix Committed

** Changed in: mir/0.25
Milestone: 0.24.1 => 0.25.0

** Also affects: mir/0.24
   Importance: Undecided
   Status: New

** Changed in: mir/0.24
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir/0.24
Milestone: None => 0.24.1

** Changed in: mir/0.24
   Importance: Undecided => High

** Changed in: mir/0.24
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1626435

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  In Progress
Status in Mir 0.25 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Split out from bug #1611859:

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626435/+subscriptions

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

[Touch-packages] [Bug 1626435] Re: Keyboard layout not applied on the shell

[Andreas Pokorny]

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1626435

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  Triaged
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Split out from bug #1611859:

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626435/+subscriptions

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

[Touch-packages] [Bug 1624437] [NEW] Wish: Provide a gtk/gdk friendly interface to content-hub

[Andreas Pokorny]

Public bug reported:

There is probably no technical limitation that blocks anyone from using
the current API of content-hub to implement drag & drop features in gdk,
but there might be other subtle issues with bringing in qt as a
dependency to gtk+.

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1624437

Title:
  Wish: Provide a gtk/gdk friendly interface to content-hub

Status in content-hub package in Ubuntu:
  New

Bug description:
  There is probably no technical limitation that blocks anyone from
  using the current API of content-hub to implement drag & drop features
  in gdk, but there might be other subtle issues with bringing in qt as
  a dependency to gtk+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1624437/+subscriptions

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

[Andreas Pokorny]

** Bug watch added: GNOME Bug Tracker #768138
   https://bugzilla.gnome.org/show_bug.cgi?id=768138

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=768138
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1591356

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+subscriptions

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Andreas Pokorny]

** Changed in: maliit-framework (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1607237

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Invalid
Status in maliit-framework package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Accented dead characters (áéíóú) not working on external keyboards

  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (OTA-12)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607237/+subscriptions

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

[Touch-packages] [Bug 1607680] Re: Smooth touchpad scrolling doesn't work in GTK-on-Mir

[Andreas Pokorny]

** Bug watch added: GNOME Bug Tracker #769554
   https://bugzilla.gnome.org/show_bug.cgi?id=769554

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=769554
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1607680

Title:
  Smooth touchpad scrolling doesn't work in GTK-on-Mir

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Smooth touchpad scrolling doesn't work in GTK-on-Mir

  Touchpad scrolling is instead jumpy and unresponsive.

  gdk/mir/gdkmireventsource.c ignores smaller scroll motion values even
  though the underlying gdk interface would support small floating point
  scroll motions

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1607680/+subscriptions

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Andreas Pokorny]

The simplest solution seems to be to load the compose input context from
the maliitphablet input context..

** Changed in: mir
   Status: Confirmed => Invalid

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: mir (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: maliit-framework (Ubuntu)
   Status: New => In Progress

** Changed in: maliit-framework (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir
 Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1607237

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in maliit-framework package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Accented dead characters (áéíóú) not working on external keyboards

  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (OTA-12)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607237/+subscriptions

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Andreas Pokorny]

Ok it works on desktop because desktop qt loads the
qcomposeplatforminputcontext plugin. On Ubuntu Touch qt loads
qmaliitphabletplatforminputcontext plugin. So no code is available to
handle dead keys.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1607237

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Accented dead characters (áéíóú) not working on external keyboards

  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (OTA-12)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607237/+subscriptions

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Andreas Pokorny]

I do not think this is affected by mir. When a keymap with dead keys is
selected clients like unity8-dash receive the respective dead key codes
the qts compose key filter would interpret.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1607237

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (OTA-12)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607237/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

There were two related sources that led to the problem. The quick fix in
unity8 was already released. The mir series of changes that ended up
being part of 0.24 would have avoided the problem too but only as a side
effect.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1565236

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions

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

[Touch-packages] [Bug 1607680] Re: Smooth touchpad scrolling doesn't work in GTK-on-Mir

[Andreas Pokorny]

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => In Progress

** Description changed:

  Smooth touchpad scrolling doesn't work in GTK-on-Mir
  
  Touchpad scrolling is instead jumpy and unresponsive.
+ 
+ gdk/mir/gdkmireventsource.c ignores smaller scroll motion values even
+ though the underlying gdk interface would support small floating point
+ scroll motions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1607680

Title:
  Smooth touchpad scrolling doesn't work in GTK-on-Mir

Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Smooth touchpad scrolling doesn't work in GTK-on-Mir

  Touchpad scrolling is instead jumpy and unresponsive.

  gdk/mir/gdkmireventsource.c ignores smaller scroll motion values even
  though the underlying gdk interface would support small floating point
  scroll motions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

** Branch linked: lp:~andreas-pokorny/mir/serverside-keymap-based-
modifier-tracking

** Changed in: mir
   Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1565236

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions

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

[Touch-packages] [Bug 1227739] Re: Mir continues to render background application surfaces even when they're not visible

[Andreas Pokorny]

no longer valid for platform api

** Changed in: platform-api
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1227739

Title:
  Mir continues to render background application surfaces even when
  they're not visible

Status in Mir:
  Fix Released
Status in platform-api:
  Invalid
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in unity-mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-mir package in Ubuntu:
  Fix Released

Bug description:
  Not sure where to file this.

  
  on the phone, if you open the clock app (which cases redraws every second 
when the second hand moves), and then open an indicator over the top, unity8 
still renders frames every second, despite the fact that nothing on the screen 
is changing.

  Talking to greyback and saviq, it sounds like some changes are
  required in both unity8 and mir before we can fix this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1227739/+subscriptions

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

[Touch-packages] [Bug 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

[Andreas Pokorny]

** Changed in: gtk
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1445543

Title:
  Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

Status in GTK+:
  New
Status in Mir:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK apps on Mir: Input focus is unreliable and sporadic. Background
  windows ignore input and/or focus switches apparently randomly.

  Example:

  $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

  Show the "Scores" - you can switch focus between this and the main
  window with Alt+` but doesn't respond to input.

  Other dialogs (e.g. "About") work fine. From the Mir side there's no
  obvious difference between these windows.

  In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
  events being correctly received on the client side. That shows most of
  the Mir stack is working correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1445543/+subscriptions

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

[Touch-packages] [Bug 1588237] Re: inconsistent behaviour of the numblock

[Andreas Pokorny]

** Branch linked: lp:~andreas-pokorny/mir/fix-1588237

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1588237

Title:
  inconsistent behaviour of the numblock

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
  M10 with external Keyboard and Screen, after restart on OTA11.
  To use numbers in the unlock screen, the num key has to be active.
  After unlocking, use a search field in the homescope or any other scope.

  Expected behaviour:
  The numblock should work, as the num key is still active.

  Actual behaviour:
  The numblock only works, when you deactivate the num key.

  This is the same for the browserbar or the telegram chat.
  After some time, the behaviour changes, so the numblock behaviour seems to be 
inconsistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588237/+subscriptions

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

[Touch-packages] [Bug 1588237] Re: inconsistent behaviour of the numblock

[Andreas Pokorny]

** Changed in: mir (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1588237

Title:
  inconsistent behaviour of the numblock

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
  M10 with external Keyboard and Screen, after restart on OTA11.
  To use numbers in the unlock screen, the num key has to be active.
  After unlocking, use a search field in the homescope or any other scope.

  Expected behaviour:
  The numblock should work, as the num key is still active.

  Actual behaviour:
  The numblock only works, when you deactivate the num key.

  This is the same for the browserbar or the telegram chat.
  After some time, the behaviour changes, so the numblock behaviour seems to be 
inconsistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588237/+subscriptions

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

[Touch-packages] [Bug 1588237] Re: inconsistent behaviour of the numblock

[Andreas Pokorny]

The described behavior matches the way keyboard mapping is handled
within mir right now. Unity8 configures keymaps for each client surface.
Each client surface then has its own independent key state. Key state
here means the set of active modifier keys, including toggles like Caps
Lock, Num Lock. So it depends on which client sees

Mir 0.24 will change this behavior. It will default to have a per
keyboard device key state tracked and updated inside a mir server like
Unity8. Thus Num Lock will stay active after you switch between
surfaces. BUT: For that to work Unity8 need to configure its own server
side per device keymaps (they only default to us). Additionally we still
allow client side per surface keymaps. As of now the solution inside of
lp:mir and the presumptive 0.24 would not be capable of transfering the
current toggle state of Caps Lock or Num Lock when switching to an
application with a client side keymap. We already identified that
problem, and I plan to address that soon. But it might not make it into
0.24

As a short term fix I suggest to switch unity8 to only use server side
keymaps with 0.24, until this last problem is also addressed.

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1588237

Title:
  inconsistent behaviour of the numblock

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:
  M10 with external Keyboard and Screen, after restart on OTA11.
  To use numbers in the unlock screen, the num key has to be active.
  After unlocking, use a search field in the homescope or any other scope.

  Expected behaviour:
  The numblock should work, as the num key is still active.

  Actual behaviour:
  The numblock only works, when you deactivate the num key.

  This is the same for the browserbar or the telegram chat.
  After some time, the behaviour changes, so the numblock behaviour seems to be 
inconsistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588237/+subscriptions

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in libertine apps does not work

[Andreas Pokorny]

https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/tree/hw/xmir
/xmir-input.c?h=xmir-1.18#n386 needs fixing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1591356

Title:
  keyboard autorepeat in libertine apps does not work

Status in X.Org X server:
  New
Status in libertine package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1591356/+subscriptions

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in libertine apps does not work

[Andreas Pokorny]

xmir treats repeat events like key up ... which probably also explains
why keys frequently get stuck in xmir..

** Also affects: xorg-server
   Importance: Undecided
   Status: New

** Tags added: xmir

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1591356

Title:
  keyboard autorepeat in libertine apps does not work

Status in X.Org X server:
  New
Status in libertine package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1591356/+subscriptions

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

[Andreas Pokorny]

** Changed in: mir
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1580774

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580774/+subscriptions

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

[Andreas Pokorny]

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir
   Status: Confirmed => In Progress

** Changed in: mir
Milestone: None => 0.22.1

** Changed in: mir
Milestone: 0.22.1 => 0.23.0

** Changed in: mir
Milestone: 0.23.0 => 0.22.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1580774

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580774/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

Ok there is actually another problem here, the modifier information
provided to unity8 from usc indicates that alt is pressed even though
the currently consuming client interprets the scan code of right alt as
level 3 shift... So still a mir change is required.

** Changed in: mir
   Status: Invalid => In Progress

** Changed in: mir (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1565236

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

Those input scenarios work when unity8 is not used as mirserver.

The right alt scan code does not reach the client. Unity8 seems to
filter out the key press. In some occasions it seems to be sent at a
later timer. Long holding of right alt and then pressing sometimes help.

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir
   Status: Confirmed => Invalid

** Changed in: mir (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1565236

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

[Andreas Pokorny]

This bug cannot be fixed in mir or qtubuntu - applications like unity8
and the applications using qtdeclarative will be slow within x11 and
mir. A backend for fixed function gpus, i.e using only GL1.5 would be
required to fix that..

** Also affects: qtdeclarative (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtdeclarative package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

** Tags added: input

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1565236

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Andreas Pokorny]

** Branch linked: lp:~andreas-pokorny/mir/fix-1549701

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1549701

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

ok this time on top of version 23.

** Patch added: "new mir backend for inputinfo"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1536669/+attachment/4607554/+files/0001-Add-mir-backend-for-input-info.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1539009] Re: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

[Andreas Pokorny]

** Changed in: mir/0.20
Milestone: 0.20.3 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1539009

Title:
  Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Triaged
Status in QtMir:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Logging in to Unity8 on desktop (xenial) the mouse cursor moves
  glacially slow. I have to move the mouse across the whole desk to get
  anywhere. This is surprising given bug 1524145 shows the opposite is
  happening in the Mir demo servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:32:27 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539009/+subscriptions

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

[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random

[Andreas Pokorny]

** Changed in: mir/0.20
Milestone: 0.20.3 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536662

Title:
  [regression] Black screen: Mir hangs and then crashes on startup/login
  due to reading from /dev/random

Status in Mir:
  In Progress
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Triaged
Status in Unity System Compositor:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  cookie_factory attempts to read data from /dev/random at boot, and
  blocks until it has enough random data or timesout after 30 seconds.

  How I can reproduce
  1. Run the Unity8 greeter as a mir server
  2. Reboot

  Expected behavior: Greeter is displayed as mir && USC run happily
  Actual behavior: Mir throws an exception after 30 seconds

  Work-around:
  Before logging in, move the mouse around lots, for at least 20 seconds. And 
after logging in, while you're looking at a black screen, move the mouse around 
furiously. This will populate the kernel entropy pool sufficiently to avoid the 
hang and crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1536662/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

Oh seems like I pulled in the wrong version.. will redo the patch..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

QInputInfo API exposes the device path - an information mir does not
offer yet (and might not be able to on grouped devices) and exposes
evdev properties for axes that clients will never see - like touchpad
ABS_MT_*... I hope that nobody relies on that information..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

qtsystems also needs to be updated to use the mir-0.21 API. I added a
change of the current QInputInfo class of but the qmake stuff I had to
change seem to be fishy. Also the

** Patch added: "0001-Input-Device-Info-base-on-Mir-API.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1536669/+attachment/4604506/+files/0001-Input-Device-Info-base-on-Mir-API.patch

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

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

** Also affects: qtsystems-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

our ci is still out of step due to the problems on outage today. The API
is already in lp:mir available you can get an example here:

http://bazaar.launchpad.net/~mir-team/mir/development-
branch/view/head:/src/utils/in.cpp

The last branch linked to this bug# handles the forwarding in a nested
session. Without it the example code above will not get any input
devices when connected to a session compositor. We plan to get that MP
out in the next mir release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Andreas Pokorny]

** Changed in: mir (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~andreas-pokorny/mir/05-csdi-nested-input-device-
hub-and-device

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

i915 does not have native shader support so mesa simulate that with
llvmpipe, using i915 only for blitting.. So a less demanding - (but also
not existing) fixed-function gl-1.x backend is the probably your best
chance to use that gpu with unity8.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

Mesa in Ubuntu has a patch for i915 that disables OpenGL 2.0 but not
GLES 2,0. Thats why all mir clients and the unity8 session starts up..
since mirserver always use GL|ES.

Regular qt clients do the EGL init in a different path and they insist
on GL 2.0.

When you recompile mesa without that patch you get the unity8 desktop
but it is just too slow.. It would be better to implement a less
demanding QtQuick backend .. and/or use a different mir compositor..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

** Changed in: mir
   Status: New => Invalid

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

Yes I believe there is still a problem setting up the rendering context. When I 
run unity8-dash in isolation I get this:
file:///usr/share/unity8//Dash/Dash.qml:39: ReferenceError: window is not 
defined
file:///usr/share/unity8//Dash/Dash.qml:265: ReferenceError: scopeStyle is not 
defined
ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file 
../../../src/ubuntumirclient/glcontext.cpp, line 71

A failure there will affect all qt applications..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

I have an intel atom catching some dust here. As long as pineview does
not contain the GMA 500 poulsbo gpu.. it should be a similar chip.

And what happens is, that unity8-dash keeps restarting. Last time I
tracked that down this was due to lack of GL 2.0 support in mesa for
that cpu.  Just upgrading now, to check if this is still the case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Andreas Pokorny]

** Description changed:

  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  
  it happens also on arale.
  
  sometimes the screen lock timeout is not honoured and the devices don't
  suspend when the lock timeout expires (display doesn' t turn off)
  
  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1
  
  Steps to reproduce on arale:
  
  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button
  
  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail
+ 
+ The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
+ The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.
+ 
+ We could fix this by:
+ - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
+ - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
+ - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1549701

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Andreas Pokorny]

We need a different solution here since we never stop reading from the
the touchscreen when the screen is off. Instead the hardware is turned
off so it never sends a release..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1549701

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Andreas Pokorny]

** Changed in: mir
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  In Progress
Status in Mir 0.20 series:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Andreas Pokorny]

The only difference to the mentioned lp:#1550050 is that the device is
not "removed" during suspend, which I suspect was fixed in lp:mir and
will be included in 0.21.0 - this together with the fix for #1550050
should solve that problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1549701

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Andreas Pokorny]

On mako the bluetooth driver seems to release all pressed keys on
removal.. Still I can experience the problem on krillin with USB
disconnect - no release event is provided before the device is removed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Andreas Pokorny]

** Changed in: mir
   Status: New => In Progress

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Andreas Pokorny]

I will start with a small fix to get the repeat to stop on disconnect..
Then there still is a problem with modifier states that might be stuck untill 
the device is reattached and the key is pressed again..

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions

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

[Touch-packages] [Bug 1547864] Re: libinput doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED), to support Android home buttons

[Andreas Pokorny]

We might not need to emit 'cancel' for keys being pressed while
switching away - it might be enough to treat vt switching as focus
gaining state change.. during which we have to inform the client about
all currently pressed keys and buttons..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1547864

Title:
  libinput doesn't handle EV_KEY event with a value of 255
  (BUTTON_CANCLED), to support Android home buttons

Status in Mir:
  Triaged
Status in libinput package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I port Ubuntu Touch to LG L90 Dual. When I press a button below the
  screen (it's the touch button and is part of the touch screen), then
  slide the finger up, a letter will repeatedly appear in any text field
  selected (for instance, if the button is a menu button, letter 'e'
  will appear repeatedly). Using evtest with the touch screen device, I
  can see what happened:

  Event: time 75.605520, type 1 (EV_KEY), code 139 (KEY_MENU), value 1
  Event: time 75.605525, -- EV_SYN 
  Event: time 75.707065, type 1 (EV_KEY), code 139 (KEY_MENU), value 255

  (See the full log here: http://paste.ubuntu.com/15112114/)
  When I place the finger down, touch screen will send an event with type 1 
(EV_KEY), code 139 (KEY_MENU), and value 1, indicating that the button is 
placed. And when I move the finger away from the button, touch screen will send 
an event with type 1 (EV_KEY), code 139 (KEY_MENU), and value 255. Digging in 
kernel code reveals that this is defined as "BUTTON_CANCLED". Looking in 
libevent code, it seems that it always assume that anything that is not 0 will 
be considered as pressed, which makes it looks like the button is hold.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1547864/+subscriptions

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

** Changed in: mir/0.20
   Status: Triaged => Fix Committed

** Changed in: mir/0.20
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Fix Committed
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

** Changed in: mir/0.20
Milestone: None => 0.20.1

** Branch linked: lp:mir/0.20

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Fix Committed
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1547864] Re: libevent doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED)

[Andreas Pokorny]

So the touchscreen tries to mimic a UI button that only sends a release
when the finger is released while inside the button area.

Since mir does not receive a release event from libinput we send repeat
events instead.

Should we define a cancel key press event type? That might be useful in
other situations too. E.g. when handling pressed keys during VT
switching.

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- libevent doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED)
+ libinput doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1547864

Title:
  libinput doesn't handle EV_KEY event with a value of 255
  (BUTTON_CANCLED)

Status in libinput package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I port Ubuntu Touch to LG L90 Dual. When I press a button below the
  screen (it's the touch button and is part of the touch screen), then
  slide the finger up, a letter will repeatedly appear in any text field
  selected (for instance, if the button is a menu button, letter 'e'
  will appear repeatedly). Using evtest with the touch screen device, I
  can see what happened:

  Event: time 75.605520, type 1 (EV_KEY), code 139 (KEY_MENU), value 1
  Event: time 75.605525, -- EV_SYN 
  Event: time 75.707065, type 1 (EV_KEY), code 139 (KEY_MENU), value 255

  (See the full log here: http://paste.ubuntu.com/15112114/)
  When I place the finger down, touch screen will send an event with type 1 
(EV_KEY), code 139 (KEY_MENU), and value 1, indicating that the button is 
placed. And when I move the finger away from the button, touch screen will send 
an event with type 1 (EV_KEY), code 139 (KEY_MENU), and value 255. Digging in 
kernel code reveals that this is defined as "BUTTON_CANCLED". Looking in 
libevent code, it seems that it always assume that anything that is not 0 will 
be considered as pressed, which makes it looks like the button is hold.

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

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

[Touch-packages] [Bug 1542305] Re: Pressing button on bluetooth game pad shuts unity down

[Andreas Pokorny]

*** This bug is a duplicate of bug 1544878 ***
https://bugs.launchpad.net/bugs/1544878

Yes is a duplicate, the referenced bug will address various similar
issues..

** This bug has been marked a duplicate of bug 1544878
   Mir servers crash if I press the side mouse button (thumb)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1542305

Title:
  Pressing button on bluetooth game pad shuts unity down

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth Ouya game controller. One of these:-

  http://www.amazon.co.uk/OUYA-Wireless-Controller-Electronic-
  Games-y/dp/B002I0GX38

  Note it has a bunch of buttons and the black square in the middle is a
  mouse/touchpad.

  Associated it with my bq e4.5 running todays rc-proposed.
  Mouse cursor appears (kinda expected, but a bit odd - on Android the mouse 
cursor doesn't appear until you touch the pad).
  Press any button and unity8 crashes hard.

  No crash file in /var/crash.

  The following appears immediately after pressing the button, in the
  unity8 log.

  qtmir.surfaces: MirSurfaceItem::MirSurfaceItem
  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is DashCommunicator(0xfe96b0), parent's thread is QThread(0xf1ef90), 
current thread is DashCommunicator(0xfe96b0)
  UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer: Connection 
refused"
  Fail to connect with service: 
QDBusError("org.freedesktop.DBus.Error.Disconnected", "Connection was 
disconnected before a reply was received")

  Running gdb produces this output when the crash happens:-

  Program received signal SIGTERM, Terminated.
  0xb6aa4fa8 in QV4::ExecutionEngine::qmlContextObject() const () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160129-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Fri Feb  5 12:24:52 2016
  InstallationDate: Installed on 2016-02-05 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160205-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

** Changed in: mir (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~andreas-pokorny/mir/fix-1544878

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

libinput treats the ranges BTN_MISC to BTN_GEAR_UP and BTN_DPAS to
BTN_TRIGGER_HAPPY40  as pointer buttons since it does not support
joystick/gamepads yet. So we get a pointer button down event... so there
are probably two places to fix. libinput should grow to support
joysticks, and mir should support more mouse buttons. And convert all
the others as key events until we support joysticks/gamepads too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Andreas Pokorny]

And yes the problem is the conversion routine only deals with BTN_LEFT
_RIGHT, _MIDDLE _BACK _FORWARD .. but not BTN_SIDE  or BTN_EXTRA and
BTN_TASK which are all in the same range of densely defined constants.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions

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

[Touch-packages] [Bug 1539009] Re: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

[Andreas Pokorny]

Started working on a test harness for input resampling..

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1539009

Title:
  Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

Status in Mir:
  Triaged
Status in QtMir:
  Incomplete
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Logging in to Unity8 on desktop (xenial) the mouse cursor moves
  glacially slow. I have to move the mouse across the whole desk to get
  anywhere. This is surprising given bug 1524145 shows the opposite is
  happening in the Mir demo servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:32:27 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539009/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

Mir problem is solved, currently not yet integrated into upcoming 0.20. 
quemu fix is on the way: 
https://code-review.phablet.ubuntu.com/#/c/431/

** Changed in: mir
 Assignee: (unassigned) => Kevin DuBois (kdub)

** Branch linked: lp:~kdub/mir/fix-1517597

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.18 series:
  Opinion
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

I wanted to share some status update, the emulated touchscreen troubles
have been resolved. Now ui elements fail to detect any gestures, the
display claims its phsyical width, height and dpi to be 0.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Opinion
Status in Mir 0.18 series:
  Opinion
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

Mir report 0x0 is the actually something to be fixed in mir to get that
bug resolved.

** Changed in: mir
   Status: Opinion => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.18 series:
  Opinion
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1539009] Re: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

[Andreas Pokorny]

Ah. It seems InputConsumer does not care about EVENT_AXIS_RX and
EVENT_AXIS_RY at all - but it should accumulate it. So it only resamples
the absolute coodinates. That could be a good reason to rewrite the
InputConsume to a more readable code..

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1539009

Title:
  Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse

Status in Mir:
  Confirmed
Status in QtMir:
  Confirmed
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Logging in to Unity8 on desktop (xenial) the mouse cursor moves
  glacially slow. I have to move the mouse across the whole desk to get
  anywhere. This is surprising given bug 1524145 shows the opposite is
  happening in the Mir demo servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:32:27 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539009/+subscriptions

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

[Touch-packages] [Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi

[Andreas Pokorny]

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
   Importance: Undecided => Critical

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1538632

Title:
  ui freezes when simultaneously moving mouse & plug/unplug hdmi

Status in canonical-pocket-desktop:
  New
Status in Mir:
  In Progress
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  confirmed to happen in latest image with usc0.3 and previous images
  with usc0.2

  steps
  1) flash ubuntu-touch/rc-proposed/ubuntu-pd
  2) connect bt mouse and see unity8 go into windowed mode
  3)  move mouse about screen while at the same time connect slimport hdmi cable

  ui will then freeze but seems content, let it sit for 30 min no reboot or 
restart, no crash files, power button does not do anything.
  It's also possible to have the slimport already connected - move mouse around 
disconnect, the ui will freeze altho in this case unity8 always seems to 
restart.

  There are no usc crash files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1538632/+subscriptions

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

[Touch-packages] [Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi

[Andreas Pokorny]

** Description changed:

  confirmed to happen in latest image with usc0.3 and previous images with
  usc0.2
  
  steps
  1) flash ubuntu-touch/rc-proposed/ubuntu-pd
  2) connect bt mouse and see unity8 go into windowed mode
  3)  move mouse about screen while at the same time connect slimport hdmi cable
  
  ui will then freeze but seems content, let it sit for 30 min no reboot or 
restart, no crash files, power button does not do anything.
  It's also possible to have the slimport already connected - move mouse around 
disconnect, the ui will freeze altho in this case unity8 always seems to 
restart.
  
  There are no usc crash files.
+ 
+ The problem is a dead lock on the Display/DisplaySyncGroup mutexes
+ between CompositingFunctor->SystemWindowManager->GraphicsDisplayLayout
+ and DisplayInputRegion.
+ 
+ Thread 6 (Thread 0xb0dff3d0 (LWP 1530)):
+ #0  0xb6cd5d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #1  0xb6cd395c in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #2  0xb6ccf19e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #3  0xb6426f02 in __gthread_mutex_lock (__mutex=0x1b34f14)
+ at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
+ No locals.
+ #4  lock (this=0x1b34f14) at /usr/include/c++/4.9/mutex:135
+ No locals.
+ #5  lock_guard (__m=..., this=0xb0dfeaf0) at /usr/include/c++/4.9/mutex:377
+ No locals.
+ #6  mir::graphics::android::Display::configuration (this=0x1b34ef8)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display.cpp:231
+ lock = {_M_device = @0x1b34f14}
+ #7  0xb6e656ca in mir::shell::GraphicsDisplayLayout::place_in_output 
(this=, id=..., 
+ rect=...)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/graphics_display_layout.cpp:72
+ config = std::unique_ptr 
containing 0xb6eb69c8
+ placed = false
+ #8  0xb6e6a888 in mir::shell::SystemCompositorWindowManager::add_display 
(this=0x1d07b24)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/system_compositor_window_manager.cpp:1
output_id = 
+ rect = {top_left = {x = {value = 0}, y = {value = 0}}, size = {width 
= {value = 768}, height = {
+   value = 1280}}}
+ surface = std::shared_ptr (count 3, weak 4) 0x0
+ __for_range = 
+ lock = {_M_device = @0x1d07b3c}
+ #9  0xb6e1ab32 in operator() (buffer=..., __closure=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #10 std::_Function_handler::_M_invoke(std::_Any_data 
const&, mir::graphics::DisplayBuffer&) (__functor=..., __args#0=...)
+ at /usr/include/c++/4.9/functional:2039
+ No locals.
+ #11 0xb64288a8 in operator() (__args#0=..., this=0xb0dfeca0) at 
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #12 
mir::graphics::android::DisplayGroup::for_each_display_buffer(std::function const&) (this=0x1b35024, f=...)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display_group.cpp:51
+ __for_range = std::map with 1 elements = {
+   [mir::graphics::android::DisplayName::primary] = 
std::unique_ptr containing 
0x1c0db40}
+ lk = {_M_device = 0x1b35028, _M_owns = true}
+ #13 0xb6e1b896 in operator() (__closure=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #14 PairedCalls (deleter=, creator=, 
this=0xb0dfec84)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:33
+ No locals.
+ #15 
paired_calls, 
mir::compositor::CompositingFunctor::operator()():: > 
(deleter=, creator=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:66
+ No locals.
+ #16 mir::compositor::CompositingFunctor::operator() (this=0x1d112d8)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:98
+ disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac
+ display_registration = {deleter = {__this = 0x1d112d8, 
+ __disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac}, 
owner = true}
+ compositor_registration = 
+ compositors = std::vector of length 1, capacity 1 = {std::tuple 
containing = {[1] = 0x1c0db40, 
+ [2] = std::unique_ptr 
containing 0xb0499848}}
+ lock = {_M_device = 0xb0402c44, _M_owns = true}
+ #17 0xb6e8aa58 in operator() (this=0xb0dfed84) at 
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #18 execute (this=0xb0dfed84)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/thread/basic_thread_pool.cpp:40
+ No locals.
+ #19 operator() 

[Touch-packages] [Bug 1538172] Re: Keyboard shortcuts stop working after console switching

[Andreas Pokorny]

*** This bug is a duplicate of bug 1536279 ***
https://bugs.launchpad.net/bugs/1536279

** This bug has been marked a duplicate of bug 1536279
   Mir does not reset key states when paused or resumed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1538172

Title:
  Keyboard shortcuts stop working after console switching

Status in mir package in Ubuntu:
  New

Bug description:
  qtmir-desktop 0.4.7+16.04.20160122-0ubuntu1
  (let me know if you need any other package version)

  Running on Xenial with unity8-desktop-session-mir installed.

  How to reproduce:
  1) login to Unity8
  2) Take a screenshot and verify that the button works
  3) switch to a virtual console (Ctrl+Alt+F2, for instance)
  4) switch back to Unity8 (Ctrl+Alt+F8)
  5) Press PrintScr again (or Alt+F4 to close an app)

  Expected outcome:
  The shortcut triggers an action

  Actual outcome:
  nothing happens

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

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

This is not a stylus emulation.. Touch screen and Mouse devices overlap
in the axes they use. SInce mice with absolute coordinates are allowed
too (i.e VMWare Mouse Emulation). A device that tries to mimic both will
run into problems, since there are differences in the press/release
behavior. If you then go on and add multitouch axes to the mix it will
get even worse, because suddenly the difference between a touchscreen a
touchpad and a mouse is lost. A device that changes its behavior without
notifying user space is not really helping here either. The android-qemu
fork could solved that in various ways. Especially not cramping
everything into a single device would have helped a lot. But I will
focus on getting the touch screen emulation working again. It does now
locally after removing the relative mouse events, but still the edge
swipes do not work. Need to look into that further.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Mir 0.18 series:
  Invalid
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

** Changed in: mir/0.18
Milestone: 0.18.1 => None

** Changed in: mir
Milestone: 0.19.0 => None

** Changed in: mir
   Status: Opinion => Invalid

** Changed in: mir/0.18
   Status: Opinion => Invalid

** Changed in: mir (Ubuntu)
   Status: Opinion => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Mir 0.18 series:
  Invalid
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1531517] Re: [regression] pinch to zoom not working reliably

[Andreas Pokorny]

Ah yes the android input transport is biting us again. We are still
bound to the limitation of that encoding. That encoding means - only one
down/up touch id per event. No matter what libinput reads or qtmir
sanitizes.. , as long as the transport from server to nested server or
from nested server to client chops of the information of every
additional down or up the gesture will break. I will keep the fix close
to the encoding so we can get rid of it easier...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1531517

Title:
  [regression] pinch to zoom not working reliably

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.18 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Won't Fix

Bug description:
  in the last few days (using rc-proposed 221 on krillin) pinch to zoom
  gestures do not work reliably anymore.

  Appears to be system wide as there have been reports in the follow
  apps that all use PinchArea from QML:

  - Camera: pinch to zoom in viewfinder stops working, pinch to zoom in Photo 
Roll to zoom a photo stops working
  - Gallery: open a photo and pinch to zoom doesn't work
  - Webbrowser: pinch to zoom on a web page not working

  Could be mir/qtmir related

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531517/+subscriptions

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

[Touch-packages] [Bug 1530384] Re: Touchscreen stop working on LG L90 Dual

[Andreas Pokorny]

If you manage to identify the device in a udev rule you could try to
attach ID_INPUT_TOUCHSCREEN=1 to extend the result of udevs own checks
with the right result. Meanwhile I will look how to extend the detection
logic inside systemd/udev to get this fixed.

I believe the problem here is not limited to this device. Looking
through the exposed keys it also sends BTN_TOUCH which should be enough
for udev to detect it..

** Also affects: udev
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1530384

Title:
  Touchscreen stop working on LG L90 Dual

Status in Canonical System Image:
  New
Status in udev:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I ports Ubuntu touch to LG L90 Dual. When I upgraded my device from
  20151218.1 to 20151221 (channel rc-proposed), the touchscreen stopped
  working. A discussion in IRC with @anpok_ suggesting that it may come
  from changing input system to udev/libevdev/libinput.

  The following udevadm output is most likely from the Touch Screen:

  $ udevadm test-builtin input_id /devices/virtual/input/input0/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: b
  capabilities/ev decoded bit map:
bit0: 000B
  capabilities/abs raw kernel attribute: 6718000 0
  capabilities/abs decoded bit map:
bit0: 
bit   32: 06718000
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 200 0 1000 4800 10 
0 1000 0
  capabilities/key decoded bit map:
bit0: 
bit   32: 1000
bit   64: 
bit   96: 0010
bit  128: 4800
bit  160: 1000
bit  192: 
bit  224: 0200
bit  256: 
bit  288: 
bit  320: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=1
  test_key: checking bit block 64 for any keys; found=1
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  The driver claims that is provides the multi touch axis touch major,
  touch minor, tracking id, x, y, tool type and slot id. So apart from
  missing properties like DIRECT it seems to be a normal touch screen,
  but udev clearly does not detect it properly.

  
  --
  The other devices are probably not the touchscreen...

  $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: 3
  capabilities/ev decoded bit map:
    bit0: 0003
  capabilities/abs raw kernel attribute: 0
  capabilities/abs decoded bit map:
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 0 c0040 0 0 0
  capabilities/key decoded bit map:
    bit0: 
    bit   32: 
    bit   64: 
    bit   96: 000C0040
    bit  128: 
    bit  160: 
    bit  192: 
    bit  224: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=0
  test_key: checking bit block 64 for any keys; found=0
  test_key: checking bit block 96 for any keys; 

[Touch-packages] [Bug 1530384] Re: Touchscreen stop working on LG L90 Dual

[Andreas Pokorny]

** Description changed:

  I ports Ubuntu touch to LG L90 Dual. When I upgraded my device from
  20151218.1 to 20151221 (channel rc-proposed), the touchscreen stopped
  working. A discussion in IRC with @anpok_ suggesting that it may come
- from changing input system to libevent.
- 
- $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
- calling: test-builtin
- === trie on-disk ===
- tool version:  219
- file size: 6711498 bytes
- header size 80 bytes
- strings1721914 bytes
- nodes  4989504 bytes
- Load module index
- Network interface NamePolicy= disabled on kernel command line, ignoring.
- timestamp of '/etc/systemd/network' changed
- timestamp of '/usr/lib/systemd/network' changed
- Parsed configuration file /lib/systemd/network/99-default.link
- Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
- Created link configuration context.
- ID_INPUT=1
- capabilities/ev raw kernel attribute: 3
- capabilities/ev decoded bit map:
-   bit0: 0003
- capabilities/abs raw kernel attribute: 0
- capabilities/abs decoded bit map:
- capabilities/rel raw kernel attribute: 0
- capabilities/rel decoded bit map:
- capabilities/key raw kernel attribute: 400 0 0 0 c0040 0 0 0
- capabilities/key decoded bit map:
-   bit0: 
-   bit   32: 
-   bit   64: 
-   bit   96: 000C0040
-   bit  128: 
-   bit  160: 
-   bit  192: 
-   bit  224: 0400
- properties raw kernel attribute: 0
- properties decoded bit map:
- test_key: checking bit block 0 for any keys; found=0
- test_key: checking bit block 32 for any keys; found=0
- test_key: checking bit block 64 for any keys; found=0
- test_key: checking bit block 96 for any keys; found=1
- test_key: checking bit block 128 for any keys; found=1
- test_key: checking bit block 160 for any keys; found=1
- test_key: checking bit block 192 for any keys; found=1
- test_key: checking bit block 224 for any keys; found=1
- ID_INPUT_KEY=1
- Unload module index
- Unloaded link configuration context.
+ from changing input system to udev/libevdev/libinput.
+ 
+ The following udevadm output is most likely from the Touch Screen:
  
  $ udevadm test-builtin input_id /devices/virtual/input/input0/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: b
  capabilities/ev decoded bit map:
bit0: 000B
  capabilities/abs raw kernel attribute: 6718000 0
  capabilities/abs decoded bit map:
bit0: 
bit   32: 06718000
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 200 0 1000 4800 10 
0 1000 0
  capabilities/key decoded bit map:
bit0: 
bit   32: 1000
bit   64: 
bit   96: 0010
bit  128: 4800
bit  160: 1000
bit  192: 
bit  224: 0200
bit  256: 
bit  288: 
bit  320: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=1
  test_key: checking bit block 64 for any keys; found=1
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.
  
- $ udevadm test-builtin input_id /devices/virtual/input/input1/
+ The driver claims that is provides the multi touch axis touch major,
+ touch minor, tracking id, x, y, tool type and slot id. So apart from
+ missing properties like DIRECT it seems to be a normal touch screen, but
+ udev clearly does not detect it properly.
+ 
+ 
+ --
+ The other devices are probably not the touchscreen...
+ 
+ $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, 

[Touch-packages] [Bug 1530384] Re: Touchscreen stop working on LG L90 Dual

[Andreas Pokorny]

Ok found the cause. The logic inside udev test ABS_X ABS_Y + BTN_TOUCH
which catches a lot of single touchscreens. For multi touch coordinates
as advertised here there is only a test for ABS_MT_POSITION_X + Y and
property DIRECT.. So adding another case for BTN_TOUCH instead of DIRECT
should solve the issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1530384

Title:
  Touchscreen stop working on LG L90 Dual

Status in Canonical System Image:
  New
Status in udev:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I ports Ubuntu touch to LG L90 Dual. When I upgraded my device from
  20151218.1 to 20151221 (channel rc-proposed), the touchscreen stopped
  working. A discussion in IRC with @anpok_ suggesting that it may come
  from changing input system to udev/libevdev/libinput.

  The following udevadm output is most likely from the Touch Screen:

  $ udevadm test-builtin input_id /devices/virtual/input/input0/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: b
  capabilities/ev decoded bit map:
bit0: 000B
  capabilities/abs raw kernel attribute: 6718000 0
  capabilities/abs decoded bit map:
bit0: 
bit   32: 06718000
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 200 0 1000 4800 10 
0 1000 0
  capabilities/key decoded bit map:
bit0: 
bit   32: 1000
bit   64: 
bit   96: 0010
bit  128: 4800
bit  160: 1000
bit  192: 
bit  224: 0200
bit  256: 
bit  288: 
bit  320: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=1
  test_key: checking bit block 64 for any keys; found=1
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  The driver claims that is provides the multi touch axis touch major,
  touch minor, tracking id, x, y, tool type and slot id. So apart from
  missing properties like DIRECT it seems to be a normal touch screen,
  but udev clearly does not detect it properly.

  
  --
  The other devices are probably not the touchscreen...

  $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: 3
  capabilities/ev decoded bit map:
    bit0: 0003
  capabilities/abs raw kernel attribute: 0
  capabilities/abs decoded bit map:
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 0 c0040 0 0 0
  capabilities/key decoded bit map:
    bit0: 
    bit   32: 
    bit   64: 
    bit   96: 000C0040
    bit  128: 
    bit  160: 
    bit  192: 
    bit  224: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=0
  test_key: checking bit block 64 for any keys; found=0
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
 

[Touch-packages] [Bug 1530384] Re: Touchscreen stop working on LG L90 Dual

[Andreas Pokorny]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: udev
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1530384

Title:
  Touchscreen stop working on LG L90 Dual

Status in Canonical System Image:
  Confirmed
Status in udev:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  I ports Ubuntu touch to LG L90 Dual. When I upgraded my device from
  20151218.1 to 20151221 (channel rc-proposed), the touchscreen stopped
  working. A discussion in IRC with @anpok_ suggesting that it may come
  from changing input system to udev/libevdev/libinput.

  The following udevadm output is most likely from the Touch Screen:

  $ udevadm test-builtin input_id /devices/virtual/input/input0/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: b
  capabilities/ev decoded bit map:
bit0: 000B
  capabilities/abs raw kernel attribute: 6718000 0
  capabilities/abs decoded bit map:
bit0: 
bit   32: 06718000
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 200 0 1000 4800 10 
0 1000 0
  capabilities/key decoded bit map:
bit0: 
bit   32: 1000
bit   64: 
bit   96: 0010
bit  128: 4800
bit  160: 1000
bit  192: 
bit  224: 0200
bit  256: 
bit  288: 
bit  320: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=1
  test_key: checking bit block 64 for any keys; found=1
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  The driver claims that is provides the multi touch axis touch major,
  touch minor, tracking id, x, y, tool type and slot id. So apart from
  missing properties like DIRECT it seems to be a normal touch screen,
  but udev clearly does not detect it properly.

  
  --
  The other devices are probably not the touchscreen...

  $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: 3
  capabilities/ev decoded bit map:
    bit0: 0003
  capabilities/abs raw kernel attribute: 0
  capabilities/abs decoded bit map:
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 0 c0040 0 0 0
  capabilities/key decoded bit map:
    bit0: 
    bit   32: 
    bit   64: 
    bit   96: 000C0040
    bit  128: 
    bit  160: 
    bit  192: 
    bit  224: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=0
  test_key: checking bit block 64 for any keys; found=0
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  
  $ udevadm test-builtin 

[Touch-packages] [Bug 1530384] Re: Touchscreen stop working on LG L90 Dual

[Andreas Pokorny]

Proposed an upstream fix https://github.com/systemd/systemd/pull/2248

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1530384

Title:
  Touchscreen stop working on LG L90 Dual

Status in Canonical System Image:
  Confirmed
Status in udev:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  I ports Ubuntu touch to LG L90 Dual. When I upgraded my device from
  20151218.1 to 20151221 (channel rc-proposed), the touchscreen stopped
  working. A discussion in IRC with @anpok_ suggesting that it may come
  from changing input system to udev/libevdev/libinput.

  The following udevadm output is most likely from the Touch Screen:

  $ udevadm test-builtin input_id /devices/virtual/input/input0/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: b
  capabilities/ev decoded bit map:
bit0: 000B
  capabilities/abs raw kernel attribute: 6718000 0
  capabilities/abs decoded bit map:
bit0: 
bit   32: 06718000
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 200 0 1000 4800 10 
0 1000 0
  capabilities/key decoded bit map:
bit0: 
bit   32: 1000
bit   64: 
bit   96: 0010
bit  128: 4800
bit  160: 1000
bit  192: 
bit  224: 0200
bit  256: 
bit  288: 
bit  320: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=1
  test_key: checking bit block 64 for any keys; found=1
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  The driver claims that is provides the multi touch axis touch major,
  touch minor, tracking id, x, y, tool type and slot id. So apart from
  missing properties like DIRECT it seems to be a normal touch screen,
  but udev clearly does not detect it properly.

  
  --
  The other devices are probably not the touchscreen...

  $ udevadm test-builtin input_id /devices/gpio_keys.70/input/input2/
  calling: test-builtin
  === trie on-disk ===
  tool version:  219
  file size: 6711498 bytes
  header size 80 bytes
  strings1721914 bytes
  nodes  4989504 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/usr/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /etc/systemd/network/00-rmnet-kernel.link
  Created link configuration context.
  ID_INPUT=1
  capabilities/ev raw kernel attribute: 3
  capabilities/ev decoded bit map:
    bit0: 0003
  capabilities/abs raw kernel attribute: 0
  capabilities/abs decoded bit map:
  capabilities/rel raw kernel attribute: 0
  capabilities/rel decoded bit map:
  capabilities/key raw kernel attribute: 400 0 0 0 c0040 0 0 0
  capabilities/key decoded bit map:
    bit0: 
    bit   32: 
    bit   64: 
    bit   96: 000C0040
    bit  128: 
    bit  160: 
    bit  192: 
    bit  224: 0400
  properties raw kernel attribute: 0
  properties decoded bit map:
  test_key: checking bit block 0 for any keys; found=0
  test_key: checking bit block 32 for any keys; found=0
  test_key: checking bit block 64 for any keys; found=0
  test_key: checking bit block 96 for any keys; found=1
  test_key: checking bit block 128 for any keys; found=1
  test_key: checking bit block 160 for any keys; found=1
  test_key: checking bit block 192 for any keys; found=1
  test_key: checking bit block 224 for any keys; found=1
  ID_INPUT_KEY=1
  Unload module index
  Unloaded link configuration context.

  
  $ udevadm test-builtin input_id /devices/virtual/input/input1/
  calling: test-builtin

[Touch-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly

[Andreas Pokorny]

Wrt to the segmentation fault more details in
https://bugs.launchpad.net/mir/+bug/1526658

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209

Title:
  [regression] Clients of nested Mir servers silently crash/exit
  instantly

Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Clients of nested Mir servers silently crash/exit instantly (on
  xenial)

  This happens in Mir trunk lp:mir and lp:mir/0.18, but not in
  lp:mir/0.17

    sudo bin/mir_demo_server_minimal -f /tmp/outside &
    sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside &
    sudo bin/mir_demo_client_egltriangle -m /tmp/inside

  And the client silently exits with return code 139.

  Valgrind or gdb show the problem though:

  ==16515== Process terminating with default action of signal 11 (SIGSEGV)
  ==16515==  Access not within mapped region at address 0x123460A8
  ==16515==at 0x6EA16E0: XGetXCBConnection (in 
/usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0)
  ==16515==by 0x517AC73: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5174ADE: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5174B98: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5170B31: eglInitialize (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350)
  ==16515==by 0x4024EC: main (egltriangle.c:85)

  #0  0x75b6e6e0 in XGetXCBConnection ()
     from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x77893c74 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #2  0x7788dadf in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #3  0x7788db99 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #4  0x77889b32 in eglInitialize ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #5  0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548,
  width=0x7fffdd48, height=0x7fffdd4c)
  at /home/dan/bzr/mir/0.18/examples/eglapp.c:350
  #6  0x004024ed in main (argc=3, argv=0x7fffe548)
  at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions

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

[Touch-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly

[Andreas Pokorny]

Yes i can also remember seeing that stacktrace when toying around with
our reload hack, to get mesa to find our symbols during egl display
detection. But I dont get that anymore on xenial with lp:mir or
lp:mir/0.18

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209

Title:
  [regression] Clients of nested Mir servers silently crash/exit
  instantly

Status in Mir:
  Triaged
Status in Mir 0.18 series:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Clients of nested Mir servers silently crash/exit instantly (on
  xenial)

  This happens in Mir trunk lp:mir and lp:mir/0.18, but not in
  lp:mir/0.17

    sudo bin/mir_demo_server_minimal -f /tmp/outside &
    sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside &
    sudo bin/mir_demo_client_egltriangle -m /tmp/inside

  And the client silently exits with return code 139.

  Valgrind or gdb show the problem though:

  ==16515== Process terminating with default action of signal 11 (SIGSEGV)
  ==16515==  Access not within mapped region at address 0x123460A8
  ==16515==at 0x6EA16E0: XGetXCBConnection (in 
/usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0)
  ==16515==by 0x517AC73: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5174ADE: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5174B98: ??? (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x5170B31: eglInitialize (in 
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0)
  ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350)
  ==16515==by 0x4024EC: main (egltriangle.c:85)

  #0  0x75b6e6e0 in XGetXCBConnection ()
     from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
  #1  0x77893c74 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #2  0x7788dadf in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #3  0x7788db99 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #4  0x77889b32 in eglInitialize ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #5  0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548,
  width=0x7fffdd48, height=0x7fffdd4c)
  at /home/dan/bzr/mir/0.18/examples/eglapp.c:350
  #6  0x004024ed in main (argc=3, argv=0x7fffe548)
  at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions

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

[Touch-packages] [Bug 1517133] Re: [regression] Mouse speed in Unity8 is much lower than elsewhere (to the point of useless)

[Andreas Pokorny]

** Changed in: mir
   Status: Invalid => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517133

Title:
  [regression] Mouse speed in Unity8 is much lower than elsewhere (to
  the point of useless)

Status in Mir:
  Fix Committed
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Running unity8 as a session on the desktop.

  The mouse is so "slow" (i.e a movement in reality moves it very few
  pixels on screen) that i can't really use it since i need to lift it
  and restart the movement a few times if i want to go to the other side
  of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1517133/+subscriptions

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

[Touch-packages] [Bug 1517133] Re: [regression] Mouse speed in Unity8 is much lower than elsewhere (to the point of useless)

[Andreas Pokorny]

You can see this bug from various perspectives. For common mice mouse,
movement of the cursor  on a high dpi screen is just slow. But since you
still need accuracy you cannot just scale the movement. To allow exact
cursor placement, movement dependent cceleration is the proper solution
for this problem.

The fact that the android input stack did not offer acceleration was not
a decision we made for versions prior to 0.18, but rather a bug in the
velocity tracker for some reason it queried and tracked a non existent
touch id. Fixing that required refactoring our tests to not rely on that
bug. Which happened in the course of this year. In the end we just
switched to libinuput.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517133

Title:
  [regression] Mouse speed in Unity8 is much lower than elsewhere (to
  the point of useless)

Status in Mir:
  Fix Committed
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Running unity8 as a session on the desktop.

  The mouse is so "slow" (i.e a movement in reality moves it very few
  pixels on screen) that i can't really use it since i need to lift it
  and restart the movement a few times if i want to go to the other side
  of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1517133/+subscriptions

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

[Touch-packages] [Bug 1519235] Re: Nexus 4 - HDMI-Slimport adapter can't charge the phone and display the screen at the same time.

[Andreas Pokorny]

I have a slimport adaber with a USB-A plug - attaching and detaching
that one from the charger or PC does not influence the HDMI output.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1519235

Title:
  Nexus 4 - HDMI-Slimport adapter can't charge the phone and display the
  screen at the same time.

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  I have a Nexus4 device and I bought a MyDP HDMI-SlimPort adapter,
  which is compatible with N4. But I can't charge my phone and display
  the screen on the external display at the same time. If I connect the
  charger the screen switches back to the device, If I disconnect the
  charger, the screen switches to the external display. It works well
  with Android.

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

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

[Touch-packages] [Bug 1520422] Re: Keyboard and mouse events should prevent screen turning off

[Andreas Pokorny]

The linked MP solves the issue.

Note that this bug and the MP does not include turning the screen on
through mouse movement or key presses..

** Branch linked: lp:~andreas-pokorny/unity-system-
compositor/fix-1514059-and-keep-display-on-for-key-presses

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1520422

Title:
  Keyboard and mouse events should prevent screen turning off

Status in Canonical System Image:
  New
Status in canonical-pocket-desktop:
  New
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I often use a bluetooth keyboard with the terminal for long periods.
  When I do so, I have to keep tapping the screen to keep it awake.
  That in turn enters a tab character so I then have to delete the
  inserted tab.  It's a pretty frustrating way to work.

  Instead, every bluetooth keypress should count as a screen wake event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520422/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: Ubuntu-emulator is broken on rc image 3

[Andreas Pokorny]

After trying around a bit more... If we intend to use the emulator in
the future we might want to tweak which input devices are exposed the
guest system. RIght now there is a single odd abs-relative-touchscreen-
mouse hybrid. For odd reasons it was treated as touch screen in the past
(we didnt really differ with the android stack: everything not a key
event is a motion event). With  libinput it will be seen as a mouse that
either emits absolute or relative coodinates. So we will lack the
capability to simulate touch input.

Additionally the relative mouse mode works very badly. It seems to skip
a lot of mouse movement or they are scaled down?

For either of the problems we might have to change the emulator window
code. Which I believe we take from here:

https://android.googlesource.com/platform/external/qemu/+/master/android/skin/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  Ubuntu-emulator is broken on rc image 3

Status in Canonical System Image:
  Incomplete
Status in mir package in Ubuntu:
  New
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: Ubuntu-emulator is broken on rc image 3

[Andreas Pokorny]

Or is the intention of the emulator to simulate a touch screen - hence
the input events only appear on press?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  Ubuntu-emulator is broken on rc image 3

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: Ubuntu-emulator is broken on rc image 3

[Andreas Pokorny]

After some digging inside the code of the emulator.. The behaviour
described above seems to be intended - at least to some degree.

To move the mouse the user has to press F6 to toggle into trackball mode
and use the mouse cursor. And it should work as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  Ubuntu-emulator is broken on rc image 3

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1517597] Re: Ubuntu-emulator is broken on rc image 3

[Andreas Pokorny]

Here are actually three problem at work:
 * The input device exposed inside the emulator /dev/input/event0 only emit 
absolute coordinate events. We recently experienced something similar with 
other incarnation of qemu in kvm: https://bugs.launchpad.net/mir/+bug/1489522 ( 
in that bug  two mouse devices are available, the one that claims to expose 
relative events never emits them) The actual cause might be in the emulator 
integration itself.
 * The input device only emits those event on mouse button down. WIthout 
pressing a mouse button the evdev device remains silent. Another emulator 
problem?
 * The android input stack used in mir does not care about absolute mouse 
movement events. So even on mouse down it does not handle those  events. The 
upcomig mir will, since it will default to mir-platform-input-evdev. So this 
will disappear with 0.18

At the moment you can see the mouse moves when you change to the new stack:
apt-get update && apt-get install mir-platform-input-evdev3
then edit  /usr/share/ubuntu-touch-session/usc-wrapper
and add
 --platform-input-lib 
/usr/lib/i386-linux-gnu/mir/server-platform/input-evdev.so.3
to the call to unity-system-compositor

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597

Title:
  Ubuntu-emulator is broken on rc image 3

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1513792] Re: mircookie requires nettle but libmircookie-dev doesn't depend on it

[Andreas Pokorny]

** Branch linked: lp:~afrantzis/mir/fix-1514391-mircookie-nettle-dev-
dependency

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1513792

Title:
  mircookie requires nettle but libmircookie-dev doesn't depend on it

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I thought that bug #1513225 was fixing this but it wasn't.

  As long as you have Requires.private: nettle in mircookie's pcfile,
  libmircookie-dev package needs to Depend on it (since pkg-config will
  cry otherwise), like:

Package 'nettle', required by 'mircookie', not found

  We're getting this failure in gtk+ now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1513792/+subscriptions

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

[Touch-packages] [Bug 1502896] Re: CI segfault in mir-mediumtests-runner-mako in client tests

[Andreas Pokorny]

Look for lp:1506137 which also mentions the above scenario with
mir_client_basic.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1502896

Title:
  CI segfault in mir-mediumtests-runner-mako in client tests

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
  mako/6883/consoleFull:

  /bin/bash: line 1: 6408 Segmentation fault mir_demo_server --test-
  client /usr/bin/mir_demo_client_fingerpaint

  Other recent CI failures that could be related:

  https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
  mako/6874/console

  [ RUN ] GLMark2Test.benchmark_fullscreen_default
  [1444017567.936891] mirplatform: Found graphics driver: android
  [1444017567.937715] mirplatform: Found graphics driver: mesa-kms
  [1444017567.937867] mirplatform: Found graphics driver: mesa-x11
  [1444017567.938630] mirplatform: Found graphics driver: dummy
  /bin/bash: line 1: 5759 Segmentation fault (core dumped) umockdev-run -- 
mir_performance_tests

  And also:

  https://bugs.launchpad.net/mir/+bug/1502782

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502896/+subscriptions

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