After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630369 - Hang on startup if named pipe in /tmp not removed after previous crash.
Hang on startup if named pipe in /tmp not removed after previous crash.
Status: RESOLVED INCOMPLETE
Product: anjuta
Classification: Applications
Component: plugins: symbol-db
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Massimo Cora'
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-22 20:57 UTC by Jonathan Giszczak
Modified: 2011-02-21 05:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jonathan Giszczak 2010-09-22 20:57:27 UTC 
If Anjuta crashes due to loss of the X-server, it leaves behind the named pipe and other files in /tmp.  If these are not removed, Anjuta will hang indefinitely, before displaying the splash screen.
Comment 1 Jonathan Giszczak 2010-09-27 22:19:15 UTC 
Also may silently exit instead of hanging.
Comment 2 Johannes Schmid 2010-10-12 14:24:45 UTC 
Hmm, well as anjuta wasn't shut down correctly (but rather by brute force) I would consider this major but we should check better for the named pipe.
Comment 3 Massimo Cora' 2011-01-03 23:52:33 UTC 
@jhs: should this be assigned to symbol-db or to general?

symbol-db is not using named pipes
Comment 4 Johannes Schmid 2011-01-04 09:19:50 UTC 
Sorry, I though symbol-db was the only thing that created files in /tmp.

We need a stacktrace for this bug. If you can still reproduce it, can please try to run anjuta in gdb and type "bt" (for backtrace) when it crashes. Paste the output of this command here.

Thanks!
Comment 5 Fabio Durán Verdugo 2011-02-21 05:10:31 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!