[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Daniel van Vugt]

As mentioned in the bug description, this bug only ever occurred on
Intel 8265 with the M337 on bionic. All other issues should be discussed
in other bugs.

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Daniel van Vugt]

This bug is not about suspending and resuming.

And I can't test resuming because my system becomes too unstable (for
other reasons). As for system reboot, I have always had problems with
some Bluetooth devices reconnecting on reboot. But that problem is not
confined to mice. It happens with audio too.

I think the mice fixes in comment #50 are worth having, but this is the
wrong bug to discuss them in.

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Kai-Heng Feng]

No it's not specific to Intel 8265.

Can your M337 reconnect automatically after system suspend or system
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/1773897

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Daniel van Vugt]

I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and
cannot reproduce any bug.

If the problem ever was specific to Intel 8265 then it might have been
fixed in firmware updates already here:

  https://launchpad.net/ubuntu/+source/linux-firmware

While comment #50 is interesting, I don't think it is relevant to this
bug at all. And this bug doesn't seem to exist any more anyway.

** No longer affects: gnome-bluetooth (Ubuntu)

** Changed in: oem-priority
   Status: Confirmed => 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/1773897

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Opinion
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions

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

[Touch-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Bose QC35 bluetooth audio cuts out and is disjoined in 18.04

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine,
  sound is disjoined

  1) Ubuntu 18.04.1 LTS

  2) apt-cache policy pkgname
  N: Impossible de trouver le paquet pkgname

  3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by
  bluetooth connection

  4) Sound is disjoined with Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 21:47:25 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN INQUIRY 
RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0
TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0

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

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

[Touch-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Bose QC35 bluetooth audio cuts out and is disjoined in 18.04

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine,
  sound is disjoined

  1) Ubuntu 18.04.1 LTS

  2) apt-cache policy pkgname
  N: Impossible de trouver le paquet pkgname

  3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by
  bluetooth connection

  4) Sound is disjoined with Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 21:47:25 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN INQUIRY 
RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0
TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0

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

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

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Bug Watch Updater]

** Changed in: xorg-server (Debian)
   Status: Unknown => Confirmed

** Changed in: xorg (Debian)
   Status: Unknown => New

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  Unknown
Status in bash package in Ubuntu:
  Opinion
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions

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

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Daniel van Vugt]

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

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

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

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

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #492
   https://gitlab.freedesktop.org/xorg/xserver/issues/492

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/issues/492
   Importance: Unknown
   Status: Unknown

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bash (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  Unknown
Status in bash package in Ubuntu:
  Opinion
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  Unknown
Status in xorg-server package in Debian:
  Unknown

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions

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

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Launchpad Bug Tracker]

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

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

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

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

[Touch-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Daniel van Vugt]

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

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 1576859, 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.


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

** This bug has been marked a duplicate of bug 1576859
   [nvidia] Graphics corruption when resuming from suspend

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

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

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

[Touch-packages] [Bug 1822073] Re: Bluetooth headset profile forgotten after disconnection

[Daniel van Vugt]

I stand corrected. There is also ~/.config/pulse

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

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

** No longer affects: gnome-control-center (Ubuntu)

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

Title:
  Bluetooth headset profile forgotten after disconnection

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug 1283003, after connecting my Bluetooth headset (Sony
  WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are
  not selectable.

  I've narrowed down the circumstances to reproduce the bug as follows:

  1. Start with working sound through Bluetooth to headset
  2. In pavucontrol's Configuration tab, note that headset is listed with A2DP 
profile
  3. Disconnect (power off) the headset
  4. Note that sound comes out of fallback device (as expected)
  5. Power on the headset and reconnect to Bluetooth
  6. Look in Gnome Control Centre and note the headset appears in Sound, but is 
not selectable (buggy)
  7. In pavucontrol's Configuration tab, note headset is listed with "Off"
  8. Manually switch to A2DP
  9. At the point, we have to cycle the connection again (disconnect/reconnect) 
and then sound is once more routed to the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 10:33:37 2019
  InstallationDate: Installed on 2015-07-04 (1363 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1822073] Re: Bluetooth headset profile forgotten after disconnection

[Daniel van Vugt]

AFAIK, only gnome-control-center has any memory of user preferences. So
reassigning there.

** Tags added: a2dp

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

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

Title:
  Bluetooth headset profile forgotten after disconnection

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug 1283003, after connecting my Bluetooth headset (Sony
  WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are
  not selectable.

  I've narrowed down the circumstances to reproduce the bug as follows:

  1. Start with working sound through Bluetooth to headset
  2. In pavucontrol's Configuration tab, note that headset is listed with A2DP 
profile
  3. Disconnect (power off) the headset
  4. Note that sound comes out of fallback device (as expected)
  5. Power on the headset and reconnect to Bluetooth
  6. Look in Gnome Control Centre and note the headset appears in Sound, but is 
not selectable (buggy)
  7. In pavucontrol's Configuration tab, note headset is listed with "Off"
  8. Manually switch to A2DP
  9. At the point, we have to cycle the connection again (disconnect/reconnect) 
and then sound is once more routed to the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 10:33:37 2019
  InstallationDate: Installed on 2015-07-04 (1363 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1

[Daniel van Vugt]

** Summary changed:

- tooltips and combo boxes in webbrowsers are all garbage
+ tooltips and combo boxes in webbrowsers are all garbage in 
xserver-xorg-video-radeon 1:19.0.0-1

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

Title:
  tooltips and combo boxes in webbrowsers are all garbage in xserver-
  xorg-video-radeon 1:19.0.0-1

Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  Disco up to date

  With Chrome and Firefox tooltips and combo boxes are all garbage and
  make the browser unusable. Cf screenshots.

  Graphics card:
  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]

  I tried gtk2 and gtk3 demos and the combo boxes are broken in the same
  way.

  I also tried FF as a snap and as a deb and the problem is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 11:51:41 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1717 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions

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

[Touch-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter (repeated kernel crashes in the nouveau driver)

[Daniel van Vugt]

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

** Summary changed:

- After install, cannot boot into system unless I use nomodeset kernel parameter
+ After install, cannot boot into system unless I use nomodeset kernel 
parameter (repeated kernel crashes in the nouveau driver)

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter (repeated kernel crashes in the nouveau driver)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Daniel van Vugt]

The kernel fix (comment #77) only checks for the laptop model name, not
anything else. So it will only work for "ASUS UX391UA". If you have a
different model of laptop then please open a different bug.

https://mailman.alsa-project.org/pipermail/alsa-
devel/2018-December/143282.html

** No longer affects: alsa-driver (Ubuntu)

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Committed

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

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

** Changed in: linux (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1821936] Re: No sound output on Zen AIO 27 Z272SD_Z272SD

[Daniel van Vugt]

I think you might be right about bug 1784485 being similar. In that case
this would be a kernel bug. And the title should refer to the model of
the computer instead of the model of sound chip.

** Summary changed:

- No sound output from ALC274
+ No sound output on Zen AIO 27 Z272SD_Z272SD

** No longer affects: pulseaudio (Ubuntu)

** No longer affects: alsa-driver (Ubuntu)

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

Title:
  No sound output on Zen AIO 27 Z272SD_Z272SD

Status in linux package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: 

[Touch-packages] [Bug 1821936] Re: No sound output from ALC274

[Daniel van Vugt]

** Summary changed:

- ALC274 unsupported
+ No sound output from ALC274

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

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

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

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

Title:
  No sound output on Zen AIO 27 Z272SD_Z272SD

Status in linux package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  

[Touch-packages] [Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install

[Tommy Trussell]

I just upgraded to from Xenial 16.04 to Bionic 18.04 and unfortunately
the scanner broke again.

Unfortunately the changes affect two places -- udev seems to have made
big changes to the scanner section, so I wrote a completely new udev
file, and the sane-dll backend doesn't look in the same directory.

I composed my new udev script, then after lots of tinkering and some
judicious use of the debug command:

$ SANE_DEBUG_DLL=128 scanimage -L

I discovered the changes to the sane-dll backend. I installed an instance of 
Trusty 14.04 and used the above command to confirm Trusty looked for brother2 
in:
/usr/lib/x86_64-linux-gnu/sane
/usr/lib/sane

Bionic ONLY looks for brother2 in:
/usr/lib/x86_64-linux-gnu/sane

I manually linked the files the brscan2 .deb installs into
/usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ into
/usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ and it
seems to work.

I will attempt to write up a procedure (for my benefit if nothing else).
But it may take me a little while.

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

Title:
  Brother's printer/scanner drivers awkward to find and install

Status in cups package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: cupsys

  Hello,

  I have the multifonction laser printer and scan Brother DCP-7030.

  It works very well in Ubuntu, but with some hard configuration.
  Printer is automatically detected when connected in USB, but Ubuntu
  does not propose DCP-7030 drivers, only DCP-7025, and it doesn't work
  well.

  To get DCP-7030 fully recognized and well printing / scanning, I have to do 
this (it's a short summary) :
  http://solutions.brother.com/linux/en_us/before.html

  - Printer BROTHER DCP-7030 :

  cd ~/desktop
  sudo aa-complain cupsd
  sudo mkdir /usr/share/cups/model
  http://solutions.brother.com/linux/en_us/download_prn.html#DCP-7030
  sudo dpkg -i --force-all --force-architecture brdcp7030lpr-2.0.2-1.i386.deb
  sudo dpkg -i --force-all --force-architecture 
cupswrapperDCP7030-2.0.2-1.i386.deb
  http://127.0.0.1:631/printers/DCP7030 : OK

  After that printer works

  
  - SCANNING :

  Install scan-key-tools  /  Brscan3
  http://solutions.brother.com/linux/en_us/download_scn.html#brscan3
  http://solutions.brother.com/linux/en_us/instruction_scn1a.html

  sudo gedit /lib/udev/rules.d/50-udev-default.rules : in section
  "libusb device nodes", replacer 0664 by 0666

  sudo lsusb
  Bus 001 Device 004: ID 04f9:01a Brother Industries, Ltd
  Go to dev/bus/usb : bus 1 and device 4 is root owned
  Open it in Nautilus as root, change it to my user name and take ownership

  Now Simple Scan works, Brother-DCP is seen.

  But... big problem !

  At each restart of Ubuntu or DCP Brother, permission resets and comes
  back to root, I have to change ownership and re-log each time, this is
  not nice...

  Is it a way to "protect" the file against erasing or permission change
  ?

  It's also true for other models than DCP-7030 (like DCP-7040...). I do
  not know if it is a Cups / Ubuntu "bug" or Openprinting missing for
  new drivers, but as Brother gives functional drivers for Linux, this
  should be easily implemented I hope, as more and more materials are
  natively identified in Ubuntu.

  Thanks in advance for your help. Best regards,

  Xavier

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

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

[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

[Daniel van Vugt]

I assume this bug is about audio and you're not talking about something
appearing muted...? :)

I also can't see any obvious problems. Do you have any gnome-shell
extensions installed? Or any other software starting automatically on
login?

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

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

[Steve Langasek]

Hello Alan, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.2 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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Steve Langasek]

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.2 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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed-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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Steve Langasek]

Hello Daniel, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Released => Fix Committed

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine 

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

[Steve Langasek]

Hello Alan, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

[Seth Arnold]

root: sudo apt update && sudo apt upgrade

Thanks

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1822092] Re: FFe: Mesa 19.0.1 for disco

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.1-1ubuntu1

---
mesa (19.0.1-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1822092)

 -- Timo Aaltonen   Thu, 28 Mar 2019 15:51:31 +0200

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

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

Title:
  FFe: Mesa 19.0.1 for disco

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 19.0.1 is a bug fix release which fixes bugs found since the
  19.0.0 release.

  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.

  https://www.mesa3d.org/relnotes/19.0.1.html

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

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

[Touch-packages] [Bug 1777006] Re: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  attempting a do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.11
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Thu Jun 14 15:02:24 2018
  DuplicateSignature: package:initramfs-tools:0.103ubuntu4.11:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-01-23 (1968 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2018-06-14 (0 days ago)

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

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

[Touch-packages] [Bug 1472758] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@161:collect_info:process_report:add_gdb_info:gdb_command

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1820132
   
/usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@161:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.17.3-0ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/bd73cc178a8f334b3cd563f43ec2912dfbf814b5
  contains more details.

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

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

[Touch-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Brian Murray]

** Tags added: disco

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in xorg package in Ubuntu:
  New

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

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

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

[Touch-packages] [Bug 1822179] [NEW] Resuming from sleep breaks desktop and lock screen background in GNOME

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

CPU: AMD Ryzen 5 1600
MOBO: MSI B350M MORTAR
GPU: NVIDIA GTX 1060

Ubuntu version: 19.04
Nvidia driver version: 418.56


The system is updated with the latest updates as today, 28 March 2019

As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted,
and the GNOME desktop has blank background after resuming from
standby/sleep

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


** Tags: bot-comment disco
-- 
Resuming from sleep breaks desktop and lock screen background in GNOME
https://bugs.launchpad.net/bugs/1822179
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

[Mathieu Trudel-Lapierre]

Yes, that does explain it.

/run/netplan/.yaml is written automatically by initramfs-
tools when booting with a remote root (ie. iscsi); so this does check
out: for example, 'critical' is required in that case, otherwise as soon
as someone runs 'netplan apply' the network will go down and you might
have filesystem errors.

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug is a follow-up to

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268

  after applying the 0001-net_failover-delay-taking-over-primary-device-
  to-acc.patch attached in that bug, the VF interface "eth0" is renamed
  to "rename4" instead of "ens4". Log is showing that attempt to rename
  "eth0" to "ens3" failed because of conflict with existing name, so
  that's why it ends up with rename4.

  vsbalakr@ubuntu-18:~$ uname -a
  Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-18:~$ ip l 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 
  2: ens3:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff 
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether 
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff 
  4: rename4:  mtu 1500 qdisc mq master ens3 
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff

  vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
  ...
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): carrier: link connected
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): enslaved to non-master-type device ens3; ignoring
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface 
name 'eth0' to 'ens3': Device or resource busy
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4' 
from 'eth0' to 'ens3': Device or resource busy

  Within VM there's netplan config as below:

  vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]

  By running udevadm test, we can see the conflicting ens3 name comes
  from netplan's /run/udev/rules.d/99-netplan-ens3.rules

  vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

  vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add" 
/sys/class/net/eth0
  calling: test
  version 237
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  Load module index
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /run/systemd/network/10-netplan-ens3.link
  Created link configuration context.
  Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
  ..
  Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
  rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
  25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie 
nodes used
  RUN '/lib/open-iscsi/net-interface-handler start' 
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
  IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
  IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description.rules:12
  RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
  IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
  IMPORT builtin 'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
  Config file /lib/systemd/network/99-default.link applies to device eth0
  link_config: autonegotiation is unset or enabled, the speed and duplex are 
not writable.
  link_config: could not set ethtool features for eth0
  Could not set offload features of eth0: Operation not permitted
  NAME 'ens4' /lib/udev/rules.d/80-net-setup-link.rules:11
  NAME 'ens3' /run/udev/rules.d/99-netplan-ens3.rules:1
  RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name 

[Touch-packages] [Bug 1821936] Re: ALC274 unsupported

[Derek Gordon]

I did this yesterday per request and marked it as confirmed.  I just
completed this for a second time agreeing to send some data which
mentioned pulse-audio, etc., to you all. It completed at 16:39 local
time, Miami.

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To 

[Touch-packages] [Bug 1821936] IwConfig.txt

[Derek Gordon]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1821936/+attachment/5250288/+files/IwConfig.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821936] WifiSyslog.txt

[Derek Gordon]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1821936/+attachment/5250297/+files/WifiSyslog.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821936] RfKill.txt

[Derek Gordon]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1821936/+attachment/5250295/+files/RfKill.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821936] Lsusb.txt

[Derek Gordon]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1821936/+attachment/5250290/+files/Lsusb.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821936] Re: ALC274 unsupported

[Derek Gordon]

apport information

** Tags added: apport-collected bionic

** Description changed:

  I find this to be an issue with current LTS 18.04's latest 4.19 kernel.
  I tested this on mainline 4.20 and 5.0 kernels as well.
  
  No audio because ALC274 not properly loaded for use, so no audio output.
  A related card had a similar bug, which was fixed, and may be of use in
  resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1784485
  
  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI
  
  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0
  
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  
  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  gdm1903 F pulseaudio
+   derek  2464 F pulseaudio
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-03-23 (5 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
+ ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-16-generic N/A
+  linux-backports-modules-4.18.0-16-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic
+ Uname: Linux 4.18.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 09/26/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: Z272SD.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: Z272SD
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 13
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
+ dmi.product.family: Zen AIO
+ dmi.product.name: Zen AIO 27 Z272SD_Z272SD
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1821936/+attachment/5250285/+files/AlsaInfo.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I 

[Touch-packages] [Bug 1821936] CurrentDmesg.txt

[Derek Gordon]

apport information

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821936] CRDA.txt

[Derek Gordon]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1821936/+attachment/5250286/+files/CRDA.txt

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1903 F pulseaudio
derek  2464 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-23 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z272SD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z272SD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
  dmi.product.family: Zen AIO
  dmi.product.name: Zen AIO 27 Z272SD_Z272SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

[Luke Faraone]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

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

Title:
  Google Online Account Two Factor with hardware key fails immediately

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  The hardware key authentication two factor fails immediately with a
  web based retry dialogue when connecting a Google account to the
  online accounts in settings using a hardware key second factor.

  Steps to reproduce:
  1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
  2. Open Online accounts
  3. Add a Google Account
  4. Enter google email address
  5. Enter google password
  6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

  Work around:
  Choose use another method to authenticate: enter the authentication code and 
you will proceed.

  Expectations were:
  The ability to use the hardware key to authenticate as the second factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 16:01:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+subscriptions

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

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Ubuntu Foundations Team Bug Bot]

The attachment "makes clear_console switch to either tty6 or tty5
instead of tty1/tty2" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in bash package in Ubuntu:
  New

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

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

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

[Si-Wei Liu]

Before answering your quesitions, I would wonder what do you know
generates the /run/netplan/ens3.yaml file in the first place? This YAML
file is not provided by us obviously, the only netplan config we have on
the root disk is /etc/netplan/01-netcfg.yaml, derived from the debian
installer. The YAML under /run overrides the one under /etc, for the
DHCP case, and that's where the odds about the additional udev rule and
various config options came from.

The DHCP server in our lab setup might have directed netroot to iSCSI so
that *might* explain where the /run/netplan/ens3.yaml with tne extra
match-mac, dhcp-identifier and critical options?

$ lsscsi -t
[6:0:0:0]storage iqn.2015-02.oracletest.boot:uefi,t,0x1  -
[6:0:0:1]diskiqn.2015-02.oracletest.boot:uefi,t,0x1  /dev/sda

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug is a follow-up to

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268

  after applying the 0001-net_failover-delay-taking-over-primary-device-
  to-acc.patch attached in that bug, the VF interface "eth0" is renamed
  to "rename4" instead of "ens4". Log is showing that attempt to rename
  "eth0" to "ens3" failed because of conflict with existing name, so
  that's why it ends up with rename4.

  vsbalakr@ubuntu-18:~$ uname -a
  Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-18:~$ ip l 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 
  2: ens3:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff 
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether 
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff 
  4: rename4:  mtu 1500 qdisc mq master ens3 
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff

  vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
  ...
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): carrier: link connected
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): enslaved to non-master-type device ens3; ignoring
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface 
name 'eth0' to 'ens3': Device or resource busy
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4' 
from 'eth0' to 'ens3': Device or resource busy

  Within VM there's netplan config as below:

  vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]

  By running udevadm test, we can see the conflicting ens3 name comes
  from netplan's /run/udev/rules.d/99-netplan-ens3.rules

  vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

  vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add" 
/sys/class/net/eth0
  calling: test
  version 237
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  Load module index
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /run/systemd/network/10-netplan-ens3.link
  Created link configuration context.
  Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
  ..
  Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
  rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
  25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie 
nodes used
  RUN '/lib/open-iscsi/net-interface-handler start' 
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
  IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
  IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description.rules:12
  RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
  IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
  IMPORT builtin 'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
  Config file 

[Touch-packages] [Bug 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

[Brian Murray]

Actually, I was looking at the wrong thing what's really missing is the
executable which crashed from the top of the function gdb_command:

assert 'ExecutablePath' in self 
executable = self.get('InterpreterPath', self['ExecutablePath'])

While it makes sense for apport-retrace to have an AssertionError if the
executable doesn't exist I don't think whoopsie-upload-all necessarily
should just because it isn't on the client system doesn't mean the
retracers won't be able to install it.

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

[Frank Heimes]

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

** No longer affects: systemd (Ubuntu)

** Changed in: ubuntu-z-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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in netplan.io package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Minimal installs using netplan to configure the network.

  [Test case]
  1) Install Ubuntu minimal server / cloud image
  2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
  3) Run 'sudo netplan apply'. Verify that the network comes up correctly.
  4) Reboot.
  5) Verify that the network comes up properly.

  [Regression potential]
  Minimal; this reverts changes in a package that was never released to 
-updates, only available as SRU in -proposed and on the devel release. This 
only applies to the order in which systemd-networkd is enabled when used as a 
renderer for netplan configuration, to start in multi-user.target instead of 
the "correct", but inefficient "network-online.target" as the latter may not be 
depended upon in minimal installs.

  ---

  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
    version: 2
    renderer: networkd
    ethernets:
  enc600:
    addresses: ¬ 10.245.236.27/24 |
    gateway4: 10.245.236.1
    nameservers:
    search: ¬ canonical.com |
    addresses:
    - "10.245.236.1"

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::28:bff:fe00:15/64 scope link
     valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600
     valid_lft forever preferred_lft forever
  inet6 fe80::28:bff:fe00:15/64 scope link
     valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

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

[Touch-packages] [Bug 1682883] Re: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

[Luigi Cisana]

The bug is still present in all subsequent versions of Ubuntu (17.10,
18.04 and 18.10).

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

Title:
  Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 
(kernel 4.10.0-19-generic).
  The issue doesn't exist when booting with the previous kernel 
(4.8.0-46-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 19:03:35 2017
  DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed
   nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed
   nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05b0]
   NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05b0]
  InstallationDate: Installed on 2015-01-17 (818 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Dell Inc. XPS 2720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d1a29a63-27bc-4b4f-b455-9be750a1356e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05R2TK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd11/13/2015:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00:
  dmi.product.name: XPS 2720
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Fri Apr 14 18:53:04 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1682883] Re: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

[Luigi Cisana]

Bug confirmed on newer versions of Ubuntu also.

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

Title:
  Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 
(kernel 4.10.0-19-generic).
  The issue doesn't exist when booting with the previous kernel 
(4.8.0-46-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 19:03:35 2017
  DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed
   nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed
   nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05b0]
   NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05b0]
  InstallationDate: Installed on 2015-01-17 (818 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Dell Inc. XPS 2720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d1a29a63-27bc-4b4f-b455-9be750a1356e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05R2TK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd11/13/2015:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00:
  dmi.product.name: XPS 2720
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Fri Apr 14 18:53:04 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

[Mathieu Trudel-Lapierre]

** Description changed:

+ [Impact]
+ Minimal installs using netplan to configure the network.
+ 
+ [Test case]
+ 1) Install Ubuntu minimal server / cloud image
+ 2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
+ 3) Run 'sudo netplan apply'. Verify that the network comes up correctly.
+ 4) Reboot.
+ 5) Verify that the network comes up properly.
+ 
+ [Regression potential]
+ Minimal; this reverts changes in a package that was never released to 
-updates, only available as SRU in -proposed and on the devel release. This 
only applies to the order in which systemd-networkd is enabled when used as a 
renderer for netplan configuration, to start in multi-user.target instead of 
the "correct", but inefficient "network-online.target" as the latter may not be 
depended upon in minimal installs.
+ 
+ ---
+ 
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.
  
  The ip cmd shows:
- ip a  
+ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
- t qlen 1000  
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
- inet 127.0.0.1/8 scope host lo  
-valid_lft forever preferred_lft forever  
- inet6 ::1/128 scope host   
-valid_lft forever preferred_lft forever  
+ t qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
- en 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
+ en 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  
  The netplan yaml file looks fine:
- cat /etc/netplan/*.yaml  
+ cat /etc/netplan/*.yaml
  # This file describes the network interfaces available on your system
- # For more information, see netplan(5).  
- network:  
-   version: 2  
-   renderer: networkd  
-   ethernets:  
- enc600:  
-   addresses: ¬ 10.245.236.27/24 |  
-   gateway4: 10.245.236.1  
-   nameservers:  
-   search: ¬ canonical.com |  
-   addresses:  
-   - "10.245.236.1"  
+ # For more information, see netplan(5).
+ network:
+   version: 2
+   renderer: networkd
+   ethernets:
+ enc600:
+   addresses: ¬ 10.245.236.27/24 |
+   gateway4: 10.245.236.1
+   nameservers:
+   search: ¬ canonical.com |
+   addresses:
+   - "10.245.236.1"
  
  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
- ip addr show enc600  
+ ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
- oup default qlen 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
- inet6 fe80::28:bff:fe00:15/64 scope link   
-valid_lft forever preferred_lft forever  
+ oup default qlen 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
+ inet6 fe80::28:bff:fe00:15/64 scope link
+    valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$
  
  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
- sudo netplan apply --dryrun  
+ sudo netplan apply --dryrun
  ubuntu§hwe0007:ß$ sudo netplan apply
- sudo netplan apply  
+ sudo netplan apply
  ubuntu§hwe0007:ß$ ip addr show enc600
- ip addr show enc600  
+ ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
- oup default qlen 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
- inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
-valid_lft forever preferred_lft forever  
- inet6 fe80::28:bff:fe00:15/64 scope link   
-valid_lft forever preferred_lft forever  
- ubuntu§hwe0007:ß$ 
+ oup default qlen 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
+ inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600
+    valid_lft forever preferred_lft forever
+ inet6 fe80::28:bff:fe00:15/64 scope link
+    valid_lft forever preferred_lft forever
+ ubuntu§hwe0007:ß$
  
  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

** Changed in: netplan.io (Ubuntu)
   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/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  In Progress
Status 

[Touch-packages] [Bug 1822184] [NEW] clear_console locks up video when X is running and you log out from a plain text console

[Quesar]

Public bug reported:

References:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898


If X is running and you switch to a plain text console (ie ctrl-alt-f3), log in 
as a regular user, and then log out, the display switches back to the graphical 
login screen and locks up.  The system is still functioning (can ssh in, etc) 
but the video output is frozen.

The underlying cause is:
https://gitlab.freedesktop.org/xorg/xserver/issues/492

However, the problem can at least be worked around by making
clear_console switch to tty 6 and back instead of switching to 1 and
back.  This patch corrects the problem:


--- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
+++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
@@ -205,7 +205,7 @@
 #if defined(__linux__)
   num = vtstat.v_active;
 #endif
-  tmp_num = (num == 1 ? 2 : 1);
+  tmp_num = (num == 6 ? 5 : 6);
 
   /* switch vt to clear the scrollback buffer */
   if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

** Patch added: "makes clear_console switch to either tty6 or tty5 instead of 
tty1/tty2"
   
https://bugs.launchpad.net/bugs/1822184/+attachment/5250280/+files/fix-clear_console-GUI-lockup.patch

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in bash package in Ubuntu:
  New

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

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

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

[Jarno Suni]

In my linux-purge script (https://launchpad.net/linux-purge) I use
extended regular expression '^linux-.+-[0-9]+\.[0-9]+\.' to match
versioned kernel package names and it has worked so far.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

[Frank Heimes]

Just as a side note - this also happens (like expected) with LPAR
installations.

I already did some earlier disco daily installations and cannot remember
that I ran into this issue before which wonders me a bit ...

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

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

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

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

[Mathieu Trudel-Lapierre]

I also forgot to mention another entry I see in some of the configs:

set-name: ens3

If you do not need to explicitly rename the interfaces yourself to a
different name, I would avoid setting this at all. It *may* be being set
automatically by cloud-init (if that's in use, but the configs provided
do not look like generated configs from cloud-init).

I'm curious to see how this behaves with the most simple netplan
configuration possible; if you still see renaming issues in that case
from the kernel -- as those would be renaming done completely outside of
netplan and further direct our debugging to systemd-network / systemd-
udev instead.

In short; how much of the issues are you seeing when the only netplan
config on the systems is /etc/netplan/01-netcfg.yaml (the one generated
by debian-installer)?

Judging from the original description, I'd say you still get renaming
issues, specifically any new device with the MAC is attempted to be
named "ens3" because of the udev rules:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

This part should not vary whether there are statically assigned
addresses or not; but it's also questionable whether or not it is useful
to write it in the first place: systemd-udev should already be following
ifnames policy to name the device appropriately (this should be true in
all scenarios, this is only marginally useful for /renaming/ (when set-
name: is specified) or setting MTU and such low-level options).

Finally, could you please also provide us with the output of:
sudo udevadm info /sys/class/net/ens4  (or rename4, depending on how it ends up 
being named).

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug is a follow-up to

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268

  after applying the 0001-net_failover-delay-taking-over-primary-device-
  to-acc.patch attached in that bug, the VF interface "eth0" is renamed
  to "rename4" instead of "ens4". Log is showing that attempt to rename
  "eth0" to "ens3" failed because of conflict with existing name, so
  that's why it ends up with rename4.

  vsbalakr@ubuntu-18:~$ uname -a
  Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-18:~$ ip l 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 
  2: ens3:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff 
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether 
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff 
  4: rename4:  mtu 1500 qdisc mq master ens3 
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff

  vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
  ...
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): carrier: link connected
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): enslaved to non-master-type device ens3; ignoring
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface 
name 'eth0' to 'ens3': Device or resource busy
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4' 
from 'eth0' to 'ens3': Device or resource busy

  Within VM there's netplan config as below:

  vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]

  By running udevadm test, we can see the conflicting ens3 name comes
  from netplan's /run/udev/rules.d/99-netplan-ens3.rules

  vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

  vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add" 
/sys/class/net/eth0
  calling: test
  version 237
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  Load module index
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed 

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

[Jarno Suni]

I meant linux-modules is excessive.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

[Mathieu Trudel-Lapierre]

All of these values should be coming directly from the netplan YAML. Are
all of these options required?

I see:

match:
  macaddress:  # Do you need to match the interface in this case? Is it 
sufficient to match by name if only ens3 is being configured?


Also:

dhcp-identifier: mac   # This should only be required for clients who do
not have control over their DHCP server, and thus can't use the DUID to
set reservations and instead must use the MAC address to get a "static"
IP from DHCP. I would recommend not setting this if it can be avoided.

Also:

critical: true # This is only required for systems booting off
the network to reach their root filesystem. It will control whether the
DHCP IP is released / regained when systemd-networkd restarts. Again, I
would recommend not setting this if it's not required; DHCP leases
lifetimes should ensure you will get the same address again.

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug is a follow-up to

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268

  after applying the 0001-net_failover-delay-taking-over-primary-device-
  to-acc.patch attached in that bug, the VF interface "eth0" is renamed
  to "rename4" instead of "ens4". Log is showing that attempt to rename
  "eth0" to "ens3" failed because of conflict with existing name, so
  that's why it ends up with rename4.

  vsbalakr@ubuntu-18:~$ uname -a
  Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-18:~$ ip l 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 
  2: ens3:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff 
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether 
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff 
  4: rename4:  mtu 1500 qdisc mq master ens3 
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd 
ff:ff:ff:ff:ff:ff

  vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
  ...
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): carrier: link connected
  Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]:  [1552932112.9591] 
device (rename4): enslaved to non-master-type device ens3; ignoring
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface 
name 'eth0' to 'ens3': Device or resource busy
  Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4' 
from 'eth0' to 'ens3': Device or resource busy

  Within VM there's netplan config as below:

  vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]

  By running udevadm test, we can see the conflicting ens3 name comes
  from netplan's /run/udev/rules.d/99-netplan-ens3.rules

  vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"

  vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add" 
/sys/class/net/eth0
  calling: test
  version 237
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  Load module index
  Parsed configuration file /lib/systemd/network/99-default.link
  Parsed configuration file /run/systemd/network/10-netplan-ens3.link
  Created link configuration context.
  Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
  ..
  Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
  rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
  25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie 
nodes used
  RUN '/lib/open-iscsi/net-interface-handler start' 
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
  IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
  IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description.rules:12
  RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
  IMPORT builtin 'path_id' 

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Triaged

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

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

As soon as the patch is incorporated upstream I will post the resulting
patch here.

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

Updated the proposed patch for upstream according to their requirements.

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No 

[Touch-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on

[Timo Aaltonen]

try linux-oem -1035 from bionic-proposed, it has ~50 commits backported
from 5.0 to i915 driver which should help with these issues

** Description changed:

  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.
  
  There seems to be a kernel crash before as seen in the dmesg log.
+ 
+ 
+ ProblemType: Bug
+ DistroRelease: Ubuntu 18.04
+ Package: xorg 1:7.7+19ubuntu7.1
+ ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
+ Uname: Linux 4.15.0-1034-oem x86_64
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ Date: Thu Mar 28 12:04:07 2019
+ DistUpgraded: Fresh install
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
+ DistroCodename: bionic
+ DistroVariant: ubuntu
+ DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
+Subsystem: Dell Device [1028:08af]
+ InstallationDate: Installed on 2019-02-12 (44 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ MachineType: Dell Inc. XPS 13 9380
+ ProcEnviron:
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem 
root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1
+ SourcePackage: xorg
+ Symptom: display
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ dmi.bios.date: 02/14/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.1
+ dmi.board.name: 0KTDY6
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 9380
+ dmi.sys.vendor: Dell Inc.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.95-1~18.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
+ version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Package changed: xorg (Ubuntu) => linux-oem (Ubuntu)

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

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

Title:
  Often the VGA screen stops working after screen saver was on

Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.

  There seems to be a kernel crash before as seen in the dmesg log.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
  Uname: Linux 4.15.0-1034-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 12:04:07 2019
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: 

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

[Jarno Suni]

Balint, I do not understand what you mean by that this bug covers very
old packages vs. the other covers current ones.

Patterns

linux-modules
linux-modules-extra
linux-modules-.*
linux-cloud-tools

have been added to APT::VersionedKernelPackages after reporting this
bug. linux-modules is not excessive as '.*-modules' already covers that.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1822026
   Live USB freezes or cannot complete install when nouveau driver is loaded

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

[Mathieu Trudel-Lapierre]

This seems quite likely to be an issue with netplan; I've had a similar
report on UC18; where systemd-networkd isn't started.

Turns out netplan moved the enablement of systemd-netwrokd to network-
online.target; but unfortunately there may be no service or target
depending on that. I'll revert the change to put systemd-networkd back
under multi-user.target.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu)
   Status: New => Triaged

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Critical

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

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

[Touch-packages] [Bug 1821936] Re: ALC274 unsupported

[Kai-Heng Feng]

Please run `apport-collect 1821936` to collect log.

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

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

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

[Touch-packages] [Bug 1822092] Re: FFe: Mesa 19.0.1 for disco

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  FFe: Mesa 19.0.1 for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.1 is a bug fix release which fixes bugs found since the
  19.0.0 release.

  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.

  https://www.mesa3d.org/relnotes/19.0.1.html

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Till Kamppeter]

Thanks. Closed network-manager tasks.

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: network-manager (Ubuntu Cosmic)
   Status: New => Invalid

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A

[Touch-packages] [Bug 1822156] [NEW] Cannot parse m3u8 playlist

[moma]

Public bug reported:

Hello,

I have a m3u8 (utf8 format) playlist, but many players do not understand that 
file.
Neither does totem-pl-parser.
Ref: https://developer.gnome.org/totem-pl-parser/stable/


radio.m3u8 attached.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libtotem-plparser-dev 3.26.3-1ubuntu1
Uname: Linux 5.0.1-050001-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 16:06:11 2019
InstallationDate: Installed on 2019-03-06 (21 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
SourcePackage: totem-pl-parser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem-pl-parser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

** Attachment added: "radio.m3u8"
   https://bugs.launchpad.net/bugs/1822156/+attachment/5250230/+files/radio.m3u8

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

Title:
  Cannot parse m3u8 playlist

Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  Hello,

  I have a m3u8 (utf8 format) playlist, but many players do not understand that 
file.
  Neither does totem-pl-parser.
  Ref: https://developer.gnome.org/totem-pl-parser/stable/

  
  radio.m3u8 attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libtotem-plparser-dev 3.26.3-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 16:06:11 2019
  InstallationDate: Installed on 2019-03-06 (21 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: totem-pl-parser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+subscriptions

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Kai-Heng Feng]

Yes it's purely a kernel bug.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session wayland-session
  Uname: Linux 

[Touch-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled

[Joseph Borg]

I think this might still be a bug as I want the notifications in GNOME
notifications, just not also via Evolution (which I don't use anyway).

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

Title:
  Evolution Alarm Notify continues pop-up reminders even though
  notifications disabled

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  I have turned off notifications for evolution alarm notify in settings:
  https://i.imgur.com/BNlfgzA.png

  But I still get pop-ups from the evolution alarm notify app for calendar 
events:
  https://i.imgur.com/BBdr9gm.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 28 11:31:46 2018
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2018-07-14 (136 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions

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

[Touch-packages] [Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs

[Lancillotto]

I encoured same issue on Ubuntu 18.04 kernel 5.1.0-rc.

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

Title:
  vgchange may deadlock in initramfs when VG present that's not used for
  rootfs

Status in lvm2 package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Fix Released
Status in lvm2 source package in Oneiric:
  Invalid
Status in udev source package in Oneiric:
  Fix Released
Status in lvm2 source package in Precise:
  Invalid
Status in udev source package in Precise:
  Fix Released

Bug description:
  The system is now unable to boot.
  I had to boot on previous kernel 3.0.0.
  Symptoms are boot freezes. When debugging, issuing a vgscan works ok.
  doing the vgchange -a y just hangs. I need to reboot the system afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lvm2 2.02.66-4ubuntu2
  ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
  Uname: Linux 3.0-0-generic x86_64
  Architecture: amd64
  Date: Mon Jun 27 18:15:46 2011
  ProcEnviron:
   LANGUAGE=fr_FR:en
   PATH=(custom, user)
   LANG=fr_FR.utf8
   LC_MESSAGES=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

[Julian Andres Klode]

This has been on my agenda for quite some time. It means apt will need
to talk dbus, and it might need to be able to react to a shutdown
notification from dbus, which might get pretty complex, but I have not
checked in detail.

It's not clear yet which dbus library to use. Starting with systemd's
library would be fine, but we might eventually want to move to gdbus if
we choose to implement a new apt daemon in apt using dbus, to not have
it be linux-specific.

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Triaged

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

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

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

[Touch-packages] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

[Julian Andres Klode]

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

** Changed in: apt (Ubuntu)
   Importance: High => Medium

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Triaged

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

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

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

[Touch-packages] [Bug 1807856] Re: During do-release-upgrade from 18.04 to 18.10: package lxd 3.0.2-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess retur

[Brian Murray]

What version of apport did you have installed? This should have been
fixed when bug 1766337 was fixed.

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

Title:
  During do-release-upgrade from 18.04 to 18.10: package lxd
  3.0.2-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-
  installation script subprocess returned error exit status 1

Status in apport package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Upgrading apt version of lxd to snap version during do-release-upgrade
  failed.

  I attempted to update my ubuntu server 18.04 system to 18.10 as root:

  apt update
  apt dist-upgrade -y
  apt autoremove -y
  do-release-upgrade

  I have an existing LXD installed via apt, and running containers.

  It asked me which snap LXD to upgrade to, and I selected "latest".

  Console log:

  ==> Installing the LXD snap from the latest track for ubuntu-18.10
  error: cannot perform the following tasks:
  - Run install hook of "lxd" snap if present (run hook "install": cannot 
perform operation: mount /var/lib/snapd/hostfs/var/lib/lxd /var/lib/lxd -o 
nosuid,nodev,noexec,rbind,rslave: Permission denied)
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gdCSiW/32-lxd_1%3a0.4_all.deb (--unpack):
   new lxd package pre-installation script subprocess returned error exit 
status 1
  Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/apt/cache.py", line 265, in __getitem__
    
  rawpkg = self._cache[key]
    
   KeyError: 
'32-lxd'

  During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 126, in _apt_pkg
    
 return 
self._cache()[package]
    

File "/usr/lib/python3/dist-packages/apt/cache.py", line 267, in 
__getitem__
    raise KeyError('The cache has no 
package named %r' % key)
    
 KeyError: "The cache has no package named '32-lxd'"

  During handling of the above exception, another exception occurred:

   Traceback (most recent call last):
   File "/usr/share/apport/package_hook", 
line 48, in 
    
  pr['SourcePackage'] = 
apport.packaging.get_source(options.package)
    

  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 
159, in get_source
     if 
self._apt_pkg(package).installed:
    
   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 
128, in _apt_pkg
    

raise ValueError('package %s does not exist' % package)
   ValueError: package 32-lxd does not exist
    Preparing to unpack 
.../33-open-iscsi_2.0.874-5ubuntu9.1_amd64.deb ...
  Unpacking open-iscsi (2.0.874-5ubuntu9.1) over (2.0.874-5ubuntu2.4) ...
  Preparing to unpack .../34-poppler-data_0.4.9-2_all.deb ...
  Unpacking poppler-data (0.4.9-2) over (0.4.8-2) ...
  Preparing to unpack .../35-tasksel-data_3.34ubuntu12_all.deb ...
  Unpacking tasksel-data (3.34ubuntu12) over (3.34ubuntu11) ...
  Preparing to unpack .../36-tasksel_3.34ubuntu12_all.deb ...
  Unpacking tasksel (3.34ubuntu12) over (3.34ubuntu11) ...
  Preparing to unpack .../37-libsepol1_2.8-1_amd64.deb ...
  Unpacking libsepol1:amd64 (2.8-1) over (2.7-1) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-gdCSiW/32-lxd_1%3a0.4_all.deb
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the 

[Touch-packages] [Bug 1822073] Re: Bluetooth headset profile forgotten after disconnection

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth headset profile forgotten after disconnection

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug 1283003, after connecting my Bluetooth headset (Sony
  WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are
  not selectable.

  I've narrowed down the circumstances to reproduce the bug as follows:

  1. Start with working sound through Bluetooth to headset
  2. In pavucontrol's Configuration tab, note that headset is listed with A2DP 
profile
  3. Disconnect (power off) the headset
  4. Note that sound comes out of fallback device (as expected)
  5. Power on the headset and reconnect to Bluetooth
  6. Look in Gnome Control Centre and note the headset appears in Sound, but is 
not selectable (buggy)
  7. In pavucontrol's Configuration tab, note headset is listed with "Off"
  8. Manually switch to A2DP
  9. At the point, we have to cycle the connection again (disconnect/reconnect) 
and then sound is once more routed to the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 10:33:37 2019
  InstallationDate: Installed on 2015-07-04 (1363 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Till Kamppeter]

Does this need any fix in network-manager? Seems to be fully fixed by
the kernel patch.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  

[Touch-packages] [Bug 1822092] Re: FFe: Mesa 19.0.1 for disco

[Timo Aaltonen]

doesn't really need a ffe since it's a bugfix release, but doesn't hurt
to have one either..

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

Title:
  FFe: Mesa 19.0.1 for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.1 is a bug fix release which fixes bugs found since the
  19.0.0 release.

  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.

  https://www.mesa3d.org/relnotes/19.0.1.html

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

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

[Touch-packages] [Bug 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage

[Jean-Baptiste Lallement]

I tried xserver-xorg-video-ati and xserver-xorg-video-radeon
19.0.1-0ubuntu1~ppa1 from ~canonical-x/x-staging and it fixes the issue

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Invalid

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

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

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Triaged

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided => High

** Tags removed: rls-dd-incoming
** Tags added: rls-dd-tracking

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

Title:
  tooltips and combo boxes in webbrowsers are all garbage

Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Triaged

Bug description:
  Disco up to date

  With Chrome and Firefox tooltips and combo boxes are all garbage and
  make the browser unusable. Cf screenshots.

  Graphics card:
  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]

  I tried gtk2 and gtk3 demos and the combo boxes are broken in the same
  way.

  I also tried FF as a snap and as a deb and the problem is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 11:51:41 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1717 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions

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

[Touch-packages] [Bug 1811129] Re: update ufw to 0.36

[Jamie Strandboge]

I've verified this on cosmic using a combination of test-ufw.py from QRT
(which in addition to various smoke/etc tests, runs all the tests in the
testsuite, including root/iptables tests):

ufw:
  Installed: 0.36-0ubuntu0.18.10.1
  Candidate: 0.36-0ubuntu0.18.10.1
  Version table:
 *** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-6 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic/main i386 Packages


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

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

Title:
  update ufw to 0.36

Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released

Bug description:
  [Impact]

  This bug is the master bug for a one time SRU of ufw to the new 0.36
  release. Typically patches would be individually backported like
  normal, but the new 'prepend' command feature is the impetus for this
  SRU and it contains most of the code changes. Other bugs fixed in the
  upstream release are either already included in the Ubuntu/Debian
  packaging or small enough to not pose a significant regression risk.
  0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading
  18.04 to 0.36 will make maintaining ufw a bit easier for the duration
  of this LTS.

  [Test Case]

  In addition to the in-build tests, there is an extensive testsuite for
  running under root on the live system. The QRT tests for ufw (scripts
  /test-ufw.py) run these tests (and more).

  [Regression Potential]

  In terms of code changes, I've attached code-changes-bionic-to-
  disco.diff which is a diff of the source code in bionic's 0.35-5 with
  patches applied and disco's 0.36-1 with its patches applied. This
  shows that:

   * only comment changes to conf/sysctl.conf
   * only comment changes to conf/ufw.defaults
   * doc/systemd.example is updated (but unused in our packaging)
   * various man page updates
   * ufw.pot is refreshed
   * various Makefile updates related to snap packaging and coverage (the 
debian packaging only uses the 'clean' target)
   * src/applications.py has only whitespace and comment changes

  The remaining code changes in src/ are quite small and address the SRU
  bugs and the regression potential for these changes will be discussed
  in those bugs.

  In addition to the SRU bugs listed in the changelog, 0.36 also fixes
  the following upstream bugs not already in 0.35-5:

  * bug 1782384 - ufw-framework document error
  * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 
51413/udp is used for DHT
  * bug 1377600 - ufw errors after ctr+c interupt
  * bug 1586258 - Rule insertion fails if ruleset is empty
  * bug 1558068 - remove extraneous source quench rule
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot preseed 
package configuration in debian-installer

  (other bugs in the 0.36-1 changelog are dupes of the above)

  [Other Info]

  Note that the 0.36 code base has been the basis for the snap for many
  months with the majority of the non-'prepend' changes in production
  during this time. 0.36-1 was uploaded to Debian in December (and it
  migrated automatically to disco shortly after) with no new ufw bug
  reports in either. Buster will release with 0.36-1.

  The snappy packaging, which is included upstream, underwent a lot of
  changes, but should not be considered as part of this SRU since it
  doesn't affect the deb builds.

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

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

[Touch-packages] [Bug 1811129] Re: update ufw to 0.36

[Jamie Strandboge]

I've verified this on bionic using a combination of test-ufw.py from QRT
(which in addition to various smoke/etc tests, runs all the tests in the
testsuite, including root/iptables tests):

ufw:
  Installed: 0.36-0ubuntu0.18.04.1
  Candidate: 0.36-0ubuntu0.18.04.1
  Version table:
 *** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

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

Title:
  update ufw to 0.36

Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released

Bug description:
  [Impact]

  This bug is the master bug for a one time SRU of ufw to the new 0.36
  release. Typically patches would be individually backported like
  normal, but the new 'prepend' command feature is the impetus for this
  SRU and it contains most of the code changes. Other bugs fixed in the
  upstream release are either already included in the Ubuntu/Debian
  packaging or small enough to not pose a significant regression risk.
  0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading
  18.04 to 0.36 will make maintaining ufw a bit easier for the duration
  of this LTS.

  [Test Case]

  In addition to the in-build tests, there is an extensive testsuite for
  running under root on the live system. The QRT tests for ufw (scripts
  /test-ufw.py) run these tests (and more).

  [Regression Potential]

  In terms of code changes, I've attached code-changes-bionic-to-
  disco.diff which is a diff of the source code in bionic's 0.35-5 with
  patches applied and disco's 0.36-1 with its patches applied. This
  shows that:

   * only comment changes to conf/sysctl.conf
   * only comment changes to conf/ufw.defaults
   * doc/systemd.example is updated (but unused in our packaging)
   * various man page updates
   * ufw.pot is refreshed
   * various Makefile updates related to snap packaging and coverage (the 
debian packaging only uses the 'clean' target)
   * src/applications.py has only whitespace and comment changes

  The remaining code changes in src/ are quite small and address the SRU
  bugs and the regression potential for these changes will be discussed
  in those bugs.

  In addition to the SRU bugs listed in the changelog, 0.36 also fixes
  the following upstream bugs not already in 0.35-5:

  * bug 1782384 - ufw-framework document error
  * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 
51413/udp is used for DHT
  * bug 1377600 - ufw errors after ctr+c interupt
  * bug 1586258 - Rule insertion fails if ruleset is empty
  * bug 1558068 - remove extraneous source quench rule
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot preseed 
package configuration in debian-installer

  (other bugs in the 0.36-1 changelog are dupes of the above)

  [Other Info]

  Note that the 0.36 code base has been the basis for the snap for many
  months with the majority of the non-'prepend' changes in production
  during this time. 0.36-1 was uploaded to Debian in December (and it
  migrated automatically to disco shortly after) with no new ufw bug
  reports in either. Buster will release with 0.36-1.

  The snappy packaging, which is included upstream, underwent a lot of
  changes, but should not be considered as part of this SRU since it
  doesn't affect the deb builds.

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

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

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

[Balint Reczey]

In the proposed fix for LP: #1821640 there is an autopkgtest to catch missing 
patterns.
It is scheduled to be fixed in Disco +1.

It is not an exact duplicate, because this bug covers very old packages
to match (for autoremoval this makes sense IMO), while the other one
covers the patterns for current 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/1607845

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1821582] Re: Don't rely on SysV init script in logrotate config

[Eric Desrochers]

[VERIFICATION XENIAL #3]

$ logrotate -vdf /etc/logrotate.conf: works as expected

...
renaming /var/log/syslog.7.gz to /var/log/syslog.8.gz (rotatecount 7, logstart 
1, i 7), 
renaming /var/log/syslog.6.gz to /var/log/syslog.7.gz (rotatecount 7, logstart 
1, i 6), 
renaming /var/log/syslog.5.gz to /var/log/syslog.6.gz (rotatecount 7, logstart 
1, i 5), 
renaming /var/log/syslog.4.gz to /var/log/syslog.5.gz (rotatecount 7, logstart 
1, i 4), 
renaming /var/log/syslog.3.gz to /var/log/syslog.4.gz (rotatecount 7, logstart 
1, i 3), 
renaming /var/log/syslog.2.gz to /var/log/syslog.3.gz (rotatecount 7, logstart 
1, i 2), 
renaming /var/log/syslog.1.gz to /var/log/syslog.2.gz (rotatecount 7, logstart 
1, i 1), 
renaming /var/log/syslog.0.gz to /var/log/syslog.1.gz (rotatecount 7, logstart 
1, i 0), 
renaming /var/log/syslog to /var/log/syslog.1
creating new /var/log/syslog mode = 0640 uid = 104 gid = 4
running postrotate script
running script with arg /var/log/syslog: "
/usr/lib/rsyslog/rsyslog-rotate
"
removing old log /var/log/syslog.8.gz
error: error opening /var/log/syslog.8.gz: No such file or directory
switching euid to 0 and egid to 0


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

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

Title:
  Don't rely on SysV init script in logrotate config

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Xenial:
  Fix Committed

Bug description:
  [IMPACT]

  Xenial uses systemd as default now, debian salsa 
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
  taking advantage of systemctl directly if systemd is active by still keeping 
Sysv init script as fallback only.

  While there is no 'real' impact, I think it make total sense for a
  systemd Xenial system, to use the systemctl approach for log rotation

  It has been brought to my attention by a Ubuntu user that:

  "Xenial logrotate is not able to perform full log rotation on a LXC
  container without the 'sys_ptrace' capability[1] using the Sysv
  approach, invoke-rc.d just fails"

  I have created a test pkg for this user, and the same user was able to
  conclude that it was working as expected with the systemd approach
  (systemctl) when sys_ptrace is disable inside the container.

  [1] - lxc config set  raw.lxc lxc.cap.drop=sys_ptrace

  [TEST CASE]

  ==
  [1] - On a Xenial active systemd system:
  ==
  Determine the script pick the right decision (systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  ==
  [2] - On a Xenial active upstart system:
  ==
  Determine the script pick the right decision (non-systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  [POTENTIAL REGRESSION

  * None, this commit introduced a new shell script (rsyslog-rotate)
  which uses systemctl directly if systemd is active (default in Xenial)
  but keeps the original Sysv init script as fallback only. Meaning no
  behaviour change for users who decided not to use systemd on their
  Xenial system.

  * I don't see any reported bug about this new helper for Bionic/Cosmic
  which has it since their released.

  /usr/lib/rsyslog/rsyslog-rotate:

  1) Check if existence of systemd, if yes:
     systemctl kill -s HUP rsyslog.service

  2) Check if existence of systemd, if no:
     invoke-rc.d rsyslog rotate > /dev/null

  [OTHER INFO]

  * Salsa rsyslog repository:
  
https://salsa.debian.org/debian/rsyslog/commit/4a49edf26d405726041bee12a42d6f064145c87e

  * First introduced:
  git describe --contains 4a49edf26d405726041bee12a42d6f064145c87e
  debian/8.27.0-4~1

  * rmadison:
  =>   rsyslog | 8.16.0-1ubuntu3  | xenial
  rsyslog | 8.32.0-1ubuntu4  | bionic
  rsyslog | 8.32.0-1ubuntu5  | cosmic
  rsyslog | 8.32.0-1ubuntu7  | disco

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

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

[Touch-packages] [Bug 1821582] Re: Don't rely on SysV init script in logrotate config

[Eric Desrochers]

[VERIFICATION XENIAL #1]

It has been brought to my attention the following by a Ubuntu user:
"My team confirms that the package which is in -proposed solves our issue."

This user was having issue doing rsyslog logrotation inside a container
which has SYS_PTRACE turned off. Using the systemctl approach fixed
their problem.

[VERIFICATION XENIAL #2]

* On a systemd machine:
 $ bash -xv /usr/lib/rsyslog/rsyslog-rotate 
#!/bin/sh

if [ -d /run/systemd/system ]; then
systemctl kill -s HUP rsyslog.service
else
invoke-rc.d rsyslog rotate > /dev/null
fi
+ '[' -d /run/systemd/system ']'
+ systemctl kill -s HUP rsyslog.service

* /etc/logrotate.d/rsyslog remains exactly the same minus the fact that
it now calls this 'rsyslog-rotate' helper to take action depending of
systemd or upstart.

* rsyslog rotation works as expected.

This was all tested with rsyslog version: 8.16.0-1ubuntu3.1

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

Title:
  Don't rely on SysV init script in logrotate config

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Xenial:
  Fix Committed

Bug description:
  [IMPACT]

  Xenial uses systemd as default now, debian salsa 
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
  taking advantage of systemctl directly if systemd is active by still keeping 
Sysv init script as fallback only.

  While there is no 'real' impact, I think it make total sense for a
  systemd Xenial system, to use the systemctl approach for log rotation

  It has been brought to my attention by a Ubuntu user that:

  "Xenial logrotate is not able to perform full log rotation on a LXC
  container without the 'sys_ptrace' capability[1] using the Sysv
  approach, invoke-rc.d just fails"

  I have created a test pkg for this user, and the same user was able to
  conclude that it was working as expected with the systemd approach
  (systemctl) when sys_ptrace is disable inside the container.

  [1] - lxc config set  raw.lxc lxc.cap.drop=sys_ptrace

  [TEST CASE]

  ==
  [1] - On a Xenial active systemd system:
  ==
  Determine the script pick the right decision (systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  ==
  [2] - On a Xenial active upstart system:
  ==
  Determine the script pick the right decision (non-systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  [POTENTIAL REGRESSION

  * None, this commit introduced a new shell script (rsyslog-rotate)
  which uses systemctl directly if systemd is active (default in Xenial)
  but keeps the original Sysv init script as fallback only. Meaning no
  behaviour change for users who decided not to use systemd on their
  Xenial system.

  * I don't see any reported bug about this new helper for Bionic/Cosmic
  which has it since their released.

  /usr/lib/rsyslog/rsyslog-rotate:

  1) Check if existence of systemd, if yes:
     systemctl kill -s HUP rsyslog.service

  2) Check if existence of systemd, if no:
     invoke-rc.d rsyslog rotate > /dev/null

  [OTHER INFO]

  * Salsa rsyslog repository:
  
https://salsa.debian.org/debian/rsyslog/commit/4a49edf26d405726041bee12a42d6f064145c87e

  * First introduced:
  git describe --contains 4a49edf26d405726041bee12a42d6f064145c87e
  debian/8.27.0-4~1

  * rmadison:
  =>   rsyslog | 8.16.0-1ubuntu3  | xenial
  rsyslog | 8.32.0-1ubuntu4  | bionic
  rsyslog | 8.32.0-1ubuntu5  | cosmic
  rsyslog | 8.32.0-1ubuntu7  | disco

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

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

[Touch-packages] [Bug 1822092] [NEW] FFe: Mesa 19.0.1 for disco

[El jinete sin cabeza]

Public bug reported:

Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
release.

Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
used. Some drivers don't support all the features required in OpenGL
4.5. OpenGL 4.5 is only available if requested at context creation.
Compatibility contexts may report a lower version depending on each
driver.

https://www.mesa3d.org/relnotes/19.0.1.html

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

** Description changed:

  Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
  release.
  
  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.
+ 
+ https://www.mesa3d.org/relnotes/19.0.1.html

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

Title:
  FFe: Mesa 19.0.1 for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.1 is a bug fix release which fixes bugs found since the
  19.0.0 release.

  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.

  https://www.mesa3d.org/relnotes/19.0.1.html

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

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

[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

[Joseph Borg]

** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+attachment/5250172/+files/allpackages.txt

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

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

[Joseph Borg]

apport information

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

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

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

[Joseph Borg]

apport information

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

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821904] ProcEnviron.txt

[Joseph Borg]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1821904/+attachment/5250170/+files/ProcEnviron.txt

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821904] CurrentDmesg.txt

[Joseph Borg]

apport information

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

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821904] PulseList.txt

[Joseph Borg]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1821904/+attachment/5250171/+files/PulseList.txt

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

[Joseph Borg]

Thanks Dan, hopefully they're all here.

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

[Joseph Borg]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  On Disco, Gnome Shell always starts muted.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu23
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  joe4766 F pulseaudio
+  /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2018-09-15 (193 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: pulseaudio 1:12.2-2ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
+ Tags:  disco wayland-session
+ Uname: Linux 5.0.0-7-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
+ UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/14/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.8.1
+ dmi.board.name: 0F6P3V
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 9370
+ dmi.product.sku: 07E6
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1821904/+attachment/5250166/+files/AlsaInfo.txt

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1821936] Re: ALC274 unsupported

[Derek Gordon]

See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485

It references another Linux variant (eww).  But, reading their thread
you will find that they made a patch in December 2018 to solve the 294
issue.  Then, the bug report for Ubuntu let to y'all doing the same.

I've done all the same steps mentioned in both threads.  It appears that
the same patch is needed for ACL274.

Post 28 from December 2018, https://forum.manjaro.org/t/alc294-analog-
audio-card-detected-but-no-sound-internaly-or-headphones/54089/28,
states:  "each one of ASUS new laptop models with Realtek ALC294 have
individual hwinfo SubVendor and SubDevice values. They are needed for
QUIRK hack directly in /sound/pci/hda/patch_realtek.c file."
Additionally, it includes 3 patches for the kernel regarding realtek.c.

This makes sense since all other methods to resolve fail.

So, what commands should I run to get you all that data to solve this
matter? :-)

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

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

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

[Touch-packages] [Bug 1822085] [NEW] Often the VGA screen stops working after screen saver was on

[Sebastian Andersson]

Public bug reported:

I have two connected external monitors. They are connected through a
Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
the VGA monitor complains about the resolution and will not work after
the screen saver has been active (and putting the monitors to sleep).
When shutting down the system, it then hangs and I have to force a
shutdown with the power button.

There seems to be a kernel crash before as seen in the dmesg log.

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


** Tags: amd64 apport-bug bionic ubuntu

** Description changed:

  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.
  
- There seems to be a kernel crash before, because the kernel log contains this:
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.716527] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885407] 
[drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 154000, 
found 307999)
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885470] 
[drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 
3a7a8132, found 332b2d53)
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885524] 
[drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 
0x0003, found 0x0001)
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885573] 
[drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock 
(expected 154000, found 307999)
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885618] 
[drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, 
found 54)
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885620] [ 
cut here ]
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885621] pipe state 
doesn't match!
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885760] WARNING: CPU: 5 
PID: 2855 at 
/build/linux-oem-PiIumz/linux-oem-4.15.0/drivers/gpu/drm/i915/intel_display.c:11601
 intel_atomic_commit_tail+0xc8e/0xd30 [i915]
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885762] Modules linked 
in: rfcomm ccm cdc_acm cdc_ether usbnet cmac r8152 mii snd_usb_audio 
snd_usbmidi_lib bnep snd_hda_codec_hdmi btusb btrtl btbcm btintel bluetooth 
uvcvideo videobuf2_vmalloc videobuf2_memops ecdh_generic videobuf2_v4l2 
videobuf2_core videodev media pci_stub arc4 vboxpci(OE) vboxnetadp(OE) 
xfrm_user vboxnetflt(OE) xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 
af_key xfrm_algo vboxdrv(OE) l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel 
udp_tunnel pppox hid_multitouch snd_soc_skl dell_laptop intel_rapl 
snd_soc_skl_ipc x86_pkg_temp_thermal intel_powerclamp snd_hda_ext_core 
snd_hda_codec_realtek snd_soc_sst_dsp snd_hda_codec_generic coretemp 
snd_soc_sst_ipc kvm_intel snd_soc_acpi kvm snd_soc_core irqbypass snd_compress 
crct10dif_pclmul ac97_bus crc32_pclmul snd_pcm_dmaengine
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885846]  
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
intel_cstate intel_rapl_perf joydev input_leds serio_raw binfmt_misc dell_wmi 
dell_smbios dcdbas nls_iso8859_1 dell_wmi_descriptor wmi_bmof 
intel_wmi_thunderbolt snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event ath10k_pci snd_rawmidi ath10k_core 
snd_seq ath snd_seq_device mac80211 snd_timer snd idma64 virt_dma soundcore 
cfg80211 rtsx_pci_ms mei_me memstick intel_lpss_pci mei intel_lpss ucsi_acpi 
processor_thermal_device intel_pch_thermal intel_soc_dts_iosf typec_ucsi typec 
mac_hid acpi_pad int3403_thermal intel_hid int3400_thermal int340x_thermal_zone 
acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 btrfs xor zstd_compress
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885931]  raid6_pq uas 
usb_storage hid_generic usbhid i915 rtsx_pci_sdmmc i2c_algo_bit psmouse 
drm_kms_helper syscopyarea sysfillrect thunderbolt sysimgblt fb_sys_fops 
rtsx_pci drm wmi i2c_hid hid video
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885962] CPU: 5 PID: 
2855 Comm: Xorg Tainted: GW  OE4.15.0-1034-oem #39-Ubuntu
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.885964] Hardware name: 
Dell Inc. XPS 13 9380/0KTDY6, BIOS 1.2.1 02/14/2019
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.886017] RIP: 
0010:intel_atomic_commit_tail+0xc8e/0xd30 [i915]
- Mar 22 13:29:38 sebastian-XPS-13-9380 kernel: [100351.886020] RSP: 

[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

[Jamie Strandboge]

Tested this is fixed in cosmic:

$ apt-cache policy ufw
ufw:
  Installed: 0.36-0ubuntu0.18.10.1
  Candidate: 0.36-0ubuntu0.18.10.1
  Version table:
 *** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-6 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic/main i386 Packages


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

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released
Status in ufw package in Debian:
  Fix Released

Bug description:
  [Impact]

  ufw's 'insert' command is designed to work with 'ufw status numbered'
  to insert rules in specific places in the ruleset. This makes it more
  difficult than it should be for using ufw as part of an IPS/dynamic
  firewall (eg, fail2ban) since if the firewall already has an IPv4 rule
  then the user/IPS must calculate the position of an IPv6-only rule
  before inserting it.

  From the git commit:

  "
  add 'prepend' command

  Introduce 'prepend' command to add rules to the top of the IPv4 and/or
  IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg,
  fail2ban). Unlike 'insert', 'prepend' does not require knowledge about
  the IPv6 rule number so integration into IPS is much easier.
  "

  [Test Case]

  $ sudo ufw allow 22/tcp
  $ sudo ufw allow from 1.2.3.4
  $ sudo ufw allow from 2001:db8::/32
  $ sudo ufw enable
  $ sudo ufw status numbered
  ...
  [ 1] 22/tcp ALLOW INAnywhere
  [ 2] Anywhere   ALLOW IN1.2.3.4
  [ 3] 22/tcp (v6)ALLOW INAnywhere (v6)
  [ 4] Anywhere (v6)  ALLOW IN2001:db8::/32

  # unchanged from 0.35
  $ sudo ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  ERROR: Invalid position '1'

  # new in 0.36
  $ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  $ sudo ufw prepend deny from 6.7.8.9
  $ sudo ufw status numbered
  ...
  [ 1] Anywhere   DENY IN 6.7.8.9
  [ 2] 22/tcp ALLOW INAnywhere
  [ 3] Anywhere   ALLOW IN1.2.3.4
  [ 4] Anywhere (v6)  DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1
  [ 5] 22/tcp (v6)ALLOW INAnywhere (v6)
  [ 6] Anywhere (v6)  ALLOW IN2001:db8::/32

  [Regression Potential]

  ufw has a clean methodology for adding new commands so while
  frontend.py necessarily has some logic changes to calculate where to
  insert the rule (ie, if IPv4 at the top, if IPv6 before other IPv6
  rules and if both, both), the changes were minimal and only are used
  if 'prepend' is specified (so people only using the previous command
  set should be fine).

  [Other Info]

  The ufw prepend command is new in 0.36 and thus only available in
  Debian, Ubuntu disco and the ufw snap for a few weeks. The snap is
  known to work with fail2ban and the prepend command in production
  environments since it was available.

  
  = Original description =

  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

-- 
Mailing list: 

[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

[Jamie Strandboge]

Verified this is fixed in bionic:

$ apt-cache policy ufw
ufw:
  Installed: 0.36-0ubuntu0.18.04.1
  Candidate: 0.36-0ubuntu0.18.04.1
  Version table:
 *** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released
Status in ufw package in Debian:
  Fix Released

Bug description:
  [Impact]

  ufw's 'insert' command is designed to work with 'ufw status numbered'
  to insert rules in specific places in the ruleset. This makes it more
  difficult than it should be for using ufw as part of an IPS/dynamic
  firewall (eg, fail2ban) since if the firewall already has an IPv4 rule
  then the user/IPS must calculate the position of an IPv6-only rule
  before inserting it.

  From the git commit:

  "
  add 'prepend' command

  Introduce 'prepend' command to add rules to the top of the IPv4 and/or
  IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg,
  fail2ban). Unlike 'insert', 'prepend' does not require knowledge about
  the IPv6 rule number so integration into IPS is much easier.
  "

  [Test Case]

  $ sudo ufw allow 22/tcp
  $ sudo ufw allow from 1.2.3.4
  $ sudo ufw allow from 2001:db8::/32
  $ sudo ufw enable
  $ sudo ufw status numbered
  ...
  [ 1] 22/tcp ALLOW INAnywhere
  [ 2] Anywhere   ALLOW IN1.2.3.4
  [ 3] 22/tcp (v6)ALLOW INAnywhere (v6)
  [ 4] Anywhere (v6)  ALLOW IN2001:db8::/32

  # unchanged from 0.35
  $ sudo ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  ERROR: Invalid position '1'

  # new in 0.36
  $ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  $ sudo ufw prepend deny from 6.7.8.9
  $ sudo ufw status numbered
  ...
  [ 1] Anywhere   DENY IN 6.7.8.9
  [ 2] 22/tcp ALLOW INAnywhere
  [ 3] Anywhere   ALLOW IN1.2.3.4
  [ 4] Anywhere (v6)  DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1
  [ 5] 22/tcp (v6)ALLOW INAnywhere (v6)
  [ 6] Anywhere (v6)  ALLOW IN2001:db8::/32

  [Regression Potential]

  ufw has a clean methodology for adding new commands so while
  frontend.py necessarily has some logic changes to calculate where to
  insert the rule (ie, if IPv4 at the top, if IPv6 before other IPv6
  rules and if both, both), the changes were minimal and only are used
  if 'prepend' is specified (so people only using the previous command
  set should be fine).

  [Other Info]

  The ufw prepend command is new in 0.36 and thus only available in
  Debian, Ubuntu disco and the ufw snap for a few weeks. The snap is
  known to work with fail2ban and the prepend command in production
  environments since it was available.

  
  = Original description =

  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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

[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

[Jamie Strandboge]

Verified this is fixed in bionic:

$ apt-cache policy ufw
ufw:
  Installed: 0.36-0ubuntu0.18.04.1
  Candidate: 0.36-0ubuntu0.18.04.1
  Version table:
 *** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released
Status in ufw package in Debian:
  Fix Released

Bug description:
  [Impact]

  ufw prior to 0.36 did not support locking or use xtables locking which
  can lead to problems when using ufw as a dynamic firewall.

  [Test Case]

  $ sudo apt-get install python-minimal # for the test script
  $ sudo ./test_ufw_threads.py # this runs for many seconds

  A patched ufw will complete with no errors. With an unpatched ufw, there will 
be many errors like:
  $ sudo ./test_ufw_threads.py
  ...
  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.

  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.

  [Regression Potential]

  ufw 0.36 implements a global exclusive lock before doing any kernel or
  file writes. Risk of regression includes the lock file not being
  released due to coding error. The locking is done via fcntl.lockf and
  ufw releases it in a finally clause that is careful to always release
  it.

  [Other Info]

  This locking code has been in production in the ufw snap for years and
  is known to work is static environments as well as in dynamic
  environments (IPS/fail2ban/etc).

  
  = Original description =

  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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

[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

[Jamie Strandboge]

Tested this is fixed in cosmic:

$ apt-cache policy ufw
ufw:
  Installed: 0.36-0ubuntu0.18.10.1
  Candidate: 0.36-0ubuntu0.18.10.1
  Version table:
 *** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 
Packages
100 /var/lib/dpkg/status
 0.35-6 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu cosmic/main i386 Packages


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

** 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 ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1204579

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Released
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Fix Committed
Status in ufw source package in Cosmic:
  Fix Committed
Status in ufw source package in Disco:
  Fix Released
Status in ufw package in Debian:
  Fix Released

Bug description:
  [Impact]

  ufw prior to 0.36 did not support locking or use xtables locking which
  can lead to problems when using ufw as a dynamic firewall.

  [Test Case]

  $ sudo apt-get install python-minimal # for the test script
  $ sudo ./test_ufw_threads.py # this runs for many seconds

  A patched ufw will complete with no errors. With an unpatched ufw, there will 
be many errors like:
  $ sudo ./test_ufw_threads.py
  ...
  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.

  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.

  [Regression Potential]

  ufw 0.36 implements a global exclusive lock before doing any kernel or
  file writes. Risk of regression includes the lock file not being
  released due to coding error. The locking is done via fcntl.lockf and
  ufw releases it in a finally clause that is careful to always release
  it.

  [Other Info]

  This locking code has been in production in the ufw snap for years and
  is known to work is static environments as well as in dynamic
  environments (IPS/fail2ban/etc).

  
  = Original description =

  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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