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 570669 - crash in Evolution Mail and Calendar: switchewd to calendar vi...
crash in Evolution Mail and Calendar: switchewd to calendar vi...
Status: RESOLVED DUPLICATE of bug 570668
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: 2009-02-05 16:19 UTC by Sam Morris
Modified: 2009-02-05 23:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Sam Morris 2009-02-05 16:19:07 UTC
What were you doing when the application crashed?
switchewd to calendar view


Distribution: Debian 5.0
Gnome Release: 2.24.2 2009-01-04 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10599902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 325136384 vsize: 325136384 resident: 12865536 share: 10366976 rss: 12865536 rss_rlim: 18446744073709551615
CPU usage: start_time: 1233850710 rtime: 6 utime: 4 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fff977a17e0 (LWP 16683)]
[New Thread 0x41487950 (LWP 16684)]
0x00007fff8f4205ef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7fff977a17e0 (LWP 16683))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.18.4/glib/gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.18.4/glib/gspawn.c line 694
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 raise
    from /lib/libc.so.6
  • #7 abort
    from /lib/libc.so.6
  • #8 IA__g_logv
  • #9 IA__g_log
    at /tmp/buildd/glib2.0-2.18.4/glib/gmessages.c line 517
  • #10 g_mutex_free_posix_impl
    at /tmp/buildd/glib2.0-2.18.4/gthread/gthread-posix.c line 171
  • #11 e_data_cal_factory_finalize
    at e-data-cal-factory.c line 286
  • #12 IA__g_object_unref
    at /tmp/buildd/glib2.0-2.18.4/gobject/gobject.c line 2417
  • #13 bonobo_object_unref
    from /usr/lib/libbonobo-2.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (7 sec old) ---------------------
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
(evolution:15190): libecal-WARNING **: e-cal.c:1034: Could not activate calendar factory (OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2)
--------------------------------------------------
Comment 1 André Klapper 2009-02-05 23:59:02 UTC

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