[Desktop-packages] [Bug 2035300] Re: CVE-2023-4863: Heap buffer overflow in libwebp
Thank you for fixing this ♥ -- 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/2035300 Title: CVE-2023-4863: Heap buffer overflow in libwebp Status in firefox package in Ubuntu: Fix Released Bug description: Mozilla released a new version under https://www.mozilla.org/en- US/security/advisories/mfsa2023-40/ fixing a critical bug. $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy firefox firefox: Installiert: 1:1snap1-0ubuntu2 Installationskandidat: 1:1snap1-0ubuntu2 Versionstabelle: *** 1:1snap1-0ubuntu2 500 500 http://mirror.init7.net/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status As of now the latest version doesn't include this critical fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2035300/+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 2036298] Re: jammy: nautilus sidebar will not accept left mouse click actions in sidebar.
** Summary changed: - jammy: nautilus sidebat will not accept left mouse click actions in sidebar. + jammy: nautilus sidebar will not accept left mouse click actions in sidebar. -- 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/2036298 Title: jammy: nautilus sidebar will not accept left mouse click actions in sidebar. Status in nautilus package in Ubuntu: New Bug description: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2036298/+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 2036298] [NEW] jammy: nautilus sidebat will not accept left mouse click actions in sidebar.
Public bug reported: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Visual of issue" https://bugs.launchpad.net/bugs/2036298/+attachment/5701397/+files/Screencast%20from%2016-09-23%2003%3A44%3A18.webm -- 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/2036298 Title: jammy: nautilus sidebat will not accept left mouse click actions in sidebar. Status in nautilus package in Ubuntu: New Bug description: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2036298/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
** Attachment added: "logs crash event gnome" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968907/+attachment/5701368/+files/logs_crash_event_gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
** Attachment added: "logs for the gnome-session-binary blackout event" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968907/+attachment/5701367/+files/logs_gnome-session-binary-blackout-event -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Hello, I have been presenting this same issue and after doing some modifications now I have been working with no problems. On my experience I identified some factors that could lead to this behavior, although they might be or not involved: 1.- Using snap to service to download firefox, chromium, vlc, etc. I started notice some issues after installing some apps via snap, so for example in the logs there are reference to some orphan process or lost dependencies packages. 2.- Using wayland as the communication protocol. On my work I make a lot of screenshots and capture video, I did notice that after disable wayland I have no more problems with this error message. but i have only test for one day so, lets hope we keep working without this blackout I am uploading the logs and please notice that September 14th around 6:00 p.m. I disable wayland and then the logs send different logs error messages regarding the gnome-session. ** Attachment added: "Log events for the GLib-GIO-CRITICAL issue" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968907/+attachment/5701366/+files/GLib-GIO-CRITICAL.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+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 2036279] [NEW] Maximize shortcut does nothing
Public bug reported: I have Super+Up configured to maximize the current window, but it does nothing. I am running the Mantic pre-release. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 14:07:10 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-05 (498 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 45~rc-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-15 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages wayland-session -- 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/2036279 Title: Maximize shortcut does nothing Status in gnome-shell package in Ubuntu: New Bug description: I have Super+Up configured to maximize the current window, but it does nothing. I am running the Mantic pre-release. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 14:07:10 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-05 (498 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 45~rc-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036279/+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 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()
Triggered for me in 23.10 during routine system updates. Problem on two 23.10 VMs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2025531 Title: file-roller crashed with signal 5 in g_object_new_valist() Status in file-roller package in Ubuntu: Incomplete Bug description: While edubuntu-mantic parallel installing kubuntu kde-desktop ubuntucinnamon-desktop: E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings- desktop_1%3a23.04.5_all.deb: »/etc/skel/.face« tried to override because of desktop-base 12.0.6ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 14:35:45 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-07-01 (0 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629) ProcCmdline: /usr/bin/file-roller --service ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: My solution in synaptic was: uninstall kubuntu-desktop and kubuntu-settings-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+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 2036190] Re: fwupd running in WSL 2 in Ubuntu-22.04 fails to start
I think that this should be changed in gnome software not to try to start fwupd then when in WSL2. ** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2036190 Title: fwupd running in WSL 2 in Ubuntu-22.04 fails to start Status in gnome-software package in Ubuntu: New Bug description: The fwupd systemd service file contains "ConditionVirtualization=!container". This blocks fwupd from starting in WSL 2 Ubuntu-22.04 instance. Modifying the fwupd systemd service file to contain: # /etc/systemd/system/fwupd.service.d/override.conf [Unit] ConditionVirtualization= fixes this issue. WSL 2 is a light-weight utility VM, not a container. I noticed this issue when starting gnome-software. gnome-software output this error to the terminal: 09:48:20:0857 Gs plugin fwupd took 25.0 seconds to do setup 09:48:21:0461 PK failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:21:0462 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:46:0298 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) 09:48:46:0299 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action get-updates-historical: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Xpra Date: Fri Sep 15 13:01:49 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2036190/+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 2036190] [NEW] fwupd running in WSL 2 in Ubuntu-22.04 fails to start
You have been subscribed to a public bug: The fwupd systemd service file contains "ConditionVirtualization=!container". This blocks fwupd from starting in WSL 2 Ubuntu-22.04 instance. Modifying the fwupd systemd service file to contain: # /etc/systemd/system/fwupd.service.d/override.conf [Unit] ConditionVirtualization= fixes this issue. WSL 2 is a light-weight utility VM, not a container. I noticed this issue when starting gnome-software. gnome-software output this error to the terminal: 09:48:20:0857 Gs plugin fwupd took 25.0 seconds to do setup 09:48:21:0461 PK failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:21:0462 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid 09:48:46:0298 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) 09:48:46:0299 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark 09:48:46:0299 Gs not handling error failed for action get-updates-historical: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Xpra Date: Fri Sep 15 13:01:49 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- fwupd running in WSL 2 in Ubuntu-22.04 fails to start https://bugs.launchpad.net/bugs/2036190 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software 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
[Desktop-packages] [Bug 2036261] Re: Outdated alsa-ucm-conf with fresh install
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2036261 Title: Outdated alsa-ucm-conf with fresh install Status in alsa-driver package in Ubuntu: New Bug description: With a fresh install of Ubuntu 22.04 or 23.04 audio on the front panel of PC doesn't work. However if an aux cord is plugged in to "Line In" port on the motherboard, the front panel audio is rerouted to that port. I fixed it by downloading the updated alsa-ucm-conf and copying ucm and ucm2 folders from said directory into "/usr/share/alsa ". However, audio through the front panel is quieter than it should be. It seems Ubuntu uses an outdated version of alsa-ucm-conf with a fresh install. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 10:54:49 2023 InstallationDate: Installed on 2023-09-15 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H.70 dmi.board.asset.tag: Default string dmi.board.name: MAG Z690 TOMAHAWK WIFI (MS-7D32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.70:bd07/04/2022:br5.25:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFI(MS-7D32):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D32 dmi.product.sku: Default string dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2036261/+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 2035560] Re: CVE-2023-4863: Update Firefox in Ubuntu20.04
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4863 -- 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/2035560 Title: CVE-2023-4863: Update Firefox in Ubuntu20.04 Status in firefox package in Ubuntu: New Bug description: Hi, The Package on Focal hasn't been updated yet for the critical in the wild exploited Zero Day, it has been almost 2 days since the patched version 117.0.1 was released! But the Ubuntu package is still outdated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2035560/+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 2036261] [NEW] Outdated alsa-ucm-conf with fresh install
You have been subscribed to a public bug: With a fresh install of Ubuntu 22.04 or 23.04 audio on the front panel of PC doesn't work. However if an aux cord is plugged in to "Line In" port on the motherboard, the front panel audio is rerouted to that port. I fixed it by downloading the updated alsa-ucm-conf and copying ucm and ucm2 folders from said directory into "/usr/share/alsa ". However, audio through the front panel is quieter than it should be. It seems Ubuntu uses an outdated version of alsa-ucm-conf with a fresh install. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 10:54:49 2023 InstallationDate: Installed on 2023-09-15 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H.70 dmi.board.asset.tag: Default string dmi.board.name: MAG Z690 TOMAHAWK WIFI (MS-7D32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.70:bd07/04/2022:br5.25:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFI(MS-7D32):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D32 dmi.product.sku: Default string dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- Outdated alsa-ucm-conf with fresh install https://bugs.launchpad.net/bugs/2036261 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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
[Desktop-packages] [Bug 1640558] Re: 16.10 Backup Failure.
I have not seen this before. Is it possible it's an Out Of Memory error? duplicity 0.7.06 is ancient and Python2.7 has been End Of Life for a couple of years. I would suggest looking into upgrading to duplicity 1.2.3, which is the last version that will support Python2.7. The easiest way is to: $ sudo apt remove duplicity <--- do not skip this step $ sudo python -m pip install duplicity==1.2.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1640558 Title: 16.10 Backup Failure. Status in duplicity package in Ubuntu: Expired Bug description: A daily backup job run by corn invokes a script that runs duplicity. Since I have upgraded to 16.10 from 16.04 duplicity crashes with the message "killed". It seems that the real problem is in the NVIDIA driver for my screen. The machine does not crash in other situations. Some info Dell XPS 15 L502X, 15,6" FHD, NVIDIA GEFORCE GT 540M GR 2 GB NVIDIA driver version 367.57 X server version 11.0, server vendor version 1.18.4, NV-control version 1.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Thanks for the updates Nathan. As previously stated, running the unconfined binary /snap/chromium/current/usr/lib/chromium-browser/chrome or /snap/firefox/current/usr/lib/firefox/firefox prevents the GPU hang, ie using the system MESA library. Also disabling GPU acceleration via MESA environment variables confirms the hang is indeed related to GPU command queue submission from the MESA library. The GPU hang still occurs after "snap refresh --candidate gnome-42-2204" and rebooting to clear possible state, however I see /snap/chromium/2623/usr/lib/chromium-browser/libGLESv2.so, therefore surely the chromium snap needs the updated MESA library? -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
When I invoke thunar from my arm 32 bit chromeboo I have this error : (thunar:2313): GVFS-WARNING **: 13:49:56.399: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. I'm using ubuntu 22.04 for armhf and I'm connecting to the arm chromebook via ssh forwarding. Instead, thunar works if I run it directly on the chromebook. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+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 2033643] Re: [SRU] libreoffice 7.5.6 for lunar
Hello Rico, or anyone else affected, Accepted libreoffice into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.6-0ubuntu0.23.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- 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/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_75/1671/ * 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/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/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 minor release with a total of 53 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Committed ** Changed in: firefox (Ubuntu) Status: New => Fix Committed -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2036222] Re: simple scan does not find the scanner
After reboot (and using the printer?) simple-scan finds the scanner but
shut down GNOME shell: https://bugs.launchpad.net/ubuntu/+source/simple-
scan/+bug/2035793
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/2036222
Title:
simple scan does not find the scanner
Status in simple-scan package in Ubuntu:
New
Bug description:
simple scan does not find the scanner. Printer is working ok
corrado@corrado-n12-mm-0915:~$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:2016: Starting simple-scan 44.0, PID=13648
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will
deadlock if server is GDBus < 2.73.3)
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation gvfs
(GDaemonVfs) for ‘gio-vfs’
[+0.06s] DEBUG: Using style
/org/gnome/Adwaita/styles/defaults-light-yaru-default.css
[+0.07s] DEBUG: app-window.vala:1436: Loading state from
/home/corrado/.config/simple-scan/state
[+0.07s] DEBUG: app-window.vala:1415: Restoring window to 600x480 pixels
[+0.14s] DEBUG: scanner.vala:1619: sane_init () -> SANE_STATUS_GOOD
[+0.14s] DEBUG: scanner.vala:1625: SANE version 1.2.1
[+0.14s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices
[+0.14s] DEBUG: scanner.vala:863: Processing request
[+0.25s] DEBUG: app-window.vala:1512: Saving state to
/home/corrado/.config/simple-scan/state
[+7.64s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD
[+7.64s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices
[+7.64s] DEBUG: scanner.vala:863: Processing request
[+7.75s] DEBUG: app-window.vala:1512: Saving state to
/home/corrado/.config/simple-scan/state
[+12.96s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD
corrado@corrado-n12-mm-0915:~$ lsusb
Bus 004 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573
Wireless Adapter
Bus 003 Device 004: ID 03f0:674a HP, Inc HP 100 USB Optical Mouse
Bus 003 Device 002: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 03f0:c911 HP, Inc Officejet 2620 series
Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-n12-mm-0915:~$
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: simple-scan 44.0+git20230905-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 13:43:10 2023
InstallationDate: Installed on 2023-09-15 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=6489c299-a498-4313-b0f5-82bf9d0684a8 ro quiet splash vt.handoff=7
SimpleScanLog:
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2022
dmi.bios.release: 14.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H610M-E D4
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.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4: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/simple-scan/+bug/2036222/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to
[Desktop-packages] [Bug 2036229] [NEW] i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #5
Public bug reported: This bug report is a duplicate of: Bug #2020183: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state. This time the displays connected to the Docking station remain black after some lockscreen unlocks. First time the DP-2-1 remain black (connected with native HDMI cable from the docking station), last time the DP-2-2-2 remain black (connected with native DP cable from the DS). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 15 14:53:36 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (14 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-01T15:03:36.827625 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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 -- 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/2036229 Title: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #5 Status in xorg package in Ubuntu: New Bug description: This bug report is a duplicate of: Bug #2020183: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state. This time the displays connected to the Docking station remain black after some lockscreen unlocks. First time the DP-2-1 remain black (connected with native HDMI cable from the docking station), last time the DP-2-2-2 remain black (connected with native DP cable from the DS). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 15 14:53:36 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (14 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh
[Desktop-packages] [Bug 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+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 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()
Triggered for me in 23.10 during routine system updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2025531 Title: file-roller crashed with signal 5 in g_object_new_valist() Status in file-roller package in Ubuntu: Incomplete Bug description: While edubuntu-mantic parallel installing kubuntu kde-desktop ubuntucinnamon-desktop: E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings- desktop_1%3a23.04.5_all.deb: »/etc/skel/.face« tried to override because of desktop-base 12.0.6ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 14:35:45 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-07-01 (0 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629) ProcCmdline: /usr/bin/file-roller --service ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: My solution in synaptic was: uninstall kubuntu-desktop and kubuntu-settings-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+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 2036222] [NEW] simple scan does not find the scanner
Public bug reported:
simple scan does not find the scanner. Printer is working ok
corrado@corrado-n12-mm-0915:~$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:2016: Starting simple-scan 44.0, PID=13648
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will
deadlock if server is GDBus < 2.73.3)
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation gvfs
(GDaemonVfs) for ‘gio-vfs’
[+0.06s] DEBUG: Using style
/org/gnome/Adwaita/styles/defaults-light-yaru-default.css
[+0.07s] DEBUG: app-window.vala:1436: Loading state from
/home/corrado/.config/simple-scan/state
[+0.07s] DEBUG: app-window.vala:1415: Restoring window to 600x480 pixels
[+0.14s] DEBUG: scanner.vala:1619: sane_init () -> SANE_STATUS_GOOD
[+0.14s] DEBUG: scanner.vala:1625: SANE version 1.2.1
[+0.14s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices
[+0.14s] DEBUG: scanner.vala:863: Processing request
[+0.25s] DEBUG: app-window.vala:1512: Saving state to
/home/corrado/.config/simple-scan/state
[+7.64s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD
[+7.64s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices
[+7.64s] DEBUG: scanner.vala:863: Processing request
[+7.75s] DEBUG: app-window.vala:1512: Saving state to
/home/corrado/.config/simple-scan/state
[+12.96s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD
corrado@corrado-n12-mm-0915:~$ lsusb
Bus 004 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573
Wireless Adapter
Bus 003 Device 004: ID 03f0:674a HP, Inc HP 100 USB Optical Mouse
Bus 003 Device 002: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 03f0:c911 HP, Inc Officejet 2620 series
Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-n12-mm-0915:~$
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: simple-scan 44.0+git20230905-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 13:43:10 2023
InstallationDate: Installed on 2023-09-15 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=6489c299-a498-4313-b0f5-82bf9d0684a8 ro quiet splash vt.handoff=7
SimpleScanLog:
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2022
dmi.bios.release: 14.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H610M-E D4
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.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4: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: simple-scan (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/2036222
Title:
simple scan does not find the scanner
Status in simple-scan package in Ubuntu:
New
Bug description:
simple scan does not find the scanner. Printer is working ok
corrado@corrado-n12-mm-0915:~$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:2016: Starting simple-scan 44.0, PID=13648
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.00s] DEBUG: Using cross-namespace E
[Desktop-packages] [Bug 2036197] [NEW] Metacity crashes inside xfce4, x2go session
Public bug reported: Ubuntu 22.04 (Jammy) Metacity 3.44.0 Metacity crashes when used on xfce4 session. patch: https://gitlab.gnome.org/GNOME/metacity/-/commit/adc3d81ad21ada80d10e3517ca307fc95d0d97cc ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2036197 Title: Metacity crashes inside xfce4, x2go session Status in metacity package in Ubuntu: New Bug description: Ubuntu 22.04 (Jammy) Metacity 3.44.0 Metacity crashes when used on xfce4 session. patch: https://gitlab.gnome.org/GNOME/metacity/-/commit/adc3d81ad21ada80d10e3517ca307fc95d0d97cc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2036197/+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 2036187] Re: gnome-shell crashed with signal 5 in g_log_structured_array()
*** This bug is a duplicate of bug 2034672 *** https://bugs.launchpad.net/bugs/2034672 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2034672, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2036187/+attachment/5701206/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701208/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701212/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701213/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701214/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701216/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2036187/+attachment/5701217/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 2034672 gnome-shell crashed with GLXBadDrawable on startup in a Xorg session ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/2036187 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: this bug appeared in 23.10 when booting the live disk image. daily build of 15th of September at 12:52PM Eastern Europe Time ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 09:48:16 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036187/+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 2035603] Re: Duplicity 1.2.2-1 fails to build from source
This bug was fixed in the package duplicity - 1.2.2-1ubuntu1
---
duplicity (1.2.2-1ubuntu1) mantic; urgency=medium
* Fix failure to build from source with new setuptools (LP: #2035603):
- d/p/08-packages: test.overrides{,.bin} are specified as separate
packages so their files are correctly included.
- d/rules: Cherry pick missing files and remove unwanted locale ones.
-- Nathan Pratta Teodosio Fri, 15 Sep
2023 09:23:08 +0200
** Changed in: duplicity (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/2035603
Title:
Duplicity 1.2.2-1 fails to build from source
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic-
amd64.duplicity_1.2.2-1_BUILDING.txt.gz
For the record this builds fine with the latest upstream release
setup.py so I'm not poking them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Confirmed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Thank for the advice. Revised patch to generate 0.9.6.2~0.22.04.6
** Patch added: "jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5701201/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.6.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Confirmed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Upload the patch for lunar
** Patch added: "lunar-0.9.7.1.1__0.9.7.1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5701202/+files/lunar-0.9.7.1.1__0.9.7.1.2.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Confirmed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2035603] Re: Duplicity 1.2.2-1 fails to build from source
Thanks Nathan, uploaded ** Changed in: duplicity (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Fix Committed Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz For the record this builds fine with the latest upstream release setup.py so I'm not poking them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 2036159] Re: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4
*** This bug is a duplicate of bug 2020183 *** https://bugs.launchpad.net/bugs/2020183 ** This bug has been marked a duplicate of bug 2020183 i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state -- 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/2036159 Title: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4 Status in xorg package in Ubuntu: New Bug description: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 15 07:25:50 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-01T15:03:36.827625 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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/2036159/+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 2036160] Re: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #3
*** This bug is a duplicate of bug 2020183 *** https://bugs.launchpad.net/bugs/2020183 ** This bug has been marked a duplicate of bug 2036159 i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4 ** This bug is no longer a duplicate of bug 2036159 i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4 ** This bug has been marked a duplicate of bug 2020183 i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state -- 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/2036160 Title: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #3 Status in xorg package in Ubuntu: New Bug description: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Sep 12 06:36:27 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (10 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-01T15:03:36.827625 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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/2036160/+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 2036159] [NEW] i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4
Public bug reported: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 15 07:25:50 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-01T15:03:36.827625 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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 -- 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/2036159 Title: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #4 Status in xorg package in Ubuntu: New Bug description: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 15 07:25:50 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB
[Desktop-packages] [Bug 2036160] [NEW] i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #3
Public bug reported: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Sep 12 06:36:27 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (10 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-01T15:03:36.827625 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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 -- 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/2036160 Title: i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state #3 Status in xorg package in Ubuntu: New Bug description: Possibly another duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020183 with different logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Sep 12 06:36:27 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] [103c:8846] InstallationDate: Installed on 2023-09-01 (10 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/elx_vg-root ro audit=0 noquiet nosplash sysrq_always_enable SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family:
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
The problem still persists in Ubuntu 22.04.3. Whether the problem appears depends on whether the Calendar application was open or not. If the Calendar has not been opened in the current session and I click on a specific day, everything works correctly. However, if the Calendar has been opened before, the error described above occurs: the calendar in the panel collapses and does not open the Calendar application. If I manually stop the gnome-calendar-service after the error occurs, the calendar in the panel will then be fixed again and will be clickable again until the next time the Calendar application is opened. -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.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.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970800/+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 2035220] Re: cve-2023-4863
libwebp also released (USN-6369-1)
** Changed in: firefox-esr (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: libwebp (Ubuntu)
Status: Confirmed => Fix Released
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
Fix Released
Status in libwebp package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Fix Released
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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
