Bug 435169

=== SUMMARY ===

When opening a file from Dolphin (such as double-clicking), and then closing the application, there will remain a hanging "file.so" process that will prevent the user from safely ejecting an external drive or disconnecting a network share.

* This does *not* happen if you first open an application (such as Kate, Chromium, XnViewMP), and then drag the file to the application's window.

* This does *not* happen if you first open an application (such as Kate, Chromium, XnViewMP), and then go to File > Open and browse for the file.

* This does *not* happen if you open a file using the "xdg-open" command from a terminal.

From my repeated and reproducable tests, this only happens when opening a file from within Dolphin.

The other methods written above do not result in a hanging "file.so" process.

The only method that results in a hanging "file.so" process is when opening a file from Dolphin.

The three completely different applications I tried this with, which all produce the same exact results:
* Kate
* Chromium / Google Chrome
* XnViewMP

I am only an end-user. I cannot tell if this is an issue with a recent update to Dolphin, or some other KDE component that Dolphin uses.

This only started happening to me after a major Manjaro update (stable repository, within the past few weeks or so?)




=== SYSTEM INFORMATION ===

Operating System: Manjaro Linux

KDE Plasma Version: 5.21.3

KDE Frameworks Version: 5.80.0

Qt Version: 5.15.2

Dolphin Version: 20.12.3

Kernel Version: 5.10.23-1-MANJARO

Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz

Memory: 11.6 GiB of RAM

Graphics Processor: GeForce GTX 1650/PCIe/SSE2




=== GLOSSARY ===
I. "FILE" is either a text file, image file, or HTML file

II. "APP" is either Kate, XnViewMP, or Chromium browser

III. "DIR" is either a removable USB drive or a network share (via Smb4K)




=== STEPS TO REPRODUCE ===

1. Browse to the DIR using Dolphin file manager

2. Double-click on the FILE, which then opens it with the associated APP

3. Close the APP

4. Try to safely remove the drive or disconnect the network share

5. !!! An error will complain that the device is still in use !!!

6. Kill the hanging "file.so" processes using KSysGuard or the terminal

7. Try again to safely remove the drive or disconnect the network share

8. This time it will work




=== ALTERNATIVE STEPS TO BYPASS THIS BUG ===

1. Open up the APP

2. Click and drag the FILE to the APP's window

3. Close the APP

4. Try to safely remove the drive or disconnect the network share

5. Success!




=== MORE ALTERNATIVE STEPS TO BYPASS THIS BUG ===

1. From the terminal, open up the FILE using the "xdg-open" command, which then opens it up in the associated APP

2. Close the APP

3. Try to safely remove the drive or disconnect the network share

4. Success!




=== EVEN MORE ALTERNATIVE STEPS TO BYPASS THIS BUG ===

1. Open up the APP

2. Go File > Open, then browse and open the FILE from the DIR

3. Close the APP

4. Try to safely remove the drive or disconnect the network share

5. Success!




=== ADDITIONAL INFORMATION ====

The following bug report is possibly related, though I think Kate is mistaken as the culprit, since as you can see this happens with at least three different applications with the same result: https://bugs.kde.org/show_bug.cgi?id=432298