[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
ubuntu 20.04.1 # update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.8.0-45-generic Found initrd image: /boot/initrd.img-5.8.0-45-generic Found linux image: /boot/vmlinuz-5.8.0-44-generic Found initrd image: /boot/initrd.img-5.8.0-44-generic File descriptor 4 (pipe:[48288]) leaked on lvs invocation. Parent PID 6394: /bin/sh File descriptor 5 (pipe:[48288]) leaked on lvs invocation. Parent PID 6394: /bin/sh File descriptor 9 (pipe:[48291]) leaked on lvs invocation. Parent PID 6394: /bin/sh /dev/sdd: open failed: No medium found /dev/sdd: open failed: No medium found Adding boot menu entry for UEFI Firmware Settings done # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop07:00 31.1M 1 loop /snap/snapd/11036 loop17:10 32.3M 1 loop /snap/snapd/11107 sda 8:00 1.1T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:208G 0 part [SWAP] └─sda3 8:30 1.1T 0 part / sdb 8:16 0 10.9T 0 disk └─sdb1 8:17 0 10.9T 0 part /var/CommuniGate sdc 8:32 0 1.1T 0 disk └─sdc1 8:33 0 1.1T 0 part /var/CommuniGate/SystemLogs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Confirmed Bug description: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-root 253:20 3.7T 0 lvm / sdb8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdg8:96 0 7.3T 0 disk └─sdg1 8:97 0 7.3T 0 part /media/scott/8TB Ext Drive sr0 11:01 15.7G 0 rom --
[Touch-packages] [Bug 1920652] [NEW] [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Black Headphone Out, Left] Background noise or low volume
Public bug reported: Sound Not clear and a2dp mode unavailable auto-selected HSP/HFP mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anonymous 13721 F pulseaudio /dev/snd/pcmC0D0c: anonymous 13721 F...m pulseaudio /dev/snd/pcmC0D0p: anonymous 13721 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 21 09:04:53 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: High background noise, or volume is too low Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A7 dmi.board.vendor: HP dmi.board.version: KBC Version 39.35 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 39.35 dmi.modalias: dmi:bvnInsyde:bvrF.31:bd06/10/2020:br15.31:efr39.35:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A7:rvrKBCVersion39.35:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 2VL79PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1920652 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Black Headphone Out, Left] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: Sound Not clear and a2dp mode unavailable auto-selected HSP/HFP mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anonymous 13721 F pulseaudio /dev/snd/pcmC0D0c: anonymous 13721 F...m pulseaudio /dev/snd/pcmC0D0p: anonymous 13721 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 21 09:04:53 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: High background noise, or volume is too low Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A7 dmi.board.vendor: HP dmi.board.version: KBC Version 39.35 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 39.35 dmi.modalias: dmi:bvnInsyde:bvrF.31:bd06/10/2020:br15.31:efr39.35:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A7:rvrKBCVersion39.35:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 2VL79PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1920652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Thanks for the workaround. Can confirm it works, I was just wondering how the key was allowed to expire, and if there is anything being done to make sure it doesn't happen again to this or other keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Hi, This is a workaround you can use temporarily: $ wget -O- http://ddebs.ubuntu.com/dbgsym-release-key.asc | sudo apt- key add - $ sudo apt update The key was extended temporarily. Best, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
I have a similar error Ign:16 http://ddebs.ubuntu.com focal-updates Release.gpg Err:17 http://ddebs.ubuntu.com focal Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Err:19 http://ddebs.ubuntu.com focal-proposed Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Hit:18 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease Reading package lists... Done E: The repository 'http://ddebs.ubuntu.com focal-updates Release' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] [NEW] EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Public bug reported: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Summary changed: - W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) + EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) ** Description changed: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: - Installed: 2020.02.11.2 - Candidate: 2020.02.11.2 - Version table: - *** 2020.02.11.2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages - 100 /var/lib/dpkg/status - $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys + Installed: 2020.02.11.2 + Candidate: 2020.02.11.2 + Version table: + *** 2020.02.11.2 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages + 100 /var/lib/dpkg/status + $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] - F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 + F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) + + + Error message on "apt update": + + E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. + N: Updating from such a repository can't be done securely, and is therefore disabled by default. + N: See apt-secure(8) manpage for repository creation and user configuration details. + W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) + E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. + N: Updating from such a repository can't be done securely, and is therefore disabled by default. + N: See apt-secure(8) manpage for repository creation and user configuration details. + W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) + E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. + N: Updating from such a repository can't be done securely, and is therefore disabled by default. + N: See apt-secure(8) manpage for repository creation and user conf
[Touch-packages] [Bug 1918021] Re: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container
Still happens. ** Also affects: ucf (Ubuntu) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1918021 Title: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container Status in docker.io package in Ubuntu: New Status in libpaper package in Ubuntu: Confirmed Status in ucf package in Ubuntu: New Bug description: Steps to reproduce: 1. Have simple Dockerfile as shown below: ``` mkdir ~/ubuntu-mate-hirsute cat < ~/ubuntu-mate-hirsute/Dockerfile FROM ubuntu:hirsute ENV SHELL=/bin/bash RUN apt-get update && \ env DEBIAN_FRONTEND=noninteractive apt-get install -y ubuntu-mate-desktop CMD ["mate-session"] EOF ``` 2. Build this Dockerfile by the command shown below docker build ~/ubuntu-mate-hirsute/ -t ubuntu-mate:hirsute Expected result: * Docker container is built and tagged as it was requested - ubuntu-mate:hirsute . Actual results: * Docker container is not built, have the following errors instead: ... Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data dpkg: error processing package libpaper1:amd64 (--configure): installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1 ... dpkg: dependency problems prevent configuration of libgs9:amd64: libgs9:amd64 depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package libgs9:amd64 (--configure): dependency problems - leaving unconfigured ... Setting up fonts-tlwg-umpush (1:0.7.2-1build1) ... dpkg: dependency problems prevent configuration of libpaper-utils: libpaper-utils depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package libpaper-utils (--configure): dependency problems - leaving unconfigured Setting up samba-common (2:4.13.3+dfsg-1ubuntu2) ... ucf: do not have write privilege to the state data dpkg: error processing package samba-common (--configure): installed samba-common package post-installation script subprocess returned error exit status 1 ... dpkg: dependency problems prevent configuration of ghostscript: ghostscript depends on libgs9 (= 9.53.3~dfsg-7); however: Package libgs9:amd64 is not configured yet. dpkg: error processing package ghostscript (--configure): dependency problems - leaving unconfigured ... Setting up fonts-tlwg-mono (1:0.7.2-1build1) ... dpkg: dependency problems prevent configuration of libatrildocument3: libatrildocument3 depends on libspectre1 (>= 0.2.3); however: Package libspectre1:amd64 is not configured yet. dpkg: error processing package libatrildocument3 (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of cups-daemon: cups-daemon depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package cups-daemon (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of atril: atril depends on libatrildocument3 (= 1.24.0-1); however: Package libatrildocument3 is not configured yet. dpkg: error processing package atril (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of libatrilview3: libatrilview3 depends on libatrildocument3 (= 1.24.0-1); however: Package libatrildocument3 is not configured yet. dpkg: error processing package libatrilview3 (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of smbclient: smbclient depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package smbclient (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of samba-common-bin: samba-common-bin depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package samba-common-bin (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of printer-driver-ptouch: printer-driver-ptouch depends on ghostscript; however: Package ghostscript is not configured yet. dpkg: error processing package printer-driver-ptouch (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of cups-filters: cups-filters depends on ghostscript; however
[Touch-packages] [Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
The GPG key has simply expired, as of 2021-03-20: $ wget -q http://ddebs.ubuntu.com/dists/focal-proposed/Release http://ddebs.ubuntu.com/dists/focal-proposed/Release.gpg $ gpg --verify Release.gpg Release gpg: Signature made Fri 19 Mar 2021 04:52:53 AM CET gpg:using RSA key 0xC8CAB6595FDFF622 gpg: Good signature from "Ubuntu Debug Symbol Archive Automatic Signing Key (2016) " [expired] gpg: Note: This key has expired! Primary key fingerprint: F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 $ gpg --list-key 0xC8CAB6595FDFF622 pub rsa4096/0xC8CAB6595FDFF622 2016-03-21 [SC] [expired: 2021-03-20] Key fingerprint = F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Time to generate a new key and distribute it, I guess. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Opinion -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce t
[Touch-packages] [Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
Focal as well: Err:19 http://ddebs.ubuntu.com focal Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920619] [NEW] Epson Stylus SX535WD does not print in Ubuntu 20.04
Public bug reported: I have an Epson Stylus SX535WD, connected to the computer via USB. It prints correctly in Ubuntu 18.04. I recently upgraded to Ubuntu 20.04.2 LTS, and it no longer prints. The setup wizard seems to work. It detects the printer correctly, and asks for permission to install drivers from Epson. When I try to print, a message appears on the screen saying that the job has been submitted. A few seconds later, another message appears, saying the job has completed, but no output appears. The job shows up as completed in the printer queue. I tried printing a test page (Settings -> Printers -> Additional Printer Settings -> right-click the printer -> Properties -> Print Test Page), and also printing a document from LibreOffice. I upgraded my hardware (motherboard and CPU) at the same time as Ubuntu, and thought that might be the cause of the problem, but I booted the computer from a live USB of Ubuntu 18.04, and the printer worked then. I followed the recommendations at https://wiki.ubuntu.com/DebuggingPrintingProblems, none of which fixed the problem. Everything that the page tells me to check looks OK. The printer has a built-in scanner, which works in 20.04. Output from apt-cache (I'm not sure which of these are right or relevant): steve@weddell:~$ apt-cache policy cups cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages steve@weddell:~$ apt-cache policy openprinting-ppds openprinting-ppds: Installed: 20200401-1 Candidate: 20200401-1 Version table: *** 20200401-1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status steve@weddell:~$ apt-cache policy ghostscript ghostscript: Installed: 9.50~dfsg-5ubuntu4.2 Candidate: 9.50~dfsg-5ubuntu4.2 Version table: *** 9.50~dfsg-5ubuntu4.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 9.50~dfsg-5ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Attached is the output from the troubleshooter (Settings -> Printers -> Additional Printer Settings -> Help -> Troubleshoot). ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output from printer troubleshooting tool" https://bugs.launchpad.net/bugs/1920619/+attachment/5478499/+files/troubleshoot.txt -- 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/1920619 Title: Epson Stylus SX535WD does not print in Ubuntu 20.04 Status in cups package in Ubuntu: New Bug description: I have an Epson Stylus SX535WD, connected to the computer via USB. It prints correctly in Ubuntu 18.04. I recently upgraded to Ubuntu 20.04.2 LTS, and it no longer prints. The setup wizard seems to work. It detects the printer correctly, and asks for permission to install drivers from Epson. When I try to print, a message appears on the screen saying that the job has been submitted. A few seconds later, another message appears, saying the job has completed, but no output appears. The job shows up as completed in the printer queue. I tried printing a test page (Settings -> Printers -> Additional Printer Settings -> right-click the printer -> Properties -> Print Test Page), and also printing a document from LibreOffice. I upgraded my hardware (motherboard and CPU) at the same time as Ubuntu, and thought that might be the cause of the problem, but I booted the computer from a live USB of Ubuntu 18.04, and the printer worked then. I followed the recommendations at https://wiki.ubuntu.com/DebuggingPrintingProblems, none of which fixed the problem. Everything that the page tells me to check looks OK. The printer has a built-in scanner, which works in 20.04. Output from apt-cache (I'm not sure which of these are right or relevant): steve@weddell:~$ apt-cache policy cups cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages steve@weddell:~$ apt-cache policy openprinting-ppds openp
[Touch-packages] [Bug 1920610] [NEW] The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
*** This bug is a security vulnerability *** Public security bug reported: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed Status in ubuntu-keyring package in Ubuntu: New Bug description: Did an update this morning and it looks like the key has expired. W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-updates Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com groovy-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920587] Re: cmake support files are installed into a wrong directory
** Description changed: This problem was discovered when updating kmymoney's cmake build system with respect to libical (see https://invent.kde.org/office/kmymoney/-/merge_requests/63) with ubuntu:20.04. libical-dev:amd64 (3.0.8-1) ... /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list /# apt update /# apt-get install libical-dev /# dpkg -L libical-dev | grep 'LibIcal$' /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal - + + The correct location is /usr/lib/x86_64-linux-gnu/cmake/LibIcal. + The issue was not fixed with ubuntu 20.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libical in Ubuntu. https://bugs.launchpad.net/bugs/1920587 Title: cmake support files are installed into a wrong directory Status in libical package in Ubuntu: New Bug description: This problem was discovered when updating kmymoney's cmake build system with respect to libical (see https://invent.kde.org/office/kmymoney/-/merge_requests/63) with ubuntu:20.04. libical-dev:amd64 (3.0.8-1) ... /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list /# apt update /# apt-get install libical-dev /# dpkg -L libical-dev | grep 'LibIcal$' /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal The correct location is /usr/lib/x86_64-linux-gnu/cmake/LibIcal. The issue was not fixed with ubuntu 20.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1920587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920587] [NEW] cmake support files are installed into a wrong directory
Public bug reported: This problem was discovered when updating kmymoney's cmake build system with respect to libical (see https://invent.kde.org/office/kmymoney/-/merge_requests/63) with ubuntu:20.04. libical-dev:amd64 (3.0.8-1) ... /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list /# apt update /# apt-get install libical-dev /# dpkg -L libical-dev | grep 'LibIcal$' /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal The issue was not fixed with ubuntu 20.10. ** Affects: libical (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libical in Ubuntu. https://bugs.launchpad.net/bugs/1920587 Title: cmake support files are installed into a wrong directory Status in libical package in Ubuntu: New Bug description: This problem was discovered when updating kmymoney's cmake build system with respect to libical (see https://invent.kde.org/office/kmymoney/-/merge_requests/63) with ubuntu:20.04. libical-dev:amd64 (3.0.8-1) ... /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list /# apt update /# apt-get install libical-dev /# dpkg -L libical-dev | grep 'LibIcal$' /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal The issue was not fixed with ubuntu 20.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1920587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp