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 365832 - crash in Evolution: changing exchange accoun...
crash in Evolution: changing exchange accoun...
Status: RESOLVED DUPLICATE of bug 312348
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-27 16:53 UTC by rpuckett
Modified: 2006-10-28 02:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rpuckett 2006-10-27 16:53:50 UTC 
What were you doing when the application crashed?
changing exchange accounts


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 191836160 vsize: 0 resident: 191836160 share: 0 rss: 42270720 rss_rlim: 0
CPU usage: start_time: 1161961751 rtime: 0 utime: 3474 stime: 0 cutime:3336 cstime: 0 timeout: 138 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232906576 (LWP 8949)]
[New Thread -1398424672 (LWP 15332)]
[New Thread -1313395808 (LWP 15320)]
[New Thread -1517634656 (LWP 11409)]
[New Thread -1509241952 (LWP 9274)]
[New Thread -1332728928 (LWP 9043)]
[New Thread -1305003104 (LWP 9038)]
[New Thread -1288000608 (LWP 8971)]
[New Thread -1279411296 (LWP 8961)]
[New Thread -1248486496 (LWP 8957)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78888

Thread 1 (Thread -1232906576 (LWP 8949))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 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
    from /usr/lib/libecal-1.2.so.7
  • #16 e_cal_view_start
    from /usr/lib/libecal-1.2.so.7
  • #17 e_cal_model_copy_component_data
    from /usr/lib/evolution/2.8/components/libevolution-calendar.so
  • #18 e_cal_model_copy_component_data
    from /usr/lib/evolution/2.8/components/libevolution-calendar.so
  • #19 gnome_calendar_discard_view_menus
    from /usr/lib/evolution/2.8/components/libevolution-calendar.so
  • #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 e_cal_free_alarms
    from /usr/lib/libecal-1.2.so.7
  • #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
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-10-28 02:35:20 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 312348 ***