[Desktop-packages] [Bug 2064099] Re: Quickly switching right and left clicks freezes Nautilus
Disabling the extension didn't solve the issue. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064099/+attachment/5772876/+files/journal.txt -- 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/2064099 Title: Quickly switching right and left clicks freezes Nautilus Status in mutter package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Bug description: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064099/+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 2064099] [NEW] Quickly switching right and left clicks freezes Nautilus
Public bug reported: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Description changed: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens - every time you do this. + every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: - b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" - b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' + b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" + b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: - file-roller 44.1-1 - nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 + file-roller 44.1-1 + nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 -- 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/2064099 Title: Quickly switching right and left clicks freezes Nautilus Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064099/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
How can I get this fix in 24.04? -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2056772] Re: Properties of Audio Files Causes Lock Ups
It happens with local files too but not all of them. -- 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/2056772 Title: Properties of Audio Files Causes Lock Ups Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: On SMB mounted file systems, right click properties on audio files causes the Nautilus to freeze. Force/Wait appears. The file system has read/write permission. Happens every time for large .flac files. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46~beta-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 10:33:22 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'recursive-search' b"'always'" b'org.gnome.nautilus.preferences' b'show-directory-item-counts' b"'always'" b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1241, 1039)' InstallationDate: Installed on 2022-04-07 (704 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.51.90-1ubuntu1 nautilus-share0.7.5-0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2056772/+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 2063935] [NEW] Getting the properties of some files freezes Nautilus
Public bug reported: When getting the properties of some files, this case it's an mp3 file, nautilus freezes and have to force kill it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 13:33:25 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (36 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (16 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Attachment added: "nautilus_debug.log" https://bugs.launchpad.net/bugs/2063935/+attachment/5771455/+files/nautilus_debug.log -- 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/2063935 Title: Getting the properties of some files freezes Nautilus Status in nautilus package in Ubuntu: New Bug description: When getting the properties of some files, this case it's an mp3 file, nautilus freezes and have to force kill it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 13:33:25 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (36 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (16 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063935/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
https://errors.ubuntu.com/user/2b93ad219b48c9b97a7a077caec6d69c0c1775edbb7ed9adc197eb0f82ef67bad56000432096446e2a08ce86802994b7d7974a33972dece2b7b97ff663da8f05 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "prevjournal-2.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770844/+files/prevjournal-2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "prevjournal-1.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770843/+files/prevjournal-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770842/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] [NEW] Sometimes gnome-shell crash upon unlocking session from suspension
Public bug reported: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]:
[Desktop-packages] [Bug 2061949] Re: nouveau error
I also noticed this crash just before the Xwayland error: [ 108.391556] [ cut here ] [ 108.391560] WARNING: CPU: 7 PID: 6474 at kernel/workqueue.c:1790 __queue_work.part.0+0x30c/0x3e0 [ 108.391570] Modules linked in: uhid vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm rfcomm snd_seq_dummy snd_hrtimer cmac algif_hash algif_skcipher af_alg qrtr bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes snd_soc_intel_hda_dsp_common snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda xt_multiport snd_hda_ext_core xt_tcpudp snd_soc_acpi_intel_match snd_soc_acpi xe xt_conntrack soundwire_generic_allocation soundwire_bus nf_conntrack nf_defrag_ipv6 snd_soc_core nf_defrag_ipv4 nft_compat snd_compress ac97_bus nf_tables snd_pcm_dmaengine drm_suballoc_helper binfmt_misc libcrc32c snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_uncore_frequency snd_hda_core intel_uncore_frequency_common intel_tcc_cooling nouveau nls_iso8859_1 snd_hw dep x86_pkg_temp_thermal snd_pcm [ 108.391611] intel_powerclamp i915 snd_seq_midi snd_seq_midi_event btusb drm_gpuvm btrtl uvcvideo coretemp processor_thermal_device_pci_legacy snd_rawmidi drm_exec iwlmvm btintel cmdlinepart videobuf2_vmalloc processor_thermal_device kvm_intel gpu_sched snd_seq btbcm uvc spi_nor processor_thermal_wt_hint videobuf2_memops snd_seq_device drm_ttm_helper drm_buddy btmtk mac80211 videobuf2_v4l2 mfd_aaeon asus_nb_wmi mei_hdcp mei_pxp mtd intel_rapl_msr libarc4 snd_timer kvm processor_thermal_rfim asus_wmi videodev bluetooth ttm iwlwifi processor_thermal_rapl irqbypass ledtrig_audio snd drm_display_helper intel_rapl_common videobuf2_common sparse_keymap rapl spi_intel_pci mei_me ecdh_generic i2c_i801 mc intel_cstate ecc platform_profile wmi_bmof mxm_wmi cec soundcore spi_intel processor_thermal_wt_req i2c_smbus cfg80211 mei rc_core processor_thermal_power_floor processor_thermal_mbox i2c_algo_bit igen6_edac intel_soc_dts_iosf int3403_thermal intel_pmc_core int340x_thermal_zone int3400_th ermal intel_vsec acpi_thermal_rel [ 108.391665] pmt_telemetry joydev input_leds pmt_class acpi_pad acpi_tad mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 usbhid dm_crypt nvme hid_multitouch nvme_core hid_generic nvme_auth crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel intel_lpss_pci rtsx_pci_sdmmc sha256_ssse3 i2c_hid_acpi intel_lpss ucsi_acpi sha1_ssse3 xhci_pci thunderbolt i2c_hid rtsx_pci video vmd idma64 typec_ucsi xhci_pci_renesas typec hid wmi pinctrl_tigerlake aesni_intel crypto_simd cryptd [ 108.391701] CPU: 7 PID: 6474 Comm: Xwayland Tainted: G O 6.8.0-22-generic #22-Ubuntu [ 108.391703] Hardware name: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG/UX435EG, BIOS UX435EG.315 04/22/2022 [ 108.391705] RIP: 0010:__queue_work.part.0+0x30c/0x3e0 [ 108.391709] Code: 4c 8b 30 49 89 c7 49 39 fe 0f 84 5a fe ff ff 0f 0b e9 53 fe ff ff 65 8b 3d cd df b0 54 e8 3c c0 ff ff 89 45 d0 e9 23 fd ff ff <0f> 0b e9 e2 fe ff ff 48 8b 0b 44 89 e0 49 8d 57 68 83 c8 07 83 e1 [ 108.391711] RSP: 0018:b10c894b3818 EFLAGS: 00010082 [ 108.391713] RAX: RBX: 951d37d1f4c0 RCX: [ 108.391714] RDX: RSI: RDI: [ 108.391715] RBP: b10c894b3850 R08: R09: [ 108.391716] R10: R11: R12: 2000 [ 108.391717] R13: 951d37d1f4c8 R14: 9520877b4500 R15: 951d001df200 [ 108.391718] FS: 7142ceae08c0() GS:95208778() knlGS: [ 108.391720] CS: 0010 DS: ES: CR0: 80050033 [ 108.391721] CR2: 7889cbf77000 CR3: 00015f1fa006 CR4: 00f70ef0 [ 108.391723] PKRU: 5554 [ 108.391724] Call Trace: [ 108.391726] [ 108.391730] ? show_regs+0x6d/0x80 [ 108.391733] ? __warn+0x89/0x160 [ 108.391736] ? __queue_work.part.0+0x30c/0x3e0 [ 108.391739] ? report_bug+0x17e/0x1b0 [ 108.391742] ? handle_bug+0x51/0xa0 [ 108.391746] ? exc_invalid_op+0x18/0x80 [ 108.391749] ? asm_exc_invalid_op+0x1b/0x20 [ 108.391755] ? __queue_work.part.0+0x30c/0x3e0 [ 108.391758] ? __queue_work.part.0+0xf7/0x3e0 [ 108.391760] ? __pfx_pci_pm_runtime_resume+0x10/0x10 [ 108.391764] __queue_work+0x36/0xa0 [ 108.391767] queue_work_on+0x67/0x70 [ 108.391771] nouveau_display_hpd_resume+0x49/0x60 [nouveau] [ 108.391897] nouveau_pmops_runtime_resume+0xef/0x1a0 [nouveau] [ 108.391986] pci_pm_runtime_resume+0xa0/0x100 [ 108.391989] __rpm_callback+0x4d/0x170 [ 108.391992] rpm_callback+0x6d/0x80 [ 108.391993] ? __pfx_pci_pm_runtime_resume+0x10/0x10 [
[Desktop-packages] [Bug 2039543] Re: Miss placed Hexchat icon when switching workspaces
And it's still happening in the latest 24.04 beta for many apps that are in the app indicator. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 2062538] [NEW] Clicking the top bar shows desktop icons above app window
Public bug reported: Sometimes when slowly double clicking the top bar while an app window is maximized, the desktop icons appear above the app and disappears as shown in the attached screen-cast. I also believe that app windows should not be handled from the top bar, like you shouldn't grab it to restore from being maximized; this should should be effective from the app window title bar only! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 13:06:43 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (28 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (8 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Attachment added: "Screencast from 2024-04-19 13-05-38.webm" https://bugs.launchpad.net/bugs/2062538/+attachment/5768158/+files/Screencast%20from%202024-04-19%2013-05-38.webm ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Description changed: Sometimes when slowly double clicking the top bar while an app window is maximized, the desktop icons appear above the app and disappears as shown in the attached screen-cast. + + I also believe that app windows should not be handled from the top bar, + like you shouldn't grab it to restore from being maximized; this should + should be effective from the app window title bar only! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 13:06:43 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (28 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (8 days ago) -- 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/2062538 Title: Clicking the top bar shows desktop icons above app window Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Sometimes when slowly double clicking the top bar while an app window is maximized, the desktop icons appear above the app and disappears as shown in the attached screen-cast. I also believe that app windows should not be handled from the top bar, like you shouldn't grab it to restore from being maximized; this should should be effective from the app window title bar only! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 13:06:43 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (28 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2062538/+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 2021956] Re: crash cups-proxyd
Still happening in 24.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: Confirmed Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Please share the link to the commit code. Usually how long it takes after a commit is pushed until the new package is available for upgrade in the repo? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Committed Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2061915] [NEW] While upgrading python3 package gives error
Public bug reported:
While upgrading the python3 package, it gave these errors:
Setting up python3 (3.12.3-0ubuntu1) ...
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence
'\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence
'\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence
'\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
/usr/lib/kitty/kitty/options/definition.py:4116: SyntaxWarning: invalid escape
sequence '\e'
long_text='''
/usr/lib/rhythmbox/plugins/alternative-toolbar/alttoolbar_plugins.py:171:
SyntaxWarning: invalid escape sequence '\('
translation = re.sub('\(..\)', '', translation, flags=re.DOTALL)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:97:
SyntaxWarning: invalid escape sequence '\/'
lyrics = re.split('()(.*)(<\/font>http://jetlyrics\.com/viewlyrics\.php\?id=[0-9]*)\'>', result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/JlyricParser.py:49:
SyntaxWarning: invalid escape sequence '\.'
m = re.search('',
result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/TerraParser.py:39:
SyntaxWarning: invalid escape sequence '\w'
pattern = re.compile("&(#?\w+?);")
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/WinampcnParser.py:87:
SyntaxWarning: invalid escape sequence '\['
lrcplaintext = re.sub('\[.*?\]', '', lrcplaintext)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44: SyntaxWarning:
invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
running python post-rtupdate hooks for python3.12...
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3 3.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 00:38:58 2024
InstallationDate: Installed on 2024-03-22 (25 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
** Also affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2061915
Title:
While upgrading python3 package gives error
Status in python3-defaults package in Ubuntu:
New
Status in rhythmbox package in Ubuntu:
New
Bug description:
While upgrading the python3 package, it gave these errors:
[Desktop-packages] [Bug 2061916] [NEW] Seahorse asks to unlock the keyring every time after login
Public bug reported: After upgrading from 23.10 to 24.10 beta, every time I login it ask me to unlock the default keyring. I set the keyring password same as my user's password but still. Please check the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: seahorse 43.0-3build2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 00:40:48 2024 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/2061916 Title: Seahorse asks to unlock the keyring every time after login Status in seahorse package in Ubuntu: New Bug description: After upgrading from 23.10 to 24.10 beta, every time I login it ask me to unlock the default keyring. I set the keyring password same as my user's password but still. Please check the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: seahorse 43.0-3build2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 00:40:48 2024 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2061916/+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 2061827] [NEW] Resizing app window can trigger tilling highlighter
Public bug reported: Sometimes when resizing apps windows, it show the tilling highlighter as shown in the screenshot and it stays like that until you try to tile a window manually. It's only a view but you can still click what's behind it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 13:28:07 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Attachment added: "Screenshot from 2024-04-16 13-27-10.png" https://bugs.launchpad.net/bugs/2061827/+attachment/5766118/+files/Screenshot%20from%202024-04-16%2013-27-10.png ** Description changed: - Sometimes when resizing apps windows, it show the tilling highlighter as shown in the screenshot. - It only a view but you can still click what's behind it. + Sometimes when resizing apps windows, it show the tilling highlighter as + shown in the screenshot and it stays like that until you try to tile a + window manually. + + It's only a view but you can still click what's behind it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 13:28:07 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) -- 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/2061827 Title: Resizing app window can trigger tilling highlighter Status in gnome-shell package in Ubuntu: New Bug description: Sometimes when resizing apps windows, it show the tilling highlighter as shown in the screenshot and it stays like that until you try to tile a window manually. It's only a view but you can still click what's behind it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 13:28:07 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061827/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I have also faced the issue ... Same manner. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half our to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2061285] [NEW] Snapshot cannot detect laptop camera
Public bug reported: It say no camera found, while the Cheese app can detect it fine. # lsusb Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:31:16 2024 InstallationDate: Installed on 2024-03-22 (23 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-snapshot UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago) ** Affects: gnome-snapshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Description changed: It say no camera found, while the Cheese app can detect it fine. + + # lsusb + Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam + ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:31:16 2024 InstallationDate: Installed on 2024-03-22 (23 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: gnome-snapshot UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-snapshot in Ubuntu. https://bugs.launchpad.net/bugs/2061285 Title: Snapshot cannot detect laptop camera Status in gnome-snapshot package in Ubuntu: New Bug description: It say no camera found, while the Cheese app can detect it fine. # lsusb Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:31:16 2024 InstallationDate: Installed on 2024-03-22 (23 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-snapshot UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-snapshot/+bug/2061285/+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 2055804] [NEW] Choosing font
Public bug reported: Hello, I want to choosing best fonts from my collection in easy way. ~/.fonts$ find . -type f |wc -l 11196 I have +1 fonts, Arabic & English. I can not comparing between fonts . More than 50% of Arabic fonts are not working (some of them were worked in 7.10). There is not grouping or sorting by language , (I can see some sorting in Open Office Writer - character ...) Some system & applications hanging if I add all of them (8g ram + swap 16g) I can not grouping them or selecting some of them to viewing & others to hide in easy way !. I can not know wich of them are working & wich are not working to removing or fixing !. Some Applications access to .fonts & change some of files (FireFox or other?) , I know that by rsync files. I can not view 0 as number , Not as O or o. Some fonts can not displayed as before. I can not found package deb to install all necessary package for Arabic fonts & English & Viewing 0. Almost I use TrueType fonts were working in WindowsXP. I need help. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Mar 3 09:49:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] InstallationDate: Installed on 2023-08-21 (194 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=31f7c266-8d08-49d3-9846-5083e162dc40 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu third-party-packages 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/2055804 Title: Choosing font Status in xorg package in Ubuntu: New Bug description: Hello, I want to choosing best fonts from my collection in easy way. ~/.fonts$ find . -type f |wc -l 11196 I have +1 fonts, Arabic & English. I can not comparing between fonts . More than 50% of Arabic fonts are not working (some of them were worked in 7.10). There is not grouping or sorting by language , (I can see some sorting in Open Office Writer - character ...) Some system & applications hanging if I add all of them (8g ram + swap 16g) I can not grouping them or selecting some of them to viewing & others to hide in easy way !. I can not know wich of them are working & wich are not working to removing or fixing !. Some Applications access to .fonts & change some of files (FireFox or other?) , I know that by rsync files. I can not view 0 as number , Not as O or o. Some fonts can not displayed as before. I can not found package deb to install all necessary package for Arabic fonts & English & Viewing 0. Almost I use TrueType fonts were working in WindowsXP. I need help. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package:
[Desktop-packages] [Bug 2055233] [NEW] [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all
Public bug reported: sound work if rechanging to Analog Stereo Duplex. but after sound file finish it broken again ! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu6 ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3 Uname: Linux 6.6.0-14-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 28 02:39:07 2024 InstallationDate: Installed on 2024-01-12 (46 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) MachineType: MSI MS-7850 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2055233 Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: sound work if rechanging to Analog Stereo Duplex. but after sound file finish it broken again ! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu6 ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3 Uname: Linux 6.6.0-14-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 28 02:39:07 2024 InstallationDate: Installed on 2024-01-12 (46 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) MachineType: MSI MS-7850 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055233/+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 2054302] [NEW] [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] Playback problem
Public bug reported: Hello, I want to someone to solve this problem in beta Kubuntu 24.04. If sound level controler added to system-panel in taskbar , sound go off. And slowing down all system. without any sound. I can fix it by change card mode "Analog Stereo Duplex" to any thing then return back to "Analog Stereo Duplex". it will work OK for current played sound then broken!. this happen after last update. Than You ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Feb 19 13:57:20 2024 InstallationDate: Installed on 2024-01-12 (38 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2054302 Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Hello, I want to someone to solve this problem in beta Kubuntu 24.04. If sound level controler added to system-panel in taskbar , sound go off. And slowing down all system. without any sound. I can fix it by change card mode "Analog Stereo Duplex" to any thing then return back to "Analog Stereo Duplex". it will work OK for current played sound then broken!. this happen after last update. Than You ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Feb 19 13:57:20 2024 InstallationDate: Installed on 2024-01-12 (38 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2054302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2051194] [NEW] Xorg freeze
Public bug reported:
Hello,
Keyboard hanging when long press SHIFT. (Microsoft curve 3000)
Can fixing that by using another keyboard (shft+alt F3 then back to current).
(wireless keyboard)
Thank you
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3
Uname: Linux 6.6.0-14-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jan 25 08:36:15 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.6.0-14-generic, x86_64: installed
bbswitch/0.8, 6.6.0-14-lowlatency, x86_64: installed
virtualbox/7.0.14, 6.6.0-14-lowlatency, x86_64: installed
ExtraDebuggingInterest: No
GpuHangFrequency: I don't know
GraphicsCard:
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller [1462:7850]
InstallationDate: Installed on 2024-01-12 (13 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-lowlatency
root=UUID=bced7c56-1cd5-4190-9ca2-31af67de9bd3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85-G41 PC Mate(MS-7850)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7850
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.117-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.3-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
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 freeze has-workaround kubuntu noble reproducible
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/2051194
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Hello,
Keyboard hanging when long press SHIFT. (Microsoft curve 3000)
Can fixing that by using another keyboard (shft+alt F3 then back to current).
(wireless keyboard)
Thank you
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3
Uname: Linux 6.6.0-14-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jan 25 08:36:15 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.6.0-14-generic, x86_64: installed
bbswitch/0.8, 6.6.0-14-lowlatency, x86_64: installed
virtualbox/7.0.14, 6.6.0-14-lowlatency, x86_64: installed
ExtraDebuggingInterest: No
GpuHangFrequency: I don't know
GraphicsCard:
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller [1462:7850]
InstallationDate: Installed on 2024-01-12 (13 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-lowlatency
root=UUID=bced7c56-1cd5-4190-9ca2-31af67de9bd3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 2021956] Re: crash cups-proxyd
I'm getting this error on 23.10: cups-proxyd[2415]: segfault at 18 ip 55efd95e6d75 sp 7ffc3ee0d810 error 4 in cups-proxyd[55efd95e3000+7000] likely on CPU 1 (core 1, socket 0) ** Changed in: cups (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: New Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2042715] [NEW] gpu-manager service takes 10 seconds during boot
Public bug reported: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042715 Title: gpu-manager service takes 10 seconds during boot Status in ubuntu-meta package in Ubuntu: New Bug description: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042715/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Also affects: gnome-shell-extension-appindicator Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 2039547] [NEW] Desktop icons appear on external monitor not the primary one
Public bug reported: When plugging external monitor, the desktop icons are placed on it not the primary display of the laptop even when trying to arrange icons. Please check the attached screenshot for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.5-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:25:50 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "signal-2023-10-17-115451.jpeg" https://bugs.launchpad.net/bugs/2039547/+attachment/5710258/+files/signal-2023-10-17-115451.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2039547 Title: Desktop icons appear on external monitor not the primary one Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: When plugging external monitor, the desktop icons are placed on it not the primary display of the laptop even when trying to arrange icons. Please check the attached screenshot for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.5-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:25:50 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2039547/+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 2039543] [NEW] Miss placed Hexchat icon when switching workspaces
Public bug reported: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast from 2023-10-17 11-12-00.webm" https://bugs.launchpad.net/bugs/2039543/+attachment/5710251/+files/Screencast%20from%202023-10-17%2011-12-00.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2039543/+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 2017341] Re: Can toggle Hexchat App Indicator from remote location
** Description changed: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself, and will prevent from closing a browser tab for the first click. + + This happen even if the AppIndicator extension is disabled. Also the app indicator icon appears temporary scaled while switching workspaces. Please see the attached screencasts of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017341 Title: Can toggle Hexchat App Indicator from remote location Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself, and will prevent from closing a browser tab for the first click. This happen even if the AppIndicator extension is disabled. Also the app indicator icon appears temporary scaled while switching workspaces. Please see the attached screencasts of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017341] Re: Can toggle Hexchat App Indicator from remote location
** Attachment added: "Screencast from 2023-04-23 11-55-57.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+attachment/5667188/+files/Screencast%20from%202023-04-23%2011-55-57.webm ** Description changed: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself, and will prevent from closing a browser tab for the first click. - Please see the attached screencast of illustration. + Also the app indicator icon appears temporary scaled while switching + workspaces. + + Please see the attached screencasts of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017341 Title: Can toggle Hexchat App Indicator from remote location Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself, and will prevent from closing a browser tab for the first click. Also the app indicator icon appears temporary scaled while switching workspaces. Please see the attached screencasts of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017376] Re: App window is moved behind the dock and top bar
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2017376 Title: App window is moved behind the dock and top bar Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Randomly or sometimes after resuming for sleep, any app window will move to the top-left and goes behind the top bar of gnome-shell and behind the Ubuntu dock as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 00:43:44 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (108 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017376] Re: App window is moved behind the dock and top bar
** Attachment added: "Screenshot from 2023-03-29 13-12-34.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+attachment/5666967/+files/Screenshot%20from%202023-03-29%2013-12-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2017376 Title: App window is moved behind the dock and top bar Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Randomly or sometimes after resuming for sleep, any app window will move to the top-left and goes behind the top bar of gnome-shell and behind the Ubuntu dock as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 00:43:44 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (108 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017376] [NEW] App window is moved behind the dock and top bar
Public bug reported: Randomly or sometimes after resuming for sleep, any app window will move to the top-left and goes behind the top bar of gnome-shell and behind the Ubuntu dock as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 00:43:44 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (108 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2017376 Title: App window is moved behind the dock and top bar Status in gnome-shell package in Ubuntu: New Bug description: Randomly or sometimes after resuming for sleep, any app window will move to the top-left and goes behind the top bar of gnome-shell and behind the Ubuntu dock as shown in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 00:43:44 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (108 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017341] Re: Can toggle Hexchat App Indicator from remote location
** Description changed: - If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself. + If I clicked on the title bar of opened window right under the Hexchat + app indicator, it will toggle the appearance of Hexchat window as if + clicking on the app indicator icon itself, and will prevent from closing + a browser tab for the first click. + Please see the attached screencast of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017341 Title: Can toggle Hexchat App Indicator from remote location Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself, and will prevent from closing a browser tab for the first click. Please see the attached screencast of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017341] Re: Can toggle Hexchat App Indicator from remote location
** Attachment added: "Screencast from 2023-04-22 11-51-53.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+attachment/5666780/+files/Screencast%20from%202023-04-22%2011-51-53.webm ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New -- 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/2017341 Title: Can toggle Hexchat App Indicator from remote location Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself. Please see the attached screencast of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017341] [NEW] Can toggle Hexchat App Indicator from remote location
Public bug reported: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself. Please see the attached screencast of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2017341 Title: Can toggle Hexchat App Indicator from remote location Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If I clicked on the title bar of opened window right under the Hexchat app indicator, it will toggle the appearance of Hexchat window as if clicking on the app indicator icon itself. Please see the attached screencast of illustration. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 11:53:20 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (107 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017224] Re: Cannot enable bluetooth in gnome-shell
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized + + + + I installed the latest linux-firmware from the repo but it didn't help. + + # dmesg | grep -i bluetooth + [ 18.861759] Bluetooth: Core ver 2.22 + [ 18.863617] NET: Registered PF_BLUETOOTH protocol family + [ 18.863621] Bluetooth: HCI device and connection manager initialized + [ 18.863628] Bluetooth: HCI socket layer initialized + [ 18.863631] Bluetooth: L2CAP socket layer initialized + [ 18.863638] Bluetooth: SCO socket layer initialized + [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 + [ 19.147702] Bluetooth: hci0: Device revision is 2 + [ 19.147707] Bluetooth: hci0: Secure boot is enabled + [ 19.147709] Bluetooth: hci0: OTP lock is enabled + [ 19.147712] Bluetooth: hci0: API lock is enabled + [ 19.147714] Bluetooth: hci0: Debug lock is disabled + [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 + [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi + [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800 + [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22 + [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2) + [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 + [ 20.015321] Bluetooth: BNEP filters: protocol multicast + [ 20.015329] Bluetooth: BNEP socket layer initialized + [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout + [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110) + [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download + [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110) + ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: - + mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After upgrade to
[Desktop-packages] [Bug 2017224] Re: Cannot enable bluetooth in gnome-shell
I installed the latest linux-firmware from the repo but it didn't help. # dmesg | grep -i bluetooth [ 18.861759] Bluetooth: Core ver 2.22 [ 18.863617] NET: Registered PF_BLUETOOTH protocol family [ 18.863621] Bluetooth: HCI device and connection manager initialized [ 18.863628] Bluetooth: HCI socket layer initialized [ 18.863631] Bluetooth: L2CAP socket layer initialized [ 18.863638] Bluetooth: SCO socket layer initialized [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 19.147702] Bluetooth: hci0: Device revision is 2 [ 19.147707] Bluetooth: hci0: Secure boot is enabled [ 19.147709] Bluetooth: hci0: OTP lock is enabled [ 19.147712] Bluetooth: hci0: API lock is enabled [ 19.147714] Bluetooth: hci0: Debug lock is disabled [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800 [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22 [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2) [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.015321] Bluetooth: BNEP filters: protocol multicast [ 20.015329] Bluetooth: BNEP socket layer initialized [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110) [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2017224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 2017222] Re: Ubuntu 23.04 can't start gnome-shell with nouveau driver
Installing the latest linux-firmware from the repo solved the issue. https://gitlab.freedesktop.org/drm/nouveau/-/issues/207 ** Bug watch added: gitlab.freedesktop.org/drm/nouveau/-/issues #207 https://gitlab.freedesktop.org/drm/nouveau/-/issues/207 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2017222 Title: Ubuntu 23.04 can't start gnome-shell with nouveau driver Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: This is a optimus laptop and after upgrade to 23.04, I purged nvidia drivers but couldn't start the desktop environment at all. kernel: nouveau: detected PR support, will not use DSM kernel: nouveau :59:00.0: enabling device ( -> 0003) kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1) kernel: nouveau :59:00.0: bios: version 90.17.61.00.73 kernel: nouveau :59:00.0: pmu: firmware unavailable kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6 kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 1822 kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97 kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8 kernel: nouveau :59:00.0: sec2: TRACEPC: 2318 kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found kernel: nouveau :59:00.0: DRM: BIT table 'L' not found kernel: nouveau :59:00.0: DRM: Pointer to TMDS table not found kernel: nouveau :59:00.0: DRM: DCB version 4.1 kernel: nouveau :59:00.0: DRM: MM: using COPY for buffer copies kernel: [drm] Initialized nouveau 1.3.1 20120801 for :59:00.0 on minor 0 kernel: nouveau :59:00.0: [drm] Cannot find any crtc or sizes kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC:
[Desktop-packages] [Bug 2017222] Re: Ubuntu 23.04 can't start gnome-shell with nouveau driver
** Description changed: This is a optimus laptop and after upgrade to 23.04, I purged nvidia drivers but couldn't start the desktop environment at all. - kernel: nouveau: detected PR support, will not use DSM kernel: nouveau :59:00.0: enabling device ( -> 0003) kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1) kernel: nouveau :59:00.0: bios: version 90.17.61.00.73 kernel: nouveau :59:00.0: pmu: firmware unavailable kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6 kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 1822 kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97 kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8 kernel: nouveau :59:00.0: sec2: TRACEPC: 2318 kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found kernel: nouveau :59:00.0: DRM: BIT table 'L' not found kernel: nouveau :59:00.0: DRM: Pointer to TMDS table not found kernel: nouveau :59:00.0: DRM: DCB version 4.1 kernel: nouveau :59:00.0: DRM: MM: using COPY for buffer copies kernel: [drm] Initialized nouveau 1.3.1 20120801 for :59:00.0 on minor 0 kernel: nouveau :59:00.0: [drm] Cannot find any crtc or sizes kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 1822 kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97 kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8 kernel: nouveau :59:00.0: sec2: TRACEPC: 2318 sensors[1464]: nouveau-pci-5900 kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
[Desktop-packages] [Bug 2017222] Re: Ubuntu 23.04 can't start gnome-shell with nouveau driver
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2017222 Title: Ubuntu 23.04 can't start gnome-shell with nouveau driver Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: This is a optimus laptop and after upgrade to 23.04, I purged nvidia drivers but couldn't start the desktop environment at all. kernel: nouveau: detected PR support, will not use DSM kernel: nouveau :59:00.0: enabling device ( -> 0003) kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1) kernel: nouveau :59:00.0: bios: version 90.17.61.00.73 kernel: nouveau :59:00.0: pmu: firmware unavailable kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6 kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 1822 kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97 kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8 kernel: nouveau :59:00.0: sec2: TRACEPC: 2318 kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found kernel: nouveau :59:00.0: DRM: BIT table 'L' not found kernel: nouveau :59:00.0: DRM: Pointer to TMDS table not found kernel: nouveau :59:00.0: DRM: DCB version 4.1 kernel: nouveau :59:00.0: DRM: MM: using COPY for buffer copies kernel: [drm] Initialized nouveau 1.3.1 20120801 for :59:00.0 on minor 0 kernel: nouveau :59:00.0: [drm] Cannot find any crtc or sizes kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel:
[Desktop-packages] [Bug 2017222] Re: Ubuntu 23.04 can't start gnome-shell with nouveau driver
** Package changed: nouveau-firmware (Ubuntu) => xserver-xorg-video- nouveau (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2017222 Title: Ubuntu 23.04 can't start gnome-shell with nouveau driver Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: This is a optimus laptop and after upgrade to 23.04, I purged nvidia drivers but couldn't start the desktop environment at all. kernel: nouveau: detected PR support, will not use DSM kernel: nouveau :59:00.0: enabling device ( -> 0003) kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1) kernel: nouveau :59:00.0: bios: version 90.17.61.00.73 kernel: nouveau :59:00.0: pmu: firmware unavailable kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6 kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 1822 kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97 kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8 kernel: nouveau :59:00.0: sec2: TRACEPC: 2318 kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found kernel: nouveau :59:00.0: DRM: BIT table 'L' not found kernel: nouveau :59:00.0: DRM: Pointer to TMDS table not found kernel: nouveau :59:00.0: DRM: DCB version 4.1 kernel: nouveau :59:00.0: DRM: MM: using COPY for buffer copies kernel: [drm] Initialized nouveau 1.3.1 20120801 for :59:00.0 on minor 0 kernel: nouveau :59:00.0: [drm] Cannot find any crtc or sizes kernel: nouveau :59:00.0: sec2: halted kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 TIDX 1b1f kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac kernel: nouveau :59:00.0: sec2: TRACEPC: 2055 kernel: nouveau :59:00.0: sec2: TRACEPC: 2305 kernel: nouveau :59:00.0: sec2: TRACEPC: 201c kernel: nouveau :59:00.0: sec2: TRACEPC: 2303 kernel: nouveau :59:00.0: sec2: TRACEPC: 2051 kernel: nouveau :59:00.0: sec2: TRACEPC: 269e kernel: nouveau :59:00.0: sec2: TRACEPC: 2617 kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2 kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9 kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa kernel: nouveau :59:00.0: sec2: TRACEPC:
[Desktop-packages] [Bug 2017239] [NEW] Prime is set to Nvidia but default renderer is still Intel
Public bug reported: Nvidia is set to Nvidia "Performance Mode" but the default renderer is still Intel: $ prime-select query nvidia $ glxinfo -B | grep -i "renderer string" OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-prime 0.8.17.1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 14:13:38 2023 Dependencies: InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/2017239 Title: Prime is set to Nvidia but default renderer is still Intel Status in nvidia-prime package in Ubuntu: New Bug description: Nvidia is set to Nvidia "Performance Mode" but the default renderer is still Intel: $ prime-select query nvidia $ glxinfo -B | grep -i "renderer string" OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-prime 0.8.17.1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 14:13:38 2023 Dependencies: InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/2017239/+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 2017224] Re: Cannot enable bluetooth in gnome-shell
Adding: Experimental = true KernelExperimental = true To: /etc/bluetooth/main.conf Cleared the above message but still can't enable bluetooth in Gnome Settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2017224/+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 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
This issue is happening in 23.04 as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 2017224] [NEW] Cannot enable bluetooth in gnome-shell
Public bug reported: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME
[Desktop-packages] [Bug 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
** Description changed: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation - $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 + $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. - - Every reboot or shutdown, the nvidia daemon doesn't terminate properly: - - Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. - Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. - Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL - Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. - Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
Should create a separate bug for Nvidia daemon issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 2016933] [NEW] Nvidia proprietary driver can't run apps
Public bug reported: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: Nvidia proprietary driver can't run apps Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 2014089] Re: Totem can't play .mp4 files
** Description changed: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". + + If I removed "apt remove gstreamer1.0-vaapi", Totem works fine. Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2014089 Title: Totem can't play .mp4 files Status in gstreamer1.0 package in Ubuntu: New Bug description: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". If I removed "apt remove gstreamer1.0-vaapi", Totem works fine. Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2014089/+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 2014089] [NEW] Totem can't play .mp4 files
Public bug reported: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2014089 Title: Totem can't play .mp4 files Status in gstreamer1.0 package in Ubuntu: New Bug description: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2014089/+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 1961508] Re: Dock displaying over window after resuming from blank screen
It can also happen while connecting an external monitor to the laptop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2003078] Re: Desktop freezes for seconds
This is issue is still happening, I hope it gets into your attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2003078 Title: Desktop freezes for seconds Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Ubuntu 22.10 on hybrid graphics laptop. Sometimes while normal workflow the desktop freezes for seconds: Asynchronous wait on fence :00:02.0:gnome-shell[4401]:96352 timed out (hint:intel_atomic_commit_ready [i915]) i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in Renderer [5405] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 i915 :00:02.0: [drm] Renderer[5405] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 14:01:20 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xserver-xorg-video-intel/+bug/2003078/+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 2013199] [NEW] App window get placed behind the dock and the top bar
Public bug reported: Sometimes after normal workflow or plugging and external monitor to the laptop, some app windows get placed behind the dock and the top bar seen in the attached screenshot for the gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libmutter-11-0 43.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 13:14:51 2023 InstallationDate: Installed on 2023-01-04 (83 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Screenshot from 2023-03-29 13-12-34.png" https://bugs.launchpad.net/bugs/2013199/+attachment/5658648/+files/Screenshot%20from%202023-03-29%2013-12-34.png ** Description changed: Sometimes after normal workflow or plugging and external monitor to the laptop, some app windows get placed behind the dock and the top bar seen - in the screenshot for the gnome-terminal. + in the attached screenshot for the gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libmutter-11-0 43.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 13:14:51 2023 InstallationDate: Installed on 2023-01-04 (83 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: mutter Importance: Undecided Status: New ** No longer affects: mutter ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- 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/2013199 Title: App window get placed behind the dock and the top bar Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Sometimes after normal workflow or plugging and external monitor to the laptop, some app windows get placed behind the dock and the top bar seen in the attached screenshot for the gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libmutter-11-0 43.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 13:14:51 2023 InstallationDate: Installed on 2023-01-04 (83 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013199/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
It is different issue than the one reported in #44. So if the fix is released for Kinetic, when it should be available in the repository for upgrade? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2012237] [NEW] Laptop freeze when trying to unlock session
Public bug reported: After locking the screen for sometime and then try to unlock, the whole laptop freeze and I have to hard reset. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 09:58:17 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (74 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012237 Title: Laptop freeze when trying to unlock session Status in gnome-shell package in Ubuntu: New Bug description: After locking the screen for sometime and then try to unlock, the whole laptop freeze and I have to hard reset. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 09:58:17 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (74 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012237/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
The workaround doesn't fix the problem for me. It's not only doesn't wake up the screen, it freezes the whole system and I have to hard reset! -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
How would you use 'Launch using Discrete Graphics Card' if you are trying to run an app from nautilus? it doesn't show that option. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 2003957] Re: Appearance set to dark but menus are the default
** Description changed: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. + + If I chose another item in the gnome settings and open "Appearance" + again, it will also trigger this bug. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. If I chose another item in the gnome settings and open "Appearance" again, it will also trigger this bug. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+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 2003957] Re: Appearance set to dark but menus are the default
** Attachment added: "Screenshot from 2023-01-26 16-56-25.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+attachment/5643605/+files/Screenshot%20from%202023-01-26%2016-56-25.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+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 2003957] [NEW] Appearance set to dark but menus are the default
Public bug reported: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Screenshot from 2023-01-26 16-56-39.png" https://bugs.launchpad.net/bugs/2003957/+attachment/5643600/+files/Screenshot%20from%202023-01-26%2016-56-39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+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 2003078] [NEW] Desktop freezes for seconds
Public bug reported: Ubuntu 22.10 on hybrid graphics laptop. Sometimes while normal workflow the desktop freezes for seconds: Asynchronous wait on fence :00:02.0:gnome-shell[4401]:96352 timed out (hint:intel_atomic_commit_ready [i915]) i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in Renderer [5405] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 i915 :00:02.0: [drm] Renderer[5405] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 14:01:20 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu ** Description changed: Ubuntu 22.10 on hybrid graphics laptop. Sometimes while normal workflow the desktop freezes for seconds: Asynchronous wait on fence :00:02.0:gnome-shell[4401]:96352 timed out (hint:intel_atomic_commit_ready [i915]) i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in Renderer [5405] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 i915 :00:02.0: [drm] Renderer[5405] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: - + CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 14:01:20 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: - virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed - virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] -Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] + Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] + Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (12 days ago)
[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
MUTTER_DEBUG_FORCE_KMS_MODE=simple Didn't solve the issue for me. This problem happens only while using the nouveau driver and I have filed a bug here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/2002314 -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1. - After locking the screen manually or automatically after the specified - timeout, the whole laptop freeze or behave extremely slow, either ways a - hard reset is a must by holding the power button to bring it back to - life. + After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. + This can happen right after the locking or after a while, but it doesn't happen if I suspended the laptop and wake it up. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 --
[Desktop-packages] [Bug 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: - This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- - video-nouveau version 1.0.17-2build1. + This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with + 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2002314 Title: System freezes after locking screen with the
[Desktop-packages] [Bug 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) - And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: - virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed - virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] -Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] + Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] + Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 - dmi.board.asset.tag: ATN12345678901234567 + dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
[Desktop-packages] [Bug 2002314] [NEW] System freezes after locking screen with the nouveau driver
Public bug reported: This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/2002314/+attachment/5640131/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2002314 Title: System freezes after locking screen with the nouveau driver Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description:
[Desktop-packages] [Bug 2001971] [NEW] Slow execution during boot and log contains many errors
Public bug reported: The service gpu-manager.service takes 10.44 seconds during boot time and it's log contains the below errors: log_file: /var/log/gpu-manager.log last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot can't access /run/u-d-c-nvidia-was-loaded file can't access /opt/amdgpu-pro/bin/amdgpu-pro-px Looking for nvidia modules in /lib/modules/5.19.0-26-generic/kernel Looking for nvidia modules in /lib/modules/5.19.0-26-generic/updates/dkms Looking for amdgpu modules in /lib/modules/5.19.0-26-generic/kernel Looking for amdgpu modules in /lib/modules/5.19.0-26-generic/updates/dkms Is nvidia loaded? no Was nvidia unloaded? no Is nvidia blacklisted? no Is intel loaded? yes Is radeon loaded? no Is radeon blacklisted? no Is amdgpu loaded? no Is amdgpu blacklisted? no Is amdgpu versioned? no Is amdgpu pro stack? no Is nouveau loaded? yes Is nouveau blacklisted? no Is nvidia kernel module available? no Is amdgpu kernel module available? no Vendor/Device Id: 8086:9a49 BusID "PCI:0@0:2:0" Is boot vga? yes Vendor/Device Id: 10de:1f9c BusID "PCI:89@0:0:0" can't open /sys/bus/pci/devices/:59:00.0/boot_vga Is boot vga? no can't open /sys/bus/pci/devices/:59:00.0/boot_vga Chassis type: "10" Laptop detected can't access /etc/u-d-c-nvidia-runtimepm-override file can't open /sys/module/nvidia/version Warning: cannot check the NVIDIA driver major version Support for runtimepm not detected. You can override this check at your own risk by creating the /etc/u-d-c-nvidia-runtimepm-override file. Is nvidia runtime pm supported for "0x1f9c"? yes Trying to create new file: /run/nvidia_runtimepm_supported Checking power status in /proc/driver/nvidia/gpus/:59:00.0/power Error while opening /proc/driver/nvidia/gpus/:59:00.0/power Is nvidia runtime pm enabled for "0x1f9c"? no Skipping "/dev/dri/card1", driven by "i915" Skipping "/dev/dri/card1", driven by "i915" Skipping "/dev/dri/card1", driven by "i915" Found "/dev/dri/card1", driven by "i915" output 0: card1-eDP-1 output 1: card1-HDMI-A-2 Number of connected outputs for /dev/dri/card1: 2 can't access /etc/prime-discrete No prime-settings found. Assuming prime is not set to ON (ONDEMAND could be on). Does it require offloading? no last cards number = 2 Has amd? no Has intel? yes Has nvidia? yes How many cards? 2 Loading nvidia with "no" parameters Has the system changed? No can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file can't open /sys/module/nvidia/version can't access /run/u-d-c-nvidia-drm-was-loaded file
[Desktop-packages] [Bug 1993902] [NEW] package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a
Public bug reported: i cant not install wine in my ubuntu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 22 22:51:38 2022 DuplicateSignature: package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1 Setting up libopenal-data (1:1.19.1-2build3) ... dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-10-21 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 jammy need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1993902 Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gdk-pixbuf package in Ubuntu: New Bug description: i cant not install wine in my ubuntu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 22 22:51:38 2022 DuplicateSignature: package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1 Setting up libopenal-data (1:1.19.1-2build3) ... dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-10-21 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993902/+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 1978805] [NEW] Using a hardware key during login sometimes fails asking for smart card instead
Public bug reported: I'm using a Yubikey with U2F during gdm3 login which works however sometimes without a reason, gdm asks for smart card instead, ignoring the inserted key and doesn't allow me to login at all unless gdm is restarted from another TTY. /etc/pam.d/common-auth: auth required pam_u2f.so The workaround to avoid this issue completely was to modify the file: /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop and make it like that: Exec=echo "/usr/libexec/gsd-smartcard" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 15 11:05:53 2022 InstallationDate: Installed on 2022-02-03 (131 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to jammy on 2022-04-21 (54 days ago) mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Smartcard.desktop: 2022-02-04T20:07:14.092002 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1978805 Title: Using a hardware key during login sometimes fails asking for smart card instead Status in gnome-settings-daemon package in Ubuntu: New Bug description: I'm using a Yubikey with U2F during gdm3 login which works however sometimes without a reason, gdm asks for smart card instead, ignoring the inserted key and doesn't allow me to login at all unless gdm is restarted from another TTY. /etc/pam.d/common-auth: auth required pam_u2f.so The workaround to avoid this issue completely was to modify the file: /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop and make it like that: Exec=echo "/usr/libexec/gsd-smartcard" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 15 11:05:53 2022 InstallationDate: Installed on 2022-02-03 (131 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to jammy on 2022-04-21 (54 days ago) mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Smartcard.desktop: 2022-02-04T20:07:14.092002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1978805/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Seems MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 solves the issue, hope it gets real fix soon without workarounds. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Attachment added: "gnome" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5596972/+files/gnome -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
Is there a way to run the extensions app on Wayland or must switch to Xorg? $ gnome-extensions-app Gdk-Message: 09:49:57.059: Error flushing display: Protocol error $ extension-manager Gdk-Message: 09:50:09.674: Error 71 (Protocol error) dispatching to Wayland display. -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+attachment/5596959/+files/journal.txt -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
This issue still happening and I enabled the above variable, gnome-shell wasn't blinking on any window up normally, I mean only when I perform an action it blinks that window until the event finish. But CPU usage still idles at 20%. -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
This happens to when connecting HDMI monitor to the laptop. The laptop's screen doesn't wake up while the external monitor turns on. Unplugging the HDMI cable, makes internal monitor works again. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1978268] Re: Internal monitor doesn't wake up if there is external monitor
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 Daniel, the other bug is about single monitor, but here I'm talking about multiple monitors. If you think it's the same issue, that's fine. -- 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/1978268 Title: Internal monitor doesn't wake up if there is external monitor Status in gnome-shell package in Ubuntu: New Bug description: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978268/+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 1767668] Re: GNOME Shell stuck at lock screen for a long time when undocked
I experience that behavior as well while I have no mounted filesystem over the network. -- 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/1767668 Title: GNOME Shell stuck at lock screen for a long time when undocked Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce on my Thinkpad X270 1. Start with laptop docked with internal and external screen in use 2. Lock machine (and potentially wait for blank screen to kick in - need to test) 3. Undock 4. Hit a key to wake screen up 5. Notice that the lock screen doesn't scroll up immediately 6. Wait for a couple of minutes until lock screen clears and you can type your password again 7. Notice that even though you can now use the desktop, you can switch to tty3, 4, etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767668/+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 1978268] [NEW] Internal monitor doesn't wake up if there is external monitor
Public bug reported: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1978268 Title: Internal monitor doesn't wake up if there is external monitor Status in gnome-shell package in Ubuntu: New Bug description: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978268/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
This is a very important issue because there are some GLX apps doesn't work with PRIME offload so they need Nvidia to be the default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1977648] [NEW] GLX is rendered by Intel GPU only in Wayland
Public bug reported: I'm using Nvidia driver and PRIME profile is set to performance, however in Wayland only, GLX is rendered by Intel GPU and can't have Nvidia as default renderer. This is a problem because not all OpenGL applications can work with XWayland or by setting the ENV variables to use Nvidia. In Xorg Nvidia can be the default renderer with the same configuration. $ prime-select query nvidia $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49) Version: 22.0.1 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 15:15:50 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- 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/1977648 Title: GLX is rendered by Intel GPU only in Wayland Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: I'm using Nvidia driver and PRIME profile is set to performance, however in Wayland only, GLX is rendered by Intel GPU and can't have Nvidia as default renderer. This is a problem because not all OpenGL applications can work with XWayland or by setting the ENV variables to use Nvidia. In Xorg Nvidia can be the default renderer with the same configuration. $ prime-select query nvidia $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49) Version: 22.0.1 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 15:15:50 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (43
[Desktop-packages] [Bug 1977643] [NEW] gdm crash when unlocking screen if using Nouveau driver
Public bug reported: Randomly but frequently when trying to unlock screen, it either becomes very slow (like when typing the password, characters are reflected very slowly) or it totally freeze and crash. Also switching TTY's doesn't work and have to hard reset. This was happening for me before while using Nvidia's driver but it has been working fine, now when I switched to the Nouveau driver, it constantly happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 13:06:05 2022 InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1977643 Title: gdm crash when unlocking screen if using Nouveau driver Status in gdm3 package in Ubuntu: New Bug description: Randomly but frequently when trying to unlock screen, it either becomes very slow (like when typing the password, characters are reflected very slowly) or it totally freeze and crash. Also switching TTY's doesn't work and have to hard reset. This was happening for me before while using Nvidia's driver but it has been working fine, now when I switched to the Nouveau driver, it constantly happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 13:06:05 2022 InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1977643/+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 1975812] [NEW] gnome-terminal freezed
Public bug reported: Randomly when having multiple tabs and ssh connections, gnome-terminal freezes and the only option is to choose "wait" or "force quite" and waiting does nothing so I have to terminate it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 11:43:02 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2022-02-03 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-04-21 (34 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1975812 Title: gnome-terminal freezed Status in gnome-terminal package in Ubuntu: New Bug description: Randomly when having multiple tabs and ssh connections, gnome-terminal freezes and the only option is to choose "wait" or "force quite" and waiting does nothing so I have to terminate it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 11:43:02 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2022-02-03 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-04-21 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1975812/+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 1975371] [NEW] Plugging / unplugging external monitor rearranges desktop icons differently
Public bug reported: Desktop icons were arranged and looking normally but after unplugging the external monitor, they looks like the screenshot. When I re-plugged the external monitor again, they were restored to the normal view. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat May 21 14:24:12 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (106 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (29 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-05-21 14-23-24.png" https://bugs.launchpad.net/bugs/1975371/+attachment/5591778/+files/Screenshot%20from%202022-05-21%2014-23-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975371 Title: Plugging / unplugging external monitor rearranges desktop icons differently Status in gnome-shell package in Ubuntu: New Bug description: Desktop icons were arranged and looking normally but after unplugging the external monitor, they looks like the screenshot. When I re-plugged the external monitor again, they were restored to the normal view. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat May 21 14:24:12 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (106 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975371/+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 1972151] Re: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor)
This also happens even if the external monitor is connected but switched off. If no monitors are connected at all, it open with in the main display normally. ** Attachment added: "photo_2022-05-21_14-12-08.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5591777/+files/photo_2022-05-21_14-12-08.jpg -- 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/1972151 Title: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor) Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
This is also happening for me When I launch extension-manager or cheese apps: [3254489.563] wl_display@1.delete_id([3254489.568] wl_display@1.error(nil, 7, "failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a ") 42) Gdk-Message: 12:22:58.093: Error flushing display: Protocol error -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
I have no manually installed extensions and I also removed the above extensions dir too. When I launch extension-manager (also cheese FYI) I get: [3254489.563] wl_display@1.delete_id([3254489.568] wl_display@1.error(nil, 7, "failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a ") 42) Gdk-Message: 12:22:58.093: Error flushing display: Protocol error Kindly note that the Brave browser is taking just 0.7%, there is nothing changing on the screen; and also when it happened, I closed all opened apps and CPU usage for gnome-shell was the same. -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974054] [NEW] Without a reason gnome-shell CPU usage gets high
Public bug reported: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-05-18 17-24-19.png" https://bugs.launchpad.net/bugs/1974054/+attachment/5590938/+files/Screenshot%20from%202022-05-18%2017-24-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: New Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974028] Re: Cheese doesn't start in Wyaland
apport-collect and ubuntu-bug are looking for package "linux" however I provided "cheese". ** Package changed: linux (Ubuntu) => cheese (Ubuntu) ** Changed in: cheese (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1974028 Title: Cheese doesn't start in Wyaland Status in cheese package in Ubuntu: Confirmed Bug description: $ WAYLAND_DEBUG=1 cheese [2642509.975] -> wl_display@1.get_registry(new id wl_registry@2) [2642509.993] -> wl_disp...@1.sync(new id wl_callback@3) [2642510.089] wl_display@1.delete_id(3) [2642510.101] wl_registry@2.global(1, "wl_compositor", 5) [2642510.110] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4) [2642510.122] wl_registry@2.global(2, "wl_drm", 2) [2642510.131] wl_registry@2.global(3, "wl_shm", 1) [2642510.138] -> wl_regis...@2.bind(3, "wl_shm", 1, new id [unknown]@5) [2642510.147] wl_registry@2.global(5, "wl_output", 2) [2642510.154] -> wl_regis...@2.bind(5, "wl_output", 2, new id [unknown]@6) [2642510.217] -> wl_disp...@1.sync(new id wl_callback@7) [2642510.223] wl_registry@2.global(6, "zxdg_output_manager_v1", 3) [2642510.233] -> wl_regis...@2.bind(6, "zxdg_output_manager_v1", 3, new id [unknown]@8) [2642510.245] -> zxdg_output_manager_v1@8.get_xdg_output(new id zxdg_output_v1@9, wl_output@6) [2642510.252] -> wl_disp...@1.sync(new id wl_callback@10) [2642510.258] wl_registry@2.global(7, "wl_data_device_manager", 3) [2642510.266] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id [unknown]@11) [2642510.278] wl_registry@2.global(8, "zwp_primary_selection_device_manager_v1", 1) [2642510.283] -> wl_regis...@2.bind(8, "zwp_primary_selection_device_manager_v1", 1, new id [unknown]@12) [2642510.291] wl_registry@2.global(9, "gtk_primary_selection_device_manager", 1) [2642510.295] -> wl_regis...@2.bind(9, "gtk_primary_selection_device_manager", 1, new id [unknown]@13) [2642510.300] wl_registry@2.global(10, "wl_subcompositor", 1) [2642510.305] -> wl_regis...@2.bind(10, "wl_subcompositor", 1, new id [unknown]@14) [2642510.313] wl_registry@2.global(11, "xdg_wm_base", 4) [2642510.320] wl_registry@2.global(12, "zxdg_shell_v6", 1) [2642510.326] wl_registry@2.global(13, "gtk_shell1", 5) [2642510.332] -> wl_regis...@2.bind(13, "gtk_shell1", 4, new id [unknown]@15) [2642510.337] wl_registry@2.global(14, "wp_viewporter", 1) [2642510.342] wl_registry@2.global(15, "zwp_pointer_gestures_v1", 3) [2642510.348] -> wl_regis...@2.bind(15, "zwp_pointer_gestures_v1", 1, new id [unknown]@16) [2642510.354] wl_registry@2.global(16, "zwp_tablet_manager_v2", 1) [2642510.359] -> wl_regis...@2.bind(16, "zwp_tablet_manager_v2", 1, new id [unknown]@17) [2642510.366] wl_registry@2.global(17, "wl_seat", 5) [2642510.372] wl_registry@2.global(18, "zwp_relative_pointer_manager_v1", 1) [2642510.376] wl_registry@2.global(19, "zwp_pointer_constraints_v1", 1) [2642510.382] wl_registry@2.global(20, "zxdg_exporter_v1", 1) [2642510.388] -> wl_regis...@2.bind(20, "zxdg_exporter_v1", 1, new id [unknown]@18) [2642510.397] wl_registry@2.global(21, "zxdg_importer_v1", 1) [2642510.402] -> wl_regis...@2.bind(21, "zxdg_importer_v1", 1, new id [unknown]@19) [2642510.409] wl_registry@2.global(22, "zwp_linux_dmabuf_v1", 4) [2642510.416] wl_registry@2.global(23, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [2642510.421] -> wl_regis...@2.bind(23, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1, new id [unknown]@20) [2642510.431] wl_registry@2.global(24, "zwp_text_input_manager_v3", 1) [2642510.438] wl_registry@2.global(25, "wp_presentation", 1) [2642510.444] wl_registry@2.global(26, "xdg_activation_v1", 1) [2642510.449] wl_callb...@3.done(23195) [2642510.485] -> wl_shm@5.create_pool(new id wl_shm_pool@3, fd 10, 2304) [2642510.623] -> wl_shm_pool@3.resize(6912) [2642510.669] -> wl_shm_pool@3.resize(16128) [2642510.745] -> wl_shm_pool@3.resize(34560) [2642510.909] -> wl_shm_pool@3.resize(71424) [2642511.697] -> wl_shm_pool@3.resize(145152) [2642511.753] -> wl_shm_pool@3.resize(292608) [2642512.954] -> wl_shm_pool@3.resize(587520) [2642514.901] -> wl_shm_pool@3.resize(1177344) [2642517.838] -> wl_shm_pool@3.resize(2356992) [2642526.562] -> wl_regis...@2.bind(17, "wl_seat", 5, new id [unknown]@21) [2642528.370] -> wl_compositor@4.create_surface(new id wl_surface@22) [2642528.384] -> zwp_primary_selection_device_manager_v1@12.get_device(new id zwp_primary_selection_device_v1@23, wl_seat@21) [2642528.389] -> wl_data_device_manager@11.get_data_device(new id wl_data_device@24, wl_seat@21) [2642528.444] -> wl_compositor@4.create_surface(new id wl_surface@25) [2642528.447] -> zwp_tablet_manager_v2@17.get_tablet_seat(new id zwp_tablet_seat_v2@26, wl_seat@21) [2642528.451] ->
[Desktop-packages] [Bug 1973175] [NEW] Window dimensions are changed and appears behind the dock
Public bug reported: After using the session for a while with a normal workflow like switching opened windows etc. Some app windows's dimensions are changed automatically from the left side and appears behind the dock as shown in the screenshot. To correct it, the window must be resized and then maximized to return back to normal dimension for the current screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 12 14:20:21 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (97 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (20 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-05-12 13-28-26.png" https://bugs.launchpad.net/bugs/1973175/+attachment/5589226/+files/Screenshot%20from%202022-05-12%2013-28-26.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1973175 Title: Window dimensions are changed and appears behind the dock Status in gnome-shell package in Ubuntu: New Bug description: After using the session for a while with a normal workflow like switching opened windows etc. Some app windows's dimensions are changed automatically from the left side and appears behind the dock as shown in the screenshot. To correct it, the window must be resized and then maximized to return back to normal dimension for the current screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 12 14:20:21 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (97 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973175/+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 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588164/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588165/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588166/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
Yes it's not related to unlocking at all and I believe it happens only if there is external monitor connected. And sometimes it opens in full screen mode. ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588163/+files/xrandr.txt -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
https://errors.ubuntu.com/user/2b93ad219b48c9b97a7a077caec6d69c0c1775edbb7ed9adc197eb0f82ef67bad56000432096446e2a08ce86802994b7d7974a33972dece2b7b97ff663da8f05 -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
when I try to open the uploaded bug, I get: "Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access." -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
I have no extensions installed manually. It happens whenever opening the file dialog, but I noticed if there is no external display connected to the laptop, it didn't happen so far. I ran ubuntu-bug against the file but the URL doesn't work, returning "Error reports sent from this system", so I'm unable to get the bug ID. -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
It can happen also after normal boot, not related to resuming or unlocking. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588086/+files/log -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+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 1972151] Re: File dialog not displayed within screen range
BTW this is not only in gedit, also in other apps. -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+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
