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 435481 - crash in Evolution:
crash in Evolution:
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-03 11:20 UTC by benjamin.leblanc
Modified: 2009-02-27 04:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description benjamin.leblanc 2007-05-03 11:20:03 UTC
What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 491847680 vsize: 491847680 resident: 14204928 share: 19644416 rss: 33849344 rss_rlim: -1485294592
CPU usage: start_time: 1178191101 rtime: 96 utime: 84 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47294155984080 (LWP 8082)]
[New Thread 1107310912 (LWP 8092)]
[New Thread 1090525504 (LWP 8091)]
[New Thread 1098918208 (LWP 8088)]
[New Thread 1082132800 (LWP 8085)]
(no debugging symbols found)
0x00002b0384e87c5f in waitpid () from /lib64/libpthread.so.0

Thread 5 (Thread 1082132800 (LWP 8085))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_106
    from /lib64/libpthread.so.0

Comment 1 palfrey 2007-05-03 12:44:46 UTC
Thanks for taking the time to report this bug.
Unfortunately, that 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 benjamin.leblanc 2007-05-08 12:25:14 UTC
I am not doing anything special when a crashing bug happens with evolution: it can be right after session login, even after a fresh system reboot, or while I was using many other applications.
I'm sorry but for the moment, I don't find any evolution-debuginfo package available in my distribution.
Comment 4 benjamin.leblanc 2007-05-08 14:20:59 UTC
Here is a copy of stack trace with debuginfo

Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 492339200 vsize: 492339200 resident: 10723328 share: 19705856 rss: 30429184 rss_rlim: -1485294592
CPU usage: start_time: 1178633880 rtime: 96 utime: 81 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47973822483664 (LWP 21264)]
[New Thread 1115703616 (LWP 21276)]
[New Thread 1107310912 (LWP 21275)]
[New Thread 1098918208 (LWP 21274)]
[New Thread 1090525504 (LWP 21271)]
[New Thread 1082132800 (LWP 21268)]
0x00002ba1c4303c5f in waitpid () from /lib64/libpthread.so.0

Thread 6 (Thread 1082132800 (LWP 21268))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_106
    from /lib64/libpthread.so.0

Comment 5 benjamin.leblanc 2007-05-08 14:31:59 UTC
This one was copied when the crash occurred just after a system reboot... hope this help.

----

Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 491315200 vsize: 491315200 resident: 9719808 share: 19591168 rss: 29310976 rss_rlim: -1485294592
CPU usage: start_time: 1178634401 rtime: 90 utime: 82 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46962726493392 (LWP 4427)]
[New Thread 1115703616 (LWP 4464)]
[New Thread 1107310912 (LWP 4463)]
[New Thread 1098918208 (LWP 4459)]
[New Thread 1090525504 (LWP 4439)]
[New Thread 1082132800 (LWP 4436)]
0x00002ab65a2bcc5f in waitpid () from /lib64/libpthread.so.0

Thread 6 (Thread 1082132800 (LWP 4436))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_106
    from /lib64/libpthread.so.0

Comment 6 benjamin.leblanc 2007-05-08 14:39:34 UTC
I have forgotten to install the gtk2 debuginfo package. Now its done and here is the trace:

Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 483581952 vsize: 483581952 resident: 9949184 share: 19746816 rss: 29696000 rss_rlim: -1485294592
CPU usage: start_time: 1178634972 rtime: 90 utime: 82 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47144692743376 (LWP 5519)]
[New Thread 1107310912 (LWP 5529)]
[New Thread 1098918208 (LWP 5528)]
[New Thread 1090525504 (LWP 5526)]
[New Thread 1082132800 (LWP 5523)]
0x00002ae0b8346c5f in waitpid () from /lib64/libpthread.so.0

Thread 5 (Thread 1082132800 (LWP 5523))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_106
    from /lib64/libpthread.so.0

Comment 7 Akhil Laddha 2009-01-21 04:09:42 UTC
All traces are different, there is no relation , can you please try current stable gnome version 2.24.3 and provide us feed back , thanks. 
Comment 8 Akhil Laddha 2009-02-27 04:30:10 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.24.x or later), please reopen. thanks in advance.