[Touch-packages] [Bug 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

[fumihiko kakuma]

** Description changed:

  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.
  
  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #
  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $
  
  I sent the patch for this bug to ML of upstream.
  
  https://www.spinics.net/lists/netdev/msg511127.html
+ 
+ I think that the above patch can be applied for the bionic.

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

The fix for 18.04 is now available for testing, in bionic proposed.

If you would like to just download and test the debs directly they are here:
https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1/+build/15084683

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1780165] Re: tc does not display value of prio and quantum options of htb

[fumihiko kakuma]

** Description changed:

  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.
  
  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #
  
+ $ lsb_release -a
+ No LSB modules are available.
+ Distributor ID: Ubuntu
+ Description:Ubuntu 18.04 LTS
+ Release:18.04
+ Codename:   bionic
+ $ uname -a
+ Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ $ dpkg -l | grep iproute
+ ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
+ $
+ 
  I sent the patch for this bug to ML of upstream.
  
  https://www.spinics.net/lists/netdev/msg511127.html

** Summary changed:

- tc does not display value of prio and quantum options of htb
+ tc does not display value of prio and quantum options of htb on bionic

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

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

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

[Touch-packages] [Bug 1780169] Re: Orientation was disappeared when the machine has accelerometer in 18.04

[Daniel van Vugt]

I get the feeling this might be an intentional feature. To check, please
report the problem to the Gnome developers here:

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues

and then tell us the ID of the issue you have reported.

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

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

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

Title:
  Orientation was disappeared when the machine has accelerometer in
  18.04

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

Bug description:
  When the machine has accelerometer, rotate the machine, the display
  orientation can be changed in 18.04

  If connect to an external monitor, can't change the orientation to
  Portrait Right, Portrait Left ...etc. manually, because "Orientation"
  was disappeared in Settings->Devices->Displays

  This is not friendly to the user who need to change the orientation
  when connect to an external monitor. (For example: need to review
  documents/codes on external monitor with Portrait mode)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-1008.11-oem 4.15.18
  Uname: Linux 4.15.0-1008-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 09:58:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0808]
  InstallationDate: Installed on 2018-06-26 (8 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-01:51
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0eef:c0aa D-WAV Scientific Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1008-oem 
root=UUID=dcf424c6-e978-4c99-a6b0-532aa8a913a6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd07/06/2017:svnDellInc.:pnInspiron5579:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5579
  dmi.sys.vendor: Dell Inc.
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1780169/+subscriptions

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

[Touch-packages] [Bug 1779413] Re: Bluetooth bug

[Daniel van Vugt]

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

OK, thanks. If it fails after "falling into a dream" then this sounds
like bug 1246981, which may be related to the more recent bug 1779289.

** This bug has been marked a duplicate of bug 1246981
   Bluetooth mouse fails to re-connect after sleep.

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  

[Touch-packages] [Bug 1780077] Re: FIFO underrun error

[Daniel van Vugt]

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

It sounds like you're referring to:

[   22.774658] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
[   23.870619] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
[   24.280905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
Rx/Tx
[   24.281048] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   25.216644] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
[   26.474633] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
[   27.720650] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun

So this would be a kernel bug. However in my experience such kernel
errors are also not fatal and won't cause permanent graphics problems.

Looking at your CPU model however:
  Core(TM)2 Duo CPU E8500 
I can tell you are experiencing bug 1727356, which is not related to kernel 
errors at all.

** This bug has been marked a duplicate of bug 1727356
   Wayland sessions (including the login screen itself) don't start up on older 
Intel GPUs (pre-Sandy Bridge)

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

Title:
  FIFO underrun error

Status in xorg package in Ubuntu:
  New

Bug description:
  Subunit 18.04 LTS
  System will not boot.

  I updated graphics drivers I think erroneously, then received the
  underrun errors and created a swap partition by accident following a
  fix for a similar error as was having trouble booting crypt.  I
  commented out the swap and turned off swap and have updated my drivers
  and purged previous.  I can access terminal, yet still cannot boot due
  to the undercut.  I think I need to create a .conf file for the
  graphics drivers.

  CPU pipe B FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Jul  4 03:45:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
 Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:3048]
  InstallationDate: Installed on 2018-01-25 (160 days ago)
  InstallationMedia: It
  MachineType: LENOVO 7220RY8
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/it--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT77AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NONE
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7220RY8:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.family: NONE
  dmi.product.name: 7220RY8
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.92+git1806210630.7164ab~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1807040730.45f9d5~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1807040730.45f9d5~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Wed Jul  4 03:33:45 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Daniel van Vugt]

Hmm, that's not right. The command:
  sudo apt install pulseaudio-module-jack
completes successfully on 16.04 for me.

Please run:
  dpkg -l > dpkgl.txt
and send us the resulting file.

You may also want to try downloading the package(s) directly:
  
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.10/+build/14813746

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Daniel van Vugt]

Also remember to run this first:

  sudo apt update

then:

  sudo apt install pulseaudio-module-jack

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779413] Re: Bluetooth bug

[John Daniels]

The mouse is connected only after its removal and reboot of the
bluetooth. But as soon as the mouse turns off falling into a dream, you
have to remove it again and restart the bluetooth. Pair does not happen.

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p: 

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)

[Daniel van Vugt]

I'm going to say that patch is rejected. It will hurt more users than it
helps and this problem only occurs on rack server graphics chips (also
seen on Matrox ones too).

Please run 'lspci -k' and send us the output.

** Summary changed:

- 18.04 login screen is blur
+ 18.04 login screen is skewed/distorted (incorrect stride)

** Tags removed: patch

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

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

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

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

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

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride)

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 1780169] [NEW] Orientation was disappeared when the machine has accelerometer in 18.04

[Betty Lin]

Public bug reported:

When the machine has accelerometer, rotate the machine, the display
orientation can be changed in 18.04

If connect to an external monitor, can't change the orientation to
Portrait Right, Portrait Left ...etc. manually, because "Orientation"
was disappeared in Settings->Devices->Displays

This is not friendly to the user who need to change the orientation when
connect to an external monitor. (For example: need to review
documents/codes on external monitor with Portrait mode)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-1008.11-oem 4.15.18
Uname: Linux 4.15.0-1008-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  5 09:58:23 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0808]
InstallationDate: Installed on 2018-06-26 (8 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-01:51
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0eef:c0aa D-WAV Scientific Co., Ltd 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5579
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1008-oem 
root=UUID=dcf424c6-e978-4c99-a6b0-532aa8a913a6 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd07/06/2017:svnDellInc.:pnInspiron5579:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5579
dmi.sys.vendor: Dell Inc.
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

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

Title:
  Orientation was disappeared when the machine has accelerometer in
  18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  When the machine has accelerometer, rotate the machine, the display
  orientation can be changed in 18.04

  If connect to an external monitor, can't change the orientation to
  Portrait Right, Portrait Left ...etc. manually, because "Orientation"
  was disappeared in Settings->Devices->Displays

  This is not friendly to the user who need to change the orientation
  when connect to an external monitor. (For example: need to review
  documents/codes on external monitor with Portrait mode)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-1008.11-oem 4.15.18
  Uname: Linux 4.15.0-1008-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 09:58:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0808]
  InstallationDate: Installed on 2018-06-26 (8 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-01:51
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0eef:c0aa D-WAV Scientific Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1008-oem 
root=UUID=dcf424c6-e978-4c99-a6b0-532aa8a913a6 ro quiet splash vt.handoff=1
  

[Touch-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI

[Daniel van Vugt]

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

Regardless of how often it happens it still sounds like bug 1711101. And
the workaround in bug 1711101 also sounds exactly like the workaround
you mention:

  "After clicking the "Speakers - Built-in Audio" line in the Output tab
of the settings (the only line available) everything is now correct."

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

Title:
  Output device doesn't always switch back from HDMI

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I disconnect to an HDMI output sometimes the configuration is
  left in an inconsistent state. It still shows as being connected to
  HDMI in volume up/down but there is no longer an HDMI option in the
  sound settings. After clicking the "Speakers - Built-in Audio" line in
  the Output tab of the settings (the only line available) everything is
  now correct. The same issue was also present in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   32004 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 22:54:14 2018
  InstallationDate: Installed on 2018-05-31 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1779413] Re: Bluetooth bug

[Daniel van Vugt]

Also, does the mouse never connect at all? Or just not reconnect on
login or on resume from suspend?

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pocoz  2614 F...m pulseaudio
   

[Touch-packages] [Bug 1780165] [NEW] tc does not display value of prio and quantum options of htb

[fumihiko kakuma]

Public bug reported:

For example when I execute the following commandline, tc does not
display value of prio and quantum option.

# tc qdisc add dev eno2 root handle 1: htb default 10
# tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
# tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
# tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
# tc -d class show dev eno2
class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit linklayer 
ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
#

I sent the patch for this bug to ML of upstream.

https://www.spinics.net/lists/netdev/msg511127.html

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

** Summary changed:

- tc does not to display prio and quantum options of htb
+ tc does not display value of prio and quantum options of htb

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

Title:
  tc does not display value of prio and quantum options of htb

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

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

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

[Touch-packages] [Bug 1779622] Re: issue is regarding boot hanging between work

[Alex Murray]

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

Title:
  issue is regarding boot hanging between work

Status in xorg package in Ubuntu:
  New

Bug description:
  the system get hang while booting and also when shutting down. while
  work some of keyboard functions stop working like brightness control
  and  sound control. at times system has to be force shut down. at
  times some of the application do not get opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jul  2 12:59:44 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-02-22 (129 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override 
locale=en_US plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0C6XG5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  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 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
  xserver.bootTime: Mon Jul  2 12:45:36 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1317 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1779201] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Alex Murray]

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

** 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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1779201

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 28 21:23:09 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-06-09 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  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.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779201/+subscriptions

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

[Touch-packages] [Bug 1779201] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1779237
   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 28 21:23:09 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-06-09 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  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.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779201/+subscriptions

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

[Touch-packages] [Bug 1780156] Re: systemd-journald crashed with SIGABRT in fsync()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1750855

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in fsync()

Status in systemd package in Ubuntu:
  New

Bug description:
  using thunar to navigate file system  and experienced a background
  error alert .. Midnight commander was also running copying files over
  network to another system .. did not stop so unaffected..  usual
  background xfce4 desktop stuff operating normally

  running cosmic 18.10 with proposed  packages etc.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: systemd 238-5ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Wed Jul  4 17:04:41 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-03-24 (467 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  MachineType: LENOVO 2746CTO
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=9eb5f4f3-b3fe-4bd7-b14c-b16e485f5865 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=17) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () from /lib/systemd/libsystemd-shared-238.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-238.so
   ?? () from /lib/systemd/libsystemd-shared-238.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-238.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: Upgraded to cosmic on 2018-06-07 (27 days ago)
  UserGroups:
   
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1774419] Re: easy_install command is missing

[Sebastian]

I am affected by this as well. Using EasyBuild which relies on
easy_install command during its installation problem. In 17.10 the cmd
is still there. Worked around it by copying the easy_install cmd from
17.10 (its actually just a short python script) and putting it into the
path. This works for me, but it is still weird that it is missing. Also
installed setuptools just via pip. Same thing. Did they make some
changes to setuptools?

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

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

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

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

[Touch-packages] [Bug 1774419] Re: easy_install command is missing

[Launchpad Bug Tracker]

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

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

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

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

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

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

[Touch-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI

[Pedro Côrte-Real]

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

I don't think this is a duplicate. My laptop does switch from HDMI most
of the time, just not always. And today I just noticed something very
strange. I booted the computer and the audio got set to HDMI even though
I had nothing attached to it.

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

Title:
  Output device doesn't always switch back from HDMI

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I disconnect to an HDMI output sometimes the configuration is
  left in an inconsistent state. It still shows as being connected to
  HDMI in volume up/down but there is no longer an HDMI option in the
  sound settings. After clicking the "Speakers - Built-in Audio" line in
  the Output tab of the settings (the only line available) everything is
  now correct. The same issue was also present in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   32004 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 22:54:14 2018
  InstallationDate: Installed on 2018-05-31 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Todd Chaffee]

Sorry, I forget to mention the output of that:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package pulseaudio-module-jack is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'pulseaudio-module-jack' has no installation candidate

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779413] Re: Bluetooth bug

[Kai-Heng Feng]

** Also 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/1779413

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pocoz  2614 F...m pulseaudio
   /dev/snd/controlC0:  pocoz  2614 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: 

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Andreas Hasenack]

My fstab has only an entry for /boot/efi. Everything else is zfs.

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1623576k,mode=700,uid=1000,gid=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
  tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

  cat /proc/mounts 
  sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
  proc /proc proc 

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Andreas Hasenack]

I can reproduce this on my 18.04 laptop with zfs on root.

kdump-tools.postinst ends up calling /etc/kernel/postinst.d/kdump-tools 
4.15.0-23-generic, which fails at this mkinitramfs line:
mkinitramfs -d /var/lib/kdump/initramfs-tools -o 
/var/lib/kdump/initrd.img-4.15.0-23-generic.new 4.15.0-23-generic
mkinitramfs: failed to determine device for /

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
  tmpfs on /run/user/1000 type tmpfs 

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Robie Basak]

Hello Ian, or anyone else affected,

Accepted bluez into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed verification-needed-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/1759628

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.34

---
software-properties (0.96.24.34) cosmic; urgency=medium

  [ Andrea Azzarone ]
  * Allow the user to disable livepatch if the gnome-online-account expired.
(lp: #1768797)

 -- Sebastien Bacher   Wed, 04 Jul 2018 15:38:17
+0200

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Touch-packages] [Bug 1778960] Re: SRU: Update python 2.7 to the final 2.7.15 release

[Robie Basak]

> po-33374: Tweak the definition of PyGC_Head, so compilers do not believe
  it is always 16-byte aligned on x86. This prevents crashes with more
  aggressive optimizations present in GCC 8.

Will this cause any ABI issues? It isn't clear to me, so I'd like
confirmation of your opinion please Matthias before accepting. I do see
that the code seems to incorporate some accommodation for the old
structure, but I don't know enough about this area to be sure that this
fully mitigates any ABI issues.

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

Title:
  SRU: Update python 2.7 to the final 2.7.15 release

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate.
  Please let's update to the final release.

  Upstream changes are:

  - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe
it is always 16-byte aligned on x86. This prevents crashes with more
aggressive optimizations present in GCC 8.

  - Identify as 2.7.15 instead of 2.7.15rc1

  Acceptance criteria: The package builds, and the testsuite doesn't
  show regressions.

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

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

[Touch-packages] [Bug 1575779] Re: hostnamectl fails under lxd unpriv container

[Christian Brauner]

Hey, so we're seeing an instance of this issue and the problem is that a
lock is taken on an fd instead of a path. This should be legal and we
urgently need a fix for this since this is starting to break all systemd
services running in a container that use PrivateUsers= and anything else
that hits the following codepath:

if (lockf(netns_storage_socket[0], F_LOCK, 0) < 0)
return -errno;

in systemd.

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

** Changed in: apparmor (Ubuntu)
   Importance: High => Critical

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780099] Re: Cache remapping breaks hashing of Package objects

[Julian Andres Klode]

** Description changed:

  [Impact]
  The apt.Package objects use the id as the hash, but the hash can change after 
reopening, meaning that code will fail to work, for example:
  
  c=apt.Cache()
  p=c["a"]
  set_of_p={p}
  c.open()
  assert p in set_of_p
  
  will fail.
  
  [Test case]
- The above test case is run as part of autopkgtest (syntax is slightly 
different)
+ The above test case is run as part of autopkgtest (syntax is slightly 
different), so passing autopkgtests means verification is done.
  
  [Regression potential]
  Hashing packages objects will be slower as it hashes the name and 
architecture now.

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

Title:
  Cache remapping breaks hashing of Package objects

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  New

Bug description:
  [Impact]
  The apt.Package objects use the id as the hash, but the hash can change after 
reopening, meaning that code will fail to work, for example:

  c=apt.Cache()
  p=c["a"]
  set_of_p={p}
  c.open()
  assert p in set_of_p

  will fail.

  [Test case]
  The above test case is run as part of autopkgtest (syntax is slightly 
different), so passing autopkgtests means verification is done.

  [Regression potential]
  Hashing packages objects will be slower as it hashes the name and 
architecture now.

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

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

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Launchpad Bug Tracker]

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

** Changed in: update-manager (Ubuntu Trusty)
   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/1773316

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Trusty:
  Confirmed
Status in update-manager source package in Trusty:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in update-manager source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  == xenial / trusty ==
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  == bionic+ ===

  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.

  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be
  raised from the apt_pkg layer.

  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()

  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Julian Andres Klode]

** Also affects: python-apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: update-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python-apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: update-manager (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Description changed:

+ == xenial / trusty ==
+ [Impact]
+ Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.
+ 
+ APT relies on the ID of the package (it's position in the cache) for
+ it's operation. So if a package has ID 0 in the old cache, and a
+ different package has ID 0 in the new cache, performing operations on
+ the old package would perform it on the new package. If the old
+ package's ID is out of bounds in the new cache, the behavior is
+ undefined - it's an out of bounds array access.
+ 
+ [Test case]
+ The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.
+ 
+ More test cases like this are in the autopkgtest.
+ 
+ [Regression potential]
+ The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.
+ 
+ == bionic+ ===
+ 
  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.
  
  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be raised
  from the apt_pkg layer.
  
  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()
  
  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.
  
  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Attachment added: "Test case for xenial/trusty"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1773316/+attachment/5159649/+files/a.py

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

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Trusty:
  Confirmed
Status in update-manager source package in Trusty:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in update-manager source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  == xenial / trusty ==
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old 

[Touch-packages] [Bug 1780105] [NEW] [xenial, trusty?] Backport cache remapping to fix crashes

[Julian Andres Klode]

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

Public bug reported:

[Impact]
Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

APT relies on the ID of the package (it's position in the cache) for
it's operation. So if a package has ID 0 in the old cache, and a
different package has ID 0 in the new cache, performing operations on
the old package would perform it on the new package. If the old
package's ID is out of bounds in the new cache, the behavior is
undefined - it's an out of bounds array access.

[Test case]
The attached test case has a list of packages 0-9, a-z; stores the package "z" 
into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

More test cases like this are in the autopkgtest.

[Regression potential]
The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "a.py"
   https://bugs.launchpad.net/bugs/1780105/+attachment/5159648/+files/a.py

** This bug has been marked a duplicate of bug 1773316
   Object of different cache passed as argument to apt_pkg.DepCache method

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

Title:
  [xenial, trusty?] Backport cache remapping to fix crashes

Status in python-apt package in Ubuntu:
  New

Bug description:
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

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

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

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Launchpad Bug Tracker]

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

** Changed in: python-apt (Ubuntu Xenial)
   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/1773316

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Trusty:
  Confirmed
Status in update-manager source package in Trusty:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in update-manager source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  == xenial / trusty ==
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  == bionic+ ===

  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.

  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be
  raised from the apt_pkg layer.

  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()

  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Launchpad Bug Tracker]

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

** Changed in: python-apt (Ubuntu Trusty)
   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/1773316

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Trusty:
  Confirmed
Status in update-manager source package in Trusty:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in update-manager source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  == xenial / trusty ==
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  == bionic+ ===

  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.

  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be
  raised from the apt_pkg layer.

  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()

  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Launchpad Bug Tracker]

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

** Changed in: update-manager (Ubuntu Xenial)
   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/1773316

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Trusty:
  Confirmed
Status in update-manager source package in Trusty:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in update-manager source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  == xenial / trusty ==
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  == bionic+ ===

  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.

  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be
  raised from the apt_pkg layer.

  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()

  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1780099] Re: Cache remapping breaks hashing of Package objects

[Julian Andres Klode]

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

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

Title:
  Cache remapping breaks hashing of Package objects

Status in python-apt package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  New

Bug description:
  [Impact]
  The apt.Package objects use the id as the hash, but the hash can change after 
reopening, meaning that code will fail to work, for example:

  c=apt.Cache()
  p=c["a"]
  set_of_p={p}
  c.open()
  assert p in set_of_p

  will fail.

  [Test case]
  The above test case is run as part of autopkgtest (syntax is slightly 
different)

  [Regression potential]
  Hashing packages objects will be slower as it hashes the name and 
architecture now.

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

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

[Chris]

I started to experience this problem for the first time on July 2nd,
2018 after upgrading to kernel 4.15.0-24-generic. It only happens on
machines with a Nvidia card. It does not matter if ANY Nvidia drivers
are installed or not. I downgraded to kernel 4.15.0-20, 0-22 and 0-23
but it didn't fix the issue. I confirmed this on 2 machines with Nvidia
cards.

adding deb http://de.archive.ubuntu.com/ubuntu/ bionic-proposed
multiverse main universe restricted

to /etc/apt/sources.list

and running apt install libglvnd0 xserver-xorg-core libgl1-mesa-glx did
not help. At least not on Linux Lite v4.0.

It's takes about 3mins and 6 seconds to get to the desktop. Everything
works as normal after that.

So i ran some tests

Lenovo ThinkPad W530 
Model Type: 2436CTO GB
16GB RAM 
Intel i7-3920XM @ 2.90Ghz
4 Core
256 SSD

lspci -vnn | grep VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro 
K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller])



Xubuntu 18.04 LTS (This is my main OS) - Broken

Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install.

Works after fresh install but not after updates applied through Software
Update.

Also tried kernel v4.17.0 and v4.17.3

login with ctrl+alt+f1 and after a few seconds i see:

nouveau :01:00.0: msvld: unable to find firmware data

dmesg | grep nouveau

[   34.304193] nouveau :01:00.0: Direct firmware load for 
nouveau/nve7_fuc084 failed with error -2
[   34.304206] nouveau :01:00.0: Direct firmware load for 
nouveau/nve7_fuc084d failed with error -2
[   34.304210] nouveau :01:00.0: msvld: unable to load firmware data
[   34.304277] nouveau :01:00.0: msvld: init failed, -19


Kubuntu 18.04 LTS - Works

Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install and after updates applied through Discover
application.



KDE neon User Edition 5.13 - Works
16.04

Kernel v4.13.0-45 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install.

Works after fresh install and after updates applied through Discover
application.

Installed nVidia driver v384.130 (nvidia-384) and still working.



Lubuntu - 18.04 LTS – Works

Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install and after updates applied through Software
Updater application.

Installed nVidia driver v390 (nvidia-driver-390) and still working.


 
Mate 18.04 LTS - Broken

Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install but not after updates applied through Software
Update.

"Could not update ICEauthority file /home/user/.ICEauthority" appears
during auto login. Desktop does not finishing loading but keyboard
shortcuts work.



Elementary OS 0.4.1 Loki – Works

Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install.

Works after fresh install and after updates applied through AppCenter.

Installed kernel v4.17.0 and v4.17.3 and still works. But did receive
this warning when upgrading the kernel.

W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module 
i915
W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_method_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_bundle_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_nonctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_ctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_inst.bin for 
module nouveau
W: Possible missing firmware 

[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method

[Julian Andres Klode]

This update causes a regression that is tracked in bug 1780099 - notably
the __hash__ of an apt.Package can change after opening, so if used in a
set, or as a dict key, the package won't be found anymore. The
regression is less worse than the previous state, but will be fixed
shortly.

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

Title:
  Object of different cache passed as argument to apt_pkg.DepCache
  method

Status in python-apt package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Won't Fix
Status in python-apt source package in Bionic:
  Fix Released
Status in update-manager source package in Bionic:
  Won't Fix
Status in python-apt source package in Cosmic:
  Fix Released
Status in update-manager source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]
  python-apt 1.6 raises an exception when objects of an old cache are passed to 
a apt_pkg.DepCache methods for a different cache. Prior to that, those would 
either segfault, succeed, or silently operate on a different object, as they 
use package/version ids, and e.g. two different packages in the old and new 
cache might have the same id.

  With 1.6.1, we introduce a remapping algorithm that remaps objects of
  apt.Cache() when calling apt.Cache.open(), allowing old objects to be
  used after reopening, as long as they exist in the new cache. If they
  don't exist in the new cache, apt_pkg.CacheMismatchError will be
  raised from the apt_pkg layer.

  [Test case]
  import apt
  c=apt.Cache()
  p=c["apt"]
  c.open()
  p.mark_install()

  [Regression potential]
  Could be remapping to wrong items which would cause us to install a wrong 
version, for example. Compared to pre-bionic, bionic is a regression already, 
though, and any regression caused here is less important than
  what we have now.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1780099] [NEW] Cache remapping breaks hashing of Package objects

[Julian Andres Klode]

Public bug reported:

[Impact]
The apt.Package objects use the id as the hash, but the hash can change after 
reopening, meaning that code will fail to work, for example:

c=apt.Cache()
p=c["a"]
set_of_p={p}
c.open()
assert p in set_of_p

will fail.

[Test case]
The above test case is run as part of autopkgtest (syntax is slightly different)

[Regression potential]
Hashing packages objects will be slower as it hashes the name and architecture 
now.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-apt (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: python-apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Cache remapping breaks hashing of Package objects

Status in python-apt package in Ubuntu:
  New
Status in python-apt source package in Bionic:
  New

Bug description:
  [Impact]
  The apt.Package objects use the id as the hash, but the hash can change after 
reopening, meaning that code will fail to work, for example:

  c=apt.Cache()
  p=c["a"]
  set_of_p={p}
  c.open()
  assert p in set_of_p

  will fail.

  [Test case]
  The above test case is run as part of autopkgtest (syntax is slightly 
different)

  [Regression potential]
  Hashing packages objects will be slower as it hashes the name and 
architecture now.

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

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

[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

[Andrea Azzarone]

Yeah this should be SRUed to bionic.

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

[Sebastien Bacher]

Uploaded to cosmic, do we think that's worth SRUing to bionic?

** Package changed: gnome-online-accounts (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

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

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

[Touch-packages] [Bug 1396787] Re: checking trust of archives eats a lot of cpu

[Francis Ginther]

** Tags added: id-5acfd3863b9f75d6e6f2a6df

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

Title:
  checking trust of archives eats a lot of cpu

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  (System: Ubuntu 14.04, up to date packages)

  I noticed that unattended-upgrades spends a significant amount of time
  in phases where it runs at 100% cpu. On a slower machine (core 2 t7200
  2GHz) this goes on for minutes rather than seconds. This interferes
  with using the machine for other tasks.

  Using the --debug option to unattended-upgrades shows that the program
  outputs a lot of lines like the following during these 100% cpu
  phases:

  matching 'a'='trusty-updates' against '

  From this output I guess the operation executed is not so complicated
  that it should require so much cpu power. ??

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Nov 26 21:53:57 2014
  InstallationDate: Installed on 2014-08-28 (90 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780080] Re: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1556439
   pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from 
pa_sink_input_finish_move() from pa_sink_move_all_finish() from 
card_set_profile() from pa_card_set_profile

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Happened during swapping "fast enough" between input sources of the
  same headset (Corsair HS40 gives Analog and Digital output).

  Also crashed the settings sound dialog. In-between crashing, the
  enumerated sources doubled.

  However:
  ```
  The problem cannot be reported:

  You have some obsolete package versions installed. Please upgrade the
  following packages and check if the problem still occurs:

  libsoup-gnome2.4-1, libsoup2.4-1
  ```

  .. apparently, because an update was given 3 days ago? :/ :@

  --

  [2018-07-04 15:11:40]:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  [2018-07-04 15:12:27]:~$ apt-cache policy pulseaudio libsoup-gnome2.4-1 
libsoup2.4-1
  pulseaudio:
Installed: 1:8.0-0ubuntu3.10
Candidate: 1:8.0-0ubuntu3.10
Version table:
   *** 1:8.0-0ubuntu3.10 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.0-0ubuntu3 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libsoup-gnome2.4-1:
Installed: 2.52.2-1ubuntu0.2
Candidate: 2.52.2-1ubuntu0.3
Version table:
   2.52.2-1ubuntu0.3 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   *** 2.52.2-1ubuntu0.2 100
  100 /var/lib/dpkg/status
   2.52.2-1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libsoup2.4-1:
Installed: 2.52.2-1ubuntu0.2
Candidate: 2.52.2-1ubuntu0.3
Version table:
   2.52.2-1ubuntu0.3 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   *** 2.52.2-1ubuntu0.2 100
  100 /var/lib/dpkg/status
   2.52.2-1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sntentos  13156 F pulseaudio
   /dev/snd/controlC0:  sntentos  13156 F pulseaudio
   /dev/snd/controlC3:  sntentos  13156 F pulseaudio
   /dev/snd/controlC2:  sntentos  13156 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul  4 14:58:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2017-09-19 (288 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release 

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Marc Deslauriers]

Oh, we don't track security updates in bugs, we track them in our
tracker.

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

No worries. I was doing the Debian update anyway and this wasn't that
much effort on top. :-)

I had clicked on the CVE link in Launchpad, which goes to
https://bugs.launchpad.net/bugs/cve/2018-12910. But I guess even if
there was a bug, it'd probably have been private security and I wouldn't
have seen it anyway.

Cheers!

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

[Alberto Milone]

I have tested the new packages here, and I can confirm that they solve
the problem.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  Triaged
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * It should be possible to change DRM driver without rebooting.
   * It should be possible to correctly suspend & resume, whilst preserving 
driver state.
   * This bug is for userspace/logind fixes, required to get above working.
   * Related kernel change is 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658
   * 
https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59

  [Test Case]

   * Test and verify that on machines with Nvidia discrete graphics, one
  can change performance/power-saving modes without rebooting.

  [Regression Potential]

   * There are changes to the fd handling that are passed to logind. At
  worst, fd to the NVIDIA driver will still be held, and thus one would
  continue to not be able to switch graphics modes without rebooting.

  [Other Info]
   
   * original bug report:

  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

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

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

[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Timo Aaltonen]

these have been tested by the OEM team when validating the 18.04.1
prerelease image, which includes mesa & libglvnd from -proposed

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1780077] [NEW] FIFO underrun error

[Esteban Benitez]

Public bug reported:

Subunit 18.04 LTS
System will not boot.

I updated graphics drivers I think erroneously, then received the
underrun errors and created a swap partition by accident following a fix
for a similar error as was having trouble booting crypt.  I commented
out the swap and turned off swap and have updated my drivers and purged
previous.  I can access terminal, yet still cannot boot due to the
undercut.  I think I need to create a .conf file for the graphics
drivers.

CPU pipe B FIFO underrun

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Wed Jul  4 03:45:23 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
   Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3048]
InstallationDate: Installed on 2018-01-25 (160 days ago)
InstallationMedia: It
MachineType: LENOVO 7220RY8
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/it--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5CKT77AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.asset.tag: 
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7220RY8:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.family: NONE
dmi.product.name: 7220RY8
dmi.product.version: ThinkCentre M58p
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.92+git1806210630.7164ab~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1807040730.45f9d5~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1807040730.45f9d5~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Wed Jul  4 03:33:45 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1780077

Title:
  FIFO underrun error

Status in xorg package in Ubuntu:
  New

Bug description:
  Subunit 18.04 LTS
  System will not boot.

  I updated graphics drivers I think erroneously, then received the
  underrun errors and created a swap partition by accident following a
  fix for a similar error as was having trouble booting crypt.  I
  commented out the swap and turned off swap and have updated my drivers
  and purged previous.  I can access terminal, yet still cannot boot due
  to the undercut.  I think I need to create a .conf file for the
  graphics drivers.

  CPU pipe B FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Jul  4 03:45:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
 Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:3048]
  InstallationDate: Installed on 2018-01-25 (160 days ago)
  InstallationMedia: It
  MachineType: LENOVO 7220RY8
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Marc Deslauriers]

Sorry about that.

You can look up the CVE in our tracker, and see if someone is in the
Assigned-to section:

https://people.canonical.com/~ubuntu-
security/cve/2018/CVE-2018-12910.html

For a security update, it's probably best to just ask us.

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Hua Zhang]

I simply add a non-empty value into crash file then I can bypass this
issue.

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

-- 
Mailing list: https://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 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Robie Basak]

On Wed, Jul 04, 2018 at 01:21:35AM -, John Gallagher wrote:
> > I'm not particularly familiar with this part of initramfs-tools, but
> it seems to me that essentials like the loading of the virtio_pci module
> would be short-circuited by your patch.
> 
> Yes, you're right, thanks for pointing that out. If the driver isn't
> built-in to the kernel, it would be omitted. I think what we need to do
> here is get a list of the devices that make up the root pool, probably
> from the output of `zpool list -vPL`, and then call 'block_dev_mod_add'
> on each device. I'll work on updating the patch.

That sounds like it might be the right approach, but I'm not sure. I'm a
bit confused as to exactly why update-initramfs fails here due to the
way it is being called - see below.

> > I was just pointed to
> https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS and told
> that ZFS filesystems aren't expected to be in /etc/fstab according to
> those instructions. Is this correct? I haven't checked but it seems that
> initramfs-tools wouldn't then fail under these conditions.
> 
> It's true that we don't have the filesystems listed in /etc/fstab. Can
> you elaborate on how you anticipate that would affect building the
> initramfs?

Ah - that won't be the issue then. I was suggesting that if you had the
filesystems in /etc/fstab, then that might be the cause of your problem.
It sounds like that isn't the case then.

> > Does this apply and work correctly on the current Ubuntu development 
> > release (Cosmic) please? We land changes there first and only once 
> > successful consider backporting to existing releases as appropriate.
> Is it possible to upgrade my machine to the development release? If not, I 
> might be able to modify our build process to build an Cosmic image that uses 
> zfs on root.

I suggest that you test using VMs, and initially use development release
images rather than upgrading up to it. But yes, you can upgrade using
do-release-upgrade(8) (in steps, with '-d' for the final step).


It looks like kdump-tools might be causing the issue here, rather than
this being (directly, at least) being a problem in initramfs-tools.
kdump-tools drops in a kernel postinst.d/ script. This script calls
mkinitramfs but with a modified MODULES=dep configuration option:
https://git.launchpad.net/ubuntu/+source/makedumpfile/tree/debian/kernel-postinst-generate-initrd?h=applied/ubuntu/devel

It might be easier to resolve this by considering this as "mkinitramfs
fails on ZFS root without /etc/fstab lines for the ZFS filesystems when
MODULES=dep is used". If that's accurate (I haven't tested).

Could you perhaps see if you can remove kdump-tools from the equation
like this?

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type 

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

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

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

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  New
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[axel]

I created this file with the above mentioned content but it doesn't work
for me. I still get error messages:

ntpdate[954]: name server cannot be used: Temporary failure in name resolution 
(-3)
cze 29 16:34:21 NetworkManager[879]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

[Sebastien Bacher]

Uploaded, it can stay in proposed while the MIR is being sorted out

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Sebastien Bacher]

SRU upload to the bionic queue now

** Also affects: bluez (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: bluez (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: bluez (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

How could I have seen that so I didn't waste my time preparing debdiffs?
Or is it just "ask"?

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1770839] Re: Syncevolution does not run in Ubuntu 18.04

[Bug Watch Updater]

** Changed in: syncevolution (Debian)
   Status: Unknown => Fix Released

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

Title:
  Syncevolution does not run in Ubuntu 18.04

Status in syncevolution package in Ubuntu:
  Confirmed
Status in syncevolution package in Debian:
  Fix Released

Bug description:
  There is a problem with the package syncevolution (1.5.3-1ubuntu2) in
  Ubuntu 18.04 :

  Step to reproduce:
  >$ sudo apt install syncevolution

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les paquets supplémentaires suivants seront installés : 
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution-common syncevolution-libs syncevolution-libs-gnome
  Les NOUVEAUX paquets suivants seront installés :
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome
  0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 2'230 ko dans les archives.
  Après cette opération, 10.2 Mo d'espace disque supplémentaires seront 
utilisés.
  Souhaitez-vous continuer ? [O/n] O
  [...]
  Paramétrage de syncevolution (1.5.3-1ubuntu2) ...
  [...]

  > $ syncevolution --version
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-peers
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-config
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  Please note that this bug semms corrected in a new release of syncevolution :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043

  Would it be possible to have the corrected verion in Ubuntu 18.04 ?

  Thanks in advance for your help

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

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

[Touch-packages] [Bug 1770839] Re: Syncevolution does not run in Ubuntu 18.04

[Hans Joachim Desserud]

** Bug watch added: Debian Bug tracker #887043
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043

** Also affects: syncevolution (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043
   Importance: Unknown
   Status: Unknown

** Tags added: bionic

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

Title:
  Syncevolution does not run in Ubuntu 18.04

Status in syncevolution package in Ubuntu:
  Confirmed
Status in syncevolution package in Debian:
  Unknown

Bug description:
  There is a problem with the package syncevolution (1.5.3-1ubuntu2) in
  Ubuntu 18.04 :

  Step to reproduce:
  >$ sudo apt install syncevolution

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les paquets supplémentaires suivants seront installés : 
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution-common syncevolution-libs syncevolution-libs-gnome
  Les NOUVEAUX paquets suivants seront installés :
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome
  0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 2'230 ko dans les archives.
  Après cette opération, 10.2 Mo d'espace disque supplémentaires seront 
utilisés.
  Souhaitez-vous continuer ? [O/n] O
  [...]
  Paramétrage de syncevolution (1.5.3-1ubuntu2) ...
  [...]

  > $ syncevolution --version
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-peers
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-config
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  Please note that this bug semms corrected in a new release of syncevolution :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043

  Would it be possible to have the corrected verion in Ubuntu 18.04 ?

  Thanks in advance for your help

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

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

[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Hua Zhang]

I run into the same problem in trusty, any workaround to bypass it ?

$ sudo apport-unpack 
_usr_lib_erlang_erts-5.10.4_bin_beam.smp.108.27June2018.crash ./core
Traceback (most recent call last): 
File "/usr/bin/apport-unpack", line 74, in  
pr.extract_keys(f, bin_keys, dir) 
File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in 
extract_keys 
[item for item, element in b64_block.items() if element is False]) 
ValueError: ['UserGroups'] has no binary content

Then this code dump can not be used because ./core/CoreDump is truncated: 
expected core file size >= 20734648320, found: 5708352522.
Cannot access memory at address 0x7fe8f266e1a8
Cannot access memory at address 0x7fe8f266e1a0
(gdb) bt
Python Exception  Cannot access memory at address 
0x7fe8eb9bd738: 
#0  0x7fe8f1345c37 in ?? ()
Cannot access memory at address 0x7fe8eb9bd738

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

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

[Touch-packages] [Bug 1780020] Re: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Running apt -V dist-upgrade suddenly failed and printed:

  W: APT had planned for dpkg to do more than it reported back (22 vs
  26). Affected packages: linux-image-4.15.0-24-generic:amd64

  I do not know what happened; I tried to run apt -V dist-upgrade one
  more time; this time it succeeded. Then I tried dpkg --configure -a
  which printed nothing so I assume everything went okay.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2348 F pulseaudio
mavi   2995 F pulseaudio
  Date: Wed Jul  4 08:52:33 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
  InstallationDate: Installed on 2016-09-05 (666 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EN0005MS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.02-2ubuntu8
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to bionic on 2018-03-13 (112 days ago)
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0005MS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN0005MS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1780020] [NEW] package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Martin Vysny]

Public bug reported:

Running apt -V dist-upgrade suddenly failed and printed:

W: APT had planned for dpkg to do more than it reported back (22 vs 26).
Affected packages: linux-image-4.15.0-24-generic:amd64

I do not know what happened; I tried to run apt -V dist-upgrade one more
time; this time it succeeded. Then I tried dpkg --configure -a which
printed nothing so I assume everything went okay.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2348 F pulseaudio
  mavi   2995 F pulseaudio
Date: Wed Jul  4 08:52:33 2018
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
InstallationDate: Installed on 2016-09-05 (666 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. 
 Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20EN0005MS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: grub-pc 2.02-2ubuntu8
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to bionic on 2018-03-13 (112 days ago)
dmi.bios.date: 03/28/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET77W (1.50 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EN0005MS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EN0005MS
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Running apt -V dist-upgrade suddenly failed and printed:

  W: APT had planned for dpkg to do more than it reported back (22 vs
  26). Affected packages: linux-image-4.15.0-24-generic:amd64

  I do not know what happened; I tried to run apt -V dist-upgrade one
  more time; this time it succeeded. Then I tried dpkg --configure -a
  which printed nothing so I assume everything went okay.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2348 F pulseaudio
mavi   2995 F pulseaudio
  Date: Wed Jul  4 08:52:33 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
  InstallationDate: Installed on 2016-09-05 (666 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EN0005MS
  ProcFB: 0 inteldrmfb