[Touch-packages] [Bug 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
the change got merged upstream, can we get it cherry picked to Ubuntu now? -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1968100] Re: Reporting firefox bug redirect to general mozilla page
** Changed in: apport (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1968100 Title: Reporting firefox bug redirect to general mozilla page Status in apport package in Ubuntu: Confirmed Bug description: When reporting a bug on firefox snap. A dialog is shown, that will redirect to https://support.mozilla.org/en-US/products/firefox and not the bug reporting website. If someone tries to file a bug this is pretty inconvenient. Starting a search there on 'report bug' shows as 2nd item. Reporting bugs is hard. The first item is about bugs fixed in a release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 10:55:35 2022 InstallationDate: Installed on 2022-03-17 (21 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-03-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968100/+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 1968100] Re: Reporting firefox bug redirect to general mozilla page
It's a bit unfortunate that apport uses a general contact URL, it would be better if the store had an additional field for a bug reporting URL. I have contacted Mozilla to suggest either changing the contact URL to point to https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox, or update the support page to include a direct link to bugzilla. Let's see what they think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1968100 Title: Reporting firefox bug redirect to general mozilla page Status in apport package in Ubuntu: Confirmed Bug description: When reporting a bug on firefox snap. A dialog is shown, that will redirect to https://support.mozilla.org/en-US/products/firefox and not the bug reporting website. If someone tries to file a bug this is pretty inconvenient. Starting a search there on 'report bug' shows as 2nd item. Reporting bugs is hard. The first item is about bugs fixed in a release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 10:55:35 2022 InstallationDate: Installed on 2022-03-17 (21 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-03-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968100/+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 1961484] Re: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed)
Does someone know any workaround or an ETA for the issue to be solved? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1961484 Title: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed) Status in libva package in Ubuntu: Confirmed Bug description: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva in 20.04.3 to match Mesa. This bug affects any application that is trying to use VAAPI for hardware acceleration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libva2 2.7.0-2 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:15 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (2424 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1961484/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Rule is triggered by all block devices, I switched it off with !="block" but that can only be a temporary 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
running fluxbox still can trigger this in 22.04 Affected scripts in my case: /etc/X11/Xsession.d/30x11-common_xresources /etc/X11/Xsession.d/90x11-common_ssh-agent -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1968305] [NEW] sshd_config.d overrides not working
Public bug reported: Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does not override settings from /etc/ssh/sshd_config >From debugging sshd, I can see the override file is indeed being read, and the option is supposedly set. But after testing, the options are not taking effect. Specifically, in the main sshd_config, I have disabled PasswordAuthentication In my override file, PasswordAuthentication is enabled Yet, when connecting to the server, it only checks public/private keys. This is for an environment where we have our default sshd_config, and in specific use-cases, we might enable PasswordAuthentication for some servers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 8 10:37:42 2022 InstallationDate: Installed on 2021-11-04 (154 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- 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/1968305 Title: sshd_config.d overrides not working Status in openssh package in Ubuntu: New Bug description: Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does not override settings from /etc/ssh/sshd_config From debugging sshd, I can see the override file is indeed being read, and the option is supposedly set. But after testing, the options are not taking effect. Specifically, in the main sshd_config, I have disabled PasswordAuthentication In my override file, PasswordAuthentication is enabled Yet, when connecting to the server, it only checks public/private keys. This is for an environment where we have our default sshd_config, and in specific use-cases, we might enable PasswordAuthentication for some servers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 8 10:37:42 2022 InstallationDate: Installed on 2021-11-04 (154 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+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 1968305] Re: sshd_config.d overrides not working
** Attachment added: "sshd debug output" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+attachment/5578186/+files/sshd_debug -- 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/1968305 Title: sshd_config.d overrides not working Status in openssh package in Ubuntu: New Bug description: Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does not override settings from /etc/ssh/sshd_config From debugging sshd, I can see the override file is indeed being read, and the option is supposedly set. But after testing, the options are not taking effect. Specifically, in the main sshd_config, I have disabled PasswordAuthentication In my override file, PasswordAuthentication is enabled Yet, when connecting to the server, it only checks public/private keys. This is for an environment where we have our default sshd_config, and in specific use-cases, we might enable PasswordAuthentication for some servers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 8 10:37:42 2022 InstallationDate: Installed on 2021-11-04 (154 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+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 1968305] Re: sshd_config.d overrides not working
** Attachment added: "Contents of override file" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+attachment/5578185/+files/sshd_config_override -- 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/1968305 Title: sshd_config.d overrides not working Status in openssh package in Ubuntu: New Bug description: Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does not override settings from /etc/ssh/sshd_config From debugging sshd, I can see the override file is indeed being read, and the option is supposedly set. But after testing, the options are not taking effect. Specifically, in the main sshd_config, I have disabled PasswordAuthentication In my override file, PasswordAuthentication is enabled Yet, when connecting to the server, it only checks public/private keys. This is for an environment where we have our default sshd_config, and in specific use-cases, we might enable PasswordAuthentication for some servers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 8 10:37:42 2022 InstallationDate: Installed on 2021-11-04 (154 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
I wonder whether my problem is this bug 1962036, or something else. Problem while upgrading impish to jammy: screen showing just background (no windows), moving/clicking mouse eliciting the "wait" cursor momentarily. Fixed by hard reset, boot to "recovery" console, and used: dpkg --configure -a apt dist-upgrade shutdown -r now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Fix Released Status in dbus source package in Jammy: Fix Released Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1968313] [NEW] Bash manual contains an error in the "Invocation" section
Public bug reported: This is a minor error in the Bash manual, which I have confirmed with one of the authors (Chet Ramey). The error appears to have been created in Debian, and therefore Ubuntu has inherited it. DETAIL In the Bash manual ("man bash"), in the "Invocation" section, the penultimate paragraph has this phrase: "… it reads and executes commands from ~/.bashrc and ~/.bashrc" The file ~/.bashrc should be stated just once, because it's confusing having it mentioned twice. This needs correcting at the Debian level, so that all Debian-based distributions will inherit the fix. • Ubuntu 20.04.4 LTS, Lubuntu 20.04, Ubuntu 21.10 • apt-cache policy bash: 5.0-6ubuntu1.1 • bash --version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 11:18:38 2022 InstallationDate: Installed on 2020-09-05 (579 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1968313 Title: Bash manual contains an error in the "Invocation" section Status in bash package in Ubuntu: New Bug description: This is a minor error in the Bash manual, which I have confirmed with one of the authors (Chet Ramey). The error appears to have been created in Debian, and therefore Ubuntu has inherited it. DETAIL In the Bash manual ("man bash"), in the "Invocation" section, the penultimate paragraph has this phrase: "… it reads and executes commands from ~/.bashrc and ~/.bashrc" The file ~/.bashrc should be stated just once, because it's confusing having it mentioned twice. This needs correcting at the Debian level, so that all Debian-based distributions will inherit the fix. • Ubuntu 20.04.4 LTS, Lubuntu 20.04, Ubuntu 21.10 • apt-cache policy bash: 5.0-6ubuntu1.1 • bash --version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 11:18:38 2022 InstallationDate: Installed on 2020-09-05 (579 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1968313/+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 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
Was this released ? I've received an update of that package this morning: > $ dpkg --list systemd-oomd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | > État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ NomVersion Architecture Description > +++-==-===-- > ii systemd-oomd 249.11-0ubuntu3 amd64Userspace out-of-memory (OOM) > killer But even with that version which fixes the issue according to: > systemd (249.11-0ubuntu3) jammy; urgency=medium > > * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: > #1966381) > File: > debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch > > https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046 > * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860) > File: > debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch > > https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997 > > -- Nick Rosbrook Thu, 07 Apr 2022 15:28:15 > -0400 I still hit the problem after a few minutes of building a debug firefox on my laptop (ThinkPad P14s, 32GB RAM) > -- Boot c45108609edc41368bc948d9ffda1f4d -- > avril 08 12:30:44 portable-alex systemd[1]: Starting Userspace Out-Of-Memory > (OOM) Killer... > avril 08 12:30:44 portable-alex systemd[1]: Started Userspace Out-Of-Memory > (OOM) Killer. > avril 08 12:42:07 portable-alex systemd-oomd[1168]: Killed > /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-Alacritty-6631.scope > due to memory used (26327048192) / total (29247873024) and swap used > (1023406080) / total (1023406080) being more than 90.00% > -- Boot 2d12cd6e16d4432b94f957fc1cd77124 -- This is what I can see in the logs ; as you can see it's killing my term (alacritty). FTR, all things being equal otherwise, I have been able to run for days with systemd-oomd masked and disabled and the same usage. -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22
[Touch-packages] [Bug 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
And FTR I also have 1GB swap, the install is not from Jammy (rather 21.04 or 21.10) $ LC_ALL=C swapon -s FilenameTypeSizeUsed Priority /dev/dm-2 partition 999420 631852 -2 -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1968338] [NEW] package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit sta
Public bug reported: my computer froze, i rebooted, and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.99.9.8 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 13:07:14 2022 ErrorMessage: new software-properties-common package pre-removal script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968338 Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 Status in software-properties package in Ubuntu: New Bug description: my computer froze, i rebooted, and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.99.9.8 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 13:07:14 2022 ErrorMessage: new software-properties-common package pre-removal script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 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/1968338/+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 1968337] [NEW] package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2
Public bug reported: my computer froze & i rebooted it and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.7 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: python-apt:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 12:38:40 2022 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 2 Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1968337 Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2 Status in python-apt package in Ubuntu: New Bug description: my computer froze & i rebooted it and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.7 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: python-apt:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 12:38:40 2022 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 2 Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1968337/+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 1967127] Re: [FFe] update libarchive to 3.6.0
This bug was fixed in the package evince - 42.1-2 --- evince (42.1-2) unstable; urgency=medium * debian/control.in: Bump minimum libarchive to 3.6.0 * Drop libarchive revert commits (LP: #1967127) -- Jeremy Bicha Wed, 30 Mar 2022 08:17:47 -0400 ** Changed in: evince (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1967127 Title: [FFe] update libarchive to 3.6.0 Status in evince package in Ubuntu: Fix Released Status in libarchive package in Ubuntu: Fix Released Bug description: I request a Feature Freeze Exception to update libarchive from 3.5.2 to 3.6.0 and build evince with libarchive 3.6. This will allow us to drop 2 revert commits we added to evince to build with the older libarchive. https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b Changes --- https://github.com/libarchive/libarchive/releases/tag/v3.6.0 https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0 Other Changes - 1. libarchive: I am cherry-picking a security fix for CVE-2022-26280 2. libarchive: debian/rules was only running dh_auto_test if 'check' was set in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That way we run the build tests by default. I'm forwarding both those changes to Debian soon. Build logs -- https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra https://buildd.debian.org/status/package.php?p=evince Testing done No errors in the install logs Evince still works fine to open a variety of PDFs and a .cbz file I have. File Roller still works fine to open a variety of compressed file types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1967127/+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 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
Hi Pirouette, Can you show the output of `oomctl` and `free -h` on your system? FWIW, at the time of writing this systemd 249.11-0ubuntu3 is still in jammy-proposed, so is only available on systems with the -proposed archive enabled. -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Global Protect VPN is a VPN client (like openvpn) which connects your desktop to a VPN. After you're connected you can acccess some remote PCs via rdp, and I used to use remmina to do that -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1965901] Re: SRU the new 1.18 serie to focal for hwe
** Description changed: [Impact] We want to update to the newer serie for better hardware support + (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] - * install modemmanager, libmbim, and libqmi from -proposed - * reboot and try WWAN function to see if any regression there. - * perform general dogfooding of its reverse dependencies (network- -manager, gnome-control-center etc.) + * install modemmanager, libmbim, and libqmi from -proposed + * reboot and try WWAN function to see if any regression there. + * perform general dogfooding of its reverse dependencies (network- + manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. - - + Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
This is the root issue: https://gitlab.gnome.org/GNOME/glib/-/issues/389 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #389 https://gitlab.gnome.org/GNOME/glib/-/issues/389 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Triaged Status in libcanberra package in Ubuntu: Triaged Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1967752] Re: check gnome-online-accounts/jammy upgrades
** Changed in: gnome-online-accounts (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1967752 Title: check gnome-online-accounts/jammy upgrades Status in gnome-online-accounts package in Ubuntu: Invalid Status in gnome-online-accounts package in Debian: Fix Released Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1967752/+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 1968368] [NEW] System sets my output device to my microphone
Public bug reported: When I plug in my Samson Go Mic microphone, Ubuntu sets my Output Device to "Speakers -- GoMic compact condenser mic," and I can no longer hear any sound. I can manually switch to "Speakers Built-in Audio," and then all is fine. But the setting will not be sticky. After I unplug the microphone, the Output Device will again switch to the microphone. What I expected: When I plug in my microphone, Ubuntu should not change my Output Device, and sound output should continue as usual. And if I do have to change the setting manually, the change should stick. The issue is discussed here: https://ubuntu-mate.community/t/18-04-my-output-device-is-set-to-my-microphone/16613 Using pavucontrol to make the changed setting sticky, as suggested there, seems to work for me. But this is a workaround. Ubuntu 21.10. Pulseaudio: 1:15.0+dfsg1-1ubuntu2.2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jswami 9217 F pulseaudio /dev/snd/controlC0: jswami 9217 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 11:35:16 2022 InstallationDate: Installed on 2017-12-08 (1581 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-10-14 (175 days ago) dmi.bios.date: 11/11/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET68W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCT01WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN1MET68W(1.53):bd11/11/2021:br1.53:efr1.20:svnLENOVO:pn20HRCT01WW:pvrThinkPad:rvnLENOVO:rn20HRCT01WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HR_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20HRCT01WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1968368 Title: System sets my output device to my microphone Status in pulseaudio package in Ubuntu: New Bug description: When I plug in my Samson Go Mic microphone, Ubuntu sets my Output Device to "Speakers -- GoMic compact condenser mic," and I can no longer hear any sound. I can manually switch to "Speakers Built-in Audio," and then all is fine. But the setting will not be sticky. After I unplug the microphone, the Output Device will again switch to the microphone. What I expected: When I plug in my microphone, Ubuntu should not change my Output Device, and sound output should continue as usual. And if I do have to change the setting manually, the change should stick. The issue is discussed here: https://ubuntu-mate.community/t/18-04-my-output-device-is-set-to-my-microphone/16613 Using pavucontrol to make the changed setting sticky, as suggested there, seems to work for me. But this is a workaround. Ubuntu 21.10. Pulseaudio: 1:15.0+dfsg1-1ubuntu2.2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jswami 9217 F pulseaudio /dev/snd/controlC0: jswami 9217 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 11:35:16 2022 InstallationDate: Installed on 2017-12-08 (1581 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-10-14 (175 days ago) dmi.bios.date: 11/11/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET68W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCT01WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20
[Touch-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libcanberra (Ubuntu) Status: Triaged => Fix Committed ** Changed in: libcanberra (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Committed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1968360] Re: jammy daily won't accept EC2 publickey (suspect cloud-init failure)
I've checked all of the following jammy daily images, and all of them fail to correctly install the EC2 metadata supplied SSH key such that it is possible to ssh ubuntu@host after startup. Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220323ami-0320e0e27a2e26467 Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220405ami-028c98d9274336455 Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220406ami-0cb3473d91f8f239d Amazon AWS us-east-1 jammy com.ubuntu.cloud.daily:server:22.04 arm64 hvm-ssd 20220407ami-03c980393156217bb Both of these do install the SSH key for ubuntu@ from AWS metadata fine: Amazon AWS us-east-1 impish 21.10 arm64 hvm-ssd 20220309 ami-0a4b1fdc2301bf1f1 Amazon AWS us-east-1 impish com.ubuntu.cloud.daily:server:21.10 arm64 hvm-ssd 20220319ami-09ce10196abcc5dc4 ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1968360 Title: jammy daily won't accept EC2 publickey (suspect cloud-init failure) Status in cloud-init: Incomplete Status in openssh package in Ubuntu: New Bug description: amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information ==> amazon-ebs: Prevalidating AMI Name: packer-honeycomb-arm-1649438444 amazon-ebs: Found Image ID: ami-03c980393156217bb ==> amazon-ebs: Creating temporary keypair: packer_62506eec-8c01-8c21-b199-32a96021bd7a ==> amazon-ebs: Creating temporary security group for this instance: packer_62506eee-c3da-1eb2-6e81-baa0c5ccfdfc ==> amazon-ebs: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups... ==> amazon-ebs: Launching a source AWS instance... ==> amazon-ebs: Adding tags to source instance amazon-ebs: Adding tag: "Name": "Packer Builder" amazon-ebs: Instance ID: i-01158f222c8664f0c ==> amazon-ebs: Waiting for instance (i-01158f222c8664f0c) to become ready... ==> amazon-ebs: Using SSH communicator to connect: 54.173.181.221 ==> amazon-ebs: Waiting for SSH to become available... ==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> amazon-ebs: Terminating the source AWS instance... ==> amazon-ebs: Cleaning up any extra volumes... ==> amazon-ebs: No volumes to clean up, skipping ==> amazon-ebs: Deleting temporary security group... ==> amazon-ebs: Deleting temporary keypair... Build 'amazon-ebs' errored after 2 minutes 42 seconds: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Wait completed after 2 minutes 42 seconds ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Builds finished but no artifacts were created. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1968360/+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 1660121] Re: LightDM can't use the user background on Mate
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1660121 Title: LightDM can't use the user background on Mate Status in lightdm package in Ubuntu: Confirmed Bug description: Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04 alpha 2). On Mate, the LightDM Gtk Greeter can't use the user background. It works fine on other DEs like Xfce. From what I understand, LightDM and/or the Gkt greeter (not sure which one handles the background) gets the background path from Gsettings, so I assume it can't find the one from Mate, which stores it in "org.mate.background picture-filename". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1660121/+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 1968379] [NEW] software-properties-gtk crashes with DBus.Error.ServiceUnknown
Public bug reported: Ubuntu 20.04.4 LTS software-properties-gtk crashes immediately after start DBus.Error.ServiceUnknown apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.9.8 Candidate: 0.99.9.8 Version table: *** 0.99.9.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages sudo software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.1625:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 222, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1625 was not provided by any .service files problem only in software-properties-gtk, software-properties-qt runs OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.99.9.8 ProcVersionSignature: Ubuntu 5.4.0-107.121-lowlatency 5.4.174 Uname: Linux 5.4.0-107-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 01:02:27 2022 InstallationDate: Installed on 2019-05-18 (1056 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968379 Title: software-properties-gtk crashes with DBus.Error.ServiceUnknown Status in software-properties package in Ubuntu: New Bug description: Ubuntu 20.04.4 LTS software-properties-gtk crashes immediately after start DBus.Error.ServiceUnknown apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.9.8 Candidate: 0.99.9.8 Version table: *** 0.99.9.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages sudo software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.1625:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 222, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.fre
[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
** No longer affects: ubuntu-mate -- 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/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in software-properties package in Ubuntu: Confirmed Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1844426/+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 1888125] Re: refreshing cache stuck in ubuntu mate 20.04
** No longer affects: ubuntu-mate -- 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/1888125 Title: refreshing cache stuck in ubuntu mate 20.04 Status in software-properties package in Ubuntu: Expired Bug description: i have a very annoying bug which is refreshing cache is just not closing only if i rebooted the system! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1888125/+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 1968360] Re: jammy daily won't accept EC2 publickey (suspect cloud-init failure)
https://github.com/hashicorp/packer/issues/11656#issuecomment-1076175764 found my problem. packer generates temporary ssh-rsa keys which are disallowed by the 22.04 default SSH key policy. ** Changed in: openssh (Ubuntu) Status: New => Invalid ** Changed in: cloud-init Status: Incomplete => Invalid ** Bug watch added: github.com/hashicorp/packer/issues #11656 https://github.com/hashicorp/packer/issues/11656 -- 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/1968360 Title: jammy daily won't accept EC2 publickey (suspect cloud-init failure) Status in cloud-init: Invalid Status in openssh package in Ubuntu: Invalid Bug description: amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information ==> amazon-ebs: Prevalidating AMI Name: packer-honeycomb-arm-1649438444 amazon-ebs: Found Image ID: ami-03c980393156217bb ==> amazon-ebs: Creating temporary keypair: packer_62506eec-8c01-8c21-b199-32a96021bd7a ==> amazon-ebs: Creating temporary security group for this instance: packer_62506eee-c3da-1eb2-6e81-baa0c5ccfdfc ==> amazon-ebs: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups... ==> amazon-ebs: Launching a source AWS instance... ==> amazon-ebs: Adding tags to source instance amazon-ebs: Adding tag: "Name": "Packer Builder" amazon-ebs: Instance ID: i-01158f222c8664f0c ==> amazon-ebs: Waiting for instance (i-01158f222c8664f0c) to become ready... ==> amazon-ebs: Using SSH communicator to connect: 54.173.181.221 ==> amazon-ebs: Waiting for SSH to become available... ==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> amazon-ebs: Terminating the source AWS instance... ==> amazon-ebs: Cleaning up any extra volumes... ==> amazon-ebs: No volumes to clean up, skipping ==> amazon-ebs: Deleting temporary security group... ==> amazon-ebs: Deleting temporary keypair... Build 'amazon-ebs' errored after 2 minutes 42 seconds: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Wait completed after 2 minutes 42 seconds ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ==> Builds finished but no artifacts were created. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1968360/+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 1968305] Re: sshd_config.d overrides not working
This reminds me of several previous bugs; this may or may not be a duplicate, and this may or may not be intentional behaviour. Hopefully these are are useful and save some debugging effort: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212 https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320 https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528 Especially 1873528 feels like most likely to be relevant, I suggesting reading that one first. Thanks -- 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/1968305 Title: sshd_config.d overrides not working Status in openssh package in Ubuntu: New Bug description: Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does not override settings from /etc/ssh/sshd_config From debugging sshd, I can see the override file is indeed being read, and the option is supposedly set. But after testing, the options are not taking effect. Specifically, in the main sshd_config, I have disabled PasswordAuthentication In my override file, PasswordAuthentication is enabled Yet, when connecting to the server, it only checks public/private keys. This is for an environment where we have our default sshd_config, and in specific use-cases, we might enable PasswordAuthentication for some servers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 8 10:37:42 2022 InstallationDate: Installed on 2021-11-04 (154 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+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 1898771] Re: suspend does not lock screen Fresh Ubuntu Mate 20.04.1
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1898771 Title: suspend does not lock screen Fresh Ubuntu Mate 20.04.1 Status in lightdm package in Ubuntu: New Bug description: When suspending my freshly installed 20.04.1 system I noticed that on waking a password is not required. lightdm does not have locking enabled on suspend. A workaround I found from pszafer on archlinux blog. Quoted below: create lockscreen.sh file somewhere in your home directory with: #!/bin/sh XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock - I've prefer just for sure creating dmlock.service file in home dir and create symlink to /etc/systemd/system. File has to be in /etc/systemd/system/dmlock.service [Unit] Description=DM Lock before sleep Before=sleep.target [Service] ExecStart=/home/user/dir/lockscreen.sh [Install] WantedBy=sleep.target For your needs, you probably need hibernate.target. Next run following commands: systemctl daemon-reload systemctl enable dmlock.service Just for sure it is working you could run: systemctl list-unit-files systemctl start dmlock.service Hope it helps you a little To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1898771/+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 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in lightdm package in Ubuntu: New Status in lightdm package in Debian: Confirmed Bug description: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+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 1921655] Re: lightdm-guest-session ICEauthority error
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1921655 Title: lightdm-guest-session ICEauthority error Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Focal: Fix Released Status in lightdm source package in Groovy: Fix Released Status in lightdm source package in Hirsute: Fix Released Bug description: [Impact] If you enable the guest session feature on e.g. Ubuntu MATE, you are met by an error message when trying to enter a guest session: "Could not update file ICEauthority file /run/user/XXX/ICEauthority" Even if it's not always a fatal error (the login may succeed after a few minutes), the user experience is really bad, and you are inclined to conclude that you are completely blocked from using the feature. The proposed fix adds a rule to the lightdm-guest-session AppArmor profile and prevents the error from happening. [Test Plan] On an updated Ubuntu MATE installation: * Enable guest session sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n" >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf' * Install lightdm from {focal,groovy}-proposed * Reboot You should now be able to enter a guest session without being stopped by the ICEauthority error. [Where problems could occur] This one-liner is a harmless change. The guest session is run in an unconfined mode since Ubuntu 16.10. That's why the feature is disabled by default. So if the additional rule would be wrong somehow (which I have no reason to believe), it wouldn't break the AppArmor security layer for the simple reason that it's already broken to begin with. [Original description] Hello I ran into trouble to start the lightdm-guest-session in linux mint (cinnamon). ## How to reproduce: - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other distros but I think others are also affected. - enable guest user session - try to login as guest user ## Error logs: ### Error Message: ` Could not update file ICEauthority file /run/user/XXX/ICEauthority` ### aa-notify: ``` Profile: /usr/lib/lightdm/lightdm-guest-session Operation: open Name: /proc/8125/uid_map Denied: w Logfile: /var/log/kern.log Profile: /usr/lib/lightdm/lightdm-guest-session Operation: open Name: /proc/8125/setgroups Denied: w Logfile: /var/log/kern.log Profile: /usr/lib/lightdm/lightdm-guest-session Operation: open Name: /proc/8125/gid_map Denied: w Logfile: /var/log/kern.log Profile: /usr/lib/lightdm/lightdm-guest-session Operation: open Name: /proc/8624/fd/ Denied: r Logfile: /var/log/kern.log ``` ### dmesg: ``` [ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" requested_mask="w" denied_mask="w" fsuid=999 ouid=0 [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" denied_mask="r" fsuid=999 #ouid=0 [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" requested_mask="w" denied_mask="w" fsuid=999 ouid=0 [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" requested_mask="l" denied_mask="l" fsuid=999 ouid=999 target="/run/user/999/ICEauthority-c" ``` ## Solutions: ### bad but common work around Solutions I found in different forums were to move lightdm-guest-session into complain mode like this: `aa-complain /usr/lib/lightdm/lightdm-guest-session` ### maybe better sollution: My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`: ``` ... /usr/lib/lightdm/lightdm-guest-session { ... owner /run/user/[0-9]*/ICEauthority-? l,` ... } ``` I honestly have no clue about apparmor and I'm unsure where to post this but I hope this maybe helps some other people in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1921655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.l
[Touch-packages] [Bug 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1920813 Title: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session requiredpam_loginuid.so" for compatibility with user applications Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.04 2. Launch MATE Terminal 3. Execute `cat /proc/self/loginuid` Expected results: * above command returned 1000 Actual results: * above command returned 4294967295 Remediation: * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment session requiredpam_loginuid.so for compatibility with user applications. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 22 22:41:05 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1920813/+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 1942694] Re: [21.04] Uncooperative WiFi manager on TTY7 for proper end user integration
** No longer affects: ubuntu-mate -- 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/1942694 Title: [21.04] Uncooperative WiFi manager on TTY7 for proper end user integration Status in network-manager package in Ubuntu: New Bug description: Desc.: Using 21.04-latest on a Dell XPS 13" laptop and working on TTY7, the wifi manager becomes uncooperative after, it seems, it gets tied up to 2 wifi profiles. Recreation steps: 1. Install 21.04-latest + full patch it using your home LAN WiFi AP; 2. Login newly installed system + test Internet = it works fine; 3. Take same laptop and go to a hotel(for example): manually create a new profile for the new WiFi network from TTY7, login "hotel" wifi network profile + test Internet = it works fine; 4. Physically move back to where your "home" LAN WiFi profile is and boot system: Problem now happens:: 1. Internet doesn't work off WiFi; 2. Click on the "Wi-Fi Network" icon at the top hand right side of the screen -> "no network devices available"; 3. Select "Edit connections" -> there will be your 2 profiles there: "home" and "hotel", delete "hotel" -> OK; 4. "no network devices available" still shows under "Wi-Fi Network" at the top. MY USER EXPECTATIONS: Get a new list of close by AP and/or automatically reconnect to "profile 1: home". NOTA: Both profiles are set to priority 0 and also all set to "all uses may connect to this network". Could this be the problem? Solution: Reboot system. After reboot. TTY7 will have defaulted back to the "home" WiFi profile and Internet will work at the first user attempt. xo PS: I have been having this problem from way before hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1942694/+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 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
** No longer affects: ubuntu-mate -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22
[Touch-packages] [Bug 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
** No longer affects: ubuntu-mate ** No longer affects: mate-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 1904796] Re: screensaver hijacks audio preferences
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1904796 Title: screensaver hijacks audio preferences Status in pulseaudio package in Ubuntu: New Bug description: Using 20.04.1-latest, on a laptop that is plugged via HDMI to a tv: if/when the audio is set to digital and the computer falls into sleep mode, upon waking up, the session's audio defaults back to analog audio output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904796/+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 1893590] Re: [20.04.1] Uncooperative network center (more irritant than joy)
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1893590 Title: [20.04.1] Uncooperative network center (more irritant than joy) Status in network-manager package in Ubuntu: New Bug description: A network center in GUI. So many reasons to love it. Here's a particularly basic one which surely would make my mom want NOT to use Linux: Network connections -> Wired connection -> IPv4 settings -> Method: from Automatic(DHCP) to Manual + add address/netmask/gateway+dns server+SAVE = OK ip a = specified IP address manually Network connections -> Wired connection -> IPv4 settings -> Method: from Manual to Automatic(DHCP)+SAVE = OK disconnect -> reconnect ip a = same specified IP address manually!! But I was expecting to be leased a DHCP IP?? solution: Network connections -> Wired connection -> IPv4 settings -> delete manually added IP address + SAVE + disconnect + reconnect = ip a = DHCP IP, \o/ Food for thought: Thankfully I didn't have 6 different IP configurations in place... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1893590/+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 1968385] [NEW] [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: Can't hear any sound on my inbuilt speaker (but it works with lubuntu). Currently using xubuntu. Also cannot hear any sound in my headphones when plugged in, although volume control recognizes that headphones have been plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 8 18:54:56 2022 InstallationDate: Installed on 2022-04-06 (2 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1968385 Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Can't hear any sound on my inbuilt speaker (but it works with lubuntu). Currently using xubuntu. Also cannot hear any sound in my headphones when plugged in, although volume control recognizes that headphones have been plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 8 18:54:56 2022 InstallationDate: Installed on 2022-04-06 (2 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968385/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
I am seeing this in 22.04 and an easy way for me to reproduce is on a fresh login, open a terminal and watch the log, open Brave/Chrome, for some reason the first time you open the browser it has a GTK title bar which goes away on closing/reopening the app, now right clicking in the terminal window or opening the hamburger menu and bringing up the menu triggers this message in the logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1769362] Re: with multiple monitors, lightDM does not appear on the display set as primary
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1769362 Title: with multiple monitors, lightDM does not appear on the display set as primary Status in lightdm package in Ubuntu: New Bug description: TV hooked up to a laptop; laptop is marked as Primary Display. With the TV turned off, the laptop went idle into the screensaver. When woken, lightDM is rendered on the (off) TV not the laptop display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1769362/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** No longer affects: ubuntu-mate ** Changed in: mate-session-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: Fix Committed Status in mate-screensaver package in Ubuntu: New Status in mate-session-manager package in Ubuntu: Invalid Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Also affects: mate-screensaver (Ubuntu) Importance: Undecided Status: New ** Also affects: arctica-greeter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in arctica-greeter package in Ubuntu: New Status in gnome-system-tools package in Ubuntu: New Status in lightdm package in Ubuntu: Fix Committed Status in mate-screensaver package in Ubuntu: New Status in mate-session-manager package in Ubuntu: Invalid Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Also affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Invalid ** Changed in: arctica-greeter (Ubuntu) Status: New => Invalid ** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed ** Changed in: gnome-system-tools (Ubuntu) Status: Confirmed => Triaged ** Changed in: mate-screensaver (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-mate-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-mate-meta (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in arctica-greeter package in Ubuntu: Invalid Status in gnome-system-tools package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in mate-screensaver package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Triaged Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
This issue is caused by the Users and Groups utility which is part of `gnome-system-tools`. When changing the password from "Asked on logon" to "Not asked on logon" the user is added to the `nopasswdlogin` group and this is what causes the switch-user screen to not ask for a password. If you select the option to not require a password to login during installation, it is not possible to bypass authentication when switching users. This is because `autologin-user` is set to your username in `/etc/lightdm/lightdm.conf` and that works correctly. `gnome-system-tools` was originally included in Ubuntu MATE because it offers user and time management features. But it can now be removed from the Ubuntu MATE default install because recent versions of MATE Control Center provide user and time management. ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Triaged => In Progress ** Summary changed: - Lock screen can be bypassed when auto-login is enabled. + Lock screen can be bypassed when auto-login is enabled via gnome-system-tools -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools Status in arctica-greeter package in Ubuntu: Invalid Status in gnome-system-tools package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in mate-screensaver package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: In Progress Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools
** Changed in: ubuntu-mate-meta (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools Status in arctica-greeter package in Ubuntu: Invalid Status in gnome-system-tools package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in mate-screensaver package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Fix Committed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04
** No longer affects: ubuntu-mate -- 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/1874689 Title: alsa force-reload needed to fix my sound after upgrade to 20.04 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS "sudo alsa force-reload" is needed to fix my sound. I upgraded yesterday (23rd) before the official announcements of 20.04 LTS. Using "do-release-upgrade -d". I'm not sure yet how often I have to run "sudo alsa force-reload". When I have no sound a reboot is not a guranteed fix although it worked once. Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time I tried. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874689/+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 1837765] Re: mono, crackly audio, device not appearing raspberry pi 2B
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1837765 Title: mono, crackly audio, device not appearing raspberry pi 2B Status in pulseaudio package in Ubuntu: New Bug description: I am using the 3.5 jack to speakers on a raspberry pi 2B As detailed here: https://ubuntu-mate.community/t/audio-output-mono- instead-of-stereo-ubuntu-18-04-1-rpi/18001 Audio output is mono Audio output is delayed and crackly for desktop sounds, as well as sometimes simply silent I note that no sound device shows up in Sound Preferences / Hardware Some workarounds from that thread: Editing /etc/pulse/default.pa such that: load-module module-udev-detect tsched=0 and commenting out: load-module module-suspend-on-idle Results in a device "Built-in Audio Analog mono output" showing up in Sound Preferences/Hardware, audio is mono, but does not crackle/miss and desktop sounds work seemingly as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1837765/+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 1892299] Re: [20.04] Keyboard volume rendered useless because of root's userspace?
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1892299 Title: [20.04] Keyboard volume rendered useless because of root's userspace? Status in pulseaudio package in Ubuntu: New Bug description: This is super minor. Yet it's super juicy: Running 20.04-latest and with the following audio hardware configuration: $ arecord -L default Playback/recording through the PulseAudio sound server surround21 2.1 Surround output to Front and Subwoofer speakers surround40 4.0 Surround output to Front and Rear speakers surround41 4.1 Surround output to Front, Rear and Subwoofer speakers surround50 5.0 Surround output to Front, Center and Rear speakers surround51 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers null Discard all samples (playback) or generate zero samples (capture) samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open Sound System pulse PulseAudio Sound Server upmix Plugin for channel upmix (4,6,8) vdownmix Plugin for channel downmix (stereo) with a simple spacialization usbstream:CARD=HDMI HDA ATI HDMI USB Stream Output sysdefault:CARD=Generic HD-Audio Generic, ALC887-VD Analog Default Audio Device front:CARD=Generic,DEV=0 HD-Audio Generic, ALC887-VD Analog Front speakers dmix:CARD=Generic,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct sample mixing device dmix:CARD=Generic,DEV=2 HD-Audio Generic, ALC887-VD Alt Analog Direct sample mixing device dsnoop:CARD=Generic,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct sample snooping device dsnoop:CARD=Generic,DEV=2 HD-Audio Generic, ALC887-VD Alt Analog Direct sample snooping device hw:CARD=Generic,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct hardware device without any conversions hw:CARD=Generic,DEV=2 HD-Audio Generic, ALC887-VD Alt Analog Direct hardware device without any conversions plughw:CARD=Generic,DEV=0 HD-Audio Generic, ALC887-VD Analog Hardware device with all software conversions plughw:CARD=Generic,DEV=2 HD-Audio Generic, ALC887-VD Alt Analog Hardware device with all software conversions usbstream:CARD=Generic HD-Audio Generic USB Stream Output $ $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 $ I am using card 2 off this last paste. If I open a folder in caja containing videos and I play one of them using regular user and celluloid, volume knob on my keyboard works fine. But if I then open any other video from an "Open as administrator" caja window, it will not play any sound(based on my non-expert status I can only assume that this happens because root space and user space do not share the same default audio settings??) First question/problem/request: just like when applying monitor resolution changes into Control Center and applying them system wide, can you also please make it the same for the audio hardware output? As from a user perspective, it makes no sense at all to segregate the hardware values for sound when jumping in root in Ubuntu. Now my real problem is if/when I close my caja window that is in priviledge mode and I then re-open a video w/ celluloid with my regular user, sounds of course works fine, but my keyboard volume knob isn't responding anymore even though I see the volume on screen going up and down when I scroll it, the sound waves do not actually increase nor decrease. Some full moons ago, I posted something on UM forum which related of something similiar and here it is as a FYI: https://ubuntu- mate.community/t/19-10-problem-with-my-sound/20338/3 Furthermore, and again only as a FYI, I have blacklisted "hdi" and "snd_hda_codec_hdmi" in /etc/modprobe.d/snd-blacklist.conf and have rebooted my system to take effect. Hence maybe when you will try reproducing this you will also need to blacklist those 2 modules to get this volume control on your keyboard not listening... And while you have your hands into the audio code, and as of why I had
[Touch-packages] [Bug 1968391] [NEW] Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Public bug reported: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in
[Touch-packages] [Bug 1968311] [NEW] Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)
You have been subscribed to a public bug: I tried installing multiple times, with the Beta version and daily 2022-04-05. I was afraid it was driver related so I tried with and without installing 3rd party software. After unlocking the drive, I can watch what services are starting - it freezes right after "Started Thunderbolt system service." After a while it says "[drm] CPU pipe a FIFO underrun." It always freezes at the same point and never boots. Jammy Jellyfish installed on EXT4 booted just fine on the Dell XPS 13. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13) https://bugs.launchpad.net/bugs/1968311 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968311] Re: Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)
Tagged xorg based on suggestion in wiki. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1968311 Title: Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13) Status in xorg package in Ubuntu: New Bug description: I tried installing multiple times, with the Beta version and daily 2022-04-05. I was afraid it was driver related so I tried with and without installing 3rd party software. After unlocking the drive, I can watch what services are starting - it freezes right after "Started Thunderbolt system service." After a while it says "[drm] CPU pipe a FIFO underrun." It always freezes at the same point and never boots. Jammy Jellyfish installed on EXT4 booted just fine on the Dell XPS 13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968311/+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 1968393] [NEW] Realvnc server won't start in wayland but works uin xorg
You have been subscribed to a public bug: Running the 22.04 beta realvnc server will start under corg but not under wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 19:48:19 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP102 [GeForce GTX 1080 Ti] [1462:3609] InstallationDate: Installed on 2022-04-02 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Micro-Star International Co., Ltd. MS-7A91 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e37b438-e5ea-4ed9-949a-92ceb6597c3e ro delayacct SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2021 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.F1 dmi.board.asset.tag: Default string dmi.board.name: X299 XPOWER GAMING AC (MS-7A91) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.F1:bd01/20/2021:br5.15:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299XPOWERGAMINGAC(MS-7A91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7A91 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze jammy ubuntu wayland-session -- Realvnc server won't start in wayland but works uin xorg https://bugs.launchpad.net/bugs/1968393 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968393] Re: Realvnc server won't start in wayland but works uin xorg
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1968393 Title: Realvnc server won't start in wayland but works uin xorg Status in xorg package in Ubuntu: New Bug description: Running the 22.04 beta realvnc server will start under corg but not under wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 19:48:19 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP102 [GeForce GTX 1080 Ti] [1462:3609] InstallationDate: Installed on 2022-04-02 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Micro-Star International Co., Ltd. MS-7A91 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e37b438-e5ea-4ed9-949a-92ceb6597c3e ro delayacct SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2021 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.F1 dmi.board.asset.tag: Default string dmi.board.name: X299 XPOWER GAMING AC (MS-7A91) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.F1:bd01/20/2021:br5.15:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299XPOWERGAMINGAC(MS-7A91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7A91 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968393/+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 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in linux package in Ubuntu: Expired Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1): supplicant
[Touch-packages] [Bug 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1874689 Title: alsa force-reload needed to fix my sound after upgrade to 20.04 Status in alsa-driver package in Ubuntu: Expired Bug description: After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS "sudo alsa force-reload" is needed to fix my sound. I upgraded yesterday (23rd) before the official announcements of 20.04 LTS. Using "do-release-upgrade -d". I'm not sure yet how often I have to run "sudo alsa force-reload". When I have no sound a reboot is not a guranteed fix although it worked once. Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time I tried. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874689/+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 1968399] [NEW] Display Server Crashes
Public bug reported: If I switch from one computer to another using my hardware KVM, when I switch back the display server has crashed and the Ubuntu boot screen is showing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..11.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 00:49:23 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104GL [RTX A4000] [10de:14ad] InstallationDate: Installed on 2022-04-07 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F62d dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF62d:bd10/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X470 MB dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1968399 Title: Display Server Crashes Status in xorg package in Ubuntu: New Bug description: If I switch from one computer to another using my hardware KVM, when I switch back the display server has crashed and the Ubuntu boot screen is showing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..11.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunnin