Bug 212818 - Gaim (crashes) receives signal SIGPIPE, Broken pipe, when logging onto a channel on irc.efnet.org
Summary: Gaim (crashes) receives signal SIGPIPE, Broken pipe, when logging onto a chan...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gaim
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-29 11:26 UTC by Peter Eriksen
Modified: 2007-11-30 22:11 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-11-27 18:18:02 UTC


Attachments (Terms of Use)
Backtrace with and without "handle SIGPIPE nostop". (14.85 KB, text/plain)
2006-10-29 11:26 UTC, Peter Eriksen
no flags Details
Disallow libdbus to exit(1) on its socket failure (455 bytes, patch)
2006-11-05 12:13 UTC, Jan Kratochvil
no flags Details | Diff
.gdbinit for Comment #1 to catch proper backtrace from exit(1) (60 bytes, text/plain)
2006-11-05 12:14 UTC, Jan Kratochvil
no flags Details

Description Peter Eriksen 2006-10-29 11:26:28 UTC
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
gaim-2.0.0-0.17.beta4.fc6
[peter@localhost ~]$ rpm -q gaim-debuginfo
gaim-debuginfo-2.0.0-0.15.beta3.fc6
[peter@localhost ~]$ rpm -q dbus
dbus-0.93-3.fc6

How reproducible:
Always.

Steps to Reproduce:
1. Start Gaim
2. Visit the #sslug chat on irc.efnet.org
3.
  
Actual results:
Program receives signal SIGPIPE, Broken pipe.

Expected results:
Gaim logs on to #sslug.

Additional info:

Comment 1 Peter Eriksen 2006-10-29 11:26:29 UTC
Created attachment 139662 [details]
Backtrace with and without "handle SIGPIPE nostop".

Comment 2 Warren Togami 2006-10-30 21:42:26 UTC
<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.)

Comment 3 Warren Togami 2006-10-30 21:44:16 UTC
<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.)

Comment 4 Luke Schierer 2006-10-30 22:03:27 UTC
we only get caught by SIGPIPE when you run in gdb without telling it 
handle SIGPIPE nostop


Comment 5 Luke Schierer 2006-10-30 22:05:11 UTC
... except apparently in this case where something weird is going on.

Comment 6 Jan Kratochvil 2006-11-05 12:13:28 UTC
Created attachment 140385 [details]
Disallow libdbus to exit(1) on its socket failure

This patch and RPMs at:
http://www.jankratochvil.net/priv/bz212818/
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.

Comment 7 Jan Kratochvil 2006-11-05 12:14:30 UTC
Created attachment 140386 [details]
.gdbinit for Comment #1 to catch proper backtrace from exit(1)

Comment 9 Ethan Blanton 2006-11-05 14:58:33 UTC
Jan -

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.

Ethan

Comment 10 Sergio Monteiro Basto 2006-11-06 12:22:23 UTC
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213800#c5
have a short solution ? 

Comment 11 Warren Togami 2006-11-09 17:36:27 UTC
http://people.redhat.com/wtogami/temp/gaim/
Please test this FC6 candidate update package here, does this solve your problem?

Comment 12 Peter Eriksen 2006-11-09 19:15:39 UTC
(In reply to comment #11)
> http://people.redhat.com/wtogami/temp/gaim/
> Please test this FC6 candidate update package here, does this solve your problem?

This package solves my problem.  Thank you!

~]$ rpm -q gaim
gaim-2.0.0-0.19.beta4.fc6


Note You need to log in before you can comment on or make changes to this bug.