If Xarchiver is starting and a socket file already exists at /tmp there isn't any message shown to the user. This should be changed because in this case (socket file already exists) xarchiver doesn't work properly. I.e. settings aren't saved or xarchiver doesn't start when duoble clicking an archive file.
Please give more details about this, I don't understand why the socket file should remain in /tmp. I'm testing the current svn and even with segfaults I can't find the socket file in /tmp.
In my case I'd to kill xarchiver before because it doesn't react anymore. So in this case there is still a socket file located in /tmp
(In reply to comment #2) > In my case I'd to kill xarchiver before because it doesn't react anymore. So in > this case there is still a socket file located in /tmp > Does this happens with the svn version? Also can you please reproduce the steps leading to Xarchiver freezing?
This happened with the svn version of 20070103 which is shipped in CentOS Extra repository. But I can't remember why I hat to kill xarchiver.
I think I can close it. Please reopen if you are able to reproduce the bug.