date:20180426

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

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


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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

** Summary changed:

- bluetooth cann't open
+ Atheros QCA9565 bluetooth hardware not detected

** This bug has been marked a duplicate of bug 1532267
   Atheros QCA9565 Bluetooth not recognized

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

Title:
  Atheros QCA9565 bluetooth hardware not detected

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2018-04-26 Thread Abhik

Hi,

Same issue.

I am using similar test application to get the neighboring mac addresses
on a Centos 7.2.1511 machine. Installed 3.21, 3.28, 3.4 versions and all
returned with NULL.

Is this going to be fixed? Or Is there any other API within libnl3 that
can do the trick?

Abhik

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

Title:
  nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

Status in libnl:
  New
Status in libnl3 package in Ubuntu:
  In Progress

Bug description:
  Retrieving information about configured neighbors fail 
  my application is running the following procedure:

  neigh = NULL;
  cache = rtnl_neigh_alloc_cache(sk);
  while(NULL == neigh){
  nl_cache_refill(sk, chache);
  neigh = rtnl_neigh_get(cache, ifindex, dst_addr);
  }

  with libnl3 3.2.21-1 this loop will never end, even when adding a static arp 
entry.
  However, with libnl-3.2.24 the neighbor lookup succeed.

  additional general info:
  $ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  $ uname -r
  3.13.0-24-generic
  $ apt-cache policy libnl-genl-3-200 libnl-route-3-200
  libnl-genl-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libnl-route-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1767258] Re: bluetooth cann't open

Please try toggling the switch in the header bar to ON (next to the
minimize/maximize/close buttons).

If that doesn't work then it appears the problem is that the kernel has
not detected your bluetooth hardware (see rfkill.txt above).


** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (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/1767258

Title:
  bluetooth cann't open

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Touch-packages] [Bug 1767258] [NEW] bluetooth cann't open

2018-04-26 Thread jackchwang

Public bug reported:

I can't open bluetooth in the setting panel,it's gray.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 12:01:53 2018
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
InterestingModules: bnep btusb bluetooth
MachineType: Acer TravelMate P257-MG
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA50_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: TravelMate P257-MG
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

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

Title:
  bluetooth cann't open

Status in bluez package in Ubuntu:
  New

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2018-04-26 Thread Abhik

** Also affects: libnl
   Importance: Undecided
   Status: New

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

Title:
  nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

Status in libnl:
  New
Status in libnl3 package in Ubuntu:
  In Progress

Bug description:
  Retrieving information about configured neighbors fail 
  my application is running the following procedure:

  neigh = NULL;
  cache = rtnl_neigh_alloc_cache(sk);
  while(NULL == neigh){
  nl_cache_refill(sk, chache);
  neigh = rtnl_neigh_get(cache, ifindex, dst_addr);
  }

  with libnl3 3.2.21-1 this loop will never end, even when adding a static arp 
entry.
  However, with libnl-3.2.24 the neighbor lookup succeed.

  additional general info:
  $ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  $ uname -r
  3.13.0-24-generic
  $ apt-cache policy libnl-genl-3-200 libnl-route-3-200
  libnl-genl-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libnl-route-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1767246] [NEW] package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 仍未被配置

2018-04-26 Thread zhaorodger

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxdamage1:i386 1:1.1.4-2
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr 23 10:02:26 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ErrorMessage: 依赖关系问题 - 仍未被配置
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
InstallationDate: Installed on 2016-08-02 (632 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: LENOVO 4291N96
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=bd4fd09f-c9c0-45d0-941d-ca61fc81d0ab ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: libxdamage
Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 
仍未被配置
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET72WW (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291N96
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET72WW(1.42):bd02/18/2016:svnLENOVO:pn4291N96:pvrThinkPadX220:rvnLENOVO:rn4291N96:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291N96
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: apport-package i386 ubuntu xenial

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

Title:
  package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 -
  仍未被配置

Status in libxdamage package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxdamage1:i386 1:1.1.4-2
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Apr 23 10:02:26 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: 依赖关系问题 - 仍未被配置
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2016-08-02 (632 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 4291N96
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=bd4fd09f-c9c0-45d0-941d-ca61fc81d0ab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: libxdamage
  Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 
仍未被配置
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET72WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291N96
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET72WW(1.42):bd02/18/2016:svnLENOVO:pn4291N96:pvrThinkPadX220:rvnLENOVO:rn4291N96:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291N96

[Touch-packages] [Bug 1767124] Re: bluetoothd crashed with SIGILL

I can't seem to find any existing reports of this crash. All I can tell
is that it looks like Ubuntu 16.04...

Please help us to debug it further by:

1. Applying the workaround from bug 994921.

2. Look in /var/crash for .crash files and when found run:
   ubuntu-bug /var/crash/YOURFILE.crash

3. Tell us here the ID of the newly-created bug.

** Tags added: xenial

** Summary changed:

- bluetoothd crashed with SIGILL
+ bluetoothd crashed with SIGILL in agent_get() from adapter_register()

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

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

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

Re: [Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: * Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 * in g_strfreev() from g_themed_icon_finalize() fr

2018-04-26 Thread chris pollock

On Fri, 2018-04-27 at 01:32 +, Daniel van Vugt wrote:
> Chris,
> 
> You seem to have opened two bugs for this crash. Bug 1706203 is
> almost
> the same.
> 
> If it's still happening then let's continue using bug 1706203.
> 
Sounds good to me, I'll just have to remember the next time it happens
and 1616651 comes up to actually post any output into 1706203.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
20:57:55 up 3:48, 1 user, load average: 0.91, 0.79, 0.75
Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-39-generic

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from
  g_themed_icon_finalize() from g_object_unref() from
  desktop_entry_unref()

Status in libgweather:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:

  [Impact] 
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
   __GI___libc_free (mem=) at malloc.c:2969
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

Please also run this command to automatically attach more system
information:

  apport-collect 1767065

P.S. Ubuntu 18.04 was released a few hours ago :)
https://www.ubuntu.com/

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

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome
  as desktop environments.

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

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

I also agree that https://imgur.com/qS0ODeq would be best.

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: * Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 * in g_strfreev() from g_themed_icon_finalize() from g

Chris,

You seem to have opened two bugs for this crash. Bug 1706203 is almost
the same.

If it's still happening then let's continue using bug 1706203.

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from
  g_themed_icon_finalize() from g_object_unref() from
  desktop_entry_unref()

Status in libgweather:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  
  [Impact] 
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
   __GI___libc_free (mem=) at malloc.c:2969
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Touch-packages] [Bug 1767228] [NEW] Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04

2018-04-26 Thread Jonty Gamao

Public bug reported:

After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm
seeing is my mouse cursor, which responds to my movements, and that's
pretty much it. I tried to see if I can start up sddm, but that failed.

I got to login by installing slick-greeter and use that instead.

After logging in, the message says:


Plasma is unable to start as it could not correctly use OpenGL 2. Please check 
that your graphics drivers are set up correctly. 


I checked the environment variable `$DISPLAY`, but it seems to be unset.

I tried reinstalling `plasma-desktop`, `sddm`, `mesa` drivers, `xorg`,
`xserver-xorg*intel`, `kde*`, `kwin`, and `nvidia-340` drivers.

My laptop is a Lenovo Z40 with NVIDIA GT810m (currently disabled and
using Intel HD Graphics).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Apr 26 20:51:46 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 nvidia-340, 340.106, 4.15.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
   Subsystem: Lenovo GeForce 820M [17aa:380d]
InstallationDate: Installed on 2017-04-11 (380 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411)
MachineType: LENOVO 20366
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8258f7ec-7593-4407-95b1-cf77cc95da6c ro nogpumanager quiet splash 
nouveau.runpm=0 vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN91WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 4A5
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z40-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20366
dmi.product.version: Lenovo Z40-70
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm
  seeing is my mouse cursor, which responds to my movements, and that's
  pretty much it. I tried to see if I can start up sddm, but that
  failed.

  I got to login by installing slick-greeter and use that instead.

  After logging in, the message says:

  
  Plasma is unable to start as it could not correctly use OpenGL 2. Please 
check that your graphics drivers are set up correctly. 
  

  I checked the environment variable `$DISPLAY`, but it seems to be
  unset.

  I tried reinstalling `plasma-desktop`, `sddm`, `mesa` drivers, `xorg`,
  `xserver-xorg*intel`, `kde*`, `kwin`, and `nvidia-340` drivers.

  My laptop is a Lenovo Z40 with NVIDIA GT810m (currently disabled and
  using Intel HD Graphics).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Apr 26 20:51:46 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu

[Touch-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager

2018-04-26 Thread Kenneth R. Crudup

I believe I am affected by this issue as well. I have a Google WiFi
device as a router, and everything works well for the first few days,
with the link-local address used on the Google WiFi's RA used as the
IPv6 default route.

After a couple of days however, the Google WiFi device changes its link-
local address (for some reason) on the LAN subnet, and although an RA
goes out with this new link-local address, NetworkManager still hangs
onto the old default route (which is marked "static" as well) and as
such I lose IPv6 connectivity to the outside world. I have to run "nmcli
conn up Ethernet" to force NM to delete the old default route and use a
the new one.

Also, if I manually "ip -6 replace default ..." leaving the line
otherwise intact as it comes from NM, changing only "proto static" to
"proto ra", as soon as the Google WiFi sends another RA, NM re-writes
the default as "proto static"- yet does NOT update the actual "via"
link-local address to the one the RA came in on.

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

Title:
  IPv6 static default route added incorrectly by network-manager

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The relevant part of the IPv6 routing table looks like this:

  fe80::/64 dev wlan0  proto kernel  metric 256
  default via fe80::5054:ff:fe64:aad0 dev wlan0  proto static  metric 1
  default via fe80::5054:ff:fe9c:741e dev wlan0  proto kernel  metric 1024  
expires 8sec
  default via fe80::5054:ff:fe64:aad0 dev wlan0  proto kernel  metric 1024  
expires 10sec

  I believe the proto static metric 1 route is an error, since it
  persists even when the router stops advertising.  This breaks the IPv6
  architecture for router redundancy.

  I am in control of this network and can alter router advertisement
  parameters if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sat Jan 19 10:47:05 2013
  InstallationDate: Installed on 2012-11-15 (65 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  IpRoute:
   default via 192.168.4.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.4.0/24 dev wlan0  proto kernel  scope link  src 192.168.4.64  metric 
9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group 
rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2012-11-25T12:30:38.408468
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1767219] [NEW] Audio Delay - [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem

2018-04-26 Thread Diogo Filho de Morais

Public bug reported:

When I put the audio out on the TV through HDMI there is a delay for the
sound to start appearing after leaving a video or music paused for a few
minutes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  diogo  2410 F pulseaudio
 /dev/snd/pcmC0D3p:   diogo  2410 F...m pulseaudio
 /dev/snd/controlC0:  diogo  2410 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 26 20:01:34 2018
InstallationDate: Installed on 2018-04-20 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful
Symptom_Card: Áudio interno - HDA Intel HDMI
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02RDQ.029.160707.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP300E5K-KF1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8732A0Z-C01-G001-S0001+10.0.10586
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02RDQ.029.160707.JJ:bd07/07/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5K/300E5Q:pvrP02RDQ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5K-KF1BR:rvrSGL8732A0Z-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 300E5K/300E5Q
dmi.product.version: P02RDQ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

Title:
  Audio Delay - [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I put the audio out on the TV through HDMI there is a delay for
  the sound to start appearing after leaving a video or music paused for
  a few minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  diogo  2410 F pulseaudio
   /dev/snd/pcmC0D3p:   diogo  2410 F...m pulseaudio
   /dev/snd/controlC0:  diogo  2410 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 20:01:34 2018
  InstallationDate: Installed on 2018-04-20 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful
  Symptom_Card: Áudio interno - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02RDQ.029.160707.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP300E5K-KF1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8732A0Z-C01-G001-S0001+10.0.10586
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02RDQ.029.160707.JJ:bd07/07/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5K/300E5Q:pvrP02RDQ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5K-KF1BR:rvrSGL8732A0Z-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 300E5K/300E5Q
  dmi.product.version: P02RDQ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

2018-04-26 Thread Ads20000

I think the latter solution - keep the dark background but remove the
line - makes the most sense. Can this be SRU'd to 18.04 when done? I
think this is a significant enough design bug that an SRU should be
done? Regression potential would be, perhaps, that updates (the change
from the buggy UI to the new UI) don't produce the intended result
(though updates can easily be tested for).

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

2018-04-26 Thread Ads20000

Oh, except for a less dramatic deviation from the current design the
sidebar should have orange text and an undivided dark background, I
think, rather than an orange line, as in the most recent imgur. Probably
the lighter shade of gray should be used.

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()

2018-04-26 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1751252

** Tags added: iso-testing

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

Title:
  ubiquity crashed with signal 5 in _XEventsQueued()

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: * Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 * in g_strfreev() from g_themed_icon_finalize() from g

2018-04-26 Thread chris pollock

Happened again during software update. Hopefully this is fixed in
18.04LTS

Syslog output here - https://pastebin.com/yhW3ZSJP

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from
  g_themed_icon_finalize() from g_object_unref() from
  desktop_entry_unref()

Status in libgweather:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  
  [Impact] 
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
   __GI___libc_free (mem=) at malloc.c:2969
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Touch-packages] [Bug 1504387] Re: [regression] Software client windows appear all-black on wily desktop

2018-04-26 Thread Bug Watch Updater

** Changed in: mesa
   Status: Confirmed => Fix Released

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

Title:
  [regression] Software client windows appear all-black on wily desktop

Status in Mesa:
  Fix Released
Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  [regression] Software client windows appear all-black, as of today on
  wily desktop.

  Although Mir has not changed. It seems like some other part of the OS
  is broken.

  $ sudo mir_proving_server &
  $ sudo mir_demo_client_progressbar

  The bug appeared in:
  mesa (11.0.2-1ubuntu3) wily; urgency=medium

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

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

[Touch-packages] [Bug 1763822] Re: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

>From the log file:

Preparing to unpack .../python3-apt_1.6.0~rc2ubuntu2_amd64.deb ...
/var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: 
py3clean: not found
dpkg: warning: subprocess old pre-removal script returned error exit status 127
dpkg: trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
dpkg: error processing archive 
/var/cache/apt/archives/python3-apt_1.6.0~rc2ubuntu2_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 127

Does the file /usr/bin/py3clean exist on your system?

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package software-properties-common 0.96.24.28 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 127

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Package crash after log in

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.28
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.28 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763822/+subscriptions

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

[Touch-packages] [Bug 1767167] Re: package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

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

** This bug has been marked a duplicate of bug 1764858
   Can't update / install / delete packages due to missing libzstd.so.1

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

Title:
  package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control
  subprocess returned error exit status 127

Status in tar package in Ubuntu:
  New

Bug description:
  help us

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tar 1.29b-2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  AptOrdering:
   tar:amd64: Install
   tar:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 25 20:51:44 2018
  DpkgTerminalLog:
   dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
   dpkg: error processing archive /var/cache/apt/archives/tar_1.29b-2_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 127
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6~beta1
  SourcePackage: tar
  Title: package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control 
subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767164] Re: Apparmor removed on 16.04 LTS -> 18.04 upgrade

2018-04-26 Thread Arni Johannesson

Yes the omission of ubuntu-standard seems to be the leading candidate
for the cause of this issue. Thank you for investigating.

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

Title:
  Apparmor removed on 16.04 LTS -> 18.04 upgrade

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Apparmor is removed when upgrading a vanilla 16.04 system to 18.04

  This broke my LXD. The LXD team guided me here, per
  https://github.com/lxc/lxd/issues/4504

  Easily solved by re-installing apparmor

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

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

[Touch-packages] [Bug 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

>From the log file:

Preparing to unpack .../python3-apt_1.6.0~rc2ubuntu2_amd64.deb ...
/var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: 
py3clean: not found
dpkg: warning: subprocess old pre-removal script returned error exit status 127
dpkg: trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
dpkg: error processing archive 
/var/cache/apt/archives/python3-apt_1.6.0~rc2ubuntu2_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 127

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

Title:
  package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Problem occurred setting the displays arrangement

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.0~rc2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

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

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

[Touch-packages] [Bug 1767164] Re: Apparmor removed on 16.04 LTS -> 18.04 upgrade

2018-04-26 Thread Jamie Strandboge

I tried to reproduce this and was unable to. The apparmor package did
added a Breaks: media-hub, mediascanner2.0, messaging-app, webbrowser-
app because of bug #1756800 and bug #1761176 so I tried upgrades with
and without these installed. Test configurations:

* Ubuntu Desktop default install
 * update sources.list to include bionic and run apt-get update
  * apt-get upgrade correctly holds apparmor
  * apt-get dist-upgrade correctly upgrades apparmor
 * revert changes to sources.list and run apt-get update
  * do-release-upgrade -d correctly upgrades apparmor. Package
removal at end does not suggest removing apparmor. Reboot
shows apparmor is installed

* Ubuntu Desktop default install with media-hub, mediascanner2.0,
  messaging-app and webbrowser-app installed
 * update sources.list to include bionic and run apt-get update
  * apt-get upgrade correctly holds apparmor
  * apt-get dist-upgrade correctly upgrades apparmor and removes
media-hub, mediascanner2.0, messaging-app and webbrowser-app
 * revert changes to sources.list and run apt-get update
  * do-release-upgrade -d correctly upgrades apparmor and removes
media-hub, mediascanner2.0, messaging-app and webbrowser-app.
Package removal at end does not suggest removing apparmor.
Reboot shows apparmor is installed

* Ubuntu Server default install
 * update sources.list to include bionic and run apt-get update
  * apt-get upgrade correctly upgrades apparmor (no Breaks
installed so no reason to hold)
  * apt-get dist-upgrade correctly upgrades apparmor
 * revert changes to sources.list and run apt-get update
  * do-release-upgrade -d correctly upgrades apparmor. Package
removal at end does not suggest removing apparmor. Reboot
shows apparmor is installed

* Ubuntu Server default install with media-hub installed
 * update sources.list to include bionic and run apt-get update
  * apt-get upgrade correctly holds apparmor
  * apt-get dist-upgrade correctly upgrades apparmor and removes
media-hub
 * revert changes to sources.list and run apt-get update
  * do-release-upgrade -d correctly upgrades apparmor and removes
media-hub. Package removal at end does not suggest removing
apparmor. Reboot shows apparmor is installed

I believe that the apparmor removal has nothing to do with the new added
Breaks in 18.04's apparmor, however, as mentioned, I cannot reproduce.

Can you provide steps to reproduce?

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

** Bug watch added: LXD bug tracker #4504
   https://github.com/lxc/lxd/issues/4504

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

Title:
  Apparmor removed on 16.04 LTS -> 18.04 upgrade

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Apparmor is removed when upgrading a vanilla 16.04 system to 18.04

  This broke my LXD. The LXD team guided me here, per
  https://github.com/lxc/lxd/issues/4504

  Easily solved by re-installing apparmor

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

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

[Touch-packages] [Bug 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

Does the file /usr/bin/py3clean exist on your system?

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Problem occurred setting the displays arrangement

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.0~rc2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

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

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

[Touch-packages] [Bug 1767164] Re: Apparmor removed on 16.04 LTS -> 18.04 upgrade

2018-04-26 Thread Jamie Strandboge

Looking at
https://github.com/lxc/lxd/issues/4504#issuecomment-384759354, it seems
that the system may not have had ubuntu-standard installed, so on do-
release-upgrade the final package removal step may have listed apparmor.

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

Title:
  Apparmor removed on 16.04 LTS -> 18.04 upgrade

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Apparmor is removed when upgrading a vanilla 16.04 system to 18.04

  This broke my LXD. The LXD team guided me here, per
  https://github.com/lxc/lxd/issues/4504

  Easily solved by re-installing apparmor

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

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

[Touch-packages] [Bug 1765479] Re: In ubuntu 18.04, when I unplug the screen cable, the user session close's

2018-04-26 Thread مالك ب

Hello
Today when I have removed the screen cable from the main unit and plug it again 
after few moments, the session did not closes and all running programs stay 
running. I did it again another time, the same thing happened: all the programs 
stayed running. It seems that the updates of theses few last days solved the 
problem.
Thanks for all ubuntu developers for the great job they are doing.

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

Title:
  In ubuntu 18.04,when I unplug the screen cable, the user session
  close's

Status in xorg package in Ubuntu:
  New

Bug description:
  I have submitted the first rapport yesterday, at the following link:
  https://bugs.launchpad.net/ubuntu/+bug/1765160
  And after the first reply from
  Ubuntu Foundations Team Bug Bot (crichton)
  I go to the page provided in this automated reply:
  https://wiki.ubuntu.com/Bugs/FindRightPackage
  and from this page I go to the following pages and I apply the step that 
match this case.
  https://wiki.ubuntu.com/X/Backtracing
  https://wiki.ubuntu.com/Apport
  https://wiki.ubuntu.com/Apport/DeveloperHowTo
  https://help.ubuntu.com/community/ReportingBugs
  https://help.ubuntu.com/community/DebuggingSystemCrash
   After I read the step described in these pages
  I run the following command in konsole (as root)
  ubuntu-bug xorg
  I click on submit, and then it take me to this page.
  In the description I have done yesterday, i wrote:
  "Hello.
  If I unplug the cable of the screen when I am logged to my user session in 
ubuntu 18.04, and then I plug again the cable of the screen, I found my session 
closed, and when I login again to my user session, I found all previous running 
programs closed.
  This bug reproduce every time I unplug the cable screen from the unit.
  what I expect: when I plug the screen cable to the unit, I must find my 
session open as I let it, and programs that were running still open or running
  What happened: after I plug the cable screen to the unit, i find my session 
and all programs closed, and when I login again to my account session, I find 
all previous programs closed.
  Distro: Ubuntu Bionic Beaver (development branch)
  CPU: Intel® Pentium(R) CPU G645 @ 2.90GHz × 2
  Graphic: Intel® Sandybridge Desktop
  Gnome: 3.28.1
  OS type: 64 bit
  If there is any other information needed to help solving this bug that i must 
submit, just let me know it."
  And today, I have included
  _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, 
text/plain)
  And I submit it again now
  Please tell me were I must continue with this bug, at this page or the 
previous (https://bugs.launchpad.net/ubuntu/+bug/1765160) or both of them, or 
it will be merged automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Apr 19 11:08:03 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
  InstallationDate: Installed on 2018-03-18 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=ar_DZ:ar
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ar_DZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=18c8c08f-eab6-491b-b3aa-b8b9a415e1f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: H61M-HVS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd09/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

2018-04-26 Thread Gustav Ekner

Two more solutions:

* Make the background the same but keep a line between: 
https://i.imgur.com/ilhA6Zr.png
* Make the background the same and remove the line: 
https://i.imgur.com/qS0ODeq.png

(I based the images of Marco Trevisan's, hope that's OK :-) )

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1447715] Update Released

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

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Released
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Original test case, before dhclient was fixed:
  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 
dhcp) and reboot. It will fail to get a dhcp address during boot.

  New test case, showing failure when using dhclient in 'stateless' mode:
  Configure ifupdown like:

  auto eth0
  iface eth0 inet6 auto
    dhcp 1

  When eth0 is down, run 'sudo ifup eth0', and it will fail as dhclient
  fails to start on the interface.

  [Regression Potential]

  As this modifies the wait-for-dad function, its potential for
  regression is to introduce failures in starting dhclient, possibly by
  failing to wait for DAD to complete or due to some other failure in
  the wait for dad function.

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

This bug was fixed in the package ifupdown - 0.8.10ubuntu1.3

---
ifupdown (0.8.10ubuntu1.3) xenial; urgency=medium

  [ Wido den Hollander ]
  * Wait properly for Link-Local Address to go through DAD.
(LP: #1447715)

 -- Dan Streetman   Tue, 17 Apr 2018 17:29:54
-0400

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

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Released
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Original test case, before dhclient was fixed:
  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 
dhcp) and reboot. It will fail to get a dhcp address during boot.

  New test case, showing failure when using dhclient in 'stateless' mode:
  Configure ifupdown like:

  auto eth0
  iface eth0 inet6 auto
    dhcp 1

  When eth0 is down, run 'sudo ifup eth0', and it will fail as dhclient
  fails to start on the interface.

  [Regression Potential]

  As this modifies the wait-for-dad function, its potential for
  regression is to introduce failures in starting dhclient, possibly by
  failing to wait for DAD to complete or due to some other failure in
  the wait for dad function.

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

2018-04-26 Thread florin

That is true, it should be the same color for icon and label as they are
one item.

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

Title:
  Nautilus sidebar theming is confusing

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

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

2018-04-26 Thread Dan Streetman

@newsuk-platform, are you still having this problem?  If not, let's
close this bug.

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

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

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1765646] Re: Ubuntu 16.04 - issue with bsdtar package installation

2018-04-26 Thread Tomas Lipensky

Thank you very much Hans Joachim. I wasn't aware that I'm missing
updates, because i was receiving some. Have a great weekend.

** Changed in: libarchive (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubuntu 16.04 - issue with bsdtar package installation

Status in libarchive package in Ubuntu:
  Invalid

Bug description:
  apt install bsdtar fails with dependency issue on 16.04:

  
  root@czz17163-laptop:~/scripts# apt-get install bsdtar
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   bsdtar : Depends: libarchive13 (= 3.1.2-11build1) but 
3.1.2-11ubuntu0.16.04.3 is to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Solution:

  Include in repository the bsdtar package from 
https://packages.ubuntu.com/xenial/amd64/bsdtar/download
  (wget 
http://security.ubuntu.com/ubuntu/pool/universe/liba/libarchive/bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb
 )
  which works with libarchive13 in version 3.1.2-11ubuntu0.16.04.3 which is 
included in U16.04

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

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

[Touch-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist

2018-04-26 Thread Kees Cook

https://github.com/systemd/systemd/pull/8830

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

Title:
  Regression: /etc/modules checked against blacklist

Status in systemd package in Ubuntu:
  New

Bug description:
  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
local module args
module="$1"
args="$2"

if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
else
  modprobe $module $args > /dev/null 2>&1 || true
fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

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

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

[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages

Thanks for your bug report. Unfortunately, the log files show that your
install did not complete - it failed to install the bootloader; probably
due to being booted in EFI mode and installing to a disk that is missing
an ESP partition.

To solve the issue, reinstall from the final 18.04 image (once
available), and make sure the bootloader installed correctly. For
further help, see https://www.ubuntu.com/support/community-support.

** Summary changed:

- Can't update / install / delete packages
+ Can't update / install / delete packages due to missing libzstd.so.1

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

Title:
  Can't update / install / delete packages due to missing libzstd.so.1

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

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

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

[Touch-packages] [Bug 1765803] Re: package installs fail due to missling libzstd.so.1

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

** This bug has been marked a duplicate of bug 1764858
   Can't update / install / delete packages

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

Title:
  package installs fail due to missling libzstd.so.1

Status in perl package in Ubuntu:
  Incomplete

Bug description:
  cant install upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: perl 5.26.1-5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 20 23:21:18 2018
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6~beta1
  SourcePackage: perl
  Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control 
subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Can't update / install / delete packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

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

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

[Touch-packages] [Bug 1766794] Re: apport-collect with debian-installer doesn't create a ProblemType in the report

2018-04-26 Thread John George

hmm, the bug I was trying to report on has now been fixed and I've re-installed 
that test system.
Without the crash from the original bug I don't get a report just 'No pending 
crash reports'.

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

Title:
  apport-collect with debian-installer doesn't create a ProblemType in
  the report

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

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

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

[Touch-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist

** Tags added: regression-release

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

Title:
  Regression: /etc/modules checked against blacklist

Status in systemd package in Ubuntu:
  New

Bug description:
  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
local module args
module="$1"
args="$2"

if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
else
  modprobe $module $args > /dev/null 2>&1 || true
fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

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

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

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

The code of openssl does not need changing a new version of the package
has been uploaded to the archive for Ubuntu 18.04.

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Bionic:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in ca-certificates package in Debian:
  New

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1767172] [NEW] Regression: /etc/modules checked against blacklist

2018-04-26 Thread Kees Cook

Public bug reported:

Before systemd-modules-load, /etc/init.d/kmod would load modules
directly with "modprobe" (and _not_ "modprobe -b"):

load_module() {
  local module args
  module="$1"
  args="$2"

  if [ "$VERBOSE" != no ]; then
log_action_msg "Loading kernel module $module"
modprobe $module $args || true
  else
modprobe $module $args > /dev/null 2>&1 || true
  fi
}

However, under 18.04, systemd-modules-load will _ignore_ modules that
are manually listed in /etc/modules and process them with the blacklist
(the same as "modprobe -b" would). This means that it is not possible to
manually load modules that are blacklisted (like watchdog modules):

systemd-238/src/modules-load/modules-load.c:

static int load_module(struct kmod_ctx *ctx, const char *m) {
const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
...
default:
err = kmod_module_probe_insert_module(mod, probe_flags,
  NULL, NULL, NULL, 
NULL);

if (err == 0)
log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
else if (err == KMOD_PROBE_APPLY_BLACKLIST)
log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

Blacklists should _not_ be applied by systemd-modules-load.

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


** Tags: regression-release

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

Title:
  Regression: /etc/modules checked against blacklist

Status in systemd package in Ubuntu:
  New

Bug description:
  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
local module args
module="$1"
args="$2"

if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
else
  modprobe $module $args > /dev/null 2>&1 || true
fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

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

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

[Touch-packages] [Bug 1763822] Re: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  package software-properties-common 0.96.24.28 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 127

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Package crash after log in

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.28
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.28 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763822/+subscriptions

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

[Touch-packages] [Bug 1767167] [NEW] package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

2018-04-26 Thread Shubham Eknath Ekade

Public bug reported:

help us

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tar 1.29b-2
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
AptOrdering:
 tar:amd64: Install
 tar:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Apr 25 20:51:44 2018
DpkgTerminalLog:
 dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
 dpkg: error processing archive /var/cache/apt/archives/tar_1.29b-2_amd64.deb 
(--unpack):
  dpkg-deb --control subprocess returned error exit status 127
ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6~beta1
SourcePackage: tar
Title: package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control 
subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control
  subprocess returned error exit status 127

Status in tar package in Ubuntu:
  New

Bug description:
  help us

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tar 1.29b-2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  AptOrdering:
   tar:amd64: Install
   tar:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 25 20:51:44 2018
  DpkgTerminalLog:
   dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
   dpkg: error processing archive /var/cache/apt/archives/tar_1.29b-2_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 127
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6~beta1
  SourcePackage: tar
  Title: package tar 1.29b-2 failed to install/upgrade: dpkg-deb --control 
subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

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

** Changed in: python-apt (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Problem occurred setting the displays arrangement

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.0~rc2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

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

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

[Touch-packages] [Bug 1767164] [NEW] Apparmor removed on 16.04 LTS -> 18.04 upgrade

2018-04-26 Thread Arni Johannesson

Public bug reported:

Apparmor is removed when upgrading a vanilla 16.04 system to 18.04

This broke my LXD. The LXD team guided me here, per
https://github.com/lxc/lxd/issues/4504

Easily solved by re-installing apparmor

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

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

Title:
  Apparmor removed on 16.04 LTS -> 18.04 upgrade

Status in apparmor package in Ubuntu:
  New

Bug description:
  Apparmor is removed when upgrading a vanilla 16.04 system to 18.04

  This broke my LXD. The LXD team guided me here, per
  https://github.com/lxc/lxd/issues/4504

  Easily solved by re-installing apparmor

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

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

[Touch-packages] [Bug 1767159] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

** Tags removed: need-duplicate-check

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  while upgrade from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 19:04:38 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-17 (678 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1767159/+subscriptions

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

[Touch-packages] [Bug 1767159] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2018-04-26 Thread _Uwe_

Public bug reported:

while upgrade from 16.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: hicolor-icon-theme 0.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Apr 26 19:04:38 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-06-17 (678 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  while upgrade from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 19:04:38 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-17 (678 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1767159/+subscriptions

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

[Touch-packages] [Bug 1767095] Re: intel vga

2018-04-26 Thread Emily Ratliff

** Information type changed from Private Security to Public

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

Title:
  intel vga

Status in xorg package in Ubuntu:
  New

Bug description:
  intel vga 
  00:02.0 vga compatible controller: intel corporation haswell-ult integrated 
graphics controller (rev 0b)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 26 10:49:19 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.13.0-38-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2212]
 Subsystem: Hewlett-Packard Company GF117M [GeForce 610M/710M/810M/820M / 
GT 620M/625M/630M/720M] [103c:2212]
  InstallationDate: Installed on 2018-04-18 (7 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=d91e6cc6-a7c9-46f9-8754-9fe5402454f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Apr 26 09:46:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

2018-04-26 Thread Dan Streetman

> Unfortunately it turns out this change does not fix the issue of interfaces 
> not
> coming up correctly for a bond with a (static) network configuration

Please keep in mind this bug is *specifically* about the regression
caused by the change from bug 1573272, as described in this bug
description.  My test criteria for the patches for this bug are listed
in comment 17 and comment 18.  This bug is *not* about any issue that
has never worked.  If your configuration worked using (assuming Xenial)
vlan version 1.9-3.2ubuntu1.16.04.1, but does not work now, then please
let me know the details; however if your config doesn't work with
(assuming Xenial) vlan version 1.9-3.2ubuntu1.16.04.1 then it's
unrelated to this bug and you should open a new bug (or un-dup bug
1759573, if appropriate).

> Executing "ifdown -a; ifup -a" shows that ifupdown tries to bring up
the bond BEFORE the slaves

what's your EXACT e/n/i configuration.  single file or multiple files?
ifup -a brings them up in order that they are listed in e/n/i

> bonds relying on slaves having "bond-master"...

this is nothing new and has nothing to do with this bug.  If this is an
issue for you, please open a new bug.  I agree with you in principle
that this should be better, but that's no guarantee it will actually get
fixed.

> bringing a specific interface up automatically brings up it's child
vlans...

this also is nothing new.  this is how things have worked for a long
time, and it has nothing to do with this bug.  If this is a problem for
you, please open a new bug and discuss there.  Note I do not think this
will change without some significant justification (provided in a new
bug, not here please) for why it's a problem.

> a vlan running on top of a bond cannot be brought up directly...

also...nothing new.  unrelated to this bug.  please open a new bug if
this is a problem for you.  Also, doubt this will change without
specific justification (not provided here, please) for why this is a
problem.

I can understand your frustration with the delicate nature of ifupdown;
its configuration is more 'delicate' than most users would like, and
calling ifup directly for specific interfaces doesn't always work the
way you would like, for more complicated configurations.  However, it's
been like this, and for the most part you just have to learn its
limitations and live with them.  Opening bugs for ifupdown limitations
is fine, but some things just won't be changed.

In the future, netplan and/or systemd-networkd take over interface
configuration, and I think you may find them much more reliable and
robust, although maybe more complicated to configure and/or less
"flexible" than ifupdown in some ways.

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  In Progress
Status in ifupdown source package in Trusty:
  In Progress
Status in vlan source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress
Status in vlan source package in Xenial:
  In Progress
Status in ifupdown source package in Artful:
  In Progress
Status in vlan source package in Artful:
  In Progress
Status in ifupdown source package in Bionic:
  In Progress
Status in vlan source package in Bionic:
  In Progress
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
└─run-parts,1501 /etc/network/if-pre-up.d
└─bridge,1502 /etc/network/if-pre-up.d/bridge
└─bridge,1508 /etc/network/if-pre-up.d/bridge
└─vlan,1511 /etc/network/if-pre-up.d/vlan
└─ifup,1532 eth0

  
  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
address 192.168.10.65
netmask 255.255.255.192
gateway 192.168.10.66

  auto eth0.11
address 192.168.11.1
netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
bridge_ports eth0.1134
bridge_stp off
bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

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

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

[Touch-packages] [Bug 1767143] Re: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ifupdown package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16
  Uname: Linux 4.13.0-39-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 17:27:57 2018
  DuplicateSignature:
   package:ifupdown:0.8.10ubuntu1.3
   Setting up ubuntu-make (17.03~xenial1) ...
   /var/lib/dpkg/info/ubuntu-make.postinst: 6: 
/var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found
   dpkg: error processing package ubuntu-make (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-01 (24 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767143] [NEW] package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-26 Thread Govorov Artem

Public bug reported:

error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.8.10ubuntu1.3
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16
Uname: Linux 4.13.0-39-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Apr 26 17:27:57 2018
DuplicateSignature:
 package:ifupdown:0.8.10ubuntu1.3
 Setting up ubuntu-make (17.03~xenial1) ...
 /var/lib/dpkg/info/ubuntu-make.postinst: 6: 
/var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found
 dpkg: error processing package ubuntu-make (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-04-01 (24 days ago)
InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: ifupdown
Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed third-party-packages xenial

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

Title:
  package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ifupdown package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16
  Uname: Linux 4.13.0-39-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 17:27:57 2018
  DuplicateSignature:
   package:ifupdown:0.8.10ubuntu1.3
   Setting up ubuntu-make (17.03~xenial1) ...
   /var/lib/dpkg/info/ubuntu-make.postinst: 6: 
/var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found
   dpkg: error processing package ubuntu-make (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-01 (24 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731879] Re: remove readline6 from the archive

2018-04-26 Thread Bryan Quigley

Both readline6 and bareos were removed at some point in the 18.04 cycle.
Checked LP/packages and tried an install.

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

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

Title:
  remove readline6 from the archive

Status in readline6 package in Ubuntu:
  Fix Released

Bug description:
  remove readline6 from the archive, replaced by readline.

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

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

[Touch-packages] [Bug 1766939] Re: dnsmasq won't start [Ubuntu 18.04]

2018-04-26 Thread Nataraj

I have resolved the issue of dnsmasq not starting.  The cause was that
virbr0 was listed in /etc/network/interface. Removing it solved the
problem. This was my error since I had put it there while trying to
configure virbr0 without dnsmasq (which I have now done sucessfully).

I still consider it a bug that there is no obvious way to edit the
configuration file for dnsmasq when it is started by libvirtd and would
still be interested in an answer to that question as well as better
documentation for the libvirtd/dnsmasq configuration.

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

Title:
  dnsmasq won't start [Ubuntu 18.04]

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  
  System: Ubuntu 18.04 All updates: Current
  Could also be a libvirt problem.

  When libvirtd tries to start dnsmasq, I get the following error and dnsmasq 
fails to start:
  libvirtd[2125]: 2018-04-24 20:38:47.073+: 2178: error : 
virNetDevIPAddrAdd:223 : Failed to add IP address 1
  error: Failed to add IP address 10.1.2.1/24 bcast 10.1.2.255 to virbr0

  This was previously working. If I edit
  /etc/libvirt/qemu/networks/default.xml and change the name of the
  interface to virbr1 dnsmasq starts up correctly, change the name back
  to virbr0 and it fails. Tried a find on the filesystem of '*virbr*' to
  see if there were any files left that shouldn't be there, but found
  only a couple of flag files (don't remember the name), 1 under
  /var/run and the other I think was in /var/lib/libvirt/dnsmasq.
  Deleted those but stll doesn't work. I have also shutdown any other
  services that were binding to the virbr0 interface while testing this.

  How can I edit /var/lib/libvirt/dnsmasq/default.conf, or in some other
  way pass my own config parameters to dnsmasq? Instructions inside the
  file say to use "virsh net-edit default", but that edits
  /etc/libvirt/qemu/networks/default.xml which is a different file? If I
  edit default.conf with a normal editor, it gets overwritten by
  libvirtd.

  It appears that the dnsmasq config file is generated automaticlly by
  libvirtd and then dnsmasq is started by libvirtd, so I can't see
  anywhere to put my own config options, short of rebuilding libvirtd
  from source. According to the man page adding the option 'port=0' to
  the dnsmasq configuration will disable dns so that dnsmasq will no
  longer listen on port 53. This is what I would like to do.

  It would be nice to know how to create the virtual NIC needed to route 
traffic from the VM's onto my network. Don't want to bridge onto LAN interface, 
because system is connected to multiple vlans and wireless when traveling.
  I can handle DNS and DHCP using bind9 and isc-dhcp-server and would prefer to 
run 1 instance of these servers for both the host and all guest VM's. Seems to 
defeat the purpose of a cache to run a seperate caching dns server for the host 
and for the VM's, and then another if you have multiple virtual network 
interfaces for different VM's. If I could do this easily, then I wouldn't need 
dnsmasq at all.

  Thank You
  Natu

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

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

[Touch-packages] [Bug 1767113] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

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

I tried to reboot:

 shemgp  shemgp-x230t  ~  ERROR  $  sudo dpkg --configure -a
[sudo] password for shemgp: 
Sorry, try again.
[sudo] password for shemgp: 
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
rehash: skipping duplicate certificate in shemgp-nas.crt
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 ca-certificates
 shemgp  shemgp-x230t  ~  ERROR  $  sudo dpkg -i 
/var/cache/apt/archives/ca-certificates_20170717~16.04.1_all.deb 
dpkg: warning: downgrading ca-certificates from 20180409 to 20170717~16.04.1
(Reading database ... 763802 files and directories currently installed.)
Preparing to unpack .../ca-certificates_20170717~16.04.1_all.deb ...
Unpacking ca-certificates (20170717~16.04.1) over (20180409) ...
Setting up ca-certificates (20170717~16.04.1) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for ca-certificates (20170717~16.04.1) ...
Updating certificates in /etc/ssl/certs...
WARNING: Skipping duplicate certificate UbuntuOne-Go_Daddy_Class_2_CA.pem
WARNING: Skipping duplicate certificate UbuntuOne-Go_Daddy_Class_2_CA.pem
WARNING: Skipping duplicate certificate shemgp-nas.pem
WARNING: Skipping duplicate certificate shemgp-nas.pem
2 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

Replacing debian:redmine.pem
Replacing debian:redmine.pem
done.
Updating Mono key store
Linux Cert Store Sync - version 4.6.2.0
Synchronize local certs with certs from local Linux trust store.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD 
licensed.

I already trust 130, your new list has 130
Import process completed.
Done
done.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1767113] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

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

Downgraded libssl1.1 and still has the error:

 shemgp  shemgp-x230t  ~  USAGE  $  apt-cache show libssl1.1
Package: libssl1.1
Architecture: amd64
Version: 1.1.0g-2ubuntu4
Multi-Arch: same
Priority: important
Section: libs
Source: openssl
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian OpenSSL Team 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3411
Depends: libc6 (>= 2.14), debconf (>= 0.5) | debconf-2.0
Breaks: salt-common (<= 2016.3.3+ds-3)
Filename: pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb
Size: 1128092
MD5sum: b2d83d966881fd0893a5394c19836a3f
SHA1: 93e1abb69a44a961ded04834b236d069d1fe6ac4
SHA256: 82e424d50e144320319414a1964d3a980abde4bc39fc7d8c2885819328cb5cb4
Homepage: https://www.openssl.org/
Description-en: Secure Sockets Layer toolkit - shared libraries
 This package is part of the OpenSSL project's implementation of the SSL
 and TLS cryptographic protocols for secure communication over the
 Internet.
 .
 It provides the libssl and libcrypto shared libraries.
Description-md5: 88547c6206c7fbc4fcc7d09ce100d210
Task: minimal
Supported: 5y

 shemgp  shemgp-x230t  ~  $  sudo dpkg --configure -a
[sudo] password for shemgp: 
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
rehash: skipping duplicate certificate in shemgp-nas.crt
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 ca-certificates
 shemgp  shemgp-x230t  ~  ERROR  $ 

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1767113] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

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

 shemgp  shemgp-x230t  ~  USAGE  $  apt-cache show libssl1.1
Package: libssl1.1
Architecture: amd64
Version: 1.1.0g-2ubuntu4
Multi-Arch: same
Priority: important
Section: libs
Source: openssl
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian OpenSSL Team 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3411
Depends: libc6 (>= 2.14), debconf (>= 0.5) | debconf-2.0
Breaks: salt-common (<= 2016.3.3+ds-3)
Filename: pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb
Size: 1128092
MD5sum: b2d83d966881fd0893a5394c19836a3f
SHA1: 93e1abb69a44a961ded04834b236d069d1fe6ac4
SHA256: 82e424d50e144320319414a1964d3a980abde4bc39fc7d8c2885819328cb5cb4
Homepage: https://www.openssl.org/
Description-en: Secure Sockets Layer toolkit - shared libraries
 This package is part of the OpenSSL project's implementation of the SSL
 and TLS cryptographic protocols for secure communication over the
 Internet.
 .
 It provides the libssl and libcrypto shared libraries.
Description-md5: 88547c6206c7fbc4fcc7d09ce100d210
Task: minimal
Supported: 5y

 shemgp  shemgp-x230t  ~  $  sudo dpkg --configure -a
[sudo] password for shemgp: 
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
rehash: skipping duplicate certificate in shemgp-nas.crt
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 ca-certificates
 shemgp  shemgp-x230t  ~  ERROR  $ 

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop

2018-04-26 Thread Kai-Heng Feng

Should be good.

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

Title:
  The wifi will be disconnected and the only thing I can do is to reboot
  the laptop

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it is true that this should be a bug related with network 
(wifi connection).
  Here is the issue:
  Every time after I login into the account, about 20 minutes later, the wifi 
will be disconnected automatically. I even cannot reconnect the wifi manually, 
the only thing that I can do is to reboot the laptop. After login again, wifi 
can be connected (but through manual way).
  By the way, during the period of wifi disconnection, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually. 
But I found that there is only one SSID which previously the laptop connected 
to. However, I was definitely sure that there should be more than one SSID 
being showed in the wifi list. Even for this only one SSID, like I mentioned 
before, I cannot reconnect manually unless I reboot the system.
  Finally, I set the wifi to be connected automatically after I login to the 
system, however, it just can't. I can only connect to the wifi manually after I 
login to the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 19:02:12 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-15 (68 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
   172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
WolfieNet-Secure  eb45c742-ba31-4f31-acf2-13a2768bcc29  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp5s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
   ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  disabled
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin  1217 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-15 (70 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.148 metric 
600
  MachineType: Lenovo F31
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  NonfreeKernelModules: nvidia
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=02a1b417-5beb-4eae-82cb-e3063372bf6d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

2018-04-26 Thread Tom Verdaat

We've been doing a lot more testing and debugging and I'd like to share
our findings:

1) Unfortunately it turns out this change does not fix the issue of interfaces 
not coming up correctly for a bond with a (static) network configuration. The 
race condition seems to be removed so at least there are no more hangs between 
bonds and their vlan children. All the interfaces also say they are UP both 
when running ifup and after reboot. However:
- Running "ifup " does bring up the bond (and its vlans) in a 
working state.
- Running "ifup -a" or rebooting don't actually work, causing "network not 
available" errors and "Destination Host Unreachable" when pinging other 
machines. Executing "ifdown -a; ifup -a" shows that ifupdown tries to bring up 
the bond BEFORE the slaves in stead of the other way around. Even though after 
the 60s timeout the bond and it's slaves say they are UP, they don't actually 
function.
- We're not seeing any issues with bonds that do not have a network 
configuration of their own

2) The networking script stack / concept seems fundamentally flawed in
three areas:

2.A) bonds relying on slaves having "bond-master" and being started by
bringing up the slaves, but not supporting the master having "bond-
slaves" and being able to start a bond by just bringing up the bond
directly.

2.B) bringing a specific interface up automatically brings up it's child
vlans. This does not make a lot of sense. The other way around does -
e.g. in order to bring up a vlan we need to bring up it's raw device -
but why would the ifupdown scripts assume that I want to bring up all of
it's vlans when I bring up an interface that (also) serves as a raw
device? In that case I would probably run "ifup -a"!

2.C) a vlan running on top of a bond cannot be brought up directly due to 
/sys/class/net// not existing. This results in the following:
>  # ifup bo-adm.2
>  Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
>  cat: /sys/class/net/bo-adm/mtu: No such file or directory
>  Device "bo-adm" does not exist.
>  bo-adm does not exist, unable to create bo-adm.2
>  run-parts: /etc/network/if-pre-up.d/vlan exited with return code 1
>  Failed to bring up bo-adm.2.

3) Our new workaround for boot has become this very intrusive systemd service:
> [Unit]
> Wants=network-online.target
> After=network-online.target
> 
> [Install]
> WantedBy=multi-user.target
> 
> [Service]
> Type=oneshot
> ExecStartPre=/sbin/ifdown bo-adm
> ExecStart=/sbin/ifup enp0s3
> ExecStart=/sbin/ifup enp0s10
> ExecStop=/sbin/ifdown bo-adm
> RemainAfterExit=yes
> TimeoutStartSec=5min

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  In Progress
Status in ifupdown source package in Trusty:
  In Progress
Status in vlan source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress
Status in vlan source package in Xenial:
  In Progress
Status in ifupdown source package in Artful:
  In Progress
Status in vlan source package in Artful:
  In Progress
Status in ifupdown source package in Bionic:
  In Progress
Status in vlan source package in Bionic:
  In Progress
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
└─run-parts,1501 /etc/network/if-pre-up.d
└─bridge,1502 /etc/network/if-pre-up.d/bridge
└─bridge,1508 /etc/network/if-pre-up.d/bridge
└─vlan,1511 /etc/network/if-pre-up.d/vlan
└─ifup,1532 eth0

  
  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
address 192.168.10.65
netmask 255.255.255.192
gateway 192.168.10.66

  auto eth0.11
address 192.168.11.1
netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
bridge_ports eth0.1134
bridge_stp off
bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

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

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

[Touch-packages] [Bug 1767124] [NEW] bluetoothd crashed with SIGILL

2018-04-26 Thread Bearsh

Public bug reported:

systemctl status bluetooth.service 
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 2min 
25s ago
 Docs: man:bluetoothd(8)
  Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
 Main PID: 1458 (code=dumped, signal=ILL)
   Status: "Running"

Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed state.
Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated too 
quickly.
Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

sudo gdb /usr/lib/bluetooth/bluetoothd
...
Program received signal SIGILL, Illegal instruction.
agent_get (owner=owner@entry=0x0) at src/agent.c:267
267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
#1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
#2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
#3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
#4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
#5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
#6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: 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/1767124

Title:
  bluetoothd crashed with SIGILL

Status in bluez package in Ubuntu:
  New

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from

[Touch-packages] [Bug 1767113] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

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

You have a version of libssl and openssl from a PPA.

libssl1.1 1.1.0g-2.1+ubuntu17.10.1+deb.sury.org+1 [origin: unknown]

That's gonna have a bug in it that the official version will not.

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop

2018-04-26 Thread Zhenqing Hu

OK, @Kai-Heng Feng, thank you for suggestions! I will have a try, and
report the result after about one week, do you think it is OK?

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

Title:
  The wifi will be disconnected and the only thing I can do is to reboot
  the laptop

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it is true that this should be a bug related with network 
(wifi connection).
  Here is the issue:
  Every time after I login into the account, about 20 minutes later, the wifi 
will be disconnected automatically. I even cannot reconnect the wifi manually, 
the only thing that I can do is to reboot the laptop. After login again, wifi 
can be connected (but through manual way).
  By the way, during the period of wifi disconnection, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually. 
But I found that there is only one SSID which previously the laptop connected 
to. However, I was definitely sure that there should be more than one SSID 
being showed in the wifi list. Even for this only one SSID, like I mentioned 
before, I cannot reconnect manually unless I reboot the system.
  Finally, I set the wifi to be connected automatically after I login to the 
system, however, it just can't. I can only connect to the wifi manually after I 
login to the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 19:02:12 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-15 (68 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
   172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
WolfieNet-Secure  eb45c742-ba31-4f31-acf2-13a2768bcc29  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp5s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
   ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  disabled
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin  1217 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-15 (70 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.148 metric 
600
  MachineType: Lenovo F31
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  NonfreeKernelModules: nvidia
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=02a1b417-5beb-4eae-82cb-e3063372bf6d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic package-from-proposed
  Uname:

[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

2018-04-26 Thread Wladimir Mutel

Why not fix this bug in Ubuntu Bionic where it still happens ?

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions

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

[Touch-packages] [Bug 1766628] Re: apparmor denies VLC to open files in devmode

2018-04-26 Thread Konstantin Pavlov

The same happens on Ubuntu 16.04.

thresh@thresh-VirtualBox:~$ cat /proc/version
Linux version 4.13.0-36-generic (buildd@lgw01-amd64-033) (gcc version 5.4.0 
20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #40~16.04.1-Ubuntu SMP Fri Feb 16 
23:25:58 UTC 2018
thresh@thresh-VirtualBox:~$ dpkg -l | grep -i snap
ii  libsnapd-glib1:amd64   1.13-0ubuntu0.16.04.1
amd64GLib snapd library
ii  snapd  2.29.4.2 
amd64Daemon and tooling that enable snap packages
ii  snapd-login-service1.13-0ubuntu0.16.04.1
amd64Daemon to allow non-root access to snapd
ii  ubuntu-core-launcher   2.29.4.2 
amd64Transitional package for snapd
thresh@thresh-VirtualBox:~$ snap version
snap2.32.5
snapd   2.32.5
series  16
ubuntu  16.04
kernel  4.13.0-36-generic
thresh@thresh-VirtualBox:~$ snap info vlc --verbose
name:  vlc
summary:   The ultimate media player
publisher: videolan
contact:   https://www.videolan.org/support/
license:   unknown
description: |
  VLC is the VideoLAN project's media player.
  
  Completely open source and privacy-friendly, it plays every multimedia file 
and streams.
  
  It notably plays MKV, MP4, MPEG, MPEG-2, MPEG-4, DivX, MOV, WMV, QuickTime, 
WebM, FLAC, MP3,
  Ogg/Vorbis files, BluRays, DVDs, VCDs, podcasts, and multimedia streams from 
various network sources.
  It supports subtitles, closed captions and is translated in numerous 
languages.
commands:
  - vlc
notes:   
  private:   false
  confinement:   strict
  devmode:   false
  jailmode:  false
  trymode:   false
  enabled:   true
  broken:false
  ignore-validation: false
snap-id:   RT9mcUhVsRYrDLG8qnvGiy26NKvv6Qkd
tracking:  beta
refreshed: 2018-04-26T09:09:49+03:00
installed:   3.0.2-11-g7c1d21a   (293) 192MB 
channels:  
  stable:3.0.1-4-g14a4897(190) 189MB -
  candidate: 3.0.2   (277) 192MB -
  beta:  3.0.2-11-g7c1d21a   (293) 192MB -
  edge:  4.0.0-dev-2536-g79afb97 (292) 197MB -
thresh@thresh-VirtualBox:~$ dpkg -l | grep -i appa
ii  apparmor   2.10.95-0ubuntu2.8   
amd64user-space parser utility for AppArmor
ii  libapparmor-perl   2.10.95-0ubuntu2.8   
amd64AppArmor library Perl bindings
ii  libapparmor1:amd64 2.10.95-0ubuntu2.8   
amd64changehat AppArmor library
thresh@thresh-VirtualBox:~$ 


** Attachment added: "Ubuntu 16.04 dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1766628/+attachment/5127649/+files/ubuntu-1604-denials.txt

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

Title:
  apparmor denies VLC to open files in devmode

Status in apparmor package in Ubuntu:
  New

Bug description:
  I see failures in VLC trying to open files and prefs while VLC snap
  seemingly uses devmode since this is on Debian "testing".

  Failures:
  ^[[1;3CApr 24 17:50:24 coal kernel: [ 7997.906298] audit: type=1400 
audit(1524581424.694:1944): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:24 coal kernel: [ 7997.906308] audit: type=1400 
audit(1524581424.694:1945): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" 
pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:24 coal kernel: [ 7997.912113] audit: type=1400 
audit(1524581424.698:1946): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:24 coal kernel: [ 7997.912122] audit: type=1400 
audit(1524581424.698:1947): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 
comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:28 coal kernel: [ 8001.418173] audit: type=1400 
audit(1524581428.206:1948): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc"

[Touch-packages] [Bug 1766628] Re: apparmor denies VLC to open files in devmode

2018-04-26 Thread Konstantin Pavlov

ubuntu 16.04 apparmor vlc rules

** Attachment added: "/var/lib/snapd/apparmor/profiles/snap.vlc.vlc from ubuntu 
16.04"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1766628/+attachment/5127650/+files/snap.vlc.vlc

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

Title:
  apparmor denies VLC to open files in devmode

Status in apparmor package in Ubuntu:
  New

Bug description:
  I see failures in VLC trying to open files and prefs while VLC snap
  seemingly uses devmode since this is on Debian "testing".

  Failures:
  ^[[1;3CApr 24 17:50:24 coal kernel: [ 7997.906298] audit: type=1400 
audit(1524581424.694:1944): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:24 coal kernel: [ 7997.906308] audit: type=1400 
audit(1524581424.694:1945): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" 
pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:24 coal kernel: [ 7997.912113] audit: type=1400 
audit(1524581424.698:1946): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:24 coal kernel: [ 7997.912122] audit: type=1400 
audit(1524581424.698:1947): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 
comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:28 coal kernel: [ 8001.418173] audit: type=1400 
audit(1524581428.206:1948): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:28 coal kernel: [ 8001.418180] audit: type=1400 
audit(1524581428.206:1949): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel.tbcache" 
pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:28 coal kernel: [ 8001.422473] audit: type=1400 
audit(1524581428.210:1950): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/#268898190" pid=19173 comm="vlc" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:28 coal kernel: [ 8001.422481] audit: type=1400 
audit(1524581428.210:1951): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" 
name="/home/thresh/snap/vlc/288/.local/share/user-places.xbel" pid=19173 
comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/thresh/snap/vlc/288/.local/share/#268898190"
  Apr 24 17:50:28 coal kernel: [ 8001.556305] audit: type=1400 
audit(1524581428.342:1952): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" 
denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:28 coal kernel: [ 8001.556318] audit: type=1400 
audit(1524581428.342:1953): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcxkYxzT.1.slave-socket" 
pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/run/user/1000/snap.vlc/#511744"
  Apr 24 17:50:28 coal kernel: [ 8001.556324] audit: type=1400 
audit(1524581428.342:1954): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/run/user/1000/snap.vlc/#511744" pid=19173 comm="vlc" requested_mask="l" 
denied_mask="l" fsuid=1000 ouid=1000
  Apr 24 17:50:28 coal kernel: [ 8001.556332] audit: type=1400 
audit(1524581428.342:1955): apparmor="DENIED" operation="link" 
profile="snap.vlc.vlc" name="/run/user/1000/snap.vlc/vlcbTrpmK.1.slave-socket" 
pid=19173 comm="vlc" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/run/user/1000/snap.vlc/#511744"
  Apr 24 17:50:28 coal kernel: [ 8001.556338] audit: type=1400 
audit(1524581428.342:1956): apparmor="DENIED" operation="link" info="Failed 
name lookup - deleted entry" error=-2 profile="snap.vlc.vlc" 
name="/run/user/1000/snap.vlc/#511744"

[Touch-packages] [Bug 1767115] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (was running upd

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1 (was running updates)

Status in avahi package in Ubuntu:
  New

Bug description:
  Was running the GUI Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 13:52:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-22 (246 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2018-04-18T10:29:06.978246

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

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

[Touch-packages] [Bug 1767115] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (was running upd

2018-04-26 Thread Marcus Howarth

When prompted I asked to keep my amended conf, it has workaround for
network

   domain-name=.alocal

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1 (was running updates)

Status in avahi package in Ubuntu:
  New

Bug description:
  Was running the GUI Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 13:52:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-22 (246 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2018-04-18T10:29:06.978246

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

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

[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

Update,

I noticed the pattern so far and turning off pulseaudio seems to have
stopped the behaviour. I obviously can't leave the system without sound,
so I'm still looking for a permanent fix.

The pattern is allways like this: 
Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 
path=/MediaEndpoint/A2DPSource
Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 
path=/MediaEndpoint/A2DPSink
Apr 26 15:06:07 ESS-PC26 pulseaudio[12799]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.of
Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Successfully made thread 12829 of 
process 12829 (n/a) owned by '108' high priority at nice level -11.
Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Supervising 9 threads of 3 
processes of 2 users.
Apr 26 15:06:07 ESS-PC26 pulseaudio[12829]: [pulseaudio] pid.c: Daemon already 
running.
Apr 26 15:06:14 ESS-PC26 org.gtk.vfs.Daemon[12708]: A connection to the bus 
can't be made


Bluetooth tries to register a device or something, pulse fails and system loggs 
out. My current workaround is to completely turn off pulseaudio by creating  a 
~/.pulse/client.conf file with autospawn=no inside.

As I've already mentioned before, pulseaudio crashing leves no crash
log. How an I get this fixed/debugged?

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

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome
  as desktop environments.

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

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

[Touch-packages] [Bug 1767113] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1767115] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (was running u

2018-04-26 Thread Marcus Howarth

Public bug reported:

Was running the GUI Software Updater

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Apr 26 13:52:42 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-08-22 (246 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.avahi.avahi-daemon.conf: 2018-04-18T10:29:06.978246

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


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

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1 (was running updates)

Status in avahi package in Ubuntu:
  New

Bug description:
  Was running the GUI Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 13:52:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-22 (246 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2018-04-18T10:29:06.978246

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

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

[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

2018-04-26 Thread Hontas Farmer

Yes it does have hybrid graphics.  I also use an external GPU.  This
occurs with or without the EGPU plugged in.

However, it may be that there was a problem in that specific version of
SDDM in that particular daily build.  Somehow, someway installing the
Ubuntu Gnome desktop system and gdm2 fixed it.  Then I did a full
upgrade a couple days ago and got a new version of sddm, switched to
that and that seems to have fixed it.

The real problem is that a new user when confronted with a utterly BLACK
screen won't know to Ctrl alt f6 into a terminal and do things from
there.  That sort of thing is a typical "why Linux will always be for
geeks" moment.

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

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

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

[Touch-packages] [Bug 1767113] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

Public bug reported:

Upgraded to new ca-certificates and still says script returned 2.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Thu Apr 26 21:00:57 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2015-09-28 (940 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check third-party-packages

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgraded to new ca-certificates and still says script returned 2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 21:00:57 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2015-09-28 (940 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767113/+subscriptions

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

[Touch-packages] [Bug 1767042] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

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

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upgrading from 17.10 to 18.04.
  This error triggers many more similar warning dialogs during the install 
process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 01:27:12 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-05-25 (1067 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767042/+subscriptions

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

[Touch-packages] [Bug 1767089] Re: totem cannot play h.264 on 18.04

2018-04-26 Thread Jay S.

It appears to affect several h.264 encoded videos I have. I have
recently purchased a number of course videos consisting each of
individual clips - and none of those will play. They do play in VLC and
SMPlayer so I assume the clips are fine.

As for precedents, I cannot think of any. It is true I have had the
occasional h.264 video failing to render as a thumbnail (I believe that
started around 16.04) - but those were exceptions and it did did not
prevent those videos from playing. Now I get neither thumbnails nor
playback so it is worse. And it affects many more videos, too.

As requested, I have added a clip that is affected by the bug.

** Attachment added: "01 - Course Introduction.mp4"

https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+attachment/5127610/+files/01%20-%20Course%20Introduction.mp4

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

Title:
totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
New

Bug description:
On a fresh install of 18.04, Totem fails to play recent h.264 video
(audio is fine). Obviously, that means failed thumbnails, too.

I have the whole set of gstreamer plugins installed (version
1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+subscriptions

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

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

2018-04-26 Thread Ernst Sjöstrand

mkinitramfs runs modinfo -F firmware i915 which only lists the following files:
i915/bxt_dmc_ver1_07.bin
i915/skl_dmc_ver1_26.bin
i915/kbl_dmc_ver1_01.bin
i915/skl_guc_ver6_1.bin
i915/kbl_huc_ver02_00_1810.bin
i915/bxt_huc_ver01_07_1398.bin
i915/skl_huc_ver01_07_1398.bin

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [

[Touch-packages] [Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

Regression Potential?

For example, what if the if statement now unintentionally never succeeds
even if get_timestamp would work?

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

2018-04-26 Thread Paul

I know as an end-user it would be nice to be prompted about what to do
with a duplicate certificate. That way when you are install more than
one packages you will not have to run "apt install -f" to get things
working.

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Bionic:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in ca-certificates package in Debian:
  New

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1767098] [NEW] Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

2018-04-26 Thread Luke Carrier

Public bug reported:

On a fresh installation of Ubuntu 18.04, both DVI outputs on the back of
the card function as expected but it is not possible to enable the HDMI
output.

I can reliably reproduce the issue under both X and Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 26 11:22:57 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
InstallationDate: Installed on 2018-04-26 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

Status in xorg package in Ubuntu:
  New

Bug description:
  On a fresh installation of Ubuntu 18.04, both DVI outputs on the back
  of the card function as expected but it is not possible to enable the
  HDMI output.

  I can reliably reproduce the issue under both X and Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 11:22:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor:

[Touch-packages] [Bug 1767089] Re: totem cannot play h.264 on 18.04

2018-04-26 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+subscriptions

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

[Touch-packages] [Bug 1767089] Re: totem cannot play h.264 on 18.04

2018-04-26 Thread Sebastien Bacher

Did you try on one of several files? Did they use to play on previous
Ubuntu version? Would it be possible to attach a file example or give an
url to download one?

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+subscriptions

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

[Touch-packages] [Bug 1332440] Re: apt-get update very slow when ulimit -n is big

I have verified that none of these failures are regressions; they all
appear in previous apt uploads/run against other triggers too.

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

Title:
  apt-get update very slow when ulimit -n is big

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt is slow at spawning subprocesses, as it calls fcntl() on each file 
descriptor, causing significant slowdown. On my container:

  0.71user 1.26system 0:01.98elapsed 99%CPU (0avgtext+0avgdata
  34164maxresident)k

  0.14user 0.05system 0:00.20elapsed 99%CPU (0avgtext+0avgdata
  34428maxresident)k

  - a 10 times difference.

  [Test case]
  (1) Run strace -f -c apt-cache search test >/dev/null, count getrlimit() and 
fcntl() calls
  (2) Upgrade libapt-pkg4.12 to proposed
  (3) Run (1) again, make sure it's significantly lower.

  
  [Regression potential]
  Isolated fix in closing "unwanted" file descriptors. Has been in use for 
years now, but if there were a regression it would probably be an fd leak.

  [Original bug report]
  I use strace to see why apt-get update is too slow,
  finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'

  ubuntu 14.04

  root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
  Package: apt
  Priority: important
  Section: admin
  Installed-Size: 3576
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Architecture: amd64
  Version: 1.0.1ubuntu2.1
  Replaces: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), 
openjdk-6-jdk (<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 
0)
  Depends: libapt-pkg4.12 (>= 0.9.16), libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), 
libstdc++6 (>= 4.6), ubuntu-keyring, gnupg
  Suggests: aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), apt-doc, 
python-apt
  Conflicts: python-apt (<< 0.7.93.2~)
  Breaks: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), openjdk-6-jdk 
(<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 0)
  Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
  Size: 952374

  [pid 20525] 
stat("/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS",
 0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
  [pid 20525] stat("/usr/lib/apt/methods/bzip2", {st_mode=S_IFREG|0755, 
st_size=23056, ...}) = 0
  [pid 20525] pipe([9, 11])   = 0
  [pid 20525] pipe([13, 14])  = 0
  [pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f99f1ea9a50) = 20538
  Process 20538 attached
  [pid 20525] fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
  [pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
  [pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_GETFL 
  [pid 20538] <... rt_sigaction resumed> {SIG_IGN, [PIPE], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0x1 (flags O_WRONLY)
  [pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0
  [pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(11 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(13 
  [pid 20538] <... rt_sigaction resumed> {0x409140, [WINCH], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGCONT, {SIG_DFL, [CONT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] select(10, [9], NULL, NULL, NULL 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] rt_sigaction(SIGTSTP, {SIG_DFL, [TSTP], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0}, {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(4, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(5, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100,

[Touch-packages] [Bug 1766566] Re: lib64z1: call dh_makeshlibs for the lib64z1 package

2018-04-26 Thread Matthias Klose

It's a change to a library package which is normally unused, so I don't
see any regression potential there.

However zlib was not built in trusty, but in saucy only. So there could
be unexpected results, however I don't see build failures in the trusty
test rebuilds either.

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

Title:
  lib64z1: call dh_makeshlibs for the lib64z1 package

Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Trusty:
  New

Bug description:
  SRU:

  dh_makeshlibs is not called for the lib64z1 package, letting packages
  which have dependencies on this library fail to build:

  DIRNAME=64  dh_shlibdeps -plib64gphobos71 
-l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib
 -- -Ldebian/shlibs.common64
  dpkg-shlibdeps: error: no dependency information found for 
/usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6
  4/libgphobos.so.71.0.2)
  dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars 
-l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l
  ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 
-l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi
  an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 
debian/lib64gphobos71/usr/lib64/libgdruntime.so
  .71.0.2 returned exit code 2
  make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2

  The fix is simple, and in wily and newer Ubuntu versions.

  SRU validation: the package builds, and dh_shlibdeps doesn't fail
  anymore for depending packages (e.g. the gcc-7 build in the ubuntu-
  toolchain-r/test directory.

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

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

[Touch-packages] [Bug 1767096] [NEW] Random Xorg crashes

2018-04-26 Thread spodin

Public bug reported:

Xorg crashes randomly: environment just freezes for a second and I'm
getting login screen.

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Pantheon
Date: Thu Apr 26 12:57:22 2018
InstallationDate: Installed on 2018-03-01 (55 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1332440] Re: apt-get update very slow when ulimit -n is big

There are some dep8 regressions reported in http://people.canonical.com
/~ubuntu-archive/pending-sru.html. I've requested some retries. If
they're still failing, please could you take a look?

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

Title:
  apt-get update very slow when ulimit -n is big

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt is slow at spawning subprocesses, as it calls fcntl() on each file 
descriptor, causing significant slowdown. On my container:

  0.71user 1.26system 0:01.98elapsed 99%CPU (0avgtext+0avgdata
  34164maxresident)k

  0.14user 0.05system 0:00.20elapsed 99%CPU (0avgtext+0avgdata
  34428maxresident)k

  - a 10 times difference.

  [Test case]
  (1) Run strace -f -c apt-cache search test >/dev/null, count getrlimit() and 
fcntl() calls
  (2) Upgrade libapt-pkg4.12 to proposed
  (3) Run (1) again, make sure it's significantly lower.

  
  [Regression potential]
  Isolated fix in closing "unwanted" file descriptors. Has been in use for 
years now, but if there were a regression it would probably be an fd leak.

  [Original bug report]
  I use strace to see why apt-get update is too slow,
  finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'

  ubuntu 14.04

  root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
  Package: apt
  Priority: important
  Section: admin
  Installed-Size: 3576
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Architecture: amd64
  Version: 1.0.1ubuntu2.1
  Replaces: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), 
openjdk-6-jdk (<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 
0)
  Depends: libapt-pkg4.12 (>= 0.9.16), libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), 
libstdc++6 (>= 4.6), ubuntu-keyring, gnupg
  Suggests: aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), apt-doc, 
python-apt
  Conflicts: python-apt (<< 0.7.93.2~)
  Breaks: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), openjdk-6-jdk 
(<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 0)
  Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
  Size: 952374

  [pid 20525] 
stat("/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS",
 0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
  [pid 20525] stat("/usr/lib/apt/methods/bzip2", {st_mode=S_IFREG|0755, 
st_size=23056, ...}) = 0
  [pid 20525] pipe([9, 11])   = 0
  [pid 20525] pipe([13, 14])  = 0
  [pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f99f1ea9a50) = 20538
  Process 20538 attached
  [pid 20525] fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
  [pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
  [pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_GETFL 
  [pid 20538] <... rt_sigaction resumed> {SIG_IGN, [PIPE], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0x1 (flags O_WRONLY)
  [pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0
  [pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(11 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(13 
  [pid 20538] <... rt_sigaction resumed> {0x409140, [WINCH], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGCONT, {SIG_DFL, [CONT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] select(10, [9], NULL, NULL, NULL 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] rt_sigaction(SIGTSTP, {SIG_DFL, [TSTP], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0}, {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(4, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(5, F_SETFD, FD_CLOEXEC) = 0

[Touch-packages] [Bug 1766566] Re: lib64z1: call dh_makeshlibs for the lib64z1 package

(or if it doesn't apply, please explain that here)

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

Title:
  lib64z1: call dh_makeshlibs for the lib64z1 package

Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Trusty:
  New

Bug description:
  SRU:

  dh_makeshlibs is not called for the lib64z1 package, letting packages
  which have dependencies on this library fail to build:

  DIRNAME=64  dh_shlibdeps -plib64gphobos71 
-l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib
 -- -Ldebian/shlibs.common64
  dpkg-shlibdeps: error: no dependency information found for 
/usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6
  4/libgphobos.so.71.0.2)
  dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars 
-l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l
  ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 
-l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi
  an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 
debian/lib64gphobos71/usr/lib64/libgdruntime.so
  .71.0.2 returned exit code 2
  make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2

  The fix is simple, and in wily and newer Ubuntu versions.

  SRU validation: the package builds, and dh_shlibdeps doesn't fail
  anymore for depending packages (e.g. the gcc-7 build in the ubuntu-
  toolchain-r/test directory.

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

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

[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

Went, did step 1 and 2, looked in /var/crash and there was nothing.

There are no crash logs in that location for the event that just
happened.

Attached another printout of journalctl. From what I can tell the system
went in full shutdown mode and logged the user out.

** Attachment added: "journalclt printout"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+attachment/5127533/+files/crash2.txt

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

Title:
pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
Hello,

I'm a sysadmin and have gotten multiple reports recently from users of
them randomly getting logged out of their machines. From what I can
tell from the journalctl printout this appears immediately after
either bluetoothd or pulsaudio crashes.

This is happening multiple time each day for each user. It doesn't
happen to all users, but the reports seem to be getting more frequent
by the day. From what I have noticed there recently was an update for
pulseaudio and its bluetooth integration.

Here is the journalctl printout:
Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219
path=/MediaEndpoint/A2DPSource
Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219
path=/MediaEndpoint/A2DPSink
Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c:
Failed to register as a handsfree audio agent with ofono:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided
by any .service files
Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of
process 8042 (n/a) owned by '108' high priority at nice level -11.
Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2
processes of 1 users.
Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already
running.
Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus
can't be made
Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session):
session closed for user lightdm

We are running Ubuntu 16.04 LTS with the latest updated.

EDIT: Worth mentioning, this error happens with both Unity and Gnome
as desktop environments.

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

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

[Touch-packages] [Bug 1766566] Re: lib64z1: call dh_makeshlibs for the lib64z1 package

Thank you for the upload. Please fill out the Regression Potential
information. See https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

Title:
  lib64z1: call dh_makeshlibs for the lib64z1 package

Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Trusty:
  New

Bug description:
  SRU:

  dh_makeshlibs is not called for the lib64z1 package, letting packages
  which have dependencies on this library fail to build:

  DIRNAME=64  dh_shlibdeps -plib64gphobos71 
-l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib
 -- -Ldebian/shlibs.common64
  dpkg-shlibdeps: error: no dependency information found for 
/usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6
  4/libgphobos.so.71.0.2)
  dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars 
-l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l
  ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 
-l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi
  an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 
debian/lib64gphobos71/usr/lib64/libgdruntime.so
  .71.0.2 returned exit code 2
  make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2

  The fix is simple, and in wily and newer Ubuntu versions.

  SRU validation: the package builds, and dh_shlibdeps doesn't fail
  anymore for depending packages (e.g. the gcc-7 build in the ubuntu-
  toolchain-r/test directory.

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

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

[Touch-packages] [Bug 1767086] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

2018-04-26 Thread Dave Schulz

Public bug reported:

a

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.12
ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-111-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Thu Apr 26 15:26:29 2018
DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.12:subprocess 
installed post-installation script returned error exit status 29
ErrorMessage: subprocess installed post-installation script returned error exit 
status 29
InstallationDate: Installed on 2018-01-17 (98 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
UpgradeStatus: Upgraded to trusty on 2018-04-12 (13 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 29

Status in openssl package in Ubuntu:
  New

Bug description:
  a

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.12
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Thu Apr 26 15:26:29 2018
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.12:subprocess 
installed post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2018-01-17 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 29
  UpgradeStatus: Upgraded to trusty on 2018-04-12 (13 days ago)

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

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

[Touch-packages] [Bug 1767089] [NEW] totem cannot play h.264 on 18.04

2018-04-26 Thread Jay S.

Public bug reported:

On a fresh install of 18.04, Totem fails to play recent h.264 video
(audio is fine). Obviously, that means failed thumbnails, too.

I have the whole set of gstreamer plugins installed (version
1.14.0-1ubuntu1), including the libav plugin.

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+subscriptions

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

[Touch-packages] [Bug 1767086] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

** Tags removed: need-duplicate-check

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 29

Status in openssl package in Ubuntu:
  New

Bug description:
  a

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.12
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Thu Apr 26 15:26:29 2018
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.12:subprocess 
installed post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2018-01-17 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.12 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 29
  UpgradeStatus: Upgraded to trusty on 2018-04-12 (13 days ago)

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

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

[Touch-packages] [Bug 810339] Re: Garbage when using qemu/kvm and cirrus emulation

2018-04-26 Thread Bug Watch Updater

** Changed in: mesa
   Status: Confirmed => Fix Released

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

Title:
  Garbage when using qemu/kvm and cirrus emulation

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce :
  glxgears

  (glxgears will display garbage on screen)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libgl1-mesa-glx 7.11~1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic x86_64
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul 14 11:07:19 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  GraphicsCard:
   Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc Device [1af4:1100]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Bochs Bochs
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-5-generic 
root=UUID=a0a28524-bdce-4d53-aa8b-f6f36554f5d3 ro quiet splash vt.handoff=7
  Renderer: Unknown
  SourcePackage: mesa
  UdevDb: Error: [Errno 2] No such file or directory
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
  dmi.product.name: Bochs
  dmi.sys.vendor: Bochs
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu6
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11~1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11~1-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.2-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Touch-packages] [Bug 1760848] Re: lxc-create can't create bionic container on xenial

2018-04-26 Thread Oliver Mueller

In my case the underlying host is an ubuntu 16.04. I don't know, if that
can cause trouble?

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

Title:
  lxc-create can't create bionic container on xenial

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  
  I did run:

   lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic

  which fails in the end:

  (...)
  Download complete
  Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... 
  Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ...
  Generating locales (this might take a while)...
de_DE.UTF-8... done
  Generation complete.
  mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' 
nicht möglich: Datei oder Verzeichnis nicht gefunden
  lxc-create: lxccontainer.c: create_run_template: 1295 container creation 
template for ubu18.04 failed
  lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04

  I've seen that when creating a xenial container this is the point
  where new sshd keys get created.

dpkg -l 'lxc*'
  ||/ Name   Version
  +++-==-==-
  ii  lxc2.0.8-0ubuntu1~16.04.2 
  ii  lxc-common 2.0.8-0ubuntu1~16.04.2 
  ii  lxc-templates  2.0.8-0ubuntu1~16.04.2 
  ii  lxc1   2.0.8-0ubuntu1~16.04.2 
  ii  lxcfs  2.0.8-0ubuntu1~16.04.2 
  un  lxcguest   
  un  lxctl

  
lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1760848] Re: lxc-create can't create bionic container on xenial

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

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

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

Title:
  lxc-create can't create bionic container on xenial

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  
  I did run:

   lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic

  which fails in the end:

  (...)
  Download complete
  Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... 
  Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ...
  Generating locales (this might take a while)...
de_DE.UTF-8... done
  Generation complete.
  mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' 
nicht möglich: Datei oder Verzeichnis nicht gefunden
  lxc-create: lxccontainer.c: create_run_template: 1295 container creation 
template for ubu18.04 failed
  lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04

  I've seen that when creating a xenial container this is the point
  where new sshd keys get created.

dpkg -l 'lxc*'
  ||/ Name   Version
  +++-==-==-
  ii  lxc2.0.8-0ubuntu1~16.04.2 
  ii  lxc-common 2.0.8-0ubuntu1~16.04.2 
  ii  lxc-templates  2.0.8-0ubuntu1~16.04.2 
  ii  lxc1   2.0.8-0ubuntu1~16.04.2 
  ii  lxcfs  2.0.8-0ubuntu1~16.04.2 
  un  lxcguest   
  un  lxctl

  
lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-26 Thread Ivan Antonijevic

I have same problem. After dist-upgrade from 17.10 to 18.04. I get black
screen, and tty only.

I can startx after removing nvidia

sudo apt-get purge nvidia*

sudo apt dist-upgrade

and remove old xorg.conf

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf_bck

Now I can get X with startx, but on boot I still getting only black
screen and tty.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

** Description changed:

  Hello,
  
  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can tell
  from the journalctl printout this appears immediately after either
  bluetoothd or pulsaudio crashes.
  
  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent by
  the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.
  
  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  
  We are running Ubuntu 16.04 LTS with the latest updated.
+ 
+ EDIT: Worth mentioning, this error happens with both Unity and Gnome as
+ desktop environments.

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

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome
  as desktop environments.

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

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

[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

If there's a crash then we will need a formal crash report. To generate
one, please:

1. Apply the workaround from bug 994921.
2. Reproduce the problem.
3. Look in /var/crash for crash files and upload them by running:
   ubuntu-bug /var/crash/YOURFILE.crash
4. Let us know the ID of the new bug created.

P.S. Please don't attach crash files to existing bugs. They must be
uploaded by the 'ubuntu-bug' command.

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

** Tags added: xenial

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

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome
  as desktop environments.

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

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

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

2018-04-26 Thread Ubuntu Foundations Team Bug Bot

The attachment "This is a patch to dell-wmi.c kernel module adding 2 new
key definitions" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  dell_wmi: Unknown key codes

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1767065] [NEW] pulseaudio+bluetooth crash causing user to be logged out