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 356323 - crash in Evolution:
crash in Evolution:
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
: 356510 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-16 21:32 UTC by Marcel Holtmann
Modified: 2006-10-09 21:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Marcel Holtmann 2006-09-16 21:32:43 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 422801408 vsize: 422801408 resident: 135577600 share: 22708224 rss: 135577600 rss_rlim: -1
CPU usage: start_time: 1158430546 rtime: 5723 utime: 4956 stime: 767 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47430865595152 (LWP 16125)]
[New Thread 1124362576 (LWP 16339)]
[New Thread 1098918224 (LWP 16338)]
[New Thread 1124096336 (LWP 16133)]
[New Thread 1115703632 (LWP 16131)]
[New Thread 1107310928 (LWP 16130)]
[New Thread 1090525520 (LWP 16128)]
[New Thread 1082132816 (LWP 16127)]
0x00002b2357cf26df in __libc_waitpid () from /lib/libc.so.6

+ Trace 72524

Thread 8 (Thread 1082132816 (LWP 16127))

  • #0 __select_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    at e-msgport.c line 643
  • #2 thread_dispatch
    at e-msgport.c line 1035
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 ??

Thread 7 (Thread 1090525520 (LWP 16128))

  • #0 __select_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    at e-msgport.c line 643
  • #2 thread_dispatch
    at e-msgport.c line 1035
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 ??

Thread 6 (Thread 1107310928 (LWP 16130))

  • #0 __select_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    at e-msgport.c line 643
  • #2 thread_dispatch
    at e-msgport.c line 1035
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 ??

Thread 5 (Thread 1115703632 (LWP 16131))

  • #0 __select_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    at e-msgport.c line 643
  • #2 thread_dispatch
    at e-msgport.c line 1035
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 ??

Thread 4 (Thread 1124096336 (LWP 16133))

  • #0 __select_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    at e-msgport.c line 643
  • #2 sync_op
    at em-sync-stream.c line 229
  • #3 stream_close
    at em-sync-stream.c line 327
  • #4 camel_object_unref
    at camel-object.c line 928
  • #5 efh_format_do
    at em-format-html.c line 1257
  • #6 mail_msg_received
    at mail-mt.c line 570
  • #7 thread_dispatch
    at e-msgport.c line 987
  • #8 start_thread
    from /lib/libpthread.so.0
  • #9 ?? 






Comment 1


Karsten Bräckelmann





          2006-09-16 21:44:17 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


André Klapper





          2006-10-06 09:40:59 UTC
        



Unfortunately the stacktrace does not have any hints about the real cause of
the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on
certain distros. However, almost all of them do turn out to be filed already,
once we managed to gather a useful stacktrace. To do so, simply install the
corresponding debugging packages and reproduce the issue, if possible. The
resulting stacktrace (see bug-buddy details) will help us to identify and fix
the issue.


Just in case you ever can reproduce this crash later, please consider
installing debugging packages [1] and either reopen this bug report or simply
file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.


Also, please feel free to report any further bugs you find.  Thanks!


[1] debugging packages for evolution and evolution-data-server, plus debugging
    packages for some basic GNOME libs. More details can be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions







Comment 3


Karsten Bräckelmann





          2006-10-09 21:42:25 UTC
        



*** Bug 356510 has been marked as a duplicate of this bug. ***