[Desktop-packages] [Bug 2058881] [NEW] [snap] Allow chromium snap to access Pressure Stall Information (PSI)
Public bug reported: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: New Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2050040 Title: Ubuntu 22.04.3 LTS top bar sound icon flickers Status in gnome-shell package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker to the right about 2 squares to the right, they keep doing that like something is download or something is going on. This is just a new install fresh download from Ubuntu website and install on SSD drive from USB iso. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-01-21 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: jammy Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2050040 Title: Ubuntu 22.04.3 LTS top bar sound icon flickers Status in gnome-shell package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker to the right about 2 squares to the right, they keep doing that like something is download or something is going on. This is just a new install fresh download from Ubuntu website and install on SSD drive from USB iso. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-01-21 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: jammy Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure
** Changed in: gobject-introspection (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2056753 Title: pygobject FTBFS on armhf: time_t build test failure Status in GObject Introspection: Fix Released Status in gobject-introspection package in Ubuntu: Fix Committed Status in gobject-introspection package in Debian: Fix Released Bug description: pygobject fails to build on armhf, the only Ubuntu 32-bit architecture that has done the time_t transition. test_gi.py runs a time_t test that I believe is using functions in glib2.0 Test log excerpt tests/test_gi.py ... [ 21%] . --- stderr --- Fatal Python error: Aborted Current thread 0xf785e020 (most recent call first): File "/<>/tests/test_gi.py", line 579 in test_time_t_in File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod File "/usr/lib/python3.12/unittest/case.py", line 634 in run File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__ File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 in console_main File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in File "", line 88 in _run_code File "", line 198 in _run_module_as_main Full build log == https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058819] Re: gnome-shell-extension-ubuntu-dock -dock asymmetrical
I'm not sure we even need to consider this a valid bug if it only existed in a PPA. But it looks like it might also exist in proposed. ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => yaru- theme (Ubuntu) ** Changed in: yaru-theme (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2058819 Title: gnome-shell-extension-ubuntu-dock -dock asymmetrical Status in yaru-theme package in Ubuntu: Fix Committed Bug description: gnome-shell-extension-ubuntu-dock 89ubuntu3 installed from https://ppa.launchpadcontent.net/ubuntu-desktop/ppa/ubuntu noble/main amd64 Packages icons are not centered in the dock. See attachment. The Ubuntu icon at bottom is centered. Note: I don't know if it's appropriate to open a bug for a PPA program. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 89ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:31:51 2024 InstallationDate: Installed on 2024-03-10 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2058819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
[1724567.629003] audit: type=1400 audit(1711133926.877:813): apparmor="DENIED" operation="file_mmap" class="file" namespace="root//lxd-noble-armhf_" profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=876865 comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=1000110 ouid=100 ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058866] [NEW] proposed-migration for cups-browsed 2.0.0-0ubuntu8
Public bug reported: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-browsed and segfaults when invoked as /usr/sbin/cups-browsed. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: cups-browsed (Ubuntu) Importance: Undecided Assignee: Steve Langasek (vorlon) Status: New ** Tags: update-excuse ** Changed in: cups-browsed (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) ** Description changed: - cups-browsed 2.0.0-0ubuntu8 is stuck in -proposed. + cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via + an autopkgtest), early enough that LD_DEBUG=all gives no output. A + local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable + ran, so 8 was uploaded to try to fix this. But the executable somehow + ONLY runs as ./debian/cups-browsed/usr/sbin/cups-browsed and segfaults + when invoked as /usr/sbin/cups-browsed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0
There's also a Noble dist upgrade problem with schemas being tracked in bug 2054761. Keep it in mind in case there's any overlap between the bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2058847 Title: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0 Status in budgie-desktop package in Ubuntu: Triaged Status in mutter package in Ubuntu: New Bug description: mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf schema. This causes budgie-wm to crash immediately on login. Downgrading to 45.3 fixes everything. $ apt policy mutter-common mutter-common: Installed: 45.3-1ubuntu1 Candidate: 46.0-1ubuntu1 Version table: 46.0-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages *** 45.3-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-core 10.9.1-3ubuntu1 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Mar 24 16:00:24 2024 InstallationDate: Installed on 2022-03-19 (736 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2058847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
It can be put into the next mutter update but there is no reason to delay the currently proposed update for it. This seems like a never- ending problem that we're discovering old intermittent build failures in an old GNOME release. We will fix them as they are discovered, but not all of them need to be treated as blockers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Alan, the fix for mantic is released in version 87ubuntu2, not 87ubuntu1. It was published to mantic updates last November so I'm not sure why you wouldn't have received it yet. You can grab it directly from: https://launchpad.net/ubuntu/+archive/primary/+files/gnome-shell-extension-ubuntu-dock_87ubuntu2_all.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Should [0] be part of the SRU to avoid the test failure? [0] https://salsa.debian.org/gnome- team/mutter/-/commit/98302806f85ffe4cd67768fe63992ba32e77146a -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Why do we have to file a new bug for this. The task for mantic says it's fix released, but it clearly isn't. alan@ziggy:~$ grep -r Meta.Rectangle /usr/share/gnome-shell/extensions/ /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js: const rect = new Meta.Rectangle(); alan@ziggy:~$ dpkg -S /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js gnome-shell-extension-ubuntu-dock: /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js alan@ziggy:~$ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 87ubuntu1 Candidate: 87ubuntu1 Version table: *** 87ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status This is fixed in noble, but not mantic. I see no SRU pending: https://ubuntu-archive-team.ubuntu.com/pending-sru This bug was filed against mantic, it's a mantic bug. So the status of 'fixed released' is clearly just incorrect, surely? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
alan@ziggy:~$ sudo journalctl -b0 | grep Meta.Rectangle | wc -l 1836 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033939] Re: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is
** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2033939 Title: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is established Status in gnome-remote-desktop package in Ubuntu: Invalid Bug description: service was working until latest update of gnome-remote-desktop yesterday. managed to reproduce on daily build. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-remote-desktop 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 03:13:31 2023 InstallationDate: Installed on 2023-09-01 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2033939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0
This is because magpie has a dependency on mutter-common. The schema comes from the mutter ubuntu x11 patch which has been temporarily disabled https://launchpad.net/ubuntu/+source/mutter/+changelog Once it has been readded then things will work correctly ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: budgie-desktop (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2058847 Title: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0 Status in budgie-desktop package in Ubuntu: Triaged Status in mutter package in Ubuntu: New Bug description: mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf schema. This causes budgie-wm to crash immediately on login. Downgrading to 45.3 fixes everything. $ apt policy mutter-common mutter-common: Installed: 45.3-1ubuntu1 Candidate: 46.0-1ubuntu1 Version table: 46.0-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages *** 45.3-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-core 10.9.1-3ubuntu1 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Mar 24 16:00:24 2024 InstallationDate: Installed on 2022-03-19 (736 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2058847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I'm agreeing with desktop in following Fedora to bump to 1048576, the precedence makes this safe, and this I consider this a bug fix for crashing software and not a feature request. ** Changed in: procps (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: procps (Ubuntu) Status: Triaged => In Progress ** Changed in: procps (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Committed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)
After extracting the intel/sof-ipc4/mtl/sof-mtl.ri.zst and intel/sof- ace-tplg/sof-mtl-rt711-4ch.tplg.zst and placing them in the same folder, the following dmesg output is created: snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 sof-audio-pci-intel-mtl :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 sof-audio-pci-intel-mtl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode sof-audio-pci-intel-mtl :00:1f.3: DMICs detected in NHLT tables: 0 sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 sof-audio-pci-intel-mtl :00:1f.3: Firmware paths/files for ipc type 1: sof-audio-pci-intel-mtl :00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri sof-audio-pci-intel-mtl :00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl sof-audio-pci-intel-mtl :00:1f.3: Topology file: intel/sof-ace-tplg/sof-mtl-rt711.tplg sof-audio-pci-intel-mtl :00:1f.3: Loaded firmware library: ADSPFW, version: 2.8.1.1 cs42l43 sdw:0:0:01fa:4243:01: supply vdd-p not found, using dummy regulator cs42l43 sdw:0:0:01fa:4243:01: supply vdd-d not found, using dummy regulator cs42l43 sdw:0:0:01fa:4243:01: supply vdd-a not found, using dummy regulator cs42l43 sdw:0:0:01fa:4243:01: supply vdd-io not found, using dummy regulator cs42l43 sdw:0:0:01fa:4243:01: supply vdd-cp not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_P not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_IO not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_A not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_P not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_IO not found, using dummy regulator cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_A not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_P not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_IO not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_A not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_P not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_IO not found, using dummy regulator cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_A not found, using dummy regulator sof-audio-pci-intel-mtl :00:1f.3: Booted firmware version: 2.8.1.1 cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03 cs35l56 sdw:0:2:01fa:3556:01:3: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:1: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:2:01fa:3556:01:2: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:0: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs42l43 sdw:0:0:01fa:4243:01: Slave 6 state check1: UNATTACHED, status was 1 cs35l56 sdw:0:2:01fa:3556:01:3: Slave 1 state check1: UNATTACHED, status was 1 cs35l56 sdw:0:2:01fa:3556:01:2: Slave 2 state check1: UNATTACHED, status was 1 cs35l56 sdw:0:3:01fa:3556:01:1: Slave 1 state check1: UNATTACHED, status was 1 cs35l56 sdw:0:3:01fa:3556:01:0: Slave 2 state check1: UNATTACHED, status was 1 Adding alias for supply vdd-amp,(null) -> vdd-amp,sdw:0:0:01fa:4243:01 sof-audio-pci-intel-mtl :00:1f.3: Topology: ABI 3:29:0 Kernel ABI 3:23:0 sof-audio-pci-intel-mtl :00:1f.3: error: can't connect DAI dai-copier.DMIC.dmic01.capture stream dmic01 sof-audio-pci-intel-mtl :00:1f.3: error: failed to add widget id 0 type 28 name : dai-copier.DMIC.dmic01.capture stream dmic01 sof_sdw sof_sdw: ASoC: failed to load widget dai-copier.DMIC.dmic01.capture sof_sdw sof_sdw: ASoC: topology: could not load header: -22 sof-audio-pci-intel-mtl :00:1f.3: error: tplg component load failed -22 sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP topology -22 sof-audio-pci-intel-mtl :00:1f.3: ASoC: error at snd_soc_component_probe on :00:1f.3: -22 sof_sdw sof_sdw: ASoC: failed to instantiate card -22 sof_sdw sof_sdw: error -EINVAL: snd_soc_register_card failed -22 sof_sdw: probe of sof_sdw failed with error -22 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058691 Title: No sound card detected on the Dell xps 16 2024 (9640) Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus Logic CS42L43 card is used which apparently got support in Linux 6.6
[Desktop-packages] [Bug 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)
During boot, dmesg reports that the intel/sof-ipc4/mtl/sof-mtl.ri and intel/sof-ace-tplg/sof-mtl-rt711.tplg files can not be found. However, the corresponding files are there but packaged with zst file endings. sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode sof-audio-pci-intel-mtl :00:1f.3: DMICs detected in NHLT tables: 0 sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 sof-audio-pci-intel-mtl :00:1f.3: SOF firmware and/or topology file not found. sof-audio-pci-intel-mtl :00:1f.3: Supported default profiles sof-audio-pci-intel-mtl :00:1f.3: - ipc type 1 (Requested): sof-audio-pci-intel-mtl :00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri sof-audio-pci-intel-mtl :00:1f.3: Topology file: intel/sof-ace-tplg/sof-mtl-rt711.tplg sof-audio-pci-intel-mtl :00:1f.3: Check if you have 'sof-firmware' package installed. sof-audio-pci-intel-mtl :00:1f.3: Optionally it can be manually downloaded from: sof-audio-pci-intel-mtl :00:1f.3: https://github.com/thesofproject/sof-bin/ sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058691 Title: No sound card detected on the Dell xps 16 2024 (9640) Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus Logic CS42L43 card is used which apparently got support in Linux 6.6 https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general- linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus- logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe- jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/ No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 23:00:06 2024 InstallationDate: Installed on 2024-03-19 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) MachineType: Dell Inc. XPS 16 9640 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0YFT36 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62: dmi.product.family: XPS dmi.product.name: XPS 16 9640 dmi.product.sku: 0C62 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055124] Re: WiFi adapter cannot get IP configuration from Netgear orbi RBR20
I made an Ubuntu update this week and now my laptop is able to connect to my Orbi access point. Maybe this one ? Start-Date: 2024-03-13 06:52:44 Commandline: apt-get upgrade Requested-By: fred (1000) Upgrade: dpkg:amd64 (1.21.1ubuntu2.2, 1.21.1ubuntu2.3), libcups2:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-bsd:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-common:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-client:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-ppdc:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-daemon:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-ipp-utils:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), dpkg-dev:amd64 (1.21.1ubuntu2.2, 1.21.1ubuntu2.3), gir1.2-accountsservice-1.0:amd64 (22.07.5-2ubuntu1.4, 22.07.5-2ubuntu1.5), libcupsimage2:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), libdpkg-perl:amd64 (1.21.1ubuntu2.2, 1.21.1ubuntu2.3), accountsservice:amd64 (22.07.5-2ubuntu1.4, 22.07.5-2ubuntu1.5), cups-core-drivers:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-server-common:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), libaccountsservice0:amd64 (22.07.5-2ubuntu1.4, 22.07.5-2ubuntu1.5) End-Date: 2024-03-13 06:52:52 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055124 Title: WiFi adapter cannot get IP configuration from Netgear orbi RBR20 Status in network-manager package in Ubuntu: New Bug description: Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect anymore to my Netgear Orbi RBR20 WiFi access point. The wifi connection is still working fine with my Android smartphone set as a WiFi access point. My other devices can connect successfully to the Orbi RBR20: printers, smartphones, TV, tablets, desktop, Sonos, Netatmo... Expected: - Get an IP address from the Netgear Orbi RBR20. Happened instead: - No IP address obtained, stuck with no WiFi connectivity. ThinkPad X13 Gen2 with Ubuntu 22.04.4 LTS: -- fred@ThinkPad:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename:jammy Mediatek WiFi adapter: -- *-network description: Interface réseau sans fil produit: MT7921 802.11ax PCI Express Wireless Network Adapter fabricant: MEDIATEK Corp. identifiant matériel: 0 information bus: pci@:03:00.0 nom logique: wlp3s0 nom logique: /dev/fb0 version: 00 numéro de série: 74:97:79:8a:36:e7 bits: 64 bits horloge: 33MHz fonctionnalités: pciexpress msi pm bus_master cap_list ethernet physical wireless fb configuration : broadcast=yes depth=32 driver=mt7921e driverversion=6.5.0-15-generic firmware=01-20220209150915 latency=0 link=yes mode=1920x1200 multicast=yes visual=truecolor wireless=IEEE 802.11 xres=1920 yres=1200 ressources : mémoireE/S:40-3f mémoireE/S:40-3f mémoireE/S:40-3f irq:87 mémoire:47020-4702f mémoire:47030-470303fff mémoire:470304000-470304fff No power saving: [connection] wifi.powersave = 2 Cannot obtain IP configuration: --- DEVICE TYPE STATE CONNECTION wlp3s0 wifi connexion (obtention de la configuration IP) ORBIchamprond Device association looks OK: [241460.865152] wlp3s0: authenticate with c2:a5:11:2f:00:c1 [241460.883343] wlp3s0: send auth to c2:a5:11:2f:00:c1 (try 1/3) [241460.886001] wlp3s0: authenticated [241460.887489] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 1/3) [241460.991496] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 2/3) [241461.016131] wlp3s0: RX AssocResp from c2:a5:11:2f:00:c1 (capab=0x1511 status=0 aid=1) [241461.046179] wlp3s0: associated RBR20 firmware version: v2.7.3.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033440 Title: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio" Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Lunar: Won't Fix Bug description: Recommend demoting pipewire-audio from Depends: to Recommends:. Reason: While it's not ideal, the Ubuntu Desktop can still function on the pulseaudio backend rather than using the direct pipewire-alsa backend which conflicts with the pulseaudio package. This would help people who wish to have a more traditional JACK setup that is bridged to pulseaudio. Right now, this setup is incompatible. Original description: I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external USB drive). Immediately after the installation, I have also installed with apt the "ubuntustudio-installer" package. In the dialog provided by the ubuntustudio-installer, I have selected the following metapackages: - linux-lowlatency - ubuntustudio-lowlatency-settings - ubuntustudio-performance-tweaks - ubuntustudio-audio - ubuntu-pulseaudio-config and pressed "Modify installed Package Selection" After a while a "qaptbatch" dialog has appeared with title "Commit Error" and message "An error occurred while applying changes" So the installation has failed. Then I have tried to manually install each metapackage in the list above with apt and every package was installed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058842] [NEW] Grid pattern not aligned with text
Public bug reported: I am using the Text Editor of GNOME 45.0 (Ubuntu 23.10) and I noticed that, when I enable the "grid pattern" in the preferences, it is not aligned with the text: https://i.imgur.com/6RLpotv.png Is this normal? ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2058842 Title: Grid pattern not aligned with text Status in gnome-text-editor package in Ubuntu: New Bug description: I am using the Text Editor of GNOME 45.0 (Ubuntu 23.10) and I noticed that, when I enable the "grid pattern" in the preferences, it is not aligned with the text: https://i.imgur.com/6RLpotv.png Is this normal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2058842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058840] [NEW] Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Public bug reported:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to the
patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
** Description changed:
+ Ubuntu 22.04 LTS Jammy x64
+
+
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
[Desktop-packages] [Bug 2049280] Re: udisks2 core dump
Hi!! I present a similar issue Here my data. Hope can help me. $ sudo systemctl status udisks2 × udisks2.service - Disk Manager Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: enabled) Active: failed (Result: core-dump) since Sun 2024-03-24 03:23:50 CST; 19min ago Docs: man:udisks(8) Process: 2615 ExecStart=/usr/libexec/udisks2/udisksd (code=dumped, signal=TRAP) Main PID: 2615 (code=dumped, signal=TRAP) CPU: 11ms mar 24 03:23:50 OldMachine systemd[1]: Starting udisks2.service - Disk Manager... mar 24 03:23:50 OldMachine udisksd[2615]: udisks daemon version 2.10.1 starting mar 24 03:23:50 OldMachine udisksd[2615]: failed to load module swap: /lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header mar 24 03:23:50 OldMachine udisksd[2615]: Failed to load the 'swap' libblockdev plugin mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Main process exited, code=dumped, status=5/TRAP mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Failed with result 'core-dump'. mar 24 03:23:50 OldMachine systemd[1]: Failed to start udisks2.service - Disk Manager. $ sudo apt search udisks2|grep -i install WARNING: apt does not have a stable CLI interface. Use with caution in scripts. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ uname -a Linux OldMachine 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ swapon -s FilenameTypeSizeUsed Priority /swapfile file2097148 0 -2 $ apt search udisks2|grep -i install WARNING: apt does not have a stable CLI interface. Use with caution in scripts. $ sudo lshw -c storage *-nvme descripción: NVMe device producto: SKHynix_HFS512GD9TNI-L2B0B fabricante: SK hynix id físico: 0 información del bus: pci@:55:00.0 nombre lógico: /dev/nvme0 versión: 11720C10 serie: CJA4N765010304Q5N anchura: 64 bits reloj: 33MHz capacidades: nvme pm msi msix pciexpress nvm_express bus_master cap_list configuración: driver=nvme latency=0 nqn=nqn.2014.08.org.nvmexpress:1c5c1c5cCJA4N765010304Q5N SKHynix_HFS512GD9TNI-L2B0B state=live recursos: irq:16 memoria:ae00-ae003fff memoria:ae005000-ae005fff memoria:ae004000-ae004fff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2049280 Title: udisks2 core dump Status in udisks2 package in Ubuntu: New Bug description: Running systemctl status on udisks2 shows core-dump being created. $ sudo systemctl status udisks2 × udisks2.service - Disk Manager Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: enabled) Active: failed (Result: core-dump) since Sat 2024-01-13 23:07:14 EET; 4s ago Docs: man:udisks(8) Process: 14345 ExecStart=/usr/libexec/udisks2/udisksd (code=dumped, signal=TRAP) Main PID: 14345 (code=dumped, signal=TRAP) CPU: 14ms Jan 13 23:07:14 testo systemd[1]: Starting udisks2.service - Disk Manager... Jan 13 23:07:14 testo udisksd[14345]: udisks daemon version 2.10.1 starting Jan 13 23:07:14 testo udisksd[14345]: failed to load module swap: /lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header Jan 13 23:07:14 testo udisksd[14345]: Failed to load the 'swap' libblockdev plugin Jan 13 23:07:14 testo systemd[1]: udisks2.service: Main process exited, code=dumped, status=5/TRAP Jan 13 23:07:14 testo systemd[1]: udisks2.service: Failed with result 'core-dump'. Jan 13 23:07:14 testo systemd[1]: Failed to start udisks2.service - Disk Manager. Ubuntu version: $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 Kernel version: $ uname -a Linux testo 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Swap status: $ swapon -s FilenameTypeSizeUsed Priority /swap.img file8388604 0 -2 Udisks2 package installation: $ apt search udisks2|grep -i install WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libudisks2-0/mantic-updates,now 2.10.1-1ubuntu1.1 amd64 [installed,automatic] udisks2/mantic-updates,now 2.10.1-1ubuntu1.1 amd64 [installed,automatic] Storage specs: $ lshw -c storage *-nvme description: NVMe device product: SKHynix_HFS001TD9TNI-L2B0B vendor: SK hynix physical id: 0 bus info: pci@:55:00.0 logical name: /dev/nvme0
[Desktop-packages] [Bug 2058819] Re: gnome-shell-extension-ubuntu-dock -dock asymmetrical
Fixed just restarting, thanks a lot ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2058819 Title: gnome-shell-extension-ubuntu-dock -dock asymmetrical Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: gnome-shell-extension-ubuntu-dock 89ubuntu3 installed from https://ppa.launchpadcontent.net/ubuntu-desktop/ppa/ubuntu noble/main amd64 Packages icons are not centered in the dock. See attachment. The Ubuntu icon at bottom is centered. Note: I don't know if it's appropriate to open a bug for a PPA program. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 89ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:31:51 2024 InstallationDate: Installed on 2024-03-10 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2058819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009712] Re: Gnome lock screen loses focus if a window opens while screen is locked
Reason of focus loss is different in mantic (GNOME 40 series) than before (GNOME 3 series). For GNOME 40 series, I have temporarily applied a workaround in my personal configuration to disable the lock screen, but wouldn't recommend that in a work or school computer. ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2009712 Title: Gnome lock screen loses focus if a window opens while screen is locked Status in gnome-shell package in Ubuntu: Triaged Bug description: The Gnome lock screen has caused me a lot of frustration over time, since I've often found that is unresponsive to the keyboard when I come back to the system and try to get back in after the screen lock has activated. I finally realized that this is usually due to the "Software Updater" window popping up while I'm away from the computer, though it can be triggered by any window opening while the screen is locked. To reproduce: Open a terminal window and type "sleep 15; gnome-terminal", then immediately click on the upper-right notification area and select the "Lock" option in the popup menu. Observe the screen go into lock. Wait 15 seconds. Press a key like Ctrl or Alt to wake the screen. Attempt to type in the password (or use a fingerprint reader if you have one). Nothing happens. Click the screen (or possibly tap/swipe it if you have a touchscreen). The password prompt will now appear, and it should be possible to type in the password (or use the fingerprint reader) This is a very annoying behavior. It shouldn't be necessary to click/tap the screen to restore focus when the whole desktop has been taken over by the screen locker. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 8 08:21:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-13 (146 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
