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 358699 - crash in Evolution: I launched evolution and...
crash in Evolution: I launched evolution and...
Status: RESOLVED DUPLICATE of bug 312348
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-01 06:44 UTC by jauco noordzij
Modified: 2006-10-01 06:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jauco noordzij 2006-10-01 06:44:19 UTC
What were you doing when the application crashed?
I launched evolution and clicked on the calendar button.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 183418880 vsize: 0 resident: 183418880 share: 0 rss: 26488832 rss_rlim: 0
CPU usage: start_time: 1159684879 rtime: 0 utime: 216 stime: 0 cutime:209 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

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 -1232877904 (LWP 15560)]
[New Thread -1349112928 (LWP 15583)]
[New Thread -1340720224 (LWP 15582)]
[New Thread -1332327520 (LWP 15573)]
[New Thread -1323541600 (LWP 15572)]
[New Thread -1276531808 (LWP 15570)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232877904 (LWP 15560))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ORBit_object_peek_connection
    from /usr/lib/libORBit-2.so.0
  • #11 ORBit_object_get_connection
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #14 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #15 GNOME_Evolution_Calendar_CalView_start
    at Evolution-DataServer-Calendar-stubs.c line 10
  • #16 e_cal_view_start
    at e-cal-view.c line 389
  • #17 update_e_cal_view_for_client
    at e-cal-model.c line 1519
  • #18 add_new_client
    at e-cal-model.c line 1590
  • #19 client_cal_opened_cb
    at gnome-cal.c line 2602
  • #20 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 async_signal_idle_cb
    at e-cal.c line 1863
  • #26 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 Jauco Noordzij 2006-10-01 06:46:16 UTC
I should probably report this to ubuntu instead of here, no?
Comment 2 Elijah Newren 2006-10-01 06:47:49 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.

Matches the stack traces in bug 358571 and bug 358242, which have been marked as a duplicate of bug 312348

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