After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 565408 - Evolution Mail and Calendar: Evolution is crashing wh...
Evolution Mail and Calendar: Evolution is crashing wh...
Status: RESOLVED DUPLICATE of bug 533743
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-12-23 00:42 UTC by Marcus
Modified: 2008-12-23 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
evolution crash (16.08 KB, text/plain)
2008-12-23 17:18 UTC, Marcus 		Details

Description Marcus 2008-12-23 00:42:55 UTC 
Evolution is crashing when I was changing a which folder in imap server would be subscript (which folder i would like to see). 
dmesg evolution[9965] trap invalid opcode ip:2bb2f19 sp:419d7048 error:0



Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.2 2008-12-18 (Gentoo)
BugBuddy Version: 2.24.2
Comment 1 André Klapper 2008-12-23 12:37:00 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Marcus 2008-12-23 15:20:59 UTC 
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!
> 
I hope it's enough.

+ Trace 211025

Thread 1 (Thread 0x7f625aabd740 (LWP 27031))

  • #0 __lll_unlock_wake
    from /lib/libpthread.so.0
  • #1 _L_unlock_47
    from /lib/libpthread.so.0
  • #2 __pthread_mutex_unlock_usercnt
    from /lib/libpthread.so.0
  • #3 ??
    from /usr/lib64/evolution/2.24/components/libevolution-mail.so
  • #4 ??
    from /usr/lib64/evolution/2.24/components/libevolution-mail.so
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 ?? 






Comment 3


André Klapper





          2008-12-23 15:38:40 UTC
        



Hmm...
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution).

More details can be found here: http://live.gnome.org/GettingTraces






Comment 4


Marcus





          2008-12-23 16:02:51 UTC
        



I remerge this packages with debug flags.






+
Trace
    211026


















Comment 5


André Klapper





          2008-12-23 16:29:08 UTC
        



would be good to have evolution, evolution-data-server and glib with debug symbols. in the last trace there are still no debug symbols at all. :-(

http://www.gentoo.org/proj/en/qa/backtraces.xml






Comment 6


Marcus





          2008-12-23 17:18:05 UTC
        



Created attachment 125206 [details]
evolution crash

Trace from evolution






Comment 7


André Klapper





          2008-12-23 17:36:57 UTC
        



Ah, thanks a lot! Same as bug 533743 comment 3.

*** This bug has been marked as a duplicate of 533743 ***