[Bug 2022391] Re: security breach
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2022391 Title: security breach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2022391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
This bug was fixed in the package lxqt-session - 1.4.0-0ubuntu3 --- lxqt-session (1.4.0-0ubuntu3) noble; urgency=medium * Copy over GTK 3 settings by default (LP: #2047705). -- Simon Quigley Fri, 29 Dec 2023 12:36:24 -0600 ** Changed in: lxqt-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
This bug still exists in Ubuntu 22.04.3. gnome-session-bin is 42.0-1ubuntu2. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Also affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Changed in: lxqt-session (Ubuntu) Status: New => In Progress ** Changed in: lxqt-session (Ubuntu) Importance: Undecided => High ** Changed in: lxqt-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047705] [NEW] Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
Public bug reported: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg- Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg-divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047696] Re: Entire system becomes laggy for unknown reason
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2047696 Title: Entire system becomes laggy for unknown reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047696/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047696] [NEW] Entire system becomes laggy for unknown reason
You have been subscribed to a public bug: Similar to whats described in https://bugs.launchpad.net/ubuntu/+bug/2032847 the system became super laggy since yesterday. It seems like something fundamental is affected. It can happen for typing, switching between tabs in browser (chrome or firefox), VS code (switching tabs, code highlighting), opening and closing applications, opening a new tmux session. Everything takes super long. Starting chromium or vs code will result in 100% cpu usage on all 8 cores according to htop for many seconds until it settles to stay around 30 to 50% all the time. Even opening a new browser tab causes comparable CPU load. But the described behaviour also happens without running chromium or vs code. Restarting gnome shell or gdm3 doesn't help. Switching back to Wayland doesn't help, there I even get mouse freezing. In summary, it seems like something multiplies the CPU usage of a lot of different processes. I've never seen anything like that. Yesterday I thought it could be the SSD breaking, because even booting (only after restart) took very long. But fsck before booting didn't show any problems. A full shutdown made it go away yesterday, and it seemed it would only appear again when I get notifications from Slack running in chromium, so I disabled it and was able to finish the work day. Today it started out well, I switched Slack to Firefox. But then it appeared again and now a shutdown doesn't fix it anymore. I know, it sounds funny, but I'm out of ideas even to narrow the source of the problem down and I really need this machine to work for work. Since yesterday I updated a system package called gjs (manually, since it was held back in sudo apt upgrade), which seems to be related to gnome-shell, it appears with quite high CPU usage in htop. I attached the output of journalctl -b0 and memfree -h, as this was asked in the thread mentioned above. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:21:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-28 (640 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-06 (478 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Entire system becomes laggy for unknown reason https://bugs.launchpad.net/bugs/2047696 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
