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 638673 - evolution crash importing ics
evolution crash importing ics
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 647610 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-04 17:12 UTC by Ambrogio De Lorenzo
Modified: 2014-12-21 03:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ics file to import (1.15 KB, text/calendar)
2011-01-04 17:12 UTC, Ambrogio De Lorenzo 		Details
Crash report from gdb (32.83 KB, application/octet-stream)
2011-01-10 12:51 UTC, Ambrogio De Lorenzo 		Details

Description Ambrogio De Lorenzo 2011-01-04 17:12:40 UTC 
Created attachment 177497 [details]
ics file to import

I was unable to see a calendar after upgrading from 2.24.5 on fedora 10 to 2.32.1 on fedora 14.
So I imported the .ics using the import function but evolution crashed.

I isolated the event that made evo to crash.
See attached ics file.
Comment 1 Akhil Laddha 2011-01-05 04:12:11 UTC 
I have tried to import attached ics file in calendar but i don't get any crash. I am running evolution master (2.91.4).

Can you please provide us traces when evolution 2.32.1 crashes ?
Comment 2 Ambrogio De Lorenzo 2011-01-05 09:26:27 UTC 
I don't know how to obtain a trace.
Please explain me how.

Now I'm working hard to recover my old evolution to the new, because I lose a lot of things.
So it will be hard to reproduce the crash. But I can try with another user.

Even with a backup and restore I obtain the same behavior.
The strange thing is that with the restore evo doesn't crash but the calendar and addressbook are unavailable and unremovable.

Bye
 Ambrogio
Comment 3 Akhil Laddha 2011-01-05 10:07:36 UTC 
Please install debuginfo packages of evolution, evolution-data-server, glib2 and gtk2 in case you don't have them. More details can be found here:
http://live.gnome.org/GettingTraces

If you can reproduce it while running
under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
Comment 4 Ambrogio De Lorenzo 2011-01-10 12:51:06 UTC 
Created attachment 177931 [details]
Crash report from gdb

gdb output.
Crash on import from ics
Comment 5 Fabio Durán Verdugo 2011-02-25 17:16:33 UTC 
Paste here the attach backtrace

(gdb) thread apply all bt

+ Trace 226121

Thread 1 (Thread 0xb7fc3880 (LWP 14932))

  • #0 g_variant_is_trusted
    at gvariant-core.c line 600
  • #1 g_variant_builder_add_value
    at gvariant.c line 2932
  • #2 g_variant_valist_new
    at gvariant.c line 3928
  • #3 g_variant_new_va
  • #4 g_variant_new
  • #5 e_gdbus_cal_call_receive_objects_sync
    at e-gdbus-egdbuscal.c line 3683
  • #6 e_cal_receive_objects
    at e-cal.c line 3705
  • #7 update_objects
    at icalendar-importer.c line 190
  • #8 ivcal_import_items
    at icalendar-importer.c line 301
  • #9 g_idle_dispatch
    at gmain.c line 4254
  • #10 g_main_dispatch
    at gmain.c line 2149
  • #11 g_main_context_dispatch
    at gmain.c line 2702
  • #12 g_main_context_iterate
    at gmain.c line 2780
  • #13 g_main_loop_run
    at gmain.c line 2988
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
    at main.c line 679 
(gdb) quit
A debugging session is active.
Comment 6 Fabio Durán Verdugo 2011-04-13 01:12:24 UTC 
*** Bug 647610 has been marked as a duplicate of this bug. ***
Comment 7 Akhil Laddha 2011-07-14 10:23:25 UTC 
not sure if this bug has been fixed in bug 634573
Comment 8 André Klapper 2014-08-26 19:41:41 UTC 
This is a crash that was reported against a 2.x version. 
I'm sorry that this report did not receive investigation/attention when you filed it, but manpower is and was limited.

Is this still a problem in a recent version (3.12)? If not, this report should probably be closed as OBSOLETE nowadays as codebases change... :-/
Comment 9 André Klapper 2014-12-21 03:51:41 UTC 
Hi Ambrogio, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.