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 407649 - crash in Evolution: switching between vertic...
crash in Evolution: switching between vertic...
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-02-13 22:19 UTC by Eloi Primaux
Modified: 2007-03-19 20:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Eloi Primaux 2007-02-13 22:19:21 UTC 
Version: 2.10.x

What were you doing when the application crashed?
switching between vertical/default show


Distribution: Unknown
Gnome Release: 2.17.91 2007-02-13 (JHBuild)
BugBuddy Version: 2.17.3

System: Linux 2.6.19.2-mactel #6 SMP PREEMPT Fri Feb 2 21:39:35 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70199002
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 98197504 vsize: 98197504 resident: 27176960 share: 19357696 rss: 27176960 rss_rlim: 4294967295
CPU usage: start_time: 1171404416 rtime: 388 utime: 356 stime: 32 cutime:46 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/local/bin/evolution-2.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235343696 (LWP 6815)]
[New Thread -1300264016 (LWP 8028)]
[New Thread -1291265104 (LWP 6918)]
[New Thread -1282872400 (LWP 6917)]
[New Thread -1274479696 (LWP 6904)]
[New Thread -1254065232 (LWP 6860)]
[New Thread -1245631568 (LWP 6855)]
0xb7f3d410 in __kernel_vsyscall ()

+ Trace 110515

Thread 1 (Thread -1235343696 (LWP 6815))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /usr/local/lib/libgnomeui-2.so.0
  • #3 segv_redirect
  • #4 <signal handler called>
  • #5 ect_check
    from /usr/local/lib/evolution/2.10/libevolution-a11y.so.0
  • #6 ect_get_name
    from /usr/local/lib/evolution/2.10/libevolution-a11y.so.0
  • #7 atk_object_get_name
    from /usr/local/lib/libatk-1.0.so.0
  • #8 spi_atk_bridge_init_base
    from /usr/local/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 spi_atk_bridge_init_nil
    from /usr/local/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 spi_atk_bridge_focus_tracker
    from /usr/local/lib/gtk-2.0/modules/libatk-bridge.so
  • #11 atk_focus_tracker_notify
    from /usr/local/lib/libatk-1.0.so.0
  • #12 gail_focus_notify
    from /usr/local/lib/gtk-2.0/modules/libgail.so
  • #13 gail_focus_idle_handler
    from /usr/local/lib/gtk-2.0/modules/libgail.so
  • #14 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/local/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(gnome-panel:6809): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
(gnome-panel:6809): Bonobo-WARNING **: Cannot get value: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
camel-Message: --
(evolution-2.10:6815): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb631c61c(0x84262c8)
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 palfrey 2007-02-14 16:39:36 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Bruno Boaventura 2007-03-19 20:52:10 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!