[Desktop-packages] [Bug 2064569] [NEW] The shortcut for "Increment number at cursor" not works in gnome-text-editor
Public bug reported: The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works in gnome-text-editor on Ubuntu 24.04. Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 2 06:33:33 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064569 Title: The shortcut for "Increment number at cursor" not works in gnome-text- editor Status in gnome-text-editor package in Ubuntu: New Bug description: The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works in gnome-text-editor on Ubuntu 24.04. Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 2 06:33:33 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064569/+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 2064025] Re: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session)
We found that the root cause is the ibus. A workaround to fix this problem is running: GTK_IM_MODULE=simple gnome-text-editor Furthermore, I will open an issue in: https://github.com/ibus/ibus ** No longer affects: gtk4 (Ubuntu) ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) Status in gnome-text-editor package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064025/+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 2064025] Re: Accented characters persisting in GNOME Text Editor
I conducted some tests: Ubuntu 24.04: GNOME Text Editor version: 46.1 gtk4-launch --version: 4.14.2 Results: - X11: the bug happens. - Wayland: no problem. Ubuntu 22.04: GNOME Text Editor version: 42.2 gtk4-launch --version: 4.6.9 Results: - X11: no problem. - Wayland: no problem. Fedora 40: GNOME Text Editor version: 46.1 gtk4-launch --version: 4.14.2 Results: - X11: no problem. - Wayland: no problem. --- It also looks to me to be Ubuntu 24.04 specific (with X11). ** Summary changed: - Accented characters persisting in GNOME Text Editor + Ubuntu 24.04: Accented characters persisting in Text Editor with X11 session ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Ubuntu 24.04: Accented characters persisting in Text Editor with X11 session + Ubuntu 24.04: Accented characters persisting in Text Editor (X11 session) ** Summary changed: - Ubuntu 24.04: Accented characters persisting in Text Editor (X11 session) + Ubuntu 24.04: Accented characters persisting in Text Editor (in X11 session) ** Summary changed: - Ubuntu 24.04: Accented characters persisting in Text Editor (in X11 session) + Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) Status in gnome-text-editor package in Ubuntu: New Status in gtk4 package in Ubuntu: New Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064025/+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 2064151] Re: text editor open with letters it won't open with blank?
Hi! It seems likely that the previous session was saved, causing this. To prevent this from happening again, navigate to "Preferences" and uncheck the option labeled "Restore Session." ** Changed in: gnome-text-editor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064151 Title: text editor open with letters it won't open with blank? Status in gnome-text-editor package in Ubuntu: Invalid Bug description: how to fix the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064151/+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 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper
Fixed in commit: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/085102be74f4c98094712a165e5128feaca50438 -- 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/1423773 Title: [memory leak] Gnome-Shell don't free ram when changing the wallpaper Status in GNOME Shell: New Status in mutter package in Ubuntu: Incomplete Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1423773/+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 1899803] Re: Some comments on annotations are not visible
The bug still continues. I've also tested using: - Ubuntu 24.04 with Evince 46.0 ** Description changed: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: + - Ubuntu 24.04 with Evince 46.0 + - Ubuntu 20.10 with Evince 3.38.0 - Ubuntu 20.04 with Evince 3.36.7 - - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 ** Description changed: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 24.04 with Evince 46.0 + - Ubuntu 22.04.2 with Evince 42.3 - Ubuntu 20.10 with Evince 3.38.0 - Ubuntu 20.04 with Evince 3.36.7 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 24.04 with Evince 46.0 - Ubuntu 22.04.2 with Evince 42.3 - Ubuntu 20.10 with Evince 3.38.0 - Ubuntu 20.04 with Evince 3.36.7 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1899803] Re: Some comments on annotations are not visible
** Tags added: jammy noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 24.04 with Evince 46.0 - Ubuntu 22.04.2 with Evince 42.3 - Ubuntu 20.10 with Evince 3.38.0 - Ubuntu 20.04 with Evince 3.36.7 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+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 1898325] Re: Gnome calendar is not syncing with Google calendar online account.
Fix released in: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/626 ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-calendar (Ubuntu) Status: Fix Released => Fix Committed ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/626 Importance: Unknown Status: Unknown ** Changed in: gnome-calendar (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1898325 Title: Gnome calendar is not syncing with Google calendar online account. Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Fix Released Bug description: I'm using Ubuntu 20.10 groovy (beta). The Gnome calendar is not syncing with Google calendar online account. In Ubuntu 20.04 (focal) there is no such problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-calendar 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:34:16 2020 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1898325/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
** Changed in: nautilus (Ubuntu) Status: New => Fix Committed ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: Fix Released Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 2064024] [NEW] Check Spelling: the menu "Languages" is empty in GNOME Text Editor
Public bug reported: In the gnome-text-editor, users are unable to change the language of the spelling checker due to an empty "Languages" menu when right-clicking in the text. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:43:39 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Summary changed: - Check Spelling: the menu "Languages" is empty. + Check Spelling: the menu "Languages" is empty in GNOME Text Editor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064024 Title: Check Spelling: the menu "Languages" is empty in GNOME Text Editor Status in gnome-text-editor package in Ubuntu: New Bug description: In the gnome-text-editor, users are unable to change the language of the spelling checker due to an empty "Languages" menu when right- clicking in the text. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:43:39 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064024/+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 2064025] [NEW] Accented characters persisting in GNOME Text Editor
Public bug reported: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (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 gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Accented characters persisting in GNOME Text Editor Status in gnome-text-editor package in Ubuntu: New Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064025/+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 2062089] Re: [NVIDIA] Ubuntu 24.04 detects three monitors instead of two
** Summary changed: - [NVIDIA] Cursor movement to right corner causes screen shift + [NVIDIA] Ubuntu 24.04 detects three monitors instead of two ** Summary changed: - [NVIDIA] Ubuntu 24.04 detects three monitors instead of two + [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) ** Description changed: I recently installed Ubuntu 24.04 for testing purposes and have - encountered an unexpected issue. When moving the cursor to the extreme - right corner of the screen, the entire display shifts to the right. - Below are the pertinent details: + encountered an unexpected issue. + + The 'Displays' configuration indicates the presence of three monitors, like this: + 1) Dell Inc. 27" + 2) Dell Inc. 27" + 3) Unknown Display + However, I only have two displays and not a third one. + + + When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/2062089 Title: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) Status in gnome-shell package in Ubuntu: New Bug description: I recently installed Ubuntu 24.04 for testing purposes and have encountered an unexpected issue. The 'Displays' configuration indicates the presence of three monitors, like this: 1) Dell Inc. 27" 2) Dell Inc. 27" 3) Unknown Display However, I only have two displays and not a third one. When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/2062089/+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 2062089] Re: [NVIDIA] Cursor movement to right corner causes screen shift
Further details: The 'Displays' configuration indicates the presence of three monitors, like this: 1) Dell Inc. 27" 2) Dell Inc. 27" 3) Unknown Display However, I only have two displays and not a third one. -- 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/2062089 Title: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) Status in gnome-shell package in Ubuntu: New Bug description: I recently installed Ubuntu 24.04 for testing purposes and have encountered an unexpected issue. When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/2062089/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Hello Daniel van Vugt (@vanvugt)! Would you mind applying your latest patches to your PPA? So we can test the new packages. - mutter_42.9-0ubuntu8.debdiff - mutter_45.2-0ubuntu5.debdiff Thanks, -- 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/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2060613] Re: Gedit sometimes crashes by segmentation fault at closure
Sporadically, I had the same issue with Ubuntu 24.04 beta. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2060613 Title: Gedit sometimes crashes by segmentation fault at closure Status in gedit package in Ubuntu: Confirmed Bug description: When I do not wait until the document is fully saved (or I only wait a short interval) gedit crashes with segmentation fault after a few seconds. It has not lead to data loss yet, but it is truly unpleasant, let alone if we include that otherwise it floods the terminal with critical GTK errors... (bug #2055010) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gedit 46.2-1build1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 07:16:42 2024 InstallationDate: Installed on 2023-07-05 (279 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2060613/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11
Hello Daniel van Vugt, I wanted to express my gratitude for your efforts. I've recently tested your mutter version with the following packages: - gir1.2-mutter-10_42.9-0ubuntu7vv1_amd64.deb - libmutter-10-0_42.9-0ubuntu7vv1_amd64.deb - mutter-common_42.9-0ubuntu7vv1_all.deb I'm pleased to report that the bug I encountered has been successfully resolved. Additionally, I'm using NVIDIA with driver version "nvidia- driver-535". Once again, thank you for your work! Best regards. -- 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/2059847 Title: Input lag or freezes on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Jammy: Triaged Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: In Progress Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Verify that input never froze for any perceptible period of time. 4. Run: journalctl -b0 | grep MetaSyncRing 5. Verify the above command does NOT show messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the code being modified. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
Based on mikabytes's answer, I've found another solution that not will not leave apt in a temporary broken state. For Ubuntu 22.04.4: Download the packages: $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/gir1.2-mutter-10_42.9-0ubuntu5_amd64.deb $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/libmutter-10-0_42.9-0ubuntu5_amd64.deb $ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/mutter-common_42.9-0ubuntu5_all.deb Install the packages: $ sudo dpkg -i *mutter*.deb Mark as hold: $ sudo apt-mark hold gir1.2-mutter-10 $ sudo apt-mark hold libmutter-10-0 $ sudo apt-mark hold mutter-common -- 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/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I've found a workaround: I conducted a fresh installation of Ubuntu 22.04.4 and subsequently marked specific packages for holding using the following commands: $ sudo apt-mark hold gir1.2-mutter-10 $ sudo apt-mark hold libmutter-10-0 $ sudo apt-mark hold mutter-common Following this, I proceeded to update all packages. So, I'm currently utilizing version "42.9-0ubuntu5" of the mutter packages, instead of version "42.9-0ubuntu7." Now, my system is with packages: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy $ dpkg -l | grep "mutter" | tr -s " " | cut -d " " -f 1-3 hi gir1.2-mutter-10:amd64 42.9-0ubuntu5 hi libmutter-10-0:amd64 42.9-0ubuntu5 hi mutter-common 42.9-0ubuntu5 $ dpkg -l | grep " nvidia-" | tr -s " " | cut -d " " -f 1-3 ii linux-modules-nvidia-535-generic-hwe-22.04 6.5.0-26.26~22.04.1 ii nvidia-compute-utils-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-firmware-535-535.161.07 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-common-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-source-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-prime 0.8.17.1 ii nvidia-settings 510.47.03-0ubuntu1 ii nvidia-utils-535 535.161.07-0ubuntu0.22.04.1 -- 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/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
Same problem here. I have the lag in Gnome Terminal and Gnome Console (kgx). $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy $ dpkg -l | grep "mutter" | tr -s " " | cut -d " " -f 1-3 ii gir1.2-mutter-10:amd64 42.9-0ubuntu7 ii libmutter-10-0:amd64 42.9-0ubuntu7 ii mutter-common 42.9-0ubuntu7 $ dpkg -l | grep " nvidia-" | tr -s " " | cut -d " " -f 1-3 ii linux-modules-nvidia-535-generic-hwe-22.04 6.5.0-26.26~22.04.1 ii nvidia-compute-utils-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-firmware-535-535.161.07 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-common-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-source-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-prime 0.8.17.1 ii nvidia-settings 510.47.03-0ubuntu1 ii nvidia-utils-535 535.161.07-0ubuntu0.22.04.1 -- 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/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 1892747] Re: GNOME hangs while changing display brightness from keyboard shortcut
Just for better bug tracking, I've added some links. Related bugs (maybe duplicated): - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013255 - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747 - https://bugs.launchpad.net/gnome-shell/+bug/1895486 - https://askubuntu.com/questions/1242205/ubuntu-20-04-hangs-when-changing-brightness-level-with-keyboard - https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-ubuntu-gnome-17-04 Upstream issues: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1279 ** Summary changed: - GNOME hangs while changing display brightness from keyboard shortcut + [media-keys] GNOME hangs while changing display brightness from keyboard shortcut -- 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/1892747 Title: [media-keys] GNOME hangs while changing display brightness from keyboard shortcut Status in gnome-shell package in Ubuntu: Fix Released Bug description: Whenever I change my display's brightness using keyboard shortcuts (For me F11 & F12), Ubuntu hangs a little, the brightness is changed immediately, but everything (except the mouse) hangs while it is being changed and sometimes for quite some time after. There is no problem doing it through the system. Changing volume using keyboard shortcuts works perfectly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747/+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 1895486] Re: [media-keys] Media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
Just for better bug tracking, I've added some links.
Related bugs (maybe duplicated):
- https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013255
- https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747
- https://bugs.launchpad.net/gnome-shell/+bug/1895486
-
https://askubuntu.com/questions/1242205/ubuntu-20-04-hangs-when-changing-brightness-level-with-keyboard
-
https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-ubuntu-gnome-17-04
Upstream issues:
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1279
** Summary changed:
- [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock"
keyboards
+ [media-keys] Media keys with lag slow/delay on Gnome with "Scroll Lock"
keyboards
** Changed in: xkeyboard-config (Ubuntu)
Assignee: Cristiano Fraga G. Nunes (cfgnunes) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
New
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.
[Desktop-packages] [Bug 2013255] Re: changing screen brightness with keyboard hotkeys reacts very slow
Related bugs (maybe duplicated): - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013255 - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747 - https://bugs.launchpad.net/gnome-shell/+bug/1895486 - https://askubuntu.com/questions/1242205/ubuntu-20-04-hangs-when-changing-brightness-level-with-keyboard - https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-ubuntu-gnome-17-04 Upstream issues: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1279 ** Summary changed: - changing screen brightness with keyboard hotkeys reacts very slow + [media-keys] Changing screen brightness with keyboard hotkeys reacts very slow -- 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/2013255 Title: [media-keys] Changing screen brightness with keyboard hotkeys reacts very slow Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using "Fn" key + brightness up/down (arrow up/down) keys reacts very delayed (up to 2 seconds) and system freezes enirely during these brightness-changes being applied by the system. It however works flawless in the brightness slider menu in the top right. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 03:38:51 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 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/gnome-shell/+bug/2013255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
As the xkeyboard-config is not the cause of that bug, the Scroll Lock
key must return because many users use this key in some apps.
I've opened a Merge Request to return the Scroll Lock key:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/555
** Changed in: xkeyboard-config (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
New
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
I've removed the patch. It did not work. This bug must be reopened. ** Patch removed: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+attachment/5679802/+files/848.patch ** Tags removed: patch -- 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/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1968792/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
I've removed the patch. It did not work. ** Patch removed: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+attachment/5679803/+files/848.patch ** Changed in: nautilus (Ubuntu) Status: Fix Released => New ** Tags removed: patch -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action
This is the patch of the bug. From: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/848/diffs#3c33043d4592495dd13d048ae9c8eee31a60fd08 ** Patch added: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+attachment/5679802/+files/848.patch -- 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/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in nautilus package in Ubuntu: Triaged Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
Possible patch for this bug. From: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/848/diffs#3c33043d4592495dd13d048ae9c8eee31a60fd08 ** Patch added: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+attachment/5679803/+files/848.patch -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
I've reported the bug in the upstream: https://gitlab.gnome.org/GNOME/nautilus/-/issues/3005 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3005 https://gitlab.gnome.org/GNOME/nautilus/-/issues/3005 -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action
This bug is similar to the bug (but not duplicated): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939 "When has selected files, the selected menus don't activate by the keyboard..." -- 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/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in nautilus package in Ubuntu: Triaged Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
This bug is similar to the bug (but not duplicated): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792 -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 1899803] Re: Some comments on annotations are not visible
The bug still continues. I've also tested using: - Ubuntu 22.04.2 with Evince 42.3 Upstream bug track: https://gitlab.gnome.org/GNOME/evince/-/issues/171 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #171 https://gitlab.gnome.org/GNOME/evince/-/issues/171 ** Changed in: evince Status: Fix Released => Unknown ** Changed in: evince Remote watch: gitlab.gnome.org/GNOME/evince/-/issues #1347 => gitlab.gnome.org/GNOME/evince/-/issues #171 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+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 2023939] [NEW] Items in the sidebar are not activated by the keyboard when has selected files
Public bug reported: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
About the fix for this bug:
This fix solves the problem only for ABNT2 keyboards (used in Brazil,
only).
But this bug affects all keyboards with "Scroll Lock" key.
The solution proposed in the merge request that I made in project
xkeyboard-config is not a suitable solution yet. It is not a definitive
solution for this problem. It was just a workaround.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
New
Status in xkeyboard-config package in Ubuntu:
Fix Released
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1892747] Re: GNOME hangs while changing display brightness from keyboard shortcut
Adding more information: Similar bug: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1895486 For ABNT2 keyboards, I've removed the "Scroll Lock" key to fix this problem, see: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/112 Bug tracking in: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821 -- 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/1892747 Title: GNOME hangs while changing display brightness from keyboard shortcut Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Whenever I change my display's brightness using keyboard shortcuts (For me F11 & F12), Ubuntu hangs a little, the brightness is changed immediately, but everything (except the mouse) hangs while it is being changed and sometimes for quite some time after. There is no problem doing it through the system. Changing volume using keyboard shortcuts works perfectly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1892747/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
Daniel you were right, disabling the extension seems to solved the problem -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place
may I could find the cause of this problem. if you look, the second animation is actually the animation that gnome shell runs when you minimize windows. gnome shell minimize application to the "activities" button while dash to dock tend to override to bottom, left or right depending on where you put the dock we need to disable the gnome shell animation and I emphasize that this glitch does not occur in wayland session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969140 Title: Window minimize animation flickers and appears in the wrong place Status in gnome-shell package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place
in my case glitches appear with any refresh rate -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place Status in gnome-shell package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] Re: graphic glitches when minimizing and maximizing apps
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969140/+attachment/5580757/+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/1969140 Title: Graphical glitches when minimizing and maximizing apps Status in gnome-shell package in Ubuntu: New Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] Re: graphic glitches when minimizing and maximizing apps
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969140/+attachment/5580758/+files/lspci.txt ** Description changed: - Graphic glitches appears while minimizing or maximizing apps in x11 + Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - graphic glitches when minimizing and maximizing apps + Graphical glitches when minimizing and maximizing 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/1969140 Title: Graphical glitches when minimizing and maximizing apps Status in gnome-shell package in Ubuntu: New Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] Re: graphic glitches when minimizing and maximizing apps
As mentioned by @vanvugt in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967471, i attached lscpi and journal ** Description changed: Graphic glitches appears while minimizing or maximizing apps in x11 - session randomly + session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140 Title: Graphical glitches when minimizing and maximizing apps Status in gnome-shell package in Ubuntu: New Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1969140] [NEW] graphic glitches when minimizing and maximizing apps
Public bug reported: Graphic glitches appears while minimizing or maximizing apps in x11 session randomly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screencast from 14-04-22 17:04:29.webm" https://bugs.launchpad.net/bugs/1969140/+attachment/5580745/+files/Screencast%20from%2014-04-22%2017%3A04%3A29.webm -- 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/1969140 Title: graphic glitches when minimizing and maximizing apps Status in gnome-shell package in Ubuntu: New Bug description: Graphic glitches appears while minimizing or maximizing apps in x11 session randomly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1969140/+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 1899803] [NEW] Some comments on annotations are not visible
Public bug reported: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible Status in evince package in Ubuntu: New Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1899803/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
This validation is blocking the commit for the bug 1892440 (that has exhaustively already validated). -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
I've also tried to reproduce adding a delay (sleep 0.1) between the commands, but without success. I've tried: $ xinput (to get the number of my mouse) $ while true; do xinput disable ; sleep 0.1; xinput enable ; sleep 0.1; done -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hi, @vanvugt. The bug 1558886 is a bit complicated to reproduce. I also have tried some times. In this case, it would be possible to mark the bug 1558886 as "opened until validation" and commit the fix for this current bug 1892440 to the "-updates"? Because, if we wait someone validate the bug 1558886, it may be that this fix is stuck forever. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
I can't reproduce the crash by using the steps mentioned in "[Test case]". After following these steps, the process Xorg consume about 100% of CPU. -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Hi Daniel! Thanks for your response. F.Y.: this bug is different from bug 1813441. There, it is not possible to drag and drop (only). This bug, in addition to not being able to drag and drop, gnome-shell crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell in Ubuntu 20.10 (beta). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1898462] [NEW] [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Public bug reported: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell in Ubuntu 20.10 (beta). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell package in Ubuntu: New Bug description: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell in Ubuntu 20.10 (beta). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898462/+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 1898325] [NEW] Gnome calendar is not syncing with Google calendar online account.
Public bug reported: I'm using Ubuntu 20.10 groovy (beta). The Gnome calendar is not syncing with Google calendar online account. In Ubuntu 20.04 (focal) there is no such problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-calendar 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:34:16 2020 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1898325 Title: Gnome calendar is not syncing with Google calendar online account. Status in gnome-calendar package in Ubuntu: New Bug description: I'm using Ubuntu 20.10 groovy (beta). The Gnome calendar is not syncing with Google calendar online account. In Ubuntu 20.04 (focal) there is no such problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-calendar 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:34:16 2020 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1898325/+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 1898324] Re: [groovy] Different thickness title bars between gtk3 / gtk2 applications
In Ubuntu 20.04 there is no such problem: all title bars have the same thickness. -- 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/1898324 Title: [groovy] Different thickness title bars between gtk3 / gtk2 applications Status in gnome-shell package in Ubuntu: New Bug description: I'm using Ubuntu 20.10 (beta). The title bar thickness is different between gtk3 / gtk2 applications. Gtk3 applications have a thicker title bar. I think all thickness must be the same to keep the visual identity of the OS. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:16:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898324/+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 1898324] [NEW] [groovy] Different thickness title bars between gtk3 / gtk2 applications
Public bug reported: I'm using Ubuntu 20.10 (beta). The title bar thickness is different between gtk3 / gtk2 applications. Gtk3 applications have a thicker title bar. I think all thickness must be the same to keep the visual identity of the OS. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:16:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Summary changed: - [groovy] Different title bar thickness between gtk3 / gtk2 applications + [groovy] Different thickness title bars between gtk3 / gtk2 applications -- 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/1898324 Title: [groovy] Different thickness title bars between gtk3 / gtk2 applications Status in gnome-shell package in Ubuntu: New Bug description: I'm using Ubuntu 20.10 (beta). The title bar thickness is different between gtk3 / gtk2 applications. Gtk3 applications have a thicker title bar. I think all thickness must be the same to keep the visual identity of the OS. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:16:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898324/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
7 days have passed. I'm waiting the package be released to "-updates". LoL -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Fix Committed -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1798166] Re: “Mouse battery low” notification can't be disabled
If I understood correctly this bug was invalidated as a Linux bug only, not as a GNOME issue. As a GNOME (or more specifically as "gnome- settings-daemon package") it is not only valid, but its priority is set to high. It makes sense to me. -- 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/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+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 1896332] Re: SRU 3.36.6
Now, I'm waiting for the SRU team release this fix to "-updates". :) -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+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 1877209] Re: Update to 3.36.2 and SRU it
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1877209 Title: Update to 3.36.2 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been quite lots of changes in monitors and clipboard management, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877209/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
The updated package will be released to "-updates" after the bug fixed have been verified and the package has been in "-proposed" for a minimum of 7 days. In this case, the status is: "Fix Committed" (not "Fix Released"). -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Fix Committed -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ).
** Summary changed: - Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. + Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ). -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1896332] Re: SRU 3.36.6
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
For ABNT2 keyboards, I've removed the "Scroll Lock" key, see:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/merge_requests/112
It is not the right solution (I even regretted it), but it works...
--
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/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested the mutter 3.36.6-1ubuntu0.20.04.2~wip1 (in the PPA). Now, all works fine! Thanks for your attention and work. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Thanks, Trevinho! ;) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
See also: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 ** Description changed: + In Ubuntu 20.04.1 (focal): + [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lsusb-v.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413598/+files/lsusb-v.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413597/+files/syslog -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413599/+files/version.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
In my syslog: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Description changed: In Ubuntu 20.04.1 (focal): [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Description changed: - In Ubuntu 20.04.1 (focal): + In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Summary changed: - Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) + Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) ** Description changed: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago)
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413602/+files/dmesg.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413601/+files/lspci-vnvn.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested in a fresh install also. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413600/+files/uname-a.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1896332] Re: SRU 3.36.6
There is a problem: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I've fill another bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1896818] [NEW] Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
Public bug reported: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) Status in mutter package in Ubuntu: New Bug description: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, After I power down my display and power up again (in the lock screen), the problem is: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+attachment/5413576/+files/syslog -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, I'll do that. Anyway, thanks for the fix. ;) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1. BUT After an "Automatic Screen Lock", the display turned off, the Gnome Shell crash and show us a blank screen with the message "Oh no! Something has gone wrong." This bug did not appears before the update. I have a NVIDIA card. I think that this problem occurs only with NVIDIA users. I have other PC (without a NVIDIA card) and the problem not occurs. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Thanks, Brian. I'll test the new package coming soon. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Committed Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome
Bug tracking in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1821
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
** Summary changed:
- [media-keys] Fn media keys with lag slow/delay on Gnome
+ [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll_Lock"
keyboards
** Summary changed:
- [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll_Lock"
keyboards
+ [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock"
keyboards
--
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/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in gnome-shell package in Ubuntu:
New
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper
** Summary changed: - Gnome-Shell don't free ram when I change a wallpaper + [memory leak] Gnome-Shell don't free ram when changing the wallpaper -- 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/1423773 Title: [memory leak] Gnome-Shell don't free ram when changing the wallpaper Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+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 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview
** Summary changed: - gnome-shell using a lot of RAM after repeatedly opening the overview + [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview -- 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/1856838 Title: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856838/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I use Ubuntu 20.04.1 (focal), and I have the same problem. I confirm this bug. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: New Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
I use Ubuntu 20.04.1, and I have the same problem. I confirm this bug. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Marco Trevisan, I found a problem with this fix from PPA: After an "Automatic Screen Lock" with a monitor turned off, the Gnome Shell crash and show us a blank screen with the message "Oh no! Something has gone wrong." -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: Fix Committed Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I did all the tests with PPA, and everything seems to be correct. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: Fix Committed Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1896332] Re: SRU 3.36.6
I did all the tests, and everything seems to be correct. -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: New Status in yaru-theme source package in Focal: New Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Grazie mille, Trevinho! -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: Fix Committed Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Summary changed: - Shell text is the wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) + Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: Fix Committed Bug description: See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
I use Ubuntu 20.04 and I have the same problem.
A similar bug I reported here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1895486
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
** Package changed: meta-gnome3 (Ubuntu) => gnome-shell (Ubuntu)
--
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/108
Title:
Desktop briefly becomes unresponsive when typing on 2 keyboards at the
same time
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
from the repos.
If I connect 2 (or more) keyboards to my computer and type on both at
the same time, the desktop briefly becomes unresponsive. More
keypresses increase the time of unresponsiveness.
E.g. when typing a full sentence in gedit or the terminal, only very
few characters show up on the screen (I guess up until something is
pressed on both keyboards at the same time), then everything freezes.
Then after a while (some seconds), all the characters show up. And the
desktop becomes responsive again.
Symptoms: During the freeze, windows stop updating their content. If
seconds are enabled on the clock at the top middle, these freeze too.
But I'm still able to move the mouse pointer around during the freeze
without any problems.
The back story:
I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
quickly noticed the issue. But initiallly I thought it was an issue
with the keyboard, and the problem wasn't that bad. But as I've gotten
more used to the keyboard since yesterday and started picking up a
proper typing speed, things got worse.
The keyboard is technically two separate cabled USB keyboards each
with only about half of they keys of a normal keyboard (or at least
that's very much my impression).
After getting the suspicion that this was a software issue, not a
hardware issue, I tried typing on my old Logitech keyboard (Unifying
Receiver) along with one of the R-Go halves: Same issue. Then I tried
each of the halves without the other (as in "single" keyboard typing):
No issue. Then I connected another Logitech keyboard (separate UR),
typed on both Logitechs: Same issue.
Some further observations:
1) Nothing of significance in my syslog.
2) If I drop to a non-graphical shell, there's no problem. I suspect this
issue is related to X.org or Gnome, but I'm in no position to say anything
credible about that.
3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS
machine.
Let me know if there are any logs I can provide or things I can run to
produce useful debug output.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/108/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome
Other users has a same problem. See:
https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-
ubuntu-gnome-17-04
This problem appears on Ubuntu 17.04, 18.04 and 20.04.
** Package changed: x11-xkb-utils (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome
Status in gnome-shell package in Ubuntu:
New
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1895486] [NEW] [media-keys] Fn media keys with lag slow/delay on Gnome
Public bug reported:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome
Status in gnome-shell package in Ubuntu:
New
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11
[Desktop-packages] [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Dear Stefan, This thread is about a bug in "mutter 3.36.4-0ubuntu0.20.04.2". Just it. (not about arguing philosophies). As it is a bug, it ends up embarrassing people. It's normal. "Freedom of choice" doesn't mean bad software. It is a wrong idea. Also, Canonical is a company and there are people working there to fix bugs. In this case, the only person behaving like a child on this thread is you. Sorry for my sincerity, Best regards, -- 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/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Focal: Confirmed Bug description: See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
Same problem here with Ubuntu 20.04.1. -- 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/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+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 1892440] Re: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
** Summary changed: - [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards + [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards -- 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/1892440 Title: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Hi, Sujit Kumar. The solution of disabling NVIDIA drivers is not so right, because I need to use my hardware completely (use the NVIDIA hardware to compute complex matrices in my work). But thanks for your reply. -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Marco Trevisan will save us! Grazie mille! ;) -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards
** This bug has been marked a duplicate of bug 1889686 [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-for-fractional-scaling-using-Randr.patch -- 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/1892440 Title: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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
