from:"mir\-ci\-bot"

[Touch-packages] [Bug 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

2017-08-09 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1672960

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
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.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
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/1672960/+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 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

2017-06-20 Thread mir-ci-bot

Fix committed into lp:miral at revision 559, scheduled for release in
miral, milestone Unknown

** Changed in: miral
   Status: Fix Released => Fix Committed

-- 
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/1625853

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in MirAL:
  Fix Committed
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625853/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up

2017-04-29 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.28.0

** Changed in: mir
   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/1655804

Title:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up.

  Test case:
   1. $ sudo apt install mir-demos
   2. $ mir_demo_client_target -- --desktop_file_hint=unity8
   3. Wiggle the mouse around over the window

  The problem goes away after you manually resize the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1655804/+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 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it

2017-04-11 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.28.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/1674201

Title:
  cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
  due to libudev.so being in a different directory to where libudev.pc
  searches for it

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Mir fails to build on arm64 cross-compiled:

  [ 11%] Linking CXX shared library ../../lib/libmirplatform.so
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1674201/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up

2017-04-10 Thread mir-ci-bot

Fix committed into lp:mir at revision 4150, scheduled for release in
mir, milestone 0.28.0

** Changed in: mir
   Status: Triaged => 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/1655804

Title:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up.

  Test case:
   1. $ sudo apt install mir-demos
   2. $ mir_demo_client_target -- --desktop_file_hint=unity8
   3. Wiggle the mouse around over the window

  The problem goes away after you manually resize the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1655804/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-04-06 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.28.0

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

-- 
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/1669524

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1676931] Re: logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport

2017-04-03 Thread mir-ci-bot

Fix committed into lp:unity-system-compositor at revision 311, scheduled
for release in unity-system-compositor, milestone Unknown

** Changed in: unity-system-compositor
   Status: In Progress => Fix Committed

-- 
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/1676931

Title:
  logs are not included in unity-system-compositor bugs automatically
  reported to Ubuntu using apport

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  Fix Committed
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676931/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-03-30 Thread mir-ci-bot

Fix committed into lp:mir at revision 4129, scheduled for release in
mir, milestone 0.27.0

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

-- 
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/1669524

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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)

2017-03-28 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/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:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released

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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

2017-03-27 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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:
  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 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

2017-03-24 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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:
  In Progress
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 1675138] Re: Please transition to Boost 1.62

2017-03-22 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1675138

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1672269] Re: [regression] Mixing screen rotation with mode changes makes the image squished

2017-03-21 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1672269

Title:
  [regression] Mixing screen rotation with mode changes makes the image
  squished

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Mixing screen rotation with mode changes makes the image
  squished

  This problem is visible in lp:mir but not in Mir 0.26 (zesty):

  1. Start a client
  2. Move the client to the top left of the screen.
  3. Rotate right (mirout rotate right)
  3. Lower the resolution (mirout mode 720x400)

  Expected: Rendering stays in correct proportions
  Observed: Rendering is squished out of proportion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1672269/+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 1393578] Re: Subpixel order not included in Mir display information

2017-03-13 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

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

-- 
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/1393578

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2017-03-09 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1669444] Re: [regression] OSK input shaping no longer works correctly

2017-03-08 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1669444

Title:
  [regression] OSK input shaping no longer works correctly

Status in Canonical System Image:
  Triaged
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-keyboard package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this 
more usable at present)
  2) Click in an input field
  3) Move the mouse over the keyboard
  4) Attempt to click on the app again

  Expected result:

  The mouse click should be passed through to the app

  Actual result:

  The click is swallowed by the keyboard surface instead. However, it is
  still possible to click on the app if this is done prior to the mouse
  entering the visible keyboard area.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2017-03-08 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few

2017-03-07 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

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

-- 
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/1211700

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  New

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1211700/+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 1665802] Re: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard

2017-03-07 Thread mir-ci-bot

Fix committed into lp:mir at revision 4072, scheduled for release in
mir, milestone 1.0.0

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

-- 
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/1665802

Title:
  [regression] mir_demo_client_eglplasma results in 100% cpu and hardly
  any updates in dragonboard

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  On a dragonboard 410c,

  With Mir 0.25 mir_demo_client_eglplasma renders steadily at 15FPS and
  with low cpu usage.

  With mir 0.26.1, the process takes 100% cpu (according to top) and
  frames hardly update on screen, but the client performance is
  60-27FPS.

  To replicate:

  mir_demo_server --arw-file --launch-client mir_demo_client_eglplasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1665802/+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 1667645] Re: If the only surface in a session cannot take focus the server crashes

2017-02-26 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1667645

Title:
  If the only surface in a session cannot take focus the server crashes

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Triaged
Status in miral package in Ubuntu:
  Triaged

Bug description:
  The problem is in ms::ApplicationSession::surface_after() it can
  dereference the surfaces.end() iterator.

  Original description:

  $ bin/miral-desktop
  ...
  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
    what():  surface_after: surface is not a member of this session
  Aborted (core dumped)

  Using tiling WM doesn't exhibit this problem:

  $ bin/miral-desktop --window-manager tiling

  I would guess this is something to do with the recent addition of
  wallpaper. And possibly due to this test box being slow (14 years
  old), not due to Xenial/Mir 21.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1667645/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

2017-02-20 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 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/1663062

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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

2017-02-16 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1664610

Title:
  qtubuntu sends wrong text as part of QKeyEvent

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  In Progress

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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

2017-02-13 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1663062

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 Num Lock

2017-02-07 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1588237

Title:
  Inconsistent behaviour of Num Lock

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

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 1661521] Re: [regression] Windowed clients of nested servers are all black

2017-02-06 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1661521

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661521/+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 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

2017-02-03 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: Triaged => 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/1661508

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661508/+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 1645372] Re: support display scaling slider in unity8

2017-01-26 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: In Progress => 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/1645372

Title:
  support display scaling slider in unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645372/+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 1369763] Re: [performance] Android overlays don't honour eglSwapInterval 0

2017-01-24 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: Triaged => 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/1369763

Title:
  [performance] Android overlays don't honour eglSwapInterval 0

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  eglSwapInterval 0 does not work when overlays are enabled.

  Both of these report the same fps:

  MIR_CLIENT_PERF_REPORT=log ./mir_demo_server_basic 
--launch-client="./mir_demo_client_egltriangle" --disable-overlays false
  MIR_CLIENT_PERF_REPORT=log ./mir_demo_server_basic 
--launch-client="./mir_demo_client_egltriangle -n" --disable-overlays false

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1369763/+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 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

2017-01-17 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1240909

Title:
  [performance] Restore support for better-than-triple buffering by
  default.

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  We really should restore support for double-buffering (or better)
  where possible. Presently we're on triple-buffering all the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1240909/+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 1591328] Re: Pointer/cursor input lag in unity8 session

2017-01-17 Thread mir-ci-bot

Fix committed into lp:mir at revision 3952, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: In Progress => 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/1591328

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Mouse pointer suffers of heavy input lag on my laptop, might also
  affect tablet

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591328/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2017-01-16 Thread mir-ci-bot

Fix committed into lp:mir at revision 3949, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1654612] Re: Setting the event handler after the surface has been created does nothing

2017-01-09 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   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/1654612

Title:
  Setting the event handler after the surface has been created does
  nothing

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Setting the surface spec for the event handler after the surface has
  been created does nothing.

  Reason:

  We dont set the event handler and recreate the input thread!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654612/+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 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

2017-01-04 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   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/1606418

Title:
  PointerConfinement.test_we_update_our_confined_region_on_a_resize

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Randomly fails 1/100 times.
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console

  Looking into it, most likely a race with surface resize...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1606418/+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 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more

2017-01-04 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   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/1654023

Title:
  [regression] Development headers reference unknown header
  "mir_toolkit/mir_input_device_types.h" so some clients can't build at
  all any more

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Trying to build GTK+ which uses mircommon and mirclient, I'm getting:

  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.
  Makefile:652: recipe for target 'gdkmircursor.lo' failed
  make[4]: *** [gdkmircursor.lo] Error 1
  make[4]: *** Waiting for unfinished jobs
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.   

  Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed   

  make[4]: *** [gdkmirdevicemanager.lo] Error 1 
 
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
 
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
  
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24:

  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"

  It seems like this header was moved, or possibly it wasn't installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654023/+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 1653789] Re: DisplayConfigurationTest.configure_session_removed_display failure

2017-01-03 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   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/1653789

Title:
  DisplayConfigurationTest.configure_session_removed_display failure

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  19:32:28 11: [2017-01-03 19:32:28.499435] mirserver: Session virtual void 
mir_test_framework::ConnectedClientHeadlessServer::SetUp() removed display 
configuration
  19:32:28 11: 
  19:32:28 11: GMOCK WARNING:
  19:32:28 11: Uninteresting mock function call - returning directly.
  19:32:28 11: Function call: session_configuration_removed(@0xbc0ca80 16-byte 
object <00-A8 97-0A 00-00 00-00 F0-A7 97-0A 00-00 00-00>)
  19:32:28 11: Stack trace:
  19:32:38 11: [2017-01-03 19:32:38.595943] mirserver: Stopping
  19:32:38 11: 
/<>/mir-0.26.0+xenial3324bzr3948/tests/acceptance-tests/test_new_display_configuration.cpp:1810:
 Failure
  19:32:38 11: Actual function call count doesn't match EXPECT_CALL(*observer, 
session_configuration_removed(_))...
  19:32:38 11: Expected: to be called once
  19:32:38 11: Actual: never called - unsatisfied and active
  19:32:38 11: [ FAILED ] 
DisplayConfigurationTest.configure_session_removed_display (11053 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3294/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1653789/+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 1651391] Re: Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

2016-12-20 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   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/1651391

Title:
  Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  tests/mirtest.pc.in contains the line:

  Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

  But debian/control doesn't have the corresponding dependency on mir-
  renderer-gl-dev

  (I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
  renderer-gl.pc, but that's a secondary issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651391/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-12-12 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1584894] Re: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU

2016-11-06 Thread mir-ci-bot

Fix committed into lp:mir at revision 3804, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1584894

Title:
  unity-system-compositor (or any Mir server) crashes on start-up with
  "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics
  Adapter and QEMU

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  (separated from bug 1118903)
  unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter

  ---

  can not login to Unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 23 19:20:43 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:

  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.68-1
  version.lightdm: lightdm 1.19.0-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584894/+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 1634508] Re: Clients cannot connect when MIR_SOCKET=""

2016-10-19 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: In Progress => 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/1634508

Title:
  Clients cannot connect when MIR_SOCKET=""

Status in Mir:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Launch a Unity 8 desktop session, log out, then log into a Unity 7
  session. Launch a Mir-on-X shell like MirAL and then try to launch a
  Mir client like mir_demo_client_egltriangle. The client will refuse to
  connect.

  Unity 8's upstart script always sets MIR_SOCKET to its old value when
  the session ends. If MIR_SOCKET wasn't set, then the post-stop script
  will still set MIR_SOCKET, setting it to "". Mir should interpret this
  as if MIR_SOCKET were unset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1634508/+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 1617865] Re: [regression] Accidental libmircommon.so.6 ABI break in Mir 0.24.0: mir::dispatch::ReadableFd* moved version stanzas

2016-10-12 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.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/1617865

Title:
  [regression] Accidental libmircommon.so.6 ABI break in Mir 0.24.0:
  mir::dispatch::ReadableFd* moved version stanzas

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Accidental libmircommon.so.6 ABI break in Mir 0.24:
  mir::dispatch::ReadableFd* moved version stanzas

  So for example server-mesa-x11.so.9 can no longer load because it expects 
from libmircommon.so.6:
 ZN3mir8dispatch10ReadableFdC1ENS_2FdERKSt8functionIFvvEE@MIR_COMMON_5.1
  but actually in Mir 0.24.0 that got duplicated and changed to:
 ZN3mir8dispatch10ReadableFdC1ENS_2FdERKSt8functionIFvvEE@MIR_COMMON_0.24

  https://bugs.launchpad.net/mir/+bug/1611804/comments/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1617865/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-10-10 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

2016-10-10 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1262116

Title:
  Nested servers prevent overlays or fullscreen bypass from working

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  Nested servers prevent fullscreen bypass from working.

  This would explain why nesting fullscreen clients is measurably slower than 
non-nesting:
  Direct (bypass) 2600
  Direct (bypass off) 2400
  Nested (bypass) 2450
  Nested (bypass off) 2330

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1262116/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-09-30 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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

2016-09-27 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: In Progress => 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/1626435

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-09-25 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-09-08 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1617435] Re: libmirserver-dev is missing a depends for uuid-dev

2016-09-01 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.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/1617435

Title:
  libmirserver-dev is missing a depends for uuid-dev

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From building qtmir:

  In file included from 
/«BUILDDIR»/qtmir-0.4.8+15.04.20160826.1/src/modules/Unity/Application/mirsurfacemanager.cpp:41:0:
  /usr/include/mirserver/mir/shell/persistent_surface_store.h:25:23: fatal 
error: uuid/uuid.h: No such file or directory
   #include 
 ^

  libmirserver-dev should depend on uuid-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1617435/+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 1617435] Re: libmirserver-dev is missing a depends for uuid-dev

2016-08-29 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1617435

Title:
  libmirserver-dev is missing a depends for uuid-dev

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From building qtmir:

  In file included from 
/«BUILDDIR»/qtmir-0.4.8+15.04.20160826.1/src/modules/Unity/Application/mirsurfacemanager.cpp:41:0:
  /usr/include/mirserver/mir/shell/persistent_surface_store.h:25:23: fatal 
error: uuid/uuid.h: No such file or directory
   #include 
 ^

  libmirserver-dev should depend on uuid-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1617435/+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 1420581] Re: [enhancement] Add support for full OpenGL compositing

2016-08-03 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.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/1420581

Title:
  [enhancement] Add support for full OpenGL compositing

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  [enhancement] Add support for full OpenGL compositing.

  libmirserver/platform presently is only compiled to use the "ES"
  subset of OpenGL. This works for mobile devices and many desktop use
  cases but not all.

  There are a few pending reasons to compile for full OpenGL on desktop
  (and/or switch at runtime!):

  1. Qt only understands full OpenGL on desktop. Presently we use a hack
  that makes it call ES functions pretending to be full OpenGL, but this
  hack will fail when we support non-Mesa desktop drivers.

  2. Proprietary desktop drivers sometimes don't support ES.

  3. Proprietary desktop drivers often (last I checked) perform better
  with full OpenGL. Not sure why, probably just driver maturity.

  4. There is evidence (bug 1420574) that ES doesn't work at all on some
  older chipsets and regular OpenGL is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1420581/+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 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay

2016-07-19 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1601810

Title:
  ftbfs in linking libmir-test-assist.a in xenial+overlay and
  yakkety+overlay

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::DescribeTo(std::ostream*) const':
  /usr/include/gmock/gmock-matchers.h:242: undefined reference to 
`testing::internal::AnyMatcherImpl::DescribeTo(std::ostream*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(char const*, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::PolymorphicMatcher > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const'
  ../libmir-test-assist.a(mock_egl.cpp.o): In function 
`testing::internal::MatcherBase::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*) const':
  /usr/include/gmock/gmock-matchers.h:232: undefined reference to 
`testing::internal::AnyMatcherImpl::MatchAndExplain(std::tuple const&, 
testing::MatchResultListener*)

[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64

2016-07-19 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1579866

Title:
  Android graphics platform doesn't get packaged for arm64

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  The android platform code is currently gated to i386,amd64,armhf
  because the libhybris upstream dependency is gated to these
  architectures.

  Upstream recently added builds for arm64, so it would be good to
  enable our android code on this arch as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1579866/+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 1602966] Re: [regression] Zoom/contrast/negative desktop effects don't work any more in mir_proving_server (Mir shells don't receive the Super modifier any more)

2016-07-15 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   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/1602966

Title:
  [regression] Zoom/contrast/negative desktop effects don't work any
  more in mir_proving_server (Mir shells don't receive the Super
  modifier any more)

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  [regression] Zoom/contrast/negative desktop effects don't work any
  more in mir_proving_server on lp:mir.

  That's Super + mousewheel,C,N respectively

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1602966/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-07-08 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: Fix Released => 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/1556205

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556205/+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 1590765] Re: OSK flickers and buttons are sometimes invisble

2016-06-30 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.24.0

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

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

Title:
  OSK flickers and buttons are sometimes invisble

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often
  invisible (pressing white part will refresh it and buttons are visible
  again) and OSK flickers a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+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 1590099] Re: Need to support pointer confinement

2016-06-27 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.24.0

** Changed in: mir
   Status: In Progress => 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/1590099

Title:
  Need to support pointer confinement

Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1590099/+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 1590099] Re: Need to support pointer confimenet

2016-06-08 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.24.0

** Changed in: mir
   Status: In Progress => 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/1590099

Title:
  Need to support pointer confimenet

Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1590099/+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 1584784] Re: Using NBS, X apps under Unity8 need interaction to start in pocket-desktop

2016-06-04 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.24.0

** Changed in: mir
   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/1584784

Title:
  Using NBS, X apps under Unity8 need interaction to start in pocket-
  desktop

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  In Progress
Status in Mir 0.24 series:
  Fix Committed
Status in QtMir:
  Invalid
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  With Mir 0.23.0, X apps under Unity8 need some interaction to get the
  applications to start. 0.23.0 is blocked pending fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1584784/+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 1447886] Re: mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface, and can lead to windows 1px wide and unrecoverable.

2016-04-29 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.23.0

** Changed in: mir
   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/1447886

Title:
  mir_demo_server(_minimal): Window movement/resizing stops responding
  when the cursor leaves the surface, and can lead to windows 1px wide
  and unrecoverable.

Status in Mir:
  Fix Committed
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  mir_demo_server(_minimal) version 0.13 and later: Window
  movement/resizing stops responding when the cursor leaves the surface.

  If you move or resize a surface with Alt+(button1/button3) then it's
  very easy to get the shell into a state where the window stops
  responding to movement/resizing and even becomes unrecoverable (window
  1px wide).

  Essentially the problem is the shell is only looking at the current
  cursor position and doesn't do anything if it's outside of the
  surface. This is frustrating as waiving the mouse around a bit it's
  very easy to reach this situation.

  It should be looking at the gesture as a whole and only doing position
  checking at the start of the move/resize gesture (ie. mouse button
  down). Thereafter the gesture should be continuous until the button is
  released, regardless of whether the cursor is still inside the
  surface/titlebar. You will find this is how all real desktops work,
  and mir_proving_server tries to too. Surfaces should always "own"
  input regardless of cursor position, just so long as the gesture
  (mouse down) began on that surface.

  The "unrecoverable" bit: This happens if you resize a surface too
  small/thin and it becomes impossible to resize it bigger again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1447886/+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 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

2016-04-28 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.23.0

** Changed in: mir
   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/1575192

Title:
  Mir-on-X11 breaks mir_proving_server resize logic

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_proving_server&
  $ mir_demo_client_egltriangle

  Alt+drag with middle mouse button

  Expect: client is resized
  Actual: Nothing happens

  A bit of investigation shows that the mouse-button-down event isn't
  being received. (The movement event is received.)

  (The problem doesn't occur on other platforms.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1575192/+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 1576260] Re: Can't VT switch from mir_demo_server

2016-04-28 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.23.0

** Changed in: mir
   Status: New => 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/1576260

Title:
  Can't VT switch from mir_demo_server

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in mir source package in Xenial:
  New

Bug description:
  I can't VT switch from mir_demo_server. This turns out to be an issue
  that occurred in 16.04 where /dev/console no longer works with VT
  switching. Using /dev/tty0 work. See bug 1566073 for associated change
  in LightDM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1576260/+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 1553549] Re: Mir crashes with useless backtrace when mg::Platform methods throw

2016-04-26 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.23.0

** Changed in: mir
   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/1553549

Title:
  Mir crashes with useless backtrace when mg::Platform methods throw

Status in Mir:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  So, the problem that causes unity-system-compositor to crash (rather
  than fail to start with a helpful error message) is that when methods
  on mg::Platform throw we unload the platform DSO before exception
  processing is completed, so libstdc++ goes merrily along trying to
  execute code that is longer mapped.

  Original report below:
  unity-system-co[5574]: segfault at 7f8056ee2490 ip 7f805c592c3b sp 
7fffd6b871a0 error 4 in libstdc++.so.6.0.21[7f805c506000+172000]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Mar  5 19:03:39 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1455894356
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1102]
     Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 
970M] [1462:1102]
  InstallationDate: Installed on 2015-02-25 (374 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 11 --to-dm-fd 20 --vt 8
  ProcCwd: /
  ProcEnviron:

  SegvAnalysis:
   Segfault happened at: 0x7f805c592c3b:mov(%rsi),%rax
   PC (0x7f805c592c3b) ok
   source "(%rsi)" (0x7f8056ee2490) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2015-11-03 (122 days ago)
  UserGroups:

  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.17.5-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1553549/+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 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened

2016-04-20 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1563287

Title:
  [regression] [OTA-10] Spread animation stutters badly with only a few
  apps opened

Status in Canonical System Image:
  Confirmed
Status in libhybris:
  New
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Triaged
Status in Mir 0.21 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:
  Regression in OTA-10:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+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 1528109] Re: [regression] Cursor mostly does not move at all in response to slow mouse movement, but then sometimes jumps

2016-04-18 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1528109

Title:
  [regression] Cursor mostly does not move at all in response to slow
  mouse movement, but then sometimes jumps

Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.20 series:
  Triaged
Status in Mir 0.21 series:
  Triaged
Status in libinput package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Starting in Mir 0.18 I've noticed with a Microsoft Intellimouse
  Explorer 3.0 that moving it slowly does not move the cursor. That is
  unless I move it slowly for a while, and then the cursor jumps.

  Xorg and Mir 0.17 do not have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1528109/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-04-15 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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

2016-04-11 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1549701

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

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.21 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random

2016-03-22 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1536662

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

Status in Mir:
  Fix Committed
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 1342092] Re: mir_acceptance_tests & mir_unit_tests dump core files (even when everything passes)

2016-03-21 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   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/1342092

Title:
  mir_acceptance_tests & mir_unit_tests dump core files (even when
  everything passes)

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  :~$ mir_acceptance_tests 
  Running main() from command_line_server_configuration.cpp
  [==] Running 116 tests from 29 test cases.
  [--] Global test environment set-up.
  [--] 6 tests from ServerConfigurationWrapping
  [ RUN  ] 
ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type
  [   OK ] 
ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type (1 ms)
  [ RUN  ] 
ServerConfigurationWrapping.can_override_surface_coordinator_methods
  [   OK ] 
ServerConfigurationWrapping.can_override_surface_coordinator_methods (0 ms)
  [ RUN  ] 
ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache
  [   OK ] 
ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache (0 ms)
  [ RUN  ] 
ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type
  [   OK ] 
ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type (1 ms)
  [ RUN  ] 
ServerConfigurationWrapping.can_override_session_coordinator_methods
  [   OK ] 
ServerConfigurationWrapping.can_override_session_coordinator_methods (0 ms)
  [ RUN  ] 
ServerConfigurationWrapping.returns_same_session_coordinator_from_cache
  [   OK ] 
ServerConfigurationWrapping.returns_same_session_coordinator_from_cache (0 ms)
  [--] 6 tests from ServerConfigurationWrapping (2 ms total)

  [--] 17 tests from ClientLibrary
  [ RUN  ] ClientLibrary.client_library_connects_and_disconnects
  [   OK ] ClientLibrary.client_library_connects_and_disconnects (3 ms)
  [ RUN  ] ClientLibrary.synchronous_connection
  [   OK ] ClientLibrary.synchronous_connection (1 ms)
  [ RUN  ] ClientLibrary.creates_surface
  [   OK ] ClientLibrary.creates_surface (1 ms)
  [ RUN  ] ClientLibrary.can_set_surface_types
  [   OK ] ClientLibrary.can_set_surface_types (24 ms)
  [ RUN  ] ClientLibrary.can_set_surface_state
  [   OK ] ClientLibrary.can_set_surface_state (22 ms)
  [ RUN  ] ClientLibrary.receives_surface_dpi_value
  [   OK ] ClientLibrary.receives_surface_dpi_value (1 ms)
  [ RUN  ] ClientLibrary.surface_scanout_flag_toggles
  [   OK ] ClientLibrary.surface_scanout_flag_toggles (2 ms)
  [ RUN  ] ClientLibrary.gets_buffer_dimensions
  [   OK ] ClientLibrary.gets_buffer_dimensions (1 ms)
  [ RUN  ] ClientLibrary.creates_multiple_surfaces
  [   OK ] ClientLibrary.creates_multiple_surfaces (3 ms)
  [ RUN  ] ClientLibrary.client_library_accesses_and_advances_buffers
  [   OK ] ClientLibrary.client_library_accesses_and_advances_buffers (4 ms)
  [ RUN  ] ClientLibrary.fully_synchronous_client
  [   OK ] ClientLibrary.fully_synchronous_client (0 ms)
  [ RUN  ] ClientLibrary.highly_threaded_client
  [   OK ] ClientLibrary.highly_threaded_client (6 ms)
  [ RUN  ] ClientLibrary.accesses_platform_package
  [   OK ] ClientLibrary.accesses_platform_package (1 ms)
  [ RUN  ] ClientLibrary.accesses_display_info
  [   OK ] ClientLibrary.accesses_display_info (1 ms)
  [ RUN  ] ClientLibrary.connect_errors_handled
  [   OK ] ClientLibrary.connect_errors_handled (0 ms)
  [ RUN  ] ClientLibrary.connect_errors_dont_blow_up
  [   OK ] ClientLibrary.connect_errors_dont_blow_up (1 ms)
  [ RUN  ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly
  [   OK ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly (76 ms)
  [--] 17 tests from ClientLibrary (149 ms total)

  [--] 2 tests from ClientLibraryThread
  [ RUN  ] ClientLibraryThread.HandlesNoSignals
  [   OK ] ClientLibraryThread.HandlesNoSignals (11 ms)
  [ RUN  ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling
  [   OK ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling (7 
ms)
  [ RUN  ] ClientLibraryThread.HandlesNoSignals
  [--] 2 tests from ClientLibraryThread (18 ms total)

  [--] 2 tests from ClientSurfaceEvents
  [ RUN  ] ClientSurfaceEvents.surface_receives_state_events
  [   OK ] ClientSurfaceEvents.surface_receives_state_events (18 ms)
  [ RUN  ] ClientSurfaceEvents.client_can_query_current_orientation
  [   OK ] ClientSurfaceEvents.client_can_query_current_orientation (5 ms)
  [--] 2 tests from ClientSurfaceEvents (23 ms total)

  [--] 3 tests from CustomInputDispatcher
  [ RUN  ] CustomInputDispatcher.receives_input
  [   OK ]

[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'

2016-03-19 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.21.0

** Changed in: mir
   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/1554635

Title:
  Importing contacts trigger unity restart - Mir crashed with exception
  'failed to add sync point to command buffer'

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps:

  Open Dekko or Telegram
  Go to import contacts
  Make sure you have a substantial amount of contacts in your phone
  When the contacts app is open in import mode, select all contact and press 
Tick

  Expected:
  contacts are imported succesfully

  Actual:
  Unity restarts (goes back to the ubuntu dot screen) and the contact import is 
interrupted

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+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

2016-03-15 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.21.0

** Changed in: mir
   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/1536662

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

Status in Mir:
  Fix Committed
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 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random

2016-02-25 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.21.0

** Changed in: mir
   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/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:
  Won't Fix
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 1549226] Re: On arale; top panel drop down menu is semi-transparent and items are unreadable

2016-02-25 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.21.0

** Changed in: mir
   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/1549226

Title:
  On arale; top panel drop down menu is semi-transparent and items are
  unreadable

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  current build number: 255
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  The drop down menu is semi transparent and the items are difficult to
  read or almost invisible (eg sound controls - picture attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549226/+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 1480164] Re: [regression] Mir is holding buffers much longer than it used to.

2016-02-24 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.21.0

** Changed in: mir
   Status: Fix Released => 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/1480164

Title:
  [regression] Mir is holding buffers much longer than it used to.

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir is holding buffers much longer than it used to. You can see from
  this bespoke logging that it's now holding each buffer from the client
  for a full frame even though the compositor itself only holds it for
  less than a millisecond (the render time):

  [1438332770.923332] mirserver: 0x7f66bc0030b0: compositor acquired 
0x7f66bc0039f0
  [1438332770.923444] mirserver: 0x7f66bc0030b0: compositor release1 
0x7f66bc0039f0
  [1438332770.923454] mirserver: 0x7f66bc0030b0: compositor release2 
0x7f66bc0039f0
  [1438332770.939927] mirserver: 0x7f66bc0030b0: compositor release3 
0x7f66bc0039f0
  [1438332770.939966] mirserver: 0x7f66bc0030b0: compositor release4 
0x7f66bc0039f0
  [1438332770.940011] mirserver: 0x7f66bc0030b0: compositor acquired 
0x7f66bc006990
  [1438332770.940117] mirserver: 0x7f66bc0030b0: compositor release1 
0x7f66bc006990
  [1438332770.940127] mirserver: 0x7f66bc0030b0: compositor release2 
0x7f66bc006990
  [1438332770.956487] mirserver: 0x7f66bc0030b0: compositor release3 
0x7f66bc006990
  [1438332770.956507] mirserver: 0x7f66bc0030b0: compositor release4 
0x7f66bc006990

  The issue appears to have been introduced in:
  
  revno: 2323 [merge]
  author: Daniel van Vugt 
  committer: Tarmac
  branch nick: development-branch
  timestamp: Tue 2015-02-17 08:19:29 +
  message:
Fix the multi-monitor frame sync logic to support high speed
compositors (tm) which only need to hold buffers very briefly
(introduced in r2183). (LP: #1420678)

Both the multi-monitor frame sync logic and the optimization of r2183
behave correctly independently. It's only when combined that they start
to interfere with each other. But we'd very much like to keep both. Fixes: 
https://bugs.launchpad.net/bugs/1420678.

Approved by Chris Halse Rogers, PS Jenkins bot, Alan Griffiths.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1480164/+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

72 matches

Mail list logo