Tiny Core Linux

Tiny Core Extensions => TCE Q&A Forum => Topic started by: MikeLockmoore on August 24, 2010, 11:58:14 PM

Title: Geany startup problem
Post by: MikeLockmoore on August 24, 2010, 11:58:14 PM

In TC 3.0, Geany is giving this error message now when I try to start it up:

Code: [Select]

Geany tried to access the Unix Domain socket of another instance running as another user.
This is a fatal error and Geany will now quit.
I tried updating Geany and it did not help.  The strange thing is, I was using this or a prior version of Geany with TC for several weeks on TC 3.0 without any problems.  Any ideas?

Title: Re: Geany startup problem
Post by: jur on August 25, 2010, 12:23:05 AM

Perhaps an uncleared geany socket from a previous session? Delete it and try again.

Title: Re: Geany startup problem
Post by: Jason W on August 25, 2010, 01:54:26 AM

I have looked into this and can only duplicate the problem when I have a running instance of geany open and change the ownership or perms of the file /home/tc/.config/geany/geany_socket_box__0.   Then any attempts to start another geany session, before or after closing the first one, will show that error. 

Title: Re: Geany startup problem
Post by: eluring on August 25, 2010, 08:12:22 AM

had happened to me also after not having closed geany and then rebooting.
help in this forum was:

Code: [Select]

rm -f ~/.config/geany/geany_socket_box*
I am used to not close geany and now I have put

Code: [Select]

rm -f /home/tc/.config/geany/geany_socket_box*into /opt/bootlocal.sh

Title: Re: Geany startup problem
Post by: MikeLockmoore on August 26, 2010, 01:44:33 PM

@Jason:  Once again, you've shared the right bit of knowledge to get me unstuck!  :)  Thanks, greatly.

@eluring: Looks like a good idea.  I've added it to my bootlocal.sh.  ;)
--
ML

Title: Re: Geany startup problem
Post by: jmhill on April 22, 2011, 06:58:55 PM

Thanks so much for the post, removing that file solved the issue.

The first few times I tried geany, I learned that a resolution of 800x600 is not adequate with geany, but after increasing to 1024x768, I came across that issue.  Apparently I didn't shut geany down.  Back to work...