Bug 581763 – crash in Home Folder: nüschts

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 581763 - crash in Home Folder: nüschts


Summary:	crash in Home Folder: nüschts


Status:	RESOLVED DUPLICATE of bug 356497

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-05-07 16:10 UTC by karl.cox
Modified:	2009-05-07 16:29 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description karl.cox 2009-05-07 16:10:41 UTC

What were you doing when the application crashed?
nüschts


Distribution: Unknown
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-2-amd64 #1 SMP Thu Mar 26 02:56:43 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 94003200 vsize: 94003200 resident: 32993280 share: 15523840 rss: 32993280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241707323 rtime: 512 utime: 416 stime: 96 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xf6a6e9a0 (LWP 11964)]
0xf72ad3d1 in waitpid () from /lib/libpthread.so.0

+ Trace 215219

Thread 1 (Thread 0xf6a6e9a0 (LWP 11964))

#0 waitpid
from /lib/libpthread.so.0
#1 IA__g_spawn_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
#2 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 strcmp
from /lib/libc.so.6
#7 update_places
at nautilus-places-sidebar.c line 251
#8 update_places_cb
at nautilus-places-sidebar.c line 408
#9 g_idle_dispatch
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 4090
#10 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2012
#11 g_main_context_iterate
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2645
#12 IA__g_main_loop_run
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
#13 IA__gtk_main
at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkmain.c line 1163
#14 main
at nautilus-main.c line 565
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
(nautilus:11964): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NautilusPlacesSidebar'
(nautilus:11964): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed
(nautilus:11964): Gtk-CRITICAL **: gtk_list_store_clear: assertion `GTK_IS_LIST_STORE (list_store)' failed
** (nautilus:11964): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
(nautilus:11964): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
(nautilus:11964): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
(nautilus:11964): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed
(nautilus:11964): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed
--------------------------------------------------

Comment 1 A. Walton 2009-05-07 16:29:58 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 356497 ***