[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

[fcole90]

** This bug is no longer a duplicate of bug 1632772
   Login option 'GNOME on Wayland' does not start from LightDM

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[fcole90]

Ok, mine is 1695872

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

[Dariusz Gadomski]

Patch proposal for Artful.

** Patch added: "cups_2.2.3-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+attachment/4889375/+files/cups_2.2.3-1ubuntu1.debdiff

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1695900] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I was doing a normal upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 10:14:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-14 (110 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1695900/+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 1673533] Re: Presentation chains should support various Vulkan presentation modes

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Presentation chains should support various Vulkan presentation modes

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

Bug description:
  Specifically, Vulkan modes:

  mir_present_mode_immediate, //same as VK_PRESENT_MODE_IMMEDIATE_KHR
  mir_present_mode_mailbox, //same as VK_PRESENT_MODE_MAILBOX_KHR
  mir_present_mode_fifo, //same as VK_PRESENT_MODE_FIFO_KHR
  mir_present_mode_fifo_relaxed, //same as VK_PRESENT_MODE_FIFO_RELAXED_KHR

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1673533/+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 1695876] [NEW] German Documentation file displays incorrect CUPS version

[Ivy Alexander]

Public bug reported:

The /doc/de/index.html.in file in the package source has an incorrect
version number written into a header instead of using '@CUPS_VERSION@'
to populate this file as in the other languages' version of the same
file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
having the wrong version once CUPS is installed:

...

  
CUPS 2.0.2
...

instead of:

...

  
CUPS @CUPS_VERSION@
...

resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  German Documentation file displays incorrect CUPS version

Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791

-- 
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 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

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 1677239] Re: mir_demo_standalone_render_overlays fails to link

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1677239/+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 393585] Re: Focused/unfocused selection colors are confusingly similar

[Matthew Paul Thomas]

ubuntu-ux was a dummy project for the purpose of getting the opinion of
Canonical’s platform design team. That team no longer exists. My view on
this, however, is the same as it was when I commented in April 2010.

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

Title:
  Focused/unfocused selection colors are confusingly similar

Status in One Hundred Papercuts:
  Invalid
Status in community-themes package in Ubuntu:
  Opinion
Status in nautilus package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Opinion

Bug description:
  Problem occurs with: Ambiance, Radiance, Clearlooks, DarkRoom,  Dust, 
Elementary, Glossy, Human, Human-Clearlooks
  Does not occur with: New Wave

  For example, open a Nautilus window and select an icon.  Switch focus
  to the desktop by clicking on it.  The window is not active but the
  icon in it retains the "selected items" color.  It appears as though
  it is still selected and that it can be modified by keyboard
  shortcuts.  By clicking on an icon on the desktop it changes color to
  be selected an now it appears that two items are selected.

  Several times I've deleted things by accident due to this, especially
  when I was new to GNOME.  I would have several windows open with items
  selected.  I would see the item I want selected and hit the delete key
  to remove it, only to realize that I had some other window focused
  where I had deleted something else.

  In Windows selected items in unfocused windows turn gray.  I think it
  also adds another visual clue as to what window is focused besides
  just the title bar.

  Firefox and Thunderbird deliver the behavior I expect (probably
  because they are only faux GTK apps).  Select some text in Firefox and
  then focus to another window and you will see that the selected text
  turns gray, indicating it is not active.  Try that in gedit or evince
  and the text will remain blue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/393585/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

Status in mir package in Ubuntu:
  In Progress
Status in mir source package in Xenial:
  In Progress
Status in mir source package in Yakkety:
  In Progress
Status in mir source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Keyboard layout not applied on the shell

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

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 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Those mir_demo_client_* which default to fullscreen now
  ignore the size parameter (-s WIDTHxHEIGHT)

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

Bug description:
  Those mir_demo_client_* which default to fullscreen now ignore the
  size parameter (-s WIDTHxHEIGHT), instead choosing to stay in
  fullscreen mode.

  This applies to mirvanity too, making testing of windowed client
  latency difficult.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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 1662455] Re: Mir graphics platform ABI broke in series 0.26 but sonames never changed

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir graphics platform ABI broke in series 0.26 but sonames never
  changed

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

Bug description:
  An ABI break in series 0.26 arose from changes to:
  include/platform/mir/graphics/display_configuration.h
  include/platform/mir/graphics/graphic_buffer_allocator.h

  However the applicable ABI(s) never changed from series 0.25:
  MIR_SERVER_GRAPHICS_PLATFORM_ABI
  MIRPLATFORM_ABI

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662455/+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 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

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

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

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

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

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1662942] Re: libmirclient-dev missing build depndency on libmircore-dev

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  libmirclient-dev missing build depndency on libmircore-dev

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

Bug description:
  There is a broken build-dep in the Mir 0.26 packaging.

  Dialogue taken from IRC revealing the details:

   alan_g, when I include mir_toolkit header files in chromium I get 
this error:
   In file included from 
/usr/include/mirclient/mir_toolkit/events/event.h:90:
   #include "mir_toolkit/mir_input_device_types.h"
   and apt-file search doesn't return anything
   I wonder what I am missing
   is this a bug or there's a lib I should have installed?
   locate also cant find this file
   that's in libmircore-dev.  What do you get from $ pkg-config 
--cflags mirclient
   $ pkg-config --cflags mirclient
   -pthread -I/usr/include/mirclient -I/usr/include/mircookie 
-I/usr/include/mircore
   that lib was missing :)
   Then /usr/include/mircore/mir_toolkit/mir_input_device_types.h ought 
to be there
   :s
   ok installing mircore-dev fixed that
   apt-file should return it though :/
   Hmm. $ apt depends libmirclient-dev doesn't list libmircore-dev - 
sounds like a bug
   yes, when I ran apt-get build-dep libmirclient-dev mircore-dev was 
not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662942/+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 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Latency for fullscreen interval 0 clients (e.g. games and
  benchmarks) increased with the introduction of nested passthrough

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency
  than interval 1 nested fullscreen clients.

  I've reproduced this a couple of times and it is concerning:

  Mir 0.25:
     Interval 0: 81ms  <-- regression
     Interval 1: 64ms  <-- improvement

  Mir 0.24:
 Interval 0: 70ms
 Interval 1: 96ms

  It's the obvious green spike in this chart:
  
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive

  Although this regression appears to be resolved in the 0.26 series
  (lp:mir) it's serious enough that we should look into finding what the
  cause was so that Mir 0.25.1 can get the same fix.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
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 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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released

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 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

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 1661704] Re: mir_window_request_persistent_id_sync seg faults when called twice

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_window_request_persistent_id_sync seg faults when called twice

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

Bug description:
  Thread 1 "gtk3-widget-fac" received signal SIGSEGV, Segmentation fault.
  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  67  ../nptl/pthread_mutex_lock.c: No such file or directory.
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x737c1003 in __gthread_mutex_lock () at 
/usr/include/x86_64-linux-gnu/c++/6/bits/gthr-default.h:748
  #2  std::mutex::lock() (this=0x0) at /usr/include/c++/6/bits/std_mutex.h:103
  #3  std::unique_lock::lock() (this=0x7fffbad0) at 
/usr/include/c++/6/bits/std_mutex.h:267
  #4  std::unique_lock::unique_lock(std::mutex&) () at 
/usr/include/c++/6/bits/std_mutex.h:197
  #5  MirWaitHandle::wait_for_all() (this=0x0) at 
./src/client/mir_wait_handle.cpp:51
  #6  0x737d0623 in mir_surface_request_persistent_id_sync 
(surface=) at ./src/client/mir_surface_api.cpp:1266
  #7  0x77b7137a in gdk_mir_display_convert_selection 
(display=0x557ad010, requestor=0x56235af0, selection=0x45, target=0x52, 
time=34494073)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gdk/mir/gdkmirdisplay.c:845
  #8  0x77aee577 in gdk_selection_convert (requestor=0x56235af0, 
selection=0x45, target=0x52, time=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gdk/gdkselection.c:273
  #9  0x773f675e in gtk_selection_convert (widget=0x55fcaf80, 
selection=0x45, target=0x52, time_=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkselection.c:1162
  #10 0x77537a04 in gtk_clipboard_real_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:1023
  #11 0x7753793f in gtk_clipboard_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:994
  #12 0x774471be in gtk_text_buffer_paste_clipboard 
(buffer=0x5594b2f0, clipboard=0x55fb7690, override_location=0x0, 
default_editable=1)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextbuffer.c:3871
  #13 0x7747f7e6 in gtk_text_view_paste_clipboard 
(text_view=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextview.c:7156
  #14 0x762b4fe7 in g_cclosure_marshal_VOID__VOID 
(closure=0x55cac020, return_value=0x0, n_param_values=1, 
param_values=0x5616a050, invocation_hint=0x7fffc0e0,
  marshal_data=0x7747f78d ) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gmarshal.c:875
  #15 0x762b24a4 in g_type_class_meta_marshal (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0, marshal_data=0x410)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:997
  #16 0x762b1dc0 in g_closure_invoke (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:804
  #17 0x762d0532 in signal_emit_unlocked_R (node=0x55cac050, 
detail=0, instance=0x55ad28b0, emission_return=0x0, 
instance_and_params=0x5616a050)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3673
  #18 0x762ce32d in g_signal_emitv (instance_and_params=0x5616a050, 
signal_id=450, detail=0, return_value=0x0) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3129
  #19 0x771a598c in gtk_binding_entry_activate (entry=0x55cc7c80, 
object=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:646
  #20 0x771a7193 in binding_activate (binding_set=0x55cac760, 
entries=0x562609c0, object=0x55ad28b0, is_release=0, 
unbound=0x7fffc2ec)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1446
  #21 0x771a7320 in gtk_bindings_activate_list (object=0x55ad28b0, 
entries=0x562609c0, is_release=0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1505
  #22 0x771a7594 in gtk_bindings_activate_event (object=0x55ad28b0, 
event=0x7fffdc002810) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1592
  #23 0x77505621 in gtk_widget_real_key_press_event 
(widget=0x55ad28b0, event=0x7fffdc002810) at 

[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1661498] Re: [regression] Segfault on detect_fd_leaks during acceptance tests (in DisplayConfiguration/{DisplayFormatSetting, DisplaySubpixelSetting})

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Segfault on detect_fd_leaks during acceptance tests (in
  DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting})

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

Bug description:
  I've seen this quite often in a silo... Not so often in CI.

  8: [ RUN ] 
DisplayConfiguration/DisplayFormatSetting.can_get_all_output_format/3
  8: [2017-02-03 01:05:22.479325] mirserver: Starting
  8: [2017-02-03 01:05:22.479397] mirserver: Selected driver: mir:stub-graphics 
(version 0.26.1)
  8: [2017-02-03 01:05:22.489793] mirserver: Using software cursor
  8: [2017-02-03 01:05:22.492185] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.1)
  8: [2017-02-03 01:05:22.492233] mirserver: Mir version 0.26.1
  8: [2017-02-03 01:05:22.492401] mirserver: Initial display configuration:
  8: [2017-02-03 01:05:22.492420] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.492430] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492436] mirserver: Power is on
  8: [2017-02-03 01:05:22.492444] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492451] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492457] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.492463] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.492468] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.492474] mirserver: Output 2: VGA disconnected
  8: [2017-02-03 01:05:22.492480] mirserver: Output 3: VGA connected, unused
  8: [2017-02-03 01:05:22.492486] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492491] mirserver: Power is off
  8: [2017-02-03 01:05:22.511553] mirserver: New display configuration:
  8: [2017-02-03 01:05:22.511586] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.511597] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.511603] mirserver: Power is on
  8: [2017-02-03 01:05:22.511611] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511618] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511624] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.511629] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.511635] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.511661] mirserver: New base display configuration:
  8: [2017-02-03 01:05:22.526758] mirserver: Stopping
  8: /<>/mir-0.26.1+17.04.20170203/tools/detect_fd_leaks.bash: line 
84: 27470 Segmentation fault  (core dumped) $@ 2>&1
  8:  27471 Done| detect_fd_leaks
   8/20 Test  #8: mir_acceptance_tests ..***Failed  
 81.66 sec
  Running main() from main.cpp
  Note: Google Test filter = -:
  [==] Running 517 tests from 86 test cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661498/+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 1626866] Re: [regression] 'make abi-check' fails to build

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] 'make abi-check' fails to build

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

Bug description:
  make abi-check fails to build:

  The GCC parameters:
/usr/bin/c++ -fdump-translation-unit -fkeep-inline-functions -c -x 
c++-header -fpermissive -w  -pthread -g -std=c++14 -Werror -Wall 
-fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC 
"/tmp/rTU25VRtKM/dump1.h"  -I/home/dan/bzr/mir/unbreak/include/common 
-I/home/dan/bzr/mir/unbreak/include/cookie -I/usr/include 
-I/home/dan/bzr/mir/unbreak/src/include/common 
-I/home/dan/bzr/mir/unbreak/build/src/protobuf 
-I/home/dan/bzr/mir/unbreak/include/platform 
-I/home/dan/bzr/mir/unbreak/src/include/platform

  In file included from /tmp/rTU25VRtKM/dump1.h:22:0:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: redefinition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~
  In file included from 
/home/dan/bzr/mir/unbreak/include/platform/mir/graphics/display_configuration.h:26:0,
   from /tmp/rTU25VRtKM/dump1.h:4:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: previous definition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1626866/+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 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Confirmed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1612012/+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 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-
  size array

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

Bug description:
  Mir FTBFS on zesty:

  In file included from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:27:0:
  
/home/dan/bzr/mir/trunk/tests/include/mir/test/doubles/mock_android_native_buffer.h:65:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::MockAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from /usr/include/android-23/hardware/gralloc.h:21,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/buffer.h:27,
   from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:20:
  /usr/include/android-23/cutils/native_handle.h:29:15: note: array member ‘int 
native_handle::data [0]’ declared here
   int data[0];/* numFds + numInts ints */
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1638774/+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 1661072] Re: [regression] Mir 0.26.0 - spinner loading animation, minimize, maximize too fast

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Mir 0.26.0 - spinner loading animation, minimize,
  maximize too fast

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate) using Mir 0.26.0

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Unity8 stutters constantly (like half frame rate) using
  Mir 0.26.0

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

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1660017] Re: EDID does not change when hotplugging a monitor

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

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 1628507] Re: Mir fails to cross-build with newer sbuild versions

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir fails to cross-build with newer sbuild versions

Status in Mir:
  Fix Released
Status in abi-compliance-checker package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When trying to cross-build Mir with sbuild version >= 0.68.0, the
  build fails with:

  sbuild-build-depends-mir-dummy:armhf : Depends: cmake-data:armhf but it is 
not installable
     Depends: abi-compliance-checker:armhf 
but it is not installable

  This is caused by a change ([1]) in the way sbuild installs build-deps
  for the package under build. Previously sbuild used the 'apt-get
  build-dep' command, but recent versions calculate the build-deps
  manually (using the Dpkg perl module) and install the -dummy package
  instead.

  This change isn't a problem in and of itself, but unfortunately
  uncovers a problem in the cmake-data and abi-compliance-checker
  packages. In particular, the two packages are not multi-arch ready and
  sbuild can't know that it needs to install their native/build (amd64)
  version, so it uses the host (armhf) version instead.

  The previous 'apt-get build-dep' way worked because APT is patched in
  ubuntu (but not in debian) to consider packages with architecture
  'all' as 'Multi-Arch: foreign' ([1],[2]). The Dpkg perl modules don't
  contain such a patch.

  [1] 
https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e227c8f3e10edd78bc71350380f559c481634b79
  [2] https://wiki.debian.org/Multiarch/CrossDependencies
  [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666772

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1628507/+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 1695887] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1552577, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889332/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889334/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889338/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889339/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889340/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889341/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1695887/+attachment/4889342/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  Automatic crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.5-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CrashReports:
   640:1000:121:6729614:2017-06-05 13:47:57.407585382 +0200:2017-06-05 
13:47:58.407585382 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:121:7583396:2017-06-05 13:47:08.600048065 +0200:2017-06-05 
13:47:09.600048065 +0200:/var/crash/_usr_bin_compiz.1000.crash
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun  5 13:47:29 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-04-29 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170428)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f30f299d909:mov(%rbx),%rdi
   PC (0x7f30f299d909) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695887/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Jeremy Bicha]

I don't think the open source NVIDIA graphics drivers support GNOME on
Wayland in Ubuntu 16.04 LTS.

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  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 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1664760/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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 1663197] Re: mir_window_spec_set_cursor_name() doesn't trigger mir::scene::SurfaceObserver::cursor_image_set_to

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_window_spec_set_cursor_name() doesn't trigger
  mir::scene::SurfaceObserver::cursor_image_set_to

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

Bug description:
  qtmir relies on mir::scene::SurfaceObserver::cursor_image_set_to being
  called whenever the surface cursor name changes.

  qtubuntu still uses the deprecated API
  "mir_cursor_configuration_from_name() && mir_window_configure_cursor".
  With that, mir::scene::SurfaceObserver::cursor_image_set_to does get
  called in qtmir.

  But once qtubuntu uses the new Mir API for that[1],
  "mir_window_spec_set_cursor_name() && mir_window_apply_spec()", the
  SurfaceObserver in qtmir no longer gets notified

  
  [1] - 
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1663197/+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 1673534] Re: Need an extension for GBM buffers to replace mir_buffer_get_buffer_package()

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Need an extension for GBM buffers to replace
  mir_buffer_get_buffer_package()

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

Bug description:
  We need for Mesa EGL

  typedef struct MirExtensionGbmBufferV2
  {
  MirConnectionAllocateBufferGbm allocate_buffer_gbm;
  MirConnectionAllocateBufferGbmSync allocate_buffer_gbm_sync;
  MirBufferIsGbmImportable is_gbm_importable;
  MirBufferGbmFd fd;
  MirBufferGbmStride stride;
  MirBufferGbmFormat format;
  MirBufferGbmFlags flags;
  MirBufferGbmAge age;
  } MirExtensionGbmBufferV2;

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset

[Launchpad Bug Tracker]

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

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Setting MirWindowSpec parameters always causes window's input_region
  to be reset

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Triaged
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've made a quick demo to reproduce this:

  https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref
  /cursor-mask-demo

  
  1. launch any mir demo server
  2. launch the above demo
  3. press 'c' to set the cursor of the window, cursor should become a cross 
over the window.
  4. press 'm' to set the input region as a subset of the window. You can 
observe the input region by moving the cursor over the window, cursor will be a 
cross inside the specified region. You can click too, will cause client to 
print "click"
  5. press 'c' again.

  Expected result
  no change

  Actual result
  Input region of surface appears to be reset - cursor is a cross over the 
entire window.

  
  I've noticed this behaviour only after this update to QtUbuntu:
  
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646
  so suspect a bug with the new api only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1662997] Re: [regression] mirscreencast hangs during screencast creation

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] mirscreencast hangs during screencast creation

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

Bug description:
  hmm, sometime between 3980 and tip, mirscreencast started hanging
  during screencast creation. Bound to generate some complaints.

  Thread 1 "mirscreencast.b" received signal SIGTSTP, Stopped (user).
  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  185   ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or 
directory.
  (gdb) bt
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x77449afc in 
std::condition_variable::wait(std::unique_lock&) ()
 from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x77ea131a in 
std::condition_variable::wait 
>(std::unique_lock &, MirWaitHandle::) 
(this=0x555da6d0, __lock=..., __p=...)
  at /usr/include/c++/6/condition_variable:99
  #3  0x77ea1061 in MirWaitHandle::wait_for_all (this=0x555da6a8)
  at /home/kdub/source/mir/mir/src/client/mir_wait_handle.cpp:53
  #4  0x77ee5420 in (anonymous namespace)::create_screencast 
(spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:38
  #5  0x77ee5631 in mir_screencast_create_sync (spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:90
  #6  0x55591430 in main (argc=3, argv=0x7fffe478)
  at /home/kdub/source/mir/mir/src/utils/screencast.cpp:568

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662997/+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 1666372] Re: Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Nested servers (Unity8) periodically stutter (half frame rate) with
  Mir 0.26.1

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested servers periodically stutter (half frame rate) with Mir 0.26.1

  On an old laptop, it's about half the time stuttering and half the
  time smooth.

  On a fast desktop, it only stutters occasionally like when a large
  blur is active.

  It seems the problem is Mir's predictive bypass optimization
  conflicting with the new client-side vsync optimization. Both are
  correct and desirable when used alone, but when used together they
  conflict, presumably because the former requires perfect vsync phase
  and the latter lacks correct vsync phase (which is still an exercise
  for later).

  A workaround to get more reliably smooth frame rates is to create a file:
/etc/lightdm/lightdm.conf.d/foo.conf
  with contents:

  [Seat:*]
  unity-compositor-command=/usr/sbin/unity-system-compositor --composite-delay=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666372/+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 1673533] Re: Presentation chains should support various Vulkan presentation modes

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Presentation chains should support various Vulkan presentation modes

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

Bug description:
  Specifically, Vulkan modes:

  mir_present_mode_immediate, //same as VK_PRESENT_MODE_IMMEDIATE_KHR
  mir_present_mode_mailbox, //same as VK_PRESENT_MODE_MAILBOX_KHR
  mir_present_mode_fifo, //same as VK_PRESENT_MODE_FIFO_KHR
  mir_present_mode_fifo_relaxed, //same as VK_PRESENT_MODE_FIFO_RELAXED_KHR

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  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 1667645] Re: If the only surface in a session cannot take focus the server crashes

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Fix Released

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)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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 Released
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 1695884] [NEW] usb probing malforms Epson TM-T70 label printer output

[Dariusz Gadomski]

Public bug reported:

CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
0x0202) which is used outside CUPS (via usblp driver).

No matter whether the printer is set up as a CUPS raw printer or it's
not used via CUPS (but rather via a device node under usblp control) the
formatting is broken on the printed out labels: the orientation is
different from what had been set, the fonts differ.

After blacklisting the printer in the quirks file all the problems were
gone.

My assumption is that this printer should be blacklisted by default.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- usb probing malforms TM-T70 output
+ usb probing malforms Epson TM-T70 output

** Summary changed:

- usb probing malforms Epson TM-T70 output
+ usb probing malforms Epson TM-T70 label printer output

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1552577] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

** Tags added: artful

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1552577/+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 1695900] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Srikanth Anantharam]

Public bug reported:

I was doing a normal upgrade and this happened

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Jun  5 10:14:07 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-02-14 (110 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I was doing a normal upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 10:14:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-14 (110 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1695900/+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 1695296] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  got the at startup, but does seem to create problems.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Jun  2 17:41:10 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Setting up libcuda1-375 (375.66-0ubuntu0.17.04.1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-17 (16 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695296/+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 1695872] [NEW] GNOME on Wayland session could not be started from lightdm

[fcole90]

Public bug reported:

GNOME on Wayland session could not be started from lightdm

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun  5 11:23:22 2017
InstallationDate: Installed on 2016-09-09 (268 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1695866] [NEW] Keyboard shortcuts take a very long time to show effect.

[Harsh Vardhan]

Public bug reported:

It takes nearly ten to thirty seconds for the terminal to show up after I 
press, [ctrl] + [alt] + [T], or for that matter any other keyboard shortcut 
like [Print-Screen].
This isn't the case with toggle keys like caps-lock or num-lock or even 
super-key + .

** This issue isn't reflected when the guest account is used. **


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun  5 14:13:33 2017
InstallationDate: Installed on 2017-04-09 (56 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Description changed:

  It takes nearly ten to thirty seconds for the terminal to show up after I 
press, [ctrl] + [alt] + [T], or for that matter any other keyboard shortcut 
like [Print-Screen].
  This isn't the case with toggle keys like caps-lock or num-lock or even 
super-key + .
  
+ ** This issue isn't reflected when the guest account is used. **
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun  5 14:13:33 2017
  InstallationDate: Installed on 2017-04-09 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  JournalErrors:
-  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
-Users in the 'systemd-journal' group can see all messages. Pass -q to
-turn off this notice.
-  No journal files were opened due to insufficient permissions.
+  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
+    Users in the 'systemd-journal' group can see all messages. Pass -q to
+    turn off this notice.
+  No journal files were opened due to insufficient permissions.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  It takes nearly ten to thirty seconds for the terminal to show up after I 
press, [ctrl] + [alt] + [T], or for that matter any other keyboard shortcut 
like [Print-Screen].
  This isn't the case with toggle keys like caps-lock or num-lock or even 
super-key + .
  
  ** This issue isn't reflected when the guest account is used. **
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun  5 14:13:33 2017
  InstallationDate: Installed on 2017-04-09 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Keyboard shortcuts take a very long time to show effect.

Status in dbus package in Ubuntu:
  New

Bug description:
  It takes nearly ten to thirty seconds for the terminal to show up after I 
press, [ctrl] + [alt] + [T], or for that matter any other keyboard shortcut 
like [Print-Screen].
  This isn't the case with toggle keys like caps-lock or num-lock or even 
super-key + .

  ** This issue isn't reflected when the guest account is used. **

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1695864] [NEW] lightdm does not respect tap to click from GNOME/libinput settings

[fcole90]

Public bug reported:

When using lightdm as display manager and GNOME Shell as DE, with
libinput installed, lightdm doesn't respect the GNOME setting for tap to
click.

This setting is correctly respected under gdm3.

This setting is also correctly respected when using lightdm without
libinput installed.

The synaptic driver is installed as well, if it was of any interest.

Also, this seems to be fixed (or always enabled) in 17.10, as I could
use tap to click in lightdm with the Daily ISO (with GNOME DE
installed).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun  5 11:04:14 2017
InstallationDate: Installed on 2016-09-09 (268 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

** Summary changed:

- lightdm does not respect tap to click
+ lightdm does not respect tap to click from GNOME/libinput

** Summary changed:

- lightdm does not respect tap to click from GNOME/libinput
+ lightdm does not respect tap to click from GNOME/libinput settings

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

Title:
  lightdm does not respect tap to click from GNOME/libinput settings

Status in lightdm package in Ubuntu:
  New

Bug description:
  When using lightdm as display manager and GNOME Shell as DE, with
  libinput installed, lightdm doesn't respect the GNOME setting for tap
  to click.

  This setting is correctly respected under gdm3.

  This setting is also correctly respected when using lightdm without
  libinput installed.

  The synaptic driver is installed as well, if it was of any interest.

  Also, this seems to be fixed (or always enabled) in 17.10, as I could
  use tap to click in lightdm with the Daily ISO (with GNOME DE
  installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:04:14 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

hi Daniel,

Fantastic! I is a really good news for me.

thanks,
Mao


On Mon, Jun 5, 2017 at 12:46 PM, Daniel Axtens 
wrote:

> Hi,
>
> I can get xorg working if I do these 2 things:
>
> 1) Edit memory with gdb to add "pci:" to bus id. This is what the kernel
> patch should do. I will test the patch soon, I am just waiting for the
> kernel to build.
>
> 2) Install this /etc/X11/xorg.conf:
>
> Section "ServerFlags"
> Option "AutoAddGPU" "off"
> EndSection
>
> Section "Device"
> Identifier "dja"
> Driver "modesetting"
> BusID "pci:0007:161:0:0"
> EndSection
>
>
> This does 2 things:
>  - AutoAddGPU prevents the card from falsely being marked as GPU. I am not
> yet fully sure why that is required.
>
>  - The Device section then specifies the busid and driver specifically.
> This forces the driver to be loaded correctly.
>
> This Xorg configuration should not be required in the long term. There
> are obviously still some bugs to be fixed. But, I wanted to let you know
> that progress was being made and give you good news.
>
> Attached is a screenshot of Xeyes over KVM.
>
> Regards,
> Daniel
>
> ** Attachment added: "xeyes.png"
>https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/
> 1691991/+attachment/4889182/+files/xeyes.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691991
>
> Title:
>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>   [sudo] password for ubuntu:
>
>   X.Org X Server 1.18.4
>   Release Date: 2016-07-19
>   X Protocol Version 11, Revision 0
>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
> earlycon=pl011,mmio,0x602B console=tty0
>   Build Date: 02 November 2016  10:05:28PM
>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
> http://www.ubuntu.com/support)
>   Current version of pixman: 0.33.6
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
>   Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   pci id for fd 10: 19e5:1711, driver (null)
>   EGL_MESA_drm_image required.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>   (EE)
>   (EE) Segmentation fault at address 0xa0
>   (EE)
>   Fatal server error:
>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>   (EE)
>   (EE)
>   Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>for help.
>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
>   (EE)
>   (EE) Server terminated with error (1). Closing log file.
>   Aborted (core dumped)
>   ubuntu@ubuntu:~$
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) 

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791

-- 
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:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  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 1673534] Re: Need an extension for GBM buffers to replace mir_buffer_get_buffer_package()

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Need an extension for GBM buffers to replace
  mir_buffer_get_buffer_package()

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

Bug description:
  We need for Mesa EGL

  typedef struct MirExtensionGbmBufferV2
  {
  MirConnectionAllocateBufferGbm allocate_buffer_gbm;
  MirConnectionAllocateBufferGbmSync allocate_buffer_gbm_sync;
  MirBufferIsGbmImportable is_gbm_importable;
  MirBufferGbmFd fd;
  MirBufferGbmStride stride;
  MirBufferGbmFormat format;
  MirBufferGbmFlags flags;
  MirBufferGbmAge age;
  } MirExtensionGbmBufferV2;

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1673534/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791

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

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

Status in mir package in Ubuntu:
  In Progress
Status in mir source package in Xenial:
  In Progress
Status in mir source package in Yakkety:
  In Progress
Status in mir source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Confirmed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1612012/+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 1573572] Re: Virtual output is not removed when screencast client disappears

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

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

Title:
  Virtual output is not removed when screencast client disappears

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.22 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  With WiFi Display we're using the screencast API from our management
  service aethercast to create an virtual display which is then used by
  Unity 8. If aethercast crashes the virtual output seems to stay as
  Unity 8 never switches back from the virtual touchpad its displaying
  since the virtual output is use.

  When aethercast terminates the screencast connection Unity 8 switches
  correctly back to the phone interface.

  I suspect this is reproducible with mirscreencast too.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

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

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

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
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 1591328] Re: Pointer/cursor input lag in unity8 session

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

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

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

Status in Canonical System Image:
  Fix Released
Status in libhybris:
  Invalid
Status in Mir:
  Fix Released
Status in Mir 0.20 series:
  Fix Released
Status in Mir 0.21 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released
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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

-- 
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 in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  Fix Released
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

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/canonical-devices-system-image/+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 1528109] Re: [regression] Cursor mostly does not move at all in response to slow mouse movement, but then sometimes jumps

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

-- 
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 Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.20 series:
  Won't Fix
Status in Mir 0.21 series:
  Fix Committed
Status in libinput package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+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 1695880] [NEW] package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Rossi Ivanova]

Public bug reported:

Could not install 'gstreamer1.0-alsa'

59.1549:package is in a very bad inconsistent state; you should
reinstall it before attempting configuration

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Mon Jun  5 20:15:16 2017
DuplicateSignature:
 package:gstreamer1.0-alsa:i386:1.8.3-1ubuntu0.2
 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
 dpkg: error processing package gstreamer1.0-alsa:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-06-05 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gst-plugins-base1.0
Title: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  Could not install 'gstreamer1.0-alsa'

  59.1549:package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 20:15:16 2017
  DuplicateSignature:
   package:gstreamer1.0-alsa:i386:1.8.3-1ubuntu0.2
   Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
   dpkg: error processing package gstreamer1.0-alsa:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1695880/+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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[Jeremy Bicha]

fcole90, please file a new bug for your issue.

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1666372] Re: Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Nested servers (Unity8) periodically stutter (half frame rate) with
  Mir 0.26.1

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested servers periodically stutter (half frame rate) with Mir 0.26.1

  On an old laptop, it's about half the time stuttering and half the
  time smooth.

  On a fast desktop, it only stutters occasionally like when a large
  blur is active.

  It seems the problem is Mir's predictive bypass optimization
  conflicting with the new client-side vsync optimization. Both are
  correct and desirable when used alone, but when used together they
  conflict, presumably because the former requires perfect vsync phase
  and the latter lacks correct vsync phase (which is still an exercise
  for later).

  A workaround to get more reliably smooth frame rates is to create a file:
/etc/lightdm/lightdm.conf.d/foo.conf
  with contents:

  [Seat:*]
  unity-compositor-command=/usr/sbin/unity-system-compositor --composite-delay=0

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

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 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] Those mir_demo_client_* which default to fullscreen now
  ignore the size parameter (-s WIDTHxHEIGHT)

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

Bug description:
  Those mir_demo_client_* which default to fullscreen now ignore the
  size parameter (-s WIDTHxHEIGHT), instead choosing to stay in
  fullscreen mode.

  This applies to mirvanity too, making testing of windowed client
  latency difficult.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644075/+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 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

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

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661163/+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 1626866] Re: [regression] 'make abi-check' fails to build

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] 'make abi-check' fails to build

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

Bug description:
  make abi-check fails to build:

  The GCC parameters:
/usr/bin/c++ -fdump-translation-unit -fkeep-inline-functions -c -x 
c++-header -fpermissive -w  -pthread -g -std=c++14 -Werror -Wall 
-fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC 
"/tmp/rTU25VRtKM/dump1.h"  -I/home/dan/bzr/mir/unbreak/include/common 
-I/home/dan/bzr/mir/unbreak/include/cookie -I/usr/include 
-I/home/dan/bzr/mir/unbreak/src/include/common 
-I/home/dan/bzr/mir/unbreak/build/src/protobuf 
-I/home/dan/bzr/mir/unbreak/include/platform 
-I/home/dan/bzr/mir/unbreak/src/include/platform

  In file included from /tmp/rTU25VRtKM/dump1.h:22:0:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: redefinition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~
  In file included from 
/home/dan/bzr/mir/unbreak/include/platform/mir/graphics/display_configuration.h:26:0,
   from /tmp/rTU25VRtKM/dump1.h:4:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: previous definition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1626866/+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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset

[Launchpad Bug Tracker]

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

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Setting MirWindowSpec parameters always causes window's input_region
  to be reset

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Triaged
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've made a quick demo to reproduce this:

  https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref
  /cursor-mask-demo

  
  1. launch any mir demo server
  2. launch the above demo
  3. press 'c' to set the cursor of the window, cursor should become a cross 
over the window.
  4. press 'm' to set the input region as a subset of the window. You can 
observe the input region by moving the cursor over the window, cursor will be a 
cross inside the specified region. You can click too, will cause client to 
print "click"
  5. press 'c' again.

  Expected result
  no change

  Actual result
  Input region of surface appears to be reset - cursor is a cross over the 
entire window.

  
  I've noticed this behaviour only after this update to QtUbuntu:
  
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646
  so suspect a bug with the new api only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1644189] Re: Shell doesn't know when base display config has changed

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1628507] Re: Mir fails to cross-build with newer sbuild versions

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Mir fails to cross-build with newer sbuild versions

Status in Mir:
  Fix Released
Status in abi-compliance-checker package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When trying to cross-build Mir with sbuild version >= 0.68.0, the
  build fails with:

  sbuild-build-depends-mir-dummy:armhf : Depends: cmake-data:armhf but it is 
not installable
     Depends: abi-compliance-checker:armhf 
but it is not installable

  This is caused by a change ([1]) in the way sbuild installs build-deps
  for the package under build. Previously sbuild used the 'apt-get
  build-dep' command, but recent versions calculate the build-deps
  manually (using the Dpkg perl module) and install the -dummy package
  instead.

  This change isn't a problem in and of itself, but unfortunately
  uncovers a problem in the cmake-data and abi-compliance-checker
  packages. In particular, the two packages are not multi-arch ready and
  sbuild can't know that it needs to install their native/build (amd64)
  version, so it uses the host (armhf) version instead.

  The previous 'apt-get build-dep' way worked because APT is patched in
  ubuntu (but not in debian) to consider packages with architecture
  'all' as 'Multi-Arch: foreign' ([1],[2]). The Dpkg perl modules don't
  contain such a patch.

  [1] 
https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e227c8f3e10edd78bc71350380f559c481634b79
  [2] https://wiki.debian.org/Multiarch/CrossDependencies
  [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666772

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

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

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791

-- 
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:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  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 1662455] Re: Mir graphics platform ABI broke in series 0.26 but sonames never changed

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Mir graphics platform ABI broke in series 0.26 but sonames never
  changed

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

Bug description:
  An ABI break in series 0.26 arose from changes to:
  include/platform/mir/graphics/display_configuration.h
  include/platform/mir/graphics/graphic_buffer_allocator.h

  However the applicable ABI(s) never changed from series 0.25:
  MIR_SERVER_GRAPHICS_PLATFORM_ABI
  MIRPLATFORM_ABI

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662455/+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 1662997] Re: [regression] mirscreencast hangs during screencast creation

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] mirscreencast hangs during screencast creation

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

Bug description:
  hmm, sometime between 3980 and tip, mirscreencast started hanging
  during screencast creation. Bound to generate some complaints.

  Thread 1 "mirscreencast.b" received signal SIGTSTP, Stopped (user).
  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  185   ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or 
directory.
  (gdb) bt
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x77449afc in 
std::condition_variable::wait(std::unique_lock&) ()
 from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x77ea131a in 
std::condition_variable::wait 
>(std::unique_lock &, MirWaitHandle::) 
(this=0x555da6d0, __lock=..., __p=...)
  at /usr/include/c++/6/condition_variable:99
  #3  0x77ea1061 in MirWaitHandle::wait_for_all (this=0x555da6a8)
  at /home/kdub/source/mir/mir/src/client/mir_wait_handle.cpp:53
  #4  0x77ee5420 in (anonymous namespace)::create_screencast 
(spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:38
  #5  0x77ee5631 in mir_screencast_create_sync (spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:90
  #6  0x55591430 in main (argc=3, argv=0x7fffe478)
  at /home/kdub/source/mir/mir/src/utils/screencast.cpp:568

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662997/+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 1661704] Re: mir_window_request_persistent_id_sync seg faults when called twice

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  mir_window_request_persistent_id_sync seg faults when called twice

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

Bug description:
  Thread 1 "gtk3-widget-fac" received signal SIGSEGV, Segmentation fault.
  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  67  ../nptl/pthread_mutex_lock.c: No such file or directory.
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x737c1003 in __gthread_mutex_lock () at 
/usr/include/x86_64-linux-gnu/c++/6/bits/gthr-default.h:748
  #2  std::mutex::lock() (this=0x0) at /usr/include/c++/6/bits/std_mutex.h:103
  #3  std::unique_lock::lock() (this=0x7fffbad0) at 
/usr/include/c++/6/bits/std_mutex.h:267
  #4  std::unique_lock::unique_lock(std::mutex&) () at 
/usr/include/c++/6/bits/std_mutex.h:197
  #5  MirWaitHandle::wait_for_all() (this=0x0) at 
./src/client/mir_wait_handle.cpp:51
  #6  0x737d0623 in mir_surface_request_persistent_id_sync 
(surface=) at ./src/client/mir_surface_api.cpp:1266
  #7  0x77b7137a in gdk_mir_display_convert_selection 
(display=0x557ad010, requestor=0x56235af0, selection=0x45, target=0x52, 
time=34494073)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gdk/mir/gdkmirdisplay.c:845
  #8  0x77aee577 in gdk_selection_convert (requestor=0x56235af0, 
selection=0x45, target=0x52, time=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gdk/gdkselection.c:273
  #9  0x773f675e in gtk_selection_convert (widget=0x55fcaf80, 
selection=0x45, target=0x52, time_=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkselection.c:1162
  #10 0x77537a04 in gtk_clipboard_real_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:1023
  #11 0x7753793f in gtk_clipboard_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:994
  #12 0x774471be in gtk_text_buffer_paste_clipboard 
(buffer=0x5594b2f0, clipboard=0x55fb7690, override_location=0x0, 
default_editable=1)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextbuffer.c:3871
  #13 0x7747f7e6 in gtk_text_view_paste_clipboard 
(text_view=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextview.c:7156
  #14 0x762b4fe7 in g_cclosure_marshal_VOID__VOID 
(closure=0x55cac020, return_value=0x0, n_param_values=1, 
param_values=0x5616a050, invocation_hint=0x7fffc0e0,
  marshal_data=0x7747f78d ) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gmarshal.c:875
  #15 0x762b24a4 in g_type_class_meta_marshal (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0, marshal_data=0x410)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:997
  #16 0x762b1dc0 in g_closure_invoke (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:804
  #17 0x762d0532 in signal_emit_unlocked_R (node=0x55cac050, 
detail=0, instance=0x55ad28b0, emission_return=0x0, 
instance_and_params=0x5616a050)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3673
  #18 0x762ce32d in g_signal_emitv (instance_and_params=0x5616a050, 
signal_id=450, detail=0, return_value=0x0) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3129
  #19 0x771a598c in gtk_binding_entry_activate (entry=0x55cc7c80, 
object=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:646
  #20 0x771a7193 in binding_activate (binding_set=0x55cac760, 
entries=0x562609c0, object=0x55ad28b0, is_release=0, 
unbound=0x7fffc2ec)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1446
  #21 0x771a7320 in gtk_bindings_activate_list (object=0x55ad28b0, 
entries=0x562609c0, is_release=0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1505
  #22 0x771a7594 in gtk_bindings_activate_event (object=0x55ad28b0, 
event=0x7fffdc002810) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1592
  #23 0x77505621 in gtk_widget_real_key_press_event 
(widget=0x55ad28b0, 

[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released

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 1667645] Re: If the only surface in a session cannot take focus the server crashes

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Fix Released

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 1660017] Re: EDID does not change when hotplugging a monitor

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  EDID does not change when hotplugging a monitor

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

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1660017/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate) using Mir 0.26.0

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] Unity8 stutters constantly (like half frame rate) using
  Mir 0.26.0

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

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661498] Re: [regression] Segfault on detect_fd_leaks during acceptance tests (in DisplayConfiguration/{DisplayFormatSetting, DisplaySubpixelSetting})

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] Segfault on detect_fd_leaks during acceptance tests (in
  DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting})

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

Bug description:
  I've seen this quite often in a silo... Not so often in CI.

  8: [ RUN ] 
DisplayConfiguration/DisplayFormatSetting.can_get_all_output_format/3
  8: [2017-02-03 01:05:22.479325] mirserver: Starting
  8: [2017-02-03 01:05:22.479397] mirserver: Selected driver: mir:stub-graphics 
(version 0.26.1)
  8: [2017-02-03 01:05:22.489793] mirserver: Using software cursor
  8: [2017-02-03 01:05:22.492185] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.1)
  8: [2017-02-03 01:05:22.492233] mirserver: Mir version 0.26.1
  8: [2017-02-03 01:05:22.492401] mirserver: Initial display configuration:
  8: [2017-02-03 01:05:22.492420] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.492430] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492436] mirserver: Power is on
  8: [2017-02-03 01:05:22.492444] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492451] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492457] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.492463] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.492468] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.492474] mirserver: Output 2: VGA disconnected
  8: [2017-02-03 01:05:22.492480] mirserver: Output 3: VGA connected, unused
  8: [2017-02-03 01:05:22.492486] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492491] mirserver: Power is off
  8: [2017-02-03 01:05:22.511553] mirserver: New display configuration:
  8: [2017-02-03 01:05:22.511586] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.511597] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.511603] mirserver: Power is on
  8: [2017-02-03 01:05:22.511611] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511618] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511624] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.511629] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.511635] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.511661] mirserver: New base display configuration:
  8: [2017-02-03 01:05:22.526758] mirserver: Stopping
  8: /<>/mir-0.26.1+17.04.20170203/tools/detect_fd_leaks.bash: line 
84: 27470 Segmentation fault  (core dumped) $@ 2>&1
  8:  27471 Done| detect_fd_leaks
   8/20 Test  #8: mir_acceptance_tests ..***Failed  
 81.66 sec
  Running main() from main.cpp
  Note: Google Test filter = -:
  [==] Running 517 tests from 86 test cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661498/+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 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-
  size array

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

Bug description:
  Mir FTBFS on zesty:

  In file included from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:27:0:
  
/home/dan/bzr/mir/trunk/tests/include/mir/test/doubles/mock_android_native_buffer.h:65:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::MockAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from /usr/include/android-23/hardware/gralloc.h:21,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/buffer.h:27,
   from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:20:
  /usr/include/android-23/cutils/native_handle.h:29:15: note: array member ‘int 
native_handle::data [0]’ declared here
   int data[0];/* numFds + numInts ints */
 ^

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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 1645372] Re: support display scaling slider in unity8

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

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 1663197] Re: mir_window_spec_set_cursor_name() doesn't trigger mir::scene::SurfaceObserver::cursor_image_set_to

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  mir_window_spec_set_cursor_name() doesn't trigger
  mir::scene::SurfaceObserver::cursor_image_set_to

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

Bug description:
  qtmir relies on mir::scene::SurfaceObserver::cursor_image_set_to being
  called whenever the surface cursor name changes.

  qtubuntu still uses the deprecated API
  "mir_cursor_configuration_from_name() && mir_window_configure_cursor".
  With that, mir::scene::SurfaceObserver::cursor_image_set_to does get
  called in qtmir.

  But once qtubuntu uses the new Mir API for that[1],
  "mir_window_spec_set_cursor_name() && mir_window_apply_spec()", the
  SurfaceObserver in qtmir no longer gets notified

  
  [1] - 
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1663197/+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 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] Latency for fullscreen interval 0 clients (e.g. games and
  benchmarks) increased with the introduction of nested passthrough

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency
  than interval 1 nested fullscreen clients.

  I've reproduced this a couple of times and it is concerning:

  Mir 0.25:
     Interval 0: 81ms  <-- regression
     Interval 1: 64ms  <-- improvement

  Mir 0.24:
 Interval 0: 70ms
 Interval 1: 96ms

  It's the obvious green spike in this chart:
  
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive

  Although this regression appears to be resolved in the 0.26 series
  (lp:mir) it's serious enough that we should look into finding what the
  cause was so that Mir 0.25.1 can get the same fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651638/+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 1662942] Re: libmirclient-dev missing build depndency on libmircore-dev

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  libmirclient-dev missing build depndency on libmircore-dev

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

Bug description:
  There is a broken build-dep in the Mir 0.26 packaging.

  Dialogue taken from IRC revealing the details:

   alan_g, when I include mir_toolkit header files in chromium I get 
this error:
   In file included from 
/usr/include/mirclient/mir_toolkit/events/event.h:90:
   #include "mir_toolkit/mir_input_device_types.h"
   and apt-file search doesn't return anything
   I wonder what I am missing
   is this a bug or there's a lib I should have installed?
   locate also cant find this file
   that's in libmircore-dev.  What do you get from $ pkg-config 
--cflags mirclient
   $ pkg-config --cflags mirclient
   -pthread -I/usr/include/mirclient -I/usr/include/mircookie 
-I/usr/include/mircore
   that lib was missing :)
   Then /usr/include/mircore/mir_toolkit/mir_input_device_types.h ought 
to be there
   :s
   ok installing mircore-dev fixed that
   apt-file should return it though :/
   Hmm. $ apt depends libmirclient-dev doesn't list libmircore-dev - 
sounds like a bug
   yes, when I ran apt-get build-dep libmirclient-dev mircore-dev was 
not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662942/+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 1661072] Re: [regression] Mir 0.26.0 - spinner loading animation, minimize, maximize too fast

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  [regression] Mir 0.26.0 - spinner loading animation, minimize,
  maximize too fast

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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 Released
Status in mir package in Ubuntu:
  Fix Released
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 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

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

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

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

Title:
  Keyboard layout not applied on the shell

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

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 1576260] Re: Can't VT switch from mir_demo_server (any more)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

-- 
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 (any more)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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