[SOLVED] Gnome is very sluggish - both Debian & Fedora

Daniel_Tirer · September 7, 2022, 5:01pm

I recently received my Framework and have tried installing both Debian (wormhole) and Fedora 36, in both cases with gnome desktop. In both cases, I found gnome is very sluggish, where it almost appears like the animations aren’t happening for windows, or frames are being dropped.

Interestingly, the live boot of Fedora 36 worked great off of the USB thumb drive, but once I installed it to the nvme drive, it exhibited the same issues as Debian

Below are the specs of my machine:

CPU: Intel® Core™ i5-1240P
Memory: 32GB (2 x 16GB) DDR4-3200
Storage: 1TB - WD_BLACK™ SN850 NVMe™

To install Debian, I followed the guide in this thread:

To install Fedora:

I first tried the live boot (which worked great) which I obtained here
Fedora Workstation | The Fedora Project
I then tried the network install, which exhibited the same sluggish behavior as Debian w/ gnome

Thomas_Piekarski · September 7, 2022, 5:56pm

Do you use Wayland or X11?

Can you please check the journal with journalctl --since today, kernel ring buffer with dmesg and perhaps run journalctl --follow as well as dmesg -follow in two terminals and use your system until first delays occur?

Does journalctl or dmesg log anything which could indicate some issue?

Daniel_Tirer · September 7, 2022, 8:06pm

I’m running Wayland in both cases

journalctl --follow has some logs but I’m not certain if it’s related:

Sep 07 15:59:14 fedora gnome-shell[1900]: #6   7ffd2e5ee120 b   resource:///org/gnome/shell/ui/windowPreview.js:363 (2b0b49d0a560 @ 222)
Sep 07 15:59:14 fedora gnome-shell[1900]: #7   7ffd2e5ee850 b   resource:///org/gnome/shell/ui/windowPreview.js:571 (2b0b49d0abf0 @ 105)
Sep 07 15:59:14 fedora gnome-shell[1900]: == Stack trace for context 0x56017152e620 ==
Sep 07 15:59:14 fedora gnome-shell[1900]: #0   7ffd2e5edcb0 b   resource:///org/gnome/shell/ui/windowPreview.js:369 (2b0b49d0a600 @ 12)
Sep 07 15:59:14 fedora gnome-shell[1900]: #1   7ffd2e5edd60 b   resource:///org/gnome/shell/ui/environment.js:153 (11f43b8cc4c0 @ 98)
Sep 07 15:59:14 fedora gnome-shell[1900]: #2   7ffd2e5ede50 b   resource:///org/gnome/shell/ui/environment.js:242 (11f43b8cc560 @ 974)
Sep 07 15:59:14 fedora gnome-shell[1900]: #3   7ffd2e5edf20 b   resource:///org/gnome/shell/ui/environment.js:388 (11f43b8ccd30 @ 23)
Sep 07 15:59:14 fedora gnome-shell[1900]: #4   7ffd2e5edfe0 b   resource:///org/gnome/shell/ui/windowPreview.js:365 (2b0b49d0a5b0 @ 109)
Sep 07 15:59:14 fedora gnome-shell[1900]: #5   7ffd2e5ee050 I   self-hosted:202 (11f43b88b240 @ 272)
Sep 07 15:59:14 fedora gnome-shell[1900]: #6   7ffd2e5ee120 b   resource:///org/gnome/shell/ui/windowPreview.js:363 (2b0b49d0a560 @ 222)
Sep 07 15:59:14 fedora gnome-shell[1900]: #7   7ffd2e5ee850 b   resource:///org/gnome/shell/ui/windowPreview.js:571 (2b0b49d0abf0 @ 105)
Sep 07 15:59:14 fedora gnome-shell[1900]: == Stack trace for context 0x56017152e620 ==
Sep 07 15:59:14 fedora gnome-shell[1900]: #0   7ffd2e5ee120 b   resource:///org/gnome/shell/ui/windowPreview.js:373 (2b0b49d0a560 @ 230)
Sep 07 15:59:14 fedora gnome-shell[1900]: #1   7ffd2e5ee850 b   resource:///org/gnome/shell/ui/windowPreview.js:571 (2b0b49d0abf0 @ 105)
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Label (0x56017a710500), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object St.Button (0x56017a7109a0), has been already disposed — 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.
Sep 07 15:59:14 fedora gnome-shell[1900]: Object .Gjs_ui_windowPreview_WindowPreview (0x560171fc4360), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 07 15:59:14 fedora gnome-shell[1900]: JS ERROR: TypeError: this.window_container is null
                                          hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9
                                          vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26
^[cSep 07 16:01:01 fedora gnome-shell[1900]: Window manager warning: last_user_time (801542) is greater than comparison timestamp (801539).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Sep 07 16:01:01 fedora gnome-shell[1900]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 801542.  Working around...
Sep 07 16:01:30 fedora gnome-shell[1900]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Boxes.SearchProvider@5.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Calculator.SearchProvider@5.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Characters@5.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Contacts.SearchProvider@5.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Nautilus@5.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Photos@9.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.Settings.SearchProvider@4.service.
Sep 07 16:01:30 fedora systemd[1767]: Started dbus-:1.2-org.gnome.clocks@5.service.
Sep 07 16:01:30 fedora PackageKit[1396]: resolve transaction /146_aeacadbc from uid 1000 finished with success after 4ms
Sep 07 16:01:31 fedora gnome-character[4507]: JS LOG: Characters Application started
Sep 07 16:01:31 fedora nautilus[4511]: Connecting to org.freedesktop.Tracker3.Miner.Files
Sep 07 16:01:31 fedora systemd[1767]: Started dbus-:1.2-com.intel.dleyna\x2drenderer@7.service.
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: dLeyna core version 0.6.0
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: dleyna-renderer-service version 0.6.0
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Type[0] Level[0x13] Mask[0x4C] Flags[0x4F]
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Load file [/home/dtirer/.config/dleyna-renderer-service.conf]
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: [General settings]
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Never Quit: F
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Connector Name: dbus
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Port: 0
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Push host port: 0
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: [Logging settings]
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Log Type : 0
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Log Level: 0x13
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: [Network filtering settings]
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Enabled : F
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Entries: (null)
Sep 07 16:01:31 fedora gnome-shell[1900]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Calling GetRenderers method
Sep 07 16:01:31 fedora dleyna-renderer-service[4593]: Client :1.190 lost
Sep 07 16:01:31 fedora PackageKit[1396]: resolve transaction /147_edddcaed from uid 1000 finished with success after 3ms
Sep 07 16:01:31 fedora systemd[1767]: app-glib-firefox-4651.scope: unit configures an IP firewall, but not running as root.
Sep 07 16:01:31 fedora systemd[1767]: (This warning is only shown for the first unit using IP firewalling.)
Sep 07 16:01:31 fedora systemd[1767]: Started app-glib-firefox-4651.scope - Application launched by gnome-shell.
Sep 07 16:01:31 fedora systemd[1767]: Created slice app-cgroupify.slice - Slice /app/cgroupify.
Sep 07 16:01:31 fedora systemd[1767]: Started cgroupify@app-glib-firefox-4651.scope.service.
Sep 07 16:01:31 fedora systemd[1767]: Started app-gnome-firefox-4651.scope - Application launched by gnome-shell.
Sep 07 16:01:31 fedora systemd[1767]: Started cgroupify@app-gnome-firefox-4651.scope.service.
Sep 07 16:01:31 fedora systemd[1767]: Stopping cgroupify@app-glib-firefox-4651.scope.service...
Sep 07 16:01:31 fedora systemd[1767]: Stopped cgroupify@app-glib-firefox-4651.scope.service.
Sep 07 16:01:31 fedora rtkit-daemon[937]: Successfully made thread 4813 of process 4651 (/usr/lib64/firefox/firefox) owned by '1000' RT at priority 10.
Sep 07 16:01:32 fedora firefox.desktop[4651]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Sep 07 16:01:32 fedora dleyna-renderer-service[4593]: dLeyna: Exit
Sep 07 16:01:41 fedora gnome-character[4507]: JS LOG: Characters Application exiting
^NSep 07 16:01:48 fedora gnome-shell[1900]: Window manager warning: last_user_time (848451) is greater than comparison timestamp (848448).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Sep 07 16:01:48 fedora gnome-shell[1900]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 848451.  Working around...
Sep 07 16:01:48 fedora systemd[1767]: Started vte-spawn-ab2f020e-182f-42dc-8809-fdea4e9e3d27.scope - VTE child process 5093 launched by gnome-terminal-server process 2597.
Sep 07 16:01:54 fedora PackageKit[1396]: search-file transaction /148_bbbbdccc from uid 1000 finished with success after 61ms
Sep 07 16:02:01 fedora chronyd[964]: Selected source 138.236.128.36 (2.fedora.pool.ntp.org)
Sep 07 16:02:47 fedora systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Sep 07 16:02:47 fedora systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Sep 07 16:02:47 fedora systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Sep 07 16:02:47 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 07 16:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 07 16:02:47 fedora wpa_supplicant[1161]: wlp166s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=9999 txrate=86700
Sep 07 16:02:49 fedora wpa_supplicant[1161]: wlp166s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=86700
Sep 07 16:02:49 fedora wpa_supplicant[1161]: wlp166s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=86700
Sep 07 16:03:47 fedora gnome-shell[1900]: Window manager warning: last_user_time (968381) is greater than comparison timestamp (968378).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Sep 07 16:03:47 fedora gnome-shell[1900]: Window manager warning: W12 appears to be one of the offending windows with a timestamp of 968381.  Working around..

Daniel_Tirer · September 7, 2022, 8:11pm

Also the CPU seems to be pretty pegged:

mjog · September 8, 2022, 1:03am

Looks like you have multiple copies of gnome-shell running from that photo? If so that’s definitely a problem. There should be two at most - one for gdm and one for your login.

Seem more likely to a system configuration problem than a GNOME or hardware issue.

Daniel_Tirer · September 8, 2022, 1:13am

@mjog Hm are those not child processes of a single process? Even on a fresh boot and opening the terminal to run htop, there appear to be about 20 of those.

A second question that I just noticed: when I got to the system settings → About, it says under “Graphics” – “Software Rendering”. I would have expected it to list the Intel chip, but maybe I’m wrong there

mjog · September 8, 2022, 1:27am

Hard to say from that photo on my phone.

But yeah, software rendering would very likely be a problem. Check you have the right drivers for Intel DRM (and X if you use that).

Daniel_Tirer · September 8, 2022, 3:03am

Okay I got some help on the Framework Discord. Turns out I had installed Fedora in “Safe Graphics” mode. I had done this because the resolution of the full graphics installer didn’t even allow the the WiFi network list to fit on the screen and the view wasn’t scrollable (I live in NYC so there’s a ton of networks around me).

As it turns, if you installed in safe graphic mode, then the installation is run with safe graphics as well.

So running cat /proc/cmdline gave me the following:

BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.19.6-200.fc36.x86_64 root=/dev/mapper/fedora_fedora-root ro rd.lvm.lv=fedora_fedora/root rd.luks.uuid=luks-888782dc-9700-4a87-ae3c-791e1e7b0211 nomodeset rhgb quiet

As you can see, nomodeset is there. So I went and removed this from /etc/default/grub, ran grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg, rebooted, and everything worked!

Ian_Comings · September 9, 2022, 3:38pm

Gnome on Manjaro seemed perfectly fine

Eric_Kearney · October 8, 2022, 3:39pm

Wow thank you @Daniel_Tirer! Such a simple thing I missed that was making my laptop almost unbearable to use. I almost distro hopped but removing nomodeset fixed everything for me as well!!

Matt_Hartley · January 9, 2023, 6:51pm

Seems removing this solved the issue for the op and others. Marking solved.