[Touch-packages] [Bug 1905106] [NEW] wifi cannot find any network
Public bug reported: I tried to use this command to try to solve the problem, but it didn't work: sudo service network manager and tried to update the system and restart the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 21:07:52 2020 InstallationDate: Installed on 2020-11-18 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.42.129 dev usb0 proto dhcp metric 100 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.163 metric 100 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-11-20 21-06-37.png" https://bugs.launchpad.net/bugs/1905106/+attachment/5436519/+files/Screenshot%20from%202020-11-20%2021-06-37.png -- 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/1905106 Title: wifi cannot find any network Status in network-manager package in Ubuntu: New Bug description: I tried to use this command to try to solve the problem, but it didn't work: sudo service network manager and tried to update the system and restart the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 21:07:52 2020 InstallationDate: Installed on 2020-11-18 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.42.129 dev usb0 proto dhcp metric 100 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.163 metric 100 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1905106/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Though I do understand it is a bit annoying that smartcard login on bionic doesn't work, it worries me that fixing this would involve a lot of backporting. This isn't a regression and bionic has been like this from day 0, right? Do we have an understanding on how wanted this is on bionic? I'm not saying no, but right now I wouldn't be comfortable in such a big set of changes without a rationale. I would rather recommend them to switch to focal and fixing it there. But I'd have to know more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
A warning dialog added in upstream git: https://github.com/ibus/ibus/commit/5322c447 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+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 1905088] Re: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1905088 Title: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: Unpacking openssh-server (1:7.6p1-4ubuntu0.3) ... Setting up openssh-server (1:7.6p1-4ubuntu0.3) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2020-11-20 22:09:42 CET; 20ms ago Process: 2918 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ... Rules updated for profile 'OpenSSH' Firewall reloaded Processing triggers for ureadahead (0.100.0-21) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.43) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Fri Nov 20 22:00:10 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-27 (694 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 13: Bad configuration option: Include /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-06-16 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1905088/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
I had a talk with the upstream on #pulseaudio IRC channel and the issue has not been resolved upstream yet. The guys expect the fix before the PA 14 release. ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1032 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1032 -- 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: New Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
Upstream report: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1032 -- 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: New Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905088] [NEW] package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu
Public bug reported: Unpacking openssh-server (1:7.6p1-4ubuntu0.3) ... Setting up openssh-server (1:7.6p1-4ubuntu0.3) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2020-11-20 22:09:42 CET; 20ms ago Process: 2918 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ... Rules updated for profile 'OpenSSH' Firewall reloaded Processing triggers for ureadahead (0.100.0-21) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.43) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Fri Nov 20 22:00:10 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-27 (694 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 13: Bad configuration option: Include /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-06-16 (157 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1905088 Title: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: Unpacking openssh-server (1:7.6p1-4ubuntu0.3) ... Setting up openssh-server (1:7.6p1-4ubuntu0.3) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2020-11-20 22:09:42 CET; 20ms ago Process: 2918 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ... Rules updated for profile 'OpenSSH' Firewall reloaded Processing triggers for ureadahead (0.100.0-21) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.43) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Fri Nov 20 22:00:10 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-27 (694 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
[Touch-packages] [Bug 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04
It seems the fix went to 13.99.2 and the Ubuntu 20.04 version is 13.99.1. -- 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/1905078 Title: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is gone. The duplex profile was there and was working properly before. The following seems to be related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905078/+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 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04
I just received some tip on the #pulseaudio IRC channel ... The above bug has been fixed with the following merge requesrt: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/349 Could you please patch/upgrade the package? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905078 Title: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is gone. The duplex profile was there and was working properly before. The following seems to be related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905078/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
I just studied the PulseAudio 13 release notes and it is probably related to the following "improvement" ... ::Automatically switch away from unavailable card profiles:: How about restoring the profile when it becomes available again? -- 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: New Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905082] [NEW] [X550CL, Realtek ALC270, Mic, Internal] Recording problem
Public bug reported: After updating to 20.04.1 from 20.04 my internal mic and webcam stoped working. internal mic only records noise. I don't have this problem in windows and FreeBSD ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ermia 8068 F pulseaudio /dev/snd/pcmC0D0p: ermia 8068 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 23:21:03 2020 InstallationDate: Installed on 2020-11-11 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [X550CL, Realtek ALC270, Mic, Internal] Recording problem UpgradeStatus: Upgraded to groovy on 2020-11-19 (1 days ago) dmi.bios.date: 08/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CL.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CL 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.:bvrX550CL.201:bd08/02/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX550CL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CL dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-12T01:47:46.509990 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1905082 Title: [X550CL, Realtek ALC270, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: After updating to 20.04.1 from 20.04 my internal mic and webcam stoped working. internal mic only records noise. I don't have this problem in windows and FreeBSD ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ermia 8068 F pulseaudio /dev/snd/pcmC0D0p: ermia 8068 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 23:21:03 2020 InstallationDate: Installed on 2020-11-11 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [X550CL, Realtek ALC270, Mic, Internal] Recording problem UpgradeStatus: Upgraded to groovy on 2020-11-19 (1 days ago) dmi.bios.date: 08/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CL.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CL 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.:bvrX550CL.201:bd08/02/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX550CL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CL dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-12T01:47:46.509990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905082/+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 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905078 Title: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is gone. The duplex profile was there and was working properly before. The following seems to be related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905078/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: New Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905080] [NEW] After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
Public bug reported: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. ** 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in systemd package in Ubuntu: New Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905080/+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 1905078] [NEW] pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04
Public bug reported: I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is gone. The duplex profile was there and was working properly before. The following seems to be related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750 ** 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/1905078 Title: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04 Status in systemd package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is gone. The duplex profile was there and was working properly before. The following seems to be related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905078/+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 1905076] [NEW] module-alsa-sink's "control" argument causes segmentation fault
Public bug reported: Loading the pulseaudio module 'module-alsa-sink' with the "control" argument causes pulseaudio to segfault on my system. In /etc/pulse/default.pa find this line: #load-module module-alsa-sink and change it to this: load-module module-alsa-sink control=Master then restart pulseaudio by running these commands: pulseaudio -k pulseaudio --start Notice that it prints this into the terminal. E: [pulseaudio] main.c: Daemon startup failed. Try starting pulseaudio itself in the terminal, and you see what's happening: W: [pulseaudio] pid.c: Stale PID file, overwriting. Segmentation fault (core dumped) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1905076 Title: module-alsa-sink's "control" argument causes segmentation fault Status in pulseaudio package in Ubuntu: New Bug description: Loading the pulseaudio module 'module-alsa-sink' with the "control" argument causes pulseaudio to segfault on my system. In /etc/pulse/default.pa find this line: #load-module module-alsa-sink and change it to this: load-module module-alsa-sink control=Master then restart pulseaudio by running these commands: pulseaudio -k pulseaudio --start Notice that it prints this into the terminal. E: [pulseaudio] main.c: Daemon startup failed. Try starting pulseaudio itself in the terminal, and you see what's happening: W: [pulseaudio] pid.c: Stale PID file, overwriting. Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
(I have ping sil2100 internally for him to provide his 2 cents on this bug.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Lukasz (sil2100) can we have your SRU team input on this bug with regard to Bionic/18.04lTS ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz + + The failing testcases are: + + - root-unittests + + Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct + ion test_capability_set_one(). Aborting. + FAIL: test-cap-list (code: 134) + + - upstream + + TEST-24-UNIT-TESTS: + + --- test-cap-list begin --- + Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct + ion test_capability_set_one(). Aborting. + --- test-cap-list end --- + + Both seem to be failing with the same assertion. + + These tests are successful on Focal with linux 5.4, therefore they would + regress when upgrading the kernel from 5.4 to 5.8. -- 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/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1905044] [NEW] systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 5.8.0-30.32~20.04.1 + systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
While Bionic could be maybe supported, that would likely require newer SSSD. Maybe in such case a pam_pkcs11 based solution could be provided, but it's quite a lot of backporting work which would need SRU team to agree with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1890332] Re: apt update fails on docker arm container 20.04
So now I manually downloaded libseccomp2_2.5.0-3_armhf.deb, copied it into the container and tried to install it from there. This didn't work either: Step 7/27 : RUN dpkg --force-all -P libseccomp2 ---> Running in bf8c3eba1b94 dpkg: libseccomp2:armhf: dependency problems, but removing anyway as you requested: apt depends on libseccomp2 (>= 2.4.2). (Reading database ... 4115 files and directories currently installed.) Removing libseccomp2:armhf (2.4.3-1ubuntu3.20.04.3) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Removing intermediate container bf8c3eba1b94 ---> 46d72c3e2384 Step 8/27 : RUN dpkg -i /libseccomp2_2.5.0-3_armhf.deb ---> Running in 2636514aa37f tar: ./control: Cannot utime: Operation not permitted tar: ./md5sums: Cannot utime: Operation not permitted tar: ./shlibs: Cannot utime: Operation not permitted tar: ./symbols: Cannot utime: Operation not permitted tar: ./triggers: Cannot utime: Operation not permitted tar: .: Cannot utime: Operation not permitted tar: Exiting with failure status due to previous errors dpkg-deb: error: tar subprocess returned error exit status 2 dpkg: error processing archive /libseccomp2_2.5.0-3_armhf.deb (--install): dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing: /libseccomp2_2.5.0-3_armhf.deb The command '/bin/sh -c dpkg -i /libseccomp2_2.5.0-3_armhf.deb' returned a non-zero code: 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 Status in libseccomp package in Ubuntu: Confirmed Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+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 1890332] Re: apt update fails on docker arm container 20.04
I have also tried this on ubuntu:20.10, ubuntu:20.04 and ubuntu:18.04 and it produces the same error there, too. I think it is an issue with the system clock reporting Jan 1st 1970. The system clock on the host system is correct though. I could only find two ways to change the system clock in the ubuntu docker image: "date -s" requires --privileged (which isn't available in docker build) hwclock, which doesn't work on raspberry pi: root@8f7355a71bca:/# hwclock --verbose hwclock from util-linux 2.34 System Time: 0.-1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. other means like ntp don't work because they aren't preinstalled and cannot be installed because apt-get doesn't work (which is the topic of this bugreport) I was also not able to update libseccomp2, because wget and curl aren't preinstalled and cannot be installed either, because apt-get doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 Status in libseccomp package in Ubuntu: Confirmed Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+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 1903966] Re: Loading keymaps via udev is not reliable, please use upstream rule
** Bug watch added: Debian Bug tracker #974567 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974567 ** Also affects: v4l-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974567 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1903966 Title: Loading keymaps via udev is not reliable, please use upstream rule Status in v4l-utils package in Ubuntu: Confirmed Status in v4l-utils package in Debian: Unknown Bug description: Dear Maintainer, the udev rule installed from debian/ir-keytable.udev is not guaranteed to be run at the appropriate moment during bootup which can cause the remote not to be configured according to the settings in /etc/rc_maps.cfg. This seems to occur more often with newer kernel versions. Please use the upstream version (https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/70-infrared.rules) instead. This commit message explains the need for this change: https://git.linuxtv.org/v4l-utils.git/commit/utils/keytable/70-infrared.rules?id=e440918467868a5f3e7f73f54ef2cbd85d68f3f1 Description:Ubuntu 20.04.1 LTS Release:20.04 ir-keytable version: 1.18.0-2build1 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1903966/+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 1903966] Re: Loading keymaps via udev is not reliable, please use upstream rule
** Changed in: v4l-utils (Ubuntu) Assignee: (unassigned) => Gregor Jasny (gjasny) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1903966 Title: Loading keymaps via udev is not reliable, please use upstream rule Status in v4l-utils package in Ubuntu: Confirmed Bug description: Dear Maintainer, the udev rule installed from debian/ir-keytable.udev is not guaranteed to be run at the appropriate moment during bootup which can cause the remote not to be configured according to the settings in /etc/rc_maps.cfg. This seems to occur more often with newer kernel versions. Please use the upstream version (https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/70-infrared.rules) instead. This commit message explains the need for this change: https://git.linuxtv.org/v4l-utils.git/commit/utils/keytable/70-infrared.rules?id=e440918467868a5f3e7f73f54ef2cbd85d68f3f1 Description:Ubuntu 20.04.1 LTS Release:20.04 ir-keytable version: 1.18.0-2build1 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1903966/+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 1905027] [NEW] Need to force alsa to reload after reboot to have sound
Public bug reported: Hello, I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version. I need to reload at each reboot alsa with: sudo alsa force-reload The workaround proposed here work for me. https://askubuntu.com/a/1281216/772996 alsa seems to kill timidity (?) This solves it: systemctl disable timidity I didn't find an issue for this bug. Feel free to remove if needed. Thanks ! apt-cache policy alsa gives me empty: alsa: Installé : (aucun) Candidat : (aucun) Table de version : ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1905027 Title: Need to force alsa to reload after reboot to have sound Status in alsa-lib package in Ubuntu: New Bug description: Hello, I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version. I need to reload at each reboot alsa with: sudo alsa force-reload The workaround proposed here work for me. https://askubuntu.com/a/1281216/772996 alsa seems to kill timidity (?) This solves it: systemctl disable timidity I didn't find an issue for this bug. Feel free to remove if needed. Thanks ! apt-cache policy alsa gives me empty: alsa: Installé : (aucun) Candidat : (aucun) Table de version : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1905027/+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 1904695] Re: systemctl doesn't work when running from `docker run $image chroot` command (Bionic)
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1904695 Title: systemctl doesn't work when running from `docker run $image chroot` command (Bionic) Status in systemd package in Ubuntu: Invalid Bug description: 1) Tested on fresh installed system using http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04-server-amd64.iso image. The release of Ubuntu via 'lsb_release -rd' Description: Ubuntu 18.04.4 LTS Release: 18.04 2) The version of the systemd package via 'apt-cache policy systemd' systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.42 Version table: 237-3ubuntu10.42 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 237-3ubuntu10.33 100 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Steps to reproduce the problem $ sudo su $ apt update $ apt install docker.io $ docker pull ubuntu:latest $ docker run -it -v /:/host_root:ro ubuntu:latest chroot /host_root/ systemctl -a 4) What you expected to happen: a list of all systemd units is expected to be displayed, e.g. UNITLOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Auto dev-cdrom.deviceloaded active plugged VBOX_CD-ROM dev-disk-by\x2did-ata\x2dVBOX_CD\x2dROM_VB2\x2d01700376.device loaded active plugged VBOX_CD-ROM [cut out] 5) What happened instead: get the following error message Failed to connect to bus: No data available 6) The same steps tested on fresh installed Ubuntu Xenial OS using http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.6-server-amd64.iso image. And in this environment the `systemctl -a` command works well. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.29 Version table: 229-4ubuntu21.29 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 229-4ubuntu21.27 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages *** 229-4ubuntu21.16 100 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 7) Additional notes: I tried to add `--privileged` options to `docker run` command but it didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904695/+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 1888889] Re: Ubuntu software center is not opening after a fresh Ubuntu install resuing /home from an earlier install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/189 Title: Ubuntu software center is not opening after a fresh Ubuntu install resuing /home from an earlier install Status in systemd package in Ubuntu: Confirmed Bug description: I tried renaming ~/.local/share/gnome-software-center but no luck Any other help is appreciated ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-systemd:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 24 23:26:04 2020 ErrorMessage: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-07-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.1 SourcePackage: systemd Title: package libpam-systemd:amd64 245.4-4ubuntu3.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/189/+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 1904695] Re: systemctl doesn't work when running from `docker run $image chroot` command (Bionic)
I found a solution that works for me: it is needed to add option `--pid host` option to `docker run` command. -- 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/1904695 Title: systemctl doesn't work when running from `docker run $image chroot` command (Bionic) Status in systemd package in Ubuntu: New Bug description: 1) Tested on fresh installed system using http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04-server-amd64.iso image. The release of Ubuntu via 'lsb_release -rd' Description: Ubuntu 18.04.4 LTS Release: 18.04 2) The version of the systemd package via 'apt-cache policy systemd' systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.42 Version table: 237-3ubuntu10.42 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 237-3ubuntu10.33 100 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Steps to reproduce the problem $ sudo su $ apt update $ apt install docker.io $ docker pull ubuntu:latest $ docker run -it -v /:/host_root:ro ubuntu:latest chroot /host_root/ systemctl -a 4) What you expected to happen: a list of all systemd units is expected to be displayed, e.g. UNITLOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Auto dev-cdrom.deviceloaded active plugged VBOX_CD-ROM dev-disk-by\x2did-ata\x2dVBOX_CD\x2dROM_VB2\x2d01700376.device loaded active plugged VBOX_CD-ROM [cut out] 5) What happened instead: get the following error message Failed to connect to bus: No data available 6) The same steps tested on fresh installed Ubuntu Xenial OS using http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.6-server-amd64.iso image. And in this environment the `systemctl -a` command works well. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.29 Version table: 229-4ubuntu21.29 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 229-4ubuntu21.27 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages *** 229-4ubuntu21.16 100 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 7) Additional notes: I tried to add `--privileged` options to `docker run` command but it didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904695/+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 1904700] Re: Mouse settings not reapplied after reconnect or resume
Indeed, I forgot to point that out: the settings in the configuration panel stay correct: to switch back to 'Right' as the primary button, I have to first select 'Left', so I can then select 'Right' again. I could probably fix it by hooking some xinput commands into the proper udev event, but since it seems to be a regression, I was hoping someone knowledgeable might realize the underlying issue, and come up with a better fix :) -- 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/1904700 Title: Mouse settings not reapplied after reconnect or resume Status in systemd package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001LMH dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904700/+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 1904811] Re: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1904811 Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 19:09:53 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-11 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 35: missing argument. SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1904811/+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 1904811] Re: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Hi, from your log SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 35: missing argument. That means you (or a program) have modified /etc/ssh/sshd_config and due to that the update (which needs to restart the server) fails. You can restore the file to its default [1] or fixup that issue in the config file manually. Then things should work again. If you are convinced this indeed is a bug in the package we'd need to see that config file what exactly is at that line 35. -- 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/1904811 Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 19:09:53 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-11 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 35: missing argument. SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1904811/+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 1008213] Re: Missing depends on whoopsie.
It's annoying to see this bug still around 3 years later, in Ubuntu 20.04,network-manager 1.22.10-1ubuntu1 -- 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/1008213 Title: Missing depends on whoopsie. Status in network-manager package in Ubuntu: Confirmed Bug description: By depends I mean one of Suggests/Recommends/Depends. Currently, with no other changes, I'd say you need Depends. Thus I think you should change part of your package to accommodate for systems that don't have whoopsie installed. /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf:91: This leads to... arcadia:~# cat /var/log/upstart/dbus.log Unknown username "whoopsie" in message bus configuration file It's not an error and it doesn't break anything, but it should be easy for you to change things a little. One option is to create this user, though I'd coordinate that with the whoopsie developer. A perhaps better solution is to split this configuration out so that is will only be included if/when whoopsie is installed or the whoopsie user is available. Thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 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 CRDA: Error: [Errno 2] No such file or directory Date: Sun Jun 3 15:05:40 2012 IpRoute: default via 192.168.172.100 dev eth2 metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.172.0/24 dev eth2 proto kernel scope link src 192.168.172.26 IwConfig: Error: [Errno 2] No such file or directory NetDevice.eth2: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=f4:6d:04:2c:0a:e1 NetDevice.lo: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=00:00:00:00:00:00 NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=false RfKill: Error: [Errno 2] No such file or directory SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-01-03 (152 days ago) WpaSupplicantLog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto eth8 759a3094-00a2-4699-bcb0-99d4662887a6 802-3-ethernet0never no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth2 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0asleep disabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1008213/+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 1904700] Re: Mouse settings not reapplied after reconnect or resume
Same issue here, except I noticed the problem because my mouse speed was getting reset after every reboot and most times I resumed from sleep. The speed displayed on the slider is correct so I usually just have to wiggle the slider to get it to actually apply the correct speed, but the same thing happens if I set the primary button to right instead of left. -- 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/1904700 Title: Mouse settings not reapplied after reconnect or resume Status in systemd package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001LMH dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904700/+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 1904700] Re: Mouse settings not reapplied after reconnect or resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1904700 Title: Mouse settings not reapplied after reconnect or resume Status in systemd package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 20.04 and notice that my mouse settings (I mouse lefthanded) are no longer restored/reapplied when I reconnect its usb receiver (gets disconnected due to use of KVM switch) or when resuming (after suspend). I now have to reselect the right button as my primary every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules Date: Wed Nov 18 09:12:11 2020 InstallationDate: Installed on 2016-07-01 (1600 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20L7001LMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001LMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001LMH dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904700/+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 1899780] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1858168 *** https://bugs.launchpad.net/bugs/1858168 ** This bug has been marked a duplicate of bug 1858168 Ubuntu 19.10 after updating the "Other Software" tab in "Software & Updates" the "cache refresh" hangs -- 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/1899780 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: New Bug description: :~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 :~$ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.98.9.2 Candidate: 0.98.9.2 Table version: *** 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Oct 14 14:49:36 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899780/+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 1904602] Re: Strange crash of Software Properties
*** This bug is a duplicate of bug 1858168 *** https://bugs.launchpad.net/bugs/1858168 ** This bug has been marked a duplicate of bug 1858168 Ubuntu 19.10 after updating the "Other Software" tab in "Software & Updates" the "cache refresh" hangs -- 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/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: Incomplete Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair Package: software-properties-gtk 0.99.3 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1904775] Re: software-properties-gtk hangs indefinitely if a single source server is down
How does it prevent users to install security updates? Those are automatically downloaded and applied in background by unattendeed- upgrade. Also software-properties is used to configure sources, not to apply updates, is your issue also impacting update manager? -- 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/1904775 Title: software-properties-gtk hangs indefinitely if a single source server is down Status in software-properties package in Ubuntu: New Bug description: Since this prevents non-technical users from installing critical security updates and does not give them any useful information, I consider it a security issue. A single repository server is down and a bug in software-properties- gtk will prevent non-technical users to continue installing security updates. Example: The Darktable repository is currently offline: https://software.opensuse.org/download.html?project=graphics:darktable:stable=darktable Running sudo apt update clearly shows that one repository is offline. When I open Software Sources app (software-properties-gtk) and it starts to “Refresh Software Cache”, I expect the following: - software sources are being refreshed. - this might take a little longer than normal. - it throws an error and returns to the main screen. - the user can continue normally. In short: it should cope with a server being down. The actual behaviour: - refreshing takes forever. - Ubuntu throws an error saying it hit an error, asking to send the report about software-properties. - I have to manually force close the loading screen. - I can close the main window of software-properties. - when I launch "Software Sources" again, I get an empty square window. This should not happen when a server happens to be down. Running sudo apt update clearly shows that one repository is offline. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Nov 18 19:59:49 2020 InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904775/+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 1904939] Re: Monitor Settings Don't Get Applied in Wayland
Thank you for your bug report, could you add the 'journalctl -b 0' log after getting the issue? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904939 Title: Monitor Settings Don't Get Applied in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: When configuring a 1080p monitor and a 4k monitor in extended screen mode while using Wayland, when trying to change the screen positions or which screen is the primary screen in the Monitor Settings, the settings reset to default when Apply is clicked. Choosing to "Revert the Settings" during the 15-second timer causes it to apply the changed settings, but this resets whenever a pop-up message appears or when returning to the Monitor Settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 16:47:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904939/+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
