You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been experiencing significant lag when using the Gnome Sweet theme, particularly when performing file operations in Chrome. The issue becomes apparent when I try to save a file using the GTK file picker modal, or try to navigate through directories with the same modal. The modal takes an unusually long time to appear, and there are noticeable delays when navigating between folders.
This occur even with Gnome extensions disabled This does not occur with other themes, like Otis
Steps to Reproduce
Install and apply the Gnome Sweet theme on a Gnome desktop environment.
Open Chrome and attempt to download any file.
When the save file dialog appears (GTK modal), observe the time it takes for the modal to show up.
Try navigating through different directories within the save file dialog.
Expected Behavior
The GTK modal should appear almost instantly when invoked.
Navigating through directories should be smooth and without any noticeable lag.
Actual Behavior
There is a significant delay before the GTK modal appears.
Navigating between directories is slow, with noticeable pauses between each folder change.
Description
I've been experiencing significant lag when using the Gnome Sweet theme, particularly when performing file operations in Chrome. The issue becomes apparent when I try to save a file using the GTK file picker modal, or try to navigate through directories with the same modal. The modal takes an unusually long time to appear, and there are noticeable delays when navigating between folders.
This occur even with Gnome extensions disabled
This does not occur with other themes, like Otis
Steps to Reproduce
Expected Behavior
Actual Behavior
System Information
OS: Arch Linux
Gnome Version: 46.2
Theme: Gnome Sweet
Chrome Version: 125.0.6422.141 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: