[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

After running "rfkill unblock 3" please then run:

  rfkill list

and send us the output.

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

** Changed in: gnome-bluetooth (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/1782893

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

Thanks. It appears you have a Qualcomm/Atheros Bluetooth adapter
connected internally via USB.

The kernel has apparently found the adapter and loaded firmware for it.
However the kernel also has it set to disabled:

0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes   <-
Hard blocked: no

In a terminal please try running:  rfkill unblock 3
Does that fix the problem?

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

Also, does the problem only occur after suspend/resume? Does it work on
a fresh reboot?

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1783076] [NEW] package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Yaroslav]

Public bug reported:

after trying to update packages (just after a fresh ubuntu 18.04
persistent install on usb 8GB) i got this error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jul 23 10:19:25 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-04-24 (89 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
PackageArchitecture: all
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.3
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-06-22 (30 days ago)

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  after trying to update packages (just after a fresh ubuntu 18.04
  persistent install on usb 8GB) i got this error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 23 10:19:25 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-24 (89 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  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.3
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-06-22 (30 days ago)

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Ákos Maróy]

$ rfkill unblock 3
$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


but the result is the same. I open the settings panel, go to the Bluetooth tab, 
try to turn it on, the switch shows 'ON', but nothing changes. going away from 
this tab and back will show the switch 'OFF'

is there a command line tool I can turn on & off?

yes, this is the effect on clean boot as well, not just after a reboot

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1783076] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[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/1783076

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  after trying to update packages (just after a fresh ubuntu 18.04
  persistent install on usb 8GB) i got this error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 23 10:19:25 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-24 (89 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  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.3
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-06-22 (30 days ago)

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Ákos Maróy]

output after a clean boot:

$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ rfkill unblock 1
$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


the effect with the settings panel is the same

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

"rfkill" is the command line tool and it is now enabled:

1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

So if it's still not working for you then that sounds like a GUI bug, or
a subtle driver/firmware bug.

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

Next, please try running "bluetoothctl" and then:

 list
 power on
 scan on

what output do you see?

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1717474] Re: Multi monitor config issues

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726538
   Dual monitor configuration not saved across logout / login
** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  Multi monitor config issues

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Since wayland will be the default with 17.10 it might be important to
  have it ready for multiple monitor support. I have the latest updates
  installed and I am on the artful channel.

  SETUP:
  HiDPI internal screen running at 2160x1440 (Surface Pro 3)
  External FullHD HDMI monitor running  at 1920x1080
  Since the upgrade to the latest GNOME 3.26, wayland got activated again. I 
was running X before. 
  Usually, I set my internal screen off and only work with the external monitor 
if plugged in.

  ISSUE:
  With wayland active for both GDM and GNOME there is actually two issues:

  1. I am able to configure my desired settings in the display settings
  as usual (=turn off internal screen and use only external monitor).
  But since the latest update this setting is not remembered after a new
  login. It can only remember the "mirror" or "join displays" options
  but not the "single display" option. Very annoying to reconfigure this
  after every login.

  Before the update to the new GNOME settings look I was at least able
  to have this setting remembered (even with wayland). However, even
  back then it was not perfect since the internal screen was not
  completely turned off (black but with light on). After manually
  setting the displays again the screen was turned off but not after a
  login. This is a wayland related issue since it is not reproducable
  with X.

  2. GDM is always on the internal screen and simply does not match and
  respect your GNOME config. I tried several ways to configure this:

  sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config - does not work
  since wayland ignores this config file.

  I tried to using shell scripts executed at startup with xrandr. But
  xrandr does not work with wayland, too. So this is also not a
  solution.

  
  FIX:
  I don't know how to configure GDM with wayland. I am willing to test things 
out but have no further ideas and am relatively new to Linux/Ubuntu. Thanks for 
any help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 10:57:43 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics 
Controller [1414:0005]
  InstallationDate: Installed on 2017-08-24 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170823)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=f348de47-cb83-4d73-8de3-bdd738092165 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2150
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2150:bd04/26/2017:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-vi

Re: [Touch-packages] [Bug 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

Its already installed on my computer...


On Monday 23 July 2018 07:43 AM, Daniel van Vugt wrote:
> Also if you wish to send a receive files, please make sure you have
> installed:
>
>sudo apt install bluez-obexd
>
> ** 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/1769443

Title:
  Bluetooth is not working after updating my laptop to 18.04 LTS version

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 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

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Ákos Maróy]

interestingly, bluez was not yet installed. after installing, I see:

$ bluetoothctl
[NEW] Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
Agent registered
[bluetooth]# list
Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 9C:B6:D0:FE:37:CA Discovering: yes
[NEW] Device 48:22:B7:D2:B1:52 48-22-B7-D2-B1-52
[NEW] Device 6A:D9:FF:E8:DF:F9 6A-D9-FF-E8-DF-F9
[NEW] Device 44:CA:BD:00:6B:53 44-CA-BD-00-6B-53
[NEW] Device 4A:75:85:93:D4:F6 4A-75-85-93-D4-F6
...


and then it also shows devices on the Bluetooth tab in Settings. so this is 
great progress.


but not all is right. if I pair it with for example a Bluetooth headset, it 
seems to pair, the it's 'Connected' for a second, and then it won't ever 
connect.

this is the log:


[CHG] Device 70:26:05:87:EC:01 TxPower: 4
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Class: 0x00240404
[CHG] Device 70:26:05:87:EC:01 Icon: audio-card
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0105
[CHG] Device 70:26:05:87:EC:01 UUIDs: 111e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1108--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110d--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1131--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110f--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 48:22:B7:D2:B1:52 RSSI: -68
[CHG] Device 48:22:B7:D2:B1:52 ManufacturerData Key: 0x004c
[CHG] Device 48:22:B7:D2:B1:52 ManufacturerData Value:
  10 02 07 00  
[CHG] Device 7C:58:67:01:4A:D2 RSSI: -75
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Key: 0x004c
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Value:
  0c 0e 08 6b c0 31 b0 2f e1 f1 ca 34 92 c6 17 b5  ...k.1./...4
[CHG] Device 48:22:B7:D2:B1:52 RSSI: -60
[CHG] Device 6A:D9:FF:E8:DF:F9 RSSI: -60
[CHG] Device 70:26:05:87:EC:01 TxPower: -13
[CHG] Device 70:26:05:87:EC:01 Name: LE_WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: LE_WH-1000XM2
[CHG] Device 44:CA:BD:00:6B:53 RSSI: -76
[CHG] Device 70:26:05:87:EC:01 RSSI: -56
[CHG] Device 70:26:05:87:EC:01 TxPower: 4
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0201
[CHG] Device 70:26:05:87:EC:01 UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1108--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 111e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 7b265b0e-2232-4d45-bef4-bb8ae62f813d
[CHG] Device 70:26:05:87:EC:01 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 70:26:05:87:EC:01 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device 70:26:05:87:EC:01 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device 70:26:05:87:EC:01 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: yes
[CHG] Device 70:26:05:87:EC:01 Paired: yes
[CHG] Device 70:26:05:87:EC:01 Trusted: yes
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: no
[CHG] Device 70:26:05:87:EC:01 Connected: no

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Ákos Maróy]

doing the pairing from bluetoothctl gets the same result:

# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Modalias: usb:v054Cp0C67d0201
[CHG] Device 70:26:05:87:EC:01 UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1108--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 111e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 7b265b0e-2232-4d45-bef4-bb8ae62f813d
[CHG] Device 70:26:05:87:EC:01 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 70:26:05:87:EC:01 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device 70:26:05:87:EC:01 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device 70:26:05:87:EC:01 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: yes
[CHG] Device 70:26:05:87:EC:01 Paired: yes
Pairing successful
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Key: 0x004c
[CHG] Device 7C:58:67:01:4A:D2 ManufacturerData Value:
  0c 0e 08 77 c0 24 1e a5 80 d6 8e f5 7b f3 0e b6  ...w.$..{...
[CHG] Device 70:26:05:87:EC:01 RSSI: -67
[CHG] Device 70:26:05:87:EC:01 Name: LE_WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: LE_WH-1000XM2
[CHG] Device 4C:47:D2:36:C9:32 RSSI: -50
[CHG] Device 70:26:05:87:EC:01 ServicesResolved: no
[CHG] Device 70:26:05:87:EC:01 Connected: no


trying to connect manually:

# connect 70:26:05:87:EC:01
Attempting to connect to 70:26:05:87:EC:01
Failed to connect: org.bluez.Error.Failed


might it be that the Settings panel Bluetooth thing interferes with the
bluetoothctl stack?

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: In

[Touch-packages] [Bug 1779815] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From abdha...@in.ibm.com 2018-07-23 04:10 EDT---
With the given fix, installer is able to detect SAS / MD device normally with 
out screen back n forth. we can close this bug as fixed and tested.

--- Comment From abdha...@in.ibm.com 2018-07-23 04:12 EDT---
I used this link to verify the bug 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/20101020ubuntu543.1/images/netboot/ubuntu-installer/ppc64el/

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No

[Touch-packages] [Bug 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

OK. If the problem persists after updating and restarting the system
then next please try:

  1. Run: 'rfkill' and send us the output.
  2. Log into Gnome Shell. Does it work better there than in Unity?

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

Title:
  Bluetooth is not working after updating my laptop to 18.04 LTS version

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 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

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Ákos Maróy]

on a second try pairing, this is what I get:


# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[NEW] Primary Service
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0001
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0001/char0002
2a05--1000-8000-00805f9b34fb
Service Changed
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0001/char0002/desc0004
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a
69a7f243-e52f-4443-a7f9-cb4d053c74d6
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000b
be8692b1-3b29-410d-94d3-50281940553e
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000d
3f92019d-ac1d-48dc-9d94-86a0fb507591
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char000d/desc000f
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0010
5bc06a57-f84d-4086-a65a-2a238cb39cdb
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0010/desc0012
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service000a/char0013
99c3f043-8431-40e9-9802-850114e4c0d1
Vendor specific
[NEW] Primary Service
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015
fe59bfa8-7fe3-4a05-9d94-99fadc69faff
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0016
104c022e-48d6-4dd2-8737-f8ac5489c5d4
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0018
69745240-ec29-4899-a2a8-cf78fd214303
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0018/desc001a
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001b
70efdf00-4375-4a9e-912d-63522566d947
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001b/desc001d
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char001e
eea2e8a0-89f0-4985-a1e2-d91dc4a52632
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0015/char0020
a79e2bd1-d6e4-4d1e-8b4f-141d69011cbb
Vendor specific
[NEW] Primary Service
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022
91c10d9c-aaef-42bd-b6d6-8a648c19213d
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0023
99d1064e-4517-46aa-8fb4-6be64dd1a1f1
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0023/desc0025
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0026
fbe87f6c-3f1a-44b6-b577-0bac731f6e85
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0026/desc0028
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0029
420791c0-bff5-4bd1-b957-371614031136
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char0029/desc002b
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char002c
e4ef5a46-30f9-4287-a3e7-643066acb768
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0022/char002c/desc002e
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[CHG] Device 70:26:05:87:EC:01 UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 70:26:05:87:EC:01 UUIDs: 1108--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:87:EC:01 UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 70:26:05:

[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted syslog-ng-incubator into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/syslog-ng-incubator/0.3.3-2ubuntu1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: syslog-ng-incubator (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Convert triggers to noawait

Status in appstream package in Ubuntu:
  Fix Released
Status in bumblebee package in Ubuntu:
  Fix Released
Status in clutter-imcontext package in Ubuntu:
  Triaged
Status in django-countries package in Ubuntu:
  Fix Released
Status in dochelp package in Ubuntu:
  Fix Released
Status in dovecot package in Ubuntu:
  Fix Released
Status in fusiondirectory package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gosa package in Ubuntu:
  Won't Fix
Status in guile-2.0 package in Ubuntu:
  Fix Released
Status in guile-2.2 package in Ubuntu:
  Fix Released
Status in hicolor-icon-theme package in Ubuntu:
  Fix Released
Status in libomxil-bellagio package in Ubuntu:
  Triaged
Status in libreoffice package in Ubuntu:
  Fix Released
Status in ltsp package in Ubuntu:
  Fix Released
Status in mate-icon-theme package in Ubuntu:
  Fix Released
Status in maxima package in Ubuntu:
  Fix Released
Status in neurodebian package in Ubuntu:
  Fix Released
Status in nevow package in Ubuntu:
  Fix Released
Status in octave package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Fix Released
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in postgresql-common package in Ubuntu:
  Fix Released
Status in qgis package in Ubuntu:
  Fix Released
Status in reconf-inetd package in Ubuntu:
  Won't Fix
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in sphinx package in Ubuntu:
  Fix Released
Status in syslog-ng-incubator package in Ubuntu:
  Fix Released
Status in tex-common package in Ubuntu:
  Fix Released
Status in wokkel package in Ubuntu:
  Fix Released
Status in xpdf package in Ubuntu:
  Fix Released
Status in yorick package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed
Status in bumblebee source package in Xenial:
  Fix Committed
Status in clutter-imcontext source package in Xenial:
  Won't Fix
Status in django-countries source package in Xenial:
  Fix Committed
Status in dochelp source package in Xenial:
  Fix Committed
Status in dovecot source package in Xenial:
  Fix Committed
Status in fusiondirectory source package in Xenial:
  Fix Committed
Status in gdk-pixbuf source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in gosa source package in Xenial:
  Won't Fix
Status in guile-2.0 source package in Xenial:
  Fix Committed
Status in hicolor-icon-theme source package in Xenial:
  Fix Committed
Status in libomxil-bellagio source package in Xenial:
  Triaged
Status in libreoffice source package in Xenial:
  Triaged
Status in ltsp source package in Xenial:
  Fix Committed
Status in mate-icon-theme source package in Xenial:
  Fix Committed
Status in maxima source package in Xenial:
  Fix Committed
Status in neurodebian source package in Xenial:
  Fix Committed
Status in nevow source package in Xenial:
  Fix Committed
Status in octave source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Fix Committed
Status in pike7.8 source package in Xenial:
  Fix Committed
Status in pike8.0 source package in Xenial:
  Fix Committed
Status in postgresql-common source package in Xenial:
  Fix Committed
Status in qgis source package in Xenial:
  Fix Committed
Status in reconf-inetd source package in Xenial:
  Won't Fix
Status in shared-mime-info source package in Xenial:
  Fix Committed
Status in sphinx source package in Xenial:
  Fix Committed
Status in syslog-ng-incubator source 

[Touch-packages] [Bug 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

It shows following out...sorry first time it was not showing the output

welcome@HP:~$ rfkill
ID TYPE  DEVICE  SOFT  HARD
 0 wlan  phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked
welcome@HP:~$

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

Title:
  Bluetooth is not working after updating my laptop to 18.04 LTS version

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 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

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

-- 
Mailing list: https://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 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

problem is persists after updating and restarting my computer..unable to 
receive file over bluetooth.

Where to run rfkill,there is no output command on terminal, and there is 
no application found on software centre,would you please elaborate what 
is the problem is going on..

On Monday 23 July 2018 01:53 PM, Daniel van Vugt wrote:
> OK. If the problem persists after updating and restarting the system
> then next please try:
>
>1. Run: 'rfkill' and send us the output.
>2. Log into Gnome Shell. Does it work better there than in Unity?
>

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

Title:
  Bluetooth is not working after updating my laptop to 18.04 LTS version

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 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

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

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

[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15

[Daniel van Vugt]

Did it ever work at all in 18.04? Do you suppose a recent update broke
it?

Next, maybe try installing a very new kernel to see if that makes it more 
stable:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Or even try older kernels if that doesn't work.

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

Title:
  Bluetooth not working on Dell XPS 15

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.

  expected behavior:

  in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
  'ON', and then Bluetooth is enabled, and one can pair devices

  what is happening:

  in Settings, when clicking on the 'ON' button in the Bluetooth tab, it
  seems to turn on, that falls back to off

  some relevant output:

  $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetoothLinux
  Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:1535]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. 
  Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
  Bus 001 Device 005: ID 0c45:6713 Microdia 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [3.905518] Bluetooth: Core ver 2.22
  [3.905532] Bluetooth: HCI device and connection manager initialized
  [3.905534] Bluetooth: HCI socket layer initialized
  [3.905536] Bluetooth: L2CAP socket layer initialized
  [3.905539] Bluetooth: SCO socket layer initialized
  [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [3.857792] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:02:00.0.bin failed with error -2
  [3.857799] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [3.860582] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  am 5501 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582
  InstallationDate: Installed on 2017-10-23 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Christian]

On latest Ubuntu 18.04 I have an inconsistent state of ufw on reboots 
(sometimes even ssh doesn't work):
root@us-proxy1:~# uname -a
Linux us-proxy1 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
root@us-proxy1:~# dpkg -l |grep ufw
ii  ufw   0.35-5
  all  program for managing a Netfilter firewall

When I login via console, 'ufw status' looks ok, but still not all services 
work. 'systemctl status ufw is FAILED'. Restarting the Firewall solves the 
issue, but always logging into a server via console if ssh doesn't work is not 
acceptable. I will try the workaround mentioned above.
Errors always happen on COMMIT of ruleset:

root@us-proxy1:~# journalctl -u ufw.service
-- Logs begin at Thu 2018-07-19 13:09:26 UTC, end at Mon 2018-07-23 08:27:50 
UTC. --
Jul 19 13:09:27 guest systemd[1]: Started Uncomplicated firewall.
-- Reboot --
Jul 19 14:12:46 us-proxy1 ufw-init[415]: iptables-restore: line 77 failed
Jul 19 14:12:47 us-proxy1 ufw-init[415]: Problem running '/etc/ufw/before.rules'
Jul 19 14:12:47 us-proxy1 systemd[1]: ufw.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 19 14:12:47 us-proxy1 systemd[1]: ufw.service: Failed with result 
'exit-code'.
Jul 19 14:12:47 us-proxy1 systemd[1]: Failed to start Uncomplicated firewall.
-- Reboot --
Jul 19 14:54:06 us-proxy1 ufw-init[421]: iptables-restore: line 44 failed
Jul 19 14:54:07 us-proxy1 ufw-init[421]: Problem running '/etc/ufw/user.rules'
Jul 19 14:54:07 us-proxy1 systemd[1]: ufw.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 19 14:54:07 us-proxy1 systemd[1]: ufw.service: Failed with result 
'exit-code'.
Jul 19 14:54:07 us-proxy1 systemd[1]: Failed to start Uncomplicated firewall.
Jul 19 15:09:51 us-proxy1 systemd[1]: Starting Uncomplicated firewall...
Jul 19 15:09:51 us-proxy1 ufw-init[1985]: Firewall already started, use 
'force-reload'
Jul 19 15:09:51 us-proxy1 systemd[1]: Started Uncomplicated firewall.
-- Reboot --
Jul 19 15:21:17 us-proxy1 ufw-init[413]: ip6tables-restore: line 138 failed
Jul 19 15:21:17 us-proxy1 ufw-init[413]: Problem running 
'/etc/ufw/before6.rules'
Jul 19 15:21:17 us-proxy1 systemd[1]: ufw.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 19 15:21:17 us-proxy1 systemd[1]: ufw.service: Failed with result 
'exit-code'.
Jul 19 15:21:17 us-proxy1 systemd[1]: Failed to start Uncomplicated firewall.
Jul 19 15:22:29 us-proxy1 systemd[1]: Starting Uncomplicated firewall...
Jul 19 15:22:29 us-proxy1 ufw-init[1424]: Firewall already started, use 
'force-reload'

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1621759] Re: [20BX000XGE, Realtek ALC3232, Speaker, Internal] audio "sleeps", needs ~4 sec to resume, blocking UI

[brandon211]

Dear gf,
thanks for your response.
As far as I can assess that, implementing the workaround did not have 
noticeable impact on the system's battery run time.

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

Title:
  [20BX000XGE, Realtek ALC3232, Speaker, Internal] audio "sleeps", needs
  ~4 sec to resume, blocking UI

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I'm using a ThinkPad T450s with Ubuntu 16.04. This problem already
  existed when it ran 15.10.

  Regardless if the notebook is connected to AC or not, external speakers are 
connected or not, the audio output seems put to sleep somehow after ~6 seconds.
  Whenever a process tries to output audio, it needs approx. 4 seconds for the 
audio to actually come out.
  Despite this laggy behaviour, it is really annoying because most applications 
freeze during this time.

  Besides different apps of daily working are affected by this
  (Thunderbird, MPlayer, VLC, ...), this even applies to the "volume
  changing sound" when using the volume -/+ keys. In detail this means:
  if I press the volume "-" key multiple times, the volume overlay
  freezes for approx. 4 seconds and then all requested volume change
  sounds are played altogether.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.7.0-040700rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buerger2941 F pulseaudio
   /dev/snd/controlC1:  buerger2941 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  9 09:05:45 2016
  InstallationDate: Installed on 2015-09-15 (359 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [20BX000XGE, Realtek ALC3232, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (139 days ago)
  dmi.bios.date: 05/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET60WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET60WW(1.24):bd05/25/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1781652] Re: should be possible to specify static routes on a dhcp-configured interface

[Launchpad Bug Tracker]

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

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

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

Title:
  should be possible to specify static routes on a dhcp-configured
  interface

Status in netplan:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  From , a user wants to add a static route to a
  network interface where the gateway is known, but the interface's
  local address is configured via dhcp.

  This doesn't work with direct netplan yaml, because networkd will try
  to apply the static routes before the interface has been configured
  via dhcp, failing because there is not yet a route to the gateway on
  that interface.

  Demonstrating in a lxd container locally, which has 10.44.49.0/24 as
  its network:

  $ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true
  routes:
 - to: 10.44.48.0/24
   via: 10.44.49.2
   metric: 10
  $  systemctl status systemd-networkd --no-pager -l
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Fri 2018-07-13 19:21:29 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 165 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-networkd.service
 └─165 /lib/systemd/systemd-networkd

  Jul 13 19:21:29 stable-dane systemd[1]: Starting Network Service...
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: Enumeration completed
  Jul 13 19:21:29 stable-dane systemd[1]: Started Network Service.
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Could not set route: 
Network is unreachable
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: DHCPv4 address 
10.44.49.32/24 via 10.44.49.1
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: Not connected to system 
bus, not setting hostname.
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Gained IPv6LL
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Configured
  Jul 13 19:21:55 stable-dane systemd-networkd[165]: Could not set hostname: 
Method call timed out
  $ ip route 
  default via 10.44.49.1 dev eth0 proto dhcp src 10.44.49.32 metric 100 
  10.44.49.0/24 dev eth0 proto kernel scope link src 10.44.49.32 
  10.44.49.1 dev eth0 proto dhcp scope link src 10.44.49.32 metric 100 
  $

  netplan and networkd should DTRT.

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

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

[Touch-packages] [Bug 1781652] Re: should be possible to specify static routes on a dhcp-configured interface

[Daniel Axtens]

This hit me too.

I'm not sure how netplan can fix this - it looks like it's generating
pretty sensible configuration files.

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

Title:
  should be possible to specify static routes on a dhcp-configured
  interface

Status in netplan:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  From , a user wants to add a static route to a
  network interface where the gateway is known, but the interface's
  local address is configured via dhcp.

  This doesn't work with direct netplan yaml, because networkd will try
  to apply the static routes before the interface has been configured
  via dhcp, failing because there is not yet a route to the gateway on
  that interface.

  Demonstrating in a lxd container locally, which has 10.44.49.0/24 as
  its network:

  $ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true
  routes:
 - to: 10.44.48.0/24
   via: 10.44.49.2
   metric: 10
  $  systemctl status systemd-networkd --no-pager -l
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Fri 2018-07-13 19:21:29 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 165 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-networkd.service
 └─165 /lib/systemd/systemd-networkd

  Jul 13 19:21:29 stable-dane systemd[1]: Starting Network Service...
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: Enumeration completed
  Jul 13 19:21:29 stable-dane systemd[1]: Started Network Service.
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Could not set route: 
Network is unreachable
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: DHCPv4 address 
10.44.49.32/24 via 10.44.49.1
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: Not connected to system 
bus, not setting hostname.
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Gained IPv6LL
  Jul 13 19:21:29 stable-dane systemd-networkd[165]: eth0: Configured
  Jul 13 19:21:55 stable-dane systemd-networkd[165]: Could not set hostname: 
Method call timed out
  $ ip route 
  default via 10.44.49.1 dev eth0 proto dhcp src 10.44.49.32 metric 100 
  10.44.49.0/24 dev eth0 proto kernel scope link src 10.44.49.32 
  10.44.49.1 dev eth0 proto dhcp scope link src 10.44.49.32 metric 100 
  $

  netplan and networkd should DTRT.

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Christian]

I changed this:
-Before=network.target
+Before=network-pre.target
+Wants=network-pre.target

and get following:
Jul 23 09:40:53 us-proxy1 ufw-init[424]: ip6tables-restore: line 4 failed
Jul 23 09:40:53 us-proxy1 systemd[1]: ufw.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 23 09:40:53 us-proxy1 systemd[1]: ufw.service: Failed with result 
'exit-code'.
Jul 23 09:40:53 us-proxy1 systemd[1]: Failed to start Uncomplicated firewall.

When I look at /lib/ufw/ufw-init-functions:
 147 printf "*filter\n"\
148 ":INPUT DROP [0:0]\n"\
149 ":FORWARD DROP [0:0]\n"\
150 ":OUTPUT DROP [0:0]\n"\
151 "-A INPUT -i lo -j ACCEPT\n"\
152 "-A OUTPUT -o lo -j ACCEPT\n"\
153 "COMMIT\n" | ip6tables-restore || error="yes"

This might be realted to loopback interface not beeing configured ? So
ufw starts too early ?

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1746419] Re: bond parameters are not changed by 'netplan apply'

[Dimitri John Ledkov]

Netplan could delete the bond, which would then be recreated by networkd
with all parameters applied.

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

Title:
  bond parameters are not changed by 'netplan apply'

Status in netplan:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have a yaml file as follows:

  network:
  version: 2
  ethernets:
  bonddevs:
  match:
  name: ens[78]
  bonds:
  bond0:
  interfaces: [bonddevs]
  parameters:
  mode: active-backup
  mii-monitor-interval: 1
  addresses:
  - 10.10.10.1/24

  
  Say I decide that 1s is too frequent for the MII interval, and I want to 
change the interval to 2s.

  If I change that in the yaml, then run
  # netplan generate
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  In other words, the change has not been applied.

  Running netplan --debug apply prints:
  DEBUG:device bond0 operstate is up, not replugging

  So I wondered if bringing the bond down would help. It does not:
  # ip link set dev bond0 down
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  However, deleting the link works:
  # ip link del dev bond0
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 2000

  This is counter-intuitive behaviour.
  Ideally, I would like a regular netplan apply to work without deleting the 
bond.
  However, a changed to the docs to make this clear would be OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nplan 0.32~17.10.1
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 31 05:47:42 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Christian]

If I use in /lib/systemd/system/ufw.service:
-Before=network.target
+After=network.target

ufw starts without errors, so there seem to be dependencies in the
network.target, that are not allowing ufw-init-functions to complete
successfully.

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load

[Dimitri John Ledkov]

How did the nvidia package get installed? By default nvidia drivers are
not installed, and only pulled in when compatible. Does the metadata on
the package claim that it is compatible with your nvidia card - when in
fact, it is not? E.g. if you use ubuntu-desktop, and remove the package,
is it still offered by additional drivers / ubuntu-drivers?

In other words, are the Modaliases listed on the nvidia-driver-390
package match the modalias of your card?

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

Title:
  systemd-udevd busyloops when nvidia kernel module fails to load

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a machine where nvidia-367 is installed, but the driver won't attach (due 
to
  the nvidia card being older and requiring legacy drivers), systemd-udevd
  repeatedly attempts to load it anyway, causing high CPU and memory usage. I
  observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by
  top(1); restarting the service reduces resource usage momentarily, but it
  appears to be climbing back up (I suspect the number of events is growing).

  Workaround is of course installing the correct driver package, but udevd 
really
  ought not behave like this if something fails to load.

  Some journal entries for systemd-udevd.service:

  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.

  dmesg shows repeated failures for loading the nvidia module:

  [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this 
system is
 NVRM:  supported through the NVIDIA 340.xx Legacy drivers. 
Please
 NVRM:  visit http://www.nvidia.com/object/unix.html for 
more
 NVRM:  information.  The 367.57 NVIDIA driver will ignore
 NVRM:  this GPU.  Continuing probe...
  [1675406.587936] NVRM: No NVIDIA graphics adapter found!
  [1675406.588078] NVRM: NVIDIA init module failed!

  Release information:

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt policy systemd udev
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages
  udev:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Christian]

Also tested:
After=network-pre.target
Wants=network-pre.target

This works as well, so this seems to be the appropriate config ? Maybe
@marcosfrm has a typo in his recommendation ?

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1783111] [NEW] PCI/internal sound card not detected

[MARYA RAJ]

Public bug reported:

No sound detected

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Jul 23 16:28:01 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-08-29 (328 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/23/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.0
dmi.board.name: 0N5RYC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd06/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0N5RYC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 15-3568
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound detected

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jul 23 16:28:01 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-08-29 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0N5RYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd06/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0N5RYC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1621759] Re: [20BX000XGE, Realtek ALC3232, Speaker, Internal] audio "sleeps", needs ~4 sec to resume, blocking UI

[gf]

Thanks for the update, Brandon. I will close the report now.
Have a great day!
:)
G


Closed per reporter’s feedback.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [20BX000XGE, Realtek ALC3232, Speaker, Internal] audio "sleeps", needs
  ~4 sec to resume, blocking UI

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I'm using a ThinkPad T450s with Ubuntu 16.04. This problem already
  existed when it ran 15.10.

  Regardless if the notebook is connected to AC or not, external speakers are 
connected or not, the audio output seems put to sleep somehow after ~6 seconds.
  Whenever a process tries to output audio, it needs approx. 4 seconds for the 
audio to actually come out.
  Despite this laggy behaviour, it is really annoying because most applications 
freeze during this time.

  Besides different apps of daily working are affected by this
  (Thunderbird, MPlayer, VLC, ...), this even applies to the "volume
  changing sound" when using the volume -/+ keys. In detail this means:
  if I press the volume "-" key multiple times, the volume overlay
  freezes for approx. 4 seconds and then all requested volume change
  sounds are played altogether.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.7.0-040700rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buerger2941 F pulseaudio
   /dev/snd/controlC1:  buerger2941 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  9 09:05:45 2016
  InstallationDate: Installed on 2015-09-15 (359 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [20BX000XGE, Realtek ALC3232, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (139 days ago)
  dmi.bios.date: 05/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET60WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET60WW(1.24):bd05/25/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1778844] woo_kdump_nvmedisk_console logs

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-07-23 07:12 
EDT---


Attached woo normal boot logs & kdump console logs with modules=dep

** Attachment added: "woo_kdump_nvmedisk_console logs"
   
https://bugs.launchpad.net/bugs/1778844/+attachment/5166656/+files/woo_kdump_nvmedisk_consolelogs.txt

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Incomplete
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 

[Touch-packages] [Bug 1778844] dmesg logs_initramfs state_woo

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-07-23 07:13 
EDT---


Attached dmesg logs from initramfs state from woo

** Attachment added: "dmesg logs_initramfs state_woo"
   
https://bugs.launchpad.net/bugs/1778844/+attachment/5166657/+files/woo_initramfstate_dmeslogs.txt

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Incomplete
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Christian]

Sorry after some more reboots the problem persists with:
After=network-pre.target
Wants=network-pre.target

So only working setup for me at the moment is:
After=network.target

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1778844] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hbath...@in.ibm.com 2018-07-23 07:30 EDT---
Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file
whne MODULES=dep is used. Also, sosreport?

(In reply to comment #26)
> Created attachment 128855 [details]
> woo_kdump_nvmedisk_console logs

btw, looks like PHB initialization is failing. So, whether nvme driver
is present or not in the initrd is secondary here, the device initialization
itself could be at fault. What is the f/w level. Is it latest?

Thanks
Hari

--- Comment From hbath...@in.ibm.com 2018-07-23 07:35 EDT---
(In reply to comment #28)
> Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file
> whne MODULES=dep is used. Also, sosreport?
>
> (In reply to comment #26)
> > Created attachment 128855 [details]
> > woo_kdump_nvmedisk_console logs
>
> btw, looks like PHB initialization is failing. So, whether nvme driver
> is present or not in the initrd is secondary here, the device initialization
> itself could be at fault. What is the f/w level. Is it latest?

also, the initial console log is different from this.. Was the f/w on the system
updated as well..

Thanks
Hari

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Incomplete
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   7

[Touch-packages] [Bug 1778844] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From indira.pr...@in.ibm.com 2018-07-23 08:14 EDT---
Also both logs were placed in

banner@9.3.117.11 (don2rry) : /home/banner

banner@banner:~> ls -l sosreport-woo-20180723065534.tar.xz
-rw--- 1 banner banner 7171548 Jul 23 07:05 
sosreport-woo-20180723065534.tar.xz
banner@banner:~> ls -l initrd.img
-rw-r--r-- 1 banner banner 24119847 Jul 23 07:04 initrd.img
banner@banner:~>

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 

[Touch-packages] [Bug 1778844] /tmp/initrd.img file

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-07-23 08:11 
EDT---


Attached /tmpinitrd.imng file

** Attachment added: "/tmp/initrd.img file"
   https://bugs.launchpad.net/bugs/1778844/+attachment/519/+files/initrd.img

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058

[Touch-packages] [Bug 1778844] sosreport_moduels=set

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-07-23 08:12 
EDT---


Attached sosreport when MODULES=set used

** Attachment added: "sosreport_moduels=set"
   
https://bugs.launchpad.net/bugs/1778844/+attachment/5166670/+files/sosreport-woo-20180723065534.tar.xz

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f7

[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Triaged

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002

[Touch-packages] [Bug 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

Problem is still going on Gnome shell desktop as well..it always shows
connection unsuccessful on other device whenever I have tried to receive
something from other device to my laptop..My computer is already up to
date ,it shows following output when i ran rfkill on a terminal


welcome@HP:~$ rfkill
ID TYPE  DEVICE  SOFT  HARD
 0 wlan  phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked
welcome@HP:~$

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

Title:
  Bluetooth is not working after updating my laptop to 18.04 LTS version

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 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

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Matt Caswell]

I just tried:
After=network.target

After 5 reboot tests I got mixed results:
The first two reboots failed to start networking at all and ufw reported its 
status as "inactive" immediately after boot.
The next two reboots networking started successfully, and ufw reported as 
active.
The final reboot, networking again did not start and ufw status was "inactive"

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1780196] Re: Timed out Availability of block devices service

[Andras Tim]

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

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

Title:
  Timed out Availability of block devices service

Status in lvm2 package in Ubuntu:
  New
Status in mdadm package in Ubuntu:
  New

Bug description:
  On a fresh Ubuntu 18.04 (64 bit) Server install, the blk-
  availability.service always killed by timeout at shutdown.

  I think the dependency of this service is bad, but I don't know what
  would be the good shutdown order for this.

  An almost same config has been worked on Xenial...

  The disk sub-system is
* NVMe SSD
  * EFI partition
  * boot partition
  * LVM phisical volume
  * root logical volume
  * swap logical volume
  * data logical volume
* 2 pcs. HDDs in RAID1 (but the md0 is not used yet)

  
  ##
  # Versions
  #

  # Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04

  # Kernel
  Linux server 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # LVM
  lvm2 2.02.176-4.1ubuntu3

  
  ##
  # Journal
  #
  systemd[1]: Stopped Load/Save Random Seed.
  systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
  systemd[1]: Stopped Network Time Synchronization.
  kernel: usb 1-13: USB disconnect, device number 2
  systemd[1]: blk-availability.service: Stopping timed out. Terminating.
  systemd[1]: blk-availability.service: Control process exited, code=killed 
status=15
  blkdeactivate[2447]:   [MD]: deactivating raid1 device md0... resync action 
in progress...
  systemd[1]: blk-availability.service: Failed with result 'timeout'.
  systemd[1]: Stopped Availability of block devices.
  systemd[1]: Stopping iSCSI initiator daemon (iscsid)...
  iscsid[951]: iscsid shutting down.
  systemd[1]: Stopped iSCSI initiator daemon (iscsid).
  systemd[1]: Stopped target Network is Online.
  systemd[1]: Stopped Wait for Network to be Configured.
  systemd[1]: Stopped target Network.
  systemd[1]: Stopping Network Name Resolution...
  systemd[1]: Stopped Network Name Resolution.
  systemd[1]: Stopping Network Service...
  systemd[1]: Stopped Create Volatile Files and Directories.
  systemd[1]: Stopped target Local File Systems.
  systemd[1]: Unmounting /boot/efi...
  systemd[1]: Unmounting /run/user/1000...
  systemd[1]: Unmounted /run/user/1000.
  systemd[1]: Stopped target Swap.
  systemd[1]: Deactivating swap 
/dev/disk/by-uuid/8a3d99d0-683e---9765162cc070...
  systemd[1]: Unmounted /boot/efi.
  systemd[1]: Unmounting /boot...
  systemd[1]: Stopped File System Check on /dev/disk/by-uuid/AB9E-5A2C.
  systemd[1]: Deactivated swap /dev/xxx_server_ssd/swap.
  systemd[1]: Deactivated swap 
/dev/disk/by-uuid/8a3d99d0-683e---9765162cc070.
  systemd[1]: Deactivated swap 
/dev/disk/by-id/dm-uuid-LVM-eatHKVdbDuw5L5RXXX2yJn7QosUWvV2IIApCOG73Bc2CbrUabBC6L3dh0N2D.
  systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-xxx_server_ssd-swap.
  systemd[1]: Deactivated swap /dev/dm-1.
  systemd[1]: Stopped Network Service.
  systemd[1]: Deactivated swap /dev/mapper/xxx_server_ssd-swap.
  systemd[1]: Unmounted /boot.
  systemd[1]: Stopped File System Check on 
/dev/disk/by-uuid/d7cc70cc-0f33---cc21d3ed1232.
  systemd[1]: Removed slice system-systemd\x2dfsck.slice.
  systemd[1]: Stopped target Local File Systems (Pre).
  systemd[1]: Stopped Remount Root and Kernel File Systems.
  systemd[1]: Stopped Create Static Device Nodes in /dev.
  systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using 
dmeventd or progress polling...
  systemd[1]: Stopped target Network (Pre).
  systemd[1]: Stopped Apply Kernel Variables.
  systemd[1]: Stopped Load Kernel Modules.
  systemd[1]: Reached target Shutdown.
  systemd[1]: Reached target Unmount All Filesystems.
  systemd[1]: Reached target Final Step.
  systemd[1]: Starting Power-Off...

  
  ##
  # systemctl cat blk-availability.service
  #
  # /lib/systemd/system/blk-availability.service
  [Unit]
  Description=Availability of block devices
  After=lvm2-activation.service lvm2-lvmetad.service iscsi-shutdown.service 
iscsi.service iscsid.service fcoe.service
  DefaultDependencies=no
  Conflicts=shutdown.target

  [Service]
  Type=oneshot
  ExecStart=/bin/true
  ExecStop=/sbin/blkdeactivate -u -l wholevg -m disablequeueing -r wait
  RemainAfterExit=yes

  [Install]
  WantedBy=sysinit.target

  
  ##
  # Other
  #
  I tried to ask help on 
https://askubuntu.com/questions/1051856/timed-out-availability-of-block-devices,
 but I haven't got any response.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jul  5 09:24:01 2018
  

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no mi

[Touch-packages] [Bug 1783138] [NEW] hinic interfaces aren't getting predictable names

[dann frazier]

Public bug reported:

On a HiSilicon D06 system we noticed that interfaces provided by a plug-
in "HINIC" network card are not getting assigned predictable names.
We're getting "ethX" names instead of the expected "enPblah" names.

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

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

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

Title:
  hinic interfaces aren't getting predictable names

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

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0

[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Frank Heimes]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] GPR28

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Manoj Iyer]

abdhalee, Looks like you have successfully verified, could you please
change the tag to verification-done-bionic ?

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu 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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[bugproxy]

** Tags removed: targetmilestone-inin--- verification-needed 
verification-needed-bionic
** Tags added: targetmilestone-inin1804 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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-m

[Touch-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined

[LocutusOfBorg]

this seems to be the reason for libunistring and libidn failures

** Changed in: gcc-defaults (Ubuntu)
   Status: New => Confirmed

** Changed in: gcc-defaults (Ubuntu)
   Importance: Undecided => High

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

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

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

Title:
  "#pragma weak" symbol is 0 even when defined

Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in libidn package in Ubuntu:
  New
Status in libunistring package in Ubuntu:
  New

Bug description:
  This compiler bug is making the gnulib tests dump core; see:

  http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html

  Compile and run the following program t.c with the shell commands "gcc
  u.c -lm; ./a.out; echo $?"

  #include 
  #pragma weak tgamma

  int
  main (void)
  {
if (!tgamma)
  return 2;
if (tgamma (1) == 1)
  return 0;
return 1;
  }

  The program will exit with status 2.  It should exit with status 0,
  because the math library does have a tgamma function and the function
  pointer should be non-null.

  I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu
  4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcc 4:4.8.2-1ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 10 07:39:11 2014
  InstallationDate: Installed on 2012-12-21 (566 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gcc-defaults
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago)

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

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

[Touch-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined

[LocutusOfBorg]

https://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00061.html

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

Title:
  "#pragma weak" symbol is 0 even when defined

Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in libidn package in Ubuntu:
  New
Status in libunistring package in Ubuntu:
  New

Bug description:
  This compiler bug is making the gnulib tests dump core; see:

  http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html

  Compile and run the following program t.c with the shell commands "gcc
  u.c -lm; ./a.out; echo $?"

  #include 
  #pragma weak tgamma

  int
  main (void)
  {
if (!tgamma)
  return 2;
if (tgamma (1) == 1)
  return 0;
return 1;
  }

  The program will exit with status 2.  It should exit with status 0,
  because the math library does have a tgamma function and the function
  pointer should be non-null.

  I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu
  4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcc 4:4.8.2-1ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 10 07:39:11 2014
  InstallationDate: Installed on 2012-12-21 (566 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gcc-defaults
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago)

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

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

0.96.24.32.4 works as described, marking as verified

** 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 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
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  When the U1 account credential expire it's not possible to disable livepatch

  * Test case
  - install/enable livepatch (from the first login wizard or 
software-properties)
  - invalidate your U1 credentials:
* open "Password and Keys"
* Search for an entry containing "ubuntusso"
* Right click and open "Properties"
* Show the password entry
* Modify the 'macaroon' field (e.g. add a 1 at the beginning of the string 
so you can easily remote it later)
  - open software-properties

  -> the livepatch status should be marked as enable but the control
  active so it's possible to disable it

  * Regression potential

  Check that the software-properties checkbox reflect the correct status
  when the account are valid and invalid

  

  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 1783157] [NEW] package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1

[Rémi Douvenot]

Public bug reported:

I also had the bug on grub-efi-amd64-signed
 https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518

Perhaps there is a link between both.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Mon Jul 23 17:43:41 2018
DpkgTerminalLog:
 Paramétrage de ntp (1:4.2.8p10+dfsg-5ubuntu7.1) ...
 Le groupe « ntp » existe déjà, sans être un groupe système. Fin de la 
procédure.
 dpkg: erreur de traitement du paquet ntp (--configure) :
  installed ntp package post-installation script subprocess returned error exit 
status 1
ErrorMessage: installed ntp package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-05-28 (56 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NtpStatus: ntpq: read: Connection refused
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=dd8086cc-9a2b-4430-b205-55feaeb96308 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=1
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.3
SourcePackage: ntp
Title: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: 
installed ntp package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade:
  installed ntp package post-installation script subprocess returned
  error exit status 1

Status in ntp package in Ubuntu:
  New

Bug description:
  I also had the bug on grub-efi-amd64-signed
   https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518

  Perhaps there is a link between both.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Jul 23 17:43:41 2018
  DpkgTerminalLog:
   Paramétrage de ntp (1:4.2.8p10+dfsg-5ubuntu7.1) ...
   Le groupe « ntp » existe déjà, sans être un groupe système. Fin de la 
procédure.
   dpkg: erreur de traitement du paquet ntp (--configure) :
installed ntp package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed ntp package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-05-28 (56 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=dd8086cc-9a2b-4430-b205-55feaeb96308 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=1
  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.3
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: 
installed ntp package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Łukasz Zemczak]

** Changed in: xorg (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Released
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing

[teo1978]

> You keep saying these random behaviors. But I am unable to 
> reproduce any of them on 18.04 & 18.10. Can you explain, how to reproduce in 
> a concise way?

If there was a reliable way of reproducing it, it wouldn't be random.

Here's what happens to me:

CASE 1:
- I mute the volume when no sound is playing
Expected behavior: the icon shouldn't go red
Observed behavior: usually the icon doesn't go red, but sometimes it does.

Then sometimes it remains red until I unmute, sometimes it goes back to
normal a few seconds later

CASE 2:
- I mute the volume
- I start playing a sound (e.g. a youtube video or whatever), or some sound 
starts playing (e.g. a Facebook notification in a browser's tab).

Expected behavior: according to you, the icon should become red and remain so 
until you manually unmute the volume. That's nonsense. What's the logic behind 
that? Why would I need a reminder that at some point a sound played? Why is a 
"specific user action required"? Why should I unmute the volume after the sound 
has already stopped playing?
To me, the expected behavior is that the icon should become red and only remain 
so while some sound is playing, and then go back to normal. It's useful to know 
when some sound IS playing and I am not hearing it because my volume is muted. 
When no sound is no longer playing, there's no use in knowing that at some 
point there had been a sound playing.

But whatever the expected behavior is, the observed behavior is that
sometimes the icon goes back to normal after the sound stops playing
without any action on my part, while sometimes it remains red until I
unmute the volume.


> But I am unable to reproduce any of them on 18.04 & 18.10

I don't know, maybe it's fixed on those versions. I'm using 16.04

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

Title:
  Muted Sound Indicator randomly remains red when no sound is playing

Status in indicator-sound package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Mute the main Ubuntu volume
  2. Play some short sound

  
  Expected behavior:
  Obviously you won't hear the sound. While the sound plays, the indicator 
should become red; then, when the sound is done playing and nothing else is 
playing, either immediately or after a very short period (e.g. a couple of 
seconds), the indicator should go back to its normal color.

  Observed behavior:
  Sometimes it behaves as expected, but sometimes it will remain red forever, 
until you unmute it.

  It's utterly random.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 13 17:09:25 2017
  InstallationDate: Installed on 2013-10-11 (1523 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log:
   (process:2339): indicator-sound-WARNING **: 
accounts-service-access.vala:218: unable to sync volume 0,608643 to 
AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such 
interface 'com.ubuntu.AccountsService.Sound'
   
   (process:2339): indicator-sound-WARNING **: 
accounts-service-access.vala:218: unable to sync volume 0,848633 to 
AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such 
interface 'com.ubuntu.AccountsService.Sound'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions

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

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Adam Conrad]

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: livecd-rootfs (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Fix Released
Status in snapd:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Bionic:
  New
Status in ubuntu-meta source package in Bionic:
  New

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/livecd-rootfs/bionic-proposed

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Fix Released
Status in snapd:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Bionic:
  New
Status in ubuntu-meta source package in Bionic:
  New

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Łukasz Zemczak]

Hello Chen-Han, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.3 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, without details of
your testing we will not be able to proceed.

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

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Status: New => Fix Committed

** 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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Fix Released
Status in snapd:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  New

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783162] [NEW] mvwin doesn't work if window is created with zero coordinates.

[Phillip Deremer]

Public bug reported:

Using the following code I cant move the window with mvwin

#include 
#include 

void quit();

int main(int argc, char** argv) {
  initscr();
  atexit(quit);
  curs_set(0);
  noecho();

  WINDOW *win = newwin(0,0,0,0); // <-- Defference
  mvwin(win,10,10);
  wresize(win,10,10);

  refresh();
  box(win,0,0);
  wrefresh(win);
  getch();

  return 0;
}

void quit() {
  endwin();
}



Changing the window start coordinates to 1,1 and it works.

#include 
#include 

void quit();

int main(int argc, char** argv) {
  initscr();
  atexit(quit);
  curs_set(0);
  noecho();

  WINDOW *win = newwin(1,1,0,0); // <-- Defference
  mvwin(win,10,10);
  wresize(win,10,10);

  refresh();
  box(win,0,0);
  wrefresh(win);
  getch();

  return 0;
}

void quit() {
  endwin();
}

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

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

Title:
  mvwin doesn't work if window is created with zero coordinates.

Status in ncurses package in Ubuntu:
  New

Bug description:
  Using the following code I cant move the window with mvwin
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(0,0,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }
  

  
  Changing the window start coordinates to 1,1 and it works.
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(1,1,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }

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

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

[Touch-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted xorg into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xorg/1:7.7+19ubuntu7.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, without details of
your testing we will not be able to proceed.

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

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviro

[Touch-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted xorg into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xorg/1:7.7+13ubuntu3.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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviro

[Touch-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted nux into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20180622.2-0ubuntu1
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted nux into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+18.04.20180622.2-0ubuntu1
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, without details of
your testing we will not be able to proceed.

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

** Changed in: nux (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

** Changed in: xorg (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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
 

[Touch-packages] [Bug 1783162] Re: mvwin doesn't work if window is created with zero coordinates.

[Phillip Deremer]

** Summary changed:

- mvwin doesn't work if window is  window is created with zero coordinates.
+ mvwin doesn't work if window is created with zero coordinates.

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

Title:
  mvwin doesn't work if window is created with zero coordinates.

Status in ncurses package in Ubuntu:
  New

Bug description:
  Using the following code I cant move the window with mvwin
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(0,0,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }
  

  
  Changing the window start coordinates to 1,1 and it works.
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(1,1,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }

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

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

[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Thadeu Lima de Souza Cascardo]

Can you run apport-collect -p linux 1778844 ?

Thank you.
Cascardo.

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [ 

[Touch-packages] [Bug 1776329] Re: apport-cli and cowbuilder fail with cert and keyring errors

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyring (Ubuntu)
   Status: New => Confirmed

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

Title:
  apport-cli and cowbuilder fail with cert and keyring errors

Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  Description: Ubuntu 18.04 LTS
  Release: 18.04
  ubuntu-keyring:  Installed: 2018.02.28
  apport:  Installed: 2.20.9-0ubuntu7.2
  cowbuilder:  Installed: 0.86

  
  On a bionic system when attempting to report what I suspect is a bug in 
ubuntu-keying I got the following error

  start capture-
  $ apport-cli ubuntu-keyring

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (1.2 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.

  *** Error: Network problem

  Cannot connect to crash database, please check your Internet
  connection.

  

  Press any key to continue...  
  end capture---

  I worked around the problem by K'eeping the report and copying it to a
  Xenial system. From there I am submitting this bug report.

  The original problem that caused me to attempt to file a bug report
  against ubuntu-keyring was an attempt to build a bionic chroot for
  package building with the following command:

  start capture-
  # DIST=bionic cowbuilder --create --distribution bionic  --components "main 
universe" --basepath /var/cache/pbuilder/base-bionic-amd64-test.cow  --mirror 
http://us.archive.ubuntu.com:80/ubuntu --debootstrapopts 
--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg
  I: Invoking pbuilder
  I: forking: pbuilder create --components 'main universe' --debootstrapopts 
--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --buildplace 
/var/cache/pbuilder/base-bionic-amd64-test.cow --mirror 
http://us.archive.ubuntu.com:80/ubuntu --distribution bionic --no-targz 
--extrapackages cowdancer
  W: /root/.pbuilderrc does not exist
  I: Running in no-targz mode
  I: Distribution is bionic.
  I: Current time: Mon Jun 11 22:44:21 UTC 2018
  I: pbuilder-time-stamp: 1528757061
  I: Building the build environment
  I: running debootstrap
  /usr/sbin/debootstrap
  I: Retrieving InRelease 
  I: Checking Release signature
  E: Release signed by unknown key (key id 3B4FE6ACC0B21F32)
  E: debootstrap failed
  E: Tail of debootstrap.log:
  gpgv: Signature made Thu Apr 26 23:38:40 2018 UTC
  gpgv:using RSA key 3B4FE6ACC0B21F32
  gpgv: Can't check signature: No public key
  E: End of debootstrap.log
  W: Aborting with an error
  E: pbuilder create failed
  I: forking: rm -rf /var/cache/pbuilder/base-bionic-amd64-test.cow
  end capture---

  On the same system the following command succeeds:

  start capture-
  DIST=xenial cowbuilder --create --distribution xenial \   
  
--components "main universe" \  
  
--basepath /var/cache/pbuilder/base-xenial-amd64.cow \  
  
--mirror http://us.archive.ubuntu.com:80/ubuntu \ 
--debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg  
  
  end capture---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-keyring 2018.02.28 [modified: 
usr/share/keyrings/ubuntu-archive-keyring.gpg]
  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
  Date: Mon Jun 11 22:51:48 2018
  Dependencies:
   
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
  SourcePackage: ubuntu-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://

[Touch-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined

[LocutusOfBorg]

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

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

Title:
  "#pragma weak" symbol is 0 even when defined

Status in binutils package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in libidn package in Ubuntu:
  New
Status in libunistring package in Ubuntu:
  New

Bug description:
  This compiler bug is making the gnulib tests dump core; see:

  http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html

  Compile and run the following program t.c with the shell commands "gcc
  u.c -lm; ./a.out; echo $?"

  #include 
  #pragma weak tgamma

  int
  main (void)
  {
if (!tgamma)
  return 2;
if (tgamma (1) == 1)
  return 0;
return 1;
  }

  The program will exit with status 2.  It should exit with status 0,
  because the math library does have a tgamma function and the function
  pointer should be non-null.

  I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu
  4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcc 4:4.8.2-1ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 10 07:39:11 2014
  InstallationDate: Installed on 2012-12-21 (566 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gcc-defaults
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago)

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

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

[Touch-packages] [Bug 1783170] Re: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

[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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1783170

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.4 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 128

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  789

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18
  Uname: Linux 4.15.0-29-lowlatency x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Jul 21 18:28:51 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
  PackageArchitecture: all
  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.3
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912

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

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

[Touch-packages] [Bug 1783170] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

[Pavel Hari Dvar]

Public bug reported:

789

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18
Uname: Linux 4.15.0-29-lowlatency x86_64
.var.log.unattended-upgrades.unattended-upgrades.log:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Jul 21 18:28:51 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
PackageArchitecture: all
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.3
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.4 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 128

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  789

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18
  Uname: Linux 4.15.0-29-lowlatency x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Jul 21 18:28:51 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
  PackageArchitecture: all
  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.3
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 128
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912

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

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

[Touch-packages] [Bug 1782835] Update Released

[Adam Conrad]

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

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

Title:
  d-i step "Configure the keyboard" fails

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Bionic:
  Fix Released

Bug description:
  Testing a bionic build of d-i w/ proposed results in a failure.

  From d-i's /var/log/syslog:

  Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected
  Jul 20 20:03:25 main-menu[897]: (process:1567): 
/var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found
  Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' 
failed with error code 127
  Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' 
failed.
  Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:46 kernel: [  224.155631] random: crng init done

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

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

[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu2.2

---
console-setup (1.178ubuntu2.2) bionic; urgency=medium

  * debian/console-setup-udeb.postinst: Guard the dpkg call in the postinst,
so it isn't attempted in the debian-installer environment (LP: #1782835)

console-setup (1.178ubuntu2.1) bionic; urgency=medium

  * debian/keyboard-configuration.postinst:
- Don't change /etc/default/keyboard at package upgrades on
  desktops, since it may conflict with how desktops deal with
  keyboard configuration (LP: #1762952).

 -- Adam Conrad   Fri, 20 Jul 2018 14:22:45 -0600

** Changed in: console-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  d-i step "Configure the keyboard" fails

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Bionic:
  Fix Released

Bug description:
  Testing a bionic build of d-i w/ proposed results in a failure.

  From d-i's /var/log/syslog:

  Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected
  Jul 20 20:03:25 main-menu[897]: (process:1567): 
/var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found
  Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' 
failed with error code 127
  Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' 
failed.
  Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:46 kernel: [  224.155631] random: crng init done

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

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

[Touch-packages] [Bug 1762952] Update Released

[Adam Conrad]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original 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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu2.2

---
console-setup (1.178ubuntu2.2) bionic; urgency=medium

  * debian/console-setup-udeb.postinst: Guard the dpkg call in the postinst,
so it isn't attempted in the debian-installer environment (LP: #1782835)

console-setup (1.178ubuntu2.1) bionic; urgency=medium

  * debian/keyboard-configuration.postinst:
- Don't change /etc/default/keyboard at package upgrades on
  desktops, since it may conflict with how desktops deal with
  keyboard configuration (LP: #1762952).

 -- Adam Conrad   Fri, 20 Jul 2018 14:22:45 -0600

** Changed in: console-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original 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 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Launchpad Bug Tracker]

This bug was fixed in the package perl - 5.26.1-6ubuntu0.2

---
perl (5.26.1-6ubuntu0.2) bionic; urgency=high

  * No change rebuild to fix LP: #1574351

 -- Balint Reczey   Wed, 18 Jul 2018 16:21:03 +0200

** Changed in: perl (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed
Status in pkgbinarymangler package in Ubuntu:
  Fix Released
Status in perl source package in Bionic:
  Fix Released
Status in pkgbinarymangler source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Pkgstripfiles generates different stripped documentation for
  arch:any packages depending on if arch:all packages are built at the
  same time. In practice it means that amd64 packages may end up
  different file contents of doc files compared to other architectures
  making multiarch installation of the affected packages impossible
  without workarounds.

   * To fix affected packages by a rebuild the pkgbinarymangler package
  needs to be backported, too.

   * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.

  [Test Case]

   * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
   * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
   * The resulting libperl5.2? package can also be analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to 
check if the original bug is fixed just install libperl5.26:amd64 and 
libperl5.26:i386 using multiarch (here we assume the current architecture is 
amd64):
  $ sudo dpkg --add-architecture i386
  $ sudo apt update
  $ sudo apt install libperl5.26:i386

  
  [Regression Potential]

   * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter
  can be avoided by checking the build logs of a few other packages
  rebuilt with the fixed pkgbinarymangler package.

  [Original Bug Text]

  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Launchpad Bug Tracker]

This bug was fixed in the package pkgbinarymangler - 138.18.04.0

---
pkgbinarymangler (138.18.04.0) bionic; urgency=medium

  * pkgstripfiles: Serialize PNG optimization and changelog trucation using
the lock already used for serializing creating symlinks for identical
documentation files. (LP: #1782094)
  * pkgstripfiles: Skip symlinking identical documentation to not built
packages, otherwise arch: any only builds may create symlinks which are
not created when building arch: all and arch: any together. The mismatch
between the symlinked and not symlinked files causes failure when trying
to coinstall arch:any packages using multiarch.
(LP: #1574351)

 -- Balint Reczey   Tue, 17 Jul 2018 16:23:13 +0200

** Changed in: pkgbinarymangler (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed
Status in pkgbinarymangler package in Ubuntu:
  Fix Released
Status in perl source package in Bionic:
  Fix Released
Status in pkgbinarymangler source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Pkgstripfiles generates different stripped documentation for
  arch:any packages depending on if arch:all packages are built at the
  same time. In practice it means that amd64 packages may end up
  different file contents of doc files compared to other architectures
  making multiarch installation of the affected packages impossible
  without workarounds.

   * To fix affected packages by a rebuild the pkgbinarymangler package
  needs to be backported, too.

   * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.

  [Test Case]

   * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
   * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
   * The resulting libperl5.2? package can also be analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to 
check if the original bug is fixed just install libperl5.26:amd64 and 
libperl5.26:i386 using multiarch (here we assume the current architecture is 
amd64):
  $ sudo dpkg --add-architecture i386
  $ sudo apt update
  $ sudo apt install libperl5.26:i386

  
  [Regression Potential]

   * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter
  can be avoided by checking the build logs of a few other packages
  rebuilt with the fixed pkgbinarymangler package.

  [Original Bug Text]

  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386

[Touch-packages] [Bug 1574351] Update Released

[Adam Conrad]

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

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed
Status in pkgbinarymangler package in Ubuntu:
  Fix Released
Status in perl source package in Bionic:
  Fix Released
Status in pkgbinarymangler source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Pkgstripfiles generates different stripped documentation for
  arch:any packages depending on if arch:all packages are built at the
  same time. In practice it means that amd64 packages may end up
  different file contents of doc files compared to other architectures
  making multiarch installation of the affected packages impossible
  without workarounds.

   * To fix affected packages by a rebuild the pkgbinarymangler package
  needs to be backported, too.

   * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.

  [Test Case]

   * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
   * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
   * The resulting libperl5.2? package can also be analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to 
check if the original bug is fixed just install libperl5.26:amd64 and 
libperl5.26:i386 using multiarch (here we assume the current architecture is 
amd64):
  $ sudo dpkg --add-architecture i386
  $ sudo apt update
  $ sudo apt install libperl5.26:i386

  
  [Regression Potential]

   * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter
  can be avoided by checking the build logs of a few other packages
  rebuilt with the fixed pkgbinarymangler package.

  [Original Bug Text]

  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1260041] Update Released

[Adam Conrad]

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

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

Title:
  Unattended-Upgrades crashes with a dpkg error

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades fails upgrading packages in the middle of a dpkg/apt 
call due to a parallel process acquiring apt or dpkg lock while u-u is running, 
but u-u running apt/dpkg anyway without successfully re-acquiring the lock.
   * The fix is stopping processing updates when the lock is detected to be 
lost.

  [Test Case]

   * Set up a system with packages (> 30) to be upgraded:
  $ lxc launch ubuntu:b36ec647e374 uu-lock-bail

   * Set up two shells to run commands in parallel
   * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
   * After u-u started installing the updates run the following command in 
shell "B":
  $  while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; 
print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done

  * With not fixed u-u observe the following exception repeated in shell "B", 
then True being printed when the lock is successfully stolen from u-u:
  ...
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  True
  True
  True
  ...

  Buggy u-u continues operation even after the lock is stolen.

  Fixed u-u stops operation with a printout similar to the following when it 
detects the lock to be stolen:
  ...
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure 
/var/cache/apt/archives/distro-info-data_0.37ubuntu0.1_all.deb 
  /usr/bin/dpkg --status-fd 9 --configure --pending 
  Exception happened during upgrade.
  Traceback (most recent call last):
File "./unattended-upgrade", line 539, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "./unattended-upgrade", line 360, in __exit__
  apt_pkg.pkgsystem_lock()
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Exception happened during upgrade.
  NoneType: None
  Installing the upgrades failed!
  error message: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  dpkg returned a error! See 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
  ...

  [Regression Potential]

   * As a consequence of the fix unattended-upgrade stops installing
  security-updates when an other dpkg frontend's parallel activity is
  detected. This is intentional to prevent parallel execution of dpkg
  and potentially leaving the system in an inconsistent state. The full
  fix will be implemented in LP: #1781169 and changing u-u to use the
  new locking mechanism, and then u-u will never lose the lock.

  [Other Info]

  I believe parallel dpkg calls cause many breakages reported against
  u-u and other packages listing breaking maintainer scripts.

  [Original Bug Text]

  As per https://bugs.launchpad.net/ubuntu/+source/unattended-
  upgrades/+bug/1052360/comments/17, I am filing a new bug with the
  specific error I am running into. This has been going on for quite a
  while now.

  Also, my log files still show up as I described in
  https://bugs.launchpad.net/ubuntu/+source/unattended-
  upgrades/+bug/1052360/comments/14.

  ProblemType: Bug
  DistroRelease: Ubuntu

[Touch-packages] [Bug 1260041] Re: Unattended-Upgrades crashes with a dpkg error

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.5

---
unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium

  * Stop updating the system when reacquiring the dpkg system lock fails.
(LP: #1260041)

 -- Balint Reczey   Wed, 18 Jul 2018 13:22:36 +0200

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Unattended-Upgrades crashes with a dpkg error

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades fails upgrading packages in the middle of a dpkg/apt 
call due to a parallel process acquiring apt or dpkg lock while u-u is running, 
but u-u running apt/dpkg anyway without successfully re-acquiring the lock.
   * The fix is stopping processing updates when the lock is detected to be 
lost.

  [Test Case]

   * Set up a system with packages (> 30) to be upgraded:
  $ lxc launch ubuntu:b36ec647e374 uu-lock-bail

   * Set up two shells to run commands in parallel
   * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
   * After u-u started installing the updates run the following command in 
shell "B":
  $  while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; 
print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done

  * With not fixed u-u observe the following exception repeated in shell "B", 
then True being printed when the lock is successfully stolen from u-u:
  ...
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  True
  True
  True
  ...

  Buggy u-u continues operation even after the lock is stolen.

  Fixed u-u stops operation with a printout similar to the following when it 
detects the lock to be stolen:
  ...
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure 
/var/cache/apt/archives/distro-info-data_0.37ubuntu0.1_all.deb 
  /usr/bin/dpkg --status-fd 9 --configure --pending 
  Exception happened during upgrade.
  Traceback (most recent call last):
File "./unattended-upgrade", line 539, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "./unattended-upgrade", line 360, in __exit__
  apt_pkg.pkgsystem_lock()
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Exception happened during upgrade.
  NoneType: None
  Installing the upgrades failed!
  error message: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  dpkg returned a error! See 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
  ...

  [Regression Potential]

   * As a consequence of the fix unattended-upgrade stops installing
  security-updates when an other dpkg frontend's parallel activity is
  detected. This is intentional to prevent parallel execution of dpkg
  and potentially leaving the system in an inconsistent state. The full
  fix will be implemented in LP: #1781169 and changing u-u to use the
  new locking mechanism, and then u-u will never lose the lock.

  [Other Info]

  I believe parallel dpkg calls cause many breakages reported against
  u-u and other packages listing breaking maintainer scripts.

  [Original Bug Text]

  As per https://bugs.launchpad.net/ubuntu/+source/unattended-
  upgrades/+bug/1052360/comments/17, I am filing a new bug with the
  specific error I am running into. This has been going on for quite a
  while now.

  Also, my log files still show up as I described in
  https://bugs.launchpad.net/ubuntu/+source/unattended-
  upgrades/+bug/1052360/comments/14.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unattended-upgrades 0.79.3ubuntu8
  ProcVersionSignature: 

[Touch-packages] [Bug 1783175] [NEW] Install fails when 'ntp' user already exists

[Paul Dickey]

Public bug reported:

I work in an enterprise environment where usernames are decided
centrally. A user has been given the user name 'ntp'. I need to be able
to tell the ntp package to use a different username, but the install
script assumes that the ntp:ntp user/group is available and valid.

At a minimum, this code needs to accept a configured username variable
instead of hard-coding ntp.

if [ "$1" = "configure" ]; then
addgroup --system --quiet ntp
adduser --system --quiet --ingroup ntp --no-create-home ntp
chown -R ntp:ntp /var/lib/ntp /var/log/ntpstats
fi

Additional requested information:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
apt-cache policy ntp
ntp:
  Installed: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
  Candidate: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
  Version table:
 *** 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1:4.2.6.p5+dfsg-3ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

3) What you expected to happen
I expected the package to install

4) What happened instead
Installation fails because the user 'ntp' already exists.

Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.13) ...
adduser: The user `ntp' already exists. Exiting.
dpkg: error processing package ntp (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 ntp
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  Install fails when 'ntp' user already exists

Status in ntp package in Ubuntu:
  New

Bug description:
  I work in an enterprise environment where usernames are decided
  centrally. A user has been given the user name 'ntp'. I need to be
  able to tell the ntp package to use a different username, but the
  install script assumes that the ntp:ntp user/group is available and
  valid.

  At a minimum, this code needs to accept a configured username variable
  instead of hard-coding ntp.

  if [ "$1" = "configure" ]; then
  addgroup --system --quiet ntp
  adduser --system --quiet --ingroup ntp --no-create-home ntp
  chown -R ntp:ntp /var/lib/ntp /var/log/ntpstats
  fi

  Additional requested information:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy ntp
  ntp:
Installed: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
Candidate: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
Version table:
   *** 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.6.p5+dfsg-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) What you expected to happen
  I expected the package to install

  4) What happened instead
  Installation fails because the user 'ntp' already exists.

  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.13) ...
  adduser: The user `ntp' already exists. Exiting.
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Adam Conrad]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  * Impact
  When the U1 account credential expire it's not possible to disable livepatch

  * Test case
  - install/enable livepatch (from the first login wizard or 
software-properties)
  - invalidate your U1 credentials:
* open "Password and Keys"
* Search for an entry containing "ubuntusso"
* Right click and open "Properties"
* Show the password entry
* Modify the 'macaroon' field (e.g. add a 1 at the beginning of the string 
so you can easily remote it later)
  - open software-properties

  -> the livepatch status should be marked as enable but the control
  active so it's possible to disable it

  * Regression potential

  Check that the software-properties checkbox reflect the correct status
  when the account are valid and invalid

  

  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

[Launchpad Bug Tracker]

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

---
software-properties (0.96.24.32.4) bionic; 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 Bionic)
   Status: Fix Committed => 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
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  * Impact
  When the U1 account credential expire it's not possible to disable livepatch

  * Test case
  - install/enable livepatch (from the first login wizard or 
software-properties)
  - invalidate your U1 credentials:
* open "Password and Keys"
* Search for an entry containing "ubuntusso"
* Right click and open "Properties"
* Show the password entry
* Modify the 'macaroon' field (e.g. add a 1 at the beginning of the string 
so you can easily remote it later)
  - open software-properties

  -> the livepatch status should be marked as enable but the control
  active so it's possible to disable it

  * Regression potential

  Check that the software-properties checkbox reflect the correct status
  when the account are valid and invalid

  

  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 1783175] Re: Install fails when 'ntp' user already exists

[Hans Joachim Desserud]

** Tags added: trusty

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

Title:
  Install fails when 'ntp' user already exists

Status in ntp package in Ubuntu:
  New

Bug description:
  I work in an enterprise environment where usernames are decided
  centrally. A user has been given the user name 'ntp'. I need to be
  able to tell the ntp package to use a different username, but the
  install script assumes that the ntp:ntp user/group is available and
  valid.

  At a minimum, this code needs to accept a configured username variable
  instead of hard-coding ntp.

  if [ "$1" = "configure" ]; then
  addgroup --system --quiet ntp
  adduser --system --quiet --ingroup ntp --no-create-home ntp
  chown -R ntp:ntp /var/lib/ntp /var/log/ntpstats
  fi

  Additional requested information:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy ntp
  ntp:
Installed: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
Candidate: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13
Version table:
   *** 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.6.p5+dfsg-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) What you expected to happen
  I expected the package to install

  4) What happened instead
  Installation fails because the user 'ntp' already exists.

  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.13) ...
  adduser: The user `ntp' already exists. Exiting.
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1779815] Update Released

[Adam Conrad]

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:5

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Launchpad Bug Tracker]

This bug was fixed in the package debian-installer - 20101020ubuntu543.1

---
debian-installer (20101020ubuntu543.1) bionic; urgency=medium

  * Move master kernels to 4.15.0-29 for the 18.04.1 release.
  * Rebuild against new systemd for SCSI sync (LP: #1779815)
  * Fix permissions on the netboot.tar kernel (LP: #1781036)

 -- Adam Conrad   Sun, 22 Jul 2018 03:19:55 -0600

** Changed in: debian-installer (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.3

---
systemd (237-3ubuntu10.3) bionic; urgency=medium

  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin
to the kernel (we previously only set it in modprobe.d) LP: #1779815

 -- Adam Conrad   Fri, 20 Jul 2018 11:13:58 -0600

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating d

[Touch-packages] [Bug 1783183] [NEW] apparmor profile denied for kerberos client keytab and credential cache files

[Kartik Subbarao]

Public bug reported:

Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate
permissions to the slapd apparmor profile? I'm getting the following
kinds of errors:

apparmor="DENIED" operation="open" profile="/usr/sbin/slapd"
name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd"
requested_mask="r" denied_mask="r" fsuid=389 ouid=389

apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd"
name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k"
denied_mask="k" fsuid=389 ouid=389

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


** Tags: apparmor kerberos keytab

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

Title:
  apparmor profile denied for kerberos client keytab and credential
  cache files

Status in openldap package in Ubuntu:
  New

Bug description:
  Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate
  permissions to the slapd apparmor profile? I'm getting the following
  kinds of errors:

  apparmor="DENIED" operation="open" profile="/usr/sbin/slapd"
  name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd"
  requested_mask="r" denied_mask="r" fsuid=389 ouid=389

  apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd"
  name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k"
  denied_mask="k" fsuid=389 ouid=389

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

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

[Touch-packages] [Bug 1783190] [NEW] Download needs decades to finish :-)

[LAZA]

Public bug reported:

```
~$ sudo apt install leafpad
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Vorgeschlagene Pakete:
  evince-gtk
Die folgenden NEUEN Pakete werden installiert:
  leafpad
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 85,1 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 461 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://de.archive.ubuntu.com/ubuntu cosmic/universe amd64 leafpad amd64 
0.8.18.1-5 [85,1 kB]
Es wurden 85,1 kB in 213503982334601 d 7 h 0 min 15 s geholt (0 B/s).
Vormals nicht ausgewähltes Paket leafpad wird gewählt.
(Lese Datenbank ... 146578 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../leafpad_0.8.18.1-5_amd64.deb ...
Entpacken von leafpad (0.8.18.1-5) ...
Trigger für mime-support (3.60ubuntu1) werden verarbeitet ...
Trigger für desktop-file-utils (0.23-1ubuntu4) werden verarbeitet ...
leafpad (0.8.18.1-5) wird eingerichtet ...
update-alternatives: /usr/bin/leafpad wird verwendet, um 
/usr/bin/gnome-text-editor (gnome-text-editor) im automatischen Modus 
bereitzustellen
Trigger für man-db (2.8.3-2) werden verarbeitet ...
Trigger für gnome-menus (3.13.3-11ubuntu2) werden verarbeitet ...
Trigger für hicolor-icon-theme (0.17-2) werden verarbeitet ...
```

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: apt 1.7.0~alpha2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu5
Architecture: amd64
Date: Mon Jul 23 20:59:31 2018
InstallationDate: Installed on 2018-05-19 (65 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to cosmic on 2018-07-23 (0 days ago)

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


** Tags: amd64 apport-bug cosmic third-party-packages

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

Title:
  Download needs decades to finish  :-)

Status in apt package in Ubuntu:
  New

Bug description:
  ```
  ~$ sudo apt install leafpad
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Vorgeschlagene Pakete:
evince-gtk
  Die folgenden NEUEN Pakete werden installiert:
leafpad
  0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
  Es müssen 85,1 kB an Archiven heruntergeladen werden.
  Nach dieser Operation werden 461 kB Plattenplatz zusätzlich benutzt.
  Holen:1 http://de.archive.ubuntu.com/ubuntu cosmic/universe amd64 leafpad 
amd64 0.8.18.1-5 [85,1 kB]
  Es wurden 85,1 kB in 213503982334601 d 7 h 0 min 15 s geholt (0 B/s).
  Vormals nicht ausgewähltes Paket leafpad wird gewählt.
  (Lese Datenbank ... 146578 Dateien und Verzeichnisse sind derzeit 
installiert.)
  Vorbereitung zum Entpacken von .../leafpad_0.8.18.1-5_amd64.deb ...
  Entpacken von leafpad (0.8.18.1-5) ...
  Trigger für mime-support (3.60ubuntu1) werden verarbeitet ...
  Trigger für desktop-file-utils (0.23-1ubuntu4) werden verarbeitet ...
  leafpad (0.8.18.1-5) wird eingerichtet ...
  update-alternatives: /usr/bin/leafpad wird verwendet, um 
/usr/bin/gnome-text-editor (gnome-text-editor) im automatischen Modus 
bereitzustellen
  Trigger für man-db (2.8.3-2) werden verarbeitet ...
  Trigger für gnome-menus (3.13.3-11ubuntu2) werden verarbeitet ...
  Trigger für hicolor-icon-theme (0.17-2) werden verarbeitet ...
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apt 1.7.0~alpha2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Mon Jul 23 20:59:31 2018
  InstallationDate: Installed on 2018-05-19 (65 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to cosmic on 2018-07-23 (0 days ago)

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

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

[Touch-packages] [Bug 1783191] [NEW] package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different fr

[Lauri R Pyle]

Public bug reported:

Tried to load scanner driver.  The error occurred during this process.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon Jul 23 14:05:27 2018
DuplicateSignature:
 package:libperl5.26:5.26.1-6ubuntu0.1
 Unpacking libperl5.26:i386 (5.26.1-6ubuntu0.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-xqmUlC/28-libperl5.26_5.26.1-6ubuntu0.1_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
InstallationDate: Installed on 2018-07-13 (10 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-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: perl
Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Tried to load scanner driver.  The error occurred during this process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Jul 23 14:05:27 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6ubuntu0.1
   Unpacking libperl5.26:i386 (5.26.1-6ubuntu0.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xqmUlC/28-libperl5.26_5.26.1-6ubuntu0.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-07-13 (10 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-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783191] Re: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from

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

Title:
  package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Tried to load scanner driver.  The error occurred during this process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Jul 23 14:05:27 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6ubuntu0.1
   Unpacking libperl5.26:i386 (5.26.1-6ubuntu0.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xqmUlC/28-libperl5.26_5.26.1-6ubuntu0.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-07-13 (10 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-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783200] [NEW] [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

[Keith Gaughan]

Public bug reported:

I believe this is a pulseaudio regression, as the output of alsa-info
(http://www.alsa-
project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine
as far as I can see.

I'm currently running Ubuntu 18.04, and I believe this is a regression
as audio used to work under 17.10. Since upgrading (which fixed a good
number of other incompatibilities with the machine), I've had no luck
getting audio to work at all.

I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and
'pulseaudio -vv'.

If I can provide any other information, or if there's anything you'd
like me to try, I'd be happy to help in any way possible.

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

** Attachment added: "Tarball of relevant logs, &c."
   https://bugs.launchpad.net/bugs/1783200/+attachment/5166847/+files/logs.tzx

** Summary changed:

- [Lenovo Miix 310, Ubuntu 18.10] Audio no longer working
+ [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

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

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I believe this is a pulseaudio regression, as the output of alsa-info
  (http://www.alsa-
  project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine
  as far as I can see.

  I'm currently running Ubuntu 18.04, and I believe this is a regression
  as audio used to work under 17.10. Since upgrading (which fixed a good
  number of other incompatibilities with the machine), I've had no luck
  getting audio to work at all.

  I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and
  'pulseaudio -vv'.

  If I can provide any other information, or if there's anything you'd
  like me to try, I'd be happy to help in any way possible.

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

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

[Touch-packages] [Bug 1783162] Re: mvwin doesn't work if window is created with zero coordinates.

[Thomas Dickey]

It's in the manual page: the zero-coordinates produce a window as large
as the screen, and mvwin will not move it off the screen.

** Changed in: ncurses (Ubuntu)
   Status: New => Invalid

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

Title:
  mvwin doesn't work if window is created with zero coordinates.

Status in ncurses package in Ubuntu:
  Invalid

Bug description:
  Using the following code I cant move the window with mvwin
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(0,0,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }
  

  
  Changing the window start coordinates to 1,1 and it works.
  
  #include 
  #include 

  void quit();

  int main(int argc, char** argv) {
initscr();
atexit(quit);
curs_set(0);
noecho();

WINDOW *win = newwin(1,1,0,0); // <-- Defference
mvwin(win,10,10);
wresize(win,10,10);

refresh();
box(win,0,0);
wrefresh(win);
getch();

return 0;
  }

  void quit() {
endwin();
  }

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

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

[Touch-packages] [Bug 1783188] Re: Ubuntu 16.04 LTS crashes

[Seth Arnold]

Next time you hit this bug please submit the collected logs.

Thanks

** Information type changed from Private Security to Public

** Package changed: shadow (Ubuntu) => ubiquity (Ubuntu)

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

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

Title:
  Ubuntu 16.04 LTS crashes

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  I can reproduce this bug everytime during installation, have
  downloaded Ubuntu 16.05 LTS iso from here.
  (http://releases.ubuntu.com/releases/16.04/ubuntu-16.04.4-desktop-
  amd64.iso)

  Base system config:
  Windows 7 SP1(64 bit), 8 GB RAM, Intel(R) Core(TM)i5-4210U CPU @ 1.70GHz 
1.70GHz 

  Oracle Virtual Box 5.2.14r, the above iso was given 2024 MB RAM 20 GB
  HD for installation, which I believe is pretty OK space to run Ubuntu.

  However, the OS get crash at ubiquity 2.21.63.6 during installation, I
  have attached video PoC for your reference.

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

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

[Touch-packages] [Bug 1783191] Re: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Tried to load scanner driver.  The error occurred during this process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Jul 23 14:05:27 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6ubuntu0.1
   Unpacking libperl5.26:i386 (5.26.1-6ubuntu0.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xqmUlC/28-libperl5.26_5.26.1-6ubuntu0.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-07-13 (10 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-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined

[Matthias Klose]

the Ubuntu gcc (as well as the OpenSuse gcc) sets ---as-needed as the
default, so your configure test fails, making wrong assumptions. So
better build your configure test with -Wl,--no-as-needed.


** Changed in: gcc-defaults (Ubuntu)
   Importance: High => Undecided

** Changed in: gcc-defaults (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: binutils (Ubuntu)
   Status: New => Invalid

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

Title:
  "#pragma weak" symbol is 0 even when defined

Status in binutils package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in libidn package in Ubuntu:
  New
Status in libunistring package in Ubuntu:
  New

Bug description:
  This compiler bug is making the gnulib tests dump core; see:

  http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html

  Compile and run the following program t.c with the shell commands "gcc
  u.c -lm; ./a.out; echo $?"

  #include 
  #pragma weak tgamma

  int
  main (void)
  {
if (!tgamma)
  return 2;
if (tgamma (1) == 1)
  return 0;
return 1;
  }

  The program will exit with status 2.  It should exit with status 0,
  because the math library does have a tgamma function and the function
  pointer should be non-null.

  I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu
  4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcc 4:4.8.2-1ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 10 07:39:11 2014
  InstallationDate: Installed on 2012-12-21 (566 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gcc-defaults
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago)

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

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

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[dann frazier]

fyi, this appears to fix the problem for me.

** Patch added: 
"0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch

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

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Touch-packages] [Bug 1783138] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1783138

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

[Michael von Glasow]

The black screen issue reappeared on 18.04 sometime last week, after two
completely trouble-free months, and it is quite frequent again. I
haven’t done and in-depth diagnosis or troubleshooting so far. The
flicker issue hasn’t appeared since I upgraded.

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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

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

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

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[Dimitri John Ledkov]

Is this critical for 18.04.1 release?

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Touch-packages] [Bug 1783207] [NEW] Problems upgrading to proposed base-files 10.1ubuntu2.1

[PhotonQyv]

Public bug reported:

On upgrading to the new bionic-proposed version of base-files
(10.1ubuntu2.1)

I got the following output:

sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  base-files
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 58.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 base-files 
amd64 10.1ubuntu2.1 [58.0 kB]
Fetched 58.0 kB in 0s (376 kB/s)
Reading changelogs... Done
(Reading database ... 771574 files and directories currently installed.)
Preparing to unpack .../base-files_10.1ubuntu2.1_amd64.deb ...
Warning: Stopping motd-news.service, but it can still be activated by:
  motd-news.timer
Unpacking base-files (10.1ubuntu2.1) over (10.1ubuntu2) ...
Setting up base-files (10.1ubuntu2.1) ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
Installing new version of config file /etc/lsb-release ...
motd-news.service is a disabled or a static unit, not starting it.
Processing triggers for install-info (6.5.0.dfsg.1-2) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.3-1ubuntu7) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for cracklib-runtime (2.9.2-5build1) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for plymouth-theme-kubuntu-text (1:18.04ubuntu11) ...
dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does 
not start with a digit
rmdir: failed to remove '/lib/plymouth/': No such file or directory
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.2) ...
update-initramfs: Generating /boot/initrd.img-4.17.8-041708-generic
qyv@Twinkle:~$ ll /lib/plymouth/
ls: cannot access '/lib/plymouth/': No such file or directory
qyv@Twinkle:~$ ll /lib/plymouth*
ls: cannot access '/lib/plymouth*': No such file or directory



Description:Ubuntu 18.04.1 LTS
Release:18.04

apt-cache policy base-files
base-files:
  Installed: 10.1ubuntu2.1
  Candidate: 10.1ubuntu2.1
  Version table:
 *** 10.1ubuntu2.1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 10.1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Problems upgrading to proposed base-files 10.1ubuntu2.1

Status in base-files package in Ubuntu:
  New

Bug description:
  On upgrading to the new bionic-proposed version of base-files
  (10.1ubuntu2.1)

  I got the following output:

  sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
base-files
  1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  Need to get 58.0 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
base-files amd64 10.1ubuntu2.1 [58.0 kB]
  Fetched 58.0 kB in 0s (376 kB/s)
  Reading changelogs... Done
  (Reading database ... 771574 files and directories currently installed.)
  Preparing to unpack .../base-files_10.1ubuntu2.1_amd64.deb ...
  Warning: Stopping motd-news.service, but it can still be activated by:
motd-news.timer
  Unpacking base-files (10.1ubuntu2.1) over (10.1ubuntu2) ...
  Setting up base-files (10.1ubuntu2.1) ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  motd-news.service is a disabled or a static unit, not starting it.
  Processing triggers for install-info (6.5.0.dfsg.1-2) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.3-1ubuntu7) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for cracklib-runtime (2.9.2-5build1) ...
  Processing triggers for man-db (2.8.3-2) ...
  Processing triggers for plymouth-theme-kubuntu-text (1:18.04ubuntu11) ...
  dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does 
not start with a digit
  rmdir: failed to remove '/lib/plymouth/': No such file or directory
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.130ubuntu3.2) ...
  update-initramfs: Generating /boot/initrd.img

[Touch-packages] [Bug 1780767] Re: Some tests are flaky due to timeout

[Brian Murray]

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  Some tests are flaky due to timeout

Status in apport package in Ubuntu:
  In Progress

Bug description:
  The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
  http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
  It's blocking randomly on different tests.

  All tests that are stucked, implements closing a request via a timeout
  (and then, executing "run"). The bet is that the timeout is short
  enough (1s) so that, when autopkgtests infra is busy, time to execute
  the bash subcommand is taking more than a second, and so "dismissing"
  is ran before execution happens and the whole testsuite hangs.

  There are few instances of setting this timeout function:
  $ grep eout_add_sec test/*
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)

  Short term solution could be to increase the timeout. Long term would
  be to eliminate this potential race implementing cancelling
  differently.

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

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

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[dann frazier]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Invalid

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

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Invalid

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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