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 506822 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-02 09:36 UTC by fs1502
Modified: 2008-01-02 14:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description fs1502 2008-01-02 09:36:32 UTC 
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: SphereCrystal

Memory status: size: 600203264 vsize: 600203264 resident: 43823104 share: 20725760 rss: 43823104 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199266542 rtime: 112 utime: 95 stime: 17 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0x2b26437b3cd0 (LWP 4161)]
[New Thread 0x45009950 (LWP 4227)]
[New Thread 0x44808950 (LWP 4199)]
[New Thread 0x44007950 (LWP 4196)]
[New Thread 0x43806950 (LWP 4195)]
[New Thread 0x43005950 (LWP 4190)]
[New Thread 0x42804950 (LWP 4189)]
[New Thread 0x42003950 (LWP 4188)]
[New Thread 0x41802950 (LWP 4187)]
[New Thread 0x41001950 (LWP 4186)]
[New Thread 0x40800950 (LWP 4185)]
(no debugging symbols found)
0x00002b263ae0b34f in waitpid () from /lib/libpthread.so.0

+ Trace 183779

Thread 1 (Thread 0x2b26437b3cd0 (LWP 4161))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4161): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-02 14:03:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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