[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
[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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Expired Status in systemd source package in Focal: Expired Status in systemd source package in Groovy: Expired Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 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 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
[Expired for systemd (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Focal) 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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Expired Status in systemd source package in Focal: Expired Status in systemd source package in Groovy: Expired Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 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 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
[Expired for systemd (Ubuntu Groovy) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Groovy) 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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Expired Status in systemd source package in Focal: Expired Status in systemd source package in Groovy: Expired Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 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 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-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: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1923686] Re: Ubuntu 20.10 Network Issue
[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/1923686 Title: Ubuntu 20.10 Network Issue Status in systemd package in Ubuntu: Expired Bug description: I have a server running Ubuntu 20.10 running VMware Workstation 16 which loses its default route. I keep setting it manually but every 30 minutes or so, it reverts to the incorrect route. This server has 5 (4 used) GigE ports on different VLANs. Each of the 4 ports is connected to a Cisco switch which applies the proper tag for that VLAN so that traffic can be routed correctly. I have tried disabling netplan and setting up interfaces in /etc/network/interfaces with the proper default route. But vmnetbrdige resets them every 30 minutes or so, adding routes for each interface which results in the incorrect default route. I have read of similar problems in Ubuntu 16.04 and 20.04 with a fix which claims to have corrected related problems, but not my issue. I had this server on CentOS 6 before and everything was work as expected. Below are the details. Contents of /etc/network/interfaces: iface eth1 inet static address 10.0.1.6 netmask 255.255.255.0 gateway 10.0.1.1 dns-nameservers 8.8.8.8, 75.75.76.76 dns-search mydomain.local up route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.1.1 dev eth0 iface eth2 inet static address 10.0.20.60 netmask 255.255.255.0 gateway 10.0.20.1 iface eth3 inet static address 10.0.4.60 netmask 255.255.255.0 gateway 10.0.4.1 iface eth4 inet static address 192.168.3.60 netmask 255.255.255.0 gateway 192.168.3.1 Output of ifconfig -a: eth1: flags=4163 mtu 1500 inet 10.0.1.60 netmask 255.255.255.0 broadcast 10.0.1.255 inet6 fe80::264b:feff:fe5a:3622 prefixlen 64 scopeid 0x20 ether 24:4b:fe:5a:36:22 txqueuelen 1000 (Ethernet) RX packets 17216 bytes 14604772 (14.6 MB) RX errors 0 dropped 1283 overruns 0 frame 0 TX packets 14670 bytes 1719546 (1.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc60-fc61 eth2: flags=4163 mtu 1500 inet 10.0.20.60 netmask 255.255.255.0 broadcast 10.0.20.255 inet6 fe80::226:55ff:fed7:d054 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:54 txqueuelen 1000 (Ethernet) RX packets 3159 bytes 212180 (212.1 KB) RX errors 0 dropped 1426 overruns 0 frame 0 TX packets 1691 bytes 122628 (122.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 106 memory 0xfca0-fca2 eth3: flags=4163 mtu 1500 inet 10.0.4.60 netmask 255.255.255.0 broadcast 10.0.4.255 inet6 fe80::226:55ff:fed7:d057 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:57 txqueuelen 1000 (Ethernet) RX packets 3835 bytes 249203 (249.2 KB) RX errors 0 dropped 1408 overruns 0 frame 0 TX packets 370 bytes 31235 (31.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 115 memory 0xfc82-fc84 eth4: flags=4163 mtu 1500 inet 192.168.3.60 netmask 255.255.255.0 broadcast 192.168.3.255 inet6 fe80::226:55ff:fed7:d056 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:56 txqueuelen 1000 (Ethernet) RX packets 2973 bytes 211765 (211.7 KB) RX errors 0 dropped 1433 overruns 0 frame 0 TX packets 238 bytes 29345 (29.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 117 memory 0xfc80-fc82 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 119 bytes 17075 (17.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 119 bytes 17075 (17.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923686/+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 1931780] Re: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
** Tags removed: need-duplicate-check -- 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/1931780 Title: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu has been telling me for some time that PulsAudio has corrupted files. I haven't figured out how to reload it yet. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 3191 F pulseaudio /dev/snd/pcmC1D7p: john 3191 F...m pulseaudio /dev/snd/controlC2: john 3191 F pulseaudio /dev/snd/controlC0: john 3191 F pulseaudio CasperMD5CheckResult: skip Date: Mon May 31 17:16:03 2021 DpkgHistoryLog: Start-Date: 2021-05-31 17:15:15 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (5.4.0-72.80, 5.4.0-73.82) DuplicateSignature: package:pulseaudio-module-bluetooth:1:13.99.1-1ubuntu3.10 Setting up linux-libc-dev:amd64 (5.4.0-73.82) ... dpkg: error processing package pulseaudio-module-bluetooth (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: pulseaudio Title: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to focal on 2020-12-27 (167 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0K4H3G dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0K4H3G:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L702X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931780/+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 1900008] Re: Sessions of screen does not keep running in background
Ok, today I have some time, I am installing Ubuntu Desktop 20.04 in VirtualBox. Meanwhile, the only way to keep a session alive (in KDE Neon 20.04) is by using: systemd-run --scope --user screen Will keep posted once I've tested in the Ubuntu installation. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1931780] [NEW] package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a
Public bug reported: Ubuntu has been telling me for some time that PulsAudio has corrupted files. I haven't figured out how to reload it yet. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 3191 F pulseaudio /dev/snd/pcmC1D7p: john 3191 F...m pulseaudio /dev/snd/controlC2: john 3191 F pulseaudio /dev/snd/controlC0: john 3191 F pulseaudio CasperMD5CheckResult: skip Date: Mon May 31 17:16:03 2021 DpkgHistoryLog: Start-Date: 2021-05-31 17:15:15 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (5.4.0-72.80, 5.4.0-73.82) DuplicateSignature: package:pulseaudio-module-bluetooth:1:13.99.1-1ubuntu3.10 Setting up linux-libc-dev:amd64 (5.4.0-73.82) ... dpkg: error processing package pulseaudio-module-bluetooth (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: pulseaudio Title: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to focal on 2020-12-27 (167 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0K4H3G dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0K4H3G:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L702X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1931780 Title: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu has been telling me for some time that PulsAudio has corrupted files. I haven't figured out how to reload it yet. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 3191 F pulseaudio /dev/snd/pcmC1D7p: john 3191 F...m pulseaudio /dev/snd/controlC2: john 3191 F pulseaudio /dev/snd/controlC0: john 3191 F pulseaudio CasperMD5CheckResult: skip Date: Mon May 31 17:16:03 2021 DpkgHistoryLog: Start-Date: 2021-05-31 17:15:15 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (5.4.0-72.80, 5.4.0-73.82) DuplicateSignature: package:pulseaudio-module-bluetooth:1:13.99.1-1ubuntu3.10 Setting up linux-libc-dev:amd64 (5.4.0-73.82) ... dpkg: error processing package pulseaudio-module-bluetooth (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: pulseaudio Title: package pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
[Touch-packages] [Bug 1895490] Re: no destination host name is cups-browsed running
Same error. But changed printer from default to one with .local at end of name then worked. Not sure why hpcups 3.20.3 printer and driverless cups-filter 1.27.4 printer are also configured but do not work. -- 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/1895490 Title: no destination host name is cups-browsed running Status in cups package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 cups-browsed: Installed: 1.27.4-1 cups: Installed: 2.3.1-9ubuntu1.1 I expect to be able to print on my Brother HL-L2350DW printer. I have no problem printing to that printer via Windows 10. I also got this error on Kubuntu 20.04. What happened instead? I cannot get my pdf to print. Instead I get an error that says 'No destination host name supplied by cups-browsed for printer "Brother_HL_L2350DW_series", is cups-browsed running?'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 20:30:40 2020 InstallationDate: Installed on 2020-08-16 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L2350DW_series: implicitclass://Brother_HL_L2350DW_series/ MachineType: LENOVO 20AN00DEUS Papersize: letter PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GLET96WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00DEUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00DEUS dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895490/+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 1895490] Re: no destination host name is cups-browsed running
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1895490 Title: no destination host name is cups-browsed running Status in cups package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 cups-browsed: Installed: 1.27.4-1 cups: Installed: 2.3.1-9ubuntu1.1 I expect to be able to print on my Brother HL-L2350DW printer. I have no problem printing to that printer via Windows 10. I also got this error on Kubuntu 20.04. What happened instead? I cannot get my pdf to print. Instead I get an error that says 'No destination host name supplied by cups-browsed for printer "Brother_HL_L2350DW_series", is cups-browsed running?'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 20:30:40 2020 InstallationDate: Installed on 2020-08-16 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L2350DW_series: implicitclass://Brother_HL_L2350DW_series/ MachineType: LENOVO 20AN00DEUS Papersize: letter PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GLET96WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00DEUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00DEUS dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895490/+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 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...
I did that, as said, I do not get anything, just returns to $ and a 0 byte .upload file with the same name appears in /var/crash. I tried multiple times. I installed Ubuntu Budgie 21.04 after downloading the image and verifying checksum, I installed it now on 5 different systems, each one shows the exact same crash file (attached). There is no way to send it. Also, there are no weird behaviors, everything just works. But the message is annoying. I got it first only at initial boot after install but now I notice it appears also after subsequent reboots, if I deleted the file in /var/crash before rebooting. https://upload.disroot.org/r/sUVtoruT#KIyWDWBiQPwQJijUs/1UsG/smNJP6BBJCei034j5K68= -- 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/1930409 Title: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ... Status in pulseaudio package in Ubuntu: Incomplete Bug description: Not sure if the bluez error is related, perhaps not (this is a desktop without Wifi/Bluetooth). jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired,> Intel i3-9100, C246 chipset, 32GB ram. Ubuntu Budgie 21.04 installed via usb boot disk. It gives me a popup "error occured" every time I reboot.. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asterix1749 F pulseaudio CasperMD5CheckResult: pass Date: Tue Jun 1 12:48:36 2021 InstallationDate: Installed on 2021-05-11 (21 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.release: 1.6 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x dmi.board.name: D3644-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3644-B1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr: dmi.product.family: OEM-FTS dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+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 1931776] Re: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de e
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1931776 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 12 11:31:14 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-06-02 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 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/1931776/+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 1931732] Re: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do sta
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1931732 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post- installation retornou erro do status de saída 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: não instalou ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 9 03:03:16 2021 ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-06-09 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do status de saída 1 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/1931732/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Changed in: unattended-upgrades (Ubuntu Trusty) Assignee: Balint Reczey (rbalint) => (unassigned) -- 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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade
[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
I have performed the verification following the Test Plan. The full log is attached. Relevant part: The following packages will be REMOVED: qt5-default The following NEW packages will be installed: gcc-11-base libboost-iostreams1.74.0 libcap2 libisl23 libmd0 libperl5.32 libxrender1 libxxhash0 lto-disabled-list perl-modules-5.32 The following packages will be upgraded: ... libqt5core5a libqt5dbus5 libqt5gui5 ... As can be seen here, no *-gles packages are installed. ** Attachment added: "chroot-upgrade.txt" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src-gles/+bug/1920130/+attachment/5504247/+files/chroot-upgrade.txt ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src-gles package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Hirsute: Fix Committed Status in qtbase-opensource-src-gles source package in Hirsute: Fix Committed Status in qtbase-opensource-src-gles package in Debian: Fix Released Bug description: [Impact] This affects Groovy → Hirsute upgrades for users who had qt5-default package installed. For these users, apt could replace libqt5gui5 with libqt5gui5-gles, which is not suitable for most desktop systems and can result in all kinds of broken UI (such as missing icons). [Test Plan] 1. Get a groovy amd64 system (e.g. a chroot). 2. Install qt5-default package. 3. Replace groovy with hirsute in /etc/apt/sources.list. 4. Run "apt update". 5. Run "apt dist-upgade". Incorrect behavior: The following packages will be REMOVED: libqt5gui5 qt5-default qtbase5-dev The following NEW packages will be installed: ... libqt5gui5-gles ... Correct behavior: only qt5-default is removed, libqt5gui5 is not removed and libqt5gui5-gles is not installed. [Where problems could occur] The fix is adding "Breaks: qt5-default" in three packages: - qtbase5-dev (built from qtbase-opensource-src source). - qtbase5-gles-dev (built from qtbase-opensource-src-gles source). - libqt5gui5-gles (built from qtbase-opensource-src-gles source). It can affect apt's dependency resolver. Example of a problem may be the resolver keeping the old behavior in some cases. [Other Info] See this post for details on what the -gles packages are: https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html See my discussion with one of the developers of apt on this issue: https://lists.debian.org/debian-devel/2021/05/msg00076.html https://lists.debian.org/debian-devel/2021/05/msg00150.html https://lists.debian.org/debian-devel/2021/05/msg00162.html Also see this comment where I collected some links to stories of users who were affected by this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10 [Original Description] Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130:
[Touch-packages] [Bug 1931776] [NEW] package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de
Public bug reported: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 12 11:31:14 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-06-02 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1931776 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 12 11:31:14 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-06-02 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 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/1931776/+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 1915502] Re: "systemd --user" fails to start for non-local users
** Bug watch added: Debian Bug tracker #878625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
--
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/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
Incomplete
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
Re: [Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 Am Do., 10. Juni 2021 um 20:23 Uhr schrieb Michael Biebl : > > The relevant upstream bug report afaics is > https://github.com/systemd/systemd/issues/7074 > > Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl : > > > > Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman > > <1915...@bugs.launchpad.net>: > > > > > > Ok, so it does sound like this and bug 1916235 are the same issue. And > > > this might be 'as designed', since upstream systemd wants systemd-logind > > > to talk to systemd-userdb instead of directly connecting to NIS servers; > > > however Debian (and Ubuntu) disable systemd-userdb. > > > > > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > > > should we also adjust the systemd-logind RestrictAddressFamilies= > > > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > > > networking? I'm not sure why ProtectHostname= would also be needed, but > > > I assume it's related to the tighter restrictions on systemd-logind. > > > > I think the nis package should ship a drop-in config for > > systemd-logind, allowing network access in systemd-logind. > > This shouldn't be enabled globally for all users. > > > > As for ldap: If you use the new libpam-ldapd, there should be no > > problem, as the network access is delegated to a separate process > > (nscld). -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus
[Touch-packages] [Bug 1691608] Re: Sporadic crackling sound from headphones
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: ubuntu Status: New => Incomplete ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1691608 Title: Sporadic crackling sound from headphones Status in Ubuntu: Incomplete Status in alsa-driver package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 64 bit HP Pavilion 15-aw077nr (Touch) Laptop Headphones had sporadic crackling sound. More often when volume increases over 30% Laptop has B speakers and headphones worked fine in Win10 before I replaced it with Ubuntu. Output from bash alsa-info.sh command: upload=true=true= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Thu May 18 01:25:26 UTC 2017 !!Linux Distribution !!-- Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; UBUNTU_CODENAME=xenial !!DMI Information !!--- Manufacturer: HP Product Name: HP Pavilion Notebook Product Version: Firmware Version: F.23 Board Vendor: HP Board Name:81FB !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ASD0001:00/status15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/HPQ6007:00/status15 /sys/bus/acpi/devices/HPQ8001:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXVIDEO:00/status 15 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0A08:00/status15 /sys/bus/acpi/devices/PNP0C01:00/status15 /sys/bus/acpi/devices/PNP0C02:02/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status11 /sys/bus/acpi/devices/PNP0C0F:01/status11 /sys/bus/acpi/devices/PNP0C0F:02/status11 /sys/bus/acpi/devices/PNP0C0F:03/status11 /sys/bus/acpi/devices/PNP0C0F:04/status11 /sys/bus/acpi/devices/PNP0C0F:05/status11 /sys/bus/acpi/devices/PNP0C0F:06/status11 /sys/bus/acpi/devices/PNP0C0F:07/status11 /sys/bus/acpi/devices/SMB0001:00/status15 /sys/bus/acpi/devices/SYN3226:00/status15 /sys/bus/acpi/devices/device:3b/status 15 !!Kernel Information !!-- Kernel release:4.8.0-52-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.8.0-52-generic Library version:1.0.14 Utilities version: 1.1.0 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeb64000 irq 39 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfeb6 irq 40 !!PCI Soundcards installed in the system !!-- 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15b3 00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Device 157a !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:01.1 0403: 1002:15b3 Subsystem: 103c:81fb -- 00:09.2 0403: 1022:157a Subsystem: 103c:81fb !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2
[Touch-packages] [Bug 1876056] Re: No automatic switch to headset microphone on connect
@eggie, I have the same issue, your approach to address it works as well for me, thanks for pointing in the good direction ;) However, I found unacceptable the fact of no mic input if headphones are plugged. As such I found an alternative, making the headset port always available and the default, even if not plugged. Thus when headphones/headset connected the port is to Headset mic, but I can still change to Internal mic. With unplugged headphone/headset the same, port is to Headset mic, but I can still change to Internal mic. 1. In /usr/share/pulseaudio/alsa-mixer/paths/analog-input-headset- mic.conf change all the 'state.plugged' and 'state.unplugged' to 'yes'. 2. Locate the name of the Source and desired Port with: $ pacmd list-sources 3. Edit /etc/pulse/default.pa to set the default Source and Port, add the line 'set-source-port SourceName PortName' in my case it was 'set- source-port alsa_input.pci-_00_1f.3.analog-stereo analog-input- headset-mic' -- 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/1876056 Title: No automatic switch to headset microphone on connect Status in pulseaudio package in Ubuntu: Invalid Bug description: On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector, the audio OUTPUT automatically switches from the speakers in the laptop to the headset. However, the audio INPUT does not switch from the microphone in the laptop to the microphone in the headset. Using for example pavucontrol, I can switch to the microphone manually on the tab 'input devices' - on that tab Port will be on 'Internal Microphone' and I can set it to 'Headset Microphone'. What's even more confusing is that when I unplug the headset, both input AND output switch back to internal automatically and the port on the 'Input Devices'. This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also see the same issue on kernel 5.3.0-48) and pulseaudio 1:13.0-1ubuntu1.1. If any more information is needed, let me know. inxi -F: System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.5 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: Mobo: Dell model: 0VYV0G v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/25/2019 Battery: ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP L2 cache: 12.0 MiB Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 9: 4291 10: 4198 11: 4149 12: 4188 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Sound Server: ALSA v: k5.4.28-050428-generic Network: Device-1: Intel driver: iwlwifi IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 953.87 GiB Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB (29.2%) Shell: bash inxi: 3.0.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks
I've queued the fix in the git packaging repository to be included in
the next upload.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in systemd package in Ubuntu:
Fix Committed
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1931725] Re: initramfs-tools: use zstd as the default compression method
This bug was fixed in the package initramfs-tools - 0.140ubuntu5 --- initramfs-tools (0.140ubuntu5) impish; urgency=medium * Switch default initramfs compression to zstd, as it produces the lower overall boot time. LP: #1931725 -- Dimitri John Ledkov Fri, 11 Jun 2021 16:55:30 +0100 ** Changed in: initramfs-tools (Ubuntu) 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/1931725 Title: initramfs-tools: use zstd as the default compression method Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: New Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3 /kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931725/+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 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
** Package changed: procps (Ubuntu) => linux-meta-kvm (Ubuntu) -- 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/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail Status in linux-meta-kvm package in Ubuntu: New Bug description: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/1931630/+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 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
Thanks for reporting. >I was told to move this issue to *linux-image-kvm*. How can I do that? If you look at the yellow line under "affects" it lists "procps (Ubuntu)". Next to it is a triangle which you can click to expand, where you can change details such as the package name and status. To move this bug report to another package you want to replace the package name. Note that you may need to use `linux-meta-kvm` if `linux- image-kvm` doesn't work, since bugs are tracked against source packages not binary ones. -- 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/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail Status in procps package in Ubuntu: New Bug description: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
Please try ubuntu kernel 5.11.0-19-generic or later version. Looks like it is a soundwire audio codec on your machine. -- 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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
