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 359606 - After e-d-s dies, can't change to any other calendar or delete the calendar that killed e-d-s in the first place
After e-d-s dies, can't change to any other calendar or delete the calendar t...
Status: RESOLVED DUPLICATE of bug 271693
Product: evolution
Classification: Applications
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-04 14:04 UTC by Sam Morris
Modified: 2006-10-04 14:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sam Morris 2006-10-04 14:04:03 UTC 
Distribution: Debian testing/unstable
Package: Evolution
Severity: normal
Version: GNOME2.15.91 (null)
Gnome-Distributor: Debian
Synopsis: After e-d-s dies, can't change to any other calendar or delete the calendar that killed e-d-s in the first place
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: (null)
BugBuddy-GnomeVersion: 2.0 (2.16.0)
Description:
Description of the crash:
Related to bug #359574

After e-d-s dies and respawns, Evolution itself crashes if I try to
change to select/view any other calendar (even local ones). I can't even
remove the buggy calendar.


Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1501820064 (LWP 9739)]
[New Thread -1542308944 (LWP 9772)]
[New Thread -1533916240 (LWP 9768)]
[New Thread -1575879760 (LWP 9761)]
[New Thread -1533650000 (LWP 9747)]
[New Thread -1524233296 (LWP 9746)]
[New Thread -1515803728 (LWP 9744)]
[New Thread -1507411024 (LWP 9743)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74498

Thread 1 (Thread -1501820064 (LWP 9739))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
    at gmessages.c line 552
  • #10 e_cal_model_set_default_client
    at e-cal-model.c line 1173
  • #11 default_client_cal_opened_cb
    at gnome-cal.c line 2682
  • #12 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #16 IA__g_signal_emit
    at gsignal.c line 2241
  • #17 async_signal_idle_cb
    at e-cal.c line 1863
  • #18 g_idle_dispatch
    at gmain.c line 3926
  • #19 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #20 g_main_context_iterate
    at gmain.c line 2677
  • #21 IA__g_main_loop_run
    at gmain.c line 2881
  • #22 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #23 main
    at main.c line 615
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-10-04 14:04 -------


Unknown version (null) in product Evolution.  Setting version to "unspecified".
Comment 1 Karsten Bräckelmann 2006-10-04 14:12:05 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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