[Touch-packages] [Bug 1698248] Re: avahi-daemon constantly registers/withdraws IPv6 address record

[Trent Lloyd]

https://github.com/lathiat/avahi/issues/41

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

Title:
  avahi-daemon constantly registers/withdraws IPv6 address record

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 17.04, have avahi-daemon 0.6.32-1ubuntu1 installed.

  If I check syslog, every 5 - 10 seconds there is a set of messages
  like message like:

  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.

  etc..., which is clearly not normal. (This was also tested on a brand
  new installation of Ubuntu 17.04, same issue). Attached is a small
  sample of my syslog file.

  This also seems to impact other programs that use an ipv6 connection.
  For example, Google Chrome - half the time I try to load a webpage I
  get "your connection was interrupted; a network change was detected".
  After about a half-second, it proceeds to load the webpage, although
  often doesn't load it properly. This does not affect all websites
  (likely only those that support ipv6).

  See https://askubuntu.com/questions/905866/new-ubuntu-17-04-problem-
  your-connection-was-interrupted for other people experiencing the same
  bug, both in avahi and Chrome.

  Disabling ipv6 seems to work as a temporary workaround.

  I am also not sure whether this bug is caused by avahi, or whether it
  is just experiencing the most "symptoms".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Jun 15 20:42:19 2017
  InstallationDate: Installed on 2017-06-10 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698248] Re: avahi-daemon constantly registers/withdraws IPv6 address record

[Trent Lloyd]

This is known upstream but not yet solved, working on it I have a theory

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

** Bug watch added: github.com/lathiat/avahi/issues #41
   https://github.com/lathiat/avahi/issues/41

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

Title:
  avahi-daemon constantly registers/withdraws IPv6 address record

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 17.04, have avahi-daemon 0.6.32-1ubuntu1 installed.

  If I check syslog, every 5 - 10 seconds there is a set of messages
  like message like:

  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.

  etc..., which is clearly not normal. (This was also tested on a brand
  new installation of Ubuntu 17.04, same issue). Attached is a small
  sample of my syslog file.

  This also seems to impact other programs that use an ipv6 connection.
  For example, Google Chrome - half the time I try to load a webpage I
  get "your connection was interrupted; a network change was detected".
  After about a half-second, it proceeds to load the webpage, although
  often doesn't load it properly. This does not affect all websites
  (likely only those that support ipv6).

  See https://askubuntu.com/questions/905866/new-ubuntu-17-04-problem-
  your-connection-was-interrupted for other people experiencing the same
  bug, both in avahi and Chrome.

  Disabling ipv6 seems to work as a temporary workaround.

  I am also not sure whether this bug is caused by avahi, or whether it
  is just experiencing the most "symptoms".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Jun 15 20:42:19 2017
  InstallationDate: Installed on 2017-06-10 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698282] [NEW] Totem uses dramatically higher CPU than any other video player

[Daniel van Vugt]

Public bug reported:

Totem uses dramatically higher CPU than any other video player.

Example 1: software playback under Gnome Shell Wayland:

totem: 120% (but drops to 80% in Unity7)
mplayer: 40%
vlc: 40%
[all are using ffmpeg for decoding]

Example 2: hardware-accelerated playback under Gnome Shell Xorg:

totem: 11%
gst-play-1.0: 3%
[both are using gstreamer-vaapi for decoding]

Since the decoding libraries are theoretically the same it sounds like
totem's performance problems might be in its rendering path.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libgstreamer1.0-0 1.12.0-2
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
Date: Fri Jun 16 12:57:11 2017
InstallationDate: Installed on 2017-05-03 (44 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug artful performance

** Package changed: gstreamer1.0 (Ubuntu) => totem (Ubuntu)

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

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

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

Title:
  Totem uses dramatically higher CPU than any other video player

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  New

Bug description:
  Totem uses dramatically higher CPU than any other video player.

  Example 1: software playback under Gnome Shell Wayland:

  totem: 120% (but drops to 80% in Unity7)
  mplayer: 40%
  vlc: 40%
  [all are using ffmpeg for decoding]

  Example 2: hardware-accelerated playback under Gnome Shell Xorg:

  totem: 11%
  gst-play-1.0: 3%
  [both are using gstreamer-vaapi for decoding]

  Since the decoding libraries are theoretically the same it sounds like
  totem's performance problems might be in its rendering path.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  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
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: Critical => High

** Changed in: oem-priority/xenial
   Importance: Critical => High

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Hi Mao,

I have done more work on the HiSilicon board. I have talked with the SEG
team and our conclusion is that the hardware is not compliant with the
specification, but that it is appropriate to include a workaround in
software.

I have developed a patch that adds a workaround or 'quirk' to the kernel
specifically for the hisilicon graphics card and the hisilicon PCI
bridge. It tests for the card and the bridge on the development board. I
think it might be acceptable for upstream. With this, X
autoconfiguration works.

Please could you ask the HiSilicon people if there are other boards or
parts with different PCI IDs that should be included in this fixup?

Regards,
Daniel

-- 
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) 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

-- 
Mailing list: https://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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Evan Ney]

I have had the same issue with my Lenovo Thinkpad T440s. I thought it
was random at first but have figured out how to consistently reproduce
the problem. The mouse will jump across the screen when you tap or click
in two different locations on the left side of the trackpad very quickly
in succession. The mouse jumps in the direction of the second click
relative to the first click, so if you use a middle finger to scroll and
then an index finger to click, this typically causes the mouse to jump
towards the bottom left. I think Juan is correct in that the issue comes
from the driver, possibly because the kernel takes over using psmouse.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://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 1698263] [NEW] Screen flashing on and off

[Paul Oglesby]

Public bug reported:

My screen is consistently going black about 2 times persecond.
There is nothing wrong with the connection as it works ok with windows 10 nd at 
the opening of the Ubuntu progran

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jun 16 13:15:29 2017
DistUpgraded: 2017-05-06 15:17:38,466 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f920]
InstallationDate: Installed on 2016-02-03 (499 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: TOSHIBA Satellite Pro L50-B
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=431ee126-87db-4913-a3b4-0c925c8d667b ro plymouth:debug drm.debug=0xe
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-05-06 (40 days ago)
dmi.bios.date: 05/05/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd05/05/2014:svnTOSHIBA:pnSatelliteProL50-B:pvrPSKT5A-001001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite Pro L50-B
dmi.product.version: PSKT5A-001001
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Sat Jun  3 17:42:48 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Screen flashing on and off

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen is consistently going black about 2 times persecond.
  There is nothing wrong with the connection as it works ok with windows 10 nd 
at the opening of the Ubuntu progran

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jun 16 13:15:29 2017
  DistUpgraded: 2017-05-06 15:17:38,466 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f920]
  InstallationDate: Installed on 2016-02-03 (499 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite Pro L50-B
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=431ee126-87db-4913-a3b4-0c925c8d667b ro plymouth:debug drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-05-06 (40 days ago)
  

[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

[Daniel van Vugt]

Minor correction - Mir 0.27.0 is not released yet :)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1698248] [NEW] avahi-daemon constantly registers/withdraws IPv6 address record

[Dan Ursu]

Public bug reported:

Running Ubuntu 17.04, have avahi-daemon 0.6.32-1ubuntu1 installed.

If I check syslog, every 5 - 10 seconds there is a set of messages like
message like:

Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.*.
Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.*.
Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.
Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.

etc..., which is clearly not normal. (This was also tested on a brand
new installation of Ubuntu 17.04, same issue). Attached is a small
sample of my syslog file.

This also seems to impact other programs that use an ipv6 connection.
For example, Google Chrome - half the time I try to load a webpage I get
"your connection was interrupted; a network change was detected". After
about a half-second, it proceeds to load the webpage, although often
doesn't load it properly. This does not affect all websites (likely only
those that support ipv6).

See https://askubuntu.com/questions/905866/new-ubuntu-17-04-problem-
your-connection-was-interrupted for other people experiencing the same
bug, both in avahi and Chrome.

Disabling ipv6 seems to work as a temporary workaround.

I am also not sure whether this bug is caused by avahi, or whether it is
just experiencing the most "symptoms".

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: avahi-daemon 0.6.32-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Thu Jun 15 20:42:19 2017
InstallationDate: Installed on 2017-06-10 (5 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "syslog snippet"
   https://bugs.launchpad.net/bugs/1698248/+attachment/4896799/+files/syslog

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

Title:
  avahi-daemon constantly registers/withdraws IPv6 address record

Status in avahi package in Ubuntu:
  New

Bug description:
  Running Ubuntu 17.04, have avahi-daemon 0.6.32-1ubuntu1 installed.

  If I check syslog, every 5 - 10 seconds there is a set of messages
  like message like:

  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.*.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.
  Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 
2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.

  etc..., which is clearly not normal. (This was also tested on a brand
  new installation of Ubuntu 17.04, same issue). Attached is a small
  sample of my syslog file.

  This also seems to impact other programs that use an ipv6 connection.
  For example, Google Chrome - half the time I try to load a webpage I
  get "your connection was interrupted; a network change was detected".
  After about a half-second, it proceeds to load the webpage, although
  often doesn't load it properly. This does not affect all websites
  (likely only those that support ipv6).

  See https://askubuntu.com/questions/905866/new-ubuntu-17-04-problem-
  your-connection-was-interrupted for other people experiencing the same
  bug, both in avahi and Chrome.

  Disabling ipv6 seems to work as a temporary workaround.

  I am also not sure whether this bug is caused by avahi, or whether it
  is just experiencing the most "symptoms".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Jun 15 20:42:19 2017
  InstallationDate: Installed on 2017-06-10 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1698244] [NEW] package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet openssl nie jest gotowy do skonfigurowania nie można go skonfigurować (bieżący stan "half-inst

[robert]

Public bug reported:

package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet
openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować
(bieżący stan "half-installed")

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Jun 14 14:33:16 2017
ErrorMessage: pakiet openssl nie jest gotowy do skonfigurowania  nie można go 
skonfigurować (bieżący stan "half-installed")
InstallationDate: Installed on 2016-09-30 (258 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet 
openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować (bieżący 
stan "half-installed")
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1698244

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet
  openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować
  (bieżący stan "half-installed")

Status in openssl package in Ubuntu:
  New

Bug description:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet
  openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować
  (bieżący stan "half-installed")

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 14 14:33:16 2017
  ErrorMessage: pakiet openssl nie jest gotowy do skonfigurowania  nie można go 
skonfigurować (bieżący stan "half-installed")
  InstallationDate: Installed on 2016-09-30 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet 
openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować (bieżący 
stan "half-installed")
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690992] Update Released

[Brian Murray]

The verification of the Stable Release Update for network-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  fix for bug #1569649 left NetworkManager-wait-online disabled on some
  systems

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  [SRU Justification]
  While attempting to verify the usage of NetworkManager-wait-online.service in 
Ubuntu, I have discovered that while the packaging says that this service 
should be enabled (LP: #1569649), it is disabled on my machine.  I believe that 
users who have continuously upgraded their systems, including over pre-releases 
of Ubuntu, may have been left in the same situation, where 
NetworkManager-wait-online.service is inactive and their boot order is 
therefore unreliable.

  This disabled NetworkManager-wait-online due to lack of upgrade fix-up
  may explain other bug reports I've seen around NFS handling, where
  users continue to report that NFS is not correctly mounted at boot.

  Though late, a one-time upgrade fix-up is warranted so that users can
  have consistent handling of the network-online target.

  [Test case]
  1. On an affected system, run 'systemctl status NetworkManager-wait-online'.  
Observe that the unit is listed as disabled.
  2. Install network-manager from -proposed.
  3. Run 'systemctl status NetworkManager-wait-online' again and verify that 
the unit is no longer marked as disabled.
  4. Reboot and verify that the system still boots correctly.

  [Regression potential]
  Since NetworkManager-wait-online uses a 30 second timeout, services that 
depend on network-online.target should see at most a 30 second delay in 
startup.  There should be no functional regressions, only regressions in the 
speed of boot and only on systems where services have explicitly declared that 
they depend on the network and the network is not available at boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1690992/+subscriptions

-- 
Mailing list: https://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 1690992] Re: fix for bug #1569649 left NetworkManager-wait-online disabled on some systems

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.4.4-1ubuntu3.1

---
network-manager (1.4.4-1ubuntu3.1) zesty; urgency=medium

  * The fix for LP #1569649 did not re-enable NetworkManager-wait-online on
systems where it had been disabled in the packaging.  Include a one-time
postinst fixup to correct this.  LP: #1690992.

 -- Steve Langasek   Mon, 15 May 2017
21:35:15 -0700

** Changed in: network-manager (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  fix for bug #1569649 left NetworkManager-wait-online disabled on some
  systems

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  [SRU Justification]
  While attempting to verify the usage of NetworkManager-wait-online.service in 
Ubuntu, I have discovered that while the packaging says that this service 
should be enabled (LP: #1569649), it is disabled on my machine.  I believe that 
users who have continuously upgraded their systems, including over pre-releases 
of Ubuntu, may have been left in the same situation, where 
NetworkManager-wait-online.service is inactive and their boot order is 
therefore unreliable.

  This disabled NetworkManager-wait-online due to lack of upgrade fix-up
  may explain other bug reports I've seen around NFS handling, where
  users continue to report that NFS is not correctly mounted at boot.

  Though late, a one-time upgrade fix-up is warranted so that users can
  have consistent handling of the network-online target.

  [Test case]
  1. On an affected system, run 'systemctl status NetworkManager-wait-online'.  
Observe that the unit is listed as disabled.
  2. Install network-manager from -proposed.
  3. Run 'systemctl status NetworkManager-wait-online' again and verify that 
the unit is no longer marked as disabled.
  4. Reboot and verify that the system still boots correctly.

  [Regression potential]
  Since NetworkManager-wait-online uses a 30 second timeout, services that 
depend on network-online.target should see at most a 30 second delay in 
startup.  There should be no functional regressions, only regressions in the 
speed of boot and only on systems where services have explicitly declared that 
they depend on the network and the network is not available at boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1690992/+subscriptions

-- 
Mailing list: https://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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu7.3

---
multipath-tools (0.5.0+git1.656f8865-5ubuntu7.3) yakkety; urgency=medium

  * debian/initramfs/hooks: drop dm-emc (it hasn't existed since 2.6.27) and
add dm-queue-length: it's required on some hardware, such as XtremIO, where
it is the default path selector. (LP: #1673350)

 -- Mathieu Trudel-Lapierre   Tue, 28 Mar 2017
09:58:21 -0400

** Changed in: multipath-tools (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in multipath-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions

-- 
Mailing list: https://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 1375637] Re: Premature end of data in tag file line 247651 with libxml2

[Brian C]

I have seen a similar issue using 'yum check-update' on Ubunty Trusty
with libxml2=2.9.1+dfsg1-3ubuntu4.8 failing to parse the primary.xml.gz
index.

$ yum check-update

  
custom-repo: 
[### ] 
6900/6903
(process:1482): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing primary.xml error: attributes 
construct error


(process:1482): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing primary.xml error: Couldn't find end 
of Start Tag size line 238347


(process:1482): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing primary.xml error: Premature end of 
data in tag package line 238338


(process:1482): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing primary.xml error: Premature end of 
data in tag metadata line 2

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in 
yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 288, in user_main
errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 140, in main
result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 436, in doCommands
self._getTs(needTsRemove)
  File "/usr/lib/python2.7/dist-packages/yum/depsolve.py", line 101, in _getTs
self._getTsInfo(remove_only)
  File "/usr/lib/python2.7/dist-packages/yum/depsolve.py", line 112, in 
_getTsInfo
pkgSack = self.pkgSack
  File "/usr/lib/python2.7/dist-packages/yum/__init__.py", line 892, in 
pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.7/dist-packages/yum/__init__.py", line 673, in 
_getSacks
self.repos.populateSack(which=repos)
  File "/usr/lib/python2.7/dist-packages/yum/repos.py", line 294, in 
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.7/dist-packages/yum/yumRepo.py", line 190, in populate
dobj = repo_cache_function(xml, csum)
  File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 46, in 
getPrimary
self.repoid))
TypeError: Parsing primary.xml error: Specification mandate value for attribute 
archive

I have seen this a few times, but never took the time to dig into it
until recently.  What I found was the size of the primary.xml.gz file is
what seems to be causing the failure.  If (size of file in bytes)/(8192
bytes) has a remainder of 1 byte this failure will occur. Basically, in
the case of "yum check-update", if the last read (that returns more than
0 bytes) on the primary.xml.gz file ONLY contains a single null
character it fails.

strace excerpt (with the primary.xml.gz as fd 5):

read(5, "\0", 8192) = 1
read(5, "", 8191)   = 0

After the above it fails immediately.

Updating libxml2 to v2.9.3+dfsg1-1ubuntu0.2 from the Ubuntu Xenial repos
seems to fix the problem, but that is not an acceptable solution in my
case because the Xenial package brings in some other dependencies that I
cannot update to.

Any chance someone could fix this issue for Ubuntu Trusty?

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

Title:
  Premature end of data in tag file line 247651 with libxml2

Status in libxml2 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm getting the following behaviour of createrepo on Ubuntu 14.04.1
  LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and
  libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main).

  createrepo -g 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml
 \
-o 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/
  I/O error : No such file or directory

  (process:29830): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag package line 246828

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

[dann frazier]

I also tested this on a Qualcomm QDF2400 server, and the onboard
platform device was renamed to "enaqcom8070i0".

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

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

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

-- 
Mailing list: https://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 1676380] Re: Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures

[Brian Murray]

** Changed in: cups (Ubuntu)
Milestone: None => ubuntu-17.06

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

Title:
  Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script
  failures

Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Xenial:
  Confirmed

Bug description:
  Even though LP: #1642966 states that this is now fixed, the very
  update that was SRU'ed in that bug-report caused this error just now.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.10.0-13.15~16.04.2-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Mar 27 12:53:31 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for iP5200R: usb://Canon/iP5200R?serial=9045C0
  MachineType: Dell Inc. Precision 5520
  Papersize: a4
  PpdFiles: iP5200R: Canon iP5200R series - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1698181] Re: Switch to netplan renderer in Artful

[Robert C Jennings]

I just learned that this doesn't need changes in cloud-init, or
shouldn't.  I was target this to ubuntu-meta for ifupdate to be removed
from the seed in 17.10.  From that we should just switch to netplan like
magic. ;)  I'll let the owners of the other affected packages close
their own bits of this bug once they've evaluated the impact.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Switch to netplan renderer in Artful

Status in cloud-images:
  New
Status in cloud-init package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  Invalid
Status in maas package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu server ISOs are moving to netplan and cloud images must follow
  suit.  We are requesting that the default renderer in 17.10 be
  switched to netplan to be consistent across all cloud images and ISO
  installs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions

-- 
Mailing list: https://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 1698097] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Launchpad Bug Tracker]

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 10:05:06 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.6
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package libssl1.0.0:amd64 (--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-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 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/openssl/+bug/1698097/+subscriptions

-- 
Mailing list: https://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 1698161] Re: dont know

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  message says  Error: brokenCount>0'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog: /dev/sda7: clean, 443640/3522560 files, 2283299/14088704 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun 15 10:58:22 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2113]
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: Lenovo RV620/M82 [Mobility Radeon HD 3450/3470] [17aa:210f]
  InstallationDate: Installed on 2017-01-29 (136 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 276581U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d43a7390-ac5d-4958-b5e4-a8bcf8c0ff82 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VET95WW (3.25 )
  dmi.board.name: 276581U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VET95WW(3.25):bd10/10/2012:svnLENOVO:pn276581U:pvrThinkPadT400:rvnLENOVO:rn276581U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 276581U
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun 15 10:13:26 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16438 
   vendor LEN
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://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 1698173] [NEW] I can't change my desktop resolution in ubuntu 16.04

[Alamgir Hossain]

Public bug reported:

Hello Sir,

I am new in ubuntu. I can't change my desktop resolution as perfect.
It's only showing two resolutin which are 800x600 and 1024x768 . But I
need 1440x900 resolution for my desktop. What can I do? Please help.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jun 15 22:59:03 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:434e]
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=c3709d88-8d31-48ed-9b97-57a6f6c3d56a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: CNG4110H.86A.0012.2009.1223.1420
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41CN
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE82429-102
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrCNG4110H.86A.0012.2009.1223.1420:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41CN:rvrAAE82429-102:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jun 15 21:56:08 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output   VGA-1
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  I can't change my desktop resolution in ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello Sir,

  I am new in ubuntu. I can't change my desktop resolution as perfect.
  It's only showing two resolutin which are 800x600 and 1024x768 . But I
  need 1440x900 resolution for my desktop. What can I do? Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun 15 22:59:03 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics 
Controller [8086:434e]
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=c3709d88-8d31-48ed-9b97-57a6f6c3d56a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CNG4110H.86A.0012.2009.1223.1420
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41CN
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE82429-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCNG4110H.86A.0012.2009.1223.1420:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41CN:rvrAAE82429-102:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  

[Touch-packages] [Bug 1698171] [NEW] package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-i

[quentin]

Public bug reported:

je voudrais installer Minecraft pour y jouer, j'ai été sur un site qui
m'a demander de faire un commande sur "Terminal". je l'ai effectuer (
voici le site :https://doc.ubuntu-fr.org/minecraft) j'espère que vous
trouverez une solution très rapidement merci.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 minecraft-installer: Install
 openssl: Configure
 minecraft-installer: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Thu Jun 15 19:13:14 2017
ErrorMessage: le paquet openssl n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
InstallationDate: Installed on 2017-05-14 (31 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: openssl
Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet 
openssl n'est pas prêt pour la configuration  configuration impossible (état 
actuel « half-installed »)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1698171

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet
  openssl n'est pas prêt pour la configuration  configuration impossible
  (état actuel « half-installed »)

Status in openssl package in Ubuntu:
  New

Bug description:
  je voudrais installer Minecraft pour y jouer, j'ai été sur un site qui
  m'a demander de faire un commande sur "Terminal". je l'ai effectuer (
  voici le site :https://doc.ubuntu-fr.org/minecraft) j'espère que vous
  trouverez une solution très rapidement merci.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   minecraft-installer: Install
   openssl: Configure
   minecraft-installer: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Jun 15 19:13:14 2017
  ErrorMessage: le paquet openssl n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-05-14 (31 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: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet 
openssl n'est pas prêt pour la configuration  configuration impossible (état 
actuel « half-installed »)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 541595] Re: [Master] package failed to install/upgrade: package is already installed and configured

[SABITRA NANDAN DAS]

I found problem to install while updating Ubuntu os.

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

Title:
  [Master] package failed to install/upgrade: package is already
  installed and configured

Status in dpkg:
  New
Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: dpkg

  For yet unknown reasons packages fail to install with an error like:

  dpkg: error processing flashplugin-installer (--configure):
   package flashplugin-installer is already installed and configured

  without further error.
  This is a "one time" failure. Another run of the installation doesn't produce 
any error.

  Users reporting this error are also experiencing bug 545790 and bug
  545738 .

  ProblemType: Bug
  Architecture: i386
  Date: Fri Mar 19 00:09:06 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  Package: dpkg 1.15.5.6ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: dpkg
  Uname: Linux 2.6.32-16-generic i686

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

-- 
Mailing list: https://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 1698163] Re: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Julian Andres Klode]

This looks like a broken disk, following bug 63222.

** Package changed: apt (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 127

Status in Ubuntu:
  Incomplete

Bug description:
  Ubuntu does not shut down correctly and comes up with an error report
  every time I turn it off manually and turn my computer back on.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Thu Jun 15 06:28:05 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

[Steve Langasek]

** Changed in: systemd (Ubuntu Artful)
 Assignee: Canonical Foundations Team (canonical-foundations) => Balint 
Reczey (rbalint)

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

Title:
  softlockup DoS causes systemd-journald.service to abort with SIGABORT

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Artful:
  New

Bug description:
  I was running the new stress-ng softlockup stressor and observed that
  systemd-journald gets killed with an abort and this corrupts the
  systemd journal.

  How to reproduce:

  git clone git://kernel.ubuntu.com/cking/stress-ng
  cd stress-ng
  make clean; make

  sudo ./stress-ng --softlockup 0 -t 360 -v

  ..and wait for 360 seconds.  dmesg shows the following, 100%
  reproduceable:

  
  [  875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 
3min)!
  [  875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 
(systemd-timesyn) with signal SIGABRT.
  [  875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, 
code=killed, status=6/ABRT
  [  875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed 
state.
  [  875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 
'watchdog'.
  [  875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off 
time, scheduling restart.
  [  875.327954] systemd[1]: Stopped Network Time Synchronization.
  [  875.328845] systemd[1]: Starting Network Time Synchronization...
  [  875.525071] systemd[1]: Started Network Time Synchronization.
  [  875.539619] systemd[1]: systemd-journald.service: Main process exited, 
code=dumped, status=6/ABRT
  [  875.544257] systemd-journald[5214]: File 
/run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or 
uncleanly shut down, renaming and replacing.

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

-- 
Mailing list: https://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 1698163] Re: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1698163

Title:
  package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 127

Status in apt package in Ubuntu:
  New

Bug description:
  Ubuntu does not shut down correctly and comes up with an error report
  every time I turn it off manually and turn my computer back on.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Thu Jun 15 06:28:05 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698163] [NEW] package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Tim]

Public bug reported:

Ubuntu does not shut down correctly and comes up with an error report
every time I turn it off manually and turn my computer back on.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Thu Jun 15 06:28:05 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 127
InstallationDate: Installed on 2017-06-15 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: apt
Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1698163

Title:
  package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 127

Status in apt package in Ubuntu:
  New

Bug description:
  Ubuntu does not shut down correctly and comes up with an error report
  every time I turn it off manually and turn my computer back on.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Thu Jun 15 06:28:05 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698160] Re: package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is not ready for configuration cannot configure (current status 'half-installed')

[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 kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1698160

Title:
  package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is
  not ready for configuration  cannot configure (current status 'half-
  installed')

Status in kbd package in Ubuntu:
  New

Bug description:
  Error message in installing anything new or turning on the computer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kbd 1.15.5-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jun 15 20:04:52 2017
  DuplicateSignature:
   package:kbd:1.15.5-1ubuntu4
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package kbd (--configure):
package kbd is not ready for configuration
  ErrorMessage: package kbd is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-10 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: kbd
  Title: package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698160] [NEW] package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is not ready for configuration cannot configure (current status 'half-installed')

[Arnav Agyeya]

Public bug reported:

Error message in installing anything new or turning on the computer.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kbd 1.15.5-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Jun 15 20:04:52 2017
DuplicateSignature:
 package:kbd:1.15.5-1ubuntu4
 Processing triggers for libc-bin (2.23-0ubuntu7) ...
 dpkg: error processing package kbd (--configure):
  package kbd is not ready for configuration
ErrorMessage: package kbd is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-04-10 (65 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: kbd
Title: package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is 
not ready for configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kbd (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 kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1698160

Title:
  package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is
  not ready for configuration  cannot configure (current status 'half-
  installed')

Status in kbd package in Ubuntu:
  New

Bug description:
  Error message in installing anything new or turning on the computer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kbd 1.15.5-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jun 15 20:04:52 2017
  DuplicateSignature:
   package:kbd:1.15.5-1ubuntu4
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package kbd (--configure):
package kbd is not ready for configuration
  ErrorMessage: package kbd is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-10 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: kbd
  Title: package kbd 1.15.5-1ubuntu4 failed to install/upgrade: package kbd is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698159] [NEW] linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

[Ian Gordon]

Public bug reported:

When running kernel version 4.4.0-78 (for example) and the unattended-
upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-
cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are
removed by the Remove-Unused-Dependencies rule, because unlike "normal"
kernel packages they are not excluded by /etc/apt/apt.conf.d
/01autoremove-kernels.

The linux-cloud-tools package has the hyper-v integration services
daemons in it, so it's deletion leaves some of the integration not
working.

Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
hyper-v users aren't caught out by this?

Thanks,

Ian.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 15 15:27:35 2017
InstallationDate: Installed on 2016-04-25 (415 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1698159/+subscriptions

-- 
Mailing list: https://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 759394] Re: can not umount rbind mounts

[Phillip Susi]

** Changed in: util-linux (Ubuntu)
   Status: Opinion => Confirmed

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

Title:
  can not umount rbind mounts

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: util-linux

  mkdir /mnt/dev
  mount --rbind /dev /mnt/dev
  umount /mnt/dev

  The umount fails because of the sub mounts that the recursive bind
  also bind mounted under /mnt/dev, which you have to remove manually
  first.  When you mount with --rbind, umount should be able to reverse
  the process, unmounting all recursively bound mounts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/759394/+subscriptions

-- 
Mailing list: https://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]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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 Released
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 Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

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

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

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

[Touch-packages] [Bug 1675138] Re: Please transition to latest Boost

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:04:47 +

-- 
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 latest Boost

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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:04:47 +

-- 
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 Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:04:47 +

-- 
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:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

** Changed in: mir (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:04:47 +

-- 
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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

  Expected:
  * session is locked, but working

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

** Changed in: mir (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 Released
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 Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

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

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

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

[Touch-packages] [Bug 1675138] Re: Please transition to latest Boost

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

** Changed in: mir (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 latest Boost

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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1675138] Re: Please transition to latest Boost

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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 latest Boost

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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

** Changed in: mir (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 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]

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:04:47 +

-- 
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 Released
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 Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

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

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

** Changed in: mir (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . 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() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

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 1677239] Update Released

[Andy Whitcroft]

The verification of the Stable Release Update for mir has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  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 1685186] Update Released

[Andy Whitcroft]

The verification of the Stable Release Update for mir has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Committed

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 1675357] Update Released

[Andy Whitcroft]

The verification of the Stable Release Update for mir has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Committed

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 1675138] Update Released

[Andy Whitcroft]

The verification of the Stable Release Update for mir has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 latest Boost

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 Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  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 1672955] Update Released

[Andy Whitcroft]

The verification of the Stable Release Update for mir has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
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 Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Committed

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 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)

[Launchpad Bug Tracker]

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

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

Title:
  [enhancement] Missing client API for relative surface movement (e.g.
  dragging client-decorated windows)

Status in Mir:
  Fix Committed
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Mir needs a client API to allow surfaces to move themselves
  relatively. This is required to support full client-side decorations
  (bug 1398849), and also other apps like Google Chrome and Gnome
  Nautilus which can be dragged using part of their client areas.

  Later additions that are so similar I think they are part of the same
  bug: there need to be client APIs for "always on top" and "client
  initiate resize".

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

-- 
Mailing list: https://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 1646558] Re: [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server

[Launchpad Bug Tracker]

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

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

Title:
  [ FAILED ]
  NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server

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

Bug description:
  
  10:25:12 11: [ RUN ] 
NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server
  10:25:12 11: [2016-12-01 10:25:12.937701] mirserver: Starting
  10:25:12 11: [2016-12-01 10:25:12.938796] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
  10:25:13 11: [2016-12-01 10:25:13.123066] mirserver: Using software cursor
  10:25:13 11: [2016-12-01 10:25:13.136371] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
  10:25:13 11: [2016-12-01 10:25:13.137063] mirserver: Mir version 0.26.0
  10:25:13 11: [2016-12-01 10:25:13.294651] mirserver: Initial display 
configuration:
  10:25:13 11: [2016-12-01 10:25:13.294952] mirserver: Output 1: VGA connected, 
used
  10:25:13 11: [2016-12-01 10:25:13.295168] mirserver: Physical size 0.0" 0x0mm
  10:25:13 11: [2016-12-01 10:25:13.295349] mirserver: Power is on
  10:25:13 11: [2016-12-01 10:25:13.295559] mirserver: Current mode 1920x1080 
60.00Hz
  10:25:13 11: [2016-12-01 10:25:13.295788] mirserver: Preferred mode 1920x1080 
60.00Hz
  10:25:13 11: [2016-12-01 10:25:13.295979] mirserver: Orientation normal
  10:25:13 11: [2016-12-01 10:25:13.296175] mirserver: Logical size 1920x1080
  10:25:13 11: [2016-12-01 10:25:13.296365] mirserver: Logical position +0+0
  10:25:13 11: [2016-12-01 10:25:13.328187] mirserver: Starting
  10:25:13 11: [2016-12-01 10:25:13.745478] mirserver: Using nested cursor
  10:25:13 11: [2016-12-01 10:25:13.803440] mirserver: Mir version 0.26.0
  10:25:13 11: [2016-12-01 10:25:13.960211] mirserver: Initial display 
configuration:
  10:25:14 11: [2016-12-01 10:25:13.960729] mirserver: Output 1: VGA connected, 
used
  10:25:14 11: [2016-12-01 10:25:13.960948] mirserver: Physical size 0.0" 0x0mm
  10:25:14 11: [2016-12-01 10:25:13.961124] mirserver: Power is on
  10:25:14 11: [2016-12-01 10:25:13.961364] mirserver: Current mode 1920x1080 
60.00Hz
  10:25:14 11: [2016-12-01 10:25:13.961572] mirserver: Preferred mode 1920x1080 
60.00Hz
  10:25:14 11: [2016-12-01 10:25:13.961753] mirserver: Orientation normal
  10:25:14 11: [2016-12-01 10:25:13.961931] mirserver: Logical size 1920x1080
  10:25:14 11: [2016-12-01 10:25:13.962107] mirserver: Logical position +0+0
  10:25:16 11: [2016-12-01 10:25:16.218016] mirserver: Stopping
  10:25:16 11: [2016-12-01 10:25:16.266813] mirserver: Stopping
  10:25:16 11: 
/<>/mir-0.25.0+yakkety3048bzr3857/tests/acceptance-tests/test_nested_input.cpp:368:
 Failure
  10:25:16 11: Actual function call count doesn't match 
EXPECT_CALL(nested_event_filter, 
handle(AllOf(mt::PointerEventWithPosition(final_x, final_y), 
mt::PointerEventWithDiff(x[2], y[2]...
  10:25:16 11: Expected: to be called once
  10:25:16 11: Actual: never called - unsatisfied and active
  10:25:16 11: [ FAILED ] 
NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server (3440 
ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3020/consoleFull

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

-- 
Mailing list: https://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 1349660] Re: Touch screen coordinates don't rotate with the screen

[Launchpad Bug Tracker]

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

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

Title:
  Touch screen coordinates don't rotate with the screen

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

Bug description:
  Touch screen coordinates don't rotate with the screen.

  Test case:
1. Find a laptop with a touch screen.
2. Start mir_demo_server_shell and a client or two.
3. Rotate the screen: Ctrl+Alt+Arrows

  Expected: Touch to also be rotated.
  Observed: Touch coordinates stay in the original native orientation - don't 
match up with fingers any more.

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

-- 
Mailing list: https://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 1195540] Re: [enhancement] Make able to get version information from client / server APIs

[Launchpad Bug Tracker]

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

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

Title:
  [enhancement] Make able to get version information from client /
  server APIs

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

Bug description:
  It would be nice for shells / Mir clients to query what version of Mir
  they are using.

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

-- 
Mailing list: https://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 1698150] [NEW] package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket openssl ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »h

[Stefan Gloeckl]

Public bug reported:

Installation over Softwarecenter and that was it, afterwards I got after
new start of the system and login the error message.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 15 12:56:35 2017
ErrorMessage: Paket openssl ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2017-03-03 (104 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket 
openssl ist nicht bereit zur Konfiguration  kann nicht konfiguriert werden 
(momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1698150

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket
  openssl ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

Status in openssl package in Ubuntu:
  New

Bug description:
  Installation over Softwarecenter and that was it, afterwards I got after
  new start of the system and login the error message.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 12:56:35 2017
  ErrorMessage: Paket openssl ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-03-03 (104 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket 
openssl ist nicht bereit zur Konfiguration  kann nicht konfiguriert werden 
(momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 1588237] Re: Inconsistent behaviour of Num Lock

[Launchpad Bug Tracker]

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

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

Title:
  Inconsistent behaviour of Num Lock

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

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

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

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

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

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

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

[Touch-packages] [Bug 1646375] Re: [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated

[Launchpad Bug Tracker]

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

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

Title:
  [ FAILED ]
  
NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated

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

Bug description:
  04:37:34 [ RUN ] 
NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated
  ...
  04:37:34 unknown file: Failure
  04:37:34
  04:37:34 Unexpected mock function call - returning default value.
  04:37:34 Function call: handle(pointer_event(when=14575773119920512 
(76.256763ms ago), from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, 
vscroll=0, hscroll=0, modifiers=none))
  04:37:34 Returns: false
  04:37:34 Google Mock tried the following 3 expectations, but none matched:
  04:37:34
  04:37:34 
/<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:321:
 tried expectation #0: EXPECT_CALL(nested_event_filter, 
handle(mt::InputDeviceStateEvent()))...
  04:37:34 Expected arg #0: input device state event
  04:37:34 Actual: pointer_event(when=14575773119920512 (28.550649ms ago), 
from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, 
modifiers=none)
  04:37:34 Expected: to be called once
  04:37:34 Actual: called once - saturated and active
  04:37:34 
/<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:326:
 tried expectation #1: EXPECT_CALL(nested_event_filter, 
handle(AllOf(mt::PointerEventWithPosition(initial_movement_x, 
initial_movement_y), mt::PointerEventWithDiff(initial_movement_x, 
initial_movement_y...
  04:37:34 Expected arg #0: (pointer event with position (30, 30)) and (pointer 
event with diff (30, 30))
  04:37:34 Actual: pointer_event(when=14575773119920512 (71.013865ms ago), 
from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, 
modifiers=none)
  04:37:34 Expected: to be called once
  04:37:34 Actual: never called - unsatisfied and active
  04:37:34 
/<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:342:
 tried expectation #2: EXPECT_CALL(nested_event_filter, 
handle(AllOf(mt::PointerEventWithPosition(initial_movement_x + 
second_movement_x, initial_movement_y + second_movement_y), 
mt::PointerEventWithDiff(second_movement_x, second_movement_y...
  04:37:34 Expected arg #0: (pointer event with position (35, 28)) and (pointer 
event with diff (5, -2))
  04:37:34 Actual: pointer_event(when=14575773119920512 (73.772187ms ago), 
from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, 
modifiers=none)
  04:37:34 Expected: to be called once
  04:37:34 Actual: never called - unsatisfied and active
  04:37:34 [2016-12-01 04:33:06.521662] mirserver: Stopping
  04:37:34 [2016-12-01 04:33:06.601438] mirserver: Stopping
  04:37:34 
/<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:326:
 Failure
  04:37:34 Actual function call count doesn't match 
EXPECT_CALL(nested_event_filter, 
handle(AllOf(mt::PointerEventWithPosition(initial_movement_x, 
initial_movement_y), mt::PointerEventWithDiff(initial_movement_x, 
initial_movement_y...
  04:37:34 Expected: to be called once
  04:37:34 Actual: never called - unsatisfied and active
  04:37:34 
/<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:342:
 Failure
  04:37:34 Actual function call count doesn't match 
EXPECT_CALL(nested_event_filter, 
handle(AllOf(mt::PointerEventWithPosition(initial_movement_x + 
second_movement_x, initial_movement_y + second_movement_y), 
mt::PointerEventWithDiff(second_movement_x, second_movement_y...
  04:37:34 Expected: to be called once
  04:37:34 Actual: never called - unsatisfied and active
  04:37:34 [ FAILED ] 
NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated 
(5578 ms)

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

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1655929] Re: [testsfail] PromptSessionClientAPI.client_pid_is_associated_with_session hangs and times out

[Launchpad Bug Tracker]

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

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

Title:
  [testsfail]
  PromptSessionClientAPI.client_pid_is_associated_with_session hangs and
  times out

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

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

  13:24:57 9: --11870-- WARNING: unhandled amd64-linux syscall: 324
  13:24:57 9: --11870-- You may be able to write your own handler.
  13:24:57 9: --11870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
  13:24:57 9: --11870-- Nevertheless we consider this a bug. Please report
  13:24:57 9: --11870-- it at http://valgrind.org/support/bug_reports.html.
  15:54:57 make: *** wait: No child processes. Stop.
  15:54:57 make: *** Waiting for unfinished jobs
  15:54:57 make: *** wait: No child processes. Stop.
  15:54:57 Makefile:130: recipe for target 'test' failed
  15:54:57 make[2]: *** [test] Terminated
  15:54:57 debian/rules:19: recipe for target 'override_dh_auto_test' failed
  15:54:57 make[1]: *** [override_dh_auto_test] Terminated
  15:54:57 E: Build killed with signal TERM after 150 minutes of 

  Also on

  amd64,gcc,xenial+overlay
  amd64,gcc,zesty

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

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

  And, probably related:

  i386,gcc,xenial+overlay

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

  15:37:14 11: --32166-- WARNING: unhandled x86-linux syscall: 375
  15:37:14 11: --32166-- You may be able to write your own handler.
  15:37:14 11: --32166-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
  15:37:14 11: --32166-- Nevertheless we consider this a bug. Please report
  15:37:14 11: --32166-- it at http://valgrind.org/support/bug_reports.html.
  18:07:14 Makefile:74: recipe for target 'test' failed

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 1649354] Re: abi_check doesn't check mircore

[Launchpad Bug Tracker]

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

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

Title:
  abi_check doesn't check mircore

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

Bug description:
  abi_check doesn't check mircore

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

-- 
Mailing list: https://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 1643488] Re: Rotating an output left or right without restarting the compositor distorts the image

[Launchpad Bug Tracker]

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

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

Title:
  Rotating an output left or right without restarting the compositor
  distorts the image

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

Bug description:
  Rotating an output left or right without restarting the compositor
  distorts the image.

  Test case (using Mir 0.26 or later):
  1. Start a server
  2. Start a client
  3. mirout rotate right

  Expected: No distortion
  Observed: Distortion

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

-- 
Mailing list: https://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-zesty-2818

-- 
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-zesty-2818

-- 
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 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-zesty-2818

-- 
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 1661187] Re: [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform

[Launchpad Bug Tracker]

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

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

Title:
  [ FAILED ]
  DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform

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

Bug description:
  04:11:46 21: [ RUN ] 
DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform
  04:11:46 21: 
/<>/mir-0.26.0+zesty3925bzr4005/tests/unit-tests/input/test_default_input_manager.cpp:171:
 Failure
  04:11:46 21: Actual function call count doesn't match EXPECT_CALL(platform, 
pause_for_config())...
  04:11:46 21: Expected: to be called once
  04:11:46 21: Actual: never called - unsatisfied and active
  04:11:46 21: [ FAILED ] 
DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform (65 
ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3883/consoleFull

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

-- 
Mailing list: https://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 1661151] Re: [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device)

[Launchpad Bug Tracker]

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

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

Title:
  [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or
  Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device)

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

Bug description:
  mir_demo_server refuses to quit on Ctrl+Alt+Backspace

  It knows it should be quitting but doesn't, even when I try multiple
  times:

  [2017-02-02 12:13:12.670302] mirserver: Stopping
  [2017-02-02 12:13:13.070166] mirserver: Stopping
  [2017-02-02 12:13:13.302165] mirserver: Stopping
  [2017-02-02 12:13:13.510186] mirserver: Stopping
  [2017-02-02 12:13:13.686165] mirserver: Stopping
  [2017-02-02 12:13:13.870160] mirserver: Stopping
  [2017-02-02 12:13:14.062330] mirserver: Stopping
  [2017-02-02 12:13:14.254349] mirserver: Stopping
  [2017-02-02 12:13:14.438335] mirserver: Stopping
  [2017-02-02 12:13:14.622329] mirserver: Stopping
  [2017-02-02 12:13:14.830312] mirserver: Stopping

  Similarly, Ctrl+C no longer works:

  [2017-02-10 11:16:18.643952] mirserver:   Logical position +0+0
  [2017-02-10 11:16:18.643955] mirserver:   Output 52: HDMI-A disconnected
  ^C^C^C^C^C^C^C^C^C^C^C

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

-- 
Mailing list: https://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-zesty-2818

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

[Launchpad Bug Tracker]

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

-- 
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 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-zesty-2818

-- 
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 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 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-zesty-2818

-- 
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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1675138] Re: Please transition to latest Boost

[Launchpad Bug Tracker]

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

-- 
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 latest Boost

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
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  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 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-zesty-2818

-- 
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 1669444] Re: [regression] OSK input shaping no longer works correctly

[Launchpad Bug Tracker]

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

-- 
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 1675331] Re: [regression] Mir is assigning the first output ID = 0 (== mir_display_output_id_invalid)

[Launchpad Bug Tracker]

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

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

Title:
  [regression] Mir is assigning the first output ID = 0 (==
  mir_display_output_id_invalid)

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

Bug description:
  Mir is assigning the first output ID = 0 (==
  mir_display_output_id_invalid):

  [2017-03-23 17:22:28.936000] mirserver: Initial display configuration:
  [2017-03-23 17:22:28.936026] mirserver:   Output 0: HDMI-A disconnected
  [2017-03-23 17:22:28.936030] mirserver:   Output 1: VGA disconnected
  [2017-03-23 17:22:28.936032] mirserver:   Output 2: DisplayPort disconnected
  [2017-03-23 17:22:28.936035] mirserver:   Output 3: HDMI-A disconnected
  [2017-03-23 17:22:28.936039] mirserver:   Output 4: DisplayPort connected, 
used

  However we have already declared that:
  include/client/mir_toolkit/client_types.h:enum { 
mir_display_output_id_invalid = 0 };

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 1665271] Re: mirout reports logical size of a rotated display incorrectly

[Launchpad Bug Tracker]

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

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

Title:
  mirout reports logical size of a rotated display incorrectly

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

Bug description:
  mirout reports logical size of a rotated display incorrectly.

  For example, if I rotate a 1920x1200 display 90 degrees right it
  reports:

  Output 48: DisplayPort, connected, "DELL U2413", 1920x1200+0+0,
  enabled, on, 520mm x 320mm (24.0"), right, 1.00x, unknown, monitor

  where "1920x1200+0+0" should actually be "1200x1920+0+0" since that's
  the logical rectangle now displayed.

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 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-zesty-2818

-- 
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 1662997] Re: [regression] mirscreencast hangs during screencast creation

[Launchpad Bug Tracker]

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

-- 
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 1662942] Re: libmirclient-dev missing build depndency on libmircore-dev

[Launchpad Bug Tracker]

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

-- 
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 1662044] Re: mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to r4001)

[Launchpad Bug Tracker]

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

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

Title:
  mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to
  r4001)

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

Bug description:
  mir_acceptance_tests now takes 10 seconds longer (in lp:mir compared
  to lp:mir/0.26)

  We may decide this isn't a bug, but sometimes these are simple
  mistakes...

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 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-zesty-2818

-- 
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 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-zesty-2818

-- 
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 Released
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
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

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 1672269] Re: [regression] Mixing screen rotation with mode changes makes the image squished

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1671037] Re: [ FAILED ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation (Timeout waiting to acquire write lock)

[Launchpad Bug Tracker]

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

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

Title:
  [  FAILED  ]
  PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation
  (Timeout waiting to acquire write lock)

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

Bug description:
  
  PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation takes 5-10 
minutes to complete then fails under valgrind:

  $ valgrind --trace-children=yes bin/mir_unit_tests 
--gtest_filter="PosixRWMutex.prefer*"
  ...
  Running main() from main.cpp
  Note: Google Test filter = PosixRWMutex.prefer*
  [==] Running 1 test from 1 test case.
  [--] Global test environment set-up.
  [--] 1 test from PosixRWMutex
  [ RUN  ] 
PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation
  /home/dan/bzr/mir/trunk/tests/unit-tests/test_posix_rw_mutex.cpp:289: Failure
  Failed
  Timeout waiting to acquire write lock
  [  FAILED  ] 
PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation (647342 ms)
  [--] 1 test from PosixRWMutex (647351 ms total)

  [--] Global test environment tear-down
  [==] 1 test from 1 test case ran. (647376 ms total)
  [  PASSED  ] 0 tests.
  [  FAILED  ] 1 test, listed below:
  [  FAILED  ] 
PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation

   1 FAILED TEST

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

-- 
Mailing list: https://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 1671033] Re: Test takes minutes to complete: MediatingDisplayChangerTest.confirmed_configuration_doesnt_revert_after_timeout

[Launchpad Bug Tracker]

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

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

Title:
  Test takes minutes to complete:
  
MediatingDisplayChangerTest.confirmed_configuration_doesnt_revert_after_timeout

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

Bug description:
  
MediatingDisplayChangerTest.confirmed_configuration_doesnt_revert_after_timeout
  takes 30+ seconds under valgrind. But only half a second without
  valgrind.

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

-- 
Mailing list: https://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 1669752] Re: [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the server to segfault

[Launchpad Bug Tracker]

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

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

Title:
  [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the
  server to segfault

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

Bug description:
  [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the
  server to segfault.

  It appears there were two points of regression:
    r3996: Hotkey mode change worked but server segfaults on shutdown.
    r4012: Server segfaults on hotkeys pressed

  Changing modes with `mirout' continues to work perfectly though.

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

-- 
Mailing list: https://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-zesty-2818

-- 
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 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-zesty-2818

-- 
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
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  Fix Committed

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 1673533] Re: Presentation chains should support various Vulkan presentation modes

[Launchpad Bug Tracker]

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

-- 
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 1664562] Re: android complaint during mirscreencast of nested server

[Launchpad Bug Tracker]

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

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

Title:
  android complaint during mirscreencast of nested server

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

Bug description:
  running mirscreencast against a nested server on android seems to
  occasionally cause:

  [2017-02-14 13:01:05.614843]  MirBufferStreamAPI: Caught exception at 
client library boundary (in mir_buffer_stream_swap_buffers): 
/home/kdub/source/mir/mir/src/client/rpc/stream_socket_transport.cpp(168): 
Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
what():  Failed to send message to server: Broken pipe

  Seems limited to android.

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

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

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

[Launchpad Bug Tracker]

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

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

Title:
  qtubuntu sends wrong text as part of QKeyEvent

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

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

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

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

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

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

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

[Touch-packages] [Bug 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-zesty-2818

-- 
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 1676320] Re: mirout commands don't work when followed by --

[Launchpad Bug Tracker]

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

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

Title:
  mirout commands don't work when followed by --

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

Bug description:
  mirout commands don't work when followed by --

  $ mirout rotate right -- --desktop_file_hint=unity8
  Unrecognized action `--'

  $ mirout off -- --desktop_file_hint=unity8
  Unrecognized action `--'

  This is only a problem for Unity8, but still a problem.

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

-- 
Mailing list: https://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-zesty-2818

-- 
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
Status in mir source package in Yakkety:
  Fix Committed
Status in mir source package in Zesty:
  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