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 360571 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 360341
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-08 08:32 UTC by paal63
Modified: 2006-10-08 12:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description paal63 2006-10-08 08:32:57 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 5.10 (breezy)
Gnome Release: 2.15.91 2006-08-13 (Debian)
BugBuddy Version: 2.16.0

Memory status: size: 71802880 vsize: 0 resident: 71802880 share: 0 rss: 22921216 rss_rlim: 0
CPU usage: start_time: 1160296046 rtime: 0 utime: 203 stime: 0 cutime:189 cstime: 0 timeout: 14 it_real_value: 0 frequency: 2

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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232783680 (LWP 5684)]
[New Thread -1265808496 (LWP 5740)]
[New Thread -1257419888 (LWP 5739)]
[New Thread -1248429168 (LWP 5704)]
[New Thread -1239397488 (LWP 5703)]
0xb76f7f61 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 75186

Thread 1 (Thread -1232783680 (LWP 5684))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870 






Comment 1


Elijah Newren





          2006-10-08 12:51:23 UTC
        



Identical stack trace to your previous report in bug 360341.

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