Red Hat Bugzilla – Bug 212818
Gaim (crashes) receives signal SIGPIPE, Broken pipe, when logging onto a channel on irc.efnet.org
Last modified: 2007-11-30 17:11:46 EST
Description of problem:
Gaim crashes, when connecting to a #sslug on irc.efnet.org.
Version-Release number of selected component (if applicable):
[peter@localhost ~]$ rpm -q gaim
[peter@localhost ~]$ rpm -q gaim-debuginfo
[peter@localhost ~]$ rpm -q dbus
Steps to Reproduce:
1. Start Gaim
2. Visit the #sslug chat on irc.efnet.org
Program receives signal SIGPIPE, Broken pipe.
Gaim logs on to #sslug.
Created attachment 139662 [details]
Backtrace with and without "handle SIGPIPE nostop".
<roland> warren: it's that application's problem whether it meant to cope with
SIGPIPE, or whether it meant to be killed by it and the socket it's writing to
is broken at that time because of something it did
(Roland McGrath indicating that this is upstream's problem.)
<drepper> warren: end don't propose to blindly ignore SIGPIPE
<drepper> warren: the right solution is to use send with the MSG_NOSIGNAL flag
(More suggestions from Ulrich Drepper.)
we only get caught by SIGPIPE when you run in gdb without telling it
handle SIGPIPE nostop
... except apparently in this case where something weird is going on.
Created attachment 140385 [details]
Disallow libdbus to exit(1) on its socket failure
This patch and RPMs at:
should resolve the DBUS cause. Still it is more a workaround - DBUS should not
fail in the first case. There is SIGPIPE from DBus exiting the process.
Anyway I believe this patch should be included as the DBus functionality is not
the principal functionality of Gaim to cause its quit.
Created attachment 140386 [details]
.gdbinit for Comment #1 to catch proper backtrace from exit(1)
That patch definitely seems to fix the symptom, I've applied it to upstream svn.
I agree that there must be a remaining Gaim or D-BUS bug, but I also agree that
a D-BUS failure should not cause Gaim to fail.
have a short solution ?
Please test this FC6 candidate update package here, does this solve your problem?
(In reply to comment #11)
> Please test this FC6 candidate update package here, does this solve your problem?
This package solves my problem. Thank you!
~]$ rpm -q gaim