Bug 466332 – crash in Open Folder:

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 466332 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 460524

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.19.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-13 18:42 UTC by e
Modified:	2007-08-21 20:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description e 2007-08-13 18:42:11 UTC

Version: 2.19.5

What were you doing when the application crashed?



Distribution: Fedora release 7.90 (Rawhide)
Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-2925.14.fc8xen #1 SMP Tue Jul 24 15:30:41 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 95023104 vsize: 95023104 resident: 36978688 share: 23482368 rss: 36978688 rss_rlim: 4294967295
CPU usage: start_time: 1187041187 rtime: 180 utime: 158 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209063664 (LWP 3437)]
(no debugging symbols found)
0x00135402 in __kernel_vsyscall ()

+ Trace 154939

Thread 1 (Thread -1209063664 (LWP 3437))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_logv
from /lib/libglib-2.0.so.0
#5 g_log
from /lib/libglib-2.0.so.0
#6 g_assert_warning
from /lib/libglib-2.0.so.0
#7 ??
#8 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 gtk_tree_model_row_deleted
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
#23 ??
#24 ??
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** ERROR **: file nautilus-navigation-window.c: line 823 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
(bug-buddy:3419): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'
(bug-buddy:3419): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:3419): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:3419): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** ERROR **: file nautilus-navigation-window.c: line 823 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------

Comment 1 Susana 2007-08-21 20:49:49 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 460524 ***