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 555638 - crash in Evolution Mail and Calendar: Evolution crashed when e...
crash in Evolution Mail and Calendar: Evolution crashed when e...
Status: RESOLVED DUPLICATE of bug 541872
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-09 05:10 UTC by meta.core.techs
Modified: 2008-10-10 07:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description meta.core.techs 2008-10-09 05:10:34 UTC
What were you doing when the application crashed?
Evolution crashed when exiting the application by using the close window button in the titlebar.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-vserver-powerpc #1 SMP Wed Sep 10 14:01:48 CEST 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crystal-Green

Memory status: size: 132763648 vsize: 132763648 resident: 46956544 share: 29118464 rss: 46956544 rss_rlim: 4294967295
CPU usage: start_time: 1223509882 rtime: 284928 utime: 271734 stime: 13194 cutime:62 cstime: 199 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x4806ea50 (LWP 9822)]
[New Thread 0x4a21e460 (LWP 9926)]
[New Thread 0x4921e460 (LWP 9863)]
0x0f60a290 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x4806ea50 (LWP 9822))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 segv_redirect
    at main.c line 519
  • #6 <signal handler called>
  • #7 ??
  • #8 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #9 rss_finalize
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #10 exit
    from /lib/libc.so.6
  • #11 generic_start_main
    from /lib/libc.so.6
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (124 sec old) ---------------------
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Mail'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Mail'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Mail'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Mail'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Mail'
(evolution:9822): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(evolution:9822): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
RSS: cleaning all remaining sessions ...done
--------------------------------------------------
Comment 1 Akhil Laddha 2008-10-10 07:43:33 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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