[Touch-packages] [Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons
We have at least 4 servers on which docker daemon was shutdown due to this unattended upgrade, and was not restarted. -- 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/1906364 Title: unattended-upgrade still restarts blacklisted daemons Status in unattended-upgrades package in Ubuntu: New Bug description: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1906364/+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 1906364] [NEW] unattended-upgrade still restarts blacklisted daemons
Public bug reported: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! >From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): - - Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. + Also this happened for us on plenty of our servers almost at the same + (why the unattended updates are not spread over time?), which destroyed + the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. + + PS: Not to say that on some servers the docker daemon did not even + restart.. -- 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/1906364 Title: unattended-upgrade still restarts blacklisted daemons Status in unattended-upgrades package in Ubuntu: New Bug description: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist:
[Touch-packages] [Bug 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.
** Changed in: snapd Assignee: Manoj Bhargav (manoj-bhargav333) => (unassigned) -- 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/1776622 Title: snapd updates on focal never finish installing. Can't install any other updates. Status in snapd: Fix Released Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.
Updating snap never finish-while I do not have/removed all snaps. ** Changed in: snapd Assignee: Michael Vogt (mvo) => Manoj Bhargav (manoj-bhargav333) -- 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/1776622 Title: snapd updates on focal never finish installing. Can't install any other updates. Status in snapd: Fix Released Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
Found on Groovy/linux 5.8.0-31.33 ** Tags added: 5.8 groovy -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1902710] Re: [SRU] Enable support for Wallaby Cloud Archive
This bug was fixed in the package software-properties - 0.99.4 --- software-properties (0.99.4) hirsute; urgency=medium * cloudarchive: Enable support for the Wallaby Ubuntu Cloud Archive on 20.04 (LP: #1902710). -- Corey Bryant Tue, 03 Nov 2020 08:58:47 -0500 ** Changed in: software-properties (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902710 Title: [SRU] Enable support for Wallaby Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Hirsute: Fix Released Bug description: Please add support for: cloud-archive:wallaby cloud-archive:wallaby-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the wallaby cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:wallaby sudo add-apt-repository cloud-archive:wallaby-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902710/+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 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers
This might provide some relief; https://wiki.strongswan.org/projects/strongswan/repository/revisions/44e5e8367691dd64f4e5ba0105fdc28b1f81ff25 -- 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/1783377 Title: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 / bionic systemd: Installé : 237-3ubuntu10.3 Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2): network-manager-strongswan: Installé : 1.4.4-1 Candidat : 1.4.4-1 Table de version : *** 1.4.4-1 300 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status 1.4.2-2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libcharon-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libcharon-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Before connecting the VPN, `systemd-resolve --status` shows : DNS Servers: 192.168.1.254 # my home box resolver After connecting : DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server 192.168.1.254 # my home box resolver This seems OK, but the resolution fails as it is still using the local DNS : systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. After issuing `systemctl reload-or-restart systemd-resolved.service`, everything seems fine. systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298 systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A. systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface enp0s3. systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A systemd-resolved[5651]: Transaction 9273 for scope dns on enp0s3/*. systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273. systemd-resolved[5651]: Using DNS server 10.0.0.254 for transaction 9273. I was hoping that `systemd-resolved` could find the new DNS without restarting its service after connecting to the VPN. Thanks for reading Best Regards, Vincent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 ** This bug has been marked a duplicate of bug 1888598 Pulseaudio breaks HDMI audio on sleep/wake -- 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/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1718927] Re: No HDMI sound after suspend/resume
See also bug 1888598 and bug 1745866 ** Tags added: hdmi ** Tags removed: hdmi-audio -- 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/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1745866] Re: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on
** Tags added: hdmi nvidia ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1745866 Title: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.14.0-15-generic. AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-25 (36 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171222) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic third-party-packages Uname: Linux 4.14.0-15-generic x86_64 UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H67M-GE/HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1745866/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
See also bug 1745866 and bug 1718927 ** Summary changed: - pulseaudio breaks hdmi audio on sleep/wake in ubuntu 20.10 + Pulseaudio breaks HDMI audio on sleep/wake ** Tags added: hdmi -- 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/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1896196] Re: Sounds switches from HDMI output to headset when screen blanks
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 ** This bug is no longer a duplicate of bug 1895665 PulseAudio automatically switches away from HDMI after display sleep ** This bug has been marked a duplicate of bug 1888598 Pulseaudio breaks HDMI audio on sleep/wake -- 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/1896196 Title: Sounds switches from HDMI output to headset when screen blanks Status in pulseaudio package in Ubuntu: New Bug description: On Groovy with all updates applied. Sound on HDMI output with speakers connected to the analog output of the monitor I've a USB sound card (Unitek Y-247A) connected to a HUB because the analog output on the machine doesn't work on which I connected the input and output jacks of a headset. If sound is playing through the speaker, when the display blanks after a period of inactivity, the sound switches to the sound card. I expect to either continue playing on the speaker or just go silent (which I would understand since the monitor goes in sleep mode) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu10 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 1348067 F pulseaudio /dev/snd/controlC1: j-lallement 1348067 F pulseaudio /dev/snd/controlC0: j-lallement 1348067 F pulseaudio /dev/snd/pcmC0D3p: j-lallement 1348067 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Sep 18 09:47:09 2020 InstallationDate: Installed on 2020-05-31 (110 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: evolution-data-server SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:br5.16:efr3.4:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896196/+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 1906292] Re: audio device changed after unlock gdm
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1888598, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: hdmi nvidia ** This bug has been marked a duplicate of bug 1888598 Pulseaudio breaks HDMI audio on sleep/wake -- 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/1906292 Title: audio device changed after unlock gdm Status in pulseaudio package in Ubuntu: New Bug description: Hello, after a long time of inactivites, my session automatically locked (GDM). When I unlock it, I can no more hear audio, device is set to spdif instead of hdmi/displayport2. I have to kill pulseaudio to retablish the good device hdmi/displayport2. It's a very annoying bug. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: romain419906 F pulseaudio /dev/snd/pcmC1D7p: romain419906 F...m pulseaudio /dev/snd/controlC0: romain419906 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 19:17:44 2020 InstallationDate: Installed on 2012-07-07 (3068 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-03 (241 days ago) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7752 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906292/+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 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates
I've been monitoring upower and I think the problem is it is incorrectly detecting the number of batteries in my laptop. I only have one yet upower detects 5 power sources. One of them is a DisplayDevice which normally shows the same amount of battery as my system battery. Sometimes that drops to 1% or 0%. I've had my laptop plugged in all day here are two upower -d dumps from within the last 5 minutes. Notice in the first dump /org/freedesktop/UPower/devices/DisplayDevice has 0% battery despite the laptop being plugged in. On the second it has the same engery, energy-full, and percentage as /org/freedesktop/UPower/devices/battery_BAT0. $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Mon 30 Nov 2020 02:36:20 PM PST (13554 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Celxpert model:5B10V98091 serial: 1695 power supply: yes updated: Mon 30 Nov 2020 06:20:22 PM PST (112 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 0 Wh energy-empty:0 Wh energy-full: 654.79 Wh energy-full-design: 80.4 Wh energy-rate: 0 W voltage: 7.189 V percentage: 0% capacity:88.4453% technology: lithium-polymer icon-name: 'battery-caution-charging-symbolic' History (charge): 1606789222 0.000 charging Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o001 native-path: ucsi-source-psy-USBC000:001 power supply: yes updated: Fri 27 Nov 2020 02:59:19 PM PST (271375 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o002 native-path: ucsi-source-psy-USBC000:002 power supply: yes updated: Fri 27 Nov 2020 02:59:18 PM PST (271376 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Mon 30 Nov 2020 06:20:22 PM PST (112 seconds ago) has history: no has statistics: no battery present: yes state: charging warning-level: none energy: 0 Wh energy-full: 654.79 Wh energy-rate: 0 W percentage: 0% icon-name: 'battery-caution-charging-symbolic' Daemon: daemon-version: 0.99.11 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Mon 30 Nov 2020 02:36:20 PM PST (13733 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Celxpert model:5B10V98091 serial: 1695 power supply: yes updated: Mon 30 Nov 2020 06:24:22 PM PST (51 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged warning-level: none energy: 71.71 Wh energy-empty:0 Wh energy-full: 654.79 Wh energy-full-design: 80.4 Wh energy-rate: 0 W voltage: 17.173 V percentage: 99% capacity:88.4453% technology: lithium-polymer icon-name: 'battery-full-charged-symbolic' Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o001 native-path: ucsi-source-psy-USBC000:001 power supply: yes updated: Fri 27 Nov 2020 02:59:19 PM PST (271554 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device:
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
@Marjan I set time by BIOS settings. -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+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 1906333] [NEW] Missing dep8 tests
Public bug reported: rsyslog is missing dep8 tests, which would be really good to have given the importance of this package and the amount of delta we're currently carrying. ** Affects: rsyslog (Ubuntu) Importance: Wishlist Status: New ** Tags: needs-dep8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1906333 Title: Missing dep8 tests Status in rsyslog package in Ubuntu: New Bug description: rsyslog is missing dep8 tests, which would be really good to have given the importance of this package and the amount of delta we're currently carrying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1906333/+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 1835660] Re: initramfs unpacking failed
so what grub is doing is correct. It pads/aligns every initrd by 4, which is fine, and as per spec. https://www.kernel.org/doc/html/latest/driver-api/early-userspace /buffer-format.html initramfs size can be filled with arbitrary amount of "\0" all the way upto initramfs_size. "In human terms, the initramfs buffer contains a collection of compressed and/or uncompressed cpio archives (in the “newc” or “crc” formats); arbitrary amounts zero bytes (for padding) can be added between members." Thus it feels to me that decompress_unlz4.c method in the kernel does not correctly stop decompressing and returning consumed output position (posp). For example, decompress_inflate.c skips over trailer and updates output pos by 8, at the end of successful conversion. Similarly unlzma also updates posp at the end of conversion. -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
The machine as such works without much problems, from time to time is under heavy load (make -j4 and such…) but I use it as my work desktop without noticeable problems. Network also works. -- 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: New Bug description: (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 55a37fe5a686 sp 7ffd9a160440 error 4 in systemd-resolved[55a37fe33000+3e000] [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15 [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15 [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in libsystemd-shared-245.so[7f66bb504000+16e000] [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in libsystemd-shared-245.so[7fdc40b2c000+16e000] [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in libsystemd-shared-245.so[7f6a92814000+16e000] [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 ip 555f9a5915e0 sp 7fff053e5e68 error 15 [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at 1991af73f2e ip 7ff194021dc9 sp 7fffa6d61680 error 4 in libsystemd-shared-245.so[7ff193ffc000+16e000] [Sun Nov 29 22:03:20 2020] systemd-resolve[1661941]: segfault at 5625966828e0 ip 5625966828e0 sp 7ffdf5a8bb48 error 15 [Sun Nov 29 22:32:44 2020] systemd-resolve[1662604]: segfault at 199f18ae01d ip 7f457c9d1dc9 sp 7ffc62b80ef0 error 4 in libsystemd-shared-245.so[7f457c9ac000+16e000] [Sun Nov 29 23:12:23 2020] systemd-resolve[1664072]: segfault at 73b8 ip 562619f8c93a sp 7ffd527b7ef0 error 6 in systemd-resolved[562619f61000+3e000] [Sun Nov 29 23:22:34 2020] systemd-resolve[1664423]: segfault at 19aaa4d4c00 ip 7f2621539dc9 sp 7ffc73102280 error 4 in libsystemd-shared-245.so[7f2621514000+16e000] [Mon Nov 30 00:12:23 2020] systemd-resolve[1666158]: segfault at 19b5c72000a ip 7f530b5c1dc9 sp 7ffc6007ccf0 error 4 in libsystemd-shared-245.so[7f530b59c000+16e000] [Mon Nov 30 00:47:54 2020] systemd-resolve[1667280]: segfault at 10036 ip 7f0736b8bbe8 sp 7fffed4d3cb0 error 4 in libsystemd-shared-245.so[7f0736acc000+16e000] [Mon Nov 30 01:57:53 2020] systemd-resolve[1669463]: segfault at 558d6b61c0c0 ip 558d6b61c0c0 sp 7ffc68df7198 error 15 [Mon Nov 30 02:58:08 2020] traps: systemd-resolve[1672553] general protection fault ip:55b967d86760 sp:7fffaecf4468 error:0 in systemd-resolved[55b967d5f000+3e000] [Mon Nov 30 03:38:08 2020] systemd-resolve[1673682]: segfault at
[Touch-packages] [Bug 1905758] Re: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1905758 Title: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libglib2.0-0:i386 2.66.1-2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 19 17:43:35 2020 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1905758/+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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
systemd-resolve journal is fairly full of failed assertions. During last 3 days I got 301 of them. This one is very frequent (I got it 294 times) ~ Nov 28 21:10:02 platon systemd-resolved[1590676]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. ~ The rest: ~ Nov 28 03:35:02 platon systemd-resolved[1542718]: Assertion '*_head == _item' failed at src/resolve/resolved-dns-query.c:397, function dns_query_free(). Aborting. Nov 28 04:20:02 platon systemd-resolved[1546490]: Assertion 'p->n_ref > 0' failed at src/resolve/resolved-dns-question.c:33, function dns_question_unref(). Aborting. Nov 28 14:20:23 platon systemd-resolved[1572471]: Assertion '*_head == _item' failed at src/resolve/resolved-dns-query.c:397, function dns_query_free(). Aborting. Nov 28 19:34:52 platon systemd-resolved[1587570]: Assertion '*_head == _item' failed at src/resolve/resolved-dns-query.c:372, function dns_query_free(). Aborting. Nov 29 18:59:52 platon systemd-resolved[1651715]: Assertion 'p->n_ref > 0' failed at src/libsystemd/sd-event/sd-event.c:1912, function sd_event_source_unref(). Aborting. Nov 30 14:35:23 platon systemd-resolved[1710789]: Assertion '*_head == _item' failed at src/resolve/resolved-dns-query.c:397, function dns_query_free(). Aborting. Nov 30 18:29:52 platon systemd-resolved[1726691]: Assertion 'p->n_ref > 0' failed at src/libsystemd/sd-event/sd-event.c:1912, function sd_event_source_unref(). Aborting. ~ -- 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: New Bug description: (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 55a37fe5a686 sp 7ffd9a160440 error 4 in systemd-resolved[55a37fe33000+3e000] [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15 [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15 [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in libsystemd-shared-245.so[7f66bb504000+16e000] [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in libsystemd-shared-245.so[7fdc40b2c000+16e000] [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in libsystemd-shared-245.so[7f6a92814000+16e000] [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 ip 555f9a5915e0 sp 7fff053e5e68 error 15 [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at 1991af73f2e ip 7ff194021dc9 sp 7fffa6d61680 error 4 in libsystemd-shared-245.so[7ff193ffc000+16e000] [Sun Nov 29
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
** Changed in: grub2 (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1905758] Re: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1905758 Title: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libglib2.0-0:i386 2.66.1-2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 19 17:43:35 2020 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1905758/+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 1906331] [NEW] systemd-resolve crashes fairly often (and reports various assertions)
Public bug reported: (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 55a37fe5a686 sp 7ffd9a160440 error 4 in systemd-resolved[55a37fe33000+3e000] [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15 [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15 [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in libsystemd-shared-245.so[7f66bb504000+16e000] [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in libsystemd-shared-245.so[7fdc40b2c000+16e000] [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in libsystemd-shared-245.so[7f6a92814000+16e000] [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 ip 555f9a5915e0 sp 7fff053e5e68 error 15 [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at 1991af73f2e ip 7ff194021dc9 sp 7fffa6d61680 error 4 in libsystemd-shared-245.so[7ff193ffc000+16e000] [Sun Nov 29 22:03:20 2020] systemd-resolve[1661941]: segfault at 5625966828e0 ip 5625966828e0 sp 7ffdf5a8bb48 error 15 [Sun Nov 29 22:32:44 2020] systemd-resolve[1662604]: segfault at 199f18ae01d ip 7f457c9d1dc9 sp 7ffc62b80ef0 error 4 in libsystemd-shared-245.so[7f457c9ac000+16e000] [Sun Nov 29 23:12:23 2020] systemd-resolve[1664072]: segfault at 73b8 ip 562619f8c93a sp 7ffd527b7ef0 error 6 in systemd-resolved[562619f61000+3e000] [Sun Nov 29 23:22:34 2020] systemd-resolve[1664423]: segfault at 19aaa4d4c00 ip 7f2621539dc9 sp 7ffc73102280 error 4 in libsystemd-shared-245.so[7f2621514000+16e000] [Mon Nov 30 00:12:23 2020] systemd-resolve[1666158]: segfault at 19b5c72000a ip 7f530b5c1dc9 sp 7ffc6007ccf0 error 4 in libsystemd-shared-245.so[7f530b59c000+16e000] [Mon Nov 30 00:47:54 2020] systemd-resolve[1667280]: segfault at 10036 ip 7f0736b8bbe8 sp 7fffed4d3cb0 error 4 in libsystemd-shared-245.so[7f0736acc000+16e000] [Mon Nov 30 01:57:53 2020] systemd-resolve[1669463]: segfault at 558d6b61c0c0 ip 558d6b61c0c0 sp 7ffc68df7198 error 15 [Mon Nov 30 02:58:08 2020] traps: systemd-resolve[1672553] general protection fault ip:55b967d86760 sp:7fffaecf4468 error:0 in systemd-resolved[55b967d5f000+3e000] [Mon Nov 30 03:38:08 2020] systemd-resolve[1673682]: segfault at 19e3c4d5050 ip 7fdf0ba29dc9 sp 7ffe4d561430 error 4 in libsystemd-shared-245.so[7fdf0ba04000+16e000] [Mon Nov 30 05:07:22 2020] systemd-resolve[1681387]: segfault at 7f7e31c39c10 ip 7f7e31c39c10 sp 7ffe5ad31f58 error 15 in libc-2.31.so[7f7e31c39000+3000] [Mon Nov 30 05:47:43 2020] systemd-resolve[1682761]: segfault at 1a00b86dff0 ip 7f69066c9dc9 sp 7fff079c4fd0 error 4 in libsystemd-shared-245.so[7f69066a4000+16e000] [Mon Nov 30 06:17:42 2020] systemd-resolve[1684158]: segfault at 1a070831ad3 ip 7f308aa19dc9 sp
[Touch-packages] [Bug 1906316] Re: Xorg crash
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906316 Title: Xorg crash Status in xorg-server package in Ubuntu: New Bug description: Just crached all of a sudden. I was in a terminal using dialog... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 22:50:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 Ti] [1462:3750] InstallationDate: Installed on 2020-08-04 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.1 dmi.board.name: MS-78511 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 3.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-B08911 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1906316/+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 1906078] Re: Whoopsie sends bug reports automatically without consent
** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1906078 Title: Whoopsie sends bug reports automatically without consent Status in whoopsie package in Ubuntu: New Bug description: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1906078/+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 1906315] Re: apt update hangs on Turkish lang
Need like an strace and a term log to analyze ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1906315 Title: apt update hangs on Turkish lang Status in apt package in Ubuntu: Incomplete Bug description: When I do "sudo apt update" hangs on Tr lang. I made fix it by LANG=C env but that is not really fix(!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 1 00:49:56 2020 InstallationDate: Installed on 2020-11-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+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 1906315] Re: apt update hangs on Turkish lang
/var/log/apt/term.log that is -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1906315 Title: apt update hangs on Turkish lang Status in apt package in Ubuntu: Incomplete Bug description: When I do "sudo apt update" hangs on Tr lang. I made fix it by LANG=C env but that is not really fix(!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 1 00:49:56 2020 InstallationDate: Installed on 2020-11-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+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 1835660] Re: initramfs unpacking failed
@twetzel21 this is not related to those changes at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1906316] Re: Xorg crash
I do not understand why this is so complicated. You dont see Microsoft or apple or google asking you to log in to a web page and diddle with some kind of ticket system... just ask for permission and collect the info. If you need to probe more and dig deeper, fine... go a head... Ask if you may contact the user... why all this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906316 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Just crached all of a sudden. I was in a terminal using dialog... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 22:50:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 Ti] [1462:3750] InstallationDate: Installed on 2020-08-04 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.1 dmi.board.name: MS-78511 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 3.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-B08911 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906316/+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 1906316] [NEW] Xorg crash
Public bug reported: Just crached all of a sudden. I was in a terminal using dialog... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 22:50:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 Ti] [1462:3750] InstallationDate: Installed on 2020-08-04 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.1 dmi.board.name: MS-78511 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 3.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-B08911 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906316 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Just crached all of a sudden. I was in a terminal using dialog... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date:
[Touch-packages] [Bug 1906315] [NEW] apt update hangs on Turkish lang
Public bug reported: When I do "sudo apt update" hangs on Tr lang. I made fix it by LANG=C env but that is not really fix(!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 1 00:49:56 2020 InstallationDate: Installed on 2020-11-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1906315 Title: apt update hangs on Turkish lang Status in apt package in Ubuntu: New Bug description: When I do "sudo apt update" hangs on Tr lang. I made fix it by LANG=C env but that is not really fix(!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 1 00:49:56 2020 InstallationDate: Installed on 2020-11-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+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 1906309] Re: printer configuration with ubuntu 20.04 - Epson ET 2750 printer not found
I am not very familiar with how all this works. Could you please tell me what would my next plan of action be? I have problems with all our laptops and have lost so many documents as a result of trying to install Ubuntu 20.04. Please help -- 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/1906309 Title: printer configuration with ubuntu 20.04 - Epson ET 2750 printer not found Status in cups package in Ubuntu: New Bug description: I don't know if this is a bug, just have been having lots of problems with all my laptops after trying to get new version of ubuntu. Don't know if my version is corrupt. Ubuntu 20.04.1 Lts Focal When i Typed 'apt-cache policy pkgname', N : Unable to locate package pkgname I was trying to send document to print (which was no problem) until 3 days ago Nothing happened - it said printer error. I deleted the printer and tried to reinstall it - but still it wouldn't print. Also all my libreoffice files have been converted to excel format in read only format. Why? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 14:40:52 2020 InstallationDate: Installed on 2018-04-30 (945 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ MachineType: Hewlett-Packard HP Folio 13 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=0950c369-cf83-439d-aabf-379cc7bfdd0d ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-09-15 (75 days ago) dmi.bios.date: 03/05/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Folio 13 Notebook PC dmi.product.sku: A3V88PA#UUF dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1906309/+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 1899041] Re: Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - patch available
** Bug watch added: Debian Bug tracker #976091 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091 Importance: Unknown Status: Unknown ** Tags added: patch-accepted-upstream ** Summary changed: - Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - patch available + Gnome-Network-Displays crashes with Intel Wireless AC due to wpasupplicant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899041 Title: Gnome-Network-Displays crashes with Intel Wireless AC due to wpasupplicant Status in wpa package in Ubuntu: Confirmed Status in wpa package in Debian: Unknown Bug description: When using Gnome-Network-Displays on a laptop with an Intel Wireless AC 9462/9560 card, wpasupplicant crashes. This reproducible bug can be fixed with this patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ A further description can be found here: https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899041/+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 1906309] [NEW] printer configuration with ubuntu 20.04 - Epson ET 2750 printer not found
Public bug reported: I don't know if this is a bug, just have been having lots of problems with all my laptops after trying to get new version of ubuntu. Don't know if my version is corrupt. Ubuntu 20.04.1 Lts Focal When i Typed 'apt-cache policy pkgname', N : Unable to locate package pkgname I was trying to send document to print (which was no problem) until 3 days ago Nothing happened - it said printer error. I deleted the printer and tried to reinstall it - but still it wouldn't print. Also all my libreoffice files have been converted to excel format in read only format. Why? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 14:40:52 2020 InstallationDate: Installed on 2018-04-30 (945 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ MachineType: Hewlett-Packard HP Folio 13 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=0950c369-cf83-439d-aabf-379cc7bfdd0d ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-09-15 (75 days ago) dmi.bios.date: 03/05/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Folio 13 Notebook PC dmi.product.sku: A3V88PA#UUF dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1906309 Title: printer configuration with ubuntu 20.04 - Epson ET 2750 printer not found Status in cups package in Ubuntu: New Bug description: I don't know if this is a bug, just have been having lots of problems with all my laptops after trying to get new version of ubuntu. Don't know if my version is corrupt. Ubuntu 20.04.1 Lts Focal When i Typed 'apt-cache policy pkgname', N : Unable to locate package pkgname I was trying to send document to print (which was no problem) until 3 days ago Nothing happened - it said printer error. I deleted the printer and tried to reinstall it - but still it wouldn't print. Also all my libreoffice files have been converted to excel format in read only format. Why? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 14:40:52 2020 InstallationDate: Installed on 2018-04-30 (945 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ MachineType: Hewlett-Packard HP Folio 13 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=0950c369-cf83-439d-aabf-379cc7bfdd0d ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-09-15 (75 days ago) dmi.bios.date: 03/05/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Folio 13
[Touch-packages] [Bug 1894329] Please test proposed package
Hello Usarin, or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1894329] Re: ZFS revert from grub menu not working.
Hello Usarin, or anyone else affected,
Accepted zfs-linux into groovy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.4-1ubuntu11.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: zfs-linux (Ubuntu Groovy)
Status: Triaged => Fix Committed
** Changed in: zfs-linux (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906267/+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 1906292] [NEW] audio device changed after unlock gdm
Public bug reported: Hello, after a long time of inactivites, my session automatically locked (GDM). When I unlock it, I can no more hear audio, device is set to spdif instead of hdmi/displayport2. I have to kill pulseaudio to retablish the good device hdmi/displayport2. It's a very annoying bug. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: romain419906 F pulseaudio /dev/snd/pcmC1D7p: romain419906 F...m pulseaudio /dev/snd/controlC0: romain419906 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 19:17:44 2020 InstallationDate: Installed on 2012-07-07 (3068 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-03 (241 days ago) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7752 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906292 Title: audio device changed after unlock gdm Status in pulseaudio package in Ubuntu: New Bug description: Hello, after a long time of inactivites, my session automatically locked (GDM). When I unlock it, I can no more hear audio, device is set to spdif instead of hdmi/displayport2. I have to kill pulseaudio to retablish the good device hdmi/displayport2. It's a very annoying bug. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: romain419906 F pulseaudio /dev/snd/pcmC1D7p: romain419906 F...m pulseaudio /dev/snd/controlC0: romain419906 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 19:17:44 2020 InstallationDate: Installed on 2012-07-07 (3068 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-03 (241 days ago) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7752 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906292/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Ok, I left the 2 lines disabled and found a fix for the dummy audio here: https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-issue-in.html Seems to be working for me so far. Thanks for everyones help. -- 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/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1903329] Re: SRU the current 2.48.9 stable update
Uploaded librsvg 2.48.9-1ubuntu0.20.04.1, now sitting in the focal unapproved queue, waiting for the SRU team to review and accept it. ** Changed in: librsvg (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Focal: In Progress Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1835660] Re: initramfs unpacking failed
Dimitri, I note your comment #106 about secureboot patches upstream. If I recall correctly, a linux security update came down through Ubuntu Updater about the same time or just prior to the LTS 20.04.1 updates in mid September. A number of issues with LTS 20.04.1 appeared following two "batches" of September Ubuntu updates. To the extent that these issues may be inter-related -- at least insofar as being triggered by upstream Linux security change(s) -- please note the bug numbers listed in post #93 above. If not relevant to this particular bug, then please disregard in deference to the other individual bug numbers; if inter-related, then perhaps this can be helpful. -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 I guess I should add some info to my post yesterday. I'm running on a Gigabyte Aorus Elite X570 MB with a Zotec GTX 1070 and I have nothing hooked up to an HDMI port on either. Disabling load-module module-switch-on-connect did nothing, still defaulting to HDMI. Disabling both lines load-module module-switch-on-port-available and load-module module-switch-on-connect shows Dummy audio after restart. -- 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/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Additional observation: I've tried using Ubuntu LTS 20.04 download images from July and August, selecting the option to install third party drivers. These images worked flawlessly at the end of the summer. But since the mid-September updates, even these earlier iso's of Ubuntu LTS 20.04 Desktop failed with this same install crash. So it would appear that there were changes in late September to things external to the Ubuntu download iso itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
With reference to post #132 above: If this is relevant to this issue I also am experiencing problems with switching drivers for the device on my systems that uses (or can use) a Ubuntu third party driver. Specifically nVidia for the GeForce 940MX. Changing between nVidia driver versions (all within the selections provided by Ubuntu's Updater) appears to succeed but driver performance is not correct. I restart after each driver change. I've seen screen tearing, freezing, video stuttering, etc while playing locally stored videos. I've used the same video file to test and the results remain unpredictable. Even going back to the generic xorg driver does not seem to fully stabilize performance of the 940MX. None of these issues were present prior to the mid- September Ubuntu updates associated with 20.04.1; and the nVidia driver(s) provided performance superior to the xorg version. Trying to reload Ubuntu in an attempt to squash these bugs triggered this crash bug. I obviously managed to work around it by NOT selecting third party drivers on install, but that necessitates changing the driver after install; and that has not worked well either. If this is not relevant to this particular bug, then please disregard in deference to other bug reports. I provide this here only to assist by providing anecdotal observations in hopes that this may help in trying to resolve this third party driver related issue. And in the event that several of these bugs may be inter-related, please refer to also posts #84, 97, and 104 above regarding a group of bugs that all appeared following the mid-September Ubuntu LTS 20.04 updates; and note that there is a bug number (not listed above here) for the suspend on login issue, it is 1897185. Again: if this is not relevant to resolving this issue then disregard here. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1906091] Re: libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Please try to confirm you are actually using the official opencv
packages for Ubuntu 18.04 aka "libbopencv-videoio3.2" and not
"libopencv-video2.4v5", which is a build of opencv from Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Status in x264 package in Ubuntu:
New
Bug description:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
both libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc
location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
byte-stream=true threads=1
tune=zerolatency bitrate=400 key-
int-max=50 option-string="force-cfr=1" !
video/x-h264,profile=baseline,stream-format="byte-stream" !
h264parse ! mpegtsmux ! hlssink
location="/tmp/data%06d.ts" max-files=100
playlist-length=10 playlist-location="/tmp/kek"
target-duration=10 playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2016-05-07 (1667 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
NonfreeKernelModules: nvidia_modeset nvidia
Package: x264 2:0.152.2854+gite9a5903-2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Tags: bionic third-party-packages
Uname: Linux 4.15.0-118-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
(3 remove tty events and 2 RUN events) ** Attachment added: "Wrong Remove" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+attachment/5439655/+files/Remove_NO.txt -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
here my RUN script /opt/trx/gprs-modem-symlink-handler.bash ** Attachment added: "RUN script" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+attachment/5439653/+files/gprs-modem-symlink-handler.bash -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
Wrong Remove -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
Correct Remove (3 remove tty events and 3 RUN events) ** Attachment added: "Remove OK" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+attachment/5439654/+files/Remove_OK.txt -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
Whooops, I read to avoid pastebin links, I'll attach files from original post. here modem rule in /etc/udev/rules.d/ ** Attachment added: "Modem Rule" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+attachment/5439649/+files/61-gprs-modem.rules -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
Thank you for your response. I wasn't able to run properly "apport-collect" due to browser/screen problem (I'm on an embedded device). Here result of ubuntu-bug udev ** Attachment added: "ubuntu-bug udev report" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+attachment/5439645/+files/apport.udev.rx2s9f5w.apport -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: enes (ekko52) => (unassigned) ** Changed in: apt (Ubuntu) Assignee: enes (ekko52) => (unassigned) ** Changed in: apt (Ubuntu Bionic) Assignee: enes (ekko52) => (unassigned) ** Changed in: apt (Ubuntu Focal) Assignee: enes (ekko52) => (unassigned) ** Changed in: apt (Ubuntu Groovy) Assignee: enes (ekko52) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update
librsvg 2.50.2+dfsg-1 is now in hirsute. We can proceed with the SRU. ** Changed in: librsvg (Ubuntu) Status: Triaged => Won't Fix ** Changed in: librsvg (Ubuntu) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Focal: Triaged Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1906267] [NEW] IntelHD audio not detected after upgrading to Ubuntu 20.10
Public bug reported: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906267/+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 992464] Re: Menu not accessible when run via ssh xforwarding
I'm seeing the same problem with gnome-mines over SSH from 20.04 to 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/992464 Title: Menu not accessible when run via ssh xforwarding Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Symptom: When starting e.g., evince via X11 Forwarding (ssh -X), then the menu is not displayed. Test setup: A ubuntu/precise laptop and a ubuntu/precise workstation, both 64bit. --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Package: evince 3.4.0-0ubuntu1 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=43083bcc-3306-4670-9169-937fd10be832 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Tags: precise apparmor Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-03-03 (58 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev proxy sambashare sbuild To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/992464/+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 1906091] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1906091/+attachment/5439619/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Status in x264 package in Ubuntu:
New
Bug description:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
both libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc
location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
byte-stream=true threads=1
tune=zerolatency bitrate=400 key-
int-max=50 option-string="force-cfr=1" !
video/x-h264,profile=baseline,stream-format="byte-stream" !
h264parse ! mpegtsmux ! hlssink
location="/tmp/data%06d.ts" max-files=100
playlist-length=10 playlist-location="/tmp/kek"
target-duration=10 playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2016-05-07 (1667 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
NonfreeKernelModules: nvidia_modeset nvidia
Package: x264 2:0.152.2854+gite9a5903-2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Tags: bionic third-party-packages
Uname: Linux 4.15.0-118-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1906091] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1906091/+attachment/5439618/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Status in x264 package in Ubuntu:
New
Bug description:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
both libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc
location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
byte-stream=true threads=1
tune=zerolatency bitrate=400 key-
int-max=50 option-string="force-cfr=1" !
video/x-h264,profile=baseline,stream-format="byte-stream" !
h264parse ! mpegtsmux ! hlssink
location="/tmp/data%06d.ts" max-files=100
playlist-length=10 playlist-location="/tmp/kek"
target-duration=10 playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2016-05-07 (1667 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
NonfreeKernelModules: nvidia_modeset nvidia
Package: x264 2:0.152.2854+gite9a5903-2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Tags: bionic third-party-packages
Uname: Linux 4.15.0-118-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1906091] Re: libx264-148 libx264-152 conflict segmentation fault SIGSEGV
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in both
libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc location=videoplayback.mp4
! decodebin ! videoconvert ! x264enc byte-stream=true
threads=1 tune=zerolatency
bitrate=400 key-int-max=50 option-
string="force-cfr=1" ! video/x-h264,profile=baseline,stream-
format="byte-stream" ! h264parse ! mpegtsmux !
hlssink location="/tmp/data%06d.ts" max-
files=100 playlist-length=10 playlist-
location="/tmp/kek" target-duration=10
playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.18
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2016-05-07 (1667 days ago)
+ InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: x264 2:0.152.2854+gite9a5903-2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
+ Tags: bionic third-party-packages
+ Uname: Linux 4.15.0-118-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
+ UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1906091/+attachment/5439617/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Status in x264 package in Ubuntu:
New
Bug description:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at
[Touch-packages] [Bug 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1906263 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => enes (ekko52) ** Changed in: apt (Ubuntu) Assignee: (unassigned) => enes (ekko52) ** Changed in: apt (Ubuntu Focal) Assignee: (unassigned) => enes (ekko52) ** Changed in: apt (Ubuntu Bionic) Assignee: (unassigned) => enes (ekko52) ** Changed in: apt (Ubuntu Groovy) Assignee: (unassigned) => enes (ekko52) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
P.S. I tried to reproduce it, but I cannot set time beyond 2036 (due to int limit problem), how did you acheive it? -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+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 1905560] Re: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Great, glad that you sorted it out and thanks for closing the ticket! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used Status in at-spi2-atk package in Ubuntu: Invalid Bug description: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+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 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
This is beacuse in 2036 UTC will reach int limit. To solve this bug time sohuld be stored in a long variable -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+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 1906263] [NEW] Udev Randomly Doesn't Run Run Script on Remove
Public bug reported: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: option rules run udev -- 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/1906263 Title: Udev Randomly Doesn't Run Run Script on Remove Status in systemd package in Ubuntu: New Bug description: Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) with 5.0.21-sunxi kernel. I've updated udev to latest version (237-3ubuntu10.43 500). I've written the following rule to create (and removing) symlink to modem ports: https://pastebin.com/cUwHrf1f Since many usb modems hase more than one serial i enumerate them with their port number (as just some specific serial can be used to connect) Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash https://pastebin.com/2XTCiV27 What I expect to happen is having many /dev/ttyTRXGPRSMODEM* (enumerated) when I plug-in a modem in the list, and having symlink cleared on removing. every modem listed in rule is using "option" usb serial driver. When i plug in a device I have no issues, everything works fine. But sometimes, on removing, I found that some links are still there (it's not happening everytime). I've enabled debug log with udev and found that sometimes is not calling RUN script: Here the working situation (3 tty remove events and 3 RUN events): https://pastebin.com/EKX5zMh7 And here is the buggy situation (3 tty remove events, but only 2 RUN events) with the same device as the example above: https://pastebin.com/dB7ujQ79 Since it's happening randomly I can't figure out whats causing the problem. I guess it's not the rule because on an old debian 7 release it's working fine, and on the release described above I get others symlinks removed even in the buggy situation (as in the example: two are removed, one not). It seems like sometimes udev ignores totally the run event. Last thing to report: I'm not opening these links! So are not locked or protected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906263/+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 1904192] Re: ebtables can not rename just created chain
Bfore upgrade: ubuntu@g-test:~$ sudo ebtables -t nat -N foo ubuntu@g-test:~$ sudo ebtables -t nat -E foo bar ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists Try `ebtables -h' or 'ebtables --help' for more information. Upgrade: ubuntu@g-test:~$ sudo apt install iptables Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libip4tc2 libip6tc2 libxtables12 Suggested packages: firewalld nftables The following packages will be upgraded: iptables libip4tc2 libip6tc2 libxtables12 4 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Need to get 498 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 iptables amd64 1.8.5-3ubuntu2.20.10.2 [432 kB] Get:2 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libxtables12 amd64 1.8.5-3ubuntu2.20.10.2 [28.7 kB] Get:3 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libip6tc2 amd64 1.8.5-3ubuntu2.20.10.2 [19.1 kB] Get:4 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libip4tc2 amd64 1.8.5-3ubuntu2.20.10.2 [18.7 kB] Fetched 498 kB in 0s (1465 kB/s) (Reading database ... 64660 files and directories currently installed.) Preparing to unpack .../iptables_1.8.5-3ubuntu2.20.10.2_amd64.deb ... Unpacking iptables (1.8.5-3ubuntu2.20.10.2) over (1.8.5-3ubuntu2.20.10.1) ... Preparing to unpack .../libxtables12_1.8.5-3ubuntu2.20.10.2_amd64.deb ... Unpacking libxtables12:amd64 (1.8.5-3ubuntu2.20.10.2) over (1.8.5-3ubuntu2.20.10.1) ... Preparing to unpack .../libip6tc2_1.8.5-3ubuntu2.20.10.2_amd64.deb ... Unpacking libip6tc2:amd64 (1.8.5-3ubuntu2.20.10.2) over (1.8.5-3ubuntu2.20.10.1) ... Preparing to unpack .../libip4tc2_1.8.5-3ubuntu2.20.10.2_amd64.deb ... Unpacking libip4tc2:amd64 (1.8.5-3ubuntu2.20.10.2) over (1.8.5-3ubuntu2.20.10.1) ... Setting up libip4tc2:amd64 (1.8.5-3ubuntu2.20.10.2) ... Setting up libip6tc2:amd64 (1.8.5-3ubuntu2.20.10.2) ... Setting up libxtables12:amd64 (1.8.5-3ubuntu2.20.10.2) ... Setting up iptables (1.8.5-3ubuntu2.20.10.2) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... After upgrade ubuntu@g-test:~$ sudo ebtables -t nat -N foo2 ubuntu@g-test:~$ sudo ebtables -t nat -E foo2 bar Thanks, setting verified! ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain Status in iptables: Unknown Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Groovy: Fix Committed Status in iptables source package in Hirsute: Fix Released Status in iptables package in Debian: Unknown Status in iptables package in Fedora: Fix Committed Bug description: [SRU] * Changes that went into 1.8.5 ave broken the errno handling. In particular loading extensions. Due to that it has become impossible to rename rules. * Upstream has created a fix and this backports that change to Ubuntu => http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247 [Test Case] * # ebtables -t nat -N foo # ebtables -t nat -E foo bar ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists * with the fix the above command sequence works [Where problems could occur] * The change moved code from nft_chain_user_rename to do_commandeb and therefore in theory any ebtables/xtables subcommand could be affected. Yet what it does is just resetting the error code in a better place, so while it "could" affect every subcommand it should (tm) not do so. [Other Info] * n/a --- Hi, I have an issue with ebtables that affects libvirt. While initially found in hirsute I had to realize this is broken in Groovy and even Bionic (might be a different reason back then) as well right now. But working in Focal (witch matches my memory of it being good before [1]). I was isolating the commands that libvirt runs (identical between Focal and Hirsute) to find a simplified trigger. Gladly I found one that leaves libvirt and other components out of the equation. The following works on focal, but fails on the other releases. Note: I checked which tool is in use and in both cases it is xtables-nft-multi. /usr/sbin/ebtables -> /etc/alternatives/ebtables* /etc/alternatives/ebtables -> /usr/sbin/ebtables-nft* /usr/sbin/ebtables-nft -> xtables-nft-multi* So I converted the libvirt issued commands into xtables-nft-multi just to be sure in case a system to compare has other alternatives set. Focal (Good):
[Touch-packages] [Bug 1876197] Re: Xubuntu 20.04 Guest Session Logout Fails
*** This bug is a duplicate of bug 1855350 *** https://bugs.launchpad.net/bugs/1855350 This also happens to me - NOT a guest session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1876197 Title: Xubuntu 20.04 Guest Session Logout Fails Status in lightdm package in Ubuntu: New Bug description: I've edited "/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf" so that it now has "allow-guest=true". And I'm now able to login to a Guest Session. But when I attempt to logout I get: Receiver error while trying to log out GDBus.Error.org .. Type of message "(yb)", does not match expected type "(b)" This occurs on both of the Xubuntu 20.04 machines I have, and also on a Virtualbox guest. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1876197/+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 1877762] Re: 1360x768 Vega graphics display staggered
This bug still seems to be active: https://forums.gentoo.org/viewtopic-p-8537062.html#8537062 It is still happening on my machine except the interference seems to be more corrupt along the lines of Simon's image. I believe it briefly stopped some time ago but by the time I started checking the new versions, it started up again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877762 Title: 1360x768 Vega graphics display staggered Status in Ubuntu MATE: New Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+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 1904192] Re: ebtables can not rename just created chain
Hello Christian, or anyone else affected, Accepted iptables into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables/1.8.5-3ubuntu2.20.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iptables (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain Status in iptables: Unknown Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Groovy: Fix Committed Status in iptables source package in Hirsute: Fix Released Status in iptables package in Debian: Unknown Status in iptables package in Fedora: Fix Committed Bug description: [SRU] * Changes that went into 1.8.5 ave broken the errno handling. In particular loading extensions. Due to that it has become impossible to rename rules. * Upstream has created a fix and this backports that change to Ubuntu => http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247 [Test Case] * # ebtables -t nat -N foo # ebtables -t nat -E foo bar ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists * with the fix the above command sequence works [Where problems could occur] * The change moved code from nft_chain_user_rename to do_commandeb and therefore in theory any ebtables/xtables subcommand could be affected. Yet what it does is just resetting the error code in a better place, so while it "could" affect every subcommand it should (tm) not do so. [Other Info] * n/a --- Hi, I have an issue with ebtables that affects libvirt. While initially found in hirsute I had to realize this is broken in Groovy and even Bionic (might be a different reason back then) as well right now. But working in Focal (witch matches my memory of it being good before [1]). I was isolating the commands that libvirt runs (identical between Focal and Hirsute) to find a simplified trigger. Gladly I found one that leaves libvirt and other components out of the equation. The following works on focal, but fails on the other releases. Note: I checked which tool is in use and in both cases it is xtables-nft-multi. /usr/sbin/ebtables -> /etc/alternatives/ebtables* /etc/alternatives/ebtables -> /usr/sbin/ebtables-nft* /usr/sbin/ebtables-nft -> xtables-nft-multi* So I converted the libvirt issued commands into xtables-nft-multi just to be sure in case a system to compare has other alternatives set. Focal (Good): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed Groovy/Hirsute (Fail): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed ebtables v1.8.5 (nf_tables): Chain 'testrule3' doesn't exists Try `ebtables -h' or 'ebtables --help' for more information. What might be the root cause for this? -- Old test instructions -- As I said I was tracking a fail in libvirt so the test instructions initially were around that: # the following us done as 2nd level guest (to not mess with the host, # but works on bare metal jst as much) uvt-kvm create --host-passthrough --memory 2048 --cpu 4 --disk 16 --password=ubuntu hirsute-kvm release=hirsute arch=amd64 label=daily # On guest then sudo apt update sudo apt install uvtool uvtool-libvirt uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=hirsute uvt-kvm create
[Touch-packages] [Bug 1906243] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439549/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906243] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439548/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906243] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439547/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906120] Re: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
Thank you for your bug report, you would probably have a better chance to get a reply reporting upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906120 Title: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROOT_PATH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROUTERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_STATIC_ROUTES=1 Nov 28
[Touch-packages] [Bug 1906243] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439551/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906243] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439550/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906243] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1906243/+attachment/5439546/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+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 1906243] [NEW] Audio comes out through system speakers when headset autoconnects
Public bug reported: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. - It doesn't work only when it connects automatically. Always works when I - connect it manually. + It doesn't work only when it connects automatically. Always works when I connect it manually. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sujit 1394 F pulseaudio + /dev/snd/controlC0: sujit 1394 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-28 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: pulseaudio 1:13.99.1-1ubuntu3.8 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 + Tags: focal + Uname: Linux 5.4.0-54-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/13/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A07 + dmi.board.name: 0JKRPT + dmi.board.vendor: Dell Inc. + dmi.board.version: A07 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: + dmi.product.name: Vostro 3446 + dmi.product.sku: 0662 + dmi.product.version: Not Specified + dmi.sys.vendor: Dell Inc. -- 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/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. ---
[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface
Sadly, the journalctl logs don't go back that far now.
It failed on a baremetal server, not a cloud.
--
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/1904549
Title:
MTU is not set on vlan interface
Status in netplan:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Hello,
Upon changing the following configuration, adding the MTU lines, I
ended up with the VLAN interfaces still in MTU 1500 after a `netplan
generate && netplan apply`
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
# uname -a
Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l netplan.io
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 VersionArchitecture Description
+++-==-==--===
ii netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network
configuration abstraction for various backends
==
# This is the network config written by 'subiquity'
network:
ethernets:
ens10f0: {}
ens10f1: {}
ens10f2: {}
ens10f3: {}
ens1f0: {}
ens1f1: {}
bonds:
bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
vlans:
vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]
vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000
vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
version: 2
==
And here is the result after the `netplan apply`
===
# netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR
Flg
bond-cor 9000 19448696 0 0 0 6858767 0 1 0
BMmRU
bond-man 1500 7981199 0 1 0 1755800 0 2 0
BMmRU
bond-oam 9000 6236232 0 0 0 4488877 0 1 0
BMmU
ens10f0 9000 3961100 0 0 0 2271891 0 0 0
BMsU
ens10f1 9000 2288169 0 0 0 2218120 0 0 0
BMsU
ens10f2 1500 2506083 0 0 0 1226075 0 0 0
BMsRU
ens10f3 1500 5475116 0 0 0529725 0 0 0
BMsRU
ens1f09000 9513761 0 0 0 3970465 0 0 0
BMsRU
ens1f19000 9934935 0 0 0 2888302 0 0 0
BMsRU
lo 6553621336 0 0 0 21336 0 0 0
LRU
[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Thank you for your bug report Till, do you know what impact that priority change failing has? Could you check with the security team if that call should be allowed by default in the cups profile? ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue with: Ubuntu 20.04.1 LTS Lenovo ThinkPad P1 (2nd Gen) Jabra Elite 85h -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1906101] Re: no sound via speakers or headphone port on Carbon X1 6th
I managed to get sound working by following the steps here: https://help.ubuntu.com/community/SoundTroubleshooting More specifically, I ran this command: sudo apt --purge reinstall linux-sound-base alsa-base alsa-utils linux-image-`uname -r` libasound2 After a restart, sound was available again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1906101 Title: no sound via speakers or headphone port on Carbon X1 6th Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded from 18.04 to 20.04. The sound worked without problems before upgrade, but now I don'get any sound at all from the speakers or the headphone jack. This seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although that bug is reported as resolved). I tried adding model=generic dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it did not help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 28 18:36:36 2020 InstallationDate: Installed on 2018-07-27 (855 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1906101/+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
