SUMMARY To give a bit of context, when an application freezes or becomes unresponsive, it becomes gray and will eventually show a dialog titled "Not Responding - Window Manager". This window gives you two options: "Terminate X", where X is the name of the process, and "Wait Longer". Selecting "Wait Longer" will close the dialog temporarily. Selecting "Terminate X" is meant to terminate the application and close all of its windows, as is mentioned in the dialog. I've found that this option almost never works. Neither does the default "Quit Application" option in System Monitor. Instead you have to go to "Send Signal" and explicitely send it a KILL signal to get it to close, which is inconvenient and annoying when there are so many easier to reach (and yet non-functional) options for closing such applications. STEPS TO REPRODUCE The most realiable way to reproduce a unresponsive application is to take advantage of a bug within Bottles that allows you to shutdown the internal soda runner without terminating the application front-end. First you will need to install the Bottles flatpak. Create a bottle, name it "Common" then configure it, and install Inkscape 0.92.5 using the windows installer (here: https://inkscape.org/en-gb/release/inkscape-0.92/?latest=1 ) Next you will want to configure SVG files to open using the bottled Inkscape. In System Settings, go to File Associations > svg+xml and add a new entry with the following parameters and set it as the default option. Name: Inkscape Comment: Launch Inkscape using Bottles. Program: flatpak Arguments: run --command=bottles-cli com.usebottles.bottles run -p Inkscape -b Common -- '"%U"' With setup complete: 1. Create 2 svg files 2. Open both in the bottled inkscape by clicking/double-clicking them 3. Once both are opened and the windows have loaded, close the you opened **last** 4. Attempt to close the remaining window If done correctly you should now have one inkscape window open that is not responding which you will not be able to close through any means other than a direct sig-kill towards the parent bottles process. OBSERVED RESULT You can attempt to close it using the (x) which will prompt the aforementioned dialog. After that clicking "Terminate inkscape.exe" appears to be no different from clicking "Wait Longer". The dialog will close, and you can continue to click (x) on the inkscape window to prompt it to re-appear. You can escalate to System Monitor and try to close it by right-clicking the Bottles process and selecting "Quit Application" but this simlarly has no effect. EXPECTED RESULT Clicking "Terminate inkscape.exe" or "Quit Application" should cause the window to close immediatly. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION
I tested this with a SIGSTOP-ed Dolphin instance on git master, and the dialog killed it with SIGKILL, so I assume this should be fixed with 6.1. If you can still reproduce with 6.1, just reopen this
I can still replicate the issue using the original steps after upgrading to 6.1 - Open first svg file - Open second svg file - Close second window - First window stops responding - First window does not respond to terminate requests Operating System: Manjaro Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-6-MANJARO (64-bit)
I have uploaded a video of the bug https://youtu.be/HA7EeAtPe8A