[Desktop-packages] [Bug 2034664] [NEW] Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Public bug reported: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: logspam mantic ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034665] [NEW] JS ERROR: Extension tiling-assist...@ubuntu.com: TypeError: "AppSwitcherPopup" is read-only
Public bug reported: This appears in peoples' logs: Sep 07 09:04:23 ThinkPad-P14s-Gen-3 gnome-shell[2181]: JS ERROR: Extension tiling-assist...@ubuntu.com: TypeError: "AppSwitcherPopup" is read-only destroy@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/altTab.js:274:9 disable@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/extension.js:248:30 _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:200:32 _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:617:24 async*_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:773:20 ExtensionManager/<@resource:///org/gnome/shell/ui/extensionSystem.js:42:18 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 _sync@resource:///org/gnome/shell/ui/sessionMode.js:216:14 pushMode@resource:///org/gnome/shell/ui/sessionMode.js:174:14 activate@resource:///org/gnome/shell/ui/screenShield.js:666:34 lock@resource:///org/gnome/shell/ui/screenShield.js:733:14 LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:519:28 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:373:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34 @resource:///org/gnome/shell/ui/init.js:21:20 ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: logspam mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2034665 Title: JS ERROR: Extension tiling-assist...@ubuntu.com: TypeError: "AppSwitcherPopup" is read-only Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: This appears in peoples' logs: Sep 07 09:04:23 ThinkPad-P14s-Gen-3 gnome-shell[2181]: JS ERROR: Extension tiling-assist...@ubuntu.com: TypeError: "AppSwitcherPopup" is read-only destroy@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/altTab.js:274:9 disable@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/extension.js:248:30 _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:200:32 _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:617:24 async*_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:773:20 ExtensionManager/<@resource:///org/gnome/shell/ui/extensionSystem.js:42:18 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 _sync@resource:///org/gnome/shell/ui/sessionMode.js:216:14 pushMode@resource:///org/gnome/shell/ui/sessionMode.js:174:14 activate@resource:///org/gnome/shell/ui/screenShield.js:666:34 lock@resource:///org/gnome/shell/ui/screenShield.js:733:14 LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:519:28 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:373:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34
[Desktop-packages] [Bug 2034602] Re: Some GTK4 apps don't respect dark theme
** Changed in: libadwaita-1 (Ubuntu) Importance: Undecided => High ** Also affects: libadwaita-1 (Ubuntu Mantic) Importance: High Status: New ** Summary changed: - Some GTK4 apps don't respect dark theme + libadwaita applications don't respect dark theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2034602 Title: libadwaita applications don't respect dark theme Status in libadwaita-1 package in Ubuntu: New Status in libadwaita-1 source package in Mantic: New Bug description: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) 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: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2034602/+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 2034672] [NEW] gnome-shell crashed with signal 5 in g_log_structured_array()
Public bug reported: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash mantic ** Information type changed from Private to Public -- 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/2034672 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034672/+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 2034579] Re: [FFe] Use tecla to display keyboard layouts
It's a low risk change since the component is only handling the display of the keyboard layout in a gtk dialog which is a pretty isolated feature and non essential to the use of the system ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2034579 Title: [FFe] Use tecla to display keyboard layouts Status in gnome-control-center package in Ubuntu: New Bug description: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved in LP: #2026774 but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center & gnome-initial-setup integration. Specific changes 1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup 2. Have gnome-control-center and gnome-initial-setup depend on Tecla 3. Promote Tecla to main. The approved MIR is https://launchpad.net/bugs/2026774 (Both 1 and 2 have been done in Debian Unstable now.) Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… 4. Drop the Tecla patch from gnome-shell 5. Have gnome-shell depend on Tecla 6. Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034579/+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 2034672] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2034672/+attachment/5698183/+files/Stacktrace.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/2034672 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034672/+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 2034672] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2034672/+attachment/5698184/+files/StacktraceSource.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/2034672 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034672/+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 2034672] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2034672/+attachment/5698186/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2034672/+attachment/5698168/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2034672 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034672/+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 2034672] StacktraceTop.txt
** Attachment added: "StacktraceTop.txt" https://bugs.launchpad.net/bugs/2034672/+attachment/5698185/+files/StacktraceTop.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/2034672 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034672/+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 2034678] [NEW] Power profile constantly resets to Balanced
Public bug reported: Setting power profile from GNOME into power saver automatically sets it to balanced after a while. Let battery drain down to critical and have automatic power saver on. Power saver profile is on for a while. Expected: Power profile stays on power saver. Actual: In about 15 minutes the power profile is seemingly set to balanced when opening the power management window, although there is a text saying that the power profile is set to saver due to the aforementioned configuration. No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 powerprofilesctl --version 0.12 neofetch .-/+oooo+/-. `:+ss+:` -- -+ssyy+- OS: Ubuntu 23.04 x86_64 .ossdMMMNyo. Host: 20N3S2NJ00 ThinkPad T490 /ssshdmmNNmmyNhss/ Kernel: 6.2.0-32-generic +shmydMMMNy+ Uptime: 2 hours, 46 mins /hNMMMyhhhmNMMMNh/Packages: 2058 (dpkg), 9 (flatpak) .dMMMNhsshNMMMd. Shell: bash 5.2.15 +hhhyNMMNyyNMMMysss+ Resolution: 1920x1080 ossyNMMMNyMMhsshmmmhssso DE: GNOME 44.3 ossyNMMMNyMMhsshmmmhssso WM: Mutter +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Yaru [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel i5-8265U (8) @ 3.900GHz .ossdMMMNyo. GPU: Intel WhiskeyLake-U GT2 [UHD Gr -+syyy+- Memory: 7718MiB / 15640MiB `:+ss+:` .-/+oooo+/-. ** Affects: power-profiles-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2034678 Title: Power profile constantly resets to Balanced Status in power-profiles-daemon package in Ubuntu: New Bug description: Setting power profile from GNOME into power saver automatically sets it to balanced after a while. Let battery drain down to critical and have automatic power saver on. Power saver profile is on for a while. Expected: Power profile stays on power saver. Actual: In about 15 minutes the power profile is seemingly set to balanced when opening the power management window, although there is a text saying that the power profile is set to saver due to the aforementioned configuration. No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 powerprofilesctl --version 0.12 neofetch .-/+oooo+/-. `:+ss+:` -- -+ssyy+- OS: Ubuntu 23.04 x86_64 .ossdMMMNyo. Host: 20N3S2NJ00 ThinkPad T490 /ssshdmmNNmmyNhss/ Kernel: 6.2.0-32-generic +shmydMMMNy+ Uptime: 2 hours, 46 mins /hNMMMyhhhmNMMMNh/Packages: 2058 (dpkg), 9 (flatpak) .dMMMNhsshNMMMd. Shell: bash 5.2.15 +hhhyNMMNyyNMMMysss+ Resolution: 1920x1080 ossyNMMMNyMMhsshmmmhssso DE: GNOME 44.3 ossyNMMMNyMMhsshmmmhssso WM: Mutter +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Yaru [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel i5-8265U (8) @ 3.900GHz .ossdMMMNyo. GPU: Intel WhiskeyLake-U GT2 [UHD Gr -+syyy+- Memory: 7718MiB / 15640MiB `:+ss+:` .-/+oooo+/-. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2034678/+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 2034672] Re: gnome-shell crashed with signal 5 in g_log_structured_array()
There may be multiple different fixes proposed for this. The first one is: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3250 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3007 https://gitlab.gnome.org/GNOME/mutter/-/issues/3007 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/-/issues/3007 Importance: Unknown Status: Unknown ** Project changed: gnome-shell => mutter ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Medium => Critical ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Summary changed: - gnome-shell crashed with signal 5 in g_log_structured_array() + gnome-shell crashed with GLXBadDrawable on startup in a Xorg 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/2034672 Title: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2034672/+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 2014996] Re: [82SJ, Realtek ALC257, Mic, Internal] Recording problem
Try to install pulse-audio and go to record tab. That worked for me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2014996 Title: [82SJ, Realtek ALC257, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: my laptop built-in micro do not work in ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minhdinh 1684 F pulseaudio /dev/snd/controlC1: minhdinh 1684 F pulseaudio /dev/snd/controlC0: minhdinh 1684 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 16:56:32 2023 InstallationDate: Installed on 2023-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic_1 failed Symptom_Type: None of the above Title: [82SJ, Realtek ALC257, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: J8CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76501 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 Pro 14ARH7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrJ8CN27WW:bd06/16/2022:br1.27:efr1.27:svnLENOVO:pn82SJ:pvrIdeaPad5Pro14ARH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76501WIN:cvnLENOVO:ct10:cvrIdeaPad5Pro14ARH7:skuLENOVO_MT_82SJ_BU_idea_FM_IdeaPad5Pro14ARH7: dmi.product.family: IdeaPad 5 Pro 14ARH7 dmi.product.name: 82SJ dmi.product.sku: LENOVO_MT_82SJ_BU_idea_FM_IdeaPad 5 Pro 14ARH7 dmi.product.version: IdeaPad 5 Pro 14ARH7 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-04-02T13:11:37.605706 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2014996/+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 2029413] Re: Tapping the top bar with the touchscreen crashes GNOME on Xorg
** Changed in: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu Lunar) Status: Triaged => In Progress ** Tags added: fixed-in-mutter-45.0 fixed-upstream -- 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/2029413 Title: Tapping the top bar with the touchscreen crashes GNOME on Xorg Status in Mutter: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: Fix Committed Bug description: Tap the current time = Immediate crash. Tap the wifi/power combo menu = Immediate crash. Tap the top bar by itself = Immediate crash. Tap the activities button = No crash? Having the GNOME shell completely crash immediately after touching the top bar is really annoying. Especially since a lot of the functionality in the top bar is pretty important. This was previously reported as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160, but that got closed because of inactivity. This is the crash report Ubuntu generated: https://errors.ubuntu.com/oops/413de504-30f9-11ee-b2c2-fa163e55efd0. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 2 15:15:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.3-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2029413/+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 2033059] Re: Unable to add a printer
(Mantic) I still do not see any system-config-printer button in g-c-c printers tab. Is that intended? I can launch s-c-p from command line, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2033059 Title: Unable to add a printer Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Ubuntu Mantic ISO dated 20230825 also with new cups NON SNAP i can't add a printer: corrado@corrado-n02-mm-0825:~$ gnome-control-center -v 13:29:12.7220cc-printers-panel[22026]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 13:29:12.7650cc-printers-panel[22026]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 13:29:12.8234cc-printers-panel[22026]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 13:29:12.9378cc-printers-panel[22026]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 13:29:12.9703cc-printers-panel[22026]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 13:29:16.7045cc-printers-panel[22026]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fedoraproject.Config.Printing was not provided by any .service files 13:29:16.7074cc-printers-panel[22026]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files 13:29:16.7085cc-printers-panel[22026]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fedoraproject.Config.Printing was not provided by any .service files 13:29:16.7085cc-printers-panel[22026]: WARNING: Installation of the new printer failed. corrado@corrado-n02-mm-0825:~$ apt policy cups cups: Installed: 2.4.5-0ubuntu2 Candidate: 2.4.5-0ubuntu2 Version table: *** 2.4.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n02-mm-0825:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.3-1ubuntu3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Fri Aug 25 13:30:10 2023 InstallationDate: Installed on 2023-08-25 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230825) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2033059/+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 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034672 Title: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2034672/+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 2029413] Re: Tapping the top bar with the touchscreen crashes GNOME on Xorg
** Changed in: mutter Status: New => 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/2029413 Title: Tapping the top bar with the touchscreen crashes GNOME on Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: Fix Committed Bug description: Tap the current time = Immediate crash. Tap the wifi/power combo menu = Immediate crash. Tap the top bar by itself = Immediate crash. Tap the activities button = No crash? Having the GNOME shell completely crash immediately after touching the top bar is really annoying. Especially since a lot of the functionality in the top bar is pretty important. This was previously reported as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160, but that got closed because of inactivity. This is the crash report Ubuntu generated: https://errors.ubuntu.com/oops/413de504-30f9-11ee-b2c2-fa163e55efd0. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 2 15:15:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.3-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2029413/+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 1922047]
I filed bug 1851258 as a follow-up for potentially rolling out this change to the release channel. Regressions from this change like bug 1849201 will need to be fixed before that happens. -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Fix Released Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033643] Re: [SRU] libreoffice 7.5.6 for lunar
** Changed in: libreoffice (Ubuntu Lunar) Status: New => In Progress ** Description changed: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 53 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked - in.a + in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wi
[Desktop-packages] [Bug 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
** Patch added: "libreoffice_7.5.6-0ubuntu0.23.04.1_bpo22.04.1.diff" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+attachment/5698276/+files/libreoffice_7.5.6-0ubuntu0.23.04.1_bpo22.04.1.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+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 2033901] Re: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET
** Changed in: mutter Status: Unknown => 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/2033901 Title: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: With the most recent Mantic updates gnome-shell is regularly, but not every time, crashing and showing me the "Oops!" screen and forcing a logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that still isn't supported in Wayland). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:57:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1703 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033901/+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 2034602] Re: libadwaita applications don't respect dark theme
This bug was caused by the xdg-desktop-portal update and will be fixed with gnome-session-common 44.0-4ubuntu1 ** Package changed: libadwaita-1 (Ubuntu Mantic) => gnome-session (Ubuntu Mantic) ** Changed in: gnome-session (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: gnome-session (Ubuntu Mantic) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2034602 Title: libadwaita applications don't respect dark theme Status in gnome-session package in Ubuntu: Fix Committed Status in gnome-session source package in Mantic: Fix Committed Bug description: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) 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: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2034602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033939] Re: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is
I figured it out. For some reason, gnome-remote-desktop listens on port 3390 instead of 3389. Connecting to port 3390 works after adding required firewall rule using ufw. Is there a way to revert back to the original port? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2033939 Title: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is established Status in gnome-remote-desktop package in Ubuntu: New Bug description: service was working until latest update of gnome-remote-desktop yesterday. managed to reproduce on daily build. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-remote-desktop 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 03:13:31 2023 InstallationDate: Installed on 2023-09-01 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2033939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034722] [NEW] High CPU usage causing slowdown
Public bug reported: I have been experiencing high CPU usage from gnome-shell since upgrading to Mantic. htop shows gnome-shell consuming around 120% of the CPU. This ends up resulting a very sluggish feeling desktop. # System Details Report --- ## Report details - **Date generated:** 2023-09-07 16:31:07 ## Hardware Information: - **Hardware Model:** Apple Inc. MacBookPro12,1 - **Memory:** 8.0 GiB - **Processor:** Intel® Core™ i5-5257U × 4 - **Graphics:**Intel® Iris® Graphics 6100 (BDW GT3) - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**184.0.0.0.0 - **OS Name:** Ubuntu Mantic Minotaur (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.rc - **Windowing System:**Wayland - **Kernel Version:** Linux 6.3.0-7-generic ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 16:25:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (525 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2034722 Title: High CPU usage causing slowdown Status in gnome-shell package in Ubuntu: New Bug description: I have been experiencing high CPU usage from gnome-shell since upgrading to Mantic. htop shows gnome-shell consuming around 120% of the CPU. This ends up resulting a very sluggish feeling desktop. # System Details Report --- ## Report details - **Date generated:** 2023-09-07 16:31:07 ## Hardware Information: - **Hardware Model:** Apple Inc. MacBookPro12,1 - **Memory:** 8.0 GiB - **Processor:** Intel® Core™ i5-5257U × 4 - **Graphics:**Intel® Iris® Graphics 6100 (BDW GT3) - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**184.0.0.0.0 - **OS Name:** Ubuntu Mantic Minotaur (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.rc - **Windowing System:**Wayland - **Kernel Version:** Linux 6.3.0-7-generic ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 16:25:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (525 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034722/+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 2034724] [NEW] minimize, maximize, close buttons in title bar become invisible
Public bug reported: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages ** Attachment added: "2023-09-07_11-34.png" https://bugs.launchpad.net/bugs/2034724/+attachment/5698308/+files/2023-09-07_11-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
** Attachment added: "2023-09-07_11-35.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+attachment/5698315/+files/2023-09-07_11-35.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 2034722] Re: High CPU usage causing slowdown
Taking a look at the log via journalctl I'm noticing non stop spam relating to KMS. -- 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/2034722 Title: High CPU usage causing slowdown Status in gnome-shell package in Ubuntu: New Bug description: I have been experiencing high CPU usage from gnome-shell since upgrading to Mantic. htop shows gnome-shell consuming around 120% of the CPU. This ends up resulting a very sluggish feeling desktop. # System Details Report --- ## Report details - **Date generated:** 2023-09-07 16:31:07 ## Hardware Information: - **Hardware Model:** Apple Inc. MacBookPro12,1 - **Memory:** 8.0 GiB - **Processor:** Intel® Core™ i5-5257U × 4 - **Graphics:**Intel® Iris® Graphics 6100 (BDW GT3) - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**184.0.0.0.0 - **OS Name:** Ubuntu Mantic Minotaur (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.rc - **Windowing System:**Wayland - **Kernel Version:** Linux 6.3.0-7-generic ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 16:25:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (525 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034722/+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 2034121] Re: Support goodix fingerprint [27c6:633C]
** Changed in: libfprint (Ubuntu) Status: New => Fix Released ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27c6:633C] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Committed Bug description: [27c6:633C] include in https://salsa.debian.org/ubuntu-dev- team/libfprint/-/commit/96645eaa7ae99a12e08b65e24a8610a3c57a92b3 [Impact] * Support goodix [27c6:633C] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+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 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements
** Summary changed: - Gnome Terminal "Copy As HTML" produces HTML containing depreciated features + Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements Status in gnome-terminal package in Ubuntu: Confirmed Bug description: If you highlight text in gnome-terminal and right-click it, you get a "Copy as HTML" option. The HTML that gnome-terminal generates when using that feature contains tags. font tags were depreciated in HTML 4.01, and made obsolete entirely in HTML 5. (See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font). Attached is a sample of the HTML generated by gnome-terminal. The correct behavior would be to include style info such as font colors inside the "style" attribute of a tag, rather than using tags. That is to say, should be replaced by , and should be replaced by This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu. I've attached both a copy of the output of Copy As HTML, containing the deprecated tag. Below is a fixed version of this output that doesn't rely on the tag: alecto@styx:~$ ls apps Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage gitkraken session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage sources alecto@styx:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1938605/+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 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements
** Also affects: gnome-terminal (Debian) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #8001 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8001 ** Also affects: gnome-terminal via https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8001 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal package in Debian: New Bug description: If you highlight text in gnome-terminal and right-click it, you get a "Copy as HTML" option. The HTML that gnome-terminal generates when using that feature contains tags. font tags were depreciated in HTML 4.01, and made obsolete entirely in HTML 5. (See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font). Attached is a sample of the HTML generated by gnome-terminal. The correct behavior would be to include style info such as font colors inside the "style" attribute of a tag, rather than using tags. That is to say, should be replaced by , and should be replaced by This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu. I've attached both a copy of the output of Copy As HTML, containing the deprecated tag. Below is a fixed version of this output that doesn't rely on the tag: alecto@styx:~$ ls apps Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage gitkraken session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage sources alecto@styx:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1938605/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
Of course, this is fine. I don't see libreoffice in the jammy queue, so feel free to upload :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
@mapreri Thanks for taking a look. :) Unfortunately this will have to wait for the SRU to get processed first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+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 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements
** Changed in: gnome-terminal Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal package in Debian: New Bug description: If you highlight text in gnome-terminal and right-click it, you get a "Copy as HTML" option. The HTML that gnome-terminal generates when using that feature contains tags. font tags were depreciated in HTML 4.01, and made obsolete entirely in HTML 5. (See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font). Attached is a sample of the HTML generated by gnome-terminal. The correct behavior would be to include style info such as font colors inside the "style" attribute of a tag, rather than using tags. That is to say, should be replaced by , and should be replaced by This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu. I've attached both a copy of the output of Copy As HTML, containing the deprecated tag. Below is a fixed version of this output that doesn't rely on the tag: alecto@styx:~$ ls apps Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage gitkraken session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage sources alecto@styx:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1938605/+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 2034602] Re: libadwaita applications don't respect dark theme
I just got the update and now everything is working again as expected. Thank you everybody! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2034602 Title: libadwaita applications don't respect dark theme Status in gnome-session package in Ubuntu: Fix Committed Status in gnome-session source package in Mantic: Fix Committed Bug description: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) 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: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2034602/+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 1971434] Re: Display powersave only blanks, but does not turn off
I'm on 22.04 and can also confirm that the fix in #33 worked for me. Thanks for the help Daniel! -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Why do they mess with that math symbol in gnome-desktop? Anyway, the issue surfaced because of the font changes I made. Previously DejaVu Sans was used to render the Ratio character, and now, when the fonts-dejavu-core package is not present, DejaVu Sans Mono seems to be used instead. Hence the extra whitespace. I uploaded a language-selector change so it uses Noto Sans Math for rendering Ratio. https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/language- selector/commit/?id=fc7ec106 ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Changed in: language-selector (Ubuntu) Importance: Undecided => Medium ** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Committed Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Thanks Gunnar! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Committed Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
This bug was fixed in the package libfprint - 1:1.94.6+tod1-0ubuntu3 --- libfprint (1:1.94.6+tod1-0ubuntu3) mantic; urgency=medium [ Marco Trevisan (Treviño) ] * Update changelog * Merge with debian changes * debian/patches: Remove execution bit from test asset [ Debian Janitor ] * Apply multi-arch hints. + libfprint-2-2: Drop Multi-Arch: same. * Trim trailing whitespace. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse. * Update standards version to 4.6.1, no changes needed. * Remove constraints unnecessary since buster (oldstable) [ Andy Chi ] * d/p/synaptics-fix-enroll_identify-problem-after-user-reset-da.patch (LP: #2034481) -- Marco Trevisan (Treviño) Thu, 07 Sep 2023 17:59:33 +0200 ** Changed in: libfprint (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) Status in OEM Priority Project: Confirmed Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Committed Status in libfprint source package in Lunar: New Status in libfprint source package in Mantic: Fix Released Bug description: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/433 [Impact] * HP laptops provide clear fingerprint from BIOS, user can enroll finger on Synaptics device after clear from BIOS. [Test Plan] * Enroll one random finger * Reboot and enter BIOS to reset fingerprint device (HP laptops) * Boot into system and re-enroll the finger * Login system with enrolled finger [Where problems could occur] * The patch only fix the issue with clear fingerprint from BIOS on Synaptics device, won't impact other vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
Right. Just upload and ping the bug once that's through! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+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 2034602] Re: libadwaita applications don't respect dark theme
This bug was fixed in the package gnome-session - 44.0-4ubuntu1
---
gnome-session (44.0-4ubuntu1) mantic; urgency=medium
* Merge with Debian to fix Dark Theme regression (LP: #2034602).
Remaining changes:
- debian/control.in:
+ Recommend session-migration
+ Move xwayland dependency to gnome-session and make gnome-session
Arch: any
+ Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
+ Add unity-session
- debian/rules: Ensure pot file is generated to translate session files
- Split ubuntu-session out of gnome-session.
- debian/data: Add old-style systemd user session used by Unity
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
Moved registering gnome-session binary as a session manager to
gnome-session-bin package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
Ubuntu):
debian/gnome-session-common.dirs, gnome-session-common.install,
gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/ubuntu/support_autostart_delay.patch:
+ Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/ubuntu/ubuntu_sessions.patch:
+ Add ubuntu sessions
- debian/patches/ubuntu/remove_session_saving_from_gui.patch:
+ Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/ubuntu/add_sessionmigration.patch:
+ launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/ubuntu/dbus_request_shutdown.patch:
+ Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ubuntu/ignore_gsettings_region.patch:
+ Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
+ Don't merge translations into gnome-session-properties.desktop
- debian/ubuntu-settings-migrate-to-defaults.18.10.1.py:
+ Migrate users using old default ubuntu-settings to current ones
- debian/xdg_dirs_desktop_session.sh: Install a new script into
/etc/profile.d to prepend a $DESKTOP_SESSION related directory to
$XDG_{CONFIG,DATA}_DIRS.
gnome-session (44.0-4) unstable; urgency=medium
* Cherry-pick 2 more patches from upstream:
- Also set LC_ADDRESS and LC_TELEPHONE from configured user region
- Make gsm-system's return_false actually return FALSE
gnome-session (44.0-3) unstable; urgency=medium
* Team upload
* d/p/data-Add-gnome-portals.conf.patch:
Add patch proposed upstream to add a gnome-portals.conf for use by
xdg-desktop-portal >= 1.17.1.
This is the replacement for the UseIn field in .portal files, and is
analogous to how we ship a mimeapps.list to configure preferred apps
to handle MIME types in GNOME.
* d/gnome-session-common.install: Install gnome-portals.conf
-- Jeremy Bícha Thu, 07 Sep 2023 10:35:01 -0400
** Changed in: gnome-session (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2034602
Title:
libadwaita applications don't respect dark theme
Status in gnome-session package in Ubuntu:
Fix Released
Status in gnome-session source package in Mantic:
Fix Released
Bug description:
I set the dark theme on the Settings, but just the Shell and GTK3 apps
(Terminator) respect this change. The GNOME Control Center and the
Text Editor keep using the light theme.
I deleted my ~/.config/dconf directory, and after that everything
became white (understandable, since that's the default theme), but I
couldn't change. I think it's something related to GTK4 apps.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45~rc-1ubuntu2
Uname: Linux 6.5.1-zabbly+ x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 6 14:00:59 2023
InstallationDate: Installed on 2021-11-26 (649 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago)
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
[Desktop-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
This bug was fixed in the package language-selector - 0.224 --- language-selector (0.224) mantic; urgency=medium * data/pkg_depends: - Pull also fcitx5-frontend-qt6 for Chinese (non-GNOME) users. * Prefer Noto Sans Math - Makes that font used instead of DejaVu Sans Mono for rendering the Ratio character in the clock (LP: #2033377). -- Gunnar Hjalmarsson Thu, 07 Sep 2023 20:30:37 +0200 ** Changed in: language-selector (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
Your screenshot is of Firefox, right? Have you noticed this issue in any other apps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
I believe so. For example I believe I've noticed it in the Settings app. I will keep an eye out and confirm here when I see it in another app. -- 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/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
*** This bug is a duplicate of bug 2002624 *** https://bugs.launchpad.net/bugs/2002624 Ok, I believe that's a Firefox issue so I'm marking this a duplicate of a previously reported issue. There is a recent gnome-control-center bug with one of its pages: LP: #2033658 ** This bug has been marked a duplicate of bug 2002624 firefox maximize button gets hidden after the screen gets (un)locked -- 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/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 2002624] Re: firefox maximize button gets hidden after the screen gets (un)locked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2002624 Title: firefox maximize button gets hidden after the screen gets (un)locked Status in firefox package in Ubuntu: Confirmed Bug description: check the attached video, after the screenasaver gets activated firefox maximize and close buttons disappears ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jan 12 09:45:38 2023 InstallationDate: Installed on 2022-09-30 (103 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002624/+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 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements
Fix was not released upstream. It was reverted. https://gitlab.gnome.org/GNOME/vte/-/issues/2604 https://gitlab.gnome.org/GNOME/vte/-/issues/2625 GNOME is holding back standards compliance because of the current Matrix Protocol. ** Bug watch added: gitlab.gnome.org/GNOME/vte/-/issues #2604 https://gitlab.gnome.org/GNOME/vte/-/issues/2604 ** Bug watch added: gitlab.gnome.org/GNOME/vte/-/issues #2625 https://gitlab.gnome.org/GNOME/vte/-/issues/2625 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal package in Debian: New Bug description: If you highlight text in gnome-terminal and right-click it, you get a "Copy as HTML" option. The HTML that gnome-terminal generates when using that feature contains tags. font tags were depreciated in HTML 4.01, and made obsolete entirely in HTML 5. (See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font). Attached is a sample of the HTML generated by gnome-terminal. The correct behavior would be to include style info such as font colors inside the "style" attribute of a tag, rather than using tags. That is to say, should be replaced by , and should be replaced by This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu. I've attached both a copy of the output of Copy As HTML, containing the deprecated tag. Below is a fixed version of this output that doesn't rely on the tag: alecto@styx:~$ ls apps Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage gitkraken session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage sources alecto@styx:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1938605/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
For the record: The different results depending on locale is a "translation" matter. While the default time separator is \u2236, it has been "translated" for e.g. en_GB in Ubuntu into \u003A: https://translations.launchpad.net/ubuntu/mantic/+source/gnome- desktop/+pots/gnome-desktop-3.0/en_GB/24 $ printf '\u2236\n' ∶ $ printf '\u003A\n' : So with the en_GB.UTF-8 locale it displays a regular colon character, which the Ubuntu font can render. (Daniel: I can't explain how you hid the issue by using en_AU.UTF-8, though.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Confirmed Status in language-pack-gnome-en package in Ubuntu: New Status in language-pack-gnome-en-base package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034763] [NEW] Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2
You have been subscribed to a public bug: I use Plasma desktop in Mantic. With the latest versions of glib2.0 and xdg-desktop-portal all Flatpak applications ignore host settings like GTK theme, cursor theme and window controls position. I can get proper appearance only in the following state: > sudo apt list --upgradable Listing... Done libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1] xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 1.16.0-3ubuntu1] Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so I don't know exactly which package causes this incompatibility. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2 https://bugs.launchpad.net/bugs/2034763 You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2
** Package changed: ubuntu => glib2.0 (Ubuntu) ** Also affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2034763 Title: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2 Status in glib2.0 package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: I use Plasma desktop in Mantic. With the latest versions of glib2.0 and xdg-desktop-portal all Flatpak applications ignore host settings like GTK theme, cursor theme and window controls position. I can get proper appearance only in the following state: > sudo apt list --upgradable Listing... Done libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1] libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1] xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 1.16.0-3ubuntu1] Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so I don't know exactly which package causes this incompatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2034763/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
*** This bug is a duplicate of bug 2002624 *** https://bugs.launchpad.net/bugs/2002624 I am not able to reproduce this merely by locking and unlocking my screen so I don't think this is the same as #2002624. -- 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/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in gnome-shell package in Ubuntu: New Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
This bug was fixed in the package gsettings-desktop-schemas - 45~rc-1ubuntu1 --- gsettings-desktop-schemas (45~rc-1ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations * Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (45~rc-1) unstable; urgency=medium * New upstream release - media-handling: Don't autostart software by default when media is inserted (LP: #1983778, LP: #1617620) * Add Breaks against packages that used dropped toggle-shaded * Drop obsolete Breaks gsettings-desktop-schemas (44.0-2) unstable; urgency=medium * Update standards version to 4.6.2, no changes needed * Release to unstable -- Jeremy Bícha Thu, 07 Sep 2023 13:24:00 -0400 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+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 1617620] Re: Autorun files from Removable Media
This bug was fixed in the package gsettings-desktop-schemas - 45~rc-1ubuntu1 --- gsettings-desktop-schemas (45~rc-1ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations * Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (45~rc-1) unstable; urgency=medium * New upstream release - media-handling: Don't autostart software by default when media is inserted (LP: #1983778, LP: #1617620) * Add Breaks against packages that used dropped toggle-shaded * Drop obsolete Breaks gsettings-desktop-schemas (44.0-2) unstable; urgency=medium * Update standards version to 4.6.2, no changes needed * Release to unstable -- Jeremy Bícha Thu, 07 Sep 2023 13:24:00 -0400 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1617620 Title: Autorun files from Removable Media Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Ubuntu 16 is still automatically executing software that resides in an external resource (removable media), such as USB or CD. I don't need to tell you how bad this is.. --- You can see the default value that allows to autoplay / autorun files by doing the following steps: 1. In Ubuntu 16.04, go to Settings -> Details. 2. In the left pane choose "Removable Media". 3. On the right pane you'll see "Software", while the value in the drop-down menu is "Run Software". --- A fix suggestion: Instead of "Run Software", the default value should be "Do nothing". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1617620/+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 2034724] Re: minimize, maximize, close buttons in title bar become invisible
Ok, unmarking as duplicate. Locking the screen might be a trigger, but in my case, this issue only happens sometimes. ** This bug is no longer a duplicate of bug 2002624 firefox maximize button gets hidden after the screen gets (un)locked ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Package changed: gnome-shell (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2034724 Title: minimize, maximize, close buttons in title bar become invisible Status in firefox package in Ubuntu: Confirmed Bug description: Recently when I go to minimize, maximize, or close a window (I have the minimize and maximize buttons enabled in Tweaks) I discover that the buttons are invisible. I know they're there, just invisible, because I can click where they should be visible and the expected thing happens. If I quit and restart the application in question the buttons become visible again. This only affects some windows (usually just one) at any given time, not all of my windows. See attached screenshots for an example of what I'm talking about. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:37:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1709 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2034724/+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 2033569] Re: suddenly choked on multiseat config in a way that survives reboots and even purging it
Found a solution. There were two separate issues: FIRST ISSUE Apparently systemd likes to start up lightdm early, so early that on a reasonably fast system the GPU driver won't be ready in time ... (I thought this was what systemd's dependency handling was for, but never mind.) This seems to be a long-standing issue; it's neither multiseat- nor GPU- driver-specific. And considering this is just a budget AMD box, albeit a new one, it's going to bite more and more people in future. My hypothesis re. why the first few boots with lightdm worked is that I was still in the middle of setting up the box, i.e. a lot changed from one boot to the next. Either one of those changes triggered the timing issue, or "clean" boots are faster per se. The workarounds detailed in the Arch Wiki (https://wiki.archlinux.org/title/LightDM#LightDM_does_not_appear_or_monitor_only_displays_TTY_output) both work, to wit: 1) Add [LightDM] logind-check-graphical=true in /etc/lightdm/lightdm.conf - OR - 2) Enable early KMS by adding your GPU driver module to /etc/initramfs- tools/modules and running update-initramfs -k all -u. SECOND ISSUE: At some point while trying to fix this I deleted /var/lib/lightdm as well, which is lightdm's home directory. Since purging lightdm does not remove the lightdm user, reinstalling it will not (re)create this directory. Unfortunately the symptoms are the same as above--lightdm goes into a restart loop, then gives up. Now, the second issue probably isn't a bug, though the postinst script could at least print a warning if the home directory isn't present and writeable, but the first one is, IMHO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/2033569 Title: suddenly choked on multiseat config in a way that survives reboots and even purging it Status in lightdm package in Ubuntu: New Bug description: I have a bog-standard loginctl multiseat setup, using lightdm because of #2033323. Except for the lack of session locking, it worked beautifully, across multiple reboots. Until it didn't. Box woke from suspend, and to be fair was acting strangely even then (Steam suddenly tried to launch using the iGPU), so suspend may well be broken on this box, but if so, that's a separate issue. Anyway, I rebooted, no lightdm greeter to be seen, the screen on seat1 was black. I did not have easy access to seat0 at the time. The journal has, looping: systemd[1]: Failed to start Detect the available GPUs and deal with any system changes. systemd[1]: lightdm.service: Start request repeated too quickly. token systemd[1]: lightdm.service: Failed with result 'exit-code'. token systemd[1]: Failed to start Light Display Manager. The first line is from gpu-manager.service, whose log contains Vendor/Device Id: 1002:164e BusID "PCI:110@0:0:0" Is boot vga? no Error: can't access /sys/bus/pci/devices/:6e:00.0/driver The device is not bound to any driver. Vendor/Device Id: 1002:73ff BusID "PCI:3@0:0:0" Is boot vga? yes Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri x-0 log has vesa: Ignoring device with a bound kernel driver vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) Scary. Thing is, both the iGPU and the dGPU are claimed by amdgpu, their "driver" symlink is accessible just fine. Switch back to gdm via dpkg- reconfigure, it boots up fine again. It's just lightdm that's hosed. I tried purging lightdm and lightdm-gtk-greeter, along with and /var/lib/lightdm, and reinstalling the packages, but no dice. What does work is starting lightdm.service manually over ssh: It takes about 1-4 tries for both gpu-manager and lightdm to successfully launch and bring up both greeters. Reboot, and it fails again. Some kind of race condition due to too lax timing and/or dependencies in the lightdm service file? Something unrelated changed the order and or speed at which systemd executes the service files, i.e. it worked by accident before and now it doesn't? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 Uname: Linux 6.4.12-060412-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 31 03:16:56 2023 InstallationDate: Installed on 2023-08-25 (5 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2033569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1846790] Re: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share)
For the record, I can confirm that the version of LO that ships with 22.04 is no longer affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1846790 Title: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: [Reported via ubuntu-bug, I'm assuming it has gathered all relevant system info. More, especially on the Samba server, if required, is available on request.] What I'm trying to do: Save a file whose name contains a '#' character to a Samba share accessed via a GVFS smb:// path. Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test #1.odt" on a Samba share mounted via Nautilus. Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or File-Open, make some changes, save it & quit. What I'm expecting to happen: The file shows up under the assigned name on both the client and the Samba server (in case of a new file); or the existing file now contains the changes made (in case of an existing file being modified). Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory. Ex. 2: I'd expect "Test #2.odt" to contain my changes. What happens instead: Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen from the client, "Test " [note the space at the end] on the server. Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" (client), or "Test " (server) is created with the saved data. Effectively, the save operation does not succeed -- without any error message. Analysis: This is based on experiments with more complex filenames. Somehow, when LibreOffice saves a file in this constellation, the filename gets truncated at the first '#', inclusive, first, suffix and all. (This in turn leaves a filename ending in a space, which isn't legal under Windows, so Samba's name mangling kicks in.) The problem does not occur with local files or on a sshfs-mount. Gedit has no problem even on smb://. It's unclear whether '#' is the only character affected. Some kind of URL handling/escaping bug in LibreOffice's GIO support? In any case, this cost me a day of work. (By the time I realised my changes hadn't actually been lost but landed in a new, cryptically- named file, I'd already recreated it to meet the deadline.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 17:12:21 2019 InstallationDate: Installed on 2019-09-23 (10 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Description changed: + [ Impact ] + the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 + [ Test case ] + + 1. When in GDM, insert a smartcard + 2. The GDM interface should require for an user + 3. The user should be set (or empty may be provided, +depending on sssd configuration) + 4. The smartcard PIN should be requested and once introduce the +user must login. + + Note that this requires configuring sssd before, a simple local + configuration could require having sssd.conf filled with: + + ```ini + [sssd] + enable_files_domain = True + services = pam + + [certmap/implicit_files/$USER] + matchrule = .*YOUR CARD IDENTIFIER* + + [pam] + pam_cert_auth = True + ``` + + The UI authentication can also be simulated via pamtester: + + # Must be ran as user + sudo apt install pamtester + pamtester -v gdm-smartcard $USER authenticate + + Expected output is + + pamtester -v gdm-smartcard ubuntu authenticate + pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) + pamtester: performing operation - authenticate + PIN for Test Organization Sub Int Token: + pamtester: successfully authenticated + + [ Regression potential ] + + Smartcard authentication using custom methods using via a custom + configured system nss database may not work anymore. + + --- + + ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) - InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - SourcePackage: gdm3 + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 ** Description changed: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, -depending on sssd configuration) + depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the -user must login. + user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated + --- + + Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + + - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh + - sudo sssd-gdm-smartcard-pam-auth-tester.sh + + The script will generate some fake CA authority, issue some + certificates, will install them in some software-based smartcards (using + softhsm2) and test that they work properly to login with gdm-smartcard. + + Using `WAIT` environment variable set (to any value) will make it to + restart gdm at each iteration so that an user can try to access, using + the username that launched the script and the pin of 123456. + [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersion
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Andreas: - I've now added SSSD to the bug - I had not uploaded the remaining bits yet as I was waiting for SSSD to hit the queue first - GNOME settings daemon is also uploaded now to the queue - GDM will be uploaded soon by Jeremy The bug has now been updated to have a proper SRU template, with all the tests required to check all the 3 packages. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu) Status: New => In Progress ** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** No longer affects: gdm3 (Ubuntu Focal) ** No longer affects: gnome-settings-daemon (Ubuntu Focal) ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sssd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-settings-daemon (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: sssd (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gdm3 (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu) Status: In Progress => Fix Released -- 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/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: In Progress Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured syste
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Description changed: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): - https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ - sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - - sudo sssd-gdm-smartcard-pam-auth-tester.sh + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh + - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm-smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 -- 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/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: In Progress Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER
[Desktop-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
> (Daniel: I can't explain how you hid the issue by using en_AU.UTF-8, though.) Maybe en_AU inherits from en_GB? ** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: language-pack-gnome-en (Ubuntu) Status: New => Won't Fix ** Changed in: language-pack-gnome-en-base (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Won't Fix Status in language-pack-gnome-en package in Ubuntu: Won't Fix Status in language-pack-gnome-en-base package in Ubuntu: Won't Fix Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034722] Re: High CPU usage causing slowdown
Those KMS messages are due to MUTTER_DEBUG=kms which should not be set by default. Do you have it in /etc/environment or /etc/environment.d/* ? There's also a little bit of bug 2034664 in your log. ** Tags added: logspam ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2034722 Title: High CPU usage causing slowdown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been experiencing high CPU usage from gnome-shell since upgrading to Mantic. htop shows gnome-shell consuming around 120% of the CPU. This ends up resulting a very sluggish feeling desktop. # System Details Report --- ## Report details - **Date generated:** 2023-09-07 16:31:07 ## Hardware Information: - **Hardware Model:** Apple Inc. MacBookPro12,1 - **Memory:** 8.0 GiB - **Processor:** Intel® Core™ i5-5257U × 4 - **Graphics:**Intel® Iris® Graphics 6100 (BDW GT3) - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**184.0.0.0.0 - **OS Name:** Ubuntu Mantic Minotaur (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.rc - **Windowing System:**Wayland - **Kernel Version:** Linux 6.3.0-7-generic ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 16:25:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (525 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034722/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen
Thanks for the fix Gunnar. The reason I didn't raise it with you earlier was because I figured a better solution would be to: 1. Patch to revert to a colon in the default US English translation. 2. Propose to upstream to not use RATIO in future because fonts don't often implement the Mathematical Operators block. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2033377 Title: New whitespace between digits and colon in time at top of desktop screen Status in gnome-desktop package in Ubuntu: Won't Fix Status in language-pack-gnome-en package in Ubuntu: Won't Fix Status in language-pack-gnome-en-base package in Ubuntu: Won't Fix Status in language-selector package in Ubuntu: Fix Released Bug description: This has been confirmed in the daily canary image and the daily normal mantic image. This whitespace didn't exist in older images or in previous releases. An image will be attached in the comments --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-08-30 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) Package: gnome-shell 44.3-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Tags: mantic wayland-session Uname: Linux 6.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 1841810] Re: Ubuntu login screen does not show full name if it's slightly too long (but not really that long)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6989 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6989 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6989 Importance: Unknown Status: Unknown -- 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/1841810 Title: Ubuntu login screen does not show full name if it's slightly too long (but not really that long) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: I use Ubuntu 18.04 LTS with gdm3 3.28.3 My native language is Spanish and my fullname use accents and hyphens (Néstor Rodríguez-Triana Domínguez) but it not appear in the gdm3 login screen, only my username (nrtriana). My locale is configured properly as: LANG=es_ES.UTF-8 LANGUAGE=es_ES LC_CTYPE="es_ES.UTF-8" LC_NUMERIC="es_ES.UTF-8" LC_TIME="es_ES.UTF-8" LC_COLLATE="es_ES.UTF-8" LC_MONETARY="es_ES.UTF-8" LC_MESSAGES="es_ES.UTF-8" LC_PAPER="es_ES.UTF-8" LC_NAME="es_ES.UTF-8" LC_ADDRESS="es_ES.UTF-8" LC_TELEPHONE="es_ES.UTF-8" LC_MEASUREMENT="es_ES.UTF-8" LC_IDENTIFICATION="es_ES.UTF-8" LC_ALL=es_ES.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841810/+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 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session
The latest proposed fixes are: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3255 https://salsa.debian.org/gnome-team/mutter/-/merge_requests/106 -- 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/2034672 Title: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2034672/+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 2034895] [NEW] [Mantic] No system-config-printer button in Printers tab
Public bug reported: Hi, Since cups-deb has been finally chosen, this useful button is missing. At least, system-config-printer should be offered in apps list, not only in command line. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2034895 Title: [Mantic] No system-config-printer button in Printers tab Status in gnome-control-center package in Ubuntu: New Bug description: Hi, Since cups-deb has been finally chosen, this useful button is missing. At least, system-config-printer should be offered in apps list, not only in command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034895/+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 2011281]
In bug description: 1> when I went to use my saved passwords in chromium today, I found that they were absent. In your last comment: 2> chromium continues to be able to *use* my saved passwords. But I don't know where they're actually saved Which one is correct/up to date? Likewise for 3> I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry and 4> But I don't know where they're actually saved It looks impossible that Chromium is accessing passwords from 'Login Data.old'; there is no longer any reference to that, anywhere, so I think quote 3 might not be up to date. Depending on the situation you could try --password-store=basic, but given the already buggy circumstances, better have those configuration files backed up. Without a reproducible case and access to those data files, which of course you must not share as it contains passwords, this is hard to debug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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
