[Desktop-packages] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
This bug was fixed in the package xorg-server - 2:21.1.4-2ubuntu1.4 --- xorg-server (2:21.1.4-2ubuntu1.4) kinetic; urgency=medium * re-calculate-the-clock-and-refresh-rate.diff: Import v3, fix a crash. (LP: #1999008) -- Timo Aaltonen Wed, 07 Dec 2022 11:28:20 +0200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
This bug was fixed in the package xorg-server - 2:21.1.3-2ubuntu2.6 --- xorg-server (2:21.1.3-2ubuntu2.6) jammy; urgency=medium * re-calculate-the-clock-and-refresh-rate.diff: Import v3, fix a crash. (LP: #1999008) -- Timo Aaltonen Wed, 07 Dec 2022 11:32:56 +0200 ** Changed in: xorg-server (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: xorg-server (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Looks like the DEP8 test is flaky; it has failed with previous non-xorg- server packages as well, and I've just retried it and it has passed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 2004623] [NEW] [GNOME 44] JS ERROR: TypeError: function Meta.new: At least 2 arguments required, but only 1 passed
Public bug reported: (gnome-shell:76461): Gjs-CRITICAL **: 14:37:54.077: JS ERROR: TypeError: function Meta.new: At least 2 arguments required, but only 1 passed LaunchSubprocess@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:492:54 launchDesktop@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:443:27 innerEnable/data.dbusConnectionId<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:182:9 ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: High Status: New ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2004623 Title: [GNOME 44] JS ERROR: TypeError: function Meta.new: At least 2 arguments required, but only 1 passed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: (gnome-shell:76461): Gjs-CRITICAL **: 14:37:54.077: JS ERROR: TypeError: function Meta.new: At least 2 arguments required, but only 1 passed LaunchSubprocess@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:492:54 launchDesktop@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:443:27 innerEnable/data.dbusConnectionId<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:182:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2004623/+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 2004534] Re: suspend does not work
Please also collect a system log of the problem. If you had to reboot to recover from it then run: journalctl -b-1 > prevboot.txt or if you didn't need to reboot then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2004534 Title: suspend does not work Status in Ubuntu: Incomplete Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2023-02-01 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: JTCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ABA7 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: dmi.product.family: IdeaPad 3 15ABA7 dmi.product.name: 82RN dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 dmi.product.version: IdeaPad 3 15ABA7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/+bug/2004534/+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 2004534] Re: suspend does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2004534 Title: suspend does not work Status in Ubuntu: Incomplete Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2023-02-01 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: JTCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ABA7 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: dmi.product.family: IdeaPad 3 15ABA7 dmi.product.name: 82RN dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 dmi.product.version: IdeaPad 3 15ABA7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/+bug/2004534/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004533 Title: Gtk-WARNING **: ...: drawing failure for widget '...': invalid value (typically too big) Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004613] Re: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K
The most likely explanation here is that the kernel is not offering 4K as a supported resolution, which you can check by running: grep . /sys/class/drm/*/modes If it's not listed there then you need a higher quality HDMI 2.0 cable. Or even better to use DisplayPort instead. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2004613 Title: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K Status in linux package in Ubuntu: Incomplete Bug description: This GPU should be capable of 4K resolution, but it's unavailable. Tried manually adding modeline with xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync xrandr --addmode HDMI-3 "3840x2160_60.00" Still fails to set 4K resolution. Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added linux-modules-extra, ensured that system is loading i915 kernel module. inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1) v: 4.6 Mesa 22.0.5 lspci -k | head -10 00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05) Subsystem: Dell Device 0ac5 00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c) Subsystem: Dell Device 0ac5 Kernel driver in use: i915 Kernel modules: i915 xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00* 59.9430.0024.0029.9723.98 1920x1080i60.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0030.0059.9429.9724.0023.98 1024x768 75.0370.0760.00 800x600 72.1975.0060.32 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8160.0059.94 720x400 70.08 3840x2160_60.00 59.98 # <--- manually configured xrandr --output HDMI-3 --mode 3840x2160_60.00 xrandr: Configure crtc 0 failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 2 22:00:36 2023 DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0ac5] InstallationDate: Installed on 2020-07-18 (929 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgkubuntu-root ro nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago) dmi.bios.date: 05/18/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.60 dmi.board.name: 057FFP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.60:bd05/18/2022:br1.1:svnDellInc.:pnOptiPlex3000:pvr:rvnDellInc.:rn057FFP:rvrA00:cvnDellInc.:ct3:cvr:sku0AC5: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3000 dmi.product.sku: 0AC5 dmi.sys.vendor:
[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
The fact that you have 3 x 4K monitors connected makes me think all those GTK warnings are some kind of texture size limit being exceeded. Although even basic GPUs should support textures up to 16K in size. Perhaps this is a GTK-specific problem where it tries to internally allocate something that the full desktop resolution and fails. -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gtk+3.0 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
It looks like you're using Xorg fractional scaling, so yes that will take the texture requirements past the limit supported by the GPU if you do it across multiple 4K monitors. Some parts of the desktop will cope and other parts (GTK) might not cope. To confirm this, please run: xrandr --verbose > xrandr.txt and attach the resulting text file here. Possible workarounds (you only need one): * Only use integer scaling * Only use Wayland sessions * Use fewer monitors ** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => nvidia-graphics-drivers-525 (Ubuntu) ** Package changed: gnome-shell-extension-desktop-icons-ng (Ubuntu) => gtk+3.0 (Ubuntu) ** Tags added: xrandr-scaling -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gtk+3.0 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about
[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
Interesting Firefox has similar warnings as DING had before. That suggests the bug is either in GTK or the graphics driver. Rather than being a DING or a Firefox problem. As for the screenshot in comment #12, make sure you're never suspending the system, switching users or even switching VTs. Because all of those can cause the Nvidia driver to lose textures, which is covered by bug 1876632. -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gtk+3.0 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 1974179] Re: Kubuntu: Noto Color Emoji
[Expired for fonts-noto-color-emoji (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1974179 Title: Kubuntu: Noto Color Emoji Status in fonts-noto-color-emoji package in Ubuntu: Expired Bug description: I am working on Kubuntu 22.04 LTS. It has been observed that with some GUI was not opening due to the Font Type Noto Color Emoji. Disabling this the GUI was successfully opened. executing the command "#display /usr/share/fonts/truetype/noto/NotoColorEmoji.ttf" Result: unable to read font /tmp/magick-8NkJdrn3QxnVQQtkhvTzrKd9bDXlxihn' @ error/annotate.c/RenderFreetype/1481. non-conforming drawing primitive definition text' @ error/draw.c/RenderMVGContent/4404. Opens a blank page without any content. This affects GUI developed in QT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1974179/+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 2004613] [NEW] Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K
Public bug reported: This GPU should be capable of 4K resolution, but it's unavailable. Tried manually adding modeline with xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync xrandr --addmode HDMI-3 "3840x2160_60.00" Still fails to set 4K resolution. Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added linux-modules-extra, ensured that system is loading i915 kernel module. inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1) v: 4.6 Mesa 22.0.5 lspci -k | head -10 00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05) Subsystem: Dell Device 0ac5 00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c) Subsystem: Dell Device 0ac5 Kernel driver in use: i915 Kernel modules: i915 xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00* 59.9430.0024.0029.9723.98 1920x1080i60.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0030.0059.9429.9724.0023.98 1024x768 75.0370.0760.00 800x600 72.1975.0060.32 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8160.0059.94 720x400 70.08 3840x2160_60.00 59.98 # <--- manually configured xrandr --output HDMI-3 --mode 3840x2160_60.00 xrandr: Configure crtc 0 failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 2 22:00:36 2023 DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0ac5] InstallationDate: Installed on 2020-07-18 (929 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgkubuntu-root ro nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago) dmi.bios.date: 05/18/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.60 dmi.board.name: 057FFP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.60:bd05/18/2022:br1.1:svnDellInc.:pnOptiPlex3000:pvr:rvnDellInc.:rn057FFP:rvrA00:cvnDellInc.:ct3:cvr:sku0AC5: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3000 dmi.product.sku: 0AC5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 kubuntu resolution ubuntu ** Summary changed: - Intel Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K + Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K -- You
[Desktop-packages] [Bug 2003331] Re: Can't log in to lunar x11 session
On 2023-02-02 20:25, Brian Murray wrote: > Could this be a duplicate of bug 2004092? I don't think so. The buttons showed up as expected, and I installed successfully. My user ID is 1000. The problem is that I can't log in to "Ubuntu on Xorg". Just updated the packages and the problem is still present. -- 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/2003331 Title: Can't log in to lunar x11 session Status in ubuntu-meta package in Ubuntu: New Bug description: On a freshly installed and updated lunar in VirtualBox it doesn't let me log in to Ubuntu on Xorg. I'm just bumped back to the login screen. journalctl extract attached. On my regular (updated) lunar install, logging in to Ubuntu on Xorg works fine. But that's anything but a fresh install. Missing dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 2004532] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644559/+files/acpidump.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.Info.core.txt
apport information ** Attachment added: "Snap.Info.core.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644555/+files/Snap.Info.core.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
# attached below, taken with the chromium browser running $ journalctl -r | head -n 300 >journal.log ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532/+attachment/5644560/+files/journal.log -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no
[Desktop-packages] [Bug 2004532] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644558/+files/UdevDb.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644557/+files/Snap.Info.gtk-common-themes.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.Info.core18.txt
apport information ** Attachment added: "Snap.Info.core18.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644556/+files/Snap.Info.core18.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644550/+files/ProcInterrupts.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644553/+files/Snap.Connections.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.Info.chromium.txt
apport information ** Attachment added: "Snap.Info.chromium.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644554/+files/Snap.Info.chromium.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Snap.ChromiumPrefs.txt
apport information ** Attachment added: "Snap.ChromiumPrefs.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644552/+files/Snap.ChromiumPrefs.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644551/+files/ProcModules.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644549/+files/ProcEnviron.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644548/+files/ProcCpuinfoMinimal.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644547/+files/ProcCpuinfo.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644546/+files/Lsusb-v.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644545/+files/Lsusb-t.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644544/+files/Lsusb.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644543/+files/Lspci-vt.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644542/+files/Lspci.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2004532/+attachment/5644541/+files/Dependencies.txt -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
apport information ** Tags added: apport-collected snap ** Description changed: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DRM.card0-DP-1: + enabled: enabled + dpms: On + status: connected + edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== + modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 + DRM.card0-DP-2: + enabled: disabled + dpms: Off + status: disconnected + edid-base64: + modes: + DRM.card0-DP-3: + enabled: disabled + dpms: Off + status: disconnected + edid-base64: + modes: + DRM.card0-HDMI-A-1: + enabled: disabled + dpms: Off + status: disconnected + edid-base64: + modes: + DiskUsage: + Filesystem Type Size Used Avail Use% Mounted on + /dev/nvme0n1p2 ext4 916G 222G 648G 26% / + tmpfs tmpfs 16G 0 16G 0% /dev/shm + /dev/nvme0n1p2 ext4 916G 222G 648G 26% / + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2020-08-02 (914 days ago) + InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: ASUS System Product Name + Package: chromium-browser 1:85.0.4183.83-0ubuntu2 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 + Snap.Changes: no changes found + Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119 (772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458}) + Snap.ChromiumVersion: + update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied + Chromium 109.0.5414.119 snap + Tags: kinetic snap + Uname: Linux 5.19.0-29-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days
[Desktop-packages] [Bug 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grilo-plugins (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1877219 Title: dozens of empty grilo-plugin-cache folders polluting /tmp Status in Grilo Plugins: Fix Released Status in grilo-plugins package in Ubuntu: Confirmed Bug description: My /tmp folder has dozens of empty folders with names like grilo- plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
some of my logs: Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkPaned': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkFileChooserWidget': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkFileChooserDialog': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: infinite surface size not supported (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkPathBar': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkStack': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkRevealer': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkPaned': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkFileChooserWidget': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure for widget 'GtkFileChooserDialog': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (firefox-aurora:221704): Gtk-WARNING **: 15:41:12.615: infinite surface size not supported -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1
[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
My desktop is still buggy, I have attached a pic of what the window controls look like on browser, file/folder windows. ** Attachment added: "Screenshot from 2023-02-02 15-39-43.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644519/+files/Screenshot%20from%202023-02-02%2015-39-43.png -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
Ok, I used the extension manager and have disabled the icons. I now have no icons and no dock, it says my dock is on, but it is no longer visible on the desktop -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.
I had already disabled all my extensions. Now I have deleted them and my dock bar is gone (still comes up when i hit the windows key). logged out and logged back in same issue. #2: # gnome-extensions disable d...@rastersoft.com Failed to connect to GNOME Shell yet without the extension specified: # gnome-extensions disable gnome-extensions: No UUID given Usage: gnome-extensions disable [OPTION…] UUID Disable an extension Application Options: -q, --quiet Do not print error messages I should also note that ANY full screen video is extremely slow, sluggish framerate etc. -- 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/2004533 Title: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: A tiny sample of of my logs starting with the subject of this thread: gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on because it needs an allocation. others gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite surface size not supported gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.) st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout ("…")] which is not in the stage. gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4 Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 0x556a2f5a5b70, but it still has children left: Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300 Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 23:40:47 2023 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" InstallationDate: Installed on 2021-01-17 (745 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top
I've also noticed that the crash in https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 gets triggered by the 1pixel shift, even when sharing the full desktop screen. ** Bug watch added: Mozilla Bugzilla #1790496 https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 2003331] Re: Can't log in to lunar x11 session
Could this be a duplicate of bug 2004092? -- 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/2003331 Title: Can't log in to lunar x11 session Status in ubuntu-meta package in Ubuntu: New Bug description: On a freshly installed and updated lunar in VirtualBox it doesn't let me log in to Ubuntu on Xorg. I'm just bumped back to the login screen. journalctl extract attached. On my regular (updated) lunar install, logging in to Ubuntu on Xorg works fine. But that's anything but a fresh install. Missing dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
In Kinetic, there is a DEP8 regression on armhf that was not addressed yet: autopkgtest for openmsx-catapult/18.0-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , ppc64el: Pass, s390x: Pass I see it was retried multiple times, and a migration-reference/0 run passed, so it's indeed a regression with xorg- server/2:21.1.4-2ubuntu1.4. Can someone address it please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 2004586] [NEW] Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
Public bug reported: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: kivu snap ** Tags added: kivu snap -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: New Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+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
Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Thank you for reporting back! > Sorry for missing pieces of info in my original report. Don't worry, you even used Apport and provided many useful details. Apparently, Apport doesn't submit enough information if snapd is its target. Can you please run apport-collect -p chromium-browser 2004532 I think that will give us more information, I'm particularly interested in dmesg at least. The journal output after you launch Chromium could also be useful, say: journalctl -r | head -n 300 > journal.log My apologies for not having asked all that at once. -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004532/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Hi Nathan, Sorry for missing pieces of info in my original report. I am running KDE/Plasma on Xorg. And yes, "chromium --disable-gpu" fixes the issue for chromium as well. I am attaching chromium run log below. ** Attachment added: "chromium.log" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532/+attachment/5644474/+files/chromium.log -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004532/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
My error is quite annoying to, already the hotspot work on the SO, the activated the wifi and detect the wifi, but when my cellphone connected to the hotspot assigned a public ip, for been exactly assigned by default the DHCP the ip 10.42.0.189 with a mask subred 255.255.255.0, but the computer than is working like service DHCP already had 192.168.1.56, i'm undestand if this hotspot is working like a bridge appliance, but, this time didnt is the case, because the default router has the 192.168.1.254, so the subred mask of the segment of the red is from 192.168.1.0 - 192.168.1.255 wtf, why assign me a public IP, jajajaj, i will send the evidence. ** Attachment added: "hotspot problem2.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5644473/+files/hotspot%20problem2.png -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 2004577] [NEW] Issue with libabsl-dev
Public bug reported: 1. Release version /$ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2. Package version. /$ apt-cache policy libabsl-dev libabsl-dev: Installed: 0~20210324.2-2 Candidate: 0~20210324.2-2 Version table: *** 0~20210324.2-2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3. Expected behavior: Correctly compile using GNU GCC or Clang compilers. 4. Observed behavior: GNU GCC reports error. Clang compiles fine though (ignores the malformed input). 5. Detailed description Installed libabsl-dev package via apt install to use its hashmap within C++. Added AX_PKG_CHECK_MODULES([ABSL], [], [absl_flat_hash_set]) to my configure.ac and respectively, added the $(ABSL_CFLAGS) and $(ABSL_LIBS) to my target's CFLAGS and LDADD within Makefile.am.: test_bench_hsd_CFLAGS = $(AM_CFLAGS) $(CATCH2_CFLAGS) $(ABSL_CFLAGS) test_bench_hsd_LDADD = $(HASHER_LIB) $(TEST_LIBS) $(CATCH2_LIBS) $(ABSL_LIBS) Here's the resulting libtool command that will generate erroneous g++ options: /bin/bash ./libtool --tag=CXX --mode=link g++ -std=c++17 -W -Wall -Wextra -Wnon-virtual-dtor -pedantic -pipe -O3 -g -g -O2 -g -L/usr/lib/x86_64-linux-gnu -L/home/ubuntu/make_world/install/lib -o test/bench_hsd test/bench_hashset.o src/lib/libhasher.la -L/home/ubuntu/make_world/install/lib -lCatch2Main -lCatch2 -labsl_cord -labsl_hash -labsl_city -labsl_bad_variant_access -labsl_wyhash -labsl_raw_hash_set -labsl_bad_optional_access -labsl_hashtablez_sampler -labsl_exponential_biased -labsl_synchronization -labsl_graphcycles_internal -labsl_stacktrace -Wl -labsl_symbolize -labsl_debugging_internal -labsl_demangle_internal -labsl_malloc_internal -labsl_time -labsl_civil_time -labsl_strings -labsl_strings_internal -Wl -labsl_base -labsl_spinlock_wait -labsl_int128 -labsl_throw_delegate -labsl_raw_logging_internal -labsl_log_severity -labsl_time_zone The generated g++ then had '-Wl -Wl' in its options and that caused the error: libtool: link: g++ -std=c++17 -W -Wall -Wextra -Wnon-virtual-dtor -pedantic -pipe -O3 -g -g -O2 -g -o test/.libs/bench_hsd test/bench_hashset.o -Wl -Wl -L/usr/lib/x86_64-linux-gnu -L/home/ubuntu/make_world/install/lib src/lib/.libs/libhasher.so -lCatch2Main -lCatch2 -labsl_cord -labsl_hash -labsl_city -labsl_bad_variant_access -labsl_wyhash -labsl_raw_hash_set -labsl_bad_optional_access -labsl_hashtablez_sampler -labsl_exponential_biased -labsl_synchronization -labsl_graphcycles_internal -labsl_stacktrace -labsl_symbolize -labsl_debugging_internal -labsl_demangle_internal -labsl_malloc_internal -labsl_time -labsl_civil_time -labsl_strings -labsl_strings_internal -labsl_base -labsl_spinlock_wait -labsl_int128 -labsl_throw_delegate -labsl_raw_logging_internal -labsl_log_severity -labsl_time_zone -Wl,-rpath -Wl,/home/ubuntu/make_world/install/lib g++: error: unrecognized command-line option '-Wl'; did you mean '-W'? g++: error: unrecognized command-line option '-Wl'; did you mean '-W'? Printing the ABSL_LIBS from within Makefile reveled that there were two occurrences of '-Wl': Makefile:1221: ABSL_LIBS: -labsl_cord -labsl_hash -labsl_city -labsl_bad_variant_access -labsl_wyhash -labsl_raw_hash_set -labsl_bad_optional_access -labsl_hashtablez_sampler -labsl_exponential_biased -labsl_synchronization -labsl_graphcycles_internal -labsl_stacktrace -Wl -labsl_symbolize -labsl_debugging_internal -labsl_demangle_internal -labsl_malloc_internal -labsl_time -labsl_civil_time -labsl_strings -labsl_strings_internal -Wl -labsl_base -labsl_spinlock_wait -labsl_int128 -labsl_throw_delegate -labsl_raw_logging_internal -labsl_log_severity -labsl_time_zone Further, I checked the .pc files and found that they have those '-Wl' keys that should not be there: /$ grep -r '\-Wl' /usr/lib/x86_64-linux-gnu/pkgconfig/ | grep '\-Wl' /usr/lib/x86_64-linux-gnu/pkgconfig/absl_random_internal_salted_seed_seq.pc:Libs: -L${libdir} -Wl /usr/lib/x86_64-linux-gnu/pkgconfig/absl_random_internal_pool_urbg.pc:Libs: -L${libdir} -Wl -labsl_random_internal_pool_urbg /usr/lib/x86_64-linux-gnu/pkgconfig/absl_symbolize.pc:Libs: -L${libdir} -Wl -labsl_symbolize /usr/lib/x86_64-linux-gnu/pkgconfig/absl_btree.pc:Libs: -L${libdir} -Wl /usr/lib/x86_64-linux-gnu/pkgconfig/absl_fast_type_id.pc:Libs: -L${libdir} -Wl /usr/lib/x86_64-linux-gnu/pkgconfig/absl_flags_private_handle_accessor.pc:Libs: -L${libdir} -Wl -labsl_flags_private_handle_accessor /usr/lib/x86_64-linux-gnu/pkgconfig/absl_strerror.pc:Libs: -L${libdir} -Wl -labsl_strerror /usr/lib/x86_64-linux-gnu/pkgconfig/absl_random_internal_randen_hwaes_impl.pc:Libs: -L${libdir} -Wl -labsl_random_internal_randen_hwaes_impl /usr/lib/x86_64-linux-gnu/pkgconfig/absl_random_internal_randen.pc:Libs: -L${libdir} -Wl -labsl_random_internal_randen /usr/lib/x86_64-linux-gnu/pkgconfig/absl_random_internal_nonsecure_base.pc:Libs: -L${libdir} -Wl
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Thanks for the report, Bamywasi. If disabling hardware acceleration managed to fix your issue for Firefox, in Chromium it should work too? The command line would be "chromium --disable-gpu". Does your KDE runs on Wayland on Xorg? If on Wayland, do you experience the same bug - with "chromium --ozone-platform=wayland"? - in Xorg? Could you please attach the chromium.log file resulting from "chromium --enable-logging --v=1 &> chromium.log"? -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004532/+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 1956005] Re: Firefox Snap won't open links to WhatsApp API
Still on Firefox 109.0 (64 bits) snap for Canonical-002 1.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1956005/+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 2004554] Re: While using application switching in multi-tasking
Thanks for the bug report. I have just tested: Settings > Multitasking > Application Switching > Include applications from the current workspace only and although I wasn't able to reproduce exactly the same bug, I was able to reproduce a similar bug in that the dot next to the Files icon disappeared even on the workspace where the Files window is still open. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Summary changed: - While using application switching in multi-tasking + Dock shows wrong indicator dots (eventually) when "Include applications from the current workspace only" is enabled ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Triaged -- 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/2004554 Title: Dock shows wrong indicator dots (eventually) when "Include applications from the current workspace only" is enabled Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: While switching workspace, the option : include applications from current workspace only is opted. The files founder does not switch properly. If opened in one workspace, and switched to another workspace. Then the dot ( that shoes finder is open) does not go away. And many more please check. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 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: ubuntu:GNOME Date: Thu Feb 2 16:47:24 2023 DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD Graphics 630] [1462:12aa] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106M [GeForce RTX 2060 Mobile] [1462:12aa] InstallationDate: Installed on 2021-05-11 (631 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. GF65 Thin 9SEXR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=f2aafeb8-65f1-4f53-a7f4-a8bac75a5fbd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-27 (6 days ago) dmi.bios.date: 10/21/2021 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16W1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-16W1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16W1IMS.10C:bd10/21/2021:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGF65Thin9SEXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16W1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16W1.1: dmi.product.family: GF dmi.product.name: GF65 Thin 9SEXR dmi.product.sku: 16W1.1 dmi.product.version: REV: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.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/gnome-shell-extension-ubuntu-dock/+bug/2004554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2003335] Re: [SRU] libreoffice 7.3.7 updates for jammy
** Patch removed: "libreoffice_7.3.7-0ubuntu0.22.04.2.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+attachment/5642528/+files/libreoffice_7.3.7-0ubuntu0.22.04.2.patch ** Patch added: "libreoffice_7.3.7-0ubuntu0.22.04.2.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+attachment/561/+files/libreoffice_7.3.7-0ubuntu0.22.04.2.patch ** Description changed: [Impact] - * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 - https://wiki.documentfoundation.org/ReleasePlan/7.3 + * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 + https://wiki.documentfoundation.org/ReleasePlan/7.3 - * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 - * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) - https://bugs.documentfoundation.org/show_bug.cgi?id=150011 - * Fix bug in copying table where we need to create a primary key - * Don’t set language to none on defined styles (tdf#126657, tdf#145104) - https://bugs.documentfoundation.org/show_bug.cgi?id=126657 - https://bugs.documentfoundation.org/show_bug.cgi?id=145104 - * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) - https://bugs.documentfoundation.org/show_bug.cgi?id=150682 + * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 + * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) + https://bugs.documentfoundation.org/show_bug.cgi?id=150011 + * Fix bug in copying table where we need to create a primary key + * Don’t set language to none on defined styles (tdf#126657, tdf#145104) + https://bugs.documentfoundation.org/show_bug.cgi?id=126657 + https://bugs.documentfoundation.org/show_bug.cgi?id=145104 + [ * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) + https://bugs.documentfoundation.org/show_bug.cgi?id=150682 + DROPPED from this SRU ] [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra + Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch
[Desktop-packages] [Bug 2004554] [NEW] While using application switching in multi-tasking
Public bug reported: While switching workspace, the option : include applications from current workspace only is opted. The files founder does not switch properly. If opened in one workspace, and switched to another workspace. Then the dot ( that shoes finder is open) does not go away. And many more please check. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 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: ubuntu:GNOME Date: Thu Feb 2 16:47:24 2023 DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD Graphics 630] [1462:12aa] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106M [GeForce RTX 2060 Mobile] [1462:12aa] InstallationDate: Installed on 2021-05-11 (631 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. GF65 Thin 9SEXR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=f2aafeb8-65f1-4f53-a7f4-a8bac75a5fbd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-27 (6 days ago) dmi.bios.date: 10/21/2021 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16W1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-16W1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16W1IMS.10C:bd10/21/2021:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGF65Thin9SEXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16W1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16W1.1: dmi.product.family: GF dmi.product.name: GF65 Thin 9SEXR dmi.product.sku: 16W1.1 dmi.product.version: REV: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.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2004554 Title: While using application switching in multi-tasking Status in xorg package in Ubuntu: New Bug description: While switching workspace, the option : include applications from current workspace only is opted. The files founder does not switch properly. If opened in one workspace, and switched to another workspace. Then the dot ( that shoes finder is open) does not go away. And many more please check. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 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: ubuntu:GNOME Date: Thu Feb 2 16:47:24 2023 DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H
[Desktop-packages] [Bug 2004552] [NEW] Sound doesn't work on ASUS X670E-E motherboard.
Public bug reported: None of the outputs work for my digital optical output on my ASUS ROG STRIX X670E-E GAMING WIFI motherboard since updating the ALC4080/ALC4082 firmware. The issue is resolved in the upstream package of alsa-ucm-conf (https://github.com/alsa-project/alsa-ucm-conf). When I applied the newer configs sound started working again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 06:08:15 2023 InstallationDate: Installed on 2023-01-08 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- 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/2004552 Title: Sound doesn't work on ASUS X670E-E motherboard. Status in alsa-driver package in Ubuntu: New Bug description: None of the outputs work for my digital optical output on my ASUS ROG STRIX X670E-E GAMING WIFI motherboard since updating the ALC4080/ALC4082 firmware. The issue is resolved in the upstream package of alsa-ucm-conf (https://github.com/alsa-project/alsa-ucm-conf). When I applied the newer configs sound started working again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 06:08:15 2023 InstallationDate: Installed on 2023-01-08 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2004552/+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 2004475] Re: Archive type selection drop-down in archive creation window is clipped
Thank you for your bug report. The issue is https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 upstream and fixed in the current Ubuntu serie, there is also a fix in a newer 42 version. We will work on issuing a stable update including the fix ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2018 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2004475 Title: Archive type selection drop-down in archive creation window is clipped Status in nautilus package in Ubuntu: Fix Released Bug description: When you try to change type of the archive that you'd like to create the drop-down list is clipped from the left, which contains most important information about the type that you try to select. At the same time archive creation window has a fixed size and cannot be resized. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 16:40:30 2023 InstallationDate: Installed on 2020-11-24 (799 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2023-01-18 (14 days ago) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2004475/+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 1828581] Re: /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed
there hasn't been any report since 3.36 so it seems it has been fixed ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828581 Title: /usr/bin/gnome- calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828581/+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 2003335] Re: [SRU] libreoffice 7.3.7 updates for jammy
I think writing a custom patch would be way more fragile than going with an existing upstream solution. So I am going to drop the Alt+Shift+E patch from this SRU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2003335 Title: [SRU] libreoffice 7.3.7 updates for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.7 of the 7.3 is EOL since November 30, 2022 https://wiki.documentfoundation.org/ReleasePlan/7.3 * Cherry-picked patches mostly based on https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-7-3 * Switch default currency HRK Croatian Kuna to EUR Euro (tdf#150011) https://bugs.documentfoundation.org/show_bug.cgi?id=150011 * Fix bug in copying table where we need to create a primary key * Don’t set language to none on defined styles (tdf#126657, tdf#145104) https://bugs.documentfoundation.org/show_bug.cgi?id=126657 https://bugs.documentfoundation.org/show_bug.cgi?id=145104 * Change shortcut of inserting Math objects to Alt+Shift+E (tdf#150682) https://bugs.documentfoundation.org/show_bug.cgi?id=150682 [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14441847/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/amd64/libr/libreoffice/20230118_041112_1de9d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/arm64/libr/libreoffice/20230117_123847_1a3af@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/armhf/libr/libreoffice/20230117_105914_aa586@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/ppc64el/libr/libreoffice/20230117_111546_c7e43@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ricotz-ppa/jammy/s390x/libr/libreoffice/20230117_150924_08154@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003335/+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 1858368] Re: single-day events on 1st of month show on all days of preceding month
Upstream closed the bug with that note > I remember seeing something like this a long time ago, but haven't seen this in recent versions such as GNOME Calendar 43. Reopen if it still happens there. is anyone still seeing the issue in recent Ubuntu series? ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1858368 Title: single-day events on 1st of month show on all days of preceding month Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Single-day events on 1st of month show on all days of preceding month. For example, someone's birthday on April 1 will show up (in the month view) as being a month-long event during all of March. I am using a NextCloud calendar. The events look OK on the NextCloud web-based calendar, on my iphone, and on Mac's Calendar.app. Those same events appear fine in the week view... they are not stretched into the previous month. Alan Porter ubuntu-launch...@kr4jb.net ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 17:24:56 2020 InstallationDate: Installed on 2019-12-30 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1858368/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Package changed: snap (Ubuntu) => snapd (Ubuntu) ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also 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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004532/+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 2004534] Re: suspend does not work
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2004534 Title: suspend does not work Status in xorg package in Ubuntu: New Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2023-02-01 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: JTCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ABA7 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: dmi.product.family: IdeaPad 3 15ABA7 dmi.product.name: 82RN dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 dmi.product.version: IdeaPad 3 15ABA7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2004534/+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 2004534] [NEW] suspend does not work
You have been subscribed to a public bug: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2023-02-01 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: JTCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ABA7 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: dmi.product.family: IdeaPad 3 15ABA7 dmi.product.name: 82RN dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 dmi.product.version: IdeaPad 3 15ABA7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 -- suspend does not work https://bugs.launchpad.net/bugs/2004534 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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