I don’t use Gimp regularly so I can’t be precise about the update timeframe.
If I use Dolphin to spawn Gimp to open an image, it opens quickly. I can make whatever edits I choose and it proceeds normally. If I use the “File” dropdown menu and select “New or Export”, the primary Gimp window becomes completely unresponsive and the child window does not open for 25 seconds or longer. Once the child window appears, all is well. Gimp only does this on the first use of the “File” menu, Subsequent uses of it are normal.
If I open Gimp from a terminal, I get the following error a split second before Gimp returns to normal behavior:
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
Since GTK is mentioned in the error, I should mention that I am a plasma user.
I run gkrellm continuously and see no CPU usage associated with the delay.
25 seconds is usual D-Bus timeout which means your program tries to contact some service over D-Bus and times out.
And here you have the service it attempts to contact.
The org.gtk.vfs.UDisks2VolumeMonitor is provided by gvfs-backends package. Looking at gimp dependency chain, it should pull in this package. On my more or less default KDE installation it is listed as available after login:
I use Packman, the Brave-Browser repo, Games repo for Tumbleweed, and a “hardware” repo from openSUSE for Tumbleweed. Other than those, all are default for Tumbleweed. Gimp and all gvfs packages are from standard Tumbleweed repos. gvfs-backend version is 1.52.1-1.1 and Gimp is 2.10.34-5.2
Thank you. I filed there yesterday and via a suggested troubleshooting tip, it seems that the gvfs-udisks2-volume-monitor service is what actually crashes. I think it’s safe to close this thread.