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 504882 - crash in Evolution Mail: starting evolution
crash in Evolution Mail: starting evolution
Status: RESOLVED DUPLICATE of bug 523463
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-21 15:20 UTC by Christoph Anton Mitterer
Modified: 2008-09-28 19:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Christoph Anton Mitterer 2007-12-21 15:20:48 UTC
What were you doing when the application crashed?
starting evolution


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

System: Linux 2.6.23 #1 SMP PREEMPT Wed Dec 5 16:04:04 CET 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 630304768 vsize: 630304768 resident: 65933312 share: 20115456 rss: 65933312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1198250419 rtime: 273 utime: 236 stime: 37 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0x2ae907e410f0 (LWP 3553)]
[New Thread 0x4680c950 (LWP 3617)]
[New Thread 0x4600b950 (LWP 3613)]
[New Thread 0x4580a950 (LWP 3612)]
[New Thread 0x45009950 (LWP 3611)]
[New Thread 0x44808950 (LWP 3606)]
[New Thread 0x44007950 (LWP 3602)]
[New Thread 0x43806950 (LWP 3599)]
[New Thread 0x43005950 (LWP 3595)]
[New Thread 0x42804950 (LWP 3593)]
[New Thread 0x42003950 (LWP 3589)]
[New Thread 0x41802950 (LWP 3587)]
[New Thread 0x41001950 (LWP 3585)]
[New Thread 0x40800950 (LWP 3583)]
(no debugging symbols found)
0x00002ae8ff88d34f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2ae907e410f0 (LWP 3553))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.14.4/glib/gspawn.c line 369
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.14.4/glib/gspawn.c line 677
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 IA__g_main_context_check
    at /build/buildd/glib2.0-2.14.4/glib/gmain.c line 2540
  • #6 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.4/glib/gmain.c line 2691
  • #7 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.4/glib/gmain.c line 2898
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 ??
  • #10 __libc_start_main
    from /lib/libc.so.6
  • #11 ??
  • #12 ??
  • #13 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
Find Items 0
get calestyo@scientia.net pop://calestyo%40scientia.net@pop3.dd24.net/
Find Items 0
get lhshas@googlemail.com pop://lhshas%40googlemail.com@pop.gmail.com/
Find Items 0
get mail@christoph.anton.mitterer.name pop://mail%40christoph.anton.mitterer.name@pop3.dd24.net/
Find Items 0
get calestyo@googlemail.com pop://calestyo%40googlemail.com@pop.gmail.com/
Find Items 0
get a2825ag pop://a2825ag@mailin.lrz-muenchen.de/
Find Items 0
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffb05fd000
capplet-common-Message: cleanup_cb: Enter
capplet-common-Message: cleanup_cb: Enter
--------------------------------------------------
Comment 1 Paul Smith 2008-03-19 22:46:22 UTC
Dup of bug #523463
Comment 2 Philip Withnall 2008-09-28 19:18:42 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 523463 ***