Bug 460496 – crash in Tasks: switching from sub-folde...

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 460496 - crash in Tasks: switching from sub-folde...


Summary:	crash in Tasks: switching from sub-folde...


Status:	RESOLVED DUPLICATE of bug 457874

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-26 08:49 UTC by vaclav.zelenka
Modified:	2007-08-17 13:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description vaclav.zelenka 2007-07-26 08:49:24 UTC

Version: 2.10

What were you doing when the application crashed?
switching from sub-folder to main "incomming messages" folder


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ThinIce
Icon Theme: Bluecurve

Memory status: size: 191705088 vsize: 191705088 resident: 79233024 share: 59117568 rss: 79233024 rss_rlim: 4294967295
CPU usage: start_time: 1185435527 rtime: 3404 utime: 3170 stime: 234 cutime:40 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209039136 (LWP 2980)]
[New Thread -1211139184 (LWP 3575)]
[New Thread -1309152368 (LWP 3574)]
[New Thread -1319908464 (LWP 3156)]
[New Thread -1319642224 (LWP 3062)]
[New Thread -1254413424 (LWP 3026)]
[New Thread -1221629040 (LWP 3025)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 150632

Thread 1 (Thread -1209039136 (LWP 2980))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove
from /lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#21 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#23 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#24 ??
from /usr/lib/libbonoboui-2.so.0
#25 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /lib/libgobject-2.0.so.0
#27 ??
from /lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#29 g_signal_emit
from /lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libbonoboui-2.so.0
#31 ??
from /usr/lib/libbonoboui-2.so.0
#32 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#33 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#34 ??
from /usr/lib/libbonoboui-2.so.0
#35 _ORBIT_skel_small_Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#36 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#37 Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#38 ??
from /usr/lib/libbonoboui-2.so.0
#39 bonobo_ui_component_rm
from /usr/lib/libbonoboui-2.so.0
#40 gal_view_menus_unmerge
from /usr/lib/evolution/2.10/libmenus.so.0
#41 ??
from /usr/lib/evolution/2.10/libmenus.so.0
#42 g_object_unref
from /lib/libgobject-2.0.so.0
#43 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#44 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#45 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#46 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#47 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#48 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#49 ??
from /lib/libglib-2.0.so.0
#50 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#51 ??
from /lib/libglib-2.0.so.0
#52 g_main_loop_run
from /lib/libglib-2.0.so.0
#53 bonobo_main
from /usr/lib/libbonobo-2.so.0
#54 main
#0 __kernel_vsyscall



----------- .xsession-errors (42 sec old) ---------------------
(evolution:2980): e-dateedit.c-WARNING **: time_text:17:00
(evolution:2980): e-dateedit.c-WARNING **: time_text:12:00
(evolution:2980): e-dateedit.c-WARNING **: time_text:17:00
(evolution:2980): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9edda20'
(evolution:2980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9edd6c0'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x300d6a8 specified for 0x300d776 (Character ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x300d6a8 specified for 0x300d910 (Character ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x300da1a specified for 0x300daa4 (Character ).
--------------------------------------------------

Comment 1 palfrey 2007-08-17 13:15:42 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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