evolution crashed with SIGSEGV in gtk_widget_get_toplevel()

StacktraceTop:
 IA__gtk_widget_get_toplevel (
 gtk_widget_get_screen_unchecked (widget=0x1bac3f0)
 IA__gtk_widget_has_screen (widget=0x1bac3f0)
 recompute_idle_func (data=<value optimized out>)
 gdk_threads_dispatch (data=0x1db8f40)

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=623832

Inadvertently reported as a duplicate (#611719) I encountered this bug/crash when attempting to open Evolution and thinking it wasn't going to open, I opened it a second time. Evolution then opened momentarily before the crash notification appeared.

I've tried several times to reproduce this crash but failed.

I can reproduce this at will.

First I open evolution to a date on which I already have an appointment scheduled. Either via the Clock (calendar) applet on my toolbar, or the command that invokes, "evolution calendar:///?startdate=20100923T040000Z", or other appointment days I've opened where it eventually crashes as well.

Then I copy from within the appointment. I can select all and copy, or highlight one letter and copy, or whatever. It doesn't matter what field - summary, location, both will eventually crash it.

So then I close the appointment out, then close evolution out.

Boom! Segmentation fault.

When I do it in gdb, I get the same stacktrace as is attached here.

welcome to open source =)

On Wed, Sep 8, 2010 at 10:38 AM, Dennis Sheil <email address hidden>wrote:

> I can reproduce this at will.
>
> First I open evolution to a date on which I already have an appointment
> scheduled. Either via the Clock (calendar) applet on my toolbar, or the
> command that invokes, "evolution
> calendar:///?startdate=20100923T040000Z", or other appointment days I've
> opened where it eventually crashes as well.
>
> Then I copy from within the appointment. I can select all and copy, or
> highlight one letter and copy, or whatever. It doesn't matter what
> field - summary, location, both will eventually crash it.
>
> So then I close the appointment out, then close evolution out.
>
> Boom! Segmentation fault.
>
> When I do it in gdb, I get the same stacktrace as is attached here.
>
> --
> evolution crashed with SIGSEGV in gtk_widget_get_toplevel()
> https://bugs.launchpad.net/bugs/602828
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I can reproduce this (or at least get the same error message) by:

- Open Evolution mail, leave it in the back ground.
- Accidentally select "contacts" from the upper menu (opens a new contacts window)
- Close the contacts and try to select the original mail window

I'd just configured a gmail account and it was about to suck down a lot of mail...

same bug for me. i did not do anything (the client just crashs while indexing 1000+ messages)...

This bug was fixed in the package evolution - 2.30.3-1ubuntu2

---------------
evolution (2.30.3-1ubuntu2) maverick; urgency=low

  * add debian/patches/89_remove_component_id_registration.patch:
    - ignore -c component gconf registration on launching just "evolution"
      (LP: #642244)
  * add debian/patches/91_git_fix_e_shell_ref_counting.patch:
    - should fix a crasher (LP: #602828) when quitting evolution because a bad
      reference counting (backport from evo 2.31)
 -- Didier Roche <email address hidden> Sun, 19 Sep 2010 15:31:34 +0200