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 372868 - 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: Evolution Shell Maintainers Team
Evolution QA team
: 372888 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-09 09:30 UTC by e.shogun
Modified: 2006-11-16 00:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description e.shogun 2006-11-09 09:30:26 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 1554579456 vsize: 1554579456 resident: 828510208 share: 19255296 rss: 828510208 rss_rlim: -1
CPU usage: start_time: 1163064504 rtime: 1292 utime: 738 stime: 554 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47434206776640 (LWP 7658)]
[New Thread 1124362576 (LWP 7677)]
[New Thread 1124096336 (LWP 7674)]
[New Thread 1115703632 (LWP 7673)]
[New Thread 1107310928 (LWP 7672)]
[New Thread 1098918224 (LWP 7668)]
[New Thread 1090525520 (LWP 7664)]
[New Thread 1082132816 (LWP 7663)]
(no debugging symbols found)
0x00002b241ebfa5cf in waitpid () from /lib/libc.so.6

+ Trace 84673

Thread 8 (Thread 1082132816 (LWP 7663))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 default_attr
    from /lib/libpthread.so.0
  • #2 ??
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??

Thread 7 (Thread 1090525520 (LWP 7664))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 6 (Thread 1098918224 (LWP 7668))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 5 (Thread 1107310928 (LWP 7672))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 4 (Thread 1115703632 (LWP 7673))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 3 (Thread 1124096336 (LWP 7674))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ?? 






Comment 1


Karsten Bräckelmann





          2006-11-09 23:09:20 UTC
        



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






Comment 2


Karsten Bräckelmann





          2006-11-09 23:15:21 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and 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!


Also, could you please add a description, what you were doing when the application crashed?


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    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-11-16 00:48:27 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!