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 270072 - Crash: after setting evolution cal webcal URL under personal into for sync evolution failed to start.
Crash: after setting evolution cal webcal URL under personal into for sync ev...
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-12-01 05:58 UTC by greg_tinker
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description greg_tinker 2004-12-01 05:58:51 UTC 
Distribution: SuSE Linux 9.2 (i586)
Package: Evolution
Priority: Critical
Version: GNOME2.6. 2.0.2
Gnome-Distributor: SUSE
Synopsis: after setting evolution cal webcal URL under personal into for sync evolution failed to start.
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.0.2
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. configure Webcal URL
2. ps -ef | grep evol, kill all PID
3. evolution-2.0 --disable-sound

Expected Results:

Start with sound disabled.  Why? because its holding the ESD open on the
sound card and no other app can use it...  Another bug that I wish to
work later.

How often does this happen?
Every time.

Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-2.0'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1093485472 (LWP 21956)]
[New Thread 1115220912 (LWP 21964)]
[Thread debugging using libthread_db enabled]
[New Thread 1093485472 (LWP 21956)]
[New Thread 1115220912 (LWP 21964)]
[Thread debugging using libthread_db enabled]
[New Thread 1093485472 (LWP 21956)]
[New Thread 1115220912 (LWP 21964)]
0xffffe410 in ?? ()

+ Trace 52990

Thread 1 (Thread 1093485472 (LWP 21956))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 segv_redirect
    at main.c line 420
  • #7 <signal handler called>
  • #8 g_type_check_instance_cast
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #9 categories_changed_idle_cb
    at e-cal.c line 975
  • #10 g_idle_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #12 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #13 g_main_context_iteration
    from /opt/gnome/lib/libglib-2.0.so.0
  • #14 send_message
    at soup-session-async.c line 224
  • #15 soup_session_send_message
    at soup-session.c line 1197
  • #16 itip_publish_comp
    at itip-utils.c line 1181
  • #17 e_pub_publish
    at e-pub-utils.c line 316
  • #18 init_calendar_publishing_cb
    at calendar-component.c line 608
  • #19 g_idle_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #21 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #23 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #24 main
    at main.c line 585
  • #0 ?? 



Unknown reporter: greg_tinker@bellsouth.net, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Gerardo Marin 2004-12-03 20:36:45 UTC 

*** This bug has been marked as a duplicate of 269566 ***
Comment 2 Gerardo Marin 2004-12-03 20:52:16 UTC 
Reopening since this doesn't happen on migration.
Comment 3 Gerardo Marin 2004-12-06 18:35:54 UTC 
*** bug 270204 has been marked as a duplicate of this bug. ***
Comment 4 Rodrigo Moya 2005-03-23 16:38:02 UTC 
This shouldn't happen anymore, as the client does not get
categories_changed signals anymore.