Crash while checking Google Apps account
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mail Notification |
New
|
Undecided
|
Unassigned |
Bug Description
I am using mail-notification from Ubuntu (5.4.dfsg.
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7ffc64276950 (LWP 17545)]
#0 0x00007ffc6c3574b1 in send () from /lib/libpthread
#1 0x00007ffc6b000243 in _gnutls_
from /usr/lib/
#2 0x00007ffc6affd181 in _gnutls_send_int () from /usr/lib/
#3 0x00007ffc6b01b7a0 in gnutls_alert_send () from /usr/lib/
#4 0x00007ffc6affd48f in gnutls_bye () from /usr/lib/
#5 0x00007ffc706a6b5f in gnome_vfs_
from /usr/lib/
#6 0x00007ffc706a666e in gnome_vfs_
from /usr/lib/
#7 0x00007ffc706a6583 in gnome_vfs_
from /usr/lib/
#8 0x00007ffc64f8d5d3 in ne_sock_close ()
from /usr/lib/
#9 0x00007ffc64f83923 in ne_close_connection ()
from /usr/lib/
#10 0x00007ffc64f81670 in ?? () from /usr/lib/
#11 0x00007ffc64f83669 in ?? () from /usr/lib/
#12 0x00007ffc64f82de4 in ne_begin_request ()
from /usr/lib/
#13 0x00007ffc64f7f760 in ?? () from /usr/lib/
#14 0x00007ffc64f7fcd9 in ?? () from /usr/lib/
#15 0x00007ffc70693097 in gnome_vfs_
from /usr/lib/
#16 0x00007ffc706a46b2 in gnome_vfs_open () from /usr/lib/
#17 0x00007ffc706aac78 in gnome_vfs_
from /usr/lib/
#18 0x0000000000430c61 in mn_vfs_
#19 0x000000000043fb25 in ?? ()
#20 0x000000000043d825 in ?? ()
#21 0x00007ffc6ce71ae4 in ?? () from /usr/lib/
#22 0x00007ffc6c3503ba in start_thread () from /lib/libpthread
#23 0x00007ffc6c0bcfcd in clone () from /lib/libc.so.6
#24 0x0000000000000000 in ?? ()
I realize this doesn't seem very helpful, so I will try to compile it myself and see if I can reproduce it.
I have attached another backtrace from an unstripped binary, however it appears to be a completely different issue! SIGABRT instead of SIGPIPE, having nothing to do with gnutls...
mail-notification: ../../src/ xcb_io. c:176: process_responses: Assertion `!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.
I guess these should be split into separate bug reports, though I have not been able to isolate the issue, nor have I figured out what is triggering it. Any help in the debugging process would be appreciated.