[Touch-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu4 --- pango1.0 (1.44.7-2ubuntu4) focal; urgency=medium * Backport some Debian changes to try to fix upgrade issues (lp: #1871960) [ Simon McVittie ] * d/shlibs.local: Upgrade all binary packages in lockstep. Like many projects where one source package builds multiple binary packages, Pango has private headers that share non-public interfaces between its binary packages. Upgrading one binary package from this source without upgrading the others is not something that its upstream developers are ever going to test or support, and neither should we. (Closes: #958017) * libpango-1.0-0: Add Breaks on older libpango*-1.0-0. This should ensure that buster users can't get a broken partial upgrade by upgrading only libpango-1.0-0, but not the others, from 1.42.x to 1.44.x. -- Sebastien Bacher Tue, 21 Apr 2020 18:02:31 +0200 ** Changed in: pango1.0 (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in libgtk3-perl package in Ubuntu: Confirmed Status in pango1.0 package in Ubuntu: Fix Released Status in libgtk3-perl source package in Focal: Confirmed Status in pango1.0 source package in Focal: Fix Released Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+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 1874021] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357823/+files/ProcEnviron.txt ** Description changed: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True - modified.conffile..etc.default.avahi-daemon: - # 1 = Try to detect unicast dns servers that serve .local and disable avahi in - # that case, 0 = Don't try to detect .local unicast dns servers, can cause - # troubles on misconfigured networks - AVAHI_DAEMON_DETECT_LOCAL=0 - AVAHI_DAEMON_START=1 - mtime.conffile..etc.avahi.avahi-daemon.conf: 2020-04-21T09:03:32.502101 - mtime.conffile..etc.default.avahi-daemon: 2020-04-21T09:11:39.632727 - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu27 - Architecture: amd64 - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 20.04 - InstallationDate: Installed on 2020-04-08 (13 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) - Package: avahi-daemon 0.7-4ubuntu7 - PackageArchitecture: amd64 - ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 - Tags: focal - Uname: Linux 5.4.0-25-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo - _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
apport information ** Description changed: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.avahi-daemon: # 1 = Try to detect unicast dns servers that serve .local and disable avahi in # that case, 0 = Don't try to detect .local unicast dns servers, can cause # troubles on misconfigured networks AVAHI_DAEMON_DETECT_LOCAL=0 AVAHI_DAEMON_START=1 mtime.conffile..etc.avahi.avahi-daemon.conf: 2020-04-21T09:03:32.502101 mtime.conffile..etc.default.avahi-daemon: 2020-04-21T09:11:39.632727 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-08 (13 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: avahi-daemon 0.7-4ubuntu7 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357821/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
journalctl ** Attachment added: "jctl.txt" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+attachment/5357824/+files/jctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357822/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357818/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357819/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] modified.conffile..etc.avahi.avahi-daemon.conf.txt
apport information ** Attachment added: "modified.conffile..etc.avahi.avahi-daemon.conf.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357820/+files/modified.conffile..etc.avahi.avahi-daemon.conf.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
apport information ** Tags added: apport-collected ** Description changed: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-08 (13 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: avahi-daemon 0.7-4ubuntu7 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + modified.conffile..etc.default.avahi-daemon: + # 1 = Try to detect unicast dns servers that serve .local and disable avahi in + # that case, 0 = Don't try to detect .local unicast dns servers, can cause + # troubles on misconfigured networks + AVAHI_DAEMON_DETECT_LOCAL=0 + AVAHI_DAEMON_START=1 + mtime.conffile..etc.avahi.avahi-daemon.conf: 2020-04-21T09:03:32.502101 + mtime.conffile..etc.default.avahi-daemon: 2020-04-21T09:11:39.632727 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1874021/+attachment/5357817/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1827263] Re: mod_brotli missing in Apache Web Server 2.4.29
Sorry I am a newbie here. But is it possible this was meant to be under Apache2 project? In which case it might be a duplicate of: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1708426 Sorry for noise if I am totally wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1827263 Title: mod_brotli missing in Apache Web Server 2.4.29 Status in curl package in Ubuntu: Confirmed Bug description: Apache Module mod_brotli Description: Compress content via Brotli before it is delivered to the client Status: Extension Module Identifier:brotli_module Source File: mod_brotli.c Compatibility:Available in version 2.4.26 and later. See https://httpd.apache.org/docs/2.4/mod/mod_brotli.html > lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 > apt-cache policy apache2 apache2: Installed: 2.4.29-1ubuntu4.6 Candidate: 2.4.29-1ubuntu4.6 Version table: *** 2.4.29-1ubuntu4.6 500 500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages 500 http://apt.dreamcompute.com bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://apt.dreamcompute.com bionic/main amd64 Packages It was expected to have de following files: /usr/lib/apache2/modules/mod_brotli.so /etc/apache2/mods-available/brotli.load /etc/apache2/mods-available/brotli.conf But the files are missing and the package does not depend in libbrotli1 or libbrotli-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1827263/+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 1776475] Re: Unlocking existing session often requires several attempts.
I've opened a new bug report: Bug #1874178 I'll mark myself as not affected by this one. -- 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/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1874178] [NEW] Unlocking existing session needs two attempts after selecting Switch User
Public bug reported: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1874178 Title: Unlocking existing session needs two attempts after selecting Switch User Status in lightdm package in Ubuntu: New Bug description: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874178/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
I have verified that enabling the bochs-drm kernel module on bionic does not cause any regressions for PowerKVM machines when the video device is VGA=std. TLDR: See Screenshot: https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png This is in response to the main cause of regression concern, LP #1378648, which got bochs-drm disabled in the first place, on yakkety. On Christian's advice, I created a ppc64el instance on Canonistack, with the m1.medium flavor and c8c120bd-3d55-4e2d-8cc5-93039a62524f image (ubuntu/ubuntu-bionic-18.04-ppc64el-server-20200407-disk1.img). >From there, I installed the KVM packages and a xfce4 desktop, and got xrdp working. I then installed virt-manager. I modprobed the kvm_pr kernel module on my instance to enable nested kvm on ppc64el. >From there, I installed Ubuntu 18.04.4 Server ppc64el, using virt- manager. The "Machine Type" was pseries-2.12, and the Video Model was set to "VGA" [1]. [1]: https://launchpadlibrarian.net/475658622/Screenshot%20from%202020-04-22%2015-14-04.png Upon booting, the system was using the Open Firmware frame buffer: [0.888072] Using unsupported 800x600 vga at 20008100, depth=32, pitch=3200 [0.890480] Console: switching to colour frame buffer device 100x37 [0.892181] fb0: Open Firmware frame buffer device on /pci@8002000/vga@6 $ cat /proc/fb 0 OFfb vga Which is what LP #1378648 wanted. I then enabled my ppa where my test packages were built: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test and installed new kmod and 4.15.0-96-generic test builds with bochs-drm enabled in the kernel config, and removed from the kmod blacklist. I then rebooted, and found that system boots successfully, and does not get hung up at the bug in LP #1378648, indicating that it has been fixed before 4.15. I checked "lsmod" and bochs-drm has been loaded, and looking at dmesg, initially the Open Firmware frame buffer device is used, and later in the boot, bochs-drm is loaded, and takes over the frame buffer. See screenshot [2] for proof that bochs-drm is running and functions correctly in virt-manager. [2]: https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png A complete dmesg from this boot can be found here [3]. [3] https://paste.ubuntu.com/p/Q8V7fKnRzz/ Interesting parts: [0.893046] Using unsupported 800x600 vga at 20008100, depth=32, pitch=3200 [0.895482] Console: switching to colour frame buffer device 100x37 [0.897270] fb0: Open Firmware frame buffer device on /pci@8002000/vga@6 ... [2.041835] checking generic (20008100 1d4c00) vs hw (20008100 100) [2.041836] fb: switching to bochsdrmfb from OFfb vga [2.042568] Console: switching to colour dummy device 80x25 [2.045581] [drm] Found bochs VGA, ID 0xb0c5. [2.046100] [drm] Framebuffer size 16384 kB @ 0x20008100, mmio @ 0x20008200. [2.058141] [TTM] Zone kernel: Available graphics memory: 504512 kiB [2.058883] [TTM] Initializing pool allocator [2.059372] [TTM] Initializing DMA pool allocator [2.074890] Console: switching to colour frame buffer device 128x48 [2.089805] bochs-drm :00:06.0: fb0: bochsdrmfb frame buffer device [2.090549] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:06.0 on minor 0 $ cat /proc/fb 0 bochsdrmfb With good dmesg outputs, and positive test results in virt-manager, I am happy to say that enabling bochs-drm will not cause any regressions on ppc64el, and with that, I hope it satisfies your request for testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic.
[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
Attached is proof the VM is using VGA=std for the ppc64el test. ** Attachment added: "Proof VM is running VGA=std on ppc64el" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357796/+files/Screenshot%20from%202020-04-22%2015-14-04.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) sudo add-apt-repository ppa:mruffell/sf272653-test 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod 4) sudo reboot 5) uname -rv
[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
Attached is screenshot proof that bochs-drm functions correctly on 4.15.0-96-generic ppc64el, and does not cause any regressions when bochs-drm is enabled on ppc64el. ** Attachment added: "bochs-drm functions correctly on ppc64el" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357795/+files/Screenshot%20from%202020-04-22%2015-14-13.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) sudo add-apt-repository ppa:mruffell/sf272653-test 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic
[Touch-packages] [Bug 1865504] Re: hwclock reports incorrect status in audit message
** Changed in: util-linux (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Released
Status in util-linux source package in Eoan:
Fix Released
Status in util-linux package in Debian:
Confirmed
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 597056] Re: HP Touchsmart 600-1005xt No sound from Internal Speakers
Hello, I have Ubuntu 18.04 installed on my HP touchsmart 600. Audio still doesn't work either the internal speakers, or if I connect outside speakers through 3.5mm audio jack. A USB headset works though and I can listen to YouTube using it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/597056 Title: HP Touchsmart 600-1005xt No sound from Internal Speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Found there is no internal speaker output from hp touchsmart 600-1005xt in all releases of Ubuntu 8.04 to 10.04LTS (64bit) with updated alsa-base (on 1.0.22.1 in Lucid now). All outputs & inputs work except the Internal speakers. I Checked all alsamixer levels, I have also noticed the nodeid's it seem to be mapped 0x15 - 0x0d - 0x03 (21 - 13 - 3) for internal speakers which gives same results (no audio) in osx Applehda.kext. The Headphone nodeid's of 0x14 - 0x0c - 0x02 (20 - 12 - 2) seem to work in all Ubuntu Dists & OSx as well. Windows 7 Driver everything works of course. Is Bios sending wrong pin configs for internal audio? if so what would the resolution be? here is my alsa-information from alsa-info.sh attached, My only guess is the pin configs how do you change them in alsa driver & how could I get the correct ones if the bios was sending wrong pathmaps? I should also note I've tried most of the model flags in alsa-base.conf in the alc888 documentation & rebooted countless times, model=auto shows the internal speaker but sound comes out headphones plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/597056/+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 1870410] Re: wireless does not work on boot on RPi 3s
** Changed in: systemd (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1870410 Title: wireless does not work on boot on RPi 3s Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Bug description: I've setup a wireless config in /etc/netplan/config.yaml and it does not activate on boot. I have to run 'sudo netplan apply' to get my wireless connected. This works fine on an RPi4 but not an RPi3B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.2-1ubuntu2 ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24 Uname: Linux 5.4.0-1006-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu21 Architecture: armhf Date: Thu Apr 2 19:02:27 2020 Lspci: Lsusb: Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+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 1870410] Re: wireless does not work on boot on RPi 3s
** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382713 -- 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/1870410 Title: wireless does not work on boot on RPi 3s Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Bug description: I've setup a wireless config in /etc/netplan/config.yaml and it does not activate on boot. I have to run 'sudo netplan apply' to get my wireless connected. This works fine on an RPi4 but not an RPi3B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.2-1ubuntu2 ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24 Uname: Linux 5.4.0-1006-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu21 Architecture: armhf Date: Thu Apr 2 19:02:27 2020 Lspci: Lsusb: Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382712 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal unlinked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382712 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+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 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
I tested an upgrade from Bionic to Focal with -proposed enabled (I had to remove the disabling of -proposed in DistUpgradeController.py) and did not encounter any of the following error messages: GLib-GObject-WARNING **: specified class size for type 'PangoCairoFcFont' is smaller than the parent type's 'PangoFcFont' class size at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-GObject-CRITICAL **: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. I had seen them when I tried upgrading the same virtual machine when -proposed was not enabled. Attached you'll find my apt-term.log from the successful upgrade. ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+attachment/5357734/+files/apt-term.log ** Also affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: pango1.0 (Ubuntu Focal) Status: New => Confirmed ** Changed in: pango1.0 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: pango1.0 (Ubuntu Focal) Milestone: None => ubuntu-20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in libgtk3-perl package in Ubuntu: Confirmed Status in pango1.0 package in Ubuntu: Confirmed Status in libgtk3-perl source package in Focal: Confirmed Status in pango1.0 source package in Focal: Confirmed Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+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 1873658] Re: Deb Files are not associated with an application that manages packages
There is no update available yet that will fix this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Confirmed Status in gdebi source package in Focal: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Same problem for me on Raspi 4 (bridged networking) I have found a quick and dirty workaround: In crontab: @reboot root netplan apply -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Not SRU - N/A [scope] This is not reproducable on Eoan or Bionic; this is needed only for Focal. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1650 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 1.6M CGroup: /system.slice/systemd-networkd.service └─1650
[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
** Also affects: desktop-file-utils (Ubuntu Focal) Importance: High Assignee: Ken VanDine (ken-vandine) Status: Confirmed ** Also affects: gdebi (Ubuntu Focal) Importance: High Status: Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Confirmed Status in gdebi source package in Focal: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor
seems related to https://bugs.launchpad.net/ubuntu/+bug/1857761 -- 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/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor Status in systemd package in Ubuntu: New Bug description: I use "do nothing" (... I guess, "ne rien faire" in french) option on both battery and supply in power manager. It works until I plug an external monitor (DisplayPort), disconnect, then it suspends when closing lid. Changing options changes nothing in /etc/systemd/logind.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool. System: Toshiba Tecra A50-A-130 Linux Mint 19 (= bionic) Cinnamon 3.8.9 5.3.0-46-generic Intel© Core™ i7-4600M CPU @ 2.90GHz × 2 apt-cache policy systemd systemd: Installé : 237-3ubuntu10.39 Candidat : 237-3ubuntu10.39 Table de version : *** 237-3ubuntu10.39 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+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 1874144] [NEW] Suspends when lid closed despite "do nothing" option after using ext monitor
Public bug reported: I use "do nothing" (... I guess, "ne rien faire" in french) option on both battery and supply in power manager. It works until I plug an external monitor (DisplayPort), disconnect, then it suspends when closing lid. Changing options changes nothing in /etc/systemd/logind.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool. System: Toshiba Tecra A50-A-130 Linux Mint 19 (= bionic) Cinnamon 3.8.9 5.3.0-46-generic Intel© Core™ i7-4600M CPU @ 2.90GHz × 2 apt-cache policy systemd systemd: Installé : 237-3ubuntu10.39 Candidat : 237-3ubuntu10.39 Table de version : *** 237-3ubuntu10.39 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor Status in systemd package in Ubuntu: New Bug description: I use "do nothing" (... I guess, "ne rien faire" in french) option on both battery and supply in power manager. It works until I plug an external monitor (DisplayPort), disconnect, then it suspends when closing lid. Changing options changes nothing in /etc/systemd/logind.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool. System: Toshiba Tecra A50-A-130 Linux Mint 19 (= bionic) Cinnamon 3.8.9 5.3.0-46-generic Intel© Core™ i7-4600M CPU @ 2.90GHz × 2 apt-cache policy systemd systemd: Installé : 237-3ubuntu10.39 Candidat : 237-3ubuntu10.39 Table de version : *** 237-3ubuntu10.39 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+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 1873658] Re: Deb Files are not associated with an application that manages packages
Please ignore last comment. Now brings up software centre and says Failed to install File - Not Supported. ** Attachment added: "Screen Grab" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357720/+files/Capture2.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873658] Re: Deb Files are not associated with an application that manages packages
Seems to have been fixed with an update this evening? ** Attachment added: "Screen Grab" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357719/+files/Capture.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1874142] [NEW] lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait
Public bug reported: The lvm2-lvmlocking.service systemd unit installed by lvm2-lockd package has the following line: # start lockspaces and wait for them to finish starting ExecStart=@SBINDIR@/lvm vgchange --lock-start --lock-opt autowait This is unfortunately wrong: the autowait option was dropped in this commit: https://www.redhat.com/archives/lvm- devel/2015-July/msg00091.html, and attempting to specify it causes the opposite effect: no waiting is done at all. It should've said --lock-opt auto. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874142 Title: lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait Status in lvm2 package in Ubuntu: New Bug description: The lvm2-lvmlocking.service systemd unit installed by lvm2-lockd package has the following line: # start lockspaces and wait for them to finish starting ExecStart=@SBINDIR@/lvm vgchange --lock-start --lock-opt autowait This is unfortunately wrong: the autowait option was dropped in this commit: https://www.redhat.com/archives/lvm- devel/2015-July/msg00091.html, and attempting to specify it causes the opposite effect: no waiting is done at all. It should've said --lock-opt auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1874142/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** No longer affects: gnome-shell (Ubuntu) ** Project changed: gnome-shell => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #447 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/447 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work
Is this still an issue?
I have Xenial installs where this occurs occasionally. I don't have much
information other than /boot partition fills where we will get alerts.
After logging in and running apt-get autoremove the space is cleared.
apt-mark showauto 'linux-image-.*'
Show 3 kernels, which I believe is normal. (currently
linux-image-4.4.0-176-generic,linux-image-4.4.0-177-generic,
linux-image-generic)
apt-mark showmanual 'linux-image-.*'
Does not show any results.
/etc/apt/apt.conf.d/50unattended-upgrades has the following uncommented:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}ESM:${distro_codename}";
};
Unattended-Upgrade::Remove-Unused-Dependencies "true";
unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6
--
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/1267059
Title:
"Unattended-Upgrade::Remove-Unused-Dependencies" does not work
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Precise:
Fix Released
Status in unattended-upgrades source package in Trusty:
Fix Released
Bug description:
I have a system that runs unattended-upgrades just fine. Now i want to
automate removal of old kernels and kernel header packages that are
accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
Dependencies "true";'. But it doesn't work.
Details: Lots of stuff pending autoremoval:
$ apt-get --assume-no autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic
linux-image-3.2.0-51-generic linux-image-3.2.0-52-generic
linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic
linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic
0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
After this operation, 2,893 MB disk space will be freed.
Do you want to continue [Y/n]? N
Abort.
Note that the majority of these packages have been installed by
unattended-upgrades from precise-security.
According to the comments within/etc/apt/apt.conf.d/50unattended-
upgrades, this should automate autoremoval:
// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";
but nothing happens (note the line "Packages that are auto removed: ''
":
$ unattended-upgrades --debug --dry-run
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=precise-security']
adjusting candidate version: ''
adjusting candidate version: ''
adjusting candidate version: ''
adjusting candidate version: ''
adjusting candidate version: ''
adjusting candidate version: ''
Checking: bc ([""])
Checking: grub-common ([""])
Checking: grub-pc ([""])
Checking: grub-pc-bin ([""])
Checking: grub2-common ([""])
Checking: iproute ([""])
Checking: landscape-common ([""])
pkgs that look like they should be upgraded:
Fetched 0 B in 0s (0 B/s)
blacklist: []
Packages that are auto removed: ''
InstCount=0 DelCount=0 BrokenCout=0
No packages found that can be upgraded unattended
I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+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 1827263] Re: mod_brotli missing in Apache Web Server 2.4.29
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1827263 Title: mod_brotli missing in Apache Web Server 2.4.29 Status in curl package in Ubuntu: Confirmed Bug description: Apache Module mod_brotli Description: Compress content via Brotli before it is delivered to the client Status: Extension Module Identifier:brotli_module Source File: mod_brotli.c Compatibility:Available in version 2.4.26 and later. See https://httpd.apache.org/docs/2.4/mod/mod_brotli.html > lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 > apt-cache policy apache2 apache2: Installed: 2.4.29-1ubuntu4.6 Candidate: 2.4.29-1ubuntu4.6 Version table: *** 2.4.29-1ubuntu4.6 500 500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages 500 http://apt.dreamcompute.com bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://apt.dreamcompute.com bionic/main amd64 Packages It was expected to have de following files: /usr/lib/apache2/modules/mod_brotli.so /etc/apache2/mods-available/brotli.load /etc/apache2/mods-available/brotli.conf But the files are missing and the package does not depend in libbrotli1 or libbrotli-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1827263/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package ubiquity - 20.04.15 --- ubiquity (20.04.15) focal; urgency=medium [ Dimitri John Ledkov ] * check-kernels: install the right nvidia modules for the OEM kernel. (LP: #1873867) [ Iain Lane ] * language, partman, prepare: Factor out sensible-browser launching and use it (LP: #1874070) -- Dimitri John Ledkov Tue, 21 Apr 2020 16:07:58 +0100 ** Changed in: ubiquity (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
** Changed in: gtk+2.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1
pulseaudio 1:11.1-1ubuntu7.5 with the new dependency was republished in bug #1781428 ** Summary changed: - pulseaudio now depends on libsnapd-glib1 which recommends snapd + pulseaudio now depends on libsnapd-glib1 -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 Status in pulseaudio package in Ubuntu: Won't Fix Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1781428] Re: please enable snap mediation support
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ sudo snap connect test-snapd-pulseaudio:pulseaudio $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connected which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-snapd-audio-record:audio-playback :audio-playback -
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
udev source package last existed in precise. systemd-udevd is now shipped in src:systemd, please file all future udev bugs against systemd as a starting point. ** Package changed: udev (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => Balint Reczey (rbalint) -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+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 1861941] [NEW] bcache by-uuid links disappear after mounting bcache0
You have been subscribed to a public bug: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2. root@ubuntu:~# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-signed-5.4 (Ubuntu) Importance: Medium Assignee: Colin Ian King (colin-king) Status: New ** Affects: systemd (Ubuntu) Importance: High Assignee: Balint Reczey (rbalint) Status: New ** Tags: amd64 apport-bug curtin focal rls-ff-incoming uec-images vmtest -- bcache by-uuid links disappear after mounting bcache0 https://bugs.launchpad.net/bugs/1861941 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package nvidia-graphics-drivers-440 - 440.82+really.440.64-0ubuntu5 --- nvidia-graphics-drivers-440 (440.82+really.440.64-0ubuntu5) focal; urgency=medium * Reverse the order of the versions of nvidia-dkms-440 in the dependency list, so that apt will default to the real package instead of picking an lrm package at "random" which won't necessarily match the target kernel. LP: #1873867. -- Steve Langasek Tue, 21 Apr 2020 08:17:20 -0700 ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1873627] Re: auditd fails after moving /var it a new filesystem and turning /var/run into a symlink to /run
Alright, close the bug, I have built two different machines and tried to reproduce the problem several different ways, but have been unable to do so. Sorry to bother you with this. Trey Schisser Waveland Technologies - https://wavelandrcm.com Director of Security Operations and IT Infrastructure tschis...@wavelandrcm.com *mobile* 512-496-6660 Never send passwords, regulated data, or confidential information via unencrypted email. Please use Signal (https://signal.org) to send short secure messages (512-496-6660) Or PGP to send encrypted messages via email (See attached public key) PGP Public key for tschisser@wavelandrcm.comLongid: F056 40E6 AEE2 EB92 -BEGIN PGP PUBLIC KEY BLOCK-Version: FlowCrypt 7.6.0 Gmail Encryption Comment: Seamlessly send and receive encrypted emailxjMEXmbFHhYJKwYBBAHaRw8BAQdAaaneOd78NEVLKtQROusVcda2zUSTeF2o NCWvClyafb3NKVRyZXkgU2NoaXNzZXIgPHRzY2hpc3NlckB3YXZlbGFuZHJj bS5jb20+wncEEBYKAB8FAl5mxR4GCwkHCAMCBBUICgIDFgIBAhkBAhsDAh4B AAoJEPBWQOau4uuSIcYBAImzI7Dc+63PVDI3OTyL6VoDZOegP1dnC1Jug3wu 1uYBAP4/bZz5Pa1qNgsAuB+HfptfdJvq+EQkbFQv4t7oDwfVAs44BF5mxR4S CisGAQQBl1UBBQEBB0A5TvjO/keeyllJllXC1fvwKNvADE/T+gNXZJ8EzYVC GAMBCAfCYQQYFggACQUCXmbFHgIbDAAKCRDwVkDmruLrkkO7AP9CUat2JSbw nk5fIpKG23eLrZOZ1JGhHQMDYMus/kOXowD/bNVOZ/yoWZ4cWq7gV9/3k3dD 4pxkHA1GaPmQwKr2/gI= =fqR7 -END PGP PUBLIC KEY BLOCK- On Mon, Apr 20, 2020 at 4:40 PM Seth Arnold <1873...@bugs.launchpad.net> wrote: > Running under strace may change the execution environment enough that > it's not reflective of the actual error, but it's still worth a shot -- > can you pastebin the whole auditd strace logs? That openat() line is > actually a success -- the error we're looking for will come from the > audit_set_pid(3) function, which uses netlink, which is an incredibly > complicated protocol. The error may not look like an error in strace > output. > > Is there any chance the kernel has logged whatever the failure was in > dmesg output? > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873627 > > Title: > auditd fails after moving /var it a new filesystem and turning > /var/run into a symlink to /run > > Status in audit package in Ubuntu: > New > > Bug description: > Auditd was working on my system (Ubuntu 18.04LTS, kernel > 4.15.0-1065-aws) until recently. But after splitting off /var into a > new filesystem it fails to launch. > > running '/sbin/auditd -f' as root indicates a problem writing the pid > file (no file exists even when it says one does) Post config load command > output: > Started dispatcher: /sbin/audispd pid: 16927 > type=DAEMON_START msg=audit(1587280022.692:2019): op=start ver=2.8.2 > format=raw kernel=4.15.0-1065-aws auid=878601141 pid=16925 uid=0 ses=24 > subj=unconfined res=success > config_manager init complete > Error setting audit daemon pid (File exists) > type=DAEMON_ABORT msg=audit(1587280022.692:2020): op=set-pid > auid=878601141 pid=16925 uid=0 ses=24 subj=unconfined res=failed > Unable to set audit pid, exiting > The audit daemon is exiting. > Error setting audit daemon pid (Permission denied) > > /var/run is a symlink to /run > /var/run permissions are 777 root:root > /run permissions are 755f root:root > no /run/auditd.pid and subsiquently no /var/run/auditd.pid exists (even > though the error incorrectly reports otherwise. > > /var/log/audit/audit.log output > type=DAEMON_START msg=audit(1587278222.942:5617): op=start ver=2.8.2 > format=raw kernel=4.15.0-1065-aws auid=4294967295 pid=7529 uid=0 > ses=4294967295 subj=unconf > ined res=success > type=DAEMON_ABORT msg=audit(1587278222.943:5618): op=set-pid > auid=4294967295 pid=7529 uid=0 ses=4294967295 subj=unconfined res=failed > > I have been pulling my hair out over this one. So I ran 'strace > /sbin/auditd -f' and found the following line in the output. > "openat(AT_FDCWD, "/var/run/auditd.pid", > O_WRONLY|O_CREAT|O_TRUNC|O_NOFOLLOW, 0644) = 4" > I am grasping at straws, but suspect that the O_NOFOLLOW option is > causing a failure in creating the pid file since /var/run is a symlink. I > could be wrong but I can't find anything else to suspect. > > Since it is best practice to split/var into a separate file system to > prevent filling the root filesystem in case of an unexpected increase > in log collection I suspect this is a bug. So either the system needs > to be able to follow symlinks or an option such as pid_file=[filepath] > needs to be available in /etc/audit/auditd.conf. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1873627/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1873627 Title: auditd fails after moving /var it a new filesystem and turning /var/run into a symlink to
[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
I can also confirm that kernel 5.4.0-26 solved the problem. Retested and all as should be. -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1872917] Re: Laptop does not recognize it's charging
Found out that my laptops charging port is (partially) broken and will be changed by guarantee. The laptop is actually charging but with a extremely low power, that's why it shows such long batery lifetimes. This bug can be closed. Windows reported discharging state, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1872917 Title: Laptop does not recognize it's charging Status in upower package in Ubuntu: Incomplete Bug description: I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few days, the laptop does not recognize that its charging all the time. It's showing the battery icon and a percent number. This must be broken a couple of days or weeks ago, this was working when I installed Ubuntu 19.10. It does not depend from dock or directly connecting the AC adapter. Incredibly long battery life time is shown, see screenshot. (laptop was connected to AC during this) This is a problem because for example firmware upgrades does not work because they require "AC-connected state". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1872917/+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 1871182] Re: [RTL810xE] No ethernet connection
confirm: kernel 5.4.0-26 solved the problem -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1030519] Re: /proc/self/exe is not necessarily correct on overlayfs
While there was some discussion by the kernel community around this on the associated bug, it appears to remain unresolved there. But it looks to me that Robie's assessment still stands that it wouldn't be appropriate to change this in just the logwatch patch alone. Given the age of this bug, I'm going to mark the logwatch task closed as I don't think there's any further action we can take on it at this time. ** Changed in: logwatch (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1030519 Title: /proc/self/exe is not necessarily correct on overlayfs Status in logwatch package in Ubuntu: Invalid Status in perl package in Ubuntu: Confirmed Bug description: Perl should check the value from /proc/self/exe for correctness. I'll open a bug in logwatch also, however there are likely many more applications that make use of this and depend on it's correctness. Bug number 1007089 tracks the overlayfs bug. /etc/cron.daily/00logwatch: sh: 1: /bin/perl: not found sh: 1: /bin/perl: not found system 'cat '/var/log/mail.log' '/var/log/mail.log.1' | /bin/perl /usr/share/logwatch/scripts/shared/expandrepeats ''| /bin/perl /usr/share/logwatch/scripts/shared/applystddate ''>/tmp/logwatch.BMbdlb_J/maillog' failed: 32512 at /usr/sbin/logwatch line 871. run-parts: /etc/cron.daily/00logwatch exited with return code 2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: perl 5.14.2-6ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sun Jul 29 09:06:20 2012 SourcePackage: perl UpgradeStatus: Upgraded to precise on 2012-01-03 (208 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1030519/+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 1874003] Re: cant log into network
Some more info can be found in this bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1873997 -- 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/1874003 Title: cant log into network Status in network-manager package in Ubuntu: Incomplete Bug description: Running Ubuntu Mate 20.04 2020-04-20 ISO live session, sometimes i'm not able to log into detected wireless networks. See screenshot for error message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: MATE Date: Tue Apr 21 05:29:48 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200420) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 c072d14c-3f17-3a1d-9679-9929ecc4d6cb ethernet 0 never yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- ---- enp4s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874003/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1872902] Re: Upgrade to Focal now removes chrony
** Tags removed: rls-ff-incoming -- 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/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Triaged Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
You need the following packages to run the script: sudo apt install libpyside2-py3-5.14 python3-pyside2.qtcore python3-pyside2.qtuitools python3-pyside2.qtwidgets qt5-style-plugins qt5-gtk2-platformtheme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
nvidia-driver-440 also currently has this dependency: nvidia-dkms-440 (= 440.64-0ubuntu3) | nvidia-dkms-440 (= 440.82+really.440.64-0ubuntu4) The first branch is satisfied by the lrm packages and the second branch is satisfied by the real nvidia-dkms-440 package, which means that apt install nvidia will always select some lrm provider but not necessarily the one that matches your kernel. We should reverse this order so that apt picks the "safe" default of the real nvidia-dkms package. This will become obsolete with the next upload of nvidia, since the real and virtual package versions will again line up. ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: Fix Committed ** Also affects: ubiquity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1874107] [NEW] qt theming issue: error 6 in libgdk-x11-2.0.so
Public bug reported: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (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 gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+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 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
# Symple application failing
import sys
from PySide2.QtWidgets import QApplication, QDialog, QLineEdit, QPushButton
class Form(QDialog):
def __init__(self, parent=None):
super(Form, self).__init__(parent)
self.setWindowTitle("My Form")
if __name__ == '__main__':
# Create the Qt Application
app = QApplication(sys.argv)
app.setStyle('gtk2')
# Create and show the form
form = Form()
form.show()
# Run the main Qt loop
sys.exit(app.exec_())
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1874107
Title:
qt theming issue: error 6 in libgdk-x11-2.0.so
Status in gtk+2.0 package in Ubuntu:
New
Bug description:
As for related bug
https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 ,
theming a qt application with the "gtk2" theme causes the app to crash with
segfault:
```
segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in
libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000]
```
Also the following code is available:
```
Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31
c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00
00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12
```
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgtk2.0-0 2.24.32-4ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Apr 21 18:08:47 2020
InstallationDate: Installed on 2020-04-03 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+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 1871182] Re: [RTL810xE] No ethernet connection
This bug was fixed in the package linux - 5.4.0-26.30 --- linux (5.4.0-26.30) focal; urgency=medium * focal/linux: 5.4.0-26.30 -proposed tracker (LP: #1873882) * Packaging resync (LP: #1786013) - update dkms package versions * swap storms kills interactive use (LP: #1861359) - SAUCE: drm/i915: prevent direct writeback from the shrinker * 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. (LP: #1873315) - [Config] lowlatency: turn off RT_GROUP_SCHED * [RTL810xE] No ethernet connection (LP: #1871182) - net: phy: realtek: fix handling of RTL8105e-integrated PHY -- Andrea Righi Mon, 20 Apr 2020 18:33:49 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1776475] Re: Unlocking existing session often requires several attempts.
Thank you for this extra information. This allowed to narrow down the bug you experienced to a simplified, shorter bug scenario. I was suspecting that this may not be the same bug. > It's not necessary to actually log in as the other user. The bug discussed here only happens when the user is already logged in. May I suggest that you open a new bug report with details of a minimal reproducible case? Thank you for your attention. -- 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/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1873658] Re: Deb Files are not associated with an application that manages packages
** Summary changed: - Deb Files are not opened by the installer 20.04 + Deb Files are not associated with an application that manages packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/382677 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: gdebi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: desktop-file-utils (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1857036] Re: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container.
from the redhat bug report seems to be fixed in sudo-1.8.31p1-1.fc30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1857036 Title: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container. Status in sudo package in Ubuntu: Confirmed Bug description: When using `sudo --login --user USERNAME` with Ubuntu Focal currently, it will correctly operate but it will also throw the following error before continuing with the logon process (which completes successfully except for the stated error): sudo: setrlimit(RLIMIT_CORE): Operation not permitted A full run of this was tested in a Focal LXD container after dropping to a root shell to reproduce (arstotzka is the host system, focal-test is the test container): teward@arstotzka:~$ lxc shell focal-test root@focal-test:~# sudo --login --user ubuntu sudo: setrlimit(RLIMIT_CORE): Operation not permitted To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. ubuntu@focal-test:~$ This appears to be similar to this issue identified on RedHat's tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sudo 1.8.29-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 Date: Thu Dec 19 17:16:31 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/90-cloud-init-users: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1857036/+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 1873658] Re: Deb Files are not opened by the installer 20.04
** Also affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: desktop-file-utils (Ubuntu) Status: New => Confirmed ** Changed in: desktop-file-utils (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873658] Re: Deb Files are not opened by the installer 20.04
I did a full install of Ubuntu Desktop and this happens if you choose to download the deb file or just open it with Firefox. ** Changed in: gdebi (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gdebi (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+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 1872715] Re: 5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem
** Description changed: Hello, I am using Ubuntu 19.10 with 5.1 surround speakers. I tried to configure 5.1 surround, but it still doesn't work. I also installed Pulse audio. Here is the info about my soundcard: # aplay -l Lista PLAYBACK de dispozitive placa 0: PCH [HDA Intel PCH], dispozitiv 0: ALC892 Analog [ALC892 Analog] - subdispozitive: 0/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 0/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 3: HDMI 0 [HDMI 0] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 7: HDMI 1 [HDMI 1] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 8: HDMI 2 [HDMI 2] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 9: HDMI 3 [HDMI 3] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 See 'lscpi -v' output attached. - $ speaker-test -c6 -l1 -twav speaker-test 1.1.9 Playback device is default Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 32 to 349525 Period size range from 10 to 116509 Using max buffer size 349524 Periods = 4 was set period_size = 87381 was set buffer_size = 349524 - 0 - Față stânga - 4 - Centru - 1 - Față dreapta - 3 - Spate dreapta - 2 - Spate stânga - 5 - LFE + 0 - Față stânga + 4 - Centru + 1 - Față dreapta + 3 - Spate dreapta + 2 - Spate stânga + 5 - LFE Timp per Perioada = 8,733519 - - I tried the test below and instead of center speaker, right speaker plays two times and the subwoofer do not work at all. + I tried the test below and instead of center speaker, right speaker + plays two times and the subwoofer do not work at all. Please let me know what other details you need. Thank you! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: lucian 1257 F pulseaudio - /dev/snd/controlC0: lucian 1257 F pulseaudio - /dev/snd/pcmC0D0p: lucian 1257 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: lucian 1257 F pulseaudio + /dev/snd/controlC0: lucian 1257 F pulseaudio + /dev/snd/pcmC0D0p: lucian 1257 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 16:46:45 2020 InstallationDate: Installed on 2019-03-30 (380 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ro_RO.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ro_RO.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.30 dmi.board.name: B150 Pro4/3.1 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.:bvrP7.30:bd11/21/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150Pro4/3.1: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. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-17T14:42:34.178435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872715 Title: 5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
The default value was 0 minutes. I set it to one minute and it made no difference. Incidentally, it seems that clicking on the "Switch user" button is enough to trigger the problem. I did this because I couldn't remember whether or not I'd added another user (I hadn't at that point). It's not necessary to actually log in as the other user. -- 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/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Tags added: id-5e8615c94049a02d98879c25 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: New Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: New Status in bluez source package in Focal: Invalid Bug description: bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04
** Tags added: id-5e9dfb71c2946013f97c4b4f ** Tags added: id-5c7fd728c5595650bd233b03 ** Tags added: id-5e907bafbc1a541703b44644 -- 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/1872485 Title: virtualbox-guest-utils fails to install on 20.04 Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Confirmed Status in systemd package in Debian: Fix Released Status in virtualbox package in Debian: New Bug description: Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install virtualbox-guest-utils` below. Steps to reproduce: 1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 test-container) 2. lxc exec test-container bash 3. apt update 4. apt full-upgrade 5. apt-get install virtualbox-guest-utils Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed init : PreDepends: systemd-sysv but it is not going to be installed Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 59 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59 Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 59 as a solution to systemd:amd64 59 Or group remove for systemd:amd64 Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23 Removing libpam-systemd:amd64 rather than change systemd:amd64 Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14 Removing libnss-systemd:amd64 rather than change systemd:amd64 Investigating (3) plymouth:amd64
[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
** Tags added: id-5e5e7f1874c52821423d5bfd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order
** Tags added: id-5e8f290ae612a06a768e6d7b -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1873528 Title: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order Status in openssh package in Ubuntu: Invalid Bug description: I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf' for use in Ubuntu cloud images. I wanted to add a config file and see if I had done things correctly. I assumed that the files were sourced lexographically (based on use of glob() in readconf.h) so that I could document how users could override our tuning. But it appears from 'sshd -T' output and observed behavior that the first file in /etc/sshd_config.d/ to define a parameter wins. I see in 'sshd -ddd' output that they are parsed lexographically but it seems that their settings apply in reverse (or whichever comes first) if that makes sense. I'd like to understand if this is correct behavior and get it documented. Steps to reproduce on focal with openssh-server 1:8.2p1-4: 1. Create the following files in /etc/ssh/sshd_config.d/ with the content shown below: 40-cloudimg-settings.conf: ClientAliveInterval 110 PasswordAuthentication yes PermitRootLogin no 50-cloudimg-settings.conf: ClientAliveInterval 120 PermitRootLogin yes 60-cloudimg-settings.conf: ClientAliveInterval 180 2. Check what sshd thinks the values will be with 'sshd -T|grep -i clientaliveinterval' and 'sshd -T|grep permitrootlogin' clientaliveinterval 110 permitrootlogin no (The tuning I cared about was ClientAliveInterval for my work but PermitRootLogin is easier to demonstrate) 3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing behavior: debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 296 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: done config len = 71 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting ClientAliveInterval 110 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting PasswordAuthentication yes debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting PermitRootLogin no debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: done config len = 46 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting ClientAliveInterval 120 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting PermitRootLogin yes debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: done config len = 25 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25 debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting ClientAliveInterval 180 4. Set a root password and unlock the account. 5. Attempt to ssh as root to the instance with a password. Observation: * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf and 'yes' in 50-foo.conf * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf and 'no' in 50-foo.conf It appears in 'sshd -ddd' output that files are parsed in lexographic order (40-foo.conf before 50-foo.conf) but the behavior observed indicates that the value set in 40-foo.conf overrides 50-foo.conf which is counter to expectations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1776475] Re: Unlocking existing session often requires several attempts.
Hi Jane @irihapeti. Thank you for reporting. The settings "delay locking after screensaver for..." that was in "Power Manager" settings, tab "Security" may correspond to what exists in 20.04 in "Screensaver" settings, tab "Lock Screen", and renamed to "Lock the screen after the screen saver is active for..." Can you report the current value? (presumably zero) And set it to one minute to see if it fixes your problem? Thanks! -- 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/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1874051] Re: Crackling headphone output after waking up from sleep
Do note that audio is flawless right after boot, this only happens if the laptop is placed into suspend and then resumed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874051 Title: Crackling headphone output after waking up from sleep Status in alsa-driver package in Ubuntu: New Bug description: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 21 09:32:28 BrokenHingeLaptop systemd[1165]: pulseaudio.service: Succeeded. Apr 21 09:32:38 BrokenHingeLaptop systemd[1165]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion x360 Convertible 14-ba0xx, Realtek ALC295, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 830F dmi.board.vendor: HP dmi.board.version: 31.25 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd05/03/2019:svnHP:pnHPPavilionx360Convertible14-ba0xx:pvrType1ProductConfigId:rvnHP:rn830F:rvr31.25:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-ba0xx dmi.product.sku: 2GV24PA#UUF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874051/+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 1874051] [NEW] Crackling headphone output after waking up from sleep
Public bug reported: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 21 09:32:28 BrokenHingeLaptop systemd[1165]: pulseaudio.service: Succeeded. Apr 21 09:32:38 BrokenHingeLaptop systemd[1165]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion x360 Convertible 14-ba0xx, Realtek ALC295, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 830F dmi.board.vendor: HP dmi.board.version: 31.25 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd05/03/2019:svnHP:pnHPPavilionx360Convertible14-ba0xx:pvrType1ProductConfigId:rvnHP:rn830F:rvr31.25:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-ba0xx dmi.product.sku: 2GV24PA#UUF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874051 Title: Crackling headphone output after waking up from sleep Status in alsa-driver package in Ubuntu: New Bug description: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no "
[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Oh, and online too, doesn't install any nvidia in target. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
with old pool (missing right modules) 1. offline install "succeeds" but doesn't install any nvidia stuff in target, no errors otherwise. 2. online install "stalls", generates crashreport pop-up (failing to install lowlatency). Possible workarounds: - fix ubuntu-drivers to detect kernel flavour correctly - switch to linux-generic flavour - oem + nvidia is probably still broken regardless -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1870957] Re: Lost all VPN passwords on upgrades and refuses to save them now
Just to be clear: for that journalctl output, I did put the correct passwords in because the VPN connection worked. The only problem is that the network manager failed to save the password for the next time I tried to use it. -- 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/1870957 Title: Lost all VPN passwords on upgrades and refuses to save them now Status in network-manager package in Ubuntu: New Bug description: On upgrade to Ubuntu-MATE 19.10, the network manager lost all my VPN passwords and now silently fails to store them when I select "save for this user", and even if I delete a VPN connection and create it again with that option, I always have to re-enter the password to use the VPN. It did not lose an wi-fi passwords. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870957/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Hans de Goede, Thank you very much for your information. I were able to install OpenSSH server, however I don't know how to do ssh in while it hangs. Thank you in advance for your help. -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1860754/+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 1874041] [NEW] [UE BOOM 2, playback] Playback problem
Public bug reported: some sounds are playing over the device (like sound the box makes when i turn the volume to max) but chrome sound output does not appear on bluetooth box this appeard after i upgraded yesterday from 19.10 -> 20.04 via do- release-upgrade all pkg's are up to date tried to reboot device // bluetooth box, reconnected, changed audio outputs, disconnected everything expect the bluetooth box, nothing helped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erami 12984 F pulseaudio /dev/snd/pcmC0D0p: erami 12984 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 11:51:25 2020 InstallationDate: Installed on 2019-03-22 (395 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: UE BOOM 2 Symptom_Type: Only some of outputs are working Title: [UE BOOM 2, playback] Playback problem UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S2JW00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L5S2JW00:pvrThinkPadT480:rvnLENOVO:rn20L5S2JW00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S2JW00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874041 Title: [UE BOOM 2, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: some sounds are playing over the device (like sound the box makes when i turn the volume to max) but chrome sound output does not appear on bluetooth box this appeard after i upgraded yesterday from 19.10 -> 20.04 via do- release-upgrade all pkg's are up to date tried to reboot device // bluetooth box, reconnected, changed audio outputs, disconnected everything expect the bluetooth box, nothing helped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erami 12984 F pulseaudio /dev/snd/pcmC0D0p: erami 12984 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 11:51:25 2020 InstallationDate: Installed on 2019-03-22 (395 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: UE BOOM 2 Symptom_Type: Only some of outputs are working Title: [UE BOOM 2, playback] Playback problem UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S2JW00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L5S2JW00:pvrThinkPadT480:rvnLENOVO:rn20L5S2JW00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S2JW00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874041/+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 1870957] Re: Lost all VPN passwords on upgrades and refuses to save them now
the log has a /usr/sbin/vpnc: hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED) unsure if that has to do with the issue ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- 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/1870957 Title: Lost all VPN passwords on upgrades and refuses to save them now Status in network-manager package in Ubuntu: New Bug description: On upgrade to Ubuntu-MATE 19.10, the network manager lost all my VPN passwords and now silently fails to store them when I select "save for this user", and even if I delete a VPN connection and create it again with that option, I always have to re-enter the password to use the VPN. It did not lose an wi-fi passwords. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870957/+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 1861081] Re: Dependency error installing pulseaudio-module-bluetooth
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1861081 Title: Dependency error installing pulseaudio-module-bluetooth Status in pulseaudio package in Ubuntu: Fix Released Bug description: running apt install pulseaudio-module-bluetooth i get the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio-module-bluetooth : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) E: Unable to correct problems, you have held broken packages. seems likely related to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622 but with a different package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861081/+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 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856691 Title: libpulse-mainloop-glib0:i386 cannot be installed Status in pulseaudio package in Ubuntu: Fix Released Bug description: libpulse-mainloop-glib0:i386 cannot be installed because it needs libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is installed. I am running Linux Mint 19.2 which is using the Ubuntu bionic packages. user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386 libpulse-mainloop-glib0:i386: Installiert: (keine) Installationskandidat: 1:11.1-1ubuntu7.4 Versionstabelle: 1:11.1-1ubuntu7.4 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages 1:11.1-1ubuntu7 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages user@computer:$ sudo apt policy libpulse0:i386 libpulse0:i386: Installiert: 1:11.1-1ubuntu7.5 Installationskandidat: 1:11.1-1ubuntu7.5 Versionstabelle: *** 1:11.1-1ubuntu7.5 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.4 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages 1:11.1-1ubuntu7 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages user@computer:$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856691/+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 1858164] Re: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1858164 Title: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates Status in pulseaudio package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu you are using: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1860622] Re: Dependency error installing pulseaudio-esound-compat
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Released Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+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 1846443] Re: Strange behavior of GNOME Tweak header when changing button positions (eoan wayland)
** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Importance: Undecided => Low ** Changed in: ubuntu Status: New => Triaged -- 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/1846443 Title: Strange behavior of GNOME Tweak header when changing button positions (eoan wayland) Status in gnome-tweaks package in Ubuntu: Triaged Bug description: 19.10 eoan Wayland sessions If the GNOME Tweak Tools window is not maximized to the full screen, then when you change the buttons from right to left, the title bar starts to behave strangely, as if it does not have enough space to place information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1846443/+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 1781428] Re: please enable snap mediation support
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.5 --- pulseaudio (1:11.1-1ubuntu7.5) bionic; urgency=medium * Update snap policy to make access to audio recording conditional on plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428): - 0700-modules-add-snappy-policy-module.patch: rewrite to query snapd for the client's plugged interfaces. - 0701-enable-snap-policy-module.patch: enable the module in the default configuration. - Build depend on libsnapd-glib-dev. * Remove module-trust-store patch set: - 0409-Trust-store-patch.patch: trimmed down to pulsecore changes. - 0410-Add-thread-to-activate-trust-store-interface.patch: removed. - 0417-increase-timeout-check-apparmor.patch: removed. -- James Henstridge Wed, 05 Nov 2019 17:16:25 +0800 ** Changed in: pulseaudio (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: pulseaudio (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ sudo snap connect test-snapd-pulseaudio:pulseaudio $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
[Touch-packages] [Bug 1868501] Re: software-properties-gtk is blank when run as normal user.
Since I updated the source.list with software-properties-gtk after the migration to eoan, software-properties-gtk refuses to be launched from gnome shell. However, sudo software-properties-gtk works. For information, I also had a non utf8 character in /var/lib/dpkg/status -- 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/1868501 Title: software-properties-gtk is blank when run as normal user. Status in software-properties package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Upgraded install from 19.10 "Software & Updates" windows is blank when initiated from either the terminal or via the "Settings..." button in the "Software Updater". If I run "software-properties-gtk" in the terminal the window is also blank. If I run it with sudo the "Software and Updates" window opens as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 22 21:30:12 2020 InstallationDate: Installed on 2019-12-15 (98 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1868501/+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 1781428] Re: please enable snap mediation support
This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.11 --- pulseaudio (1:8.0-0ubuntu3.11) xenial; urgency=medium * Backport the snap policy module to make access to audio recording conditional on plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428): - 0450-modules-add-snappy-policy-module.patch: rewrite to query snapd for the client's plugged interfaces. - 0451-enable-snap-policy-module.patch: enable the module in the default configuration. - Build depend on libsnapd-glib-dev. * Backport libjson-c dependency removal from Pulse Audio 10. This is required by the snap policy module due to a symbol name clash with libjson-glib. - 0805-remove-libjson-c-dependency.patch: new file. -- James Henstridge Tue, 05 Nov 2019 17:16:22 +0800 -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ sudo snap connect test-snapd-pulseaudio:pulseaudio $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the
[Touch-packages] [Bug 1868501] Re: software-properties-gtk is blank when run as normal user.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1868501 Title: software-properties-gtk is blank when run as normal user. Status in software-properties package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Upgraded install from 19.10 "Software & Updates" windows is blank when initiated from either the terminal or via the "Settings..." button in the "Software Updater". If I run "software-properties-gtk" in the terminal the window is also blank. If I run it with sudo the "Software and Updates" window opens as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 22 21:30:12 2020 InstallationDate: Installed on 2019-12-15 (98 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1868501/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
This bug was fixed in the package json-glib - 1.4.4-2ubuntu0.19.10.1 --- json-glib (1.4.4-2ubuntu0.19.10.1) eoan; urgency=medium * debian/patches/0001-json-gvariant-Stop-string-to-GVariant-conversion-fai.patch: - Fix JSON to GVariant conversion failing sometimes (LP: #1871023) -- Robert Ancell Tue, 07 Apr 2020 09:50:05 +1200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Released Status in json-glib source package in Bionic: Fix Released Status in json-glib source package in Eoan: Fix Released Status in json-glib source package in Focal: Fix Released Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
This bug was fixed in the package json-glib - 1.4.2-3ubuntu0.18.04.1 --- json-glib (1.4.2-3ubuntu0.18.04.1) bionic; urgency=medium * debian/patches/0001-json-gvariant-Stop-string-to-GVariant-conversion-fai.patch: - Fix JSON to GVariant conversion failing sometimes (LP: #1871023) -- Robert Ancell Tue, 07 Apr 2020 09:50:05 +1200 ** Changed in: json-glib (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: json-glib (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Released Status in json-glib source package in Bionic: Fix Released Status in json-glib source package in Eoan: Fix Released Status in json-glib source package in Focal: Fix Released Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+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 1871023] Update Released
The verification of the Stable Release Update for json-glib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Released Status in json-glib source package in Bionic: Fix Released Status in json-glib source package in Eoan: Fix Committed Status in json-glib source package in Focal: Fix Released Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1874003] Re: cant log into network
Thank you for your bug report. Could you add your 'journalctl -b 0' log after getting the issue? Is it specific to some wifis? Could you test under GNOME if you can connect to those? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1874003 Title: cant log into network Status in network-manager package in Ubuntu: Incomplete Bug description: Running Ubuntu Mate 20.04 2020-04-20 ISO live session, sometimes i'm not able to log into detected wireless networks. See screenshot for error message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: MATE Date: Tue Apr 21 05:29:48 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200420) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 c072d14c-3f17-3a1d-9679-9929ecc4d6cb ethernet 0 never yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- ---- enp4s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874003/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1874021 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. ** Changed in: avahi (Ubuntu) Importance: Undecided => Low ** Changed in: avahi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
Could you also add the 'journalctl -b 0' log from a session having the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Incomplete Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1871182] Re: [RTL810xE] No ethernet connection
Test kernel from comment #11 worked! -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** Patch added: "libxau_1.0.8-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1559650/+attachment/5357502/+files/libxau_1.0.8-1ubuntu1.debdiff ** Changed in: libxau (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1559650/+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 1828134] Re: Wifi not working after suspend/resume cycle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1828134 Title: Wifi not working after suspend/resume cycle Status in NetworkManager: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1828134/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** Description changed: + [Impact] + + gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 + + [Test Case] + + None known yet. Just keeping an eye on the above link for regressions. + + [Regression Potential] + + Low. The same fix has been released to newer distros for the past 2 + years already. + + [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: In Progress Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1559650/+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
