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 595168 - [abrt] crash detected in evolution-2.27.92-1.fc12
[abrt] crash detected in evolution-2.27.92-1.fc12
Status: RESOLVED DUPLICATE of bug 557613
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-09-14 13:07 UTC by Matthew Barnes
Modified: 2013-09-13 01:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Barnes 2009-09-14 13:07:25 UTC 
Random stack trace from Fedora's new "abrt" system.
Forwarded from: http://bugzilla.redhat.com/show_bug.cgi?id=522242

No reproducer steps provided.


[New Thread 3048]
[New Thread 3314]
[New Thread 3315]
[New Thread 3049]
[New Thread 3055]
[New Thread 3310]
[New Thread 3052]
[New Thread 3058]
[New Thread 3059]
[New Thread 3065]
[New Thread 3097]
[New Thread 3098]
Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 217566

Thread 1 (Thread 3043)

  • #0 __pthread_mutex_lock
    at pthread_mutex_lock.c line 50
  • #1 e_flag_set
    at e-flag.c line 83
  • #2 emit_async_open_response
    at e-book.c line 2814
  • #3 g_main_dispatch
    at gmain.c line 1960
  • #4 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #5 g_main_context_iterate
    at gmain.c line 2591
  • #6 IA__g_main_loop_run
    at gmain.c line 2799
  • #7 bonobo_main
    at bonobo-main.c line 311
  • #8 main
    at main.c line 732 






Comment 1


Akhil Laddha





          2009-09-15 03:33:52 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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