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 512024 - Crashes when reading calendar data from newer version (2.12.1)
Crashes when reading calendar data from newer version (2.12.1)
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-25 11:49 UTC by Chris Wilson
Modified: 2009-10-01 11:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Chris Wilson 2008-01-25 11:49:06 UTC
Steps to reproduce:
1. Open evolution 2.8.1, no problems, and close.
2. Open evolution 2.12.1, configuration upgraded, no problems, and close.
3. Open evolution 2.8.1, crashes on startup.


Stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233226064 (LWP 12157)]
0xb340ba70 in calendar_component_init (component=0x80ae6f0)
    at calendar-component.c:199
199     calendar-component.c: No such file or directory.
        in calendar-component.c
(gdb) apply all bt
Undefined command: "apply".  Try "help".
(gdb) thread apply all bt

Thread 1 (Thread -1233226064 (LWP 12157))

  • #0 calendar_component_init
    at calendar-component.c line 199
  • #1 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #2 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #3 bonobo_object_add_interface
    from /usr/lib/libbonobo-2.so.0
  • #4 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #7 calendar_component_peek
    at calendar-component.c line 1719
  • #8 factory
    at main.c line 175
  • #9 bonobo_marshal_OBJECT__STRING
    from /usr/lib/libbonobo-2.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #12 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #13 bonobo_generic_factory_get_type
    from /usr/lib/libbonobo-2.so.0
  • #14 bonobo_shlib_factory_get_type
  • #15 bonobo_generic_factory_get_type
    from /usr/lib/libbonobo-2.so.0
  • #16 _ORBIT_skel_small_Bonobo_GenericFactory_createObject
    from /usr/lib/libbonobo-activation.so.4
  • #17 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #18 Bonobo_GenericFactory_createObject
    from /usr/lib/libbonobo-activation.so.4
  • #19 bonobo_activation_activate_shlib_server
    from /usr/lib/libbonobo-activation.so.4
  • #20 bonobo_activation_init_activation_env
    from /usr/lib/libbonobo-activation.so.4
  • #21 bonobo_activation_activate
    from /usr/lib/libbonobo-activation.so.4
  • #22 bonobo_activation_activate_from_id
    from /usr/lib/libbonobo-activation.so.4
  • #23 query_components
    at e-component-registry.c line 192
  • #24 e_component_registry_peek_list
    at e-component-registry.c line 295
  • #25 e_shell_construct
    at e-shell.c line 688
  • #26 e_shell_new
    at e-shell.c line 736
  • #27 idle_cb
    at main.c line 350
  • #28 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #32 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #33 main
    at main.c line 615


Other information:
We have several users with NFS shared home directories moving between evo 2.8.1 (ubuntu 6.10) and evo 2.12.1 (ubuntu 7.04).

We discovered that some users who use the calendar on 2.12.1 have crashes when they go back to 2.8.1 afterwards. 

gconftool-2 --recursive-unset /apps/evolution/calendar is a workaround, but deletes any additional calendars.

Ubuntu bug filed at https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/175530 more than a month ago, no response so far.
Comment 1 André Klapper 2008-01-25 13:47:59 UTC
did you also stop evolution-data-server 1.12 and ran evolution-data-server 1.8?
Comment 2 Chris Wilson 2008-01-25 14:20:06 UTC
Just tested killing evolution-data-server before starting evo 2.8.1, and the problem persists.

By the way this is on two separate machines with an NFS-shared /home filesystem, so EDS 1.12 and 1.8 can be running at the same time on different machines.
Comment 3 André Klapper 2008-01-25 14:27:46 UTC
that did not answer my question.
the question is whether e-d-s 1.8.x gets started when evo 2.8.x gets started. the e-d-s version number would be interesting to have here.

e-d-s is a single-user server. i can predict that you will run into problems if you run two instances of e-d-s, i'd close such reports as NOTABUG.
Comment 4 Chris Wilson 2008-01-25 15:02:26 UTC
EDS 1.8.x gets started with Evo 2.8.1:

chris@fen-ndiyo2(~)$ ps auxww | grep evolution | grep chris
chris    15587  0.0  0.4  29700  9892 ?        Sl   14:17   0:00 /usr/lib/evolution/2.8/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.8 --oaf-ior-fd=19
chris    24946  0.0  0.0   2804   788 pts/4    S+   14:57   0:00 grep evolution

chris@fen-ndiyo2(~)$ kill 15587

chris@fen-ndiyo2(~)$ ps auxww | grep evolution | grep chris
chris    24982  0.0  0.0   2800   784 pts/4    S+   14:58   0:00 grep evolution

chris@fen-ndiyo2(~)$ gdb evolution
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) r
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread -1232959824 (LWP 25039)]
CalDAV Eplugin starting up ...

(evolution-2.8:25039): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(evolution-2.8:25039): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evolution-2.8:25039): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one

(evolution-2.8:25039): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'

(evolution-2.8:25039): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(evolution-2.8:25039): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evolution-2.8:25039): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `ESourceGroup'

(evolution-2.8:25039): e-data-server-CRITICAL **: e_source_group_peek_base_uri: assertion `E_IS_SOURCE_GROUP (group)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1232959824 (LWP 25039)]
0xb344ca70 in calendar_component_init (component=0x80ae6f0)
    at calendar-component.c:199
199     calendar-component.c: No such file or directory.
        in calendar-component.c
(gdb) The program is running.  Exit anyway? (y or n) y

chris@fen-ndiyo2(~)$ ps auxww | grep evolution | grep chris
chris    25056  0.6  0.2  18084  5944 ?        Sl   14:58   0:00 /usr/lib/evolution/evolution-data-server-1.8 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck --oaf-ior-fd=18
chris    25061  2.8  0.4  29700  9900 ?        Sl   14:58   0:00 /usr/lib/evolution/2.8/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.8 --oaf-ior-fd=19
chris    25098  0.0  0.0   2804   788 pts/4    S+   14:58   0:00 grep evolution

This is with no other EDS running on the other machine.
Comment 5 Chris Wilson 2008-01-25 15:07:46 UTC
chris@fen-ndiyo2(~)$ /usr/lib/evolution/evolution-data-server-1.8 --version
evolution-data-server-Message: Starting server
Gnome evolution-data-server 1.8.1
Comment 6 André Klapper 2009-07-24 18:01:48 UTC
This crash report has been submitted against Evolution version 2.10 (or earlier).
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field?
Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Comment 7 Akhil Laddha 2009-10-01 11:51:36 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.3 or 2.28.0 or later), please reopen. thanks in advance.