[Desktop-packages] [Bug 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO
** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-22.04-feature-freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956350 Title: xdg-desktop-portal-gnome missing in Jammy ISO Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome is missing. xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on Wayland. see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074 apt show xdg-desktop-portal-gnome says: Non-GNOME GTK-based desktop environments should normally use xdg-desktop-portal-gtk or their own portal implementation instead of this one. and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be included in the ISO image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+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 1956390] Re: User profile picture color not selected until you unlock and click on the letter.
Steps to reproduce 1. Install Ubuntu 2. Notice blank colorless human outline on first login profile and privilege elevation GUI textboxes. 3. Go to settings. 4. Click Users. 5. Click icon next to username but don't click on any profile picture or even the letter with color itself. 6. Go back to login through lock or other method. Also look at the icon in privilege elevation popup. It is now colored with the first letter of your username. -- 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/1956390 Title: User profile picture color not selected until you unlock and click on the letter. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is no color on a picture-less user profile picture unless you go to Users, click unlock, click the icon, and select the default with the first character of your username. If the color is unintentional altogether, this is still a bug, just in reverse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956390/+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 1956801] xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for()
StacktraceTop: gdk_window_set_transient_for (window=0x0, parent=0x55efae2db6c0) at ../../../../gdk/gdkwindow.c:10545 popover_realize.part.0.lto_priv.0 (widget=widget@entry=0x7f68540357b0, popover=popover@entry=0x55efadb751b0, window=window@entry=0x55efae1ac430) at ../../../../gtk/gtkwindow.c:6882 popover_realize (window=0x55efae1ac430, popover=0x55efadb751b0, widget=0x7f68540357b0) at ../../../../gtk/a11y/gtkcontaineraccessible.c:218 _gtk_window_add_popover (window=0x55efae1ac430, popover=0x7f68540357b0, parent=0x55efae2623c0, clamp_allocation=) at ../../../../gtk/gtkwindow.c:12649 gtk_popover_update_relative_to (popover=0x7f68540357b0, relative_to=) at ../../../../gtk/gtkpopover.c:2168 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1956801 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.12.0-1 Uname: Linux 5.15.13-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 8 00:03:34 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk InstallationDate: Installed on 2021-12-23 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211222) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk SegvAnalysis: Segfault happened at: 0x7f686770ceb4 : mov0x18(%rdi),%rax PC (0x7f686770ceb4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: gdk_window_set_transient_for () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_popover_set_relative_to () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1956801/+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 1956801] [NEW] xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for()
Public bug reported: crash ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.12.0-1 Uname: Linux 5.15.13-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 8 00:03:34 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk InstallationDate: Installed on 2021-12-23 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211222) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk SegvAnalysis: Segfault happened at: 0x7f686770ceb4 : mov 0x18(%rdi),%rax PC (0x7f686770ceb4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: gdk_window_set_transient_for () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_popover_set_relative_to () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo separator: ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1956801 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.12.0-1 Uname: Linux 5.15.13-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 8 00:03:34 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk InstallationDate: Installed on 2021-12-23 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211222) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk SegvAnalysis: Segfault happened at: 0x7f686770ceb4 : mov0x18(%rdi),%rax PC (0x7f686770ceb4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: gdk_window_set_transient_for () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_popover_set_relative_to () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1956801/+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 1956637] Re: I have disabled the touchpad through settings, but that has no effect
To try something else I uninstalled touchpad-indicator and not the Settings for the touchpad work as expected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1956637 Title: I have disabled the touchpad through settings, but that has no effect Status in ubuntu-settings package in Ubuntu: New Bug description: I'm running Ubuntu 21.10 on a laptop Ubuntu-settings is V 21.10.4 Disabling the touchpad on my new laptop has no effect. The only way to disable the touchpad was to install Touchpad-indicator ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-settings 21.10.4 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 12:05:10 2022 InstallationDate: Installed on 2021-12-31 (6 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1956637/+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 1318327] Re: Can't open .webp files
There is available code to fix that. Someone could package so we can get it working in Jammy? I think it's quite important since it's a 5-years long release. Here is the code: https://github.com/aruiz/webp-pixbuf-loader -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1318327 Title: Can't open .webp files Status in Eye of GNOME: Confirmed Status in eog package in Ubuntu: Triaged Bug description: Please, add webp support. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1318327/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu) -- 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/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1951878/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Jay, a belated thank-you for that link! It's now a much nicer option until the fix rolls out to regular users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1932328]
Confirming this bug persists in TB 91 under Pop!_OS 21.10. A fix for this was apparently [committed](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2027) several months ago, but (per [this comment](https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/comments/64)) users will not see it until updating to gnome 40.6. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1728342] Re: Some applications disable "Night Light" and it is not reenabled upon exiting application
It happens on Ubuntu 20.04 as well -- 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/1728342 Title: Some applications disable "Night Light" and it is not reenabled upon exiting application Status in gnome-shell package in Ubuntu: Confirmed Bug description: Some applications disable "Night Light" and it is not reenabled upon exiting application. Examples: Minecraft Nvidia Settings World of Warcraft via Wine. You can go into settings and manually toggle "Night Light" off and back on in order to get the blue light reduction to take effect again. Not all application/games will cause this. Rocket League, Civilization 5 are examples that do not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 29 00:50:51 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: 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-shell/+bug/1728342/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
With gnome-shell 3.36.9-0ubuntu0.20.04.2 I too see this with only the built-in "Desktop Icons", "Ubuntu AppIndicators", "Ubuntu Dock" extensions and no further extensions in ~/.local/share/gnome-shell/ $ journalctl -S -1hour | grep 'Jan 07 08:19:35' | sort | uniq -c Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 4314 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending callback was paint(), a vfunc. 4291 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending callback was SourceFunc(). 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending signal was paint on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5581d33fc7d0. -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
I experience the same issue on 20.04.3 LTS, I think the issue is just lazy pixel updating. When the clock changes numbers, a column (maybe a couple columns) of pixels get stuck in the side of the clock, resulting in a smudge on the side of it. Issue gets resolved by moving the mouse there because it updates the pixels in that area. -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882291/+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 1942789] Re: On-demand and RTD3 need to be separated
With test on Dell Vostro 5568 witch got GPU can be supported by nvidia- driver-390 package. Install nvidia-driver-390 via ubuntu-drivers install nvidia:390. The default GPU mode will be nvidia. Manually switch GPU mode to on-demand, and running glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". It seems on-demand mode not work with nvidia-driver-390. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Focal: New Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: New Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1951599] Re: gnome-shell logs errors when ejecting SD card
@daniel, Agree with it, and could we SRU this fix into gnome-shell-extension- ubuntu-dock 68ubuntu1 in focal? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: In Progress Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1951599] Re: gnome-shell logs errors when ejecting SD card
OK so the first issue covered by the Bug Description is fixed by the above commit. We should make this bug about that only. The second issue you didn't mention until comment #4 so that should probably be moved to a new bug. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-in-72 fixed-upstream ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Triaged -- 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/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: In Progress Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1951599] Re: gnome-shell logs errors when ejecting SD card
@daniel, Oh, I checked the log, found the error messages in description was gone, so the patch fixed the error messages, although it didn't fix the eject issue in nautilus. https://github.com/micheleg/dash-to- dock/commit/d8dbbd8f776ec64d65f9938c2b597104c09ca86f -- 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/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: New Bug description: When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1951599] Re: gnome-shell logs errors when ejecting SD card
@daniel, Thanks for your feedback, but it didn't work for this issue. I doubt it's related nautilus, when I click the eject icon in nautilus to umount the sdcard, the item of sdcard is still there, as "4.0 GB Volume", and the sdcard was removed successfuly from kernel's log. So if click the eject icon again, it will show an error "Unable to eject 4.0 GB Volume", "Error ejecting /dev/mmcblk0: Command-line 'eject /dev/mmcblk0' exited with non-zero..". -- 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/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: New Bug description: When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview
Yes I noticed that part but it's not a bug. GNOME Shell often allocates things lazily the first time they are used, without any intention to free them if they are going to be used again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856838 Title: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview
Memory usage increases only at the first time when a push Super+A. Repeatedly pushing Super+A doesn't cause further jumps. However, this allocated memory never seems to be released (memory usage doesn't drop back to the original level). On Jan 7 2022, at 8:32 am, Daniel van Vugt <1856...@bugs.launchpad.net> wrote: > Is anyone still affected by this bug? If so then please ensure you don't > have any extensions loaded and tell us what version of Ubuntu you are > using. > > > ** Changed in: gnome-shell (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1856838 > > Title: > [memory leak] gnome-shell using a lot of RAM after repeatedly opening > the overview > > Status in GNOME Shell: > New > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. > Spoke to duflu on irc and he suggested I file a bug, and to make sure > I'm not using any extra extensions. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 > ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 > Uname: Linux 5.3.0-24-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Dec 18 10:49:44 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2018-02-04 (681 days ago) > InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary > 20180202-11:07 > RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1856838/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856838 Title: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.
I can't see any growth in memory usage on 22.04 when stressing everything related to the trash icon. Although I haven't tried waiting multiple hours and I haven't tried an older Ubuntu release yet. (I don't use the dock on my own desktops) Can anyone reproduce it in 22.04? http://cdimage.ubuntu.com/daily- live/current/ Can anyone suggest a test case that accelerates the leak? ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1876641 Title: gnome-shell leaks hundreds of megabytes when the dock option 'show- trash' is enabled. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Gnome shell is the single largest resident memory user on my system. It was hovering at ~700mb, then with a few minutes of use of the system (nothing in particular, mostly shell windows, one google-chrome window) - spiked to ~980mb or so, before retreating to 903m. Even with 16gb of ram, that's a huge chunk of the system. I've not been able to identify anything in particular that I'm doing that triggers the growth. In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1856838/comments/5, it was suggested to open a new bug, instead of adding to one of the several existing bugs for this. I'm happy to help try and debug this, but it's not clear where to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 17:32:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-18 (532 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876641/+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
