[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

[Launchpad Bug Tracker]

This bug was fixed in the package cryptsetup - 2:2.2.2-3ubuntu2.3

---
cryptsetup (2:2.2.2-3ubuntu2.3) focal; urgency=medium

  * Introduce retry logic for external invocations after mdadm (LP: #1879980)
- Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (e.g., a member is removed/failed)
  the cryptsetup scripts cannot mount the rootfs, and the boot fails.
  We fix that issue here by allowing the cryptroot script to be re-run
  by initramfs-tools/local-block stage, as mdadm can activate degraded
  arrays at that stage.
  There is an initramfs-tools counter-part for this fix, but alone the
  cryptsetup portion is harmless.
- d/cryptsetup-initramfs.install: ship the new local-bottom script.
- d/functions: declare variables for local-top|block|bottom scripts
  (flag that local-block is running and external invocation counter.)
- d/i/s/local-block/cryptroot: set flag that local-block is running.
- d/i/s/local-bottom/cryptroot: clean up the flag and counter files.
- d/i/s/local-top/cryptroot: change the logic from just waiting 180
  seconds to waiting 5 seconds first, then allowing initramfs-tools
  to run mdadm (to activate degraded arrays) and call back at least
  30 times/seconds more.

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Wed, 16 Sep 2020
17:40:05 -0300

** Changed in: cryptsetup (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and 

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

[Launchpad Bug Tracker]

This bug was fixed in the package cryptsetup - 2:2.0.2-1ubuntu1.2

---
cryptsetup (2:2.0.2-1ubuntu1.2) bionic; urgency=medium

  * Introduce retry logic for external invocations after mdadm (LP: #1879980)
- Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (e.g., a member is removed/failed)
  the cryptsetup scripts cannot mount the rootfs, and the boot fails.
  We fix that issue here by allowing the cryptroot script to be re-run
  by initramfs-tools/local-block stage, as mdadm can activate degraded
  arrays at that stage.
  There is an initramfs-tools counter-part for this fix, but alone the
  cryptsetup portion is harmless.
- d/i/cryptroot-script: set files used by cryptsetup/initramfs-tools
  (flag that local-block is running and external invocation counter);
  change logic from just wait 180 seconds / activating LVM every 10
  seconds to waiting 5 seconds first, then allowing initramfs-tools
  to run mdadm (to activate degraded arrays) and call back at least
  30 times/seconds more / activating LVM every 1 second.
- d/i/cryptroot-script-block: set flag that local-block is running.
- d/i/cryptroot-script-bottom: clean up the flag and counter files.
- d/rules: ship the new local-bottom script.

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 03 Aug 2020
18:28:48 -0300

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are 

[Touch-packages] [Bug 1890903] Re: systemd-resolved.service still breaks (now 20.04, since as least 16)

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-resolved.service still breaks (now 20.04, since as least 16)

Status in systemd package in Ubuntu:
  Expired

Bug description:
  There are still occurrences of this service breaking down.

  At some moment the service just stops working correctly and is not
  able to recover.

  I can reset the service by restarting it:
 systemctl restart systemd-resolved.service

  I've also tried to set the caching off, but it still fails on me
  occasionally (on 18.04 as well).

  There is a local DNS in the network, I would like to directly use that in 
stead of:
 nameserver 127.0.0.53

  
  Example:
  geus@desk-02:~$ ssh smb-01
  ssh: Could not resolve hostname smb-01: Temporary failure in name resolution
  ...
  root@desk-02:/home/geus# systemctl restart systemd-resolved.service
  root@desk-02:/home/geus# nslookup smb-01
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  Name: smb-01.lan
  Address: 192.168.178.39
  ...
  geus@desk-02:~$ ssh smb-01
  geus@smb-01's password:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Aug  8 17:03:50 2020
  InstallationDate: Installed on 2020-05-31 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1520928] Re: package ... failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package ... failed to install/upgrade: end of file on stdin at
  conffile prompt

Status in dpkg package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  it was about the detected the

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: open-vm-tools 2:9.10.2-2822639-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  Date: Sun Nov 29 04:58:20 2015
  DuplicateSignature: package:open-vm-tools:2:9.10.2-2822639-1ubuntu3:end of 
file on stdin at conffile prompt
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2015-11-29 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: open-vm-tools
  Title: package open-vm-tools 2:9.10.2-2822639-1ubuntu3 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.vmware.tools.tools.conf: [deleted]
  modified.conffile..etc.vmware.tools.vm.support: [deleted]
  mtime.conffile..etc.pam.d.vmtoolsd: 2015-11-29T04:38:14.726165
  mtime.conffile..etc.vmware.tools.poweroff.vm.default: 
2015-11-29T04:37:58.870079
  mtime.conffile..etc.vmware.tools.poweron.vm.default: 
2015-11-29T04:37:58.986080
  mtime.conffile..etc.vmware.tools.resume.vm.default: 2015-11-29T04:37:58.902079
  mtime.conffile..etc.vmware.tools.scripts.vmware.network: 
2015-11-29T04:37:58.942080
  mtime.conffile..etc.vmware.tools.statechange.subr: 2015-11-29T04:37:58.838079
  mtime.conffile..etc.vmware.tools.suspend.vm.default: 
2015-11-29T04:37:56.670067

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

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

[Touch-packages] [Bug 1900414] Re: sudo[5580]: root : problem with defaults entries ; TTY=unknown ; PWD=/root ; USER=navycat ;

[navycat]

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

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

Title:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ;
  PWD=/root ; USER=navycat ;

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ; 
PWD=/root ; USER=navycat ;
  sudo[11487]:  navycat : problem with defaults entries ; TTY=pts/0 ; 
PWD=/home/navycat ; USER=root ;

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: sudo 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 13:03:37 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824118] Re: wpa_supplicant executes hundreds of failed atempts in a second

[David Post]

Same problem here. If I use my WiFi as a normal interface, no issues at
all. I have wired ethernet and use this as a hotspot for some devices
and once every second I see:

Oct 20 20:32:14 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:15 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:16 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:17 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:18 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:19 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:20 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Oct 20 20:32:21 KRainbow wpa_supplicant[898]: wlp5s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1

If I setup a wpa_supplicant configuration and run it manually this does
not happen. When running as AP I would like to disable periodic
scanning.

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.10
DISTRIB_CODENAME=groovy
DISTRIB_DESCRIPTION="Ubuntu 20.10"

Happened on 20.04 as well.

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

Title:
  wpa_supplicant executes hundreds of failed atempts in a second

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  I use my computer to create a wifi hotspot to my local wired network.
  Whenever I do so I get short hangs that last for about a second every few 
minutes.
  Looking into the syslog in /var/log/syslog I get the output at the end of 
this message.
  I have tried my best to look for an answer to this bug, but the reported bugs 
on wpa_supplicant are
  all for other ret codes.

  Best,

  Victor

  Apr 10 10:54:40 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:55:13 Amaterasu wpa_supplicant[1048]: message repeated 33 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating via systemd: service name='org.gnome.evince.Daemon' 
unit='evince.service' requested by ':1.413' (uid=1000 pid=6414 comm="emacs 
lib/legacy/uv_check.f90 " label="unconfined")
  Apr 10 10:55:14 Amaterasu systemd[1695]: Starting Evince document viewer...
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Successfully activated service 'org.gnome.evince.Daemon'
  Apr 10 10:55:14 Amaterasu systemd[1695]: Started Evince document viewer.
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating service name='org.x.reader.Daemon' requested by ':1.413' (uid=1000 
pid=6414 comm="emacs lib/legacy/uv_check.f90 " label="unconfined")
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Successfully activated service 'org.x.reader.Daemon'
  Apr 10 10:55:14 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:55:37 Amaterasu wpa_supplicant[1048]: message repeated 23 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:55:38 Amaterasu dbus-daemon[1748]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" 
member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 
label="snap.spotify.spotify"
  Apr 10 10:55:38 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:57:39 Amaterasu wpa_supplicant[1048]: message repeated 120 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:57:40 Amaterasu dbus-daemon[1748]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" 
member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 
label="snap.spotify.spotify"
  Apr 10 10:57:40 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:58:15 Amaterasu wpa_supplicant[1048]: message repeated 35 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating via systemd: service name='org.gnome.evince.Daemon' 
unit='evince.service' requested by ':1.421' (uid=1000 pid=6772 comm="emacs 
/var/log/syslog " label="unconfined")
  Apr 10 10:58:15 Amaterasu systemd[1695]: Starting Evince document viewer...
  Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Successfully activated service 'org.gnome.evince.Daemon'
  Apr 10 10:58:15 Amaterasu systemd[1695]: Started Evince document viewer.
  Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating service name='org.x.reader.Daemon' 

[Touch-packages] [Bug 1900777] Re: [amdgpu] Screen freeze

[Daniel van Vugt]

Please look in /var/crash for any crash files and tell us what you find.

Also, next time the freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Open Terminal and run:

   journalctl -b-1 > prevboot.txt

   and attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ [amdgpu] Screen freeze

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

** Changed in: ubuntu
   Status: New => Incomplete

** Tags added: amdgpu

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

Title:
  [amdgpu] Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/+bug/1900777/+subscriptions

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

[Touch-packages] [Bug 1732559] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  weather applet crashes on logou

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports: 600:0:116:2842973:2017-11-15 19:14:12.331785678 
-0400:2017-11-15 19:14:13.331785678 -0400:/var/crash/apport.0.crash
  Date: Wed Nov 15 19:14:13 2017
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-08-04 (468 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.apport.conf: 2016-04-13T22:46:42
  mtime.conffile..etc.init.d.apport: 2016-03-31T09:43:38
  mtime.conffile..etc.logrotate.d.apport: 2016-04-13T22:46:42

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

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

[Touch-packages] [Bug 1738624] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apport package in Ubuntu:
  New

Bug description:
  It continuis say ubuntu failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CrashReports:
   600:0:116:1112449:2017-12-17 06:24:46.961136817 +0100:2017-12-17 
06:24:47.961136817 +0100:/var/crash/apport.0.crash
   640:1000:116:13567287:2017-12-16 21:09:14.022696971 +0100:2017-12-17 
00:44:06.876408497 +0100:/var/crash/_usr_bin_vlc.1000.crash
   600:0:116:1112827:2017-12-17 06:24:47.973136923 +0100:2017-12-17 
06:24:47.961136896 +0100:/var/crash/apport-gtk.0.crash
  Date: Sun Dec 17 06:24:47 2017
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-08-11 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.apport.conf: 2016-05-18T11:14:57
  mtime.conffile..etc.init.d.apport: 2016-03-31T16:13:38
  mtime.conffile..etc.logrotate.d.apport: 2016-05-18T11:14:57

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

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

[Touch-packages] [Bug 1781716] Re: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I do not know, there is a bug report, but it is the system, I do not
  understand anything

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.5
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Jul 12 07:47:13 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-02-21 (142 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for ML-1660-Series: 
usb://Samsung/ML-1660%20Series?serial=Z4S2BKDZB05423Y.
   device for Stylus-CX5600: usb://EPSON/Stylus%20CX5600?serial=0=1
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   ML-1660-Series: Samsung ML-1660, 2.0.0
   Stylus-CX5600: Epson Stylus CX5600 - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pam.d.cups:
   @include common-auth
   @include common-account
   @include common-session
  modified.conffile..etc.ufw.applications.d.cups:
   [CUPS]
   title=Common UNIX Printing System server
   description=CUPS is a printing system with support for IPP, samba, lpd, and 
other protocols.
   ports=631
  mtime.conffile..etc.apparmor.d.usr.sbin.cupsd: 2016-03-25T14:42:02
  mtime.conffile..etc.cups.cups-files.conf: 2016-03-25T14:41:32
  mtime.conffile..etc.init.cups.conf: 2016-03-25T14:42:00
  mtime.conffile..etc.init.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.logrotate.d.cups-daemon: 2016-02-13T12:37:50
  mtime.conffile..etc.pam.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.ufw.applications.d.cups: 2016-03-25T14:42:02

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

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

[Touch-packages] [Bug 1778815] Re: package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bin/

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps
  sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx
  usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime
  usr/bin/vmstat usr/bin/w.procps usr/bin/watch] failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in procps package in Ubuntu:
  New

Bug description:
  erro

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps sbin/sysctl 
usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch]
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jun 21 22:15:50 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-23 (611 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps 
sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch] failed to install/upgrade: end of file on stdin 
at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1875098] Re: package netbase 6.1 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package netbase 6.1 failed to install/upgrade: end of file on stdin at
  conffile prompt

Status in netbase package in Ubuntu:
  New

Bug description:
  upgrade from 18.04 to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: netbase 6.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 25 13:09:41 2020
  Dependencies:
   
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2019-02-04 (445 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: netbase
  Title: package netbase 6.1 failed to install/upgrade: end of file on stdin at 
conffile prompt
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

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

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

[Touch-packages] [Bug 1837317] Re: package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on
  stdin at conffile prompt

Status in apt package in Ubuntu:
  New

Bug description:
  Unknown error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Jul 14 20:33:28 2019
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2017-07-19 (731 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.29ubuntu0.1
  SourcePackage: apt
  Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on 
stdin at conffile prompt
  UpgradeStatus: Upgraded to xenial on 2019-07-13 (7 days ago)
  mtime.conffile..etc.apt.apt.conf.d.01autoremove: 2016-04-14T09:45:21
  mtime.conffile..etc.cron.daily.apt-compat: 2017-01-17T17:36:38
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2017-01-18T14:24:43
  mtime.conffile..etc.logrotate.d.apt: 2016-04-05T20:24:43

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

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

[Touch-packages] [Bug 1861594] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in avahi package in Ubuntu:
  New

Bug description:
  New to ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-76.86~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Sat Feb  1 19:06:33 2020
  ErrorMessage: end of file on stdin at conffile prompt
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to xenial on 2020-01-27 (5 days ago)
  modified.conffile..etc.avahi.hosts: [modified]
  modified.conffile..etc.dbus-1.system.d.avahi-dbus.conf: [modified]
  modified.conffile..etc.default.avahi-daemon: [modified]
  modified.conffile..etc.init.avahi-daemon.conf: [modified]
  modified.conffile..etc.init.d.avahi-daemon: [modified]
  modified.conffile..etc.network.if-up.d.avahi-daemon: [modified]
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2015-11-24T16:30:19
  mtime.conffile..etc.avahi.hosts: 2015-11-24T16:30:19
  mtime.conffile..etc.dbus-1.system.d.avahi-dbus.conf: 2015-11-24T16:30:19
  mtime.conffile..etc.default.avahi-daemon: 2015-11-05T02:33:19
  mtime.conffile..etc.init.avahi-cups-reload.conf: 2015-11-24T14:01:36
  mtime.conffile..etc.init.avahi-daemon.conf: 2015-11-24T14:01:36
  mtime.conffile..etc.init.d.avahi-daemon: 2015-11-05T02:33:19
  mtime.conffile..etc.network.if-up.d.avahi-daemon: 2015-11-05T02:33:19
  mtime.conffile..etc.resolvconf.update-libc.d.avahi-daemon: 2015-11-24T16:30:22

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

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

[Touch-packages] [Bug 1830521] Re: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apparmor package in Ubuntu:
  New

Bug description:
  There is 1 error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   apparmor:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun May 26 12:20:33 2019
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2019-01-29 (116 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d069525a-3d3c-4c29-9f77-9e8a6233320d ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.1
  SourcePackage: apparmor
  Syslog:
   
  Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.abstractions.dovecot-common: [modified]
  modified.conffile..etc.apparmor.d.abstractions.enchant: [modified]
  modified.conffile..etc.apparmor.d.abstractions.fcitx: [modified]
  modified.conffile..etc.apparmor.d.abstractions.fcitx-strict: [modified]
  modified.conffile..etc.apparmor.d.abstractions.launchpad-integration: 
[modified]
  modified.conffile..etc.apparmor.d.abstractions.ldapclient: [modified]
  modified.conffile..etc.apparmor.d.abstractions.nis: [modified]
  modified.conffile..etc.apparmor.d.abstractions.openssl: [modified]
  modified.conffile..etc.apparmor.d.abstractions.orbit2: [modified]
  modified.conffile..etc.apparmor.d.abstractions.p11-kit: [modified]
  modified.conffile..etc.apparmor.d.abstractions.php5:
   #backwards compatibility include, actual abstraction moved from php5 to php
   
   #include 
  modified.conffile..etc.apparmor.d.abstractions.postfix-common: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.X: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apache2-common: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.change_profile: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.examine: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.find_mountpoint: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.introspect: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.apparmor_api.is_enabled: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.aspell: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.audio: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.authentication: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.base: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.bash: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.consoles: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.cups-client: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus-accessibility: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus-accessibility-strict: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus-session: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus-session-strict: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dbus-strict: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dconf: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.dovecot-common: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.enchant: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.fcitx: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.fcitx-strict: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.fonts: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.freedesktop.org: 
2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.gnome: 2018-04-18T01:45:16
  mtime.conffile..etc.apparmor.d.abstractions.gnupg: 2018-04-18T01:45:16
  

[Touch-packages] [Bug 1840970] Re: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: end
  of file on stdin at conffile prompt

Status in ntp package in Ubuntu:
  New

Bug description:
  Ran dist package upgrade, it gave error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185
  Uname: Linux 4.4.0-159-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Aug 21 18:57:08 2019
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-10-17 (308 days ago)
  InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-159-generic 
root=UUID=be9ecdfa-71a7-466d-a56a-7369dfd226db ro consoleblank=0
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.2
   apt  1.6.11
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: end 
of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to bionic on 2019-08-21 (0 days ago)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2018-10-17T11:14:02.816000

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

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

[Touch-packages] [Bug 1598556] Re: package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end
  of file on stdin at conffile prompt

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Error occured while doing release upgrade from 15.10 to 16.04 desktop
  version

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul  3 10:45:20 2016
  DhclientLeases:
   
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2015-09-04 (302 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-41-generic.efi.signed 
root=UUID=394a7cec-3436-4743-b236-ff62b2f11441 ro quiet splash acpi_osi= 
vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12 failed to install/upgrade: end 
of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to xenial on 2016-07-03 (0 days ago)
  mtime.conffile..etc.dhcp.dhclient.conf: 2015-11-23T10:24:22.137341

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

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

[Touch-packages] [Bug 1638675] Re: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in procps package in Ubuntu:
  New

Bug description:
  Not really know of any. Was trying to upgrade 16.04 to 16.10 headless
  home media server. Pressed ctrl+c by mistake during install. All hell
  broke loose.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: procps 2:3.3.12-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 18:37:42 2016
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2013-11-06 (1092 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: procps
  Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)
  mtime.conffile..etc.sysctl.conf: 2014-05-05T12:03:01.086378

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

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

[Touch-packages] [Bug 1677189] Re: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Help me

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Mar 28 18:54:30 2017
  ErrorMessage: end of file on stdin at conffile prompt
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=0ab5d59c-4406-4d9d-b40a-139718895ca0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apparmor
  Syslog:
   Mar 28 18:51:36 Rodrigo-Inspiron dbus[899]: [system] AppArmor D-Bus 
mediation is enabled
   Mar 29 06:42:47 Rodrigo-Inspiron dbus[825]: [system] AppArmor D-Bus 
mediation is enabled
  Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.apparmor.conf: 2016-10-04T17:49:43
  mtime.conffile..etc.init.d.apparmor: 2016-10-04T17:49:43

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

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

[Touch-packages] [Bug 1650729] Re: package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on stdin at conffile prompt

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1520928
   package ... failed to install/upgrade: end of file on stdin at conffile 
prompt

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

Title:
  package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on
  stdin at conffile prompt

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 17 11:51:35 2016
  ErrorMessage: end of file on stdin at conffile prompt
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apt
  Title: package apt 1.2.15ubuntu0.2 failed to install/upgrade: end of file on 
stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900688] Re: dual monitor login screen

[Daniel van Vugt]

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

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 1760849, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1760849
   Login screen appears on only one monitor and it's not the one I want

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

Title:
  dual monitor login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors:
  1: Primary "main" monitor, landscape orientation.
  2: Secondary monitor, "portrait left" rotation (so long axis of monitor is 
vertical).

  I have happily configured monitors for desktop display.

  However at login time, the list of users to log in to the computer is
  on the secondary monitor and is also landscape oriented.  Now because
  this monitor is rotated left 90 degrees in real life, the login window
  is also rotated.  Have to tilt your head 90 degrees left to read it.
  Login window seems not to be picking up the display configuration -
  just assumes both monitors are landscape orientation and does not send
  login options to primary monitor.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:44:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:11d7]
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H110M-H
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=19fe7a97-ae05-4a35-9ff5-6a2c2655e58a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd04/11/2018:svnGigabyteTechnologyCo.,Ltd.:pnH110M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H110M-H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1900688/+subscriptions

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

[Touch-packages] [Bug 1899352] Re: Pulseaudio cannot be kept from starting or respawning

[Daniel van Vugt]

OK those are different filenames to your first comment #3, which is why
they don't exist...

Packages like pulseaudio are intended to support multiple different
distros and "flavours". Sometimes those won't have systemd. So
especially if the package predates systemd, there's no reason to drop
files that support the alternatives. Such files are harmless, mostly
unused, and occasionally useful.

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

Title:
  Pulseaudio cannot be kept from starting or respawning

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  On my freshly installed system, I need to run pulseaudio in system
  mode.  Alas, by default, pulseaudio is run in user mode, and is set to
  respawn, so that I cannot kill the user process and start pulseaudio
  in system mode.

  I tried:

  1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
  2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
  3. I removed the file /usr/bin/start-pulseaudio.  Why   Of course, this 
did nothing.
  4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 
did NOTHING.

  User mode is still starting, and respawning is enabled.

  What the heck do I have to do to get rid of user mode pulseaudio?
  Could you please clean up this clusterfuck?

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

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

[Touch-packages] [Bug 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature

[Nattapong Sirilappanich]

Thanks for your promptly reply. 
I filed the issue here:
https://github.com/ibus/ibus/issues/2271

** Bug watch added: github.com/ibus/ibus/issues #2271
   https://github.com/ibus/ibus/issues/2271

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

Title:
  Ubuntu 20.04 has no capability of surrounding-text feature

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
  After the upgrade, I failed to type Thai text with any combining character in 
some apps.
  The log contains this error message:
  `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 
09:07:10.843: google-chrome-stable has no capability of surrounding-text 
feature`
  `gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

  Expected behavior: Capable of typing any Thai character in any app.
  Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

  Step to reproduce:
  1. Boot up the machine.
  2. Open Google Chrome.
  3. Switch keyboard layout to `Thai (LibThai)`
  4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.

  
  Current workaround:
  Whenever you want to type Thai switch 
  1. Open `Gnome Text Editor`
  2. Switch keyboard layout to `Thai (LibThai)`
  3. Switch to Chrome
  4. Type Thai

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Ranjan]

Yes, on 20.10 beta the bug seems to have been fixed

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1900777] Re: Xorg freeze

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

hard reboot?  if the music is playing the kernel would be running and
thus you should be able to direct kernel via SysRq commands.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1900777/+subscriptions

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

[Touch-packages] [Bug 1900777] Re: Xorg freeze

[Blaise Mariner]

The freeze on this system and the other system was similar. But on this
one, the screen goes black, the music keeps playing and I am unable to
take any actionable steps other than a hard reboot.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1900777/+subscriptions

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

[Touch-packages] [Bug 1900777] [NEW] Xorg freeze

[Blaise Mariner]

Public bug reported:

I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my
2-year-old Dell laptop was the problem. However, I froze during Zoom
yesterday and during coding today after fresh-installing Ubuntu 20.04 on
Sunday. I also froze mid-attempt to submit a bug report after the coding
freeze. Any help is appreciated. Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 17:38:31 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
 amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
 rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
 rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
InstallationDate: Installed on 2020-10-18 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X513IA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X513IA
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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze 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/1900777

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA 

[Touch-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend

[Tim Nolte]

This is still present with Ubuntu 20.04 and the latest XFCE & LightDM.
This is a major pain almost to the point of me wanting to switch back to
GDM & Gnome.

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

Title:
  lightdm does not greet or present login prompt when resuming from
  laptop suspend

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Expected result: when opening laptop lid the lock screen presents
  itself so I can unlock my session

  Actual result: the contents of my desktop are visible (windows, etc)
  and I can move my mouse cursor around but I cannot interact with the
  desktop session at all. Hovering over UI elements or clicking them has
  no effect.

  In order to get the login prompt I have to ctrl+alt+f1, login at the
  console, and run sudo systemctl restart lightdm, then I can login
  normally and resume whatever I was doing from before I closed the
  laptop lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 23 09:08:32 2019
  InstallationDate: Installed on 2019-11-09 (14 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Jay,

The good news is that, with 0.130ubuntu3.11, initramfs-tools is now able
to render a correct netplan YAML file:

# cat /run/netplan/ens3.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
ens3:
  set-name: ens3
  dhcp4: true
  dhcp-identifier: mac
  critical: true
  nameservers:
addresses: ["100.100.100.60", "100.100.100.160"]
search: ["domainname.com"]

However, net_failover 3-netdev interfaces are still showing incorrect
names:

# 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 12:3f:bd:fd:bb:1e brd ff:ff:ff:ff:ff:ff
3: rename3:  mtu 1500 qdisc pfifo_fast master 
ens3 state UP mode DEFAULT group default qlen 1000
link/ether 12:3f:bd:fd:bb:1e 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 12:3f:bd:fd:bb:1e brd ff:ff:ff:ff:ff:ff

while we should expect to see something like:

# ip link show
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 12:3f:bd:fd:bb:1e 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 12:3f:bd:fd:bb:1e brd ff:ff:ff:ff:ff:ff
4: ens4:  mtu 1500 qdisc mq master ens3 state 
UP mode DEFAULT group default qlen 1000
link/ether 12:3f:bd:fd:bb:1e brd ff:ff:ff:ff:ff:ff

The culprit, as I ever indicated before, is that even with the seemingly
correct netplan config provided, the netplan tool itself still doesn't
recognize the 3-netdev failover interface, ending up with below udev
rules renderred that runs conflict with the 3-netdev model:

# cat /run/systemd/network/10-netplan-ens3.link
[Match]
MACAddress=12:3f:bd:fd:bb:1e

[Link]
Name=ens3
WakeOnLan=off

# cat /run/udev/rules.d/99-netplan-ens3.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="12:3f:bd:fd:bb:1e", NAME="ens3"

I understand that the solution we agreed upon has to rely on cloud-init
providing supplemental udev rules for naming the ens3nsby (failover
standby) and the ens4 (failover primary) interface. But, I don't see how
the resulted 99-netplan-ens3.rules would work, given that all the 3
netdevs share a same MAC address, and there's no other udev attribute to
differentiate? What's in your mind that needs to be fixed next, netplan
or udevd?

Thanks,
-Siwei

-- 
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 initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  [Impact]

  * At present, virtual machines utilizing net_failover network
  interface configurations are incorrectly configured due to the
  reliance on the MAC address to identify specific network interfaces.
  When net_failover is utilized, multiple interfaces will bear the same
  MAC address (the net_failover master itself, as well as the interfaces
  subordinate to it), rendering the MAC address ineffective for unique
  identification of the interface.  This results in incorrect naming of
  network interfaces from the "set-name" directive in the netplan
  configuration.

  * The solution here is to use the interface name instead of the MAC
  address when the interface is a net_failover master device.  Logic is
  added on initramfs-tools to check the device type and virtio flags to
  apply this change only to net_failover master devices.

  [Test Case]

  * The change can be tested by configuring a virtual machine with a
  virtio_net network device with the "failover=on" option to the
  "-device" option to qemu, e.g.,

  -device virtio-net-
  
pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on

  * This will set the virtio device "standby" feature bit (bit 62,
  counting from 0).  This requires a version of qemu with support for
  this feature.

  * When so configured, the netplan configuration generated by initramfs
  will not contain a "macaddress:" match directive for the network
  interface in question.

  [Regression Potential]

  * Erroneous identification of a network interface as a net_failover
  master device could lead to omission of a macaddress directive,
  

[Touch-packages] [Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Mauricio Faria de Oliveira]

Hi SRU team,

All autopkgtest failures in #4 are now passing on all architectures.
- gvfs/amd64 was flaky, passed on retry.
- openssh/* needs the test-case fix staged in bionic-proposed;
  passed by adding openssh/1:7.6p1-4ubuntu0.4 to the triggers.

(Thanks @halves for spotting a flaky/false-negative result in #5.)

Results:
---

Version TriggersDateDurationRequester
Result

gvfs/amd64 [1]
1.36.1-0ubuntu1.3.3 sudo/1.8.21p2-3ubuntu1.32020-10-08 13:45:28 UTC 
0h 04m 00s  mfo pass

openssh/amd64 [2]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 19:27:35 UTC 0h 19m 30s  mfo pass

openssh/arm64 [3]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 20:29:37 UTC 0h 32m 55s  mfo pass

openssh/armhf [4]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 20:43:55 UTC 0h 42m 08s  mfo pass

openssh/i386 [5]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 20:19:33 UTC 0h 21m 36s  mfo pass

openssh/ppc64el [6]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 20:22:09 UTC 0h 20m 32s  mfo pass

openssh/s390x [7]
1:7.6p1-4ubuntu0.4  sudo/1.8.21p2-3ubuntu1.3 openssh/1:7.6p1-4ubuntu0.4 
2020-10-20 20:13:52 UTC 0h 16m 22s  mfo pass

[1] https://autopkgtest.ubuntu.com/packages/gvfs/bionic/amd64
[2] https://autopkgtest.ubuntu.com/packages/openssh/bionic/amd64
[3] https://autopkgtest.ubuntu.com/packages/openssh/bionic/arm64
[4] https://autopkgtest.ubuntu.com/packages/openssh/bionic/armhf
[5] https://autopkgtest.ubuntu.com/packages/openssh/bionic/i386
[6] https://autopkgtest.ubuntu.com/packages/openssh/bionic/ppc64el
[7] https://autopkgtest.ubuntu.com/packages/openssh/bionic/s390x

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  sudo commands can hang when IO logging is enabled

  [Description]
  When doing cleanup in pty_close(), sudo can leave file descriptors and events
  behind that would later cause poll() to wait on a "dead" pty. This can cause
  sudo to hang when IO logging is enabled, due to the poll() timeouts.

  The issue has been fixed upstream by the commit below:
  - In pty_close() close the slave and remove any events associated 
(4df454310dae)

  $ git describe --contains 4df454310dae96d01d09a05be89dc8c57fd4cef7
  SUDO_1_8_23

  $ rmadison sudo
   sudo | 1.8.16-0ubuntu1 | xenial   | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-security  | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-updates   | source, ...
   sudo | 1.8.21p2-3ubuntu1   | bionic   | source, ...
   sudo | 1.8.21p2-3ubuntu1.2 | bionic-security  | source, ...
   => sudo | 1.8.21p2-3ubuntu1.2 | bionic-updates   | source, ... <
   sudo | 1.8.31-1ubuntu1 | focal| source, ...
   sudo | 1.8.31-1ubuntu1.1   | focal-updates| source, ...
   sudo | 1.9.1-1ubuntu1  | groovy   | source, ...

  Xenial doesn't exhibit this behaviour, so fixes are only needed for Bionic
  (Focal onwards already have the fix by default due to sudo version).

  [Test Case]

  1. Ensure /etc/sudoers contains 'Defaults use_pty'
  2. Execute the following test command:
  $ for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal will hang during syslog output.

  [Regression Potential]
  The fix introduces additional cleaning when closing/flushing pty devices, so 
the
  regression potential should be low. It has been present upstream since
  sudo-1.8.23, so it has seen thorough testing in most Linux distributions
  including Ubuntu.

  A regression could possibly cause issues when switching back out from sudo
  sessions, as the changes only touch the pty_close path, but seems unlikely
  considering the patch has been present in other Ubuntu releases as well.

  --
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running a 
command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at 

[Touch-packages] [Bug 1664846] Re: [Wishlist] Support for teaming driver

[Josh England]

I'm curious if there has been any movement on this.  We switched to
using the 'team' driver over the 'bonding' driver some time ago.  Having
an abstracted network configuration capability through netplan would be
very nice.

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

Title:
  [Wishlist] Support for teaming driver

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

Bug description:
  The MAAS team is supporting a customer who is using the 'teaming'
  driver rather than the 'bonding' driver. This is essentially a bonding
  driver which also delivers some additional features, and has
  additional userspace runtime control.

  Netplan should allow for bonds to be configured with the teaming
  driver in addition to the bonding driver.

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

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

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted zlib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zlib/1:1.2.11.dfsg-
2ubuntu1.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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: zlib (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Committed
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

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

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

[Touch-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

[Brian Murray]

Hello Amr, or anyone else affected,

Accepted libgweather into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.36.1-1~ubuntu20.04.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: libgweather (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  Fix Committed
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Executenor]

@Javier
That is weird that laptop does not have a intel bluetooth/wifi chip? I own one 
too as a private laptop and it has a qualcomm that should not be affected by 
this bug. Can you please post which chipset is has? Maybe Dell released one 
with an intel chipset too.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1900748] Re: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'

[Guruprasad]

Uninstalling the older, unused kernel packages doesn't help because zsys
takes snapshots of the boot pool before the removal and still eats up a
comparable amount of space, thereby not solving the problem at all.

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

Title:
  update-initramfs fails with an error 'Error 24 : Write error : cannot
  write compressed block'

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard
  disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk
  installation using the latest installer ISO available on the Ubuntu
  releases site.

  After installation, I booted into the installed OS and tried to
  install all the package updates. It went mostly fine till when it
  tried to run the update-initramfs operation and failed. Below are the
  relevant messages printed to the console.

  
  Setting up initramfs-tools (0.137ubuntu12) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  ZSys is adding automatic system snapshot to GRUB menu
  

  I checked the free disk space to ensure that there is enough
  available.

  
  guruprasad@groovy:~$ df -h
  FilesystemSize  Used Avail Use% 
Mounted on
  tmpfs 796M  1.5M  795M   1% /run
  /dev/mapper/keystore-rpool453M  748K  419M   1% 
/run/keystore/rpool
  rpool/ROOT/ubuntu_slz5nq  6.0G  3.9G  2.1G  66% /
  tmpfs 3.9G   33M  3.9G   1% 
/dev/shm
  tmpfs 5.0M  4.0K  5.0M   1% 
/run/lock
  tmpfs 4.0M 0  4.0M   0% 
/sys/fs/cgroup
  bpool/BOOT/ubuntu_slz5nq  268M  197M   71M  74% /boot
  rpool/USERDATA/guruprasad_bdqa1x  2.1G   32M  2.1G   2% 
/home/guruprasad
  /dev/sda2 512M   19M  494M   4% 
/boot/efi
  rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G  384K  2.1G   1% 
/var/snap
  rpool/ROOT/ubuntu_slz5nq/usr/local2.1G  512K  2.1G   1% 
/usr/local
  rpool/ROOT/ubuntu_slz5nq/srv  2.1G  256K  2.1G   1% /srv
  rpool/ROOT/ubuntu_slz5nq/var/lib  3.0G  933M  2.1G  31% 
/var/lib
  rpool/ROOT/ubuntu_slz5nq/var/www  2.1G  256K  2.1G   1% 
/var/www
  rpool/USERDATA/root_bdqa1x2.1G  256K  2.1G   1% /root
  rpool/ROOT/ubuntu_slz5nq/var/log  2.1G   25M  2.1G   2% 
/var/log
  rpool/ROOT/ubuntu_slz5nq/var/spool2.1G  384K  2.1G   1% 
/var/spool
  rpool/ROOT/ubuntu_slz5nq/var/games2.1G  256K  2.1G   1% 
/var/games
  rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G  256K  2.1G   1% 
/var/mail
  rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService  2.1G  384K  2.1G   1% 
/var/lib/AccountsService
  rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager   2.1G  256K  2.1G   1% 
/var/lib/NetworkManager
  rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G   59M  2.1G   3% 
/var/lib/dpkg
  rpool/ROOT/ubuntu_slz5nq/var/lib/apt  2.2G   77M  2.1G   4% 
/var/lib/apt
  tmpfs 796M  188K  796M   1% 
/run/user/1000
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: initramfs-tools 0.137ubuntu12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 23:05:25 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  PackageArchitecture: all
  RebootRequiredPkgs:
   evolution-data-server
   gnome-shell
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900396] Re: netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

[Lucas Kanashiro]

Thanks for taking the time and trying to make Ubuntu better.

I am not sure if I understood your problem here. All the options you
mentioned are in the netstat manpage, they are listed in the SYNOPSIS
section and also OUTPUT section as "Active Internet connections (TCP,
UDP, raw)". They are not regular options, they are used to specify the
connection type.

I do not consider this as an Ubuntu bug, if you think more explanation
is required you should get in touch with upstream. I marking this bug as
Invalid, if you do not agree or you have more info to provide please do
it and put the status back to NEW.

** Changed in: net-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

Status in net-tools package in Ubuntu:
  Invalid

Bug description:
  I tried looking up `netstat -tlnp` on https://explainshell.com, but
  there was no explanation for `-t`. It turns out that at least
  `-t|--tcp`, `-u|--udp` and `-w|--raw` aren't documented in the man-
  page
  (http://manpages.ubuntu.com/manpages/precise/en/man8/netstat.8.html).

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

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

[Touch-packages] [Bug 1900748] Re: update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'

[Guruprasad]

This appears to be because of the limited remaining space in the /boot
partition but the partition layout and sizes were automatically
configured by the Ubuntu installer, which seems to be the culprit here.

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

Title:
  update-initramfs fails with an error 'Error 24 : Write error : cannot
  write compressed block'

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard
  disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk
  installation using the latest installer ISO available on the Ubuntu
  releases site.

  After installation, I booted into the installed OS and tried to
  install all the package updates. It went mostly fine till when it
  tried to run the update-initramfs operation and failed. Below are the
  relevant messages printed to the console.

  
  Setting up initramfs-tools (0.137ubuntu12) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  ZSys is adding automatic system snapshot to GRUB menu
  

  I checked the free disk space to ensure that there is enough
  available.

  
  guruprasad@groovy:~$ df -h
  FilesystemSize  Used Avail Use% 
Mounted on
  tmpfs 796M  1.5M  795M   1% /run
  /dev/mapper/keystore-rpool453M  748K  419M   1% 
/run/keystore/rpool
  rpool/ROOT/ubuntu_slz5nq  6.0G  3.9G  2.1G  66% /
  tmpfs 3.9G   33M  3.9G   1% 
/dev/shm
  tmpfs 5.0M  4.0K  5.0M   1% 
/run/lock
  tmpfs 4.0M 0  4.0M   0% 
/sys/fs/cgroup
  bpool/BOOT/ubuntu_slz5nq  268M  197M   71M  74% /boot
  rpool/USERDATA/guruprasad_bdqa1x  2.1G   32M  2.1G   2% 
/home/guruprasad
  /dev/sda2 512M   19M  494M   4% 
/boot/efi
  rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G  384K  2.1G   1% 
/var/snap
  rpool/ROOT/ubuntu_slz5nq/usr/local2.1G  512K  2.1G   1% 
/usr/local
  rpool/ROOT/ubuntu_slz5nq/srv  2.1G  256K  2.1G   1% /srv
  rpool/ROOT/ubuntu_slz5nq/var/lib  3.0G  933M  2.1G  31% 
/var/lib
  rpool/ROOT/ubuntu_slz5nq/var/www  2.1G  256K  2.1G   1% 
/var/www
  rpool/USERDATA/root_bdqa1x2.1G  256K  2.1G   1% /root
  rpool/ROOT/ubuntu_slz5nq/var/log  2.1G   25M  2.1G   2% 
/var/log
  rpool/ROOT/ubuntu_slz5nq/var/spool2.1G  384K  2.1G   1% 
/var/spool
  rpool/ROOT/ubuntu_slz5nq/var/games2.1G  256K  2.1G   1% 
/var/games
  rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G  256K  2.1G   1% 
/var/mail
  rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService  2.1G  384K  2.1G   1% 
/var/lib/AccountsService
  rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager   2.1G  256K  2.1G   1% 
/var/lib/NetworkManager
  rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G   59M  2.1G   3% 
/var/lib/dpkg
  rpool/ROOT/ubuntu_slz5nq/var/lib/apt  2.2G   77M  2.1G   4% 
/var/lib/apt
  tmpfs 796M  188K  796M   1% 
/run/user/1000
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: initramfs-tools 0.137ubuntu12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 23:05:25 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  PackageArchitecture: all
  RebootRequiredPkgs:
   evolution-data-server
   gnome-shell
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900748] [NEW] update-initramfs fails with an error 'Error 24 : Write error : cannot write compressed block'

[Guruprasad]

Public bug reported:

On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard
disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk
installation using the latest installer ISO available on the Ubuntu
releases site.

After installation, I booted into the installed OS and tried to install
all the package updates. It went mostly fine till when it tried to run
the update-initramfs operation and failed. Below are the relevant
messages printed to the console.


Setting up initramfs-tools (0.137ubuntu12) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.137ubuntu12) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-25-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 initramfs-tools
ZSys is adding automatic system snapshot to GRUB menu


I checked the free disk space to ensure that there is enough available.


guruprasad@groovy:~$ df -h
FilesystemSize  Used Avail Use% Mounted 
on
tmpfs 796M  1.5M  795M   1% /run
/dev/mapper/keystore-rpool453M  748K  419M   1% 
/run/keystore/rpool
rpool/ROOT/ubuntu_slz5nq  6.0G  3.9G  2.1G  66% /
tmpfs 3.9G   33M  3.9G   1% /dev/shm
tmpfs 5.0M  4.0K  5.0M   1% 
/run/lock
tmpfs 4.0M 0  4.0M   0% 
/sys/fs/cgroup
bpool/BOOT/ubuntu_slz5nq  268M  197M   71M  74% /boot
rpool/USERDATA/guruprasad_bdqa1x  2.1G   32M  2.1G   2% 
/home/guruprasad
/dev/sda2 512M   19M  494M   4% 
/boot/efi
rpool/ROOT/ubuntu_slz5nq/var/snap 2.1G  384K  2.1G   1% 
/var/snap
rpool/ROOT/ubuntu_slz5nq/usr/local2.1G  512K  2.1G   1% 
/usr/local
rpool/ROOT/ubuntu_slz5nq/srv  2.1G  256K  2.1G   1% /srv
rpool/ROOT/ubuntu_slz5nq/var/lib  3.0G  933M  2.1G  31% /var/lib
rpool/ROOT/ubuntu_slz5nq/var/www  2.1G  256K  2.1G   1% /var/www
rpool/USERDATA/root_bdqa1x2.1G  256K  2.1G   1% /root
rpool/ROOT/ubuntu_slz5nq/var/log  2.1G   25M  2.1G   2% /var/log
rpool/ROOT/ubuntu_slz5nq/var/spool2.1G  384K  2.1G   1% 
/var/spool
rpool/ROOT/ubuntu_slz5nq/var/games2.1G  256K  2.1G   1% 
/var/games
rpool/ROOT/ubuntu_slz5nq/var/mail 2.1G  256K  2.1G   1% 
/var/mail
rpool/ROOT/ubuntu_slz5nq/var/lib/AccountsService  2.1G  384K  2.1G   1% 
/var/lib/AccountsService
rpool/ROOT/ubuntu_slz5nq/var/lib/NetworkManager   2.1G  256K  2.1G   1% 
/var/lib/NetworkManager
rpool/ROOT/ubuntu_slz5nq/var/lib/dpkg 2.2G   59M  2.1G   3% 
/var/lib/dpkg
rpool/ROOT/ubuntu_slz5nq/var/lib/apt  2.2G   77M  2.1G   4% 
/var/lib/apt
tmpfs 796M  188K  796M   1% 
/run/user/1000


ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: initramfs-tools 0.137ubuntu12
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 23:05:25 2020
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
PackageArchitecture: all
RebootRequiredPkgs:
 evolution-data-server
 gnome-shell
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  update-initramfs fails with an error 'Error 24 : Write error : cannot
  write compressed block'

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On a VirtualBox 6.1.14 VM with 2 vCPUs and 8 GB RAM and a 10 GiB hard
  disk space, I installed Ubuntu 20.10 with ZFS enabled on a full disk
  installation using the latest installer ISO available on the Ubuntu
  releases site.

  After installation, I booted into the installed OS and tried to
  install all the package updates. It went mostly fine till when it
  tried to run the update-initramfs operation and failed. Below are the
  relevant messages 

[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

[Linux Admin]

After upgrade to Ubuntu 20.04 most KDE native apps are now crashing and
this includes systemsettings5. segfault stacktrace points to crash in
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so

> inxi -G
Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel 
   Display: x11 server: X.Org 1.20.8 driver: intel resolution: 
3440x1440~60Hz 
   OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 
20.1.8 

xserver-xorg-video-intel version 2:2.99.917+git20200226-1

Setting MESA_LOADER_DRIVER_OVERRIDE=i965 does resolve this issue
completely, however I am wondering why this is not selected
automatically if iris driver does not support my GPU.

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

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in ring package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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

[Touch-packages] [Bug 1900349] Re: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48

[Corbin]

After updating again, the bug is gone. I will be closing the bug report

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

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

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

Title:
  [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but
  does in 5.4.0-48

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

Bug description:
  While pusleaudio works properly on gdm before logging in, once I
  login, it fails. I was able to successfully restart pulseaudio with
  pulseaudio -k on my first attempt, and one other time, but I have been
  unable to reproduce this. It (pulseaudio -k )usually does nothing. As
  such, adding "pulseaudio -k" to run on on login as a workaround does
  not work. This started happening after updating from kernel 5.4.0-48
  to 5.4.0-52. Rolling back to 48 makes the issue go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 18 14:11:31 2020
  InstallationDate: Installed on 2020-07-03 (107 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1900727] [NEW] Update ca-certificates with latest NSS roots

[Quentin Bracken]

Public bug reported:

Please refresh the default ca-certificates package with the latest NSS
roots?

Specifically, we would like to ensure these two roots from NSS 3.54 (26
June 2020) are included in the package:

Bug 1641716 - Microsoft ECC Root Certificate Authority 2017
SHA-256 Fingerprint: 
358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02

Bug 1641716 - Microsoft RSA Root Certificate Authority 2017
SHA-256 Fingerprint: 
C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0

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

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

Title:
  Update ca-certificates with latest NSS roots

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Please refresh the default ca-certificates package with the latest NSS
  roots?

  Specifically, we would like to ensure these two roots from NSS 3.54
  (26 June 2020) are included in the package:

  Bug 1641716 - Microsoft ECC Root Certificate Authority 2017
  SHA-256 Fingerprint: 
358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02

  Bug 1641716 - Microsoft RSA Root Certificate Authority 2017
  SHA-256 Fingerprint: 
C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0

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

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

[Touch-packages] [Bug 1900349] Re: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48

[Corbin]

I am not certain the kernel is the cause, I just noticed the bug
manifested when I updated. I will upload apport logs. I don't actually
believe it is a kernel bug, because PA works properly on the login
screen and only fails after login.

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

Title:
  [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but
  does in 5.4.0-48

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

Bug description:
  While pusleaudio works properly on gdm before logging in, once I
  login, it fails. I was able to successfully restart pulseaudio with
  pulseaudio -k on my first attempt, and one other time, but I have been
  unable to reproduce this. It (pulseaudio -k )usually does nothing. As
  such, adding "pulseaudio -k" to run on on login as a workaround does
  not work. This started happening after updating from kernel 5.4.0-48
  to 5.4.0-52. Rolling back to 48 makes the issue go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 18 14:11:31 2020
  InstallationDate: Installed on 2020-07-03 (107 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Sebastien Bacher]

Thanks for the report and adding some details, it's still unclear what
the testcase and issue is though. If the problem that due to the patch
it errors out in cases where it should return an empty list? Or that
it's giving access to more information that it should?

Could you also give a testcase including steps that could be used for
testing by others who are not especially familiar with the issue?
something along the lines of

- 
- 
- 

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

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

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

[Touch-packages] [Bug 1899352] Re: Pulseaudio cannot be kept from starting or respawning

[ralphb]

The package "pulseaudio" contains the files:

/usr/bin/start-pulseaudio-x11
/etc/pulse/client.conf.d/01-enable-autospawn.conf

Thus, it should be fairly obvious where I got the files from.

And /etc/pulse/client.conf is ignored, despite my user (and root) not
having a ~/.local/pulse directory.

And why would we need files for non-systemd systems if Ubuntu _is_ a
systemd-base system?

So I still think something is quite wrong with the pulseaudio package.

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

Title:
  Pulseaudio cannot be kept from starting or respawning

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  On my freshly installed system, I need to run pulseaudio in system
  mode.  Alas, by default, pulseaudio is run in user mode, and is set to
  respawn, so that I cannot kill the user process and start pulseaudio
  in system mode.

  I tried:

  1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
  2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
  3. I removed the file /usr/bin/start-pulseaudio.  Why   Of course, this 
did nothing.
  4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 
did NOTHING.

  User mode is still starting, and respawning is enabled.

  What the heck do I have to do to get rid of user mode pulseaudio?
  Could you please clean up this clusterfuck?

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

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

[Touch-packages] [Bug 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature

[Gunnar Hjalmarsson]

Thanks for your report. I could reproduce it, both on 20.04 and 20.10
(the latter with ibus 1.5.23).

This is probably an upstream problem, and it would be great if you could
submit an upstream issue:

https://github.com/ibus/ibus/issues/

If you do, please post the URL to the upstream issue in a comment here
for tracking purposes.

P.S. The issue was not present when I used the Thai XKB layout.

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Ubuntu 20.04 has no capability of surrounding-text feature

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
  After the upgrade, I failed to type Thai text with any combining character in 
some apps.
  The log contains this error message:
  `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 
09:07:10.843: google-chrome-stable has no capability of surrounding-text 
feature`
  `gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

  Expected behavior: Capable of typing any Thai character in any app.
  Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

  Step to reproduce:
  1. Boot up the machine.
  2. Open Google Chrome.
  3. Switch keyboard layout to `Thai (LibThai)`
  4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.

  
  Current workaround:
  Whenever you want to type Thai switch 
  1. Open `Gnome Text Editor`
  2. Switch keyboard layout to `Thai (LibThai)`
  3. Switch to Chrome
  4. Type Thai

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

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

[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings

[Brian Murray]

** Tags added: rls-hh-incoming

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

Title:
  private master bugs are confusing and lead to more duplicate filings

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  Apport currently tracks the master bug as a private bug visible only
  to Ubuntu developers (bugcontrol) and makes duplicate bugs public
  after stripping their data.

  This works well but has some downsides:
   - Launchpad cannot show the master bug to folk reporting bugs via apport (so 
they file new bugs always)
   - After users file a new bug apport detects its a duplicate and then they 
cannot see the master bug and get frustrated.

  It would be nice to have:
   - the master bug be public so that reporters of dups can see it in the dupe 
finder and can see if a dupe is detected post-filing.
   - Developers still have easy access to the raw crash data.
    - One way to do that that does not need much development would be to have a 
private bug exist, linked from the master bug (e.g. with a comment or in the 
description; something like 'Confidential crashdump for this bug is attached to 
bug 12345 - only visible to Ubuntu developers').

  One way to achieve this is to have apport file a new public bug to be
  the master. This would have the necessary metadata and would include
  the link to the private bug + gather all the duplicates to itself. One
  downside is that Apport would appear to be the bug reporter for all
  crashdump based bug reports. That's not necessarily a bad thing, but
  it may confuse people.

  Another way would be to have apport file a new private bug, move the
  attachments over from the original bug, add explanation and metadata
  in the description, subscribe bugcontrol and then sanitise the
  original bug report the same way it sanitises public bugs today. This
  would make the original bug be the public master, preserving the date
  of filing and the reporter. OTOH large files would need to be shuffled
  around and this might be unreliable.

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-10-20 08:53 EDT---
IBM Buzgilla -> closed, Fix Released with all requested distros

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

Title:
  [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not
  gzip/zlib) streams

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  zlib on s390x may produce incomplete raw (but not gzip/zlib) streams

  ---uname output---
  Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x 
#1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Create a raw (negative windowBits value) stream with zlib. EOBS might be 
missing or truncated.


  This affects all distro levels that contain hardware acceleration
  (DFLTCC) patch. I've attached the preliminary fix.

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-10-20 08:50 EDT---
IBM Bugzilla closed, Fix Released with all requested distros

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This SRU fixes a combination of multiple issues:

   * zlib DFLTCC compression level switching can corrupt data because
  hardware and software compression states become desynchronized. (LP
  1893170)

   * Since zlib is not working on all s390x system configurations
  support for switching between software and hardware compression is
  required especially for Java. (LP 1882494)

   * zlib on s390x may produce incomplete raw streams (but not
  gzip/zlib). (LP 1889059)

  [Test Case]

   * Since especially DFLTCC requires a s390x generation z15 or LinuxONE
  III the tests need to be done by IBM.

   * IBM has a set of tests available, that exercise public zlib APIs by
  calling them in different sequences with different buffer sizes and
  flush modes.

  * Partially these come from the IBM z/OS team, who developed their own
  zlib support for the hardware accelerator, and partially they are
  developed by the IBM Linux team based on issues encountered during
  development as well as fuzzing.

  * IBM also uses the zlib-ng test-suite as well as squash and stress-
  ng.

   * Compress data using zlib/DFLTCC with different compression level
  and verify state and if data got corrupted or not. (LP 1893170)

   * On a system with patched zlib package, switch between hardware and
  software compression and use zlib via the java.util.zip package
  (http://java.sun.com/developer/technicalArticles/Programming/compression/).
  (LP 1882494)

  * On a z15 system with hardware acceleration compression (DFLTCC)
  enabled, create a raw (negative windowBits value) stream with zlib.
  Then check if EOBS is missing or truncated. (LP 1889059)

  [Regression Potential]

   * There is a certain risk for regressions with the modifications that
  are introduced by the four LP bugs.

   * In case the package fails entirely, it will have (in worst case) an
  impact on all zlib, gzip and DFLTCC compression/decompression
  functions, that are very wide spread (gzip, tar cfz, everything with
  zlib) in Linux and would virtually make the system unusable.

   * If potential issues are limited to hardware assisted compression
  (which is more likely, since these patches are mostly about hw
  assisted compression), then issues would be limited to systems that
  provide this feature (latest s390x generation only).

  * A switch back to software got introduced (by setting DFLTCC=0
  environment variable) that will help to mitigate a potential negative
  impact of the hw assisted compression.

   * Only the latest s390x generation (z15 and LinuxONE III) supports
  hardware assisted DFLTCC and is potentially affected.

   * A patched test package was made available and got successfully
  tested by IBM. All four bugs were finally considered as solved with
  zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here:
  
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib

  __

  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
     does not accept patches at the moment, the fix has been
     integrated into the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
     discovered using example_call_fuzzer from:
     https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

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

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

[Touch-packages] [Bug 1653635] Re: cmake unable to report INCLUDE_DIRS and LIBRARIES

[Gianfranco Costamagna]

Hello, as workaround, using pkg-config to detect it should work
pkg_search_module(JSONCPP jsoncpp)

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

Title:
  cmake unable to report INCLUDE_DIRS and LIBRARIES

Status in libjsoncpp package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ dpkg -l|grep libjsoncpp
  ii  libjsoncpp-dev:amd64   1.7.2-1
   amd64library for reading and writing JSON for C++ (devel 
files)
  ii  libjsoncpp1:amd64  1.7.2-1
   amd64library for reading and writing JSON for C++

  When try to use jsoncpp, the ${jsoncpp_INCLUDE_DIRS} and
  ${jsoncpp_LIBRARIES} fail to report.

  CMakeLists.txt
  
  cmake_minimum_required(VERSION 2.6.2)
  project(jsoncpp_test)

  find_package(jsoncpp REQUIRED)
  message("FOUND CONFIG: ${jsoncpp_CONFIG}")
  message("INCLUDE DIRS: ${jsoncpp_INCLUDE_DIRS}")
  message("LIBRARIES: ${jsoncpp_LIBRARIES}")

  The actual result is:
  
  FOUND CONFIG: /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake
  INCLUDE DIRS: 
  LIBRARIES:

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

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

[Touch-packages] [Bug 1900688] Re: dual monitor login screen

[Ubuntu Foundations Team Bug Bot]

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

Title:
  dual monitor login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors:
  1: Primary "main" monitor, landscape orientation.
  2: Secondary monitor, "portrait left" rotation (so long axis of monitor is 
vertical).

  I have happily configured monitors for desktop display.

  However at login time, the list of users to log in to the computer is
  on the secondary monitor and is also landscape oriented.  Now because
  this monitor is rotated left 90 degrees in real life, the login window
  is also rotated.  Have to tilt your head 90 degrees left to read it.
  Login window seems not to be picking up the display configuration -
  just assumes both monitors are landscape orientation and does not send
  login options to primary monitor.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:44:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:11d7]
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H110M-H
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=19fe7a97-ae05-4a35-9ff5-6a2c2655e58a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd04/11/2018:svnGigabyteTechnologyCo.,Ltd.:pnH110M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H110M-H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1900688/+subscriptions

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

[Touch-packages] [Bug 1900688] [NEW] dual monitor login screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have two monitors:
1: Primary "main" monitor, landscape orientation.
2: Secondary monitor, "portrait left" rotation (so long axis of monitor is 
vertical).

I have happily configured monitors for desktop display.

However at login time, the list of users to log in to the computer is on
the secondary monitor and is also landscape oriented.  Now because this
monitor is rotated left 90 degrees in real life, the login window is
also rotated.  Have to tilt your head 90 degrees left to read it.  Login
window seems not to be picking up the display configuration - just
assumes both monitors are landscape orientation and does not send login
options to primary monitor.

Description:Ubuntu 20.04.1 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 21:44:32 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:11d7]
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Gigabyte Technology Co., Ltd. H110M-H
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=19fe7a97-ae05-4a35-9ff5-6a2c2655e58a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F24
dmi.board.asset.tag: Default string
dmi.board.name: H110M-H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd04/11/2018:svnGigabyteTechnologyCo.,Ltd.:pnH110M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: H110M-H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
dual monitor login screen
https://bugs.launchpad.net/bugs/1900688
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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[Julian Andres Klode]

as in, the fix for this bug does not fix the Debian one.

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  In Progress
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in apt source package in Focal:
  Triaged
Status in glibc source package in Focal:
  Invalid
Status in apt package in Debian:
  Unknown

Bug description:
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[Julian Andres Klode]

@Balint The Debian bug is different - it's single arch

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  In Progress
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in apt source package in Focal:
  Triaged
Status in glibc source package in Focal:
  Invalid
Status in apt package in Debian:
  Unknown

Bug description:
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[Balint Reczey]

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

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

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  In Progress
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in apt source package in Focal:
  Triaged
Status in glibc source package in Focal:
  Invalid
Status in apt package in Debian:
  Unknown

Bug description:
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900135] Re: Bluetooth headsets (mostly Sony) are not working HSP/HFP mode

[Otkar Doetker]

Sony WH-1000XM2 
Switch from HSP/HSF -> A2DP:

Oct 20 12:25:08 gandalf-the-white gnome-shell[2705]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3200199 for override-redirect window 0x3200db9 is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the root window.
Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Supervising 7 threads of 
2 processes of 2 users.
Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Successfully made thread 
129874 of process 2457 owned by '1000' RT at priority 5.
Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Supervising 8 threads of 
2 processes of 2 users.
Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_sink.70_26_05_29_7A_44.headset_head_unit"
Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_sink.70_26_05_29_7A_44.headset_head_unit"
Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_source.70_26_05_29_7A_44.headset_head_unit"
Oct 20 12:25:09 gandalf-the-white gsd-media-keys[2843]: Unable to get default 
sink
Oct 20 12:25:09 gandalf-the-white gsd-media-keys[2843]: Unable to get default 
source
Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.a2dp_sink"


Switch from A2DP to HSP/HSF:
Oct 20 12:25:50 gandalf-the-white gnome-shell[2705]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3200199 for override-redirect window 0x32010c6 is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the root window.
Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Supervising 7 threads of 
2 processes of 2 users.
Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Successfully made thread 
129888 of process 2457 owned by '1000' RT at priority 5.
Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Supervising 8 threads of 
2 processes of 2 users.
Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.a2dp_sink"
Oct 20 12:25:52 gandalf-the-white gsd-media-keys[2843]: Unable to get default 
sink
Oct 20 12:25:52 gandalf-the-white gsd-media-keys[2843]: Unable to get default 
source
Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_sink.70_26_05_29_7A_44.headset_head_unit"
Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_source.70_26_05_29_7A_44.headset_head_unit"
Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: 
org.kde.pulseaudio: No object for name 
"bluez_source.70_26_05_29_7A_44.headset_head_unit"

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

Title:
  Bluetooth headsets (mostly Sony) are not working HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sony WH-1000XM2 and Taotronics SoundLiberty 53 are both not working in
  headset mode, but do in A2DP mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marc   2635 F pulseaudio
   /dev/snd/controlC0:  marc   2635 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 13:06:42 2020
  InstallationDate: Installed on 2020-06-13 (124 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.07.23
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxTM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.07.23:bd04/09/2019:svnNotebook:pnP7xxTM1:pvrNotApplicable:rvnNotebook:rnP7xxTM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxTM1
  dmi.product.sku: Not Applicable
  

[Touch-packages] [Bug 1898729] Re: shim can end up being removed

[Julian Andres Klode]

** Changed in: shim (Ubuntu Focal)
   Status: Confirmed => Won't Fix

** Changed in: shim (Ubuntu Focal)
   Status: Won't Fix => New

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

** Also affects: shim-signed (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: shim (Ubuntu)

** No longer affects: apt (Ubuntu)

** No longer affects: apt (Ubuntu Focal)

** No longer affects: apt (Ubuntu Groovy)

** No longer affects: shim (Ubuntu Focal)

** No longer affects: shim (Ubuntu Groovy)

** Changed in: shim-signed (Ubuntu Groovy)
   Status: New => Triaged

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

Title:
  shim can end up being removed

Status in shim-signed package in Ubuntu:
  Triaged
Status in shim-signed source package in Focal:
  New
Status in shim-signed source package in Groovy:
  Triaged

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1898729/+subscriptions

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

[Touch-packages] [Bug 1898729] Re: shim can end up being removed

[Launchpad Bug Tracker]

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

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

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

Title:
  shim can end up being removed

Status in shim-signed package in Ubuntu:
  Triaged
Status in shim-signed source package in Focal:
  New
Status in shim-signed source package in Groovy:
  Triaged

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1898729/+subscriptions

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

[Touch-packages] [Bug 1898729] Re: shim can end up being removed

[Launchpad Bug Tracker]

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

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

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

Title:
  shim can end up being removed

Status in shim-signed package in Ubuntu:
  Triaged
Status in shim-signed source package in Focal:
  New
Status in shim-signed source package in Groovy:
  Triaged

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1898729/+subscriptions

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

[Touch-packages] [Bug 1898729] Re: shim can end up being removed

[Launchpad Bug Tracker]

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

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

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

Title:
  shim can end up being removed

Status in shim-signed package in Ubuntu:
  Triaged
Status in shim-signed source package in Focal:
  New
Status in shim-signed source package in Groovy:
  Triaged

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1898729/+subscriptions

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

[Touch-packages] [Bug 1898729] Re: shim can end up being removed

[Launchpad Bug Tracker]

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

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

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

Title:
  shim can end up being removed

Status in shim-signed package in Ubuntu:
  Triaged
Status in shim-signed source package in Focal:
  New
Status in shim-signed source package in Groovy:
  Triaged

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1898729/+subscriptions

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

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

[Dimitri John Ledkov]

** No longer affects: ubuntu-release-notes

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

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

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

[Touch-packages] [Bug 1900670] Re: vimdiff confuses lines

[Rostislav]

Here are the files.

Thnk you!

** Attachment added: "files for the vimdiff example"
   
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1900670/+attachment/5424568/+files/vimbug.tar.gz

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

Title:
  vimdiff confuses lines

Status in vim package in Ubuntu:
  New

Bug description:
  I try to see diff of two files in my Ubuntu 20.04.

  $ vimdiff outlog_20201020082321-head.log
  outlog_20201020084056-head.log

  The diff matches wrong lines and highlights them strangely..
  Reproducible with removed ~/.vimrc and ~/.vim.

  $ vim --version
  VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
  Included patches: 1-2269
  Modified by team+...@tracker.debian.org
  Compiled by team+...@tracker.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl   -farsi -mouse_sysmouse-tag_any_white
  +arabic+file_in_path  +mouse_urxvt   -tcl
  +autocmd   +find_in_path  +mouse_xterm   +termguicolors
  +autochdir +float +multi_byte+terminal
  -autoservername+folding   +multi_lang+terminfo
  -balloon_eval  -footer-mzscheme  +termresponse
  +balloon_eval_term +fork()+netbeans_intg +textobjects
  -browse+gettext   +num64 +textprop
  ++builtin_terms-hangul_input  +packages  +timers
  +byte_offset   +iconv +path_extra+title
  +channel   +insert_expand -perl  -toolbar
  +cindent   +job   +persistent_undo   +user_commands
  -clientserver  +jumplist  +postscript+vartabs
  -clipboard +keymap+printer   +vertsplit
  +cmdline_compl +lambda+profile   +virtualedit
  +cmdline_hist  +langmap   -python+visual
  +cmdline_info  +libcall   +python3   +visualextra
  +comments  +linebreak +quickfix  +viminfo
  +conceal   +lispindent+reltime   +vreplace
  +cryptv+listcmds  +rightleft +wildignore
  +cscope+localmap  -ruby  +wildmenu
  +cursorbind-lua   +scrollbind+windows
  +cursorshape   +menu  +signs +writebackup
  +dialog_con+mksession +smartindent   -X11
  +diff  +modify_fname  +sound -xfontset
  +digraphs  +mouse +spell -xim
  -dnd   -mouseshape+startuptime   -xpm
  -ebcdic+mouse_dec +statusline-xsmp
  +emacs_tags+mouse_gpm -sun_workshop  -xterm_clipboard
  +eval  -mouse_jsbterm +syntax-xterm_save
  +ex_extra  +mouse_netterm +tag_binary
  +extra_search  +mouse_sgr -tag_old_static
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
 defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 
-fdebug-prefix-map=/build/vim-iU6mZD/vim-8.1.2269=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1   
  Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux  -lcanberra -lacl 
-lattr -lgpm -ldl -L/usr/lib/python3.8/config-3.8-x86_64-linux-gnu 
-lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm  

  Any clue?  Thank you!

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

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

[Touch-packages] [Bug 1900670] [NEW] vimdiff confuses lines

[Rostislav]

Public bug reported:

I try to see diff of two files in my Ubuntu 20.04.

$ vimdiff outlog_20201020082321-head.log outlog_20201020084056-head.log

The diff matches wrong lines and highlights them strangely..
Reproducible with removed ~/.vimrc and ~/.vim.

$ vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
Included patches: 1-2269
Modified by team+...@tracker.debian.org
Compiled by team+...@tracker.debian.org
Huge version without GUI.  Features included (+) or not (-):
+acl   -farsi -mouse_sysmouse-tag_any_white
+arabic+file_in_path  +mouse_urxvt   -tcl
+autocmd   +find_in_path  +mouse_xterm   +termguicolors
+autochdir +float +multi_byte+terminal
-autoservername+folding   +multi_lang+terminfo
-balloon_eval  -footer-mzscheme  +termresponse
+balloon_eval_term +fork()+netbeans_intg +textobjects
-browse+gettext   +num64 +textprop
++builtin_terms-hangul_input  +packages  +timers
+byte_offset   +iconv +path_extra+title
+channel   +insert_expand -perl  -toolbar
+cindent   +job   +persistent_undo   +user_commands
-clientserver  +jumplist  +postscript+vartabs
-clipboard +keymap+printer   +vertsplit
+cmdline_compl +lambda+profile   +virtualedit
+cmdline_hist  +langmap   -python+visual
+cmdline_info  +libcall   +python3   +visualextra
+comments  +linebreak +quickfix  +viminfo
+conceal   +lispindent+reltime   +vreplace
+cryptv+listcmds  +rightleft +wildignore
+cscope+localmap  -ruby  +wildmenu
+cursorbind-lua   +scrollbind+windows
+cursorshape   +menu  +signs +writebackup
+dialog_con+mksession +smartindent   -X11
+diff  +modify_fname  +sound -xfontset
+digraphs  +mouse +spell -xim
-dnd   -mouseshape+startuptime   -xpm
-ebcdic+mouse_dec +statusline-xsmp
+emacs_tags+mouse_gpm -sun_workshop  -xterm_clipboard
+eval  -mouse_jsbterm +syntax-xterm_save
+ex_extra  +mouse_netterm +tag_binary
+extra_search  +mouse_sgr -tag_old_static
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
  user exrc file: "$HOME/.exrc"
   defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 
-fdebug-prefix-map=/build/vim-iU6mZD/vim-8.1.2269=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1   
Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-o vim-lm -ltinfo -lnsl  -lselinux  -lcanberra -lacl -lattr -lgpm -ldl  
   -L/usr/lib/python3.8/config-3.8-x86_64-linux-gnu -lpython3.8 -lcrypt 
-lpthread -ldl -lutil -lm -lm  

Any clue?  Thank you!

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

** Attachment added: "screenshot"
   https://bugs.launchpad.net/bugs/1900670/+attachment/5424567/+files/vimbug.png

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

Title:
  vimdiff confuses lines

Status in vim package in Ubuntu:
  New

Bug description:
  I try to see diff of two files in my Ubuntu 20.04.

  $ vimdiff outlog_20201020082321-head.log
  outlog_20201020084056-head.log

  The diff matches wrong lines and highlights them strangely..
  Reproducible with removed ~/.vimrc and ~/.vim.

  $ vim --version
  VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
  Included patches: 1-2269
  Modified by team+...@tracker.debian.org
  Compiled by team+...@tracker.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl   -farsi -mouse_sysmouse-tag_any_white
  +arabic+file_in_path  +mouse_urxvt   -tcl
  +autocmd   +find_in_path  +mouse_xterm   +termguicolors
  +autochdir +float +multi_byte+terminal
  -autoservername+folding   +multi_lang+terminfo
  -balloon_eval  -footer-mzscheme  +termresponse
  +balloon_eval_term +fork()+netbeans_intg +textobjects
  -browse+gettext   +num64 +textprop
  ++builtin_terms-hangul_input  +packages  

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-10-20 04:48 EDT---
IBM Bugzilla status-> closed, Fix Released for all req. distros

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

Title:
  [UBUNTU 20.04] zlib not working on all s390x systems configurations

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Eoan:
  Won't Fix
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Pull request (https://github.com/madler/zlib/pull/410) and tagged
  https://github.com/iii-i/zlib/tree/dfltcc-20200511.

  The new code contains the following improvements:
  * Added support for switching between software and hardware compression.
  * Added --dfltcc configure flag (the old way of building it still works).

  Switching between software and hardware compression is not simply a
  nice-to-have feature, but is actually required by Java - that's why we
  are requesting an update.

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

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

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Sebastien Bacher]

THose having the issue still, it would be better to report directly
upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues since
Ubuntu doesn't currently have a dedicated pulseaudio maintainer

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Javier Paniagua Laconich]

I'm on 20.10 Groovy Beta and, after today's kernel + linux-firmware
update, HFP/HSP is working on my dell xps 13 9380.

It stopped working since 20.04, it wasn't working with all previous
kernel/linux-firmware versions in 20.10. Today it's finally back.

$ uname -a
Linux mydellxps 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.190
  Candidate: 1.190
  Version table:
 *** 1.190 500
500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu groovy/main i386 Packages
100 /var/lib/dpkg/status

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

[raneq]

Hi, ending 2020 and still an issue :/

Using Debian 10, Evolution version 3.30.5-1.1. Trying to connect to
Microsoft Exchange 2007.

I just started Evolution for the 2d time, 1st after trying set up an EWS
account, and all attempts I had done appeared in the account list at
left. Now it just works, thanks!

However, it confused me a lot. Specially no error messages, no logs at
the shell, no nothing. People that isn't "techie and english-speaking",
both at the same time, won't find this bugpage nor the askubuntu site,
I'm afraid.

If the issue can't be solved after 8 years, there must be a reason.
Therefore, why not add a warning at the end of the wizard with "Please
now restart Evolution" ??

Thank for making possible to stay in linux even when working for
microsoft corporate environments.

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

Title:
  Evolution appears unable to create EWS or Exchange MAPI account

Status in evolution-ews:
  Expired
Status in evolution package in Ubuntu:
  Triaged
Status in evolution-data-server package in Ubuntu:
  Triaged
Status in evolution-ews package in Ubuntu:
  Triaged
Status in evolution-mapi package in Ubuntu:
  Won't Fix

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions

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

[Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

[x31eq]

** Attachment added: "Former contents of /etc/pulse"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900481/+attachment/5424534/+files/pulse.tgz

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

[x31eq]

On 20/10/2020, Daniel van Vugt <1900...@bugs.launchpad.net> wrote:
> That sounds like it might be the problem. Please look in /etc/pulse/ and
> see if you can remember what you changed. Failing that, just
> reinstalling and not modifying the system, might be the fastest
> solution.

I moved /etc/pulse/ and reinstalled pulseaudio.  Now the "Sound
Settings" applet looks correct, but still sound is not working.  The
PulseAudio volume control simply says "Establishing connection to
PulseAudio. Please wait...".  This is what mplayer says:

MPlayer 1.3.0 (Debian), built with gcc-9 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing Know_Your_Car.ogg.
libavformat version 58.29.100 (external)
libavformat file format detected.
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
[lavf] stream 0: audio (vorbis), -aid 0
Load subtitles in ./
==
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
libavcodec version 58.54.100 (external)
AUDIO: 44100 Hz, 2 ch, floatle, 112.0 kbit/3.97% (ratio: 14000->352800)
Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis)
==
AO: [pulse] Init failed: Connection refused
Failed to initialize audio driver 'pulse'
[AO_ALSA] alsa-lib: pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to
create IPC semaphore
[AO_ALSA] Playback open error: Permission denied
Failed to initialize audio driver 'alsa'
[AO SDL] Samplerate: 44100Hz Channels: Stereo Format floatle
[AO SDL] using aalib audio driver.
[AO SDL] Unsupported audio format: 0x1d.
[AO SDL] Unable to open audio: No available audio device
Failed to initialize audio driver 'sdl:aalib'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video


Exiting... (End of file)


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900481
>
> Title:
>   [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
>   card
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Following upgrade to 20.04, I have no audio.  My output device is
>   "Dummy Output".  I chose one audio device to report against: none are
>   detected.  All this may be obvious from the auto-detected diagnostics.
>   It was working in 18.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: pulseaudio 1:13.99.1-1ubuntu3.7
>   ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
>   Uname: Linux 5.4.0-51-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.9
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code
> 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: MATE
>   Date: Mon Oct 19 19:43:52 2020
>   InstallationDate: Installed on 2018-05-05 (897 days ago)
>   InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180505)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_Card: HDA-Intel - HDA Intel MID
>   Symptom_Jack: Mic, Top
>   Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
> card
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/25/2010
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A10
>   dmi.board.name: 030DMJ
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A10
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A10
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
>   dmi.product.name: Vostro 3300
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: A10
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900481/+subscriptions
>

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 

[Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

[Daniel van Vugt]

That sounds like it might be the problem. Please look in /etc/pulse/ and
see if you can remember what you changed. Failing that, just
reinstalling and not modifying the system, might be the fastest
solution.

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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