Re: SWH3D Frozen and unable to close it

by sjb007 » Mon May 06, 2024 3:12 am

...even after rebooting it is still there frozen.
This is simply not possible. I think you are sleeping or hibernating your system. This does not terminate running programs.

You say you are not a nerd. Do you know about processes, and how to kill them? It may be possible to terminate the running process without rebooting your system. It is very rare, but sometimes a Linux system can leave a frozen window even when the process has been killed. In that situation only a full shutdown and restart will rid you of the window.

First lets see if we can help you kill the frozen process. Open a terminal, and type the following:

Code: Select all

ps -ef | grep -i sweet | grep -v grep
(list all processes, do a case insensitive search for "sweet", then exclude our own search process from the result. There should only be one line.)

You will see a very long line. First your username, then the process id. i.e.

Code: Select all

steve     [b]653099[/b]   89919 32 02:59 pts/3    00:00:28 SweetHome3D-7.2/runtime/bin/java -Xmx2g -classpath SweetHome3D-7.2/lib/SweetHome3D.jar:SweetHome3D-7.2/lib/Furniture.jar:SweetHome3D-7.2/lib/Textures.jar:SweetHome3D-7.2/lib/Examples.jar:SweetHome3D-7.2/lib/Help.jar:SweetHome3D-7.2/lib/batik-svgpathparser-1.7.jar:SweetHome3D-7.2/lib/jeksparser-calculator.jar:SweetHome3D-7.2/lib/iText-2.1.7.jar:SweetHome3D-7.2/lib/freehep-vectorgraphics-svg-2.1.1c.jar:SweetHome3D-7.2/lib/sunflow-0.07.3i.jar:SweetHome3D-7.2/lib/jmf.jar:SweetHome3D-7.2/lib/java3d-1.6/j3dcore.jar:SweetHome3D-7.2/lib/java3d-1.6/j3dutils.jar:SweetHome3D-7.2/lib/java3d-1.6/vecmath.jar:SweetHome3D-7.2/lib/java3d-1.6/gluegen-rt.jar:SweetHome3D-7.2/lib/java3d-1.6/jogl-java3d.jar:SweetHome3D-7.2/lib/jnlp.jar -Djava.library.path=SweetHome3D-7.2/lib/java3d-1.6:SweetHome3D-7.2/lib/yafaray -Djogamp.gluegen.UseTempJarCache=false -Dcom.eteks.sweethome3d.applicationId=SweetHome3D#Installer com.eteks.sweethome3d.SweetHome3D -open
I've bolded the process id here. Important! The process id on your system will be different. So now type the following, but replacing my process id with your own:

Code: Select all

kill -9 653099
The -9 (aka SIGKILL) flag makes it not a request to the application to terminate (i.e. -15 aka SIGTERM), but a hard kill.

Hope that helps.