[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Tags added: apport-collected artful wayland-session

** Description changed:

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse
  and keyboard connects, works for a few seconds, then doesn't react.
  
  Bluetooth package version: 5.46-0ubuntu3 500
  
  Please tell me which log-files to upload.
  
  Thanks
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2016-06-11 (509 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
+  Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 13d3:5664 IMC Networks 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 80MK
+ Package: bluez 5.46-0ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=da_DK.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/01/2016
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: C6CN37WW
+ 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 900-13ISK
+ dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
+ dmi.product.family: IDEAPAD
+ dmi.product.name: 80MK
+ dmi.product.version: Lenovo YOGA 900-13ISK
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN INQUIRY 
+   RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
+   TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002811/+files/CurrentDmesg.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:

[Touch-packages] [Bug 1729389] Dependencies.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002812/+files/Dependencies.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] ProcInterrupts.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002817/+files/ProcInterrupts.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] ProcModules.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002818/+files/ProcModules.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] ProcCpuinfoMinimal.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002816/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] Lspci.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1729389/+attachment/5002814/+files/Lspci.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] JournalErrors.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002813/+files/JournalErrors.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] ProcCpuinfo.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002815/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] UdevDb.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1729389/+attachment/5002819/+files/UdevDb.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] rfkill.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1729389/+attachment/5002821/+files/rfkill.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] getfacl.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1729389/+attachment/5002820/+files/getfacl.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] syslog.txt

2017-11-03 Thread Jeppe Bundsgaard
apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1729389/+attachment/5002822/+files/syslog.txt

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-03 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-03 Thread Daniel van Vugt
Thanks.

It seems the firmware updater can't reach your devices any more after a
few seconds:

nov 03 08:04:54 username-YOGA fwupd[1972]: failed to open: failed to ping 
Bluetooth Travel Mouse: failed to send: failed to write: wrote 0 of 7
nov 03 08:04:58 username-YOGA kernel: hid-generic 0005:046D:B309.0007: unknown 
main item tag 0x0
nov 03 08:04:58 username-YOGA upowerd[1075]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B309.0007/power_supply/hid-00:07:61:f7:66:65-battery
nov 03 08:04:59 username-YOGA fwupd[1972]: failed to open: failed to ping 
diNovo Edge: failed to send: failed to write: wrote 0 of 7

Please try disabling fwupd first, then reconnect the devices after:

   sudo systemctl stop fwupd.service

if that works then maybe keep it disabled:

   sudo systemctl disable fwupd.service



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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-03 Thread Alfonso Sanchez-Beato
@Lukasz those are patches for Dell modems (plano project, unbuntu core).
It makes sense to upstream some of them in fact, and that is something I
can try.

But, it would still make sense to backport the zesty packages to xenial,
as that has the support needed for DW5816e (lp #1693756). If you prefer,
we can go that way and leave out the patches for the moment until I get
a response for MM upstream.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  In Progress

Bug description:
  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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


[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

2017-11-03 Thread md_5
Java looks to be using the disabled foreground colour correctly (to me,
the untrained observer):

gtk2_widget = gtk2_get_widget(widget_type);
GtkStyle* style = gtk2_widget->style;

switch (color_type)
{
case FOREGROUND:
color = &(style->fg[state_type]);
break;


Worth noting using GTK3 breaks other things, but actually fixes this bug (but 
that could simply point to an issue with Java's GTK2 code).

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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


[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-11-03 Thread Jordi Miralles
Confirming is working again in 17.10

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-11-03 Thread Sebastien Bacher
it was fixed in that commit
https://sourceware.org/git/?p=glibc.git;a=commit;h=fe05e1cb

Would be nice to SRU to 17.10

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  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
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

2017-11-03 Thread md_5
Ok Turns out Java has some super funky code:

int componentState = context.getComponentState();
if ((componentState & SynthConstants.DISABLED) ==
  SynthConstants.DISABLED){
if (!GTKLookAndFeel.is3()) {
Color orgColor = g.getColor();
g.setColor(context.getStyle().getColor(context,
GTKColorType.WHITE));
x += 1;
y += 1;
super.paintText(context, g, text, x, y, mnemonicIndex);

g.setColor(orgColor);
x -= 1;
y -= 1;
}
super.paintText(context, g, text, x, y, mnemonicIndex);
}


Removing this silly +1 white shadowing nonsense results in perfect looking 
menus both when dark and light.
I will take this upstream and see if it can be patched into Ubuntu, not a 
theming bug after all.

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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


[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-11-03 Thread Adam Conrad
** Changed in: cups (Ubuntu)
 Assignee: uklas (uklasius) => (unassigned)

** Changed in: glibc (Ubuntu)
 Assignee: uklas (uklasius) => Adam Conrad (adconrad)

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  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
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-11-03 Thread ChristianEhrhardt
Per former comments setting 17.10 to fix released.

** Changed in: network-manager (Ubuntu Artful)
   Status: Confirmed => Fix Released

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Touch-packages] [Bug 1677305] Re: /dev/sda1 is checked at every boot instead of once every N mounts

2017-11-03 Thread Marco Lazzaroni
The problem shows up again. I am not able to tell the cause that made it
to come back.

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

Title:
  /dev/sda1 is checked at every boot instead of once every N mounts

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Every time I login I get the message:

  *** /dev/sda1 will be checked for errors at next reboot ***

  /dev/sda1 is my root partition. fsck was successfully run, but it
  looks like systemd is not aware of this, so fsck will be run again at
  the next boot.

  root@serverlinux:~# lsb_release -rd
  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  root@serverlinux:~# LANG=en_US apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu16
    Candidate: 229-4ubuntu16
    Version table:
   *** 229-4ubuntu16 500
  500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  root@serverlinux:~# cat /run/initramfs/fsck.log
  Log of fsck -C -a -T -t ext4 /dev/sda1
  Wed Mar 29 00:26:26 2017

  /dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks
  (check in 2 mounts)

  Wed Mar 29 00:26:26 2017
  

  root@serverlinux:~# LANG=en_US ls -l /run/initramfs/
  total 4
  -rw-r--r-- 1 root root   0 Mar 29 02:26 fsck-root
  -rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log

  [There's a discrepancy between the time in fsck.log and the time of
  the fsck.log but I suspect this is a UTC/CEST issue:

  root@serverlinux:~# LANG=en_US date
  Wed Mar 29 17:43:17 CEST 2017
  root@serverlinux:~# LANG=en_US date -u
  Wed Mar 29 15:43:21 UTC 2017

  The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25
  UTC)]

  This is the content of /etc/fstab:

  root@serverlinux:~#  cat /etc/fstab
  #
  proc/proc   procnodev,noexec,nosuid 0   0
  # / was on /dev/sda1 during installation
  UUID=c50edc7d-9f0b-4958-8e44-00bb5433ba42 /   ext4
errors=remount-ro,noatime,nodiratime,commit=60 0   1
  # swap was on /dev/sda5 during installation
  UUID=93b413bc-8663-44b4-81de-1a225a2f90da noneswapsw  
0   0
  # /dev/sdb1 in ext4 250GB
  UUID=5f987a15-685a-4d2b-adf9-8bcde0eca04e   /data ext4 
errors=remount-ro,noatime,nodiratime,commit=60   0   1

  The output of dumpe2fs on /dev/sda1 is:
  root@serverlinux:~# LANG=en_US dumpe2fs /dev/sda1
  (...)
  Filesystem created:   Thu Apr 15 15:23:07 2010
  Last mount time:  Wed Mar 29 02:26:26 2017
  Last write time:  Wed Mar 29 02:26:26 2017
  Mount count:  30
  Maximum mount count:  31
  Last checked: Tue Sep  6 02:46:17 2016
  Check interval:   15552000 (6 months)
  Next check after: Sun Mar  5 01:46:17 2017
  (...)

  For some reason, "Last checked:" time is not up to date (see above for
  the content of /run/initramfs/fsck.log), hence the problem (I
  suppose).

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

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


[Touch-packages] [Bug 1729827] [NEW] $ ubuntu-bug xorg

2017-11-03 Thread Daniele Calamandrei
Public bug reported:

i don't know whot i'm doing. I hopo he will automatically report the
bugs he found

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Nov  3 11:48:15 2017
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1070]
InstallationDate: Installed on 2017-11-01 (1 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:3491 IMC Networks 
 Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. P553UA
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=57084a81-3d5b-47bb-9418-c24272cfbe28 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
dmi.bios.date: 01/25/2017
dmi.bios.vendor: ASUSTeK COMPUTER INC.
dmi.bios.version: P553UA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P553UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvrP553UA.303:bd01/25/2017:svnASUSTeKCOMPUTERINC.:pnP553UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP553UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: P
dmi.product.name: P553UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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
xserver.bootTime: Fri Nov  3 11:34:57 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
$ ubuntu-bug xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't know whot i'm doing. I hopo he will automatically report the
  bugs he found

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  3 11:48:15 2017
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1070]
  InstallationDate: Installed on 2017-11-01 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3491 IMC Networks 
   Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. P553UA
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=57084a81-3d5b-47bb-9418-c24272cfbe28 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  dmi.bios.date: 01/25/2017
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: P553UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P553UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.typ

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-11-03 Thread bagl0312
Hi,
I confirm that with the command:

sudo nmcli connection modify  ipv4.dns-priority -42

there is not anymore DNS leakage.

However I am wondering why this command is needed, why the fix released
cannot include it by default ?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Touch-packages] [Bug 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server

2017-11-03 Thread Andreas Hasenack
Hm, cosmic rays, my comment wasn't saved :/

I also did some testing and the only case that won't work without either
the hook, or using the IP_FREEBIND socket option, is when ListenAddress
is set to an IP that doesn't exist yet. Meaning, sshd won't listen on
that IP when it comes up.

Maybe people caught in this corner case should use 0.0.0.0 (or the IPv6
equivalent) for ListenAddress and firewall rules to control which
traffic can reach the sshd daemon. That's the only way in artful now
anyway.

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  New

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network devices are
  everywhere.

  The hack introduces a race: you run into connection errors after
  bringing up a new interface as sshd stops listening briefly while
  being reloaded. That's the reason why I looked at it, as this
  regularly happens in upstream's cockpit integration tests.

  Also, /etc/network/if-up.d/ isn't being run when using
  networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
  this doesn't seem to have caused any issues.

  I asked the original reporter of bug 103436 for some details, and to
  check whether that hack is still necessary. There is actually a
  proposed patch upstream [2] to use IP_FREEBIND, which is the modern
  solution to listening to all "future" interfaces as well. But at least
  for the majority of cases it seems to work fine without that even.

  So I wonder if it's time to bury that hack?

  [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
  [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512

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

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


[Touch-packages] [Bug 1729836] [NEW] update-initramfs generating unbootable initrd files

2017-11-03 Thread Jeff Turner
Public bug reported:

After running 'update-initramfs -u -k $(uname -r)', Linux will not boot.
With 'quiet splash' set in grub, it appears to freeze after the 'Loading
ramdisk...' message, and if booted in recovery mode, I see the following
kernel panic:

Freeing unused kernel memory: 948k
Freeing unused kernel memory: 104K
x86/mm: Chcked W+X mappings: passed, no W+X pages found.
Failed to execute /init (error -2)
Kernel panic - not syncing: No working init found.  Try passing init= optin to 
kernel. See Linux Documentation/admin-guide/init.rst for guidance.
CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
Call Trace:
  dump_stack+0x63/0x8b
  ? rest_init+0xb0/0xc0
  panic+0xe4/0x23d
  ? putname+0x4b/0x50
  ? rest_init+0xc0/0xc0
  kernel_init+0xeb/0xfc
  ret_from_fork0x25/0x30
Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

(full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

Examining the initrd files, here is a good one, as installed by the
Ubuntu 17.10 installer:

# file /boot/initrd.img-4.13.0-16-generic
/boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
# ls -la /boot/initrd.img-4.13.0-16-generic
-rw-r--r-- 1 root root 50764087 Nov  3 21:02 /boot/initrd.img-4.13.0-16-generic

and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

# file /boot/initrd.img-4.13.0-16-generic
/boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
-rw-r--r-- 1 root root 50895514 Nov  3 21:01 /boot/initrd.img-4.13.0-16-generic

Good and bad initrds can be downloaded from
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

After downloading initrd.img-4.13.0-16-generic-broken, the panic can be
replicated in qemu with:

kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
/boot/initrd.img-4.13.0-16-generic-broken

(tip obtained from https://lists.debian.org/debian-
kernel/2016/02/msg00323.html)

I've experienced this problem with Ubuntu 17.04 and 17.10 on two
separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
until one day I update the kernel or something, and a .deb postinst
script calls update-initramfs and trashes that kernel's initrd file. If
I run 'update-initramfs -u -k all', all my old initrd files are toast.

The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
strange. I'm not getting many google hits on it. None of my other
Ubuntu/Debian servers use that format in their initrds.

ProblemType: Bug
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
Architecture: amd64
Date: Fri Nov  3 21:33:12 2017
InstallationDate: Installed on 2017-08-05 (90 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago)

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


** Tags: amd64 apport-bug 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/1729836

Title:
  update-initramfs generating unbootable initrd files

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at ht

[Touch-packages] [Bug 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server

2017-11-03 Thread ChristianEhrhardt
Ok, that said:
1. the hook is no more active
2. it works without it by sshd re-binding interfaces when it comes up when it 
is an open ListenAddress

@cjwatson - I think you can drop this Delta when you merge openssh next
time, what do you think?

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  New

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network devices are
  everywhere.

  The hack introduces a race: you run into connection errors after
  bringing up a new interface as sshd stops listening briefly while
  being reloaded. That's the reason why I looked at it, as this
  regularly happens in upstream's cockpit integration tests.

  Also, /etc/network/if-up.d/ isn't being run when using
  networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
  this doesn't seem to have caused any issues.

  I asked the original reporter of bug 103436 for some details, and to
  check whether that hack is still necessary. There is actually a
  proposed patch upstream [2] to use IP_FREEBIND, which is the modern
  solution to listening to all "future" interfaces as well. But at least
  for the majority of cases it seems to work fine without that even.

  So I wonder if it's time to bury that hack?

  [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
  [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512

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

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


[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-03 Thread Łukasz Zemczak
The main requirement is that those patches need to be first present in
the devel series (so in bionic). I would propose forwarding them
upstream and then actually distro-patching them into the current version
in bionic. We can then easily pull those into zesty and xenial.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  In Progress

Bug description:
  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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


[Touch-packages] [Bug 1729850] [NEW] artful openssl FTBFS on armhf

2017-11-03 Thread Marc Deslauriers
Public bug reported:

openssl FTBFS on artful armhf with the following:

../util/shlib_wrap.sh ./sha256t
Testing SHA-256 
TEST 1 of 3 failed.

** Affects: gcc-7 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gcc-7 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  artful openssl FTBFS on armhf

Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1729850/+subscriptions

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


[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-03 Thread Jeppe Bundsgaard
This didn't make any difference. It seems like the mouse works for
longer time, if I don't connect the keyboard. It also seems like the
mouse stops working when I change the active window (which sounds
strange, I agree). I can switch bluetooth off and on, and then the mouse
works again.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc 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: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  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 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-03 Thread Marc Deslauriers
It FTBFS with gcc 7.2 in artful and bionic, but builds fine with gcc 7.1
that was previously in artful.

Openssl 1.0.2m fails in the same way.

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

Title:
  artful openssl FTBFS on armhf

Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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)

2017-11-03 Thread Daniel Klafft
I had the same issue on a Lenovo laptop. The command

 sudo rfkill unblock all

mentioned by @vanvugt solved the issue for me.

Linux 4.13.0-16-generic

-- 
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 1729861] [NEW] [2.2.2] ABI upgrade needed

2017-11-03 Thread dino99
Public bug reported:

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)

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

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

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


** Tags: amd64 apport-bug bionic

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

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

** Description changed:

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

-- 
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:
  New
Status in opencv package in Ubuntu:
  New
Status in vtk package in Ubuntu:
  New

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 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
** Changed in: biometryd (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: buteo-sync-plugins-contacts (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: buteo-syncfw (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: history-service (Ubuntu)
 Assignee: Will Cooke (willcooke) => Łukasz Zemczak (sil2100)

** Changed in: libiphb (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  New
Status in libiphb package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic amd64
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic arm64
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic armhf
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic i386
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic ppc64el
buteo-syncfw 0.8.5+16.10.20160818-0ubuntu1 in bionic s390x
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic amd64
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic arm64
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic armhf
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic i386
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic 
ppc64el
libbuteosyncfw5-0 0.8.5+16.10.20160818-0ubuntu1 in bionic s390x
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic 
amd64
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic 
arm64
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic 
armhf
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic i386
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic 
ppc64el
libbuteosyncfw5-dev 0.8.5+16.10.20160818-0ubuntu1 in bionic 
s390x
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic 
amd64
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic 
arm64
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic 
armhf
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic i386
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic 
ppc64el
libbuteosyncfw5-doc 0.8.5+16.10.20160818-0ubuntu1 in bionic 
s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.


** Changed in: buteo-syncfw (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
libiphb 1.2.4+15.10.20150929-0ubuntu1 in bionic
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic amd64
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic arm64
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic armhf
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic i386
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic ppc64el
libiphb-dev 1.2.4+15.10.20150929-0ubuntu1 in bionic s390x
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic amd64
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic arm64
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic armhf
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic i386
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic ppc64el
libiphb0 1.2.4+15.10.20150929-0ubuntu1 in bionic s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.


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

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
thumbnailer 2.4+17.04.20161114.1-0ubuntu1 in bionic
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
amd64
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
arm64
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
armhf
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
i386
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
ppc64el
libthumbnailer-qt-dev 2.4+17.04.20161114.1-0ubuntu1 in bionic 
s390x
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
amd64
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
arm64
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
armhf
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
i386
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
ppc64el
libthumbnailer-qt-doc 2.4+17.04.20161114.1-0ubuntu1 in bionic 
s390x
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
amd64
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
arm64
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
armhf
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
i386
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
ppc64el
libthumbnailer-qt1.0 2.4+17.04.20161114.1-0ubuntu1 in bionic 
s390x
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic amd64
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic arm64
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic armhf
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic i386
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic ppc64el
qml-module-ubuntu-thumbnailer0.1 2.4+17.04.20161114.1-0ubuntu1 
in bionic s390x
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic amd64
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic arm64
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic armhf
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic i386
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic ppc64el
qtdeclarative5-ubuntu-thumbnailer0.1 
2.4+17.04.20161114.1-0ubuntu1 in bionic s390x
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic 
amd64
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic 
arm64
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic 
armhf
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic i386
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic 
ppc64el
thumbnailer-service 2.4+17.04.20161114.1-0ubuntu1 in bionic 
s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.

Removing packages from bionic-proposed:
thumbnailer 2.4+17.04.20161114.1-0ubuntu2 in bionic
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.

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

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
history-service 0.1+17.04.20161130-0ubuntu1 in bionic
history-service 0.1+17.04.20161130-0ubuntu1 in bionic amd64
history-service 0.1+17.04.20161130-0ubuntu1 in bionic arm64
history-service 0.1+17.04.20161130-0ubuntu1 in bionic armhf
history-service 0.1+17.04.20161130-0ubuntu1 in bionic i386
history-service 0.1+17.04.20161130-0ubuntu1 in bionic ppc64el
history-service 0.1+17.04.20161130-0ubuntu1 in bionic s390x
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic 
amd64
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic 
arm64
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic 
armhf
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic i386
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic 
ppc64el
history-service-tools 0.1+17.04.20161130-0ubuntu1 in bionic 
s390x
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic 
amd64
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic 
arm64
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic 
armhf
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic i386
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic 
ppc64el
libhistoryservice-dev 0.1+17.04.20161130-0ubuntu1 in bionic 
s390x
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic amd64
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic arm64
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic armhf
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic i386
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic ppc64el
libhistoryservice0 0.1+17.04.20161130-0ubuntu1 in bionic s390x
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic amd64
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic arm64
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic armhf
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic i386
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic ppc64el
qtdeclarative5-ubuntu-history0.1 0.1+17.04.20161130-0ubuntu1 in 
bionic s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.


** Changed in: history-service (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic-proposed:
biometryd 0.0.1+16.10.20160922.3-0ubuntu3 in bionic
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic amd64
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic arm64
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic armhf
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic i386
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic ppc64el
biometryd-bin 0.0.1+16.10.20160922.3-0ubuntu2 in bionic s390x
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic amd64
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic arm64
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic armhf
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic i386
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
ppc64el
libbiometryd-dev 0.0.1+16.10.20160922.3-0ubuntu2 in bionic s390x
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic amd64
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic arm64
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic armhf
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic i386
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic ppc64el
libbiometryd1 0.0.1+16.10.20160922.3-0ubuntu2 in bionic s390x
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
amd64
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
arm64
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
armhf
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
i386
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
ppc64el
qml-module-biometryd 0.0.1+16.10.20160922.3-0ubuntu2 in bionic 
s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.

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

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1713076] Re: Please remove more orphaned unity8 packages

2017-11-03 Thread Łukasz Zemczak
Removing packages from bionic:
buteo-sync-plugins-contacts 0.1+16.10.20160818.1-0ubuntu1 in bionic
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic amd64
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic arm64
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic armhf
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic i386
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic ppc64el
buteo-sync-plugins-contacts-google 
0.1+16.10.20160818.1-0ubuntu1 in bionic s390x
Comment: Obsolete; LP: #1713076
Remove [y|N]? y
1 package successfully removed.


** Changed in: buteo-sync-plugins-contacts (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove more orphaned unity8 packages

Status in biometryd package in Ubuntu:
  Fix Released
Status in buteo-sync-plugins-contacts package in Ubuntu:
  Fix Released
Status in buteo-syncfw package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in libiphb package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  biometryd
  buteo-sync-plugins-contacts
  buteo-syncfw
  history-service
  libiphb
  thumbnailer

  From other bugs
  ===

  LP: #1702429
  
  system-image
  ubuntu-download-manager

  LP: #1688395
  
  oxide-qt

  LP: #1712955
  
  repowerd and several others

  LP: #1728188
  
  trust-store

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

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


[Touch-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

2017-11-03 Thread brad
** Changed in: xorg (Ubuntu)
   Status: Incomplete => New

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

Title:
  AMD r7 250 wrong detection

Status in xorg package in Ubuntu:
  New

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1702429] Re: Please remove system-image from Ubuntu Artful

2017-11-03 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1713262 ***
https://bugs.launchpad.net/bugs/1713262

** Tags added: u8rm

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

Title:
  Please remove system-image from Ubuntu Artful

Status in system-image package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released

Bug description:
  I would like to request the removal of source and binaries of the
  system-image in artful. The rationale is that the package no longer
  has any active maintainer and doesn't have any consumers since vivid.
  With the incoming Python 3.6 transition, system-image will just cause
  unneeded delays.

  There are no reverse dependencies in artful:

  sil2100@ideamatsu:~$ reverse-depends system-image-cli
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends system-image-dbus
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends -b system-image-dev
  No reverse dependencies found

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1702429/+subscriptions

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


[Touch-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

2017-11-03 Thread Steve Langasek
Removing packages from bionic:
oxide-qt 1.21.5-0ubuntu1 in bionic
liboxideqt-qmlplugin 1.21.5-0ubuntu1 in bionic amd64
liboxideqt-qmlplugin 1.21.5-0ubuntu1 in bionic arm64
liboxideqt-qmlplugin 1.21.5-0ubuntu1 in bionic armhf
liboxideqt-qmlplugin 1.21.5-0ubuntu1 in bionic i386
liboxideqtcore-dev 1.21.5-0ubuntu1 in bionic amd64
liboxideqtcore-dev 1.21.5-0ubuntu1 in bionic arm64
liboxideqtcore-dev 1.21.5-0ubuntu1 in bionic armhf
liboxideqtcore-dev 1.21.5-0ubuntu1 in bionic i386
liboxideqtcore0 1.21.5-0ubuntu1 in bionic amd64
liboxideqtcore0 1.21.5-0ubuntu1 in bionic arm64
liboxideqtcore0 1.21.5-0ubuntu1 in bionic armhf
liboxideqtcore0 1.21.5-0ubuntu1 in bionic i386
liboxideqtquick-dev 1.21.5-0ubuntu1 in bionic amd64
liboxideqtquick-dev 1.21.5-0ubuntu1 in bionic arm64
liboxideqtquick-dev 1.21.5-0ubuntu1 in bionic armhf
liboxideqtquick-dev 1.21.5-0ubuntu1 in bionic i386
liboxideqtquick0 1.21.5-0ubuntu1 in bionic amd64
liboxideqtquick0 1.21.5-0ubuntu1 in bionic arm64
liboxideqtquick0 1.21.5-0ubuntu1 in bionic armhf
liboxideqtquick0 1.21.5-0ubuntu1 in bionic i386
liboxideubuntuuitk0 1.21.5-0ubuntu1 in bionic amd64
liboxideubuntuuitk0 1.21.5-0ubuntu1 in bionic arm64
liboxideubuntuuitk0 1.21.5-0ubuntu1 in bionic armhf
liboxideubuntuuitk0 1.21.5-0ubuntu1 in bionic i386
oxideqt-codecs 1.21.5-0ubuntu1 in bionic amd64
oxideqt-codecs 1.21.5-0ubuntu1 in bionic arm64
oxideqt-codecs 1.21.5-0ubuntu1 in bionic armhf
oxideqt-codecs 1.21.5-0ubuntu1 in bionic i386
oxideqt-codecs-extra 1.21.5-0ubuntu1 in bionic amd64
oxideqt-codecs-extra 1.21.5-0ubuntu1 in bionic arm64
oxideqt-codecs-extra 1.21.5-0ubuntu1 in bionic armhf
oxideqt-codecs-extra 1.21.5-0ubuntu1 in bionic i386
oxideqt-doc 1.21.5-0ubuntu1 in bionic amd64
oxideqt-doc 1.21.5-0ubuntu1 in bionic arm64
oxideqt-doc 1.21.5-0ubuntu1 in bionic armhf
oxideqt-doc 1.21.5-0ubuntu1 in bionic i386
oxideqt-doc 1.21.5-0ubuntu1 in bionic ppc64el
oxideqt-doc 1.21.5-0ubuntu1 in bionic s390x
qml-module-oxide-ubuntu 1.21.5-0ubuntu1 in bionic amd64
qml-module-oxide-ubuntu 1.21.5-0ubuntu1 in bionic arm64
qml-module-oxide-ubuntu 1.21.5-0ubuntu1 in bionic armhf
qml-module-oxide-ubuntu 1.21.5-0ubuntu1 in bionic i386
Comment: obsoleted product, security sensitive, unmaintained; LP: #1688395
1 package successfully removed.


** Changed in: oxide-qt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions

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


[Touch-packages] [Bug 1702429] Re: Please remove system-image from Ubuntu Artful

2017-11-03 Thread Adam Conrad
*** This bug is a duplicate of bug 1713262 ***
https://bugs.launchpad.net/bugs/1713262

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: New => Fix Released

** Changed in: system-image (Ubuntu)
   Status: New => Fix Released

** This bug has been marked a duplicate of bug 1713262
   remove system-image, ubuntu-download-manager, ubuntu-core-upgrader: Ubuntu 
Touch / Ubuntu Core 15 components, no longer used

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

Title:
  Please remove system-image from Ubuntu Artful

Status in system-image package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released

Bug description:
  I would like to request the removal of source and binaries of the
  system-image in artful. The rationale is that the package no longer
  has any active maintainer and doesn't have any consumers since vivid.
  With the incoming Python 3.6 transition, system-image will just cause
  unneeded delays.

  There are no reverse dependencies in artful:

  sil2100@ideamatsu:~$ reverse-depends system-image-cli
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends system-image-dbus
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends -b system-image-dev
  No reverse dependencies found

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1702429/+subscriptions

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


[Touch-packages] [Bug 1729879] [NEW] apport-collect is still requesting python-apport installation

2017-11-03 Thread dino99
Public bug reported:

apport-collect should now run via python3-apport package, as python2.7
is now gone on bionic. But that fail and show:

 apport-collect 1729877
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

this is not expected now.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3-apport 2.20.7-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportLog:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov  3 16:12:40 2017
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  apport-collect is still requesting python-apport installation

Status in apport package in Ubuntu:
  New

Bug description:
  apport-collect should now run via python3-apport package, as python2.7
  is now gone on bionic. But that fail and show:

   apport-collect 1729877
  You need to run 'sudo apt-get install python-apport' for apport-collect to 
work.

  this is not expected now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.7-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  3 16:12:40 2017
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1718027] Re: RM: obsolete product

2017-11-03 Thread Adam Conrad
Removing packages from bionic:
libusermetrics 1.1.1+17.04.20161208.1-0ubuntu1 in bionic
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
amd64
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
arm64
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
armhf
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
i386
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
ppc64el
libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
s390x
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
amd64
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
arm64
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
armhf
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
i386
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
ppc64el
libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
s390x
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
amd64
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
arm64
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
armhf
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
i386
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
ppc64el
libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
s390x
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic amd64
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic arm64
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic armhf
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic i386
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic ppc64el
libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic s390x
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
amd64
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
arm64
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
armhf
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
i386
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
ppc64el
libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
s390x
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic amd64
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic arm64
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic armhf
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic i386
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic ppc64el
libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in 
bionic s390x
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic amd64
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic arm64
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic armhf
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic i386
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic ppc64el
qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 
in bionic s390x
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
amd64
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
arm64
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
armhf
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
i386
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
ppc64el
usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic 
s390x
Comment: Obsolete; LP: #1718027
Remove [y|N]? y
1 package successfully removed.


** Changed in: libusermetrics (Ubuntu)
 Assignee: Will Cooke (willcooke) => Adam Conrad (adconrad)

** Changed in: libusermetrics (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete product

Status in libusermetrics package in Ubuntu:
  Fix Released

Bug description:
  libusermetrics was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from t

[Touch-packages] [Bug 1718022] Re: RM: obsolete product

2017-11-03 Thread Adam Conrad
Removing packages from bionic:
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic amd64
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic arm64
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic armhf
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic i386
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic ppc64el
telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic s390x
telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in 
bionic amd64
telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in 
bionic arm64
telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in 
bionic armhf
telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in 
bionic i386
Comment: Obsolete; LP: #1718022
Remove [y|N]? y
1 package successfully removed.


** Changed in: telepathy-ofono (Ubuntu)
 Assignee: Will Cooke (willcooke) => Adam Conrad (adconrad)

** Changed in: telepathy-ofono (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete product

Status in telepathy-ofono package in Ubuntu:
  Fix Released

Bug description:
  telepathy-ofono was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:telepathy-ofono
  No reverse dependencies found

  $ reverse-depends -b src:telepathy-ofono
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1718022/+subscriptions

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


[Touch-packages] [Bug 1728931] Re: [testsfail] ServerDisconnect.is_detected_by_client

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

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

Title:
  [testsfail] ServerDisconnect.is_detected_by_client

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

Bug description:
  [ RUN ] ServerDisconnect.is_detected_by_client
  [2017-10-27 21:38:41.897919] mirserver: Starting
  [2017-10-27 21:38:41.898180] mirserver: Selected driver: mir:stub-graphics 
(version 0.28.1)
  [2017-10-27 21:38:41.908376] mirserver: Using software cursor
  [2017-10-27 21:38:41.912088] mirserver: Selected input driver: mir:stub-input 
(version: 0.28.1)
  [2017-10-27 21:38:41.920187]  mirserver: No WaylandAllocator EGL 
support!
  error: XDG_RUNTIME_DIR not set in the environment
  [2017-10-27 21:38:41.922664] mirserver: Mir version 0.28.1
  [2017-10-27 21:38:41.923122] mirserver: Initial display configuration:
  [2017-10-27 21:38:41.923141] mirserver: CTestConfig.cmake CTestTestfile.cmake 
mir_acceptance_tests.bin_10.xml mir_acceptance_tests.bin_11.xml 
mir_acceptance_tests.bin_1.xml mir_acceptance_tests.bin_2.xml 
mir_acceptance_tests.bin_3.xml mir_acceptance_tests.bin_4.xml 
mir_acceptance_tests.bin_5.xml mir_acceptance_tests.bin_6.xml 
mir_acceptance_tests.bin_7.xml mir_acceptance_tests.bin_8.xml 
mir_acceptance_tests.bin_9.xml mir_acceptance_tests.bin.xml steer.cmake Testing 
Output 1: VGA connected, used
  [2017-10-27 21:38:41.923157] mirserver: . |_ Physical size 0.0" 0x0mm
  [2017-10-27 21:38:41.923162] mirserver: . |_ Power is on
  [2017-10-27 21:38:41.923167] mirserver: . |_ Current mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923172] mirserver: . |_ Preferred mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923175] mirserver: . |_ Orientation normal
  [2017-10-27 21:38:41.923181] mirserver: . |_ Logical size 1600x1600
  [2017-10-27 21:38:41.923184] mirserver: . |_ Logical position +0+0
  [2017-10-27 21:38:41.923188] mirserver: . |_ Scaling factor: 1.00
  [2017-10-27 21:38:41.940284] mirserver: Stopping
  /spread/mir/tests/mir_test_framework/interprocess_client_server_test.cpp:167: 
Failure
  Value of: result.exit_code
  Expected: is equal to 0
  Actual: 1 (of type int)
  [2017-10-27 21:38:41.953366]  MirWindowAPI: Caught exception at client 
library boundary (in window_release_helper): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [2017-10-27 21:38:41.953754]  MirConnectionAPI: Caught exception at 
client library boundary (in mir_connection_release): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [ FAILED ] ServerDisconnect.is_detected_by_client (58 ms)

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

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


[Touch-packages] [Bug 1671771] Re: Missing client API to indicate some windows should never receive keyboard focus

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  Missing client API to indicate some windows should never receive
  keyboard focus

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

Bug description:
  Missing client API to indicate some windows should never receive
  keyboard focus.

  According to the Unity8 design:
   duflu, yes, the “gloss” and “tip” types are unfocusable, and an 
app/toolkit should be able to specify whether a particular “freestyle” window 
is unfocusable. 

  But Xmir has broader requirements that menus and utility windows
  should have the option of being unfocusable. This is required to fix
  bug 1625846 and bug 1671744. Maybe also bug 1662733.

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

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


[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-11-03 Thread 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1669524

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

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

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

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

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

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


[Touch-packages] [Bug 1677128] Re: On nouveau in clone mode the hardware cursor lags a lot (by seconds)

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1677128

Title:
  On nouveau in clone mode the hardware cursor lags a lot (by seconds)

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

Bug description:
  On nouveau in clone mode the hardware cursor lags a lot (by seconds)
  if a client is rendering constantly.

  Hacking the server to force use of the software cursor however fixes
  the problem and it becomes perfectly responsive.

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

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


[Touch-packages] [Bug 1728613] Re: On Artful, resizing a Mir EGL client on a Mir server nested on a Mir-on-X server crashes the nested server

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1728613

Title:
  On Artful, resizing a Mir EGL client on a Mir server nested on a Mir-
  on-X server crashes the nested server

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

Bug description:
  $ mir_demo_server --window-manager system-compositor
  $ gdb --args build/bin/mir_demo_server --no-file --host 
$XDG_RUNTIME_DIR/mir_socket --test-timeout 100 --test-client 
build/bin/mir_demo_client_egltriangle

  Resize using Alt+middle mouse button
  ...

  Thread 5 "Mir/Comp" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffe84e1700 (LWP 15370)]
  0x75901e68 in dri2_image_get_buffers (driDrawable=0x55a17b00, 
format=4099, stamp=, loaderPrivate=0x55a17640, 
buffer_mask=, 
  buffers=0x7fffe84e0960) at 
../../../src/egl/drivers/dri2/platform_mir.c:137
  137   ../../../src/egl/drivers/dri2/platform_mir.c: No such file or directory.
  (gdb) bt
  #0  0x75901e68 in dri2_image_get_buffers (driDrawable=0x55a17b00, 
format=4099, stamp=, loaderPrivate=0x55a17640, 
buffer_mask=, buffers=0x7fffe84e0960) at 
../../../src/egl/drivers/dri2/platform_mir.c:137
  #1  0x7fffe9d62fee in intel_update_image_buffers 
(drawable=0x55a17b00, brw=0x77f83040) at 
../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1657
  #2  0x7fffe9d62fee in intel_update_renderbuffers 
(context=context@entry=0x55a0ef90, drawable=drawable@entry=0x55a17b00)
  at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1325
  #3  0x7fffe9d63311 in intel_prepare_render (brw=brw@entry=0x77f83040) 
at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1346
  #4  0x7fffe9d5ee65 in brw_clear (ctx=0x77f83040, mask=2) at 
../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:224
  #5  0x7518049c in 
mir::renderer::gl::Renderer::render(std::vector,
 std::allocator > > const&) const 
(this=0x7fffeb10, renderables=std::vector of length 3, capacity 3 = {...}) 
at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:209
  #6  0x750b2460 in 
mir::compositor::DefaultDisplayBufferCompositor::composite(std::vector,
 std::allocator > >&&) 
(this=this@entry=0x7fffe04a5a90, scene_elements=...)
  at 
/home/alan/display_server/mir/src/server/compositor/default_display_buffer_compositor.cpp:84
  #7  0x750b7f1b in mir::compositor::CompositingFunctor::operator()() 
(this=0x55794550)
  at 
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:141
  #8  0x7517cbd5 in std::function::operator()() const 
(this=0x7fffe84e0e60) at /usr/include/c++/7/bits/std_function.h:706
  #9  0x7517cbd5 in (anonymous namespace)::Task::execute 
(this=0x7fffe84e0e60) at 
/home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:40
  #10 0x7517cbd5 in (anonymous namespace)::Worker::operator() 
(this=0x55a97680) at 
/home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:91
  #11 0x7517cbd5 in std::__invoke_impl (__f=...) at /usr/include/c++/7/bits/invoke.h:60
  #12 0x7517cbd5 in std::__invoke<(anonymous namespace)::Worker&> 
(__fn=...) at /usr/include/c++/7/bits/invoke.h:95
  #13 0x7517cbd5 in std::thread::_Invoker >::_M_invoke<0> (this=) at 
/usr/include/c++/7/thread:234
  #14 0x7517cbd5 in std::thread::_Invoker >::operator() (this=) at 
/usr/include/c++/7/thread:243
  #15 0x7517cbd5 in 
std::thread::_State_impl > >::_M_run() (this=)
  at /usr/include/c++/7/thread:186
  #16 0x779070ff in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #17 0x7741c7fc in start_thread (arg=0x7fffe84e1700) at 
pthread_create.c:465
  #18 0x77149b0f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

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

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


[Touch-packages] [Bug 1728188] Re: Don't build pulseaudio with trust-store support

2017-11-03 Thread Adam Conrad
@vanvugt It doesn't sound like that to me at all.  seb128 was just
pointing out that the snappy patches depend on the trust-store changes
to a degree.  If those dependencies can be isolated, moved to the snappy
changeset, and the trust-store dep dropped, then everyone wins.

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

Title:
  Don't build pulseaudio with trust-store support

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Please check whether we still need to build pulseaudio with trust-
  store support or if we can drop it and remove trust-store from Ubuntu.

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

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


[Touch-packages] [Bug 1665123] Re: Mir graphics platform determined based on host server outside of snap

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  Mir graphics platform determined based on host server outside of snap

Status in Mir:
  New
Status in Unity8 Session Snap:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  People have reported the unity8 session snap to fail to start, with a
  log excerpt (http://pastebin.ubuntu.com/24000769/):

  ERROR: 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/common/sharedlibrary/shared_library.cpp(33):
 Throw in function mir::SharedLibrary::SharedLibrary(const char*)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: 
/snap/unity8-session/439/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12:
 cannot open shared object file: No such file or directory

  Mir 0.26 is trying to load the mesa graphics v12, which only came in
  Mir 0.26.1. It seems Mir is somehow expecting for the system-installed
  graphics v12 to be there in the snap.

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

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


[Touch-packages] [Bug 1666259] Re: [kvm] Dolphin screen goes black opening Find dialog [mirclient: Caught exception at client library boundary (in mir_buffer_release) ... std::exception::what: error:

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  [kvm] Dolphin screen goes black opening Find dialog [mirclient: Caught
  exception at client library boundary (in mir_buffer_release) ...
  std::exception::what: error: use of MirBuffer when
  mir_buffer_is_valid() is false]

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

Bug description:
  Test case.
  - Install Dolphin.
  - Log in Unity8 session.
  - Open the Drawer and start Dolphin.
  - Go to Edit > Find.

  Expected result.
  - Find dialog opens.

  Actual result.
  - After clicking in Find, the Dolphin screen goes black.

  Tested in Zesty and Xenial + Overlay in a qemu-kvm VM (amd64).

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

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


[Touch-packages] [Bug 1649758] Re: [ FAILED ] LifecycleEventTest.lifecycle_event_test

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1649758

Title:
  [ FAILED ] LifecycleEventTest.lifecycle_event_test

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

Bug description:
  16:16:26 13: [ RUN ] LifecycleEventTest.lifecycle_event_test
  ...
  16:16:28 13: 
/<>/mir-0.25.0+yakkety3172bzr3818/tests/integration-tests/shell/test_session_lifecycle_event.cpp:85:
 Failure
  16:16:28 13: Actual function call count doesn't match EXPECT_CALL(*handler, 
state_changed(Eq(mir_lifecycle_state_will_suspend)))...
  16:16:28 13: Expected: to be called once
  16:16:28 13: Actual: never called - unsatisfied and active
  16:16:28 13: [ FAILED ] LifecycleEventTest.lifecycle_event_test (2292 ms)

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

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

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


[Touch-packages] [Bug 1669177] Re: Mir client crashes in google::protobuf::MessageLite::ParseFromString when the server sends an error response

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  Mir client crashes in google::protobuf::MessageLite::ParseFromString
  when the server sends an error response

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Mir 0.26 series:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Mir client crash occurred during executing 01_hello_SDL
  (SDL_VIDEODRIVER=mir ./01_hello_SDL) program (program source is
  available here:
  http://lazyfoo.net/tutorials/SDL/01_hello_SDL/01_hello_SDL.zip ).

  Stack trace:
  #0  0x700050c0 in ?? ()
  #1  0x759e796f in 
google::protobuf::MessageLite::ParseFromString(std::__cxx11::basic_string, std::allocator > const&) () from 
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #2  0x76affb88 in 
mir::client::rpc::MirProtobufRpcChanneloperator()(google::protobuf::MessageLite
 *) const (__closure=0x74bc9a20, result_message=0x70004f80)
  at 
/media/kinga/Dane/mir/mir_nowy/src/client/rpc/mir_protobuf_rpc_channel.cpp:506
  #3  0x76b00897 in 
std::_Function_handler
 >::_M_invoke(const std::_Any_data &, ) (__functor=..., 
  __args#0=)
  at /usr/include/c++/5/functional:1871
  #4  0x76afbab5 in std::function::operator()(google::protobuf::MessageLite*) 
const (this=0x74bc9a20, __args#0=0x70004f80) at 
/usr/include/c++/5/functional:2267
  #5  0x76afad99 in 
mir::client::rpc::detail::PendingCallCache::populate_message_for_result(mir::protobuf::wire::Result&,
 std::function const&) (this=0x61e990, 
result=..., 
  populator=...) at 
/media/kinga/Dane/mir/mir_nowy/src/client/rpc/mir_basic_rpc_channel.cpp:74
  #6  0x76affed5 in 
mir::client::rpc::MirProtobufRpcChannel::on_data_available (this=0x61e960)
  at 
/media/kinga/Dane/mir/mir_nowy/src/client/rpc/mir_protobuf_rpc_channel.cpp:508
  #7  0x76b09c95 in 
mir::client::rpc::TransportObserversoperator()
 >(std::shared_ptr) const (
  __closure=0x74bc9bd0, observer=warning: RTTI symbol not found for 
class 'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'
  warning: RTTI symbol not found for class 
'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'
  std::shared_ptr (count 3, weak 0) 0x61e970)
  at 
/media/kinga/Dane/mir/mir_nowy/src/client/rpc/stream_socket_transport.cpp:40
  #8  0x76b0ad2c in std::_Function_handler&), 
mir::client::rpc::TransportObservers::on_data_available():: 
>::_M_invoke(const std::_Any_data &, const 
std::shared_ptr &) (__functor=..., 
__args#0=warning: RTTI symbol not found for class 
'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'
  warning: RTTI symbol not found for class 
'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'

  std::shared_ptr (count 3, weak 0) 0x61e970) at 
/usr/include/c++/5/functional:1871
  #9  0x76b0c551 in std::function 
const&)>::operator()(std::shared_ptr
 const&) const (this=0x74bc9bd0, 
  __args#0=warning: RTTI symbol not found for class 
'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'
  warning: RTTI symbol not found for class 
'std::_Sp_counted_deleter >, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr > const&, 
std::shared_ptr const&)::NullDeleter, 
std::allocator, (__gnu_cxx::_Lock_policy)2>'
  std::shared_ptr (count 3, weak 0) 0x6

[Touch-packages] [Bug 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

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

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #4  0x7fffed1d7ec6 in copy_config (conf=) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44
  #5  __base_ctor  (other=warning: RTTI symbol not found for class 
'mir::graphics::nested::NestedDisplayConfiguration'
  ..., this=0x7fffd8047300) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61

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

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


[Touch-packages] [Bug 1664180] Re: Crash in mesa::RealKMSOutput::max_refresh_rate() when hotplugging screens in host server

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  Crash in mesa::RealKMSOutput::max_refresh_rate() when hotplugging
  screens in host server

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

Bug description:
  Crash when hotplugging screen running mir_demo_server as a host server
  to qtmir.

  Crash file attached.

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

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


[Touch-packages] [Bug 1666181] Re: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  gnome-system-monitor crashed with SIGSEGV in make_protobuf_object()
  from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

Status in Mir:
  New
Status in gnome-system-monitor package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8 deb session
  gnome-system-monitor crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Mon Feb 20 12:29:22 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2016-12-12 (69 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: gnome-system-monitor
  Signal: 11
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: gnome-system-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


touch-packages@lists.launchpad.net

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  *** buffer overflow detected ***: unity8 terminated ... in
  MirEvent::deserialize(std::string const&)

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

Bug description:
  *** buffer overflow detected ***: unity8 terminated ... in
  MirEvent::deserialize(std::string const&)

  From one user's unity8.log:

  qtmir.mir: Command line arguments passed to Qt: ("unity8")
  [2016-10-05 15:44:31.663159] mirserver: Starting
  [2016-10-05 15:44:31.670542] mirserver: Using nested cursor
  *** buffer overflow detected ***: unity8 terminated
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fc167c71725]
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7fc167d1289c]
  /lib/x86_64-linux-gnu/libc.so.6(+0x1168a0)[0x7fc167d108a0]
  
/usr/lib/x86_64-linux-gnu/libmircommon.so.6(_ZN8MirEvent11deserializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x79)[0x7fc15d3aa9a9]
  
/usr/lib/x86_64-linux-gnu/libmirclient.so.9(_ZN3mir6events17deserialize_eventERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x1d)[0x7fc15f50667d]
  /usr/lib/x86_64-linux-gnu/libmirclient.so.9(+0x51fad)[0x7fc15f4fafad]
  /usr/lib/x86_64-linux-gnu/libmirclient.so.9(+0x4b857)[0x7fc15f4f4857]
  /usr/lib/x86_64-linux-gnu/libmirclient.so.9(+0x572d3)[0x7fc15f5002d3]
  /usr/lib/x86_64-linux-gnu/libmirclient.so.9(+0x4c0ed)[0x7fc15f4f50ed]
  /usr/lib/x86_64-linux-gnu/libmirclient.so.9(+0x4c1d7)[0x7fc15f4f51d7]
  
/usr/lib/x86_64-linux-gnu/libmircommon.so.5(_ZN3mir8dispatch24MultiplexingDispatchable8dispatchEj+0x134)[0x7fc15e500354]
  
/usr/lib/x86_64-linux-gnu/libmircommon.so.5(_ZN3mir8dispatch24MultiplexingDispatchable8dispatchEj+0x134)[0x7fc15e500354]
  /usr/lib/x86_64-linux-gnu/libmircommon.so.5(+0x2081f)[0x7fc15e50f81f]
  /usr/lib/x86_64-linux-gnu/libmircommon.so.5(+0x187fe)[0x7fc15e5077fe]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80)[0x7fc168291c80]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7fc1679e46fa]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc167d00b5d]

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

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


[Touch-packages] [Bug 1656250] Re: Unity8 crashes on screensaver suspend [Nested Mir Display Error: Failed to update EGL surface: EGL_BAD_CONTEXT (0x3006)]

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1656250

Title:
  Unity8 crashes on screensaver suspend [Nested Mir Display Error:
  Failed to update EGL surface: EGL_BAD_CONTEXT (0x3006)]

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

Bug description:
  On Zesty desktop with unity8-session 16.04 349

  Test Case
  1. Start a unity8 session
  2. Launch an app (eg Calculator)
  3. Wait 

  Expected result
  After an hour the session and the calculator are still running

  Actual result
  At some point (less than an hour) the session restarts (the calculator is 
gone if you were not staring at the screen when it restarted)

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

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


[Touch-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1625846

Title:
  Xmir -rootless: Firefox menus pop up then close right away

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Triaged
Status in MirAL:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  To reproduce:
  1) Open firefox on a rootless Xmir
  2) Right click or attempt to open the menu on the top right

  Expected:
  Menu to open

  Result:
  Menu pops up then closes right away.

  I think this is an expected bug, but dont remember the bug# soo figure
  would make one here :)

  *NOTE*: similar cause, but different usecase to lp:1662733

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

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


[Touch-packages] [Bug 1586382] Re: UnresponsiveClient.does_not_hang_server hangs server

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1586382

Title:
  UnresponsiveClient.does_not_hang_server hangs server

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

Bug description:
  10:35:12 [ RUN ] 
ServerWithoutActiveOutputs.creates_valid_client_surface
  10:35:12 [ OK ] 
ServerWithoutActiveOutputs.creates_valid_client_surface (51 ms)
  10:35:12 [--] 1 test from ServerWithoutActiveOutputs (51 ms 
total)
  10:35:12 
  10:35:12 [--] 2 tests from ServerStartup
  10:35:12 [ RUN ] ServerStartup.creates_endpoint_on_filesystem
  10:35:12 [ OK ] ServerStartup.creates_endpoint_on_filesystem (63 ms)
  10:35:12 [ RUN ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  10:35:13 [ OK ] 
ServerStartup.after_server_sigkilled_can_start_new_instance (110 ms)
  10:35:13 [--] 2 tests from ServerStartup (173 ms total)
  10:35:13 
  10:35:13 [--] 1 test from ServerStartupReliability
  10:35:13 [ RUN ] ServerStartupReliability.can_start_with_low_entropy
  10:35:13 [ OK ] ServerStartupReliability.can_start_with_low_entropy 
(38 ms)
  10:35:13 [--] 1 test from ServerStartupReliability (38 ms 
total)
  10:35:13 
  10:35:13 [--] 3 tests from DebugAPI
  10:35:13 [ RUN ] 
DebugAPI.translates_surface_coordinates_to_screen_coordinates
  10:35:13 [ OK ] 
DebugAPI.translates_surface_coordinates_to_screen_coordinates (56 ms)
  10:35:13 [ RUN ] 
DebugAPI.is_unavailable_when_server_not_started_with_debug
  10:35:13 [ OK ] 
DebugAPI.is_unavailable_when_server_not_started_with_debug (52 ms)
  10:35:13 [ RUN ] DebugAPI.is_overrideable
  10:35:13 [ OK ] DebugAPI.is_overrideable (53 ms)
  10:35:13 [--] 3 tests from DebugAPI (164 ms total)
  10:35:13 
  10:35:13 [--] 1 test from UnresponsiveClient
  10:35:13 [ RUN ] UnresponsiveClient.does_not_hang_server
  10:47:00 Build timed out (after 30 minutes). Marking the build as aborted.
  10:47:00 Build was aborted
  10:47:00 Archiving artifacts
  10:47:00 [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
  10:47:00 Finished: ABORTED

  Happened at least twice this week on krillin.

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

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


[Touch-packages] [Bug 1616312] Re: CI fails with error: invalid argument '/build/mir' to -fdebug-prefix-map

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1616312

Title:
  CI fails with error: invalid argument '/build/mir' to -fdebug-prefix-
  map

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

Bug description:
  CI fails with:

  cc1plus: error: invalid argument '/build/mir' to -fdebug-prefix-map
  or
  clang: error: invalid argument '/build/mir' to -fdebug-prefix-map

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

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

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


[Touch-packages] [Bug 1613523] Re: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1613523

Title:
  [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host

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

Bug description:
  Sounds like bug 1462033 but seems different...

  06:57:59 [ RUN ] 
NestedInput.nested_event_filter_receives_keyboard_from_host
  06:57:59 unknown file: Failure
  06:57:59 
  06:57:59 Unexpected mock function call - returning default value.
  06:57:59 Function call: handle(key_event(when=529970166879 (1.635846ms ago), 
from=1, down, code=97, scan=30, modifiers=1))
  06:57:59 Returns: false
  06:57:59 Google Mock tried the following 3 expectations, but none matched:
  06:57:59 
  06:57:59 
/build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195:
 tried expectation #0: EXPECT_CALL(nested_event_filter, 
handle(mt::InputDeviceStateEvent()))...
  06:57:59 Expected arg #0: input device state event
  06:57:59 Actual: key_event(when=529970166879 (1.214154ms ago), from=1, down, 
code=97, scan=30, modifiers=1)
  06:57:59 Expected: to be called once
  06:57:59 Actual: never called - unsatisfied and active
  06:57:59 
/build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:196:
 tried expectation #1: EXPECT_CALL(nested_event_filter, 
handle(mt::KeyOfScanCode(30)))...
  06:57:59 Expected: all pre-requisites are satisfied
  06:57:59 Actual: the following immediate pre-requisites are not satisfied:
  06:57:59 
/build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195:
 pre-requisite #0
  06:57:59 (end of pre-requisites)
  06:57:59 Expected: to be called at least once
  06:57:59 Actual: never called - unsatisfied and active
  06:57:59 
/build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:200:
 tried expectation #2: EXPECT_CALL(nested_event_filter, 
handle(mt::KeyOfScanCode(54)))...
  06:57:59 Expected arg #0: key of scan code 54
  06:57:59 Actual: key_event(when=529970166879 (1.579538ms ago), from=1, down, 
code=97, scan=30, modifiers=1)
  06:57:59 Expected: to be called twice
  06:57:59 Actual: never called - unsatisfied and active
  06:57:59 [ FAILED ] 
NestedInput.nested_event_filter_receives_keyboard_from_host (200 ms)

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

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

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


[Touch-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few

2017-11-03 Thread 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/1211700

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

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

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

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

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

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

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

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


[Touch-packages] [Bug 1209441] Re: [enhancement] Need automation to run stress test as part of CI process

2017-11-03 Thread 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/1209441

Title:
  [enhancement] Need automation to run stress test as part of CI process

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

Bug description:
  We need to run the mir stress test suite as part of the CI automation
  process. This requires the following:

   * A Jenkins job that take a source branch as a parameter. That job should 
provision an up-to-date saucy machine and:
- Build the source branch packages
- Install the mir-demos and mir-test-tools packages
- From a VT, run mir_demo_server
- run "mir_stress -n 60", and check the return code of the mir_stress 
program. If it exited with a RC of 0, the jenkins job should pass. If it exits 
with any other return code, or fails to exit after 60 seconds (maybe 80 
seconds, to give it some grace time), the job should fail.
- (optional) Sends Ctrl+C to the mir_demo_server.

  
  Once that's in place we need to hook this job up to the mir CI stack, so we 
cannot land mir code that breaks the stress tests.

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

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


[Touch-packages] [Bug 1522104] Re: Workaround to fix 1521651 needs further improvement

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

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

Title:
  Workaround to fix 1521651 needs further improvement

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

Bug description:
  lp: #1521651 was worked around by disabling the x11 input platform based on 
the VT switch.
  https://code.launchpad.net/~andreas-pokorny/mir/band-aid-1521651/+merge/279272

  This is ugly because we shouldn't have the x11 platform(s) dependent
  on switches specific to kms platform(s) - it doesn't scale in the
  number of platforms supported.

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

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


[Touch-packages] [Bug 1194384] Re: Mir client callbacks are not thread-safe

2017-11-03 Thread 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/1194384

Title:
  Mir client callbacks are not thread-safe

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

Bug description:
  Mir clients may not be aware, but the callbacks made by libmirclient
  are not thread safe in any way.

  An apparently simple single-threaded Mir client has 3 threads, which
  can execute concurrently:

  1. The "main" thread, where the initial connection was made.
  2. The socket thread, where the protocol is handled (mir_connected_callback, 
mir_surface_callback, MirSurfaceEvent)
  3. The input thread, where input events are received (MirMotionEvent, 
MirKeyEvent)

  Yes, you could receive a MirSurfaceEvent and MirMotionEvent
  simultaneously in different threads. Neither of which are the main
  thread.

  This is how a Mir client works. Unfortunately the existence of these
  threads is not yet documented. I will update the docs. But this bug is
  really about finding a way to make the client API more thread safe for
  simple toolkits and clients that normally don't care about threads.
  UPDATE: Client API docs improved in r789.

  To make matters worse, the client API functions are generally not
  thread safe either: mir_surface_* mir_connection_*. So libmirclient
  forces you to run in multiple threads and yet doesn't protect you at
  all against races and corruption that could arise from calling
  libmirclient from varying threads. UPDATE: Fixed in r827

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

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


[Touch-packages] [Bug 1193933] Re: [enhancement] [docs] How to write a a Mir backend for a toolkit

2017-11-03 Thread 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/1193933

Title:
  [enhancement] [docs] How to write a a Mir backend for a toolkit

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

Bug description:
  Document how to write a a Mir backend for a graphical toolkit (e.g.
  Qt, GTK+)

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

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


[Touch-packages] [Bug 1211063] Re: [enhancement] Add support for color profiles

2017-11-03 Thread 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/1211063

Title:
  [enhancement] Add support for color profiles

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Open system settings, select color. Select a color profile. With X,
  the change was live. With XMir, the profile is not applied.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-system-compositor 0.0.1+13.10.20130810.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Sun Aug 11 23:24:53 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-02-20 (537 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac 
(20120220)
  MarkForUpload: True
  SourcePackage: unity-system-compositor
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (0 days ago)

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

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


[Touch-packages] [Bug 1169020] Re: [regression] Mir gives up too easily - std::exception::what: Failed to find the current VT

2017-11-03 Thread 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/1169020

Title:
  [regression] Mir gives up too easily - std::exception::what: Failed to
  find the current VT

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

Bug description:
  I have always run Mir from an ssh login, but also made sure I have a
  VT1 login on the console too. This has worked well until recently. Now
  we seem to have introduced a restriction that mir can only be started
  from the physical console...

  $ bin/mir
  ERROR: 
/home/dan/bzr/mir/trunk/src/server/graphics/gbm/linux_virtual_terminal.cpp(70): 
Throw in function int {anonymous}::find_active_vt_number()
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to find the current VT

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

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


[Touch-packages] [Bug 1195978] Re: Trackpad isn't recognized on logging in to multiple users

2017-11-03 Thread 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/1195978

Title:
  Trackpad isn't recognized on logging in to multiple users

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

Bug description:
  The trackpad isn't recognized on logging into multiple users. The
  software cursor is still present on the screen. Everything else,
  including the keyboard, still works.

  To reproduce the bug, log into a user session and switch to the guest
  session.

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

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


[Touch-packages] [Bug 1523621] Re: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host)

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1523621

Title:
  [ FAILED ] NestedServer.*_cursor_* (usually
  NestedServer.named_cursor_image_changes_are_forwarded_to_host)

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

Bug description:
  while bin/mir_acceptance_tests
  --gtest_filter=NestedServer.named_cursor_image_changes_are_forwarded_to_host;
  do :; done

  fails after a few hundred iterations.

  NB There two are other tests that are probably manifesting the same
  underlying issue:

  NestedServer.can_hide_the_host_cursor
  NestedServer.animated_cursor_image_changes_are_forwarded_to_host

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

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


[Touch-packages] [Bug 1102772] Re: /dev/dri permissions not set

2017-11-03 Thread 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/1102772

Title:
  /dev/dri permissions not set

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

Bug description:
  /dev/dri permissions are not set correctly when logging in to an mir
  seat.

  This is probably caused by not correctly ConsoleKit-ing the session, or 
something. Indeed, under this XMir session I have:
  ck-list-sessions:
  Session7:
unix-user = '1000'
realname = 'Christopher James Halse Rogers'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2013-01-22T04:34:11.320077Z'
login-session-id = '4294967295'
  Session9:
unix-user = '1000'
realname = 'Christopher James Halse Rogers'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2013-01-22T04:34:18.727880Z'
login-session-id = '4294967295'

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

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


[Touch-packages] [Bug 1175721] Re: We lack a good testing story for our use of egl/drm/gbm/...

2017-11-03 Thread 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/1175721

Title:
  We lack a good testing story for our use of egl/drm/gbm/...

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

Bug description:
  In trying to write an integration test for the hardware cursor spike
  it became apparent:

  1. The linkage seam used MockEGL, MockDRM affects all tests in the binary.
  2. That we have code that depend on the runtime environment (egl, drm, gbm, 
ioctl) that isn't cleanly isolated from other logic
  3. There is no easy way to substitute a stub/mock for the runtime environment

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

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


[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2017-11-03 Thread Norbert
** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: brasero (Ubuntu)

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Confirmed
Status in chromium package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Touch-packages] [Bug 1729887] [NEW] Drag-and-drop to desktop not possible without copying the file under wayland

2017-11-03 Thread John Does
Public bug reported:

since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-and-
drop from any folder to my desktop are copied but not moved.

Using strg+x and strg+v works. When i open the desktop as a folder usual
drag-and-drop from different folders do work without copying the files.

This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
before and allows normal drag-and-drop from folders to the desktop.


(I reported the issue before at https://askubuntu.com/questions/972533/)

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


** Tags: desktop wayland

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

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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


[Touch-packages] [Bug 1706471] Re: please demote exiv2 to universe

2017-11-03 Thread Adam Conrad
Unsubscribing ~ubuntu-archive, this is up to the desktop team to choose
to remove from their seeds and, if they do, our magic reports will tell
us to demote, we don't need a bug for that.

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

Title:
  please demote exiv2 to universe

Status in gexiv2:
  Confirmed
Status in exiv2 package in Ubuntu:
  Triaged

Bug description:
  Hello,

  Please consider demoting exiv2 to universe.

  http://dev.exiv2.org/issues/1248

  The upstream author appears overwhelmed with the task of hardening
  exiv2 for use against untrusted inputs and thus far (~nine months) no
  users have provided the project with patches against known issues.

  $ reverse-depends -c main -r artful src:exiv2
  Reverse-Depends
  ===
  * libgexiv2-2   (for libexiv2-14)
  * libgexiv2-dev (for libexiv2-dev)

  Thanks

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

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


[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2017-11-03 Thread Colin Leroy
Hi,
Yeah. That bug hits a lot of applications because GTK+3 does things differently 
than GTK+2 in this regard, which is why I submitted the bugreport (and a patch) 
to GTK+3 instead of all these applications.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Confirmed
Status in chromium package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2017-11-03 Thread Adam Conrad
Removing packages from bionic:
lubuntu-software-center 0.0.10-0ubuntu2 in bionic
lubuntu-software-center 0.0.10-0ubuntu2 in bionic amd64
lubuntu-software-center 0.0.10-0ubuntu2 in bionic arm64
lubuntu-software-center 0.0.10-0ubuntu2 in bionic armhf
lubuntu-software-center 0.0.10-0ubuntu2 in bionic i386
lubuntu-software-center 0.0.10-0ubuntu2 in bionic ppc64el
lubuntu-software-center 0.0.10-0ubuntu2 in bionic s390x
Comment: Obsolete and unused; LP: #1673258
Remove [y|N]? y
1 package successfully removed.


** Changed in: lubuntu-software-center (Ubuntu)
   Status: New => Fix Released

** Changed in: lubuntu-software-center (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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


[Touch-packages] [Bug 1728931] Re: [testsfail] ServerDisconnect.is_detected_by_client

2017-11-03 Thread 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/1728931

Title:
  [testsfail] ServerDisconnect.is_detected_by_client

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

Bug description:
  [ RUN ] ServerDisconnect.is_detected_by_client
  [2017-10-27 21:38:41.897919] mirserver: Starting
  [2017-10-27 21:38:41.898180] mirserver: Selected driver: mir:stub-graphics 
(version 0.28.1)
  [2017-10-27 21:38:41.908376] mirserver: Using software cursor
  [2017-10-27 21:38:41.912088] mirserver: Selected input driver: mir:stub-input 
(version: 0.28.1)
  [2017-10-27 21:38:41.920187]  mirserver: No WaylandAllocator EGL 
support!
  error: XDG_RUNTIME_DIR not set in the environment
  [2017-10-27 21:38:41.922664] mirserver: Mir version 0.28.1
  [2017-10-27 21:38:41.923122] mirserver: Initial display configuration:
  [2017-10-27 21:38:41.923141] mirserver: CTestConfig.cmake CTestTestfile.cmake 
mir_acceptance_tests.bin_10.xml mir_acceptance_tests.bin_11.xml 
mir_acceptance_tests.bin_1.xml mir_acceptance_tests.bin_2.xml 
mir_acceptance_tests.bin_3.xml mir_acceptance_tests.bin_4.xml 
mir_acceptance_tests.bin_5.xml mir_acceptance_tests.bin_6.xml 
mir_acceptance_tests.bin_7.xml mir_acceptance_tests.bin_8.xml 
mir_acceptance_tests.bin_9.xml mir_acceptance_tests.bin.xml steer.cmake Testing 
Output 1: VGA connected, used
  [2017-10-27 21:38:41.923157] mirserver: . |_ Physical size 0.0" 0x0mm
  [2017-10-27 21:38:41.923162] mirserver: . |_ Power is on
  [2017-10-27 21:38:41.923167] mirserver: . |_ Current mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923172] mirserver: . |_ Preferred mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923175] mirserver: . |_ Orientation normal
  [2017-10-27 21:38:41.923181] mirserver: . |_ Logical size 1600x1600
  [2017-10-27 21:38:41.923184] mirserver: . |_ Logical position +0+0
  [2017-10-27 21:38:41.923188] mirserver: . |_ Scaling factor: 1.00
  [2017-10-27 21:38:41.940284] mirserver: Stopping
  /spread/mir/tests/mir_test_framework/interprocess_client_server_test.cpp:167: 
Failure
  Value of: result.exit_code
  Expected: is equal to 0
  Actual: 1 (of type int)
  [2017-10-27 21:38:41.953366]  MirWindowAPI: Caught exception at client 
library boundary (in window_release_helper): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [2017-10-27 21:38:41.953754]  MirConnectionAPI: Caught exception at 
client library boundary (in mir_connection_release): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [ FAILED ] ServerDisconnect.is_detected_by_client (58 ms)

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

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


[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-11-03 Thread 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1669524

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

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

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

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

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

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


[Touch-packages] [Bug 1649758] Re: [ FAILED ] LifecycleEventTest.lifecycle_event_test

2017-11-03 Thread 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/1649758

Title:
  [ FAILED ] LifecycleEventTest.lifecycle_event_test

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

Bug description:
  16:16:26 13: [ RUN ] LifecycleEventTest.lifecycle_event_test
  ...
  16:16:28 13: 
/<>/mir-0.25.0+yakkety3172bzr3818/tests/integration-tests/shell/test_session_lifecycle_event.cpp:85:
 Failure
  16:16:28 13: Actual function call count doesn't match EXPECT_CALL(*handler, 
state_changed(Eq(mir_lifecycle_state_will_suspend)))...
  16:16:28 13: Expected: to be called once
  16:16:28 13: Actual: never called - unsatisfied and active
  16:16:28 13: [ FAILED ] LifecycleEventTest.lifecycle_event_test (2292 ms)

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

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

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


[Touch-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few

2017-11-03 Thread 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/1211700

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

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

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

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

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

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

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

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


[Touch-packages] [Bug 1542782] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

2017-11-03 Thread Jim Campbell
Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date

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

Title:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I do not know, this error was made in a background.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  7 08:36:54 2016
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2016-02-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7fbb1b3300 : 
movzbl 0xc0(%rdi),%eax
   PC (0x7f7fbb1b3300) ok
   source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   g_desktop_app_info_get_is_hidden () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
  Title: unity-scope-loader crashed with SIGSEGV in 
g_desktop_app_info_get_is_hidden()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1169020] Re: [regression] Mir gives up too easily - std::exception::what: Failed to find the current VT

2017-11-03 Thread 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/1169020

Title:
  [regression] Mir gives up too easily - std::exception::what: Failed to
  find the current VT

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

Bug description:
  I have always run Mir from an ssh login, but also made sure I have a
  VT1 login on the console too. This has worked well until recently. Now
  we seem to have introduced a restriction that mir can only be started
  from the physical console...

  $ bin/mir
  ERROR: 
/home/dan/bzr/mir/trunk/src/server/graphics/gbm/linux_virtual_terminal.cpp(70): 
Throw in function int {anonymous}::find_active_vt_number()
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to find the current VT

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

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


[Touch-packages] [Bug 1728931] Re: [testsfail] ServerDisconnect.is_detected_by_client

2017-11-03 Thread 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/1728931

Title:
  [testsfail] ServerDisconnect.is_detected_by_client

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

Bug description:
  [ RUN ] ServerDisconnect.is_detected_by_client
  [2017-10-27 21:38:41.897919] mirserver: Starting
  [2017-10-27 21:38:41.898180] mirserver: Selected driver: mir:stub-graphics 
(version 0.28.1)
  [2017-10-27 21:38:41.908376] mirserver: Using software cursor
  [2017-10-27 21:38:41.912088] mirserver: Selected input driver: mir:stub-input 
(version: 0.28.1)
  [2017-10-27 21:38:41.920187]  mirserver: No WaylandAllocator EGL 
support!
  error: XDG_RUNTIME_DIR not set in the environment
  [2017-10-27 21:38:41.922664] mirserver: Mir version 0.28.1
  [2017-10-27 21:38:41.923122] mirserver: Initial display configuration:
  [2017-10-27 21:38:41.923141] mirserver: CTestConfig.cmake CTestTestfile.cmake 
mir_acceptance_tests.bin_10.xml mir_acceptance_tests.bin_11.xml 
mir_acceptance_tests.bin_1.xml mir_acceptance_tests.bin_2.xml 
mir_acceptance_tests.bin_3.xml mir_acceptance_tests.bin_4.xml 
mir_acceptance_tests.bin_5.xml mir_acceptance_tests.bin_6.xml 
mir_acceptance_tests.bin_7.xml mir_acceptance_tests.bin_8.xml 
mir_acceptance_tests.bin_9.xml mir_acceptance_tests.bin.xml steer.cmake Testing 
Output 1: VGA connected, used
  [2017-10-27 21:38:41.923157] mirserver: . |_ Physical size 0.0" 0x0mm
  [2017-10-27 21:38:41.923162] mirserver: . |_ Power is on
  [2017-10-27 21:38:41.923167] mirserver: . |_ Current mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923172] mirserver: . |_ Preferred mode 1600x1600 60.00Hz
  [2017-10-27 21:38:41.923175] mirserver: . |_ Orientation normal
  [2017-10-27 21:38:41.923181] mirserver: . |_ Logical size 1600x1600
  [2017-10-27 21:38:41.923184] mirserver: . |_ Logical position +0+0
  [2017-10-27 21:38:41.923188] mirserver: . |_ Scaling factor: 1.00
  [2017-10-27 21:38:41.940284] mirserver: Stopping
  /spread/mir/tests/mir_test_framework/interprocess_client_server_test.cpp:167: 
Failure
  Value of: result.exit_code
  Expected: is equal to 0
  Actual: 1 (of type int)
  [2017-10-27 21:38:41.953366]  MirWindowAPI: Caught exception at client 
library boundary (in window_release_helper): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [2017-10-27 21:38:41.953754]  MirConnectionAPI: Caught exception at 
client library boundary (in mir_connection_release): 
/spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function 
virtual void mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  [ FAILED ] ServerDisconnect.is_detected_by_client (58 ms)

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

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


[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2017-11-03 Thread Jeremy Bicha
mythbuntu-control-center Deleted on 2017-03-31 by Steve Langasek
discontinued flavor; LP: #1639445

** Changed in: mythbuntu-control-centre (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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


[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-11-03 Thread 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1669524

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

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

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

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

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

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


[Touch-packages] [Bug 1649758] Re: [ FAILED ] LifecycleEventTest.lifecycle_event_test

2017-11-03 Thread 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/1649758

Title:
  [ FAILED ] LifecycleEventTest.lifecycle_event_test

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

Bug description:
  16:16:26 13: [ RUN ] LifecycleEventTest.lifecycle_event_test
  ...
  16:16:28 13: 
/<>/mir-0.25.0+yakkety3172bzr3818/tests/integration-tests/shell/test_session_lifecycle_event.cpp:85:
 Failure
  16:16:28 13: Actual function call count doesn't match EXPECT_CALL(*handler, 
state_changed(Eq(mir_lifecycle_state_will_suspend)))...
  16:16:28 13: Expected: to be called once
  16:16:28 13: Actual: never called - unsatisfied and active
  16:16:28 13: [ FAILED ] LifecycleEventTest.lifecycle_event_test (2292 ms)

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

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

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


[Touch-packages] [Bug 1286252] Re: mir_demo_server* successfully start without input support as non-root, making them unusable

2017-11-03 Thread 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/1286252

Title:
  mir_demo_server* successfully start without input support as non-root,
  making them unusable

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

Bug description:
  On desktop PC

  1. Switch to VT1
  2. Log in as non-root user
  3. Run mir_demo_server_shell
  4. Try to stop it and get back to your X session

  I'm a Macbook user, so please keep that in mind before suggesting a
  kernel specific keystroke trick.

  This is really annoying, I keep falling into this trap.

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

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


[Touch-packages] [Bug 1169020] Re: [regression] Mir gives up too easily - std::exception::what: Failed to find the current VT

2017-11-03 Thread 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/1169020

Title:
  [regression] Mir gives up too easily - std::exception::what: Failed to
  find the current VT

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

Bug description:
  I have always run Mir from an ssh login, but also made sure I have a
  VT1 login on the console too. This has worked well until recently. Now
  we seem to have introduced a restriction that mir can only be started
  from the physical console...

  $ bin/mir
  ERROR: 
/home/dan/bzr/mir/trunk/src/server/graphics/gbm/linux_virtual_terminal.cpp(70): 
Throw in function int {anonymous}::find_active_vt_number()
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: Failed to find the current VT

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

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


[Touch-packages] [Bug 1233181] Re: [enhancement] libmirserver needs a better arg parsing mechanism

2017-11-03 Thread 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/1233181

Title:
  [enhancement] libmirserver needs a better arg parsing mechanism

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

Bug description:
  so there was a quick fix for this particular issue, originally reported in 
this bug
  https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1226227
  with this merge proposal
  https://code.launchpad.net/~mterry/mir/dev-unregistered-options/+merge/188177

  however, all agree there should be a better way per the bug
  correspondence in bug#1226227

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

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


[Touch-packages] [Bug 1216329] Re: unity-system-compositor crashed with SIGSEGV in ~task_cleanup

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1216329

Title:
  unity-system-compositor crashed with SIGSEGV in ~task_cleanup

Status in Mir:
  Incomplete
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  I was opening synaptic and compiz crashed and after that this error
  appear.

  The compiz crash was reported as bug 1216325

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-system-compositor 0.0.1+13.10.20130822.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Sat Aug 24 09:33:50 2013
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5730 / 
6570M] [1002:68c0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1594]
  InstallationDate: Installed on 2013-03-16 (161 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 
--vt 7
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f41b4733f74 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7f41b4733f74) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x14af1f0) at pthread_mutex_lock.c:50
   boost::asio::detail::task_io_service::run(boost::system::error_code&) () 
from /usr/lib/x86_64-linux-gnu/libmirserver.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   start_thread (arg=0x7f41a6759700) at pthread_create.c:311
  Title: unity-system-compositor crashed with SIGSEGV in 
__GI___pthread_mutex_lock()
  UnitySystemCompositorLog:
   dm_connection_start
   set_active_session '0'
   set_active_session
   Segmentation fault (core dumped)
  UpgradeStatus: Upgraded to saucy on 2013-03-17 (160 days ago)
  UserGroups:

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

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

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


[Touch-packages] [Bug 1230091] Re: [enhancement] Trusted Session surface management (required for appstore app trust model), modal subwindows

2017-11-03 Thread 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/1230091

Title:
  [enhancement] Trusted Session surface management (required for
  appstore app trust model), modal subwindows

Status in content-hub:
  Invalid
Status in Mir:
  Triaged
Status in unity-mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in signon package in Ubuntu:
  Invalid
Status in unity-mir package in Ubuntu:
  Triaged

Bug description:
  (I'm filing this as a bug in order to be able to point other people to
  it, and to track its progress; if there's a blueprint containing this
  task, please let me know)

  Some components (such as the Online Accounts trusted helper) need to
  be able to pop-up a window (typically, a dialog) on top of the running
  application. Such windows should be modal to the application, that is
  the user should not be able to interact with the application while the
  modal window is displayed on top of them. This also means that in the
  task switcher one shouldn't see two windows, but only the topmost
  modal window (and parts of the application window, in case the modal
  window on top is a non-fullscreen dialog).

  For developers, this API already exists in Qt: 
http://doc.qt.io/qt-5/qwindow.html#fromWinId
  It needs to be implemented in the QPA plugin, so feel free to add the 
relevant projects to the bug report.

  From jdstrand>
  This is a hard requirement for application confinement because of our trust 
model-- permission to access sensitive data by AppStore apps is typically 
granted or denied at the time of access (caching the result for later use as 
appropriate), so users have a context for the access being requested. We do 
this instead of throwing up a permissions prompt at installation. However, for 
it to work, trusted helpers like online accounts and location require this 
functionality from unity-mir. A trust-store is also being implemented so other 
services like calendar and contacts can do the same. Because this feature is 
not implemented, the implementation for online accounts, location and the 
trust-store is blocked and appstore apps are therefore able to access these 
services without the user knowing.

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

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


[Touch-packages] [Bug 1224252] Re: VTs become blank and unusable after "sudo stop lightdm"

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1224252

Title:
  VTs become blank and unusable after "sudo stop lightdm"

Status in Light Display Manager:
  Incomplete
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  VTs become blank and unusable after "sudo stop lightdm".

  All I want to do is stop unity-system-compositor so I can run and test my own 
server. So I:
    sudo stop lightdm
  This works, but it leaves me with a black screen and no opportunity to switch 
VTs. The system is essentially unusable till you ssh in and "sudo start 
lightdm".

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

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


[Touch-packages] [Bug 1284411] Re: [enhancement] enable ThreadSanitizer test suite

2017-11-03 Thread Michał Sawicz
Syncing task from Mir.

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

** 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/1284411

Title:
  [enhancement] enable ThreadSanitizer test suite

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

Bug description:
  https://code.google.com/p/data-race-test/wiki/ThreadSanitizer

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

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


  1   2   3   4   >