[Touch-packages] [Bug 1729861] Re: [2.2.2] ABI upgrade needed

[dino99]

* No-change rebuild against gdal-abi-2-2-2

 -- Steve Langasek   Fri, 03 Nov 2017
20:32:07 +

** Changed in: gdal (Ubuntu)
   Status: New => Fix Released

** Changed in: opencv (Ubuntu)
   Status: New => Fix Released

** Changed in: vtk (Ubuntu)
   Status: New => Fix Released

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

Title:
  [2.2.2] ABI upgrade needed

Status in gdal package in Ubuntu:
  Fix Released
Status in opencv package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released

Bug description:
  the proposed libgdal20 2.2.2+dfsg-2 package cant be upgraded:

  sudo apt upgrade libgdal20
  

  The following packages have unmet dependencies:
   libopencv-imgcodecs3.2 : Depends: gdal-abi-2-2-1
   libvtk6.3 : Depends: gdal-abi-2-2-1
  E: Broken packages

  vtk6 is now two years old, maybe upload at least 7.1 version
  https://ftp-master.debian.org/new/vtk7_7.1.1+dfsg1-1~exp1.html
  https://www.vtk.org/gitweb?p=VTK.git
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810254

  opencv also have a newer version:
  https://packages.debian.org/source/experimental/opencv

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgdal20 2.2.1+dfsg-2build5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  3 15:00:33 2017
  SourcePackage: gdal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1714431] Re: Can not login after switch to runlevel 3 from 1

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can not login after switch to runlevel 3 from 1

Status in systemd package in Ubuntu:
  Expired

Bug description:
  No login prompt or anything on console after switch to runlevel 3/5
  from 1

  Step to reproduce
  1) Make sure root password is set
  2) login as root on console
  3) `init 1` switch to runlevel 1
  4) login again as root
  5) `init 3` or `init 5` and no login or prompt

  root@D05-2:~# init 1
  root@D05-2:~# 
  Ubuntu 16.04.3 LTS D05-2 ttyAMA0

  D05-2 login: root 
  System is going down.

  Password: 
  Last login: Fri Sep  1 07:28:04 UTC 2017 on ttyAMA0
  Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-33-generic aarch64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
  http://www.ubuntu.com/business/services/cloud

  0 packages can be updated.
  0 updates are security updates.

  
  root@D05-2:~# init 5
  [  103.499358] cloud-init[4497]: Cloud-init v. 0.7.9 running 'init-local' at 
Fri, 01 Sep 2017 07:28:40 +. Up 103.12 seconds.

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

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

[Touch-packages] [Bug 1730028] Re: logspam about Duplicate line for path "/var/log"

[Seth Arnold]

$ dpkg -l systemd rsyslog | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--=
ii  rsyslog8.16.0-1ubuntu3 amd64reliable system and kernel 
logging daemon
ii  systemd229-4ubuntu20   amd64system and service manager

Thanks

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

Title:
  logspam about Duplicate line for path "/var/log"

Status in systemd package in Ubuntu:
  New

Bug description:
  Similar to bug 1484027, but that's marked 'Fix released', so something
  must have regressed in the meantime.

  $ journalctl | grep "Duplicate line" | wc -l
  58

  $ grep "/var/log " /usr/lib/tmpfiles.d/*
  /usr/lib/tmpfiles.d/00rsyslog.conf:# Override systemd's default 
tmpfiles.d/var.conf to make /var/log writable by
  /usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
  /usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -

  
  Ideally I'd see at most one line about this in my logs.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov  3 19:42:41 2017
  InstallationDate: Installed on 2016-04-04 (578 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  MachineType: Supermicro SSG-6038R-E1CR16L
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=d1ab8bd8-41d5-4142-92d6-d0926539807b ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRH-iT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSSG-6038R-E1CR16L:pvr123456789:rvnSupermicro:rnX10DRH-iT:rvr1.01:cvnSupermicro:ct1:cvrDefaultstring:
  dmi.product.name: SSG-6038R-E1CR16L
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

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

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

[Touch-packages] [Bug 1730028] [NEW] logspam about Duplicate line for path "/var/log"

[Seth Arnold]

Public bug reported:

Similar to bug 1484027, but that's marked 'Fix released', so something
must have regressed in the meantime.

$ journalctl | grep "Duplicate line" | wc -l
58

$ grep "/var/log " /usr/lib/tmpfiles.d/*
/usr/lib/tmpfiles.d/00rsyslog.conf:# Override systemd's default 
tmpfiles.d/var.conf to make /var/log writable by
/usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
/usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -


Ideally I'd see at most one line about this in my logs.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu20
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Nov  3 19:42:41 2017
InstallationDate: Installed on 2016-04-04 (578 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
MachineType: Supermicro SSG-6038R-E1CR16L
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=d1ab8bd8-41d5-4142-92d6-d0926539807b ro
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
 
 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: Default string
dmi.board.name: X10DRH-iT
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSSG-6038R-E1CR16L:pvr123456789:rvnSupermicro:rnX10DRH-iT:rvr1.01:cvnSupermicro:ct1:cvrDefaultstring:
dmi.product.name: SSG-6038R-E1CR16L
dmi.product.version: 123456789
dmi.sys.vendor: Supermicro

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

Title:
  logspam about Duplicate line for path "/var/log"

Status in systemd package in Ubuntu:
  New

Bug description:
  Similar to bug 1484027, but that's marked 'Fix released', so something
  must have regressed in the meantime.

  $ journalctl | grep "Duplicate line" | wc -l
  58

  $ grep "/var/log " /usr/lib/tmpfiles.d/*
  /usr/lib/tmpfiles.d/00rsyslog.conf:# Override systemd's default 
tmpfiles.d/var.conf to make /var/log writable by
  /usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
  /usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -

  
  Ideally I'd see at most one line about this in my logs.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov  3 19:42:41 2017
  InstallationDate: Installed on 2016-04-04 (578 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  MachineType: Supermicro SSG-6038R-E1CR16L
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=d1ab8bd8-41d5-4142-92d6-d0926539807b ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRH-iT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 1730019] [NEW] Mouse/pointer missing after resume from sleep

[serge rey]

Public bug reported:

After waking the machine up, I am no longer able to use the mouse as the
pointer does not respond. Only a hard reboot fixes this.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  3 18:19:46 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
InstallationDate: Installed on 2017-11-02 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. 
 Bus 001 Device 003: ID 5986:0535 Acer, Inc 
 Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80HE
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A6CN58WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 3 Pro-1370
dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
dmi.product.family: IDEAPAD
dmi.product.name: 80HE
dmi.product.version: Lenovo YOGA 3 Pro-1370
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
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.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Mouse/pointer missing after resume from sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  After waking the machine up, I am no longer able to use the mouse as
  the pointer does not respond. Only a hard reboot fixes this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  3 18:19:46 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2017-11-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. 
   Bus 001 Device 003: ID 5986:0535 Acer, Inc 
   Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80HE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  

[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li

[Launchpad Bug Tracker]

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

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

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

Title:
  arguments to dbus_connection_unref() were incorrect, assertion
  "connection->generation == _dbus_current_generation" failed in file
  ../../../dbus/dbus-connection.c line 2824.

Status in dbus package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Maybe related to my bug report on the steam package, my hard guess is
  that the missing system tray is causing this.

  Sadly enough it really spams the syslog in a way which makes it
  unusable. Have to truncate it every day from a size of around 60MB
  down to 0.

  The PID mentioned is connected to the steam client running. has as well been 
reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just 
ubuntu-bug did not want to send in a proper bug report on this package.
  (marked the bug report the link goes to as a duplicate of this bug)

  IMHO this is critical, even if SSDs are more stable as people think,
  this produces unnecessary write and delete cycles

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dbus 1.10.22-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 25 19:19:54 2017
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li

[Launchpad Bug Tracker]

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

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

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

Title:
  arguments to dbus_connection_unref() were incorrect, assertion
  "connection->generation == _dbus_current_generation" failed in file
  ../../../dbus/dbus-connection.c line 2824.

Status in dbus package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Maybe related to my bug report on the steam package, my hard guess is
  that the missing system tray is causing this.

  Sadly enough it really spams the syslog in a way which makes it
  unusable. Have to truncate it every day from a size of around 60MB
  down to 0.

  The PID mentioned is connected to the steam client running. has as well been 
reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just 
ubuntu-bug did not want to send in a proper bug report on this package.
  (marked the bug report the link goes to as a duplicate of this bug)

  IMHO this is critical, even if SSDs are more stable as people think,
  this produces unnecessary write and delete cycles

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dbus 1.10.22-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 25 19:19:54 2017
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1730000] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1727828
   package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package initramfs-tools 0.125ubuntu12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Xubuntu 17.10
  while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  AptOrdering:
   widelands:amd64: Install
   widelands-data:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Nov  4 01:16:29 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-10 (177 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/173/+subscriptions

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

[Touch-packages] [Bug 1730000] [NEW] package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nick]

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

Public bug reported:

Xubuntu 17.10
while installing updates

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
AptOrdering:
 widelands:amd64: Install
 widelands-data:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Nov  4 01:16:29 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-05-10 (177 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package initramfs-tools 0.125ubuntu12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Xubuntu 17.10
  while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  AptOrdering:
   widelands:amd64: Install
   widelands-data:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Nov  4 01:16:29 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-10 (177 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/173/+subscriptions

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

[Touch-packages] [Bug 1729983] [NEW] /lib/systemd/systemd-udevd:6:__libc_open64:open64:synthesize_change:on_inotify:source_dispatch

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/67bc161b5b72d00a9c69637a4579fa27d07e1dfe 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful xenial zesty

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

Title:
  /lib/systemd/systemd-
  udevd:6:__libc_open64:open64:synthesize_change:on_inotify:source_dispatch

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/67bc161b5b72d00a9c69637a4579fa27d07e1dfe 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1729989] [NEW] /usr/share/gdebi/gdebi-kde:ModuleNotFoundError:/usr/bin/gdebi-kde@26:/usr/lib/python3/dist-packages/PyKDE4/__init__.py@1

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdebi.  This problem was most recently seen with package version 
0.9.5.7+nmu1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/3095898ede09f60b77e63f8f347e54a8dce44857 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful kylin-17.10

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

Title:
  /usr/share/gdebi/gdebi-kde:ModuleNotFoundError:/usr/bin/gdebi-
  kde@26:/usr/lib/python3/dist-packages/PyKDE4/__init__.py@1

Status in gdebi package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdebi.  This problem was most recently seen with package version 
0.9.5.7+nmu1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/3095898ede09f60b77e63f8f347e54a8dce44857 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1729938] [NEW] package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Gary Pinsky]

Public bug reported:

crashed

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libx11-doc 2:1.6.4-3
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Nov  3 17:06:23 2017
Dependencies:
 
DistUpgraded: 2017-10-25 21:46:58,559 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
DistroCodename: zesty
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-11-03  17:06:23
 Commandline: apt-get install apt-transport-https
 Requested-By: gary (1000)
DpkgTerminalLog:
 dpkg: error processing package libx11-doc (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family 
Integrated Graphics Controller [1179:fcd0]
InstallationDate: Installed on 2017-07-10 (116 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: TOSHIBA Satellite L745
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=d1d5ae7f-47b1-4f8a-867b-ff6e4b1b30f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: libx11
Title: package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to zesty on 2017-10-26 (8 days ago)
dmi.bios.date: 05/17/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base 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:bvnINSYDE:bvr1.60:bd05/17/2011:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-01V00E
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.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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: Fri Nov  3 16:38:19 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-package compiz-0.9 ubuntu zesty

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

Title:
  package libx11-doc 2:1.6.4-3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libx11 package in Ubuntu:
  New

Bug description:
  crashed

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libx11-doc 2:1.6.4-3
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  3 17:06:23 2017
  Dependencies:
   
  DistUpgraded: 2017-10-25 21:46:58,559 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: zesty
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-11-03  17:06:23
   Commandline: apt-get install apt-transport-https
   Requested-By: gary (1000)
  DpkgTerminalLog:
   dpkg: error processing package libx11-doc (--configure):
package is in a very bad 

[Touch-packages] [Bug 1718931] Re: No VPN autoconnect

[Odd Tore]

Not working for me at all.

I have a PPTP VPN server at home running on a linux 12.04 server.

Connecting to this server works like a charm from Android
phones/tablets, I-phone (IOS versions before they stopped supporting
PPTP), and win10.

I use this primarily to get IP adress from my home country when needed.

Anyway, my first issue was after installing Ubuntu 17.10 on a PC.
Experienced all the above mentioned issues, except that whatever I try to do 
with "Store password for all users" does not help.

Ended up setting up the VPN connection from command-line using the
following tutorial: https://help.my-private-
network.co.uk/support/solutions/articles/8452-pptp-vpn-setup-on-linux-
ubuntu-via-terminal-command-line

Now I actually get connected to my server using pon , but
DNS does not work.

I can open webpages typing in ip-address directly, and when I run
traceroute, traffic appears to be going through my home network.

In /etc/ppp/ the 2 nameservers I have configured on server appears in
resolv.conf

Any idea before I go mad?

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

Title:
  No VPN autoconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1729928] Re: package apport 2.20.4-0ubuntu4 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1729928

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 127

Status in apport package in Ubuntu:
  New

Bug description:
  its automatically pop up after the crash of MENDELEY software

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports: 600:0:122:134334:2017-11-04 01:29:21.195202350 +0530:2017-11-04 
01:29:22.195202350 +0530:/var/crash/apport.0.crash
  Date: Sat Nov  4 01:29:21 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-10-27 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: 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/apport/+bug/1729928/+subscriptions

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

[Touch-packages] [Bug 1729928] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[ajantha]

Public bug reported:

its automatically pop up after the crash of MENDELEY software

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CrashReports: 600:0:122:134334:2017-11-04 01:29:21.195202350 +0530:2017-11-04 
01:29:22.195202350 +0530:/var/crash/apport.0.crash
Date: Sat Nov  4 01:29:21 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 127
InstallationDate: Installed on 2017-10-27 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 127

Status in apport package in Ubuntu:
  New

Bug description:
  its automatically pop up after the crash of MENDELEY software

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports: 600:0:122:134334:2017-11-04 01:29:21.195202350 +0530:2017-11-04 
01:29:22.195202350 +0530:/var/crash/apport.0.crash
  Date: Sat Nov  4 01:29:21 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-10-27 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: 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/apport/+bug/1729928/+subscriptions

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

[Touch-packages] [Bug 1662166] Re: [TM1612, Realtek ALC233, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [TM1612, Realtek ALC233, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  6 20:48:01 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [TM1612, Realtek ALC233, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: A04
  dmi.board.asset.tag: Any
  dmi.board.name: TM1612
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrA04:bd08/06/2016:svnTimi:pnTM1612:pvr:rvnTimi:rnTM1612:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.name: TM1612
  dmi.sys.vendor: Timi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1662166/+subscriptions

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Launchpad Bug Tracker]

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

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

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1729910] [NEW] lp ignores ~/.cups/lpoptions in 17.10

[Gabriel Ramirez]

Public bug reported:

LP ignores the settings defined in ~/cups/lpoptions in artful

Steps to reproduce:

1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
2) Execute lpstat -d
3) Above will output default defined in prints.conf instead of ~/cups/lpoptions

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

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  New

Bug description:
  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1274819] Re: (Desktop) display tears slightly for one frame when waking from sleep mode

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  (Desktop) display tears slightly for one frame when waking from sleep
  mode

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

Bug description:
  (Desktop) display tears slightly for one frame when waking from sleep
  mode.

  Test case:
1. Start mir_demo_server_shell
2. Start mir_demo_client_SOMETHING that will animate constantly
3. Alt+P  to put the display to sleep
4. Alt+P to wake the dislplay

  Expected: The client continues being composited flawlessly.
  Observed: Slight tearing when the display comes back on. But it only seems to 
last about one frame.

  I think the problem is mesa::Display::resume() calling
  schedule_set_crtc. I know it needs to, but resetting the CRTC(s) does
  a page flip without synchronization to vblank. So that's probably the
  one frame of tearing.

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

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

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

[joshas]

Mentioned "rfkill unblock all" command actually enables bluetooth, which I'd 
like to keep disabled.
bluetoothd should check if device is blocked and do not try setting mode for 
such devices.

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1194333] Re: [enhancement] Add support for single buffered clients

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [enhancement] Add support for single buffered clients

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

Bug description:
  Clients can't render single-buffered (direct front-buffer write
  access).

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

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

[Touch-packages] [Bug 1221375] Re: test command line options do not work as expected

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  test command line options do not work as expected

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

Bug description:
  if you run

  ./acceptance-tests --help,
  you get the gtest help options.

  If you run 
  ./acceptance-tests --option-that-doesnt-exist
  you get the mir server command line options (and the server still tries to 
run)

  if you mix gtest options and mir server options, it doesn't work (one
  or the other seems to be ignored)

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

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

[Touch-packages] [Bug 1304372] Re: cross compile chroot fails under non-English locales

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  cross compile chroot fails under non-English locales

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  When I try to cross compile under polish locale (pl_PL.UTF-8), the
  script fails, and leaves the current dir dirty, it should probably
  clean up on chroot creation failure.

  ⟫ ./cross-compile-chroot.sh   

   
  no partial chroot dir detected. attempting to create one
  creating phablet-compatible armhf partial chroot for mir compilation in 
directory /home/michal/dev/canonical/unity8/mir/partial-armhf-chroot
  I: Retrieving Release 
  I: Retrieving Release.gpg 
  I: Checking Release signature
  I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32)
  I: Retrieving Packages 
  I: Validating Packages 
  I: Resolving dependencies of required packages...
  I: Resolving dependencies of base packages...
  I: Found additional base dependencies: bsdmainutils dh-apparmor file 
fontconfig fontconfig-config fonts-dejavu-core gettext gettext-base 
gir1.2-glib-2.0 gir1.2-umockdev-1.0 groff-base icu-devtools intltool-debian 
libandroid-properties1 libarchive13 libasn1-8-heimdal libasprintf0c2 
libboost-atomic1.54-dev libboost-atomic1.54.0 libboost-chrono1.54-dev 
libboost-chrono1.54.0 libboost-date-time1.54-dev libboost-date-time1.54.0 
libboost-filesystem1.54-dev libboost-filesystem1.54.0 
libboost-program-options1.54-dev libboost-program-options1.54.0 
libboost-regex1.54-dev libboost-regex1.54.0 libboost-serialization1.54-dev 
libboost-serialization1.54.0 libboost-system1.54-dev libboost-system1.54.0 
libboost-thread1.54-dev libboost-thread1.54.0 libboost1.54-dev libc6-dbg 
libcairo2 libcdt5 libcgraph6 libcroco3 libcurl3 libdatrie1 libdrm-nouveau2 
libdrm-omap1 libdrm-radeon1 libegl1-mesa libegl1-mesa-drivers libelf1 libelfg0 
libexpat1 libffi6 libfontconfig1 libfreetype6 libgbm1 libgcrypt11 libgd3 
libgflags-dev libgflags2 libgirepository-1.0-1 libgl1-mesa-dri libglapi-mesa 
libgles2-mesa libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev 
libgnutls26 libgoogle-glog0 libgpg-error0 libgraphite2-3 libgssapi-krb5-2 
libgssapi3-heimdal libgvc6 libgvpr2 libhardware2 libharfbuzz0b 
libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal 
libhx509-5-heimdal libhybris-common1 libice6 libicu-dev libicu52 libidn11 
libjbig0 libjpeg-turbo8 libjpeg8 libk5crypto3 libkeyutils1 libkrb5-26-heimdal 
libkrb5-3 libkrb5support0 libldap-2.4-2 libllvm3.4 libltdl7 liblttng-ust-ctl2 
liblttng-ust0 liblzo2-2 libmagic1 libmirclient-dev libmirclient7 
libmirclientplatform-mesa libmirprotobuf-dev libmirprotobuf0 libnettle4 
libopenvg1-mesa libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0 
libpangoft2-1.0-0 libpathplan4 libpcre3-dev libpcrecpp0 libpipeline1 
libpixman-1-0 libpopt0 libprotobuf-lite8 libprotobuf8 libprotoc8 
libpthread-stubs0-dev libroken18-heimdal librtmp0 libsasl2-2 
libsasl2-modules-db libsm6 libsqlite3-0 libssl1.0.0 libtasn1-6 libthai-data 
libthai0 libtiff5 libumockdev0 libunistring0 liburcu-dev liburcu1 libvpx1 
libwayland-client0 libwayland-cursor0 libwayland-dev libwayland-egl1-mesa 
libwayland-server0 libwind0-heimdal libx11-6 libx11-data libx11-dev 
libx11-xcb-dev libx11-xcb1 libxau-dev libxau6 libxaw7 libxcb-dri2-0 
libxcb-dri2-0-dev libxcb-dri3-0 libxcb-dri3-dev libxcb-glx0 libxcb-glx0-dev 
libxcb-present-dev libxcb-present0 libxcb-randr0 libxcb-randr0-dev 
libxcb-render0 libxcb-render0-dev libxcb-shape0 libxcb-shape0-dev libxcb-shm0 
libxcb-sync-dev libxcb-sync1 libxcb-xfixes0 libxcb-xfixes0-dev libxcb1 
libxcb1-dev libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev 
libxext6 libxfixes-dev libxfixes3 libxkbcommon0 libxml2 libxmu6 libxpm4 
libxrender1 libxshmfence-dev libxshmfence1 libxslt1.1 libxt6 libxxf86vm-dev 
libxxf86vm1 man-db mircommon-dev po-debconf systemtap-sdt-dev ucf uuid-dev 
x11-common x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev 
x11proto-fixes-dev x11proto-gl-dev x11proto-input-dev x11proto-kb-dev 
x11proto-xext-dev x11proto-xf86vidmode-dev xkb-data xorg-sgml-doctools 
xtrans-dev zlib1g-dev 
  I: Checking component main on http://ports.ubuntu.com/ubuntu-ports...
  E: Couldn't find these debs: Niespełnione pakietu: budowania zależności

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

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

[Touch-packages] [Bug 1323092] Re: Mir Wiki: Error in build instructions for PC.

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Mir Wiki: Error in build instructions for PC.

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

Bug description:
  At http://unity.ubuntu.com/mir/building_source_for_pc.html the install
  instructions are missing a step, thus causing the build process to
  fail. Immediately after branching the mir repository, the user should
  cd into the mir directory. Without this step, all following steps will
  fail.

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

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

[Touch-packages] [Bug 1193263] Re: [enhancement] [docs] How to write a driver that supports Mir

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  [enhancement] [docs] How to write a driver that supports Mir

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

Bug description:
  It'd be good to document this. This is blocked on bug 1118909 though.

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

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

[Touch-packages] [Bug 1729900] [NEW] I used the tool

[Verónica B .]

Public bug reported:

I am using Ubuntu 16.04- 64 bits

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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
Date: Fri Nov  3 14:29:05 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated 
Graphics [1462:7a15]
InstallationDate: Installed on 2017-06-24 (131 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1a2c:0c23 China Resource Semico Co., Ltd 
 Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ 
Mini Traveler / Genius NetScroll 120
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7A15
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=5361567f-1ada-452b-b7b9-c77c77242c7f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.50
dmi.board.asset.tag: Default string
dmi.board.name: H110M PRO-VH PLUS (MS-7A15)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd12/16/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VHPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7A15
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Fri Nov  3 08:57:00 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
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/1729900

Title:
  I used the tool

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 16.04- 64 bits

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Fri Nov  3 14:29:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated 
Graphics [1462:7a15]
  InstallationDate: Installed on 2017-06-24 (131 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:0c23 China Resource Semico Co., Ltd 
   Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A15
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=5361567f-1ada-452b-b7b9-c77c77242c7f ro quiet 

[Touch-packages] [Bug 1300200] Re: Unable to find GMock/GTest on distributions other than Ubuntu

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Unable to find GMock/GTest on distributions other than Ubuntu

Status in dbus-cpp:
  New
Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  CMake fails to find GMock/GTest on Fedora and Gentoo with

  $ cmake -DCMAKE_BUILD_TYPE=Debug ..
  
  CMake Error at cmake/FindGtest.cmake:13 (message):
google-mock package not found
  Call Stack (most recent call first):
tests/CMakeLists.txt:20 (find_package)
  -- Configuring incomplete, errors occurred!

  within the call to

  find_path(GMOCK_INSTALL_DIR gmock/CMakeLists.txt HINTS /usr/src)

  in cmake/FindGtest.cmake line 10. I suspect, this is because
  gmock/CMakeLists.txt is not installed on those distributions along
  with the rest of the package.

  Anyway, Google Test developers discourage the use of a pre-compiled library, 
see their FAQ [1]. This issue also affects
  - https://launchpad.net/process-cpp
  - https://launchpad.net/properties-cpp

  Possible solution: I have an alternative find-script at hand that also
  uses ExternalProject_Add() but always downloads and extracts Google
  Mock in your build tree, automatically adds the Google Mock libraries
  as dependency of the test, and compiles the Google Mock libraries
  along with your project.

  I'm willing to contribute this find-script to your project if you wish
  but I need to check with my employer's Open Source contribution
  policies before I do that.

  [1] https://code.google.com/p/googletest/wiki/FAQ
  #Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1300200/+subscriptions

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

[Touch-packages] [Bug 1195762] Re: Feature request: support multiseat on a multi-head single card

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Feature request: support multiseat on a multi-head single card

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

Bug description:
  As long as LightDM gains support to logind's automatic multiseat
  feature (https://bugs.launchpad.net/lightdm/+bug/1190581), it would be
  nice if the couple Mir+LightDM also support multiseat for a single
  multi-headed graphics card.

  Currently in X.Org, the only way to do such a thing is launching a
  bare (no greeter) X server spanning all available monitors, on top of
  which one launches nested X servers (usually Xephyr instances), one
  for each seat.

  Maybe I should open this bug in LightDM page, but I'm opening it here
  because I wonder if Mir could support this feature without the need of
  nested servers.

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

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

[Touch-packages] [Bug 1312099] Re: The exception thrown by clients when a server dies is more confusing and worrying than it should be - what(): Failed to send message to server: Bad file descriptor

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  The exception thrown by clients when a server dies is more confusing
  and worrying than it should be - what():  Failed to send message to
  server: Bad file descriptor

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

Bug description:
  The exception thrown by clients when a server dies is more confusing
  and worrying than it should be -

  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
what():  Failed to send message to server: Bad file descriptor

  It sounds like a catastrophic client bug. Actually it just means the
  server went away. So maybe we should change the error message to
  explain that and sound less worrying.

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

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

[Touch-packages] [Bug 1729634] Re: Linker warnings for apparmor.o

[Joseph Salisbury]

** Package changed: linux (Ubuntu) => apparmor (Ubuntu)

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

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

Title:
  Linker warnings for apparmor.o

Status in apparmor package in Ubuntu:
  New

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Touch-packages] [Bug 1211699] Re: radeon + mir_demo_standalone_render_surfaces = corrupt textures

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  radeon + mir_demo_standalone_render_surfaces = corrupt textures

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  radeon + mir_demo_standalone_render_surfaces = corrupt textures

  Verified with lp:mir r971. Seems to be a recent regression because
  there's no problem with r947. I suspect it broke in r948.

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

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

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

[Touch-packages] [Bug 1205389] Re: Mir is built assuming armhf is always android

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Mir is built assuming armhf is always android

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

Bug description:
  The Mir packaging for Ubuntu is configured to build only for an
  Android-based runtime.  It should instead be built to detect the
  runtime at runtime.

  This problem causes the tests run during packaging to fail, since the
  packaging is built on a  non-Android runtime (see bug #1195265 and bug
  #1203004).

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

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

[Touch-packages] [Bug 1194031] Re: Mir callback types don't follow the correct coding style

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Mir callback types don't follow the correct coding style

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

Bug description:
  Mir callback types don't follow the correct coding style...

  include/shared/mir_toolkit/client_types.h:
  typedef void (*mir_connected_callback)(MirConnection *connection, void 
*client_context);
  typedef void (*mir_surface_callback)(MirSurface *surface, void 
*client_context);
  typedef void (*mir_event_delegate_callback)(

  I think the correct style would be capitalized like all the other types:
  MirConnectedCallback
  MirSurfaceCallback
  MirEventDelegateCallback (although not sure about the need for "Delegate").

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

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

[Touch-packages] [Bug 1293950] Re: [enhancement] Add support for deep color

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [enhancement] Add support for deep color

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

Bug description:
  It would be nice to eventually add support for deep color. That is
  30-bit or higher color depths. I suspect doing so would require work
  both in the server and clients (new pixel formats).

  http://en.wikipedia.org/wiki/Color_depth#Deep_color_.2830.2F36.2F48-bit.29

  See also related bug 1212753, which I suspect could be solved by
  adding high colour support.

  See also bug 1469673 which is about high colour.

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

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

[Touch-packages] [Bug 1193260] Re: [enhancemement] [docs] How to write a a Mir backend for a shell

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [enhancemement] [docs] How to write a a Mir backend for a shell

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

Bug description:
  Feedback from Daniel van Vugt:
   - Backend for a "window manager": This means a shell, linking to 
libmirserver. 
   - Class structure (via libmirserver) maybe not quite right to go documenting 
this yet. 
   - you can look at examples/demo-shell/* which is intended to be a totally  
generic 
 shell with no links to Unity. It still needs more functionality  yet, 
though.

  We could link to this example more prominently on the main page to
  start this effort.

  Is the class structure definition tracked somewhere else?

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

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

[Touch-packages] [Bug 1729634] [NEW] Linker warnings for apparmor.o

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121 gives
warnings when linking apparmor.o such as:

  LD  security/apparmor/apparmor.o
WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
(next build fault)
The function param_get_mode() references
the variable __initdata apparmor_initialized.
This is often because param_get_mode lacks a __initdata 
annotation or the annotation of apparmor_initialized is wrong.

I believe this is because the __initdata annotation was removed from
security/apparmor/lsm.c but not from security/apparmor/include/lib.h

The following patch cleans the compilation warnings, but may not be the
correct fix:

--- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
+++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
@@ -56,7 +56,7 @@
} while (0)
 
 /* Flag indicating whether initialization completed */
-extern int apparmor_initialized __initdata;
+extern int apparmor_initialized;
 
 /* fn's in lib */
 char *aa_split_fqname(char *args, char **ns_name);

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

-- 
Linker warnings for apparmor.o
https://bugs.launchpad.net/bugs/1729634
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor in Ubuntu.

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

[Touch-packages] [Bug 1210434] Re: mir_demo_standalone_render_to_fb cannot be quit or switched away from

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  mir_demo_standalone_render_to_fb cannot be quit or switched away from

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

Bug description:
  mir_demo_standalone_render_to_fb cannot be quit or switched away from.
  It doesn't seem to have the same Ctrl+Alt+Backspace or Ctrl+Alt+Fn
  support our other demos do.

  To kill it you actually have to ssh in from another machine.

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

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

[Touch-packages] [Bug 1323978] Re: Surfaces that open underneath the cursor aren't aware the cursor is inside them until the cursor moves

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Surfaces that open underneath the cursor aren't aware the cursor is
  inside them until the cursor moves

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

Bug description:
  Surfaces that open underneath the cursor aren't aware the cursor is
  inside them until the cursor moves.

  This means that a toolkit like GTK+ wont correctly render elements
  like buttons to indicate they are active.

  This could be solved by getting a motion event with action=hover-enter
  after the surface is created.

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

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

[Touch-packages] [Bug 1236224] Re: "float alpha()" is potentially confusing, and should be "float opacity()"

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  "float alpha()" is potentially confusing, and should be "float
  opacity()"

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

Bug description:
  "float alpha()" is potentially confusing, and should be "float
  opacity()".

  This is because there are two aspects to alpha blending of a surface:
1. The surface's own alpha channel, which can have different values for 
each pixel (hence making surfaces of any shape and transparent in places).
2. The overall surface opacity value desired by the shell/compositor.

  In Mir we presently mean #2 when using "float alpha()". But I think it
  should be renamed to "float opacity()" to minimize confusion in future
  with #1.

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

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

[Touch-packages] [Bug 1285479] Re: [enhancement] add clearing screen on exit

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [enhancement] add clearing screen on exit

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

Bug description:
  Inconsistency: "stop unity8" clears the screen on N4 but not on any
  other device. You're usually left with what looks like Unity8 still,
  but of course it doesn't respond when Unity8's no running any more.

  I think it would be nice to have some consistency. Maybe we should be
  clearing the screen on exit? Is that even feasible?

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

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

[Touch-packages] [Bug 1216245] Re: mir_demo_server_shell doesn't respond to hotplugging monitors

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  mir_demo_server_shell doesn't respond to hotplugging monitors

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

Bug description:
  mir_demo_server_shell doesn't respond to hotplugging monitors. I have
  to restart the server to use new monitors. Probably just hasn't been
  implemented in the demo shell yet...

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

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

[Touch-packages] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Add support for fake modes on laptop screens which only have one

Status in Canonical System Image:
  Triaged
Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

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

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

[Touch-packages] [Bug 1200389] Re: [enhancement] Shell should be able to affect input device probing

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [enhancement] Shell should be able to affect input device probing

Status in Mir:
  Triaged
Status in Unity System Compositor:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  In the case of the System Compositor, we are not necessarily
  interested in opening all input devices (i.e. pointer), but we would
  like to open the keyboard.

  It would be nice if the shell/system-compositor could interfere with
  input device probing, i.e.

  bool Input::use_device(DeviceInfo)

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

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

[Touch-packages] [Bug 1660889] Re: Intermittent failure in mir_demo_client_animated_cursor smoke test on krillin

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Intermittent failure in mir_demo_client_animated_cursor smoke test on
  krillin

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

Bug description:
  Intermittent failure in mir_demo_client_animated_cursor smoke test on
  krillin, which is a longstanding failure split from bug 1560909.

  Still happening again today here:

  03:21:03 I: The following clients failed to execute successfully:
  03:21:03 I: mir_demo_client_animated_cursor
  03:21:03 I: Smoke testing complete with returncode -1
  03:21:03 + mir_rc=-1

  https://mir-jenkins.ubuntu.com/job/device-runtests-
  mir/2894/device_type=krillin/console

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

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

[Touch-packages] [Bug 1659999] Re: [ FAILED] mir_demo_client_eglstateswitcher smoke tests on krillin

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED] mir_demo_client_eglstateswitcher smoke tests on krillin

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

Bug description:
  00:02:29 mir_demo_server --test-timeout=3 --test-client 
mir_demo_client_eglstateswitcher
  
  00:02:30 Mir chose pixel format 1.
  00:02:30 Using pixel format 2.
  00:02:30 Current active output is 540x960 +0+0
  00:02:30 Window is on output 1: 241 DPI, scale 1.0x, phone form factor, 
66.57Hz
  00:02:30 Window exposed
  00:02:32 Current state: mir_window_state_restored
  00:02:32 Requesting state: mir_window_state_unknown
  00:02:33 Signal 15 received. Good night.
  00:02:33 Current state: mir_window_state_restored
  00:02:33 Requesting state: mir_window_state_maximized
  00:02:33 Resized to 540x960
  00:02:34 [2017-01-28 00:02:34.067441] server_example_test_client.cpp: 
Terminating client
  00:02:34 [2017-01-28 00:02:34.067675] mirserver: Stopping
  00:02:34 I: [FAILED] mir_demo_client_eglstateswitcher

  Here

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

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

[Touch-packages] [Bug 1631597] Re: Protobuf 3.1 compatibility

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Protobuf 3.1 compatibility

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

Bug description:
  Protobuf 3.1 contains the change:

  * Moved default_instances to global variables. This allows
  default_instance addresses to be known at compile time.

  This results if trying to compile against protobuf 3.1 that there will be 
errors like:
  undefined reference to `mir::protobuf::SurfaceId_default_instance_'

  and similar missing references to default_instance

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

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

[Touch-packages] [Bug 1676313] Re: Mir-on-X is very laggy and stutters (if rendering and moving the mouse simultaneously)

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Mir-on-X is very laggy and stutters (if rendering and moving the mouse
  simultaneously)

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

Bug description:
  Mir-on-X is very laggy and stutters (if rendering and moving the mouse
  simultaneously)

  Test case: Start a server under X and a client or two like
  mir_demo_client_egltriangle. Now try moving the cursor/windows around.

  Expected: Responsive shell
  Observed: Heavy stuttering and lag

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

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

[Touch-packages] [Bug 1690358] Re: [testsfail] PromptSessionClientAPI.can_get_fds_for_prompt_providers

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [testsfail] PromptSessionClientAPI.can_get_fds_for_prompt_providers

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

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

  10:17:00 11: [ RUN ] PromptSessionClientAPI.can_get_fds_for_prompt_providers
  10:17:00 11: [2017-05-12 10:16:59.854674] mirserver: Starting
  10:17:00 11: [2017-05-12 10:16:59.884156] mirserver: Selected driver: 
mir:stub-graphics (version 0.27.0)
  10:17:01 11: [2017-05-12 10:17:00.172141] mirserver: Using software cursor
  10:17:02 11: [2017-05-12 10:17:00.214677] mirserver: Selected input driver: 
mir:stub-input (version: 0.27.0)
  10:17:03 11: [2017-05-12 10:17:00.248791] mirserver: Mir version 0.27.0
  10:17:05 11: [2017-05-12 10:17:00.329566] mirserver: Initial display 
configuration:
  10:17:06 11: [2017-05-12 10:17:00.329980] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  10:17:07 11: [2017-05-12 10:17:00.330253] mirserver: . |_ Physical size 0.0" 
0x0mm
  10:17:08 11: [2017-05-12 10:17:00.330468] mirserver: . |_ Power is on
  10:17:09 11: [2017-05-12 10:17:00.330732] mirserver: . |_ Current mode 
1600x1600 60.00Hz
  10:17:09 11: [2017-05-12 10:17:00.331030] mirserver: . |_ Preferred mode 
1600x1600 60.00Hz
  10:17:09 11: [2017-05-12 10:17:00.331292] mirserver: . |_ Orientation normal
  10:17:09 11: [2017-05-12 10:17:00.331542] mirserver: . |_ Logical size 
1600x1600
  10:17:09 11: [2017-05-12 10:17:00.331760] mirserver: . |_ Logical position 
+0+0
  10:17:09 11: [2017-05-12 10:17:00.331989] mirserver: . |_ Scaling factor: 1.00
  10:17:10 11: 
/<>/mir-0.26.1+17.04.20170209.1+xenial4731bzr4168/tests/acceptance-tests/test_prompt_session_client_api.cpp:374:
 Failure
  10:17:10 11: Value of: wait_for_callback(std::chrono::milliseconds(500))
  10:17:10 11: Actual: false
  10:17:10 11: Expected: true
  10:17:10 11: 
/<>/mir-0.26.1+17.04.20170209.1+xenial4731bzr4168/tests/acceptance-tests/test_prompt_session_client_api.cpp:375:
 Failure
  10:17:10 11: Value of: actual_fds.size()
  10:17:10 11: Expected: is equal to 3
  10:17:11 11: Actual: 0 (of type unsigned int)
  10:17:11 11: [2017-05-12 10:17:07.544093] mirserver: Stopping
  10:17:11 11: [ FAILED ] 
PromptSessionClientAPI.can_get_fds_for_prompt_providers (8287 ms)

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

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

[Touch-packages] [Bug 1660039] Re: [FAILED] mir_demo_client_pointer_confinement in smoke tests

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [FAILED] mir_demo_client_pointer_confinement in smoke tests

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

Bug description:
  04:25:54 mir_demo_server --test-timeout=3 --test-client 
mir_demo_client_pointer_confinement
  
  04:25:55 Mir chose pixel format 1.
  04:25:55 Using pixel format 2.
  04:25:55 Current active output is 540x960 +0+0
  04:25:55 Window is on output 1: 241 DPI, scale 1.0x, phone form factor, 
66.58Hz
  04:25:55 Resized to 270x480
  04:25:58 Signal 15 received. Good night.
  04:25:59 [2017-01-28 04:25:59.031006] server_example_test_client.cpp: Client 
exited successfully
  04:25:59 [2017-01-28 04:25:59.031488] mirserver: Stopping
  04:26:10 /home/phablet/mir-testrunner/mir-smoke-test-runner.sh: line 24: 
12507 Segmentation fault (core dumped) ${root}mir_demo_server 
--test-timeout=$timeout --test-client $root$client
  04:26:10 I: [FAILED] mir_demo_client_pointer_confinement

  https://mir-jenkins.ubuntu.com/job/device-runtests-
  mir/2880/device_type=krillin/consoleFull

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

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

[Touch-packages] [Bug 1663288] Re: std::exception::what: Image is too big for GBM cursor buffer

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  std::exception::what: Image is too big for GBM cursor buffer

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

Bug description:
  When using:

  auto stream = mir_connection_create_buffer_stream_sync(connection,
  500, 166, mir_pixel_format_argb_, mir_buffer_usage_software);

  //Fill in buffer stream

  auto configuration = 
mir_cursor_configuration_from_buffer_stream(bufferStream, 0, 0);
  mir_window_configure_cursor(window, configuration);

  In the server, this results in:

  [2017-02-09 09:49:52.789913]  evdev: Failure processing input event 
received from libinput: 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/platforms/mesa/server/kms/cursor.cpp(150):
 Throw in function void 
mir::graphics::mesa::Cursor::pad_and_write_image_data_locked(const 
std::lock_guard&, const mir::graphics::CursorImage&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Image is too big for GBM cursor buffer

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

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

[Touch-packages] [Bug 1655374] Re: mir-client-debug-extension pkgconfig file has wrong library name

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  mir-client-debug-extension pkgconfig file has wrong library name

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

Bug description:
  Relevant exerpt:

  Libs: -L${libdir} -lmirclient-debug

  But actual file is /usr/lib/x86_64-linux-gnu/libmirclient-debug-
  extension.so

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

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

[Touch-packages] [Bug 1680069] Re: CI test failure in TestTouchspotVisualizations.touchspots_follow_gesture

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  CI test failure in
  TestTouchspotVisualizations.touchspots_follow_gesture

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

Bug description:
  [ RUN ] TestTouchspotVisualizations.touchspots_follow_gesture
  15: [2017-04-05 08:31:32.091583] mirplatform: Found graphics driver: 
mir:mesa-x11 (version 0.27.0)
  15: [2017-04-05 08:31:32.100130] mirplatform: Found graphics driver: 
mir:android (version 0.27.0)
  15: [2017-04-05 08:31:32.122274] mirplatform: Found graphics driver: 
mir:mesa-kms (version 0.27.0)
  15: [2017-04-05 08:31:32.123563] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.27.0)
  15: [2017-04-05 08:31:32.124924] mirplatform: Found graphics driver: 
throw-on-creation (version 0.27.0)
  15: [2017-04-05 08:31:32.397386] mirserver: Selected input driver: 
mir:stub-input (version: 0.27.0)
  15: [2017-04-05 08:31:32.423077] mirserver: Mir version 0.27.0
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:192:
 Failure
  15: Mock function called more times than expected - returning directly.
  15: Function call: visualize_touches(@0xbde54d0 { 12-byte object <00-00 00-00 
00-00 00-00 00-00 80-3F> })
  15: Expected: to be called once
  15: Actual: called twice - over-saturated and active
  15: [2017-04-05 08:31:32.506774] mirserver: Initial display configuration:
  15: [2017-04-05 08:31:32.507052] mirserver: CMakeFiles CTestTestfile.cmake 
Makefile client cmake_install.cmake compositor graphics input 
mir_integration_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed process shell Output 1: VGA connected, 
used
  15: [2017-04-05 08:31:32.507270] mirserver: . |_ Physical size 0.0" 0x0mm
  15: [2017-04-05 08:31:32.507488] mirserver: . |_ Power is on
  15: [2017-04-05 08:31:32.507758] mirserver: . |_ Current mode 1600x1600 
60.00Hz
  15: [2017-04-05 08:31:32.508021] mirserver: . |_ Preferred mode 1600x1600 
60.00Hz
  15: [2017-04-05 08:31:32.508242] mirserver: . |_ Orientation normal
  15: [2017-04-05 08:31:32.508487] mirserver: . |_ Logical size 1600x1600
  15: [2017-04-05 08:31:32.508734] mirserver: . |_ Logical position +0+0
  15: [2017-04-05 08:31:32.508969] mirserver: . |_ Scaling factor: 1.00
  15: unknown file: Failure
  15: 
  15: Unexpected mock function call - returning directly.
  15: Function call: visualize_touches(@0xbde54d0 {})
  15: Google Mock tried the following 4 expectations, but none matched:
  15: 
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:191:
 tried expectation #0: EXPECT_CALL(server_configuration.mock_visualizer, 
visualize_touches(NoSpots()))...
  15: Expected: the expectation is active
  15: Actual: it is retired
  15: Expected: to be called at most once
  15: Actual: never called - satisfied and retired
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:192:
 tried expectation #1: EXPECT_CALL(server_configuration.mock_visualizer, 
visualize_touches(TouchedSpotsAt(expected_spots_1)))...
  15: Expected arg #0: touched spots at { (0, 0) }
  15: Actual: {}
  15: Expected: to be called once
  15: Actual: called twice - over-saturated and active
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:193:
 tried expectation #2: EXPECT_CALL(server_configuration.mock_visualizer, 
visualize_touches(TouchedSpotsAt(expected_spots_2)))...
  15: Expected arg #0: touched spots at { (1599, 1599) }
  15: Actual: {}
  15: Expected: to be called once
  15: Actual: never called - unsatisfied and active
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:194:
 tried expectation #3: EXPECT_CALL(server_configuration.mock_visualizer, 
visualize_touches(NoSpots()))...
  15: Expected: all pre-requisites are satisfied
  15: Actual: the following immediate pre-requisites are not satisfied:
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:193:
 pre-requisite #0
  15: (end of pre-requisites)
  15: Expected: to be called once
  15: Actual: never called - unsatisfied and active
  15: unknown file: Failure
  15: C++ exception with description "Timeout" thrown in TearDown().
  15: 
/<>/mir-0.26.1+17.04.20170209.1+zesty4580bzr4141/tests/integration-tests/test_touchspot_visualization.cpp:193:
 Failure
  15: Actual function call count doesn't match 
EXPECT_CALL(server_configuration.mock_visualizer, 
visualize_touches(TouchedSpotsAt(expected_spots_2)))...
  15: Expected: to be called once
  15: 

[Touch-packages] [Bug 1647416] Re: GL clients never show up in VMware [VMWare: No 3D enabled (0, Success).]

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  GL clients never show up in VMware [VMWare: No 3D enabled (0,
  Success).]

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

Bug description:
  Steps to reproduce:
  * install vmware workstation player
  * setup an ubuntu image with the zesty iso image for amd64
  * apt install mir-demos
  * run sudo  miral-shell --arw-file --vt 2 -f /tmp/mir_socket
  * mir_demo_client_eglplasma -m /tmp/mir_socket

  The client application exits and in the terminal output you should see:
  VMWare: No 3D enabled (0, Success).

  That message is from the mesa vmware driver:

  
https://github.com/mesa3d/mesa/blob/master/src/gallium/winsys/svga/drm/vmw_screen_ioctl.c#L880

  The ioctl seems to complete successfully but yields the wrong result.

  The same can be experienced with miral-shell running in X11.
  GL clients within X11 work. EGL on DRM seems to work - since  
mir_proving_server on DRM works too.

  Update: The problem seems to be related to dmabuf fds. The error
  message mentioned above does not seem to stop the egl initialization.
  So later in the process when mirclient receives the buffers the driver
  fails to import the dmabuf fds. So maybe the interrupted
  initialization leaves the egl structures in a state incapable to
  perform the dmabuf fd to drm handle mapping.

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

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

[Touch-packages] [Bug 1657639] Re: Valgrind errors in CI: Conditional jump or move depends on uninitialised value(s) ... mir_test_framework::ServerRunner::start_mir_server()

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Valgrind errors in CI: Conditional jump or move depends on
  uninitialised value(s) ...
  mir_test_framework::ServerRunner::start_mir_server()

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

Bug description:
  04:25:55 15: [ RUN ] 
FocusSelection.when_client_connects_shell_is_notified_of_session
  04:25:58 15: [2017-01-19 04:25:57.802102] mirplatform: Found graphics driver: 
mir:android (version 0.26.0)
  04:25:58 15: [2017-01-19 04:25:58.140960] mirplatform: Found graphics driver: 
mir:mesa-kms (version 0.26.0)
  04:25:58 15: [2017-01-19 04:25:58.145057] mirplatform: Found graphics driver: 
mir:mesa-x11 (version 0.26.0)
  04:25:58 15: [2017-01-19 04:25:58.263957] mirplatform: Found graphics driver: 
throw-on-creation (version 0.26.0)
  04:25:58 15: [2017-01-19 04:25:58.267747] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.26.0)
  04:26:08 15: [2017-01-19 04:26:08.636322] mirserver: Mir version 0.26.0
  04:26:10 15: [2017-01-19 04:26:10.457557] mirserver: Initial display 
configuration:
  04:26:10 15: [2017-01-19 04:26:10.469071] mirserver: Output 1: VGA connected, 
used
  04:26:10 15: [2017-01-19 04:26:10.490347] mirserver: Physical size 0.0" 0x0mm
  04:26:10 15: [2017-01-19 04:26:10.567493] mirserver: Power is on
  04:26:10 15: [2017-01-19 04:26:10.594867] mirserver: Current mode 1600x1600 
60.00Hz
  04:26:11 15: [2017-01-19 04:26:11.428953] mirserver: Preferred mode 1600x1600 
60.00Hz
  04:26:13 15: [2017-01-19 04:26:13.065882] mirserver: Orientation normal
  04:26:13 15: [2017-01-19 04:26:13.071502] mirserver: Logical size 1600x1600
  04:26:13 15: [2017-01-19 04:26:13.159336] mirserver: Logical position +0+0
  04:26:13 15: ==15173== Thread 2:
  04:26:13 15: ==15173== Conditional jump or move depends on uninitialised 
value(s)
  04:26:13 15: ==15173== at 0x6FDBD55: pthread_mutex_lock 
(pthread_mutex_lock.c:71)
  04:26:13 15: ==15173== by 0x11CD392: __gthread_mutex_lock(pthread_mutex_t*) 
(gthr-default.h:748)
  04:26:13 15: ==15173== by 0x11D040B: std::mutex::lock() (mutex:135)
  04:26:13 15: ==15173== by 0x12C9D45: 
std::lock_guard::lock_guard(std::mutex&) (mutex:386)
  04:26:13 15: ==15173== by 0x169DD82: 
mir_test_framework::ServerRunner::start_mir_server()::{lambda()#1}::operator()()
 const::{lambda(mir::DisplayServer&)#1}::operator()(mir::DisplayServer) 
const::{lambda()#1}::operator()() const (server_runner.cpp:117)
  04:26:13 15: ==15173== by 0x169E5EF: std::_Function_handler::_M_invoke(std::_Any_data const&) (functional:1871)
  04:26:13 15: ==15173== by 0x12F9EED: std::function::operator()() 
const (functional:2267)
  04:26:13 15: ==15173== by 0x13F6B5F: mir::GLibMainLoop::enqueue(void const*, 
std::function const&)::{lambda()#1}::operator()() const 
(glib_main_loop.cpp:237)
  04:26:13 15: ==15173== by 0x13F9169: std::_Function_handler 
const&)::{lambda()#1}>::_M_invoke(std::_Any_data const&) (functional:1871)
  04:26:13 15: ==15173== by 0x12F9EED: std::function::operator()() 
const (functional:2267)
  04:26:14 15: ==15173== by 0x13FF12A: 
mir::detail::add_server_action_gsource(_GMainContext*, void const*, 
std::function const&, std::function 
const&)::ServerActionGSource::dispatch(_GSource*, int (*)(void*), void*) 
(glib_main_loop_sources.cpp:217)
  04:26:14 15: ==15173== by 0x5B891A6: g_main_context_dispatch (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
  04:26:14 15: ==15173== by 0x5B893FF: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
  04:26:14 15: ==15173== by 0x5B894AB: g_main_context_iteration (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
  04:26:14 15: ==15173== by 0x13F5D72: mir::GLibMainLoop::run() 
(glib_main_loop.cpp:145)
  04:26:14 15: ==15173== by 0x13E0B69: mir::DisplayServer::run() 
(display_server.cpp:216)
  04:26:14 15: ==15173== by 0x13DF939: mir::run_mir(mir::ServerConfiguration&, 
std::function, std::function const&) 
(run_mir.cpp:110)
  04:26:14 15: ==15173== by 0x13DF553: mir::run_mir(mir::ServerConfiguration&, 
std::function) (run_mir.cpp:68)
  04:26:14 15: ==15173== by 0x169DE94: 
mir_test_framework::ServerRunner::start_mir_server()::{lambda()#1}::operator()()
 const (server_runner.cpp:121)
  04:26:14 15: ==15173== by 0x169FA8B: void 
std::_Bind_simple::_M_invoke<>(std::_Index_tuple<>) (functional:1531)
  04:26:14 15: ==15173== by 0x169F9E1: 
std::_Bind_simple::operator()() (functional:1520)
  04:26:14 15: ==15173== by 0x169F971: 
std::thread::_Impl >::_M_run() (thread:115)
  04:26:14 15: ==15173== by 0x67E8C7F: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  04:26:14 

[Touch-packages] [Bug 1659310] Re: With Mir 0.26 test silo, when relaunching an application during/after invoking a trust session causes a crash

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  With Mir 0.26 test silo, when relaunching an application during/after
  invoking a trust session causes a crash

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  What happened:
  1) Installed Silo 2369 [0] on Xenial + Overlay using Unity8 Deb edition
  2) Launched an application
  3) Invoked a trust session within that application
  4) Optional: Closed the trust session
  5) Closed the application
  6) Launched the same application from the dash
  7) The whole of Unity8 froze (and I assume crashed)

  What I expected to happen:
  At step 7 for Unity8 not to freeze.

  Two crash logs:
  webbrowser - http://pastebin.ubuntu.com/23863224/
  Kate - http://pastebin.ubuntu.com/23859188/

  For the webbrowser crash I didn't close the trust session (step #4).

  For Kate I *think* I did, but will confirm collecting some more
  crashes and noting what I have clicked.

  
  0 - https://bileto.ubuntu.com/#/ticket/2369

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

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

[Touch-packages] [Bug 1664311] Re: Lifting ctrl and fn keys at the same time while tapping an arrow key rapidly, can cause keys to become stuck

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Lifting ctrl and fn keys at the same time while tapping an arrow key
  rapidly, can cause keys to become stuck

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

Bug description:
  I'm in a terminal and I usually use Ctrl + Arrows or Home/End (which
  on my keyboard are Fn+Left Arrow and Fn+Right Arrow), however when
  pressing a certain key sequences quickly together the keys can become
  stuck, forcing the cursor to one end of the terminal. Also note it is
  not just related to the terminal, the cursor is forced to one end of
  any input within the scopes or other apps

  What happened:
  1) Focus a text field with a few words in it
  2) Press and hold both Ctrl + Fn
  3) Tap the RightArrow rapidly
  4) While tapping release Ctrl + Fn together (keep tapping the RightArrow a 
bit longer than the ctrl + fn - up to a second longer)
  5) Sometimes the cursor will jump to the right of the field and is 'stuck'
  6) Depending on timing of lifting the keys at the same time, you then have to 
press Fn+RightArrow or Ctrl+RightArrow to make it 'unstuck'

  Note: this is down to timing so doesn't always happen

  What I expected to happen:
  At #5 for the cursor not to become stuck due to the system thinking the key 
is pressed.

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

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

[Touch-packages] [Bug 1668147] Re: [ FAILED ] TestClientCursorAPI.cursor_passed_through_nested_server

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ] TestClientCursorAPI.cursor_passed_through_nested_server

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

Bug description:
  22:27:10 [ RUN ] TestClientCursorAPI.cursor_passed_through_nested_server
  ...
  22:27:10 
/<>/mir-0.26.0+zesty4155bzr4052/tests/acceptance-tests/test_client_cursor_api.cpp:677:
 Failure
  22:27:10 Actual function call count doesn't match EXPECT_CALL(cursor, 
hide())...
  22:27:10 Expected: to be called once
  22:27:10 Actual: never called - unsatisfied and active
  22:27:10 [2017-02-23 22:24:26.184260] mirserver: Stopping
  22:27:10 [2017-02-23 22:24:26.338221] mirserver: Stopping
  22:27:10 [ FAILED ] TestClientCursorAPI.cursor_passed_through_nested_server 
(62544 ms)

  Looks like bug 1525003

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

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

[Touch-packages] [Bug 1659190] Re: [ FAILED ] DemoPrivateProtobuf.client_receives_result

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ] DemoPrivateProtobuf.client_receives_result

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

Bug description:
  05:13:40 15: [ RUN ] DemoPrivateProtobuf.client_receives_result
  ...
  05:13:42 15: 
/<>/mir-0.26.0+zesty3842bzr3988/tests/integration-tests/test_protobuf.cpp:315:
 Failure
  05:13:42 15: Value of: result.value()
  05:13:42 15: Expected: is equal to 0x13d2740 pointing to "virtual void 
DemoPrivateProtobuf_client_receives_result_Test::TestBody()"
  05:13:42 15: Actual: ""
  05:13:42 15: [ FAILED ] DemoPrivateProtobuf.client_receives_result (2407 ms)

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

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

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

[Touch-packages] [Bug 1646302] Re: [ FAILED ] NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ]
  
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset

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

Bug description:
  It seems bug 1591354 wasn't really fixed...

  18:39:24 11: [ RUN ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
  ...
  18:39:30 11: 
/<>/mir-0.25.0+xenial3037bzr3844/tests/acceptance-tests/test_nested_mir.cpp:1420:
 Failure
  18:39:30 11: Value of: condition.raised()
  18:39:30 11: Actual: false
  18:39:30 11: Expected: true
  18:39:30 11: 
/<>/mir-0.25.0+xenial3037bzr3844/tests/acceptance-tests/test_nested_mir.cpp:1414:
 Failure
  18:39:30 11: Actual function call count doesn't match 
EXPECT_CALL(*the_mock_display_configuration_report(), 
configuration_applied(Pointee(mt::DisplayConfigMatches(expected_config...
  18:39:30 11: Expected: to be called once
  18:39:30 11: Actual: never called - unsatisfied and active
  ...
  18:39:30 11: [ FAILED ] 
NestedServer.given_nested_server_set_base_display_configuration_when_monitor_plugged_in_configuration_is_reset
 (6721 ms)

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

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

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

[Touch-packages] [Bug 1636901] Re: Seamless mouse integration does not work with Mir in a VM

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  Seamless mouse integration does not work with Mir in a VM

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse integration is off using virt-manager/viewer/QVC/Spice with
  Unity8/mir as the guest.

  Steps to reproduce;
  1. Install in a virt-manager VM with QVC and Spice enabled.
  2. Login to Unity7, notice how mouse flows seamlessly between Host and Guest 
machine.
  3. Login to Unity8. Note how you can't bring the mouse to the top of the 
screen (or the far left usually).  Specifically it goes back to the host too 
quickly.

  The box that you can move in does change a bit (AFAICT).  Try
  fullscreen to see.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 26 11:32:57 2016
  InstallationDate: Installed on 2016-08-23 (64 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160823)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1700128] Re: [ FAILED ] NestedServer.display_orientation_changes_are_forwarded_to_host

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ]
  NestedServer.display_orientation_changes_are_forwarded_to_host

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

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

  12:06:59 11: [ RUN ] 
NestedServer.display_orientation_changes_are_forwarded_to_host
  12:06:59 11: [2017-06-23 12:06:59.314029] mirserver: Starting
  12:06:59 11: [2017-06-23 12:06:59.319872] mirserver: Selected driver: 
mir:stub-graphics (version 0.27.0)
  12:06:59 11: [2017-06-23 12:06:59.620966] mirserver: Using software cursor
  12:06:59 11: [2017-06-23 12:06:59.699891] mirserver: Selected input driver: 
mir:stub-input (version: 0.27.0)
  12:06:59 11: [2017-06-23 12:06:59.754930] mirserver: Mir version 0.27.0
  12:06:59 11: [2017-06-23 12:06:59.766681] mirserver: Initial display 
configuration:
  12:06:59 11: [2017-06-23 12:06:59.767200] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  12:06:59 11: [2017-06-23 12:06:59.767480] mirserver: . |_ Physical size 0.0" 
0x0mm
  12:06:59 11: [2017-06-23 12:06:59.767705] mirserver: . |_ Power is on
  12:06:59 11: [2017-06-23 12:06:59.767975] mirserver: . |_ Current mode 
640x480 60.00Hz
  12:06:59 11: [2017-06-23 12:06:59.768245] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  12:06:59 11: [2017-06-23 12:06:59.768466] mirserver: . |_ Orientation normal
  12:06:59 11: [2017-06-23 12:06:59.768713] mirserver: . |_ Logical size 640x480
  12:06:59 11: [2017-06-23 12:06:59.768940] mirserver: . |_ Logical position 
+0+0
  12:06:59 11: [2017-06-23 12:06:59.769167] mirserver: . |_ Scaling factor: 1.00
  12:06:59 11: [2017-06-23 12:06:59.867155] mirserver: Starting
  12:07:01 11: [2017-06-23 12:07:01.245425] mirserver: Using nested cursor
  12:07:01 11: [2017-06-23 12:07:01.442669] mirserver: Mir version 0.27.0
  12:07:01 11: [2017-06-23 12:07:01.703321] mirserver: Initial display 
configuration:
  12:07:01 11: [2017-06-23 12:07:01.704397] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  12:07:02 11: [2017-06-23 12:07:01.704594] mirserver: . |_ Physical size 0.0" 
0x0mm
  12:07:04 11: [2017-06-23 12:07:01.704734] mirserver: . |_ Power is on
  12:07:06 11: [2017-06-23 12:07:01.704927] mirserver: . |_ Current mode 
640x480 60.00Hz
  12:07:07 11: [2017-06-23 12:07:01.705103] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  12:07:09 11: [2017-06-23 12:07:01.705245] mirserver: . |_ Orientation normal
  12:07:09 11: [2017-06-23 12:07:01.705403] mirserver: . |_ Logical size 640x480
  12:07:09 11: [2017-06-23 12:07:01.705543] mirserver: . |_ Logical position 
+0+0
  12:07:10 11: [2017-06-23 12:07:01.705690] mirserver: . |_ Scaling factor: 1.00
  12:07:10 11: [2017-06-23 12:07:03.071555] mirserver: Session 
{anonymous}::Client::Client({anonymous}::NestedMirRunner&) applied display 
configuration
  12:07:10 11: [2017-06-23 12:07:03.072282] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  12:07:10 11: [2017-06-23 12:07:03.072475] mirserver: . |_ Physical size 0.0" 
0x0mm
  12:07:10 11: [2017-06-23 12:07:03.072616] mirserver: . |_ Power is on
  12:07:10 11: [2017-06-23 12:07:03.072790] mirserver: . |_ Current mode 
640x480 60.00Hz
  12:07:10 11: [2017-06-23 12:07:03.072959] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  12:07:10 11: [2017-06-23 12:07:03.073097] mirserver: . |_ Orientation left
  12:07:11 11: [2017-06-23 12:07:03.075131] mirserver: . |_ Logical size 480x640
  12:07:11 11: [2017-06-23 12:07:03.075306] mirserver: . |_ Logical position 
+0+0
  12:07:13 11: [2017-06-23 12:07:03.075467] mirserver: . |_ Scaling factor: 1.00
  12:07:13 11: [2017-06-23 12:07:09.372041] mirserver: Session nested-mir@:none 
applied display configuration
  12:07:15 11: [2017-06-23 12:07:09.372407] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  12:07:15 11: [2017-06-23 12:07:09.372594] mirserver: . |_ Physical size 0.0" 
0x0mm
  12:07:15 11: [2017-06-23 12:07:09.372734] mirserver: . |_ Power is on
  12:07:16 11: [2017-06-23 12:07:09.372908] mirserver: . |_ Current mode 
640x480 60.00Hz
  12:07:17 11: [2017-06-23 12:07:09.373179] mirserver: . |_ 

[Touch-packages] [Bug 1680378] Re: Xmir hangs in mir_buffer_stream_get_graphics_region() from xmir_input_set_cursor()

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Xmir hangs in mir_buffer_stream_get_graphics_region() from
  xmir_input_set_cursor()

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

Bug description:
  Xmir freezes in mir_buffer_stream_get_graphics_region() from
  xmir_input_set_cursor()

  Seems to happen a lot when testing Firefox and Chrome when
  entering/leaving the address bar...

  (gdb) bt
  #0  pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f5ea91e3c5c in 
std::condition_variable::wait(std::unique_lock&) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x7f5eac25b6b2 in 
std::condition_variable::wait::ReadLock::ReadLock(mir::client::PromiseStateBase&)::{lambda()#1}>(std::unique_lock&, 
mir::client::PromiseStateBase::ReadLock::ReadLock(mir::client::PromiseStateBase&)::{lambda()#1}) ()
  at /usr/include/c++/6/condition_variable:99
  #3  __base_ctor  (parent=..., this=0x7fff74877420)
  at ./src/client/no_tls_future-inl.h:136
  #4  mir::client::PromiseStateBase::ensure_read_context() () at ./src/client/no_tls_future-inl.h:152
  #5  get_value (this=0x55de6688f830) at ./src/client/no_tls_future-inl.h:223
  #6  get (this=0x7f5e9c008160) at ./src/client/no_tls_future-inl.h:354
  #7  
mir::client::BufferDepository::advance_current_buffer(std::unique_lock&)
 (this=this@entry=0x7f5e9c008160, lk=...)
  at ./src/client/buffer_stream.cpp:166
  #8  0x7f5eac25f9ed in current_buffer_id (this=)
  at ./src/client/buffer_stream.cpp:183
  #9  get_current_buffer (this=0x7f5e9c007f40)
  at ./src/client/buffer_stream.cpp:400
  #10 0x7f5eac25f517 in secure_for_cpu_write (this=0x7f5e9c007f40)
  at ./src/client/buffer_stream.cpp:419
  #11 0x7f5eac263f28 in mir_buffer_stream_get_graphics_region (
  buffer_stream=buffer_stream@entry=0x7f5e9c007f48, 
  region_out=region_out@entry=0x7fff748775d0)
  at ./src/client/mir_buffer_stream_api.cpp:149
  #12 0x55de647da90e in xmir_input_set_cursor (cursor=0x55de6687ff60, 
  xmir_input=, xmir_input=)
  at xmir-cursor.c:108
  #13 0x55de64829eab in miPointerUpdateSprite (pDev=0x55de66621c10)
  at mipointer.c:468
  #14 0x55de6482a0fa in miPointerDisplayCursor (pDev=0x55de66621c10, 
  pScreen=0x55de65c775b0, pCursor=0x55de6687ff60) at mipointer.c:206
  #15 0x55de64816bf1 in CursorDisplayCursor (pDev=0x55de66621c10, 
  pScreen=0x55de65c775b0, pCursor=0x55de6687ff60) at cursor.c:150
  #16 0x55de6489f4e0 in AnimCurDisplayCursor (pDev=0x55de66621c10, 
  pScreen=0x55de65c775b0, pCursor=0x55de6687ff60) at animcur.c:220
  #17 0x55de64910cc8 in ChangeToCursor (pDev=0x55de66621c10, 
  cursor=0x55de6687ff60) at events.c:937
  #18 0x55de64912107 in WindowHasNewCursor (pWin=pWin@entry=0x55de66840be0)
  at events.c:3369
  #19 0x55de64939740 in ChangeWindowAttributes (pWin=0x55de66840be0, 
  vmask=, vlist=vlist@entry=0x55de6690e17c, 
  client=client@entry=0x55de667e37e0) at window.c:1561
  #20 0x55de64901bed in ProcChangeWindowAttributes (client=0x55de667e37e0)
  at dispatch.c:726
  #21 0x55de64907ed5 in Dispatch () at dispatch.c:479
  #22 0x55de6490be58 in dix_main (argc=6, argv=0x7fff74877a58, 
  envp=) at main.c:287
  #23 0x7f5eaa4bf3f1 in __libc_start_main (main=0x55de647d5f70 , 
  argc=6, argv=0x7fff74877a58, init=, fini=, 
  rtld_fini=, stack_end=0x7fff74877a48)
  at ../csu/libc-start.c:291
  #24 0x55de647d5faa in _start ()

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

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

[Touch-packages] [Bug 1194057] Re: mir_motion_action_move not received for thinkpad buttons (only for the clickpad)

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  mir_motion_action_move not received for thinkpad buttons (only for the
  clickpad)

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

Bug description:
  Running mir_demo_client_fingerpaint on a Thinkpad, it does not paint
  anything while I hold down button 1 (left button). It only seems to
  respond to the clickpad.

  This makes it seem like something needs work in the android input
  translation.

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

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

[Touch-packages] [Bug 1706050] Re: [testsfail] NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [testsfail]
  
NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration

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

Bug description:
  08:52:06 9: [ RUN ] 
NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration
  08:52:06 9: [2017-07-24 08:52:06.185457] mirserver: Starting
  08:52:06 9: [2017-07-24 08:52:06.186524] mirserver: Selected driver: 
mir:stub-graphics (version 0.27.0)
  08:52:06 9: [2017-07-24 08:52:06.196052] mirserver: Using software cursor
  08:52:06 9: [2017-07-24 08:52:06.430690] mirserver: Selected input driver: 
mir:stub-input (version: 0.27.0)
  08:52:06 9: [2017-07-24 08:52:06.438641] mirserver: Mir version 0.27.0
  08:52:06 9: [2017-07-24 08:52:06.443482] mirserver: Initial display 
configuration:
  08:52:06 9: [2017-07-24 08:52:06.443704] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  08:52:06 9: [2017-07-24 08:52:06.443988] mirserver: . |_ Physical size 0.0" 
0x0mm
  08:52:06 9: [2017-07-24 08:52:06.444144] mirserver: . |_ Power is on
  08:52:06 9: [2017-07-24 08:52:06.444331] mirserver: . |_ Current mode 640x480 
60.00Hz
  08:52:06 9: [2017-07-24 08:52:06.444514] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  08:52:06 9: [2017-07-24 08:52:06.444669] mirserver: . |_ Orientation normal
  08:52:06 9: [2017-07-24 08:52:06.444828] mirserver: . |_ Logical size 640x480
  08:52:06 9: [2017-07-24 08:52:06.444983] mirserver: . |_ Logical position +0+0
  08:52:06 9: [2017-07-24 08:52:06.445145] mirserver: . |_ Scaling factor: 1.00
  08:52:06 9: [2017-07-24 08:52:06.463562] mirserver: Starting
  08:52:07 9: [2017-07-24 08:52:06.995460] mirserver: Using nested cursor
  08:52:07 9: [2017-07-24 08:52:07.254892] mirserver: Mir version 0.27.0
  08:52:07 9: [2017-07-24 08:52:07.423622] mirserver: Initial display 
configuration:
  08:52:07 9: [2017-07-24 08:52:07.424162] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  08:52:07 9: [2017-07-24 08:52:07.424372] mirserver: . |_ Physical size 0.0" 
0x0mm
  08:52:07 9: [2017-07-24 08:52:07.424529] mirserver: . |_ Power is on
  08:52:07 9: [2017-07-24 08:52:07.424717] mirserver: . |_ Current mode 640x480 
60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.424895] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.425049] mirserver: . |_ Orientation normal
  08:52:07 9: [2017-07-24 08:52:07.425207] mirserver: . |_ Logical size 640x480
  08:52:07 9: [2017-07-24 08:52:07.425361] mirserver: . |_ Logical position +0+0
  08:52:07 9: [2017-07-24 08:52:07.425522] mirserver: . |_ Scaling factor: 1.00
  08:52:07 9: [2017-07-24 08:52:07.743892] mirserver: Session (anonymous 
namespace)::Client::Client((anonymous namespace)::NestedMirRunner &) applied 
display configuration
  08:52:07 9: [2017-07-24 08:52:07.744240] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  08:52:07 9: [2017-07-24 08:52:07.744437] mirserver: . |_ Physical size 0.0" 
0x0mm
  08:52:07 9: [2017-07-24 08:52:07.744594] mirserver: . |_ Power is on
  08:52:07 9: [2017-07-24 08:52:07.744780] mirserver: . |_ Current mode 640x480 
60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.744965] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.745126] mirserver: . |_ Orientation normal
  08:52:07 9: [2017-07-24 08:52:07.745289] mirserver: . |_ Logical size 640x480
  08:52:07 9: [2017-07-24 08:52:07.745455] mirserver: . |_ Logical position +0+0
  08:52:07 9: [2017-07-24 08:52:07.745646] mirserver: . |_ Scaling factor: 1.00
  08:52:07 9: [2017-07-24 08:52:07.749309] mirserver: New display configuration:
  08:52:07 9: [2017-07-24 08:52:07.749661] mirserver: CMakeFiles 
CTestTestfile.cmake Makefile cmake_install.cmake 
mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags 
precompiled.hpp.compileflags.processed Output 1: VGA connected, used
  08:52:07 9: [2017-07-24 08:52:07.751157] mirserver: . |_ Physical size 0.0" 
0x0mm
  08:52:07 9: [2017-07-24 08:52:07.751446] mirserver: . |_ Power is on
  08:52:07 9: [2017-07-24 08:52:07.753406] mirserver: . |_ Current mode 640x480 
60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.759606] mirserver: . |_ Preferred mode 
640x480 60.00Hz
  08:52:07 9: [2017-07-24 08:52:07.759818] mirserver: . |_ 

[Touch-packages] [Bug 1720391] Re: Client input receiver report is never called

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Client input receiver report is never called

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

Bug description:
  mcl::DefaultConnectionConfiguration::the_input_receiver_report() is
  never used, so the input receiver report is never called.

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

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

[Touch-packages] [Bug 1591376] Re: Crash caused by exception thown from DMABufTextureBinder::ensure_egl_image()

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Crash caused by exception thown from
  DMABufTextureBinder::ensure_egl_image()

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

Bug description:
  The most reliable way I have to reproduce is:

  1. Run (Mir-on-X) $ miral-shell --window-manager tiling
  2. Run a script that iterates over mir_demo_client_* launching all our demo 
clients.

  The following exception causes a segfault in report_exception() -
  because by then the library has been unloaded:

  Thread 3 "Mir/Comp" hit Catchpoint 1 (exception thrown), 0x76ee58bd 
in __cxa_throw ()
 from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  (gdb) bt
  #0  0x76ee58bd in __cxa_throw () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #1  0x718275be in throw_exception (e=...) at 
/usr/include/boost/throw_exception.hpp:69
  #2  
boost::exception_detail::throw_exception_(std::system_error 
const&, char const*, char const*, int) [clone .constprop.114] (x=..., 
  current_function=0x7182b2e0 <(anonymous 
namespace)::DMABufTextureBinder::ensure_egl_image()::__PRETTY_FUNCTION__> 
"virtual void {anonymous}::DMABufTextureBinder::ensure_egl_image()", 
file=, line=)
  at /usr/include/boost/throw_exception.hpp:86
  #3  0x71822967 in (anonymous 
namespace)::DMABufTextureBinder::ensure_egl_image() [clone .lto_priv.250] (
  this=)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/platforms/mesa/server/common/buffer_allocator.cpp:147
  #4  0x7182308e in (anonymous 
namespace)::EGLImageBufferTextureBinder::gl_bind_to_texture() [clone 
.lto_priv.247] (
  this=0x7fffe8509c50) at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/platforms/mesa/server/common/buffer_allocator.cpp:71
  #5  mir::graphics::mesa::GBMBuffer::gl_bind_to_texture() (this=)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/platforms/mesa/server/common/gbm_buffer.cpp:166
  #6  0x765e402f in 
mir::gl::RecentlyUsedCache::load(mir::graphics::Renderable const&) 
(this=, 
  renderable=...) at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/gl/recently_used_cache.cpp:45
  #7  0x765fd2f9 in 
mir::renderer::gl::Renderer::draw(mir::graphics::Renderable const&, 
mir::renderer::gl::Renderer::Program const&) const 
(this=this@entry=0x7fffe80008c0, renderable=..., prog=...)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/renderers/gl/renderer.cpp:247
  #8  0x765fd590 in 
mir::renderer::gl::Renderer::render(std::vector > const&) const 
(this=0x7fffe80008c0, renderables=...)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/renderers/gl/renderer.cpp:205
  #9  0x765a30be in composite (this=this@entry=0x7fffe84c76c0, 
  scene_elements=scene_elements@entry=)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/compositor/default_display_buffer_compositor.cpp:83
  #10 0x765a1076 in mir::compositor::CompositingFunctor::operator()() 
(this=0x7c4570)
  at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/compositor/multi_threaded_compositor.cpp:141
  #11 0x76601087 in std::function::operator()() const () at 
/usr/include/c++/5/functional:2267
  #12 execute (this=0x7fffef7afdf0) at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/thread/basic_thread_pool.cpp:40
  #13 operator() (this=0x7c4660) at 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/thread/basic_thread_pool.cpp:91
  #14 __invoke () at /usr/include/c++/5/functional:201
  #15 operator() () at /usr/include/c++/5/functional:428
  #16 _M_invoke () at /usr/include/c++/5/functional:1531
  #17 operator() () at /usr/include/c++/5/functional:1520
  #18 _M_run (this=) at /usr/include/c++/5/thread:115
  #19 0x76f10c70 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #20 0x762e46fa in start_thread (arg=0x7fffef7b0700) at 
pthread_create.c:333
  #21 0x7697fb5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

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

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

[Touch-packages] [Bug 1615470] Re: [ FAILED ] DisplayConfiguration/DisplaySubpixelSetting.can_get_all_subpixel_arrangements/4, where GetParam() = 4

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ]
  
DisplayConfiguration/DisplaySubpixelSetting.can_get_all_subpixel_arrangements/4,
  where GetParam() = 4

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

Bug description:
  07:14:22 9: [ RUN ] 
DisplayConfiguration/DisplaySubpixelSetting.can_get_all_subpixel_arrangements/4
  07:14:22 9: [2016-08-19 07:14:22.037720] mirserver: Starting
  07:14:22 9: [2016-08-19 07:14:22.041482] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  07:14:22 9: [2016-08-19 07:14:22.057828] mirserver: Using software cursor
  07:14:22 9: [2016-08-19 07:14:22.066742] mirserver: Initial display 
configuration:
  07:14:22 9: [2016-08-19 07:14:22.067073] mirserver: 1.1: VGA 0.0" 0x0mm
  07:14:22 9: [2016-08-19 07:14:22.067282] mirserver: Current mode 4x3 10.00Hz
  07:14:22 9: [2016-08-19 07:14:22.067471] mirserver: Preferred mode 4x3 10.00Hz
  07:14:22 9: [2016-08-19 07:14:22.067636] mirserver: Logical position +0+0
  07:14:22 9: [2016-08-19 07:14:22.067803] mirserver: 1.2: unused VGA
  07:14:22 9: [2016-08-19 07:14:22.067997] mirserver: 1.3: VGA 0.0" 0x0mm
  07:14:22 9: [2016-08-19 07:14:22.068144] mirserver: Disabled
  07:14:22 9: [2016-08-19 07:14:22.086365] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  07:14:22 9: [2016-08-19 07:14:22.088142] mirserver: Mir version 0.25.0
  07:14:22 9: [2016-08-19 07:14:22.435350] mirserver: New display configuration:
  07:14:22 9: [2016-08-19 07:14:22.436123] mirserver: 1.1: LVDS 8.8" 200x100mm
  07:14:22 9: [2016-08-19 07:14:22.436416] mirserver: Current mode 1920x1200 
60.00Hz
  07:14:22 9: [2016-08-19 07:14:22.436642] mirserver: Preferred mode 1920x1200 
60.00Hz
  07:14:22 9: [2016-08-19 07:14:22.436882] mirserver: Logical position +0+0
  07:14:22 9: 
/��BUILDDIR��/mir-0.24.0+yakkety1900bzr3659/tests/acceptance-tests/test_new_display_configuration.cpp:423:
 Failure
  07:14:22 9: Value of: mir_output_get_subpixel_arrangement(output)
  07:14:22 9: Expected: is equal to 4
  07:14:22 9: Actual: 0 (of type MirSubpixelArrangement)
  07:14:22 9: 
/��BUILDDIR��/mir-0.24.0+yakkety1900bzr3659/tests/acceptance-tests/test_new_display_configuration.cpp:423:
 Failure
  07:14:22 9: Value of: mir_output_get_subpixel_arrangement(output)
  07:14:22 9: Expected: is equal to 4
  07:14:22 9: Actual: 0 (of type MirSubpixelArrangement)
  07:14:22 9: 
/��BUILDDIR��/mir-0.24.0+yakkety1900bzr3659/tests/acceptance-tests/test_new_display_configuration.cpp:423:
 Failure
  07:14:22 9: Value of: mir_output_get_subpixel_arrangement(output)
  07:14:22 9: Expected: is equal to 4
  07:14:22 9: Actual: 0 (of type MirSubpixelArrangement)
  07:14:22 9: [2016-08-19 07:14:22.648534] mirserver: Stopping
  07:14:22 9: [ FAILED ] 
DisplayConfiguration/DisplaySubpixelSetting.can_get_all_subpixel_arrangements/4,
 where GetParam() = 4 (641 ms)

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

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

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

[Touch-packages] [Bug 1598936] Re: mir::scene::Surface::input_area_contains is reset when surface moved onto a new display

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  mir::scene::Surface::input_area_contains is reset when surface moved
  onto a new display

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

Bug description:
  I'm changing ubuntu-keyboard to fill out its input shape/region.

  qtmir/unity8 then calls mir::scene::Surface::input_area_contains on a
  surface that is hit by an input event in unity8 QML scene before
  deciding whether that Qt input event is gonna be transformed into a
  MirEvent and consumed/sent-to that mir::scene::Surface or whether it
  will pass through.

  It all works as expected until I connect my mako to an external
  display. Once that happens, mir::scene::Surface::input_area_contains
  returns false on any point on any surface. Meaning that no surface
  gets input.

  At the present moment, that code hasn't landed yet. It's in
  https://requests.ci-train.ubuntu.com/#/ticket/1525.

  The qtmir patch is
  
https://code.launchpad.net/~dandrader/qtmir/mirSurfaceInputBounds/+merge/296986

  In the meantime I've added a workaround in this branch that makes
  qtmir store locally the input rect and use it to decide whether a
  point hits the surface's input area instead of querying
  mir::scene::Surface::input_area_contains

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

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

[Touch-packages] [Bug 1588967] Re: input region or input shape? Naming inconsistency

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  input region or input shape? Naming inconsistency

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

Bug description:
  The same concept is named "input region" in some places and "input
  shape" in others. This concept should have the same name throughout
  Mir API.

  shape:
  mir::shell::SurfaceSpecification::input_shape
  mir_surface_spec_set_input_shape

  region:
  mir::scene::Surface::set_input_region

  Or I misunderstood things and they are indeed different concepts?

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

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

[Touch-packages] [Bug 1613518] Re: [ FAILED ] NestedServer.posts_when_scene_has_visible_changes

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [ FAILED ] NestedServer.posts_when_scene_has_visible_changes

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

Bug description:
  08:54:08 9: [ RUN ] NestedServer.posts_when_scene_has_visible_changes
  08:54:08 9: [2016-08-15 08:54:08.145414] mirserver: Starting
  08:54:08 9: [2016-08-15 08:54:08.150775] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  08:54:08 9: [2016-08-15 08:54:08.193213] mirserver: Using software cursor
  08:54:08 9: [2016-08-15 08:54:08.255717] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  08:54:08 9: [2016-08-15 08:54:08.258141] mirserver: Mir version 0.25.0
  08:54:08 9: [2016-08-15 08:54:08.321425] mirserver: Starting
  08:54:08 9: [2016-08-15 08:54:08.530922] mirserver: Using nested cursor
  08:54:08 9: [2016-08-15 08:54:08.618740] mirserver: Initial display 
configuration:
  08:54:08 9: [2016-08-15 08:54:08.619915] mirserver: 1.1: VGA 0.0" 0x0mm
  08:54:08 9: [2016-08-15 08:54:08.620212] mirserver: Current mode 640x480 
60.00Hz
  08:54:08 9: [2016-08-15 08:54:08.620471] mirserver: Preferred mode 640x480 
60.00Hz
  08:54:08 9: [2016-08-15 08:54:08.620698] mirserver: Logical position +0+0
  08:54:08 9: [2016-08-15 08:54:08.621163] mirserver: 1.2: VGA 0.0" 0x0mm
  08:54:08 9: [2016-08-15 08:54:08.621468] mirserver: Current mode 1920x1080 
60.00Hz
  08:54:08 9: [2016-08-15 08:54:08.621710] mirserver: Preferred mode 1920x1080 
60.00Hz
  08:54:08 9: [2016-08-15 08:54:08.621922] mirserver: Logical position +640+0
  08:54:08 9: [2016-08-15 08:54:08.642074] mirserver: Mir version 0.25.0
  08:54:08 9: 
/��BUILDDIR��/mir-0.24.0+yakkety1839bzr3644/tests/acceptance-tests/test_nested_mir.cpp:801:
 Failure
  08:54:08 9: Actual function call count doesn't match 
EXPECT_CALL(*mock_session_mediator_report, session_submit_buffer_called(_))...
  08:54:08 9: Expected: to be called twice
  08:54:08 9: Actual: called once - unsatisfied and active
  08:54:08 9: 
/��BUILDDIR��/mir-0.24.0+yakkety1839bzr3644/tests/acceptance-tests/test_nested_mir.cpp:816:
 Failure
  08:54:08 9: Mock function called more times than expected - returning 
directly.
  08:54:08 9: Function call: session_submit_buffer_called(@0x10523ae8 
"nested-mir@:none")
  08:54:08 9: Expected: to be called twice
  08:54:08 9: Actual: called 3 times - over-saturated and active
  08:54:08 9: [2016-08-15 08:54:08.962404] mirserver: Stopping
  08:54:09 9: [2016-08-15 08:54:09.070964] mirserver: Stopping
  08:54:09 9: [ FAILED ] NestedServer.posts_when_scene_has_visible_changes 
(1070 ms)

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

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

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

[Touch-packages] [Bug 1603219] Re: Mir on X does not grab the x11 cursor when the surface is confined

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Mir on X does not grab the x11 cursor when the surface is confined

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

Bug description:
  To reproduce:
  1: Start a Mir On X session
  2: Run an example/demo that confines the pointer to a surface (so far only an 
SDL2 example exists)
  3: Moving the pointer to the left as far as you cant

  Expected:
  1: The mouse continues to generate events for the confined surface

  Results:
  1: The X11 mouse moves out of the Mir On X window and all mir events stop 
generating.

  A possible fix would be to imagine the X11 platform like a WM window.
  It grabs the pointer so you cant move either mouse outside of the X11
  boundaries and you need a key combo to release the grab.

  Not sure if this is wanted or not but without you cannot use anything
  that depends on pointer confinement in mir on Mir On X.

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

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

[Touch-packages] [Bug 1604425] Re: Trust session cannot be created on Unity8 desktop session

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Trust session cannot be created on Unity8 desktop session

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

Bug description:
  Create an Ubuntu One account in settings, and see that it is successfully 
created.
  Open the store.
  The account disappears.

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

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

[Touch-packages] [Bug 1583959] Re: mir_proving_server with INTEL_DEBUG=perf says: CPU mapping a busy miptree BO stalled and took 0.078 ms.

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  mir_proving_server with INTEL_DEBUG=perf says: CPU mapping a busy
  miptree BO stalled and took 0.078 ms.

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

Bug description:
  mir_proving_server with INTEL_DEBUG=perf says this when some clients
  (hardware or software) run:

  CPU mapping a busy miptree BO stalled and took 0.078 ms.
  CPU mapping a busy miptree BO stalled and took 0.038 ms.
  CPU mapping a busy miptree BO stalled and took 0.005 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.000 ms.
  CPU mapping a busy miptree BO stalled and took 0.000 ms.
  CPU mapping a busy miptree BO stalled and took 0.000 ms.
  CPU mapping a busy miptree BO stalled and took 0.000 ms.
  CPU mapping a busy miptree BO stalled and took 0.080 ms.
  CPU mapping a busy miptree BO stalled and took 0.128 ms.
  CPU mapping a busy miptree BO stalled and took 0.005 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.004 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.004 ms.
  CPU mapping a busy miptree BO stalled and took 0.146 ms.
  CPU mapping a busy miptree BO stalled and took 0.089 ms.
  CPU mapping a busy miptree BO stalled and took 0.008 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.002 ms.
  CPU mapping a busy miptree BO stalled and took 0.001 ms.
  CPU mapping a busy miptree BO stalled and took 0.001 ms.
  CPU mapping a busy miptree BO stalled and took 0.001 ms.
  CPU mapping a busy miptree BO stalled and took 0.000 ms.
  CPU mapping a busy miptree BO stalled and took 0.001 ms.

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

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

[Touch-packages] [Bug 1613529] Re: phablet-test-run fails on krillin: dpkg-query: package 'mir-demos' is not installed

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  phablet-test-run fails on krillin: dpkg-query: package 'mir-demos' is
  not installed

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

Bug description:
  18:30:26 + phablet-test-run -x -s JB011018 -v 
/home/phablet/mir-testrunner/mir-smoke-test-runner.sh
  18:30:26 running /home/phablet/mir-testrunner/mir-smoke-test-runner.sh
  18:30:26 [timestamp] Start time : 2016-08-15T18:30:26+
  18:30:26 dpkg-query: package 'mir-demos' is not installed

  [https://mir-jenkins.ubuntu.com/job/device-runtests-
  mir/1334/device_type=krillin/console]

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

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

[Touch-packages] [Bug 1613207] Re: mesa-kms is not Mesa-specific, so needs renaming

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  mesa-kms is not Mesa-specific, so needs renaming

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

Bug description:
  mesa-kms is not Mesa-specific, so needs renaming. I suggest renaming
  mesa-kms to gbm-kms.

  For a long time it wasn't clear which name was more appropriate but now it 
is. I have seen one OEM implement Wayland support for their proprietary 
hardware as custom binaries completely replacing the Mesa binaries:
     libgbm.so.1
     libEGL.so.1
     libGLESv2.so.2

  It works, and it should work for Mir too. So in this way our driver
  'mesa-kms' should more accurately be called 'gbm-kms'. Because we are
  not bound to a specific "Mesa" library, just to GBM ABI level 1. And
  the driver gbm-kms (formerly known as mesa-kms) should transparently
  support non-Mesa implementations of GBM.

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

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

[Touch-packages] [Bug 1584677] Re: Mir-on-X mir_proving_server crashes with SIGSEGV on shutdown or just when 'mir_demo_client_egltriangle -n' connects (which causes shutdown?)

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Mir-on-X mir_proving_server crashes with  SIGSEGV on shutdown or just
  when 'mir_demo_client_egltriangle -n' connects (which causes
  shutdown?)

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

Bug description:
  Mir-on-X mir_proving_server crashes with  SIGSEGV on shutdown or just
  when 'mir_demo_client_egltriangle -n' connects (which causes
  shutdown?)

  ==2601== Process terminating with default action of signal 11 (SIGSEGV)
  ==2601==  Access not within mapped region at address 0xCD8E430
  ==2601==at 0x650DC3B: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  ==2601==by 0x650E1BE: __gxx_personality_v0 (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  ==2601==by 0x6B1C262: _Unwind_RaiseException (in 
/lib/x86_64-linux-gnu/libgcc_s.so.1)
  ==2601==by 0x6B1C56C: _Unwind_Resume_or_Rethrow (in 
/lib/x86_64-linux-gnu/libgcc_s.so.1)
  ==2601==by 0x650E95B: __cxa_rethrow (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  ==2601==by 0x4E96696: mir::report_exception(std::ostream&) 
(report_exception.cpp:30)
  ==2601==by 0x4736ED: main (demo_shell.cpp:118)

  and then using --on-fatal-error-abort to work around the above
  uselessness:

  (gdb) bt
  #0  0x7f0f33ef25a9 in malloc_consolidate (
  av=av@entry=0x7f0f34237b20 ) at malloc.c:4176
  #1  0x7f0f33ef41e8 in _int_free (av=0x7f0f34237b20 ,
  p=, have_lock=0) at malloc.c:4076
  #2  0x7f0f33ef7abc in __GI___libc_free (mem=)
  at malloc.c:2969
  #3  0x7f0f2cef90bd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #4  0x7f0f2cef90bd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #5  0x7f0f2cef90bd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #6  0x7f0f2cef90bd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #7  0x7f0f2d003ed7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #8  0x7f0f2cf6cf1f in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #9  0x7f0f31dbc2d3 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #10 0x7f0f31db271d in eglTerminate ()
     from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  #11 0x7f0f2d7e46f9 in ?? ()
     from /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.8
  #12 0x7f0f33bd171a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
  #13 0x7f0f33b8316e in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
  #14 0x7f0f33bd171a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
  #15 0x7f0f33bbc074 in mir::shell::AbstractShell::~AbstractShell() ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
  #16 0x004213a9 in ?? ()
  #17 0x00422c36 in ?? ()
  #18 0x0041402d in main ()

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

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

[Touch-packages] [Bug 1617456] Re: [Feature Request] Gaming Mode for Unity

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [Feature Request] Gaming Mode for Unity

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

Bug description:
  Gaming is an important part for the desktop and besides workstations
  the most important and popular thing you can do with it. This is why
  Ubuntu should treat them well and I think they can do that with little
  effort.

  Unity 8 should not get in the way while playing a game, you can
  achieve this in several ways:

  
  - Suppress Notifications

  Problem: Gamer on Windows often complain about unwanted notifications,
  like system updates or other apps wanting attention. Notifications can
  be annoying while playing a game and cause a drop in FPS.

  Solution: So, Unity 8 should not display the at all during a game.
  Maybe a sound could inform the user instead?

  - Disable Keys That Throw You To The Desktop

  Problem: Accidentally hitting the SUPER- or ALT-key could throw you to
  the desktop

  Solution: they should be disabled and the user should instead just use
  ALT + TAB to get to the desktop. Maybe even provide a native steam-
  like Unity overlay? where you hit a Keyboard combination and can do
  stuff on your PC while having the game in sight.

  I'm sure there are things also things that could improve performance,
  if you have any other ideas feel free to post them below.

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

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

[Touch-packages] [Bug 1628831] Re: Mir clients never receive a MirSurfaceOutputEvent when the display mode changes (and thus DPI is changing)

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Mir clients never receive a MirSurfaceOutputEvent when the display
  mode changes (and thus DPI is changing)

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

Bug description:
  Mir clients never receive a MirSurfaceOutputEvent when the display
  mode changes (and thus DPI is changing)

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

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

[Touch-packages] [Bug 1618334] Re: mirin reports seemingly garbage strings

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  mirin reports seemingly garbage strings

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

Bug description:
  mirin reports seemingly garbage strings (Mir 0.24.0 on yakkety):

  1:Power Button:-event1-0-1n  keys
  2:Video Bus:-event2-0-6  keys
  3:Power Button:-event0-0-1n  keys
  4:Microsoft Microsoft 5-Button Mouse with IntelliEye(TM):-event9-1118-71soft 
5-Button Mouse with IntelliEye(TM)  pointer
  5:Lite-On Technology Corp. ThinkPad USB Keyboard with 
TrackPoint:-event10-6127-24585Corp. ThinkPad USB Keyboard with TrackPoint  full 
keyboard

  which supposedly represents the server whose log says:

  [2016-08-30 14:35:21.486613] evdev-input: Added /dev/input/event1
  [2016-08-30 14:35:21.488860] evdev-input: Added /dev/input/event2
  [2016-08-30 14:35:21.490844] evdev-input: Added /dev/input/event0
  [2016-08-30 14:35:21.492817] evdev-input: Added /dev/input/event9: Microsoft 
5-Button Mouse with IntelliEye TM 
  [2016-08-30 14:35:21.492832] evdev-input: Added /dev/input/event10: ThinkPad 
USB Keyboard with TrackPoint
  [2016-08-30 14:35:21.494802] evdev-input: Added /dev/input/event11: ThinkPad 
USB Keyboard with TrackPoint

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

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

[Touch-packages] [Bug 1609411] Re: CI failures caused by NestedServer.applies_display_config_on_startup memory error (invalid read of size 8)

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  CI failures caused by NestedServer.applies_display_config_on_startup
  memory error (invalid read of size 8)

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

Bug description:
  12:10:32 11: [ RUN ] NestedServer.applies_display_config_on_startup
  12:10:32 11: [2016-08-03 12:10:32.254941] mirserver: Starting
  12:10:32 11: [2016-08-03 12:10:32.256803] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  12:10:32 11: [2016-08-03 12:10:32.260847] mirserver: Using software cursor
  12:10:32 11: [2016-08-03 12:10:32.282496] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  12:10:32 11: [2016-08-03 12:10:32.283421] mirserver: Mir version 0.25.0
  12:10:32 11: [2016-08-03 12:10:32.332147] mirserver: Starting
  12:10:32 11: [2016-08-03 12:10:32.454335] mirserver: Using nested cursor
  12:10:32 11: [2016-08-03 12:10:32.504765] mirserver: Initial display 
configuration:
  12:10:32 11: [2016-08-03 12:10:32.505625] mirserver: 1.1: VGA 0.0" 0x0mm
  12:10:32 11: [2016-08-03 12:10:32.505887] mirserver: Current mode 640x480 
60.00Hz
  12:10:32 11: [2016-08-03 12:10:32.506133] mirserver: Preferred mode 640x480 
60.00Hz
  12:10:32 11: [2016-08-03 12:10:32.506341] mirserver: Logical position +0+0
  12:10:32 11: [2016-08-03 12:10:32.506978] mirserver: 1.2: VGA 0.0" 0x0mm
  12:10:32 11: [2016-08-03 12:10:32.507230] mirserver: Current mode 1920x1080 
60.00Hz
  12:10:32 11: [2016-08-03 12:10:32.507475] mirserver: Preferred mode 1920x1080 
60.00Hz
  12:10:32 11: [2016-08-03 12:10:32.507690] mirserver: Logical position +640+0
  12:10:32 11: [2016-08-03 12:10:32.521401] mirserver: Mir version 0.25.0
  12:10:32 11: [2016-08-03 12:10:32.650729] mirserver: Stopping
  12:10:32 11: ==11247== Thread 11 Input dispatch:
  12:10:32 11: ==11247== Invalid read of size 8
  12:10:32 11: ==11247== at 0x4116330: 
mir::graphics::nested::detail::DisplayBuffer::event_thunk(MirSurface*, MirEvent 
const*, void*) (display_buffer.cpp:109)
  12:10:32 11: ==11247== by 0x4E6BDBD: std::_Function_handler >::_M_invoke(std::_Any_data const&, 
MirEvent*&&) (functional:2267)
  12:10:32 11: ==11247== by 0x4EA007F: 
mir::input::receiver::android::InputReceiver::process_and_maybe_send_event() 
[clone .constprop.55] (functional:2267)
  12:10:32 11: ==11247== by 0x50E2209: operator() (functional:2267)
  12:10:32 11: ==11247== by 0x50E2209: (anonymous 
namespace)::DispatchableAdaptor::dispatch(unsigned int) [clone .lto_priv.445] 
(multiplexing_dispatchable.cpp:57)
  12:10:32 11: ==11247== by 0x50E330C: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  12:10:32 11: ==11247== by 0x50E330C: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  12:10:32 11: ==11247== by 0x50F250E: (anonymous 
namespace)::dispatch_loop(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function const&) 
[clone .lto_priv.314] (threaded_dispatcher.cpp:211)
  12:10:32 11: ==11247== by 0x50EACFD: _M_invoke (functional:1531)
  12:10:32 11: ==11247== by 0x50EACFD: operator() (functional:1520)
  12:10:32 11: ==11247== by 0x50EACFD: 
std::thread::_Impl, 
std::shared_ptr,
 std::shared_ptr, std::function))(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function const&)> 
>::_M_run() (thread:115)
  12:10:32 11: ==11247== by 0x586496F: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22)
  12:10:32 11: ==11247== by 0x5D4F709: start_thread (pthread_create.c:333)
  12:10:32 11: ==11247== by 0x606B6AC: clone (clone.S:109)
  12:10:32 11: ==11247== Address 0xe043c20 is 64 bytes inside a block of size 
136 free'd
  12:10:32 11: ==11247== at 0x4C2F24B: operator delete(void*) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  12:10:32 11: ==11247== by 0x41125B8: _M_release (shared_ptr_base.h:150)
  12:10:33 11: ==11247== by 0x41125B8: __base_dtor (shared_ptr_base.h:659)
  12:10:33 11: ==11247== by 0x41125B8: __base_dtor (shared_ptr_base.h:925)
  12:10:33 11: ==11247== by 0x41125B8: __base_dtor (shared_ptr.h:93)
  12:10:33 11: ==11247== by 0x41125B8: __base_dtor (stl_pair.h:96)
  12:10:33 11: ==11247== by 0x41125B8: destroy (new_allocator.h:124)
  12:10:33 11: ==11247== by 0x41125B8: destroy (alloc_traits.h:542)
  12:10:33 11: ==11247== by 0x41125B8: 
std::__detail::_Hashtable_alloc const, std::shared_ptr >, true> > 
>::_M_deallocate_node(std::__detail::_Hash_node const, 

[Touch-packages] [Bug 1619893] Re: SDL2 windowed apps launch on full screen in desktop mode (tablet)

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  SDL2 windowed apps launch on full screen in desktop mode (tablet)

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

Bug description:
  SDL2 windowed apps launch on full screen in desktop mode (tablet)

  install balls app https://uappexplorer.com/app/balls.briketa
  launch it in desktop mode (on tablet). the app creates a resistible window 
but the tablet launches the app in full screen

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

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

[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  Incomplete
Status in Oxide:
  Fix Released
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

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

[Touch-packages] [Bug 1620053] Re: Touch no longer working after suspend

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  Touch no longer working after suspend

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

Bug description:
  I have a Dell XPS 9350 qhd+ touch. All works fine. If I suspend it and
  then restart, touch no longer works.

  Version 16.04.1 LTS

  (Sorry -new to Ubuntu, but definitely abandonding Windows. Thank you!)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  4 14:49:24 2016
  InstallationDate: Installed on 2016-09-02 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1600205] Re: CI failure (invalid read of memory already freed) in NestedServer.display_orientation_changes_are_forwarded_to_host

[Michał Sawicz]

Syncing task from Mir.

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

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

Title:
  CI failure (invalid read of memory already freed) in
  NestedServer.display_orientation_changes_are_forwarded_to_host

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

Bug description:
  11:16:29 9: [ RUN ] 
NestedServer.display_orientation_changes_are_forwarded_to_host
  
  11:16:32 9: ==17691== Thread 11 Input dispatch:
  11:16:32 9: ==17691== Invalid read of size 8
  11:16:32 9: ==17691== at 0x50C9D8C: 
std::__shared_ptr::operator->() const (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmirserver.so.41)
  11:16:32 9: ==17691== by 0x51F8711: 
mir::graphics::nested::detail::DisplayBuffer::mir_event(MirEvent const&) 
(display_buffer.cpp:115)
  11:16:32 9: ==17691== by 0x51F815F: 
mir::graphics::nested::detail::DisplayBuffer::event_thunk(MirSurface*, MirEvent 
const*, void*) (display_buffer.cpp:104)
  11:16:32 9: ==17691== by 0x40A563B: void std::_Bind, void*))(MirSurface*, MirEvent const*, 
void*)>::__call(std::tuple&&, std::_Index_tuple<0ul, 1ul, 2ul>) (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmirclient.so.9)
  11:16:32 9: ==17691== by 0x40A5575: void std::_Bind, void*))(MirSurface*, MirEvent const*, 
void*)>::operator()(MirEvent const*&&) (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmirclient.so.9)
  11:16:32 9: ==17691== by 0x40A52EE: std::_Function_handler, 
void*))(MirSurface*, MirEvent const*, void*)> >::_M_invoke(std::_Any_data 
const&, MirEvent const*) (functional:2039)
  11:16:32 9: ==17691== by 0x40A1283: std::function::operator()(MirEvent const*) const (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmirclient.so.9)
  11:16:32 9: ==17691== by 0x40A4DEE: std::_Function_handler >::_M_invoke(std::_Any_data const&, 
MirEvent*) (functional:2039)
  11:16:32 9: ==17691== by 0x4123E43: std::function::operator()(MirEvent*) const (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmirclient.so.9)
  11:16:32 9: ==17691== by 0x4122733: 
mir::input::receiver::android::InputReceiver::process_and_maybe_send_event() 
(android_input_receiver.cpp:180)
  11:16:32 9: ==17691== by 0x4122EF7: 
mir::input::receiver::android::InputReceiver::InputReceiver(android::sp
 const&, std::shared_ptr const&, 
std::function const&, 
std::shared_ptr const&, 
std::function > 
(int)>)::$_2::operator()() const (android_input_receiver.cpp:91)
  11:16:32 9: ==17691== by 0x4122CBC: std::_Function_handler
 const&, std::shared_ptr const&, 
std::function const&, 
std::shared_ptr const&, 
std::function > 
(int)>)::$_2>::_M_invoke(std::_Any_data const&) (functional:2039)
  11:16:32 9: ==17691== by 0x548E32D: std::function::operator()() 
const (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmircommon.so.6)
  11:16:32 9: ==17691== by 0x5492B96: (anonymous 
namespace)::DispatchableAdaptor::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:57)
  11:16:32 9: ==17691== by 0x5490DDB: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  11:16:32 9: ==17691== by 0x41224E1: 
mir::input::receiver::android::InputReceiver::dispatch(unsigned int) 
(android_input_receiver.cpp:118)
  11:16:32 9: ==17691== by 0x5490DDB: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  11:16:32 9: ==17691== by 0x549519B: (anonymous 
namespace)::dispatch_loop(std::string const&, 
std::shared_ptr,
 std::shared_ptr, std::function const&) 
(threaded_dispatcher.cpp:211)
  11:16:32 9: ==17691== by 0x549A8D0: void std::_Bind_simple,
 std::shared_ptr, std::function))(std::string const&, 
std::shared_ptr,
 std::shared_ptr, std::function 
const&)>::_M_invoke<0ul, 1ul, 2ul, 3ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul>) 
(functional:1699)
  11:16:32 9: ==17691== by 0x549A814: std::_Bind_simple,
 std::shared_ptr, std::function))(std::string const&, 
std::shared_ptr,
 std::shared_ptr, std::function 
const&)>::operator()() (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmircommon.so.6)
  11:16:32 9: ==17691== by 0x549A7EB: std::thread::_Impl 
>::_M_run() (in 
/��BUILDDIR��/mir-0.24.0+vivid1507bzr3583/obj-x86_64-linux-gnu/lib/libmircommon.so.6)
  11:16:32 9: ==17691== by 0x60B1E2F: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20)
  11:16:32 9: ==17691== 

[Touch-packages] [Bug 1599416] Re: CI test failure (segfault) in UnresponsiveClient.does_not_hang_server

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  CI test failure (segfault) in UnresponsiveClient.does_not_hang_server

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

Bug description:
  [--] 1 test from UnresponsiveClient
  [ RUN ] UnresponsiveClient.does_not_hang_server
  [2016-07-05 21:46:09.004682] mirserver: Starting
  [2016-07-05 21:46:09.006605] mirserver: Selected driver: mir:stub-graphics 
(version 0.24.0)
  [2016-07-05 21:46:09.010375] mirserver: Using software cursor
  [2016-07-05 21:46:09.020844] mirserver: Initial display configuration:
  [2016-07-05 21:46:09.021706] mirserver: 1.1: VGA 0.0" 0x0mm
  [2016-07-05 21:46:09.021998] mirserver: Current mode 1600x1600 60.00Hz
  [2016-07-05 21:46:09.022266] mirserver: Preferred mode 1600x1600 60.00Hz
  [2016-07-05 21:46:09.022485] mirserver: Logical position +0+0
  [2016-07-05 21:46:09.054260] mirserver: Selected input driver: mir:stub-input 
(version: 0.24.0)
  [2016-07-05 21:46:09.054871] mirserver: Mir version 0.24.0
  ==20941== Thread 8:
  ==20941== Invalid read of size 8
  ==20941== at 0x6BD83E: operator() (test_unresponsive_client.cpp:100)
  ==20941== by 0x6BD83E: std::_Function_handler const&), 
UnresponsiveClient_does_not_hang_server_Test::TestBody()::{lambda()#2}::operator()()
 const::{lambda()#1}::operator()() const::{lambda()#1}::operator()() 
const::{lambda(std::shared_ptr 
const&)#1}>::_M_invoke(std::_Any_data const&, 
std::shared_ptr const&) (functional:1871)
  ==20941== by 0x6BB4A2: operator() (functional:2267)
  ==20941== by 0x6BB4A2: for_each (test_unresponsive_client.cpp:65)
  ==20941== by 0x6BB4A2: operator() (test_unresponsive_client.cpp:101)
  ==20941== by 0x6BB4A2: std::_Function_handler::_M_invoke(std::_Any_data const&) [clone .lto_priv.4853] 
(functional:1871)
  ==20941== by 0x6E97AD: operator() (functional:2267)
  ==20941== by 0x6E97AD: mir::test::CrossProcessAction::exec(std::function const&) (cross_process_action.cpp:26)
  ==20941== by 0x61FDB4: operator() (test_unresponsive_client.cpp:103)
  ==20941== by 0x61FDB4: _M_invoke (functional:1531)
  ==20941== by 0x61FDB4: operator() (functional:1520)
  ==20941== by 0x61FDB4: 
std::thread::_Impl >::_M_run() (thread:115)
  ==20941== by 0x5836C6F: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  ==20941== by 0x5D1E6F9: start_thread (pthread_create.c:333)
  ==20941== by 0x603AB5C: clone (clone.S:109)
  ==20941== Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==20941==
  ==20941==
  ==20941== Process terminating with default action of signal 11 (SIGSEGV)
  ==20941== at 0x5D282A9: raise (pt-raise.c:35)
  ==20941== by 0x4084FC3: fatal_signal_cleanup (run_mir.cpp:62)
  ==20941== by 0x5F6949F: ??? (in /lib/x86_64-linux-gnu/libc-2.23.so)
  ==20941== by 0x6BD83D: operator() (test_unresponsive_client.cpp:100)
  ==20941== by 0x6BD83D: std::_Function_handler const&), 
UnresponsiveClient_does_not_hang_server_Test::TestBody()::{lambda()#2}::operator()()
 const::{lambda()#1}::operator()() const::{lambda()#1}::operator()() 
const::{lambda(std::shared_ptr 
const&)#1}>::_M_invoke(std::_Any_data const&, 
std::shared_ptr const&) (functional:1871)
  ==20941== by 0x6BB4A2: operator() (functional:2267)
  ==20941== by 0x6BB4A2: for_each (test_unresponsive_client.cpp:65)
  ==20941== by 0x6BB4A2: operator() (test_unresponsive_client.cpp:101)
  ==20941== by 0x6BB4A2: std::_Function_handler::_M_invoke(std::_Any_data const&) [clone .lto_priv.4853] 
(functional:1871)
  ==20941== by 0x6E97AD: operator() (functional:2267)
  ==20941== by 0x6E97AD: mir::test::CrossProcessAction::exec(std::function const&) (cross_process_action.cpp:26)
  ==20941== by 0x61FDB4: operator() (test_unresponsive_client.cpp:103)
  ==20941== by 0x61FDB4: _M_invoke (functional:1531)
  ==20941== by 0x61FDB4: operator() (functional:1520)
  ==20941== by 0x61FDB4: 
std::thread::_Impl >::_M_run() (thread:115)
  ==20941== by 0x5836C6F: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
  ==20941== by 0x5D1E6F9: start_thread (pthread_create.c:333)
  ==20941== by 0x603AB5C: clone (clone.S:109)

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

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

[Touch-packages] [Bug 1626888] Re: 'make abi-check' fails to detect symbol version changes that break the ABI

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  'make abi-check' fails to detect symbol version changes that break the
  ABI

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

Bug description:
  'make abi-check' fails to detect symbol version changes that break the
  ABI.

  Like most people I assumed bug 1617865 occurred due to a simple
  mistake like us releasing Mir 0.24.0 without checking for ABI breaks.

  Well, now I've compared 0.23, 0.24 and trunk, and even tried making
  similar breaks. And in all cases 'make abi-check' has failed to detect
  the break (symbols keep the same name but change version stanzas).

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

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

[Touch-packages] [Bug 1445265] Re: Image flickers when switching to/from fullscreen

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  Image flickers when switching to/from fullscreen

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  With vivid-proposed on mako.

  We have a Image component with PreserveAspectRatio set as fillMode
  filling all the Page. When the application is going fullscreen / non-
  fullscreen on device the Image flickers during the process. Hiding the
  header too seems to make the result worse. This is the scenario for
  gallery-app during media viewer.

  On this branch [0] we have a sample app that seems to trigger the
  issue. Just tap the picture to go fullscreen / non-fullscreen.

  [0] lp:~artmello/+junk/fullscreen_issue

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

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

[Touch-packages] [Bug 1668159] Re: [enhancement] Add support for limited/full RGB range selection on HDMI outputs

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [enhancement] Add support for limited/full RGB range selection on HDMI
  outputs

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

Bug description:
  Add support for limited/full RGB range selection on HDMI outputs.

  Users of HDMI connected TVs might be familiar with the problem of
  blacks displayed as grey, or dark shades being too dark. These are
  both consequences of a mismatch between the range of the HDMI signal
  being output and what the HDMI display (usually a TV) expects.

  The two possible ranges of values for 8 bit per component are:
  Full: 0-255
  Limited: 16-235 (where 16 is the blackest black and 235 is the whitest white)

  The HDMI 1.3a spec clarified expected default behaviour in its table 6-3 
(section 6.6) and that
  "While using RGB, Limited Range shall be used for all video formats
  defined in CEA-861-D, with the exception of VGA (640x480) format, which 
requires Full Range."

  So apparently the correct default range for 8-bit output to HDMI is
  limited 16-235. However, a monitor's EDID may provide more information
  indicating that full range is preferable (and expected for correct
  colour output).

  The i915 kernel driver appears to give us a connector property
  "Broadcast RGB" for controlling this setting (auto/full/limited). So
  we should implement that. It's likely to also be useful in other
  future drivers, albeit with different implementations.

  If your device (Mir) and display support changing this setting then the 
optimal setup is:
    Output: Full range
    Display: Full range (AKA Black level "high" or "normal").

  But if your device (Mir) doesn't yet support changing the setting, and
  your HDMI-connected TV looks a bit wrong then you can probably just
  change the TV settings:

  Picture is too dark/black: Likely problem is that your device is
  outputting full range and your TV is expecting limited. Change your TV
  settings to Black level = Normal or High

  Picture is washed out (blacks appear grey and whites are dim): Likely
  problem is that your device is outputting limited range and your TV is
  configured for full range. Change your TV settings to Black level =
  Low (which means to treat 16 as full black and 235 as full white).

  The terminology might sound backwards, but in a TV's settings menus
  "low" black level means signal level 16 is full black (ie. make it
  visually lower), and "high" or "normal" black level means to make
  signal level 16 visually higher if it looks black (and real black is
  then level 0).

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

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

[Touch-packages] [Bug 1434478] Re: Ubuntu Core has no fonts installed: DemoRenderer: Failed to load titlebar font: /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Ubuntu Core has no fonts installed:  DemoRenderer: Failed to
  load titlebar font: /usr/share/fonts/truetype/liberation
  /LiberationSans-Bold.ttf

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

Bug description:
  Ubuntu Core has no fonts installed and Mir does not bring its own.
  This is to be expected, but a minor blemish...

  # /apps/bin/mir-run /apps/mir-demos/current/mir_proving_server 
  ...
  [1426843831.345651]  DemoRenderer: Failed to load titlebar font: 
/usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf

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

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

[Touch-packages] [Bug 1621828] Re: The mir_tool/events headers are entangled

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  The mir_tool/events headers are entangled

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

Bug description:
  This appears almost *halfway through*
  include/client/mir_toolkit/events/event.h

  ...
  #include "mir_toolkit/events/input/input_event.h"
  #include "mir_toolkit/events/resize_event.h"
  #include "mir_toolkit/events/surface_event.h"
  #include "mir_toolkit/events/orientation_event.h"
  #include "mir_toolkit/events/prompt_session_event.h"
  #include "mir_toolkit/events/keymap_event.h"
  #include "mir_toolkit/events/input_configuration_event.h"
  #include "mir_toolkit/events/surface_output_event.h"
  #include "mir_toolkit/events/input_device_state_event.h"
  ...

  And, of course, each of these #includes mir_toolkit/events/event.h

  It's a case of include one, include all.

  So, these headers don't win the client any specificity. Just obscure
  dependencies.

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

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

[Touch-packages] [Bug 1459508] Re: Mir builds successfully without libfreetype6-dev, resulting in black-block titlebars

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Mir builds successfully without libfreetype6-dev, resulting in black-
  block titlebars

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

Bug description:
  Mir builds successfully without libfreetype6-dev installed, resulting
  in black-block titlebars.

  Originally I intended this fallback to the stub renderer as a feature,
  to highlight that Freetype was an optional feature. However now I'm
  thinking it might be more confusing/annoying than it's worth. Perhaps
  the build should fail if libfreetype6-dev is missing. Even I as the
  author forget to install it and wonder why the titlebar is black
  blocks...

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

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

[Touch-packages] [Bug 1548236] Re: Add mouse cursor warping

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Add mouse cursor warping

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

Bug description:
  Add mouse cursor warping - an API (for nested shells at least if not
  all clients) to limit and reposition the mouse cursor.

  This is one of three missing Mir features that is preventing Unity8 from 
using Mir's built-in mouse cursor. The other two issues are:
* Android performance bug 1373696
* Mesa hardware cursor does not rotate with screen.

  See also: https://trello.com/c/sDnxldwa

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

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

[Touch-packages] [Bug 1539896] Re: [enhancement] Support Vulkan

[Michał Sawicz]

Syncing task from Mir.

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

Title:
  [enhancement] Support Vulkan

Status in Mir:
  Triaged
Status in Ubuntu SDK IDE:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  full support to the libraries vulkan in mir and in canonical system
  image.

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

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

[Touch-packages] [Bug 1368095] Re: libmirclient-dev's dependency on libmircommon-dev is weak

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

Title:
  libmirclient-dev's dependency on libmircommon-dev is weak

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

Bug description:
  libmirclient-dev's dependency on libmircommon-dev is weak and forces
  Mir client developers to install C++ tooling.

  Package: libmirclient-dev
  Section: libdevel
  Architecture: i386 amd64 armhf arm64
  Multi-Arch: same
  Pre-Depends: ${misc:Pre-Depends}
  Depends: libmirclient8 (= ${binary:Version}),
   libmircommon-dev (= ${binary:Version}),<==
   libprotobuf-dev (>= 2.4.1),
   ${misc:Depends},

  This is presently correct as our client headers use headers from
  libmircommon-dev. However a client developer can't link directly to
  any symbols exported by libmircommon.so.*. So the dependency exists
  for headers only.

  Maybe we can somehow reduce the dependency further so that client
  developers are not forced to install libmircommon-dev and the C++ that
  comes with it.

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

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

[Touch-packages] [Bug 1422262] Re: [regression] MirEvent 2.0 has no replacement for mir_motion_tool_type_eraser

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [regression] MirEvent 2.0 has no replacement for
  mir_motion_tool_type_eraser

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

Bug description:
  [enhancement] MirEvent 2.0 has no replacement for
  mir_motion_tool_type_eraser (yet)

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

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

[Touch-packages] [Bug 1672912] Re: Test takes up to 14 seconds to complete: ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Test takes up to 14 seconds to complete:
  ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly

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

Bug description:
  09:37:12 11: [ OK ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly 
(14235 ms)
  
[https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/4235/consoleFull]

  09:44:04 9: [ OK ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly 
(12894 ms)
  
[https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/4235/consoleFull]

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

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

[Touch-packages] [Bug 1431712] Re: Misnomer in mir_protobuf.proto: Void is not void. It contains an error message that we use.

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Misnomer in mir_protobuf.proto: Void is not void. It contains an error
  message that we use.

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

Bug description:
  Misnomer in mir_protobuf.proto: Void is not void. It contains an error
  message that we use.

  message Void {
optional string error = 127;
  }

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

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

[Touch-packages] [Bug 1370117] Re: [regression] Unresponsive/hung clients may never recover after waking up and could get disconnected

[Michał Sawicz]

Syncing task from Mir.

** Changed in: mir (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [regression] Unresponsive/hung clients may never recover after waking
  up and could get disconnected

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

Bug description:
  After the merge [1], if a client is blocked and the socket becomes
  full, then:

  1. if the server tries to send an event and it can't the event will be dropped
  2. if the server tries to reply to an RPC call (e.g. next_buffer) and it 
can't, it will disconnect the client

  We need to deal with the issue more gracefully, allowing clients to
  better recover from transient freezes. At the same time we need to
  have some mechanism to handle clients that are unresponsive for too
  long, so that we don't waste server-side resources.

  [1] https://code.launchpad.net/~afrantzis/mir/fix-1350207
  -unresponsive-clients/+merge/233934

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

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