Bug 467913 – crash in Tasks: Viewing folders just mov...

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 467913 - crash in Tasks: Viewing folders just mov...


Summary:	crash in Tasks: Viewing folders just mov...


Status:	RESOLVED DUPLICATE of bug 431396

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-08-18 09:46 UTC by mikewheeler971
Modified:	2007-09-04 23:10 UTC

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

Description mikewheeler971 2007-08-18 09:46:17 UTC

Version: 2.10

What were you doing when the application crashed?
Viewing folders just moved to trash 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-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 109002752 vsize: 109002752 resident: 41426944 share: 29286400 rss: 41426944 rss_rlim: 4294967295
CPU usage: start_time: 1187433787 rtime: 451 utime: 416 stime: 35 cutime:41 cstime: 16 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 -1208214800 (LWP 3332)]
[New Thread -1216984176 (LWP 3418)]
[New Thread -1249457264 (LWP 3417)]
[New Thread -1267410032 (LWP 3373)]
[New Thread -1227474032 (LWP 3354)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 156108

Thread 1 (Thread -1208214800 (LWP 3332))

#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 (84 sec old) ---------------------
** (evolution:3332): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3332): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3332): 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:3332): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9751020'
(evolution:3332): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9751140'
(evolution:3332): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed
(evolution:3332): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-04 23:10:12 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 431396 ***