Bug 496586

SUMMARY
When you drag and drop an image (only tested with png so far) from dolphin to the layers pane in Gimp, rather than trying to import the image once, it tries to add it an infinite amount of times, until it runs out of swap, and dolphin crashes (which also takes down Brave browser, likely due to swap).  The whole time the system is all but locked.  I was able to get into `top` enough to see dozens and dozens of `file-png` ??? processes spawned.  Really a toss-up if you can wait out the infinite loop or of you have to power cycle the box.  This has happened three times in a row (every time I've tried it), each with different images. These are small images I'm working with: favicons on the order 1-2kB.

I also do this with a selected list of images, dragging many nearly identical images at once for image-stacking purposes, but I haven't tested trying to drag multiple images.

STEPS TO REPRODUCE
1. Open some image in gimp, or start a new image.
2. Add a new layer, by dragging a file from dolphin, and dropping it into the layers pane in gimp.
3.  Go have a beer while you watch your computer melt. :-)

OBSERVED RESULT
System all but locks up, and eventually dolphin crashes, apparently due to running out of swap, which then takes down Brave.  Gimp remains up, and will have the image inserted many times.  The one time I let it spin without rebooting, the image had been inserted 119 times instead of once.

EXPECTED RESULT
Dolphin should give gimp just the selected file(s), and only once.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-9-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-5250U CPU @ 1.60GHz
Memory: 14.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 6000

ADDITIONAL INFORMATION
Using GIMP 2.10.38

I do not have a backtrace, but I did add `export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com"` to my ~/.bashrc in case I am a glutton for punishment enough to make the mistake of trying this again.

This seems similar to Bug 482298, but that is supposedly fixed.  Perhaps my versions are still too old.