evolution crashed with SIGSEGV in giop_recv_buffer_get()

Bug #132920 reported by Paul Wagland
6
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

There are similar bugs already reported, however this is a new stacktrace from the current version, all of the previous reports seem to be from prior versions.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 16 15:01:02 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: vmnet vmmon nvidia
Package: evolution 2.11.90-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: evolution
ProcCwd: /home/users/paul
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
Signal: 11
SourcePackage: evolution
StacktraceTop:
 giop_recv_buffer_get ()
 ORBit_small_invoke_stub ()
 Bonobo_Unknown_unref ()
 bonobo_object_release_unref ()
 e_cal_view_finalize (object=0xb90b60)
Title: evolution crashed with SIGSEGV in giop_recv_buffer_get()
Uname: Linux paul 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Tags: apport-crash
Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :
Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :

This happened when I was trying to do a full message search on my entire exchange mailbox, which is over 1GB in size. I expected it to take a while, which it did, and then it crashed, which I didn't expect ;-)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:giop_recv_buffer_get (ent=0x7ffff8c4f090, timeout=0x7ffff8c4f0cc) at giop-recv-buffer.c:733
ORBit_small_invoke_stub (obj=0x25c83e0, m_data=0x2b34b72492a0, ret=0x0, args=0x0, ctx=0x0, ev=0x7ffff8c4f140) at orbit-small.c:658
Bonobo_Unknown_unref (_obj=0x663e50, ev=<value optimized out>) at Bonobo_Unknown-stubs.c:15
bonobo_object_release_unref (object=0x25c83e0, opt_ev=0x0) at bonobo-object.c:577
e_cal_view_finalize (object=0xb90b60) at e-cal-view.c:227

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
C de-Avillez (hggdh2) wrote :

This one seems very similar to upstream http://bugzilla.gnome.org/show_bug.cgi?id=330161. I am not marking it as confirmed (but it is very near so... I retyped this some 3 times, changing between confirming and not confirming :-).

@Paul: can you repeat at will?

Also, is your gutsy up-to-date? Reason for asking is that I see you are running gutsy, but still at kernel 2.6.20, so I wonder about it... if you are not up-to-date, would it be possible to update (except kernel), and try again? But I think you are up-to-date... I looked at a few of the dependencies, and they match current gutsy.

Anyway: the upstream bug suggests race conditions. There, we have the issue during business hours (also involving LDAPs), here on a very long search via exchange... perhaps an Evo exchange trace would give us a bit more of light. Please see http://www.gnome.org/projects/evolution/bugs.shtml, specially the end (Evo Exchange debugging). Probably E2K_DEBUG=2m would do the trick (on both Evolution and evolution-exchange).

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :

I will try to reproduce this, but will not be near my main machine much in the next week.

And yes, I am fully uptodate, however I also need to run VMWare 5.5, which does not compile against the 2.6.22 kernel, so I still run with a 2.6.20 kernel, but all libraries/packages/et al. are up to date.

Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :

I can reproduce the crash, although it does not always give me the approx popup.

As an aside, since the crash I can only see e-mails that turned up after the crash. I know that they are all still in my mailbox, as I can see them with webmail, do you know how I can force evolution to fully reread the mailbox again? I do have a workaround, in that if I move the mail to another mbox, and then back into the INBOX then evo will see it and download it.... however I have a lot of e-mails in my inbox, and this is a tedious process :-)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Is this still an issue with evolution 2.12?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this report for now, feel free to re open if it is still an issue with latest package from Gutsy. thanks.

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.