Apparent issue with current Gimp

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:

 org.gtk.vfs.UDisks2VolumeMonitor               - -               -    (activatable) -

It is possible that this backend needs something from GNOME environment that is missing. Try running

journalctl --user --follow

in terminal and doing whatever operation causes timeout. Post output of journalctl.

Output of journalctl:

Sep 23 08:33:29 RYZEN9 plasmashell[2490]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x556f296ad430) Q
QmlContext(0x556f28f5cb10) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/glo
bal/Globals.qml") 
Sep 23 08:33:29 RYZEN9 plasmashell[2490]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x556f296ad430) Q
QmlContext(0x556f28f5cb10) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/glo
bal/Globals.qml") 
Sep 23 08:33:32 RYZEN9 dbus-daemon[2318]: [session uid=1000 pid=2318] Activating via systemd: service name='org.
gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.83' (uid=1000 pid=5385
comm="gimp") 
Sep 23 08:33:32 RYZEN9 systemd[2285]: Starting Virtual filesystem service - disk device monitor... 
Sep 23 08:33:32 RYZEN9 kernel: gvfs-udisks2-vo[5642]: segfault at 0 ip 00007f214376f84d sp 00007ffc9fe99d68 erro
r 4 in libc.so.6[7f2143626000+16c000] likely on CPU 8 (core 10, socket 0) 
Sep 23 08:33:32 RYZEN9 kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 89 f8 48 89 fa c5 f9 ef 
c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 b3 01 00 00 <c5> fd 76 0f c5 fd d7 c1 85 c0 0f 84 a3 00 00 00 f3 0f bc c0
c1 e8 
Sep 23 08:33:32 RYZEN9 systemd[1]: Started Process Core Dump (PID 5664/UID 0). 
Sep 23 08:33:32 RYZEN9 systemd-coredump[5665]:

A large core dump followed which I saved but did not include. I see a mention of a missing Plasmoid, but have to idea how to proceed.

So the program crashes. Are you using any non-default repositories?

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

Then I can only suggest bug report.

I agree, but I’m not sure where to file. With KDE or possibly Gimp?

I would start with openSUSE bugzilla.

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.