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 261154 - evolution crashed on startup due to dodge calendar setup?
evolution crashed on startup due to dodge calendar setup?
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
1.5.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 264107 313111 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-07-05 04:35 UTC by Rodd Clarkson
Modified: 2013-09-10 13:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rodd Clarkson 2004-07-05 04:35:09 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.7.1 unspecified
Gnome-Distributor: GARNOME
Synopsis: evolution crashed on startup due to dodge calendar setup?
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.7.1)
Description:
Description of the crash:

Might be due to a dodgy calendar I set-up.

I manually added a calendar (using an ics file generated from the MacOS
X calendar software - iCal?) but stuffed up the apache conf.

I then fixed the apache conf, but the calendar still did not load, so I
--force-shutdown'ed evo and then restarted it to bve greated by this
crash.

of course it could be unrelated, but it's unlike.


Debugging Information:

Backtrace was generated from '/home/rodd/gnome-2.7.1/bin/evolution-1.5'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150732128 (LWP 5693)]
[New Thread 29371312 (LWP 5710)]
[Thread debugging using libthread_db enabled]
[New Thread -150732128 (LWP 5693)]
[New Thread 29371312 (LWP 5710)]
[Thread debugging using libthread_db enabled]
[New Thread -150732128 (LWP 5693)]
[New Thread 29371312 (LWP 5710)]
0x00d88402 in ?? ()

Thread 1 (Thread -150732128 (LWP 5693))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #3 segv_redirect
    at main.c line 454
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/tls/libc.so.6
  • #6 process_detached_instances
    at e-cal.c line 2830
  • #7 generate_instances
    at e-cal.c line 2949
  • #8 e_cal_generate_instances_for_object
    at e-cal.c line 3061
  • #9 tag_calendar_by_comp
    at tag-calendar.c line 217
  • #10 dn_e_cal_view_objects_added_cb
    at gnome-cal.c line 421
  • #11 g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 601
  • #12 g_closure_invoke
    at gclosure.c line 437
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2436
  • #14 g_signal_emit_valist
    at gsignal.c line 2195
  • #15 g_signal_emit
    at gsignal.c line 2239
  • #16 objects_added_cb
    at e-cal-view.c line 77
  • #17 g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 601
  • #18 g_closure_invoke
    at gclosure.c line 437
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2436
  • #20 g_signal_emit_valist
    at gsignal.c line 2195
  • #21 g_signal_emit
    at gsignal.c line 2239
  • #22 impl_notifyObjectsAdded
    at e-cal-view-listener.c line 124
  • #23 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalViewListener_notifyObjectsAdded
    at Evolution-DataServer-Calendar-common.c line 34
  • #24 ORBit_POAObject_invoke
    at poa.c line 1141
  • #25 ORBit_OAObject_invoke
    at orbit-adaptor.c line 284
  • #26 ORBit_small_invoke_adaptor
    at orbit-small.c line 835
  • #27 ORBit_POAObject_handle_request
    at poa.c line 1350
  • #28 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1418
  • #29 giop_thread_queue_process
    at giop.c line 743
  • #30 giop_mainloop_handle_input
    at giop.c line 450
  • #31 link_source_dispatch
    at linc-source.c line 53
  • #32 g_main_dispatch
    at gmain.c line 1942
  • #33 g_main_context_dispatch
    at gmain.c line 2492
  • #34 g_main_context_iterate
    at gmain.c line 2573
  • #35 g_main_loop_run
    at gmain.c line 2777
  • #36 bonobo_main
    at bonobo-main.c line 297
  • #37 main
    at main.c line 604
  • #0 ??



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Rodd Clarkson 2004-07-05 04:48:41 UTC
Turns out the ics file and evolution don't like each other.

I removed the calendar setup using gconf-editor and evo works once again.

I then tried loading the calendar using a webcal:// address and
evolution broke.  Removed the offending calendar using gconf-editor
and it works again.

I'll see if I can give you a copy of the file, but it's my bosses work
calendar, so it would be great if it could be a little repected.  I'll
ask my boss and then find someone in #evolution who might be able to
handle the file discreetly.

Tell me if the backtrace is good enough that the file isn't needed?
Comment 2 Rodd Clarkson 2004-07-07 02:06:50 UTC
Okay, a little more information.

The same guy sent me another ics file for a different calendar in iCal
and this ics file works.

He also sent me an updated ics file for the first calendar and this
still crashes evo.

I'm not sure if this is related, but the initial ics file (and the
update) both add calendar information AND task information, whereas
the other ics file only had calendar information.

If I delete the calendar information (using gconf-editor) but leave
the task information then evo works and the tasks appear (both in evo
and also in the calendar display for the panel-clock.)
Comment 3 Gerardo Marin 2004-08-27 18:08:29 UTC
*** bug 264107 has been marked as a duplicate of this bug. ***
Comment 4 Gerardo Marin 2004-08-27 18:08:57 UTC
Up to major since duplicate arrived.
Comment 5 Rodrigo Moya 2005-03-29 16:33:19 UTC
Yes, we might need the file, maybe you can attach it here removing all
sensitive information (replacing text with 'xxxx's for instance).
Comment 6 Teppo Turtiainen 2005-08-11 15:26:25 UTC
*** Bug 313111 has been marked as a duplicate of this bug. ***
Comment 7 viren 2005-09-09 06:57:25 UTC
closing this bug as the reporter has not responded. Please reopen the bug if you
find this happening in the latest version with the needed information.