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 478585 - crash in Evolution: Crashed while opening. ...
crash in Evolution: Crashed while opening. ...
Status: RESOLVED DUPLICATE of bug 523463
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-20 12:59 UTC by Michael Schurter
Modified: 2008-09-28 18:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Michael Schurter 2007-09-20 12:59:41 UTC
What were you doing when the application crashed?
Crashed while opening.  Both my IMAP and Evolution folders had opened and the number of unread items in the inbox had updated, but nothing had appeared in the e-mail list or view panes.

I had left my Gnome session logged in for over 24 hours, and I'm assuming Evolutions backend was running that whole time if it makes any difference.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Tango

Memory status: size: 121966592 vsize: 121966592 resident: 27275264 share: 17489920 rss: 27275264 rss_rlim: 4294967295
CPU usage: start_time: 1190293047 rtime: 106 utime: 90 stime: 16 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb67c3aa0 (LWP 28517)]
[New Thread 0xb1b12b90 (LWP 28572)]
[New Thread 0xb2373b90 (LWP 28571)]
[New Thread 0xb2b74b90 (LWP 28549)]
[New Thread 0xb35fcb90 (LWP 28547)]
[New Thread 0xb3dfdb90 (LWP 28545)]
[New Thread 0xb45feb90 (LWP 28544)]
[New Thread 0xb4dffb90 (LWP 28543)]
[New Thread 0xb5903b90 (LWP 28541)]
[New Thread 0xb6222b90 (LWP 28540)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb67c3aa0 (LWP 28517))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 427
  • #4 <signal handler called>
  • #5 IA__g_main_context_check
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2540
  • #6 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2691
  • #7 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
    at main.c line 611
  • #0 __kernel_vsyscall


----------- .xsession-errors (13 sec old) ---------------------
observer removed
(evolution-2.10:3904): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution-2.10:3904): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(gecko:5656): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-terminal:5778): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gecko:5656): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gecko:5656): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
evolution-shell-Message: Killing old version of evolution-data-server...
--------------------------------------------------
Comment 1 Michael Schurter 2007-09-20 13:01:24 UTC
After executing "evolution --force-shutdown", Evolution started up just fine.  I am running Debian Sid and had upgraded some Gnome packages yesterday, so perhaps I needed to restart evolution's backend after that.
Comment 2 Paul Smith 2008-03-19 22:44:21 UTC
Dup of bug #523463
Comment 3 Claudio Saavedra 2008-09-28 18:46:39 UTC

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