Bug 504175 – 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 504175 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 459221

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-18 03:50 UTC by tomb
Modified:	2007-12-18 22:35 UTC

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

Description tomb 2007-12-18 03:50:11 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-10-07 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-perf #5 SMP PREEMPT Wed Dec 5 20:50:28 GMT 2007 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: 232398848 vsize: 232398848 resident: 40570880 share: 23105536 rss: 40570880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197949798 rtime: 127 utime: 107 stime: 20 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47806903468960 (LWP 6272)]
0x00002b7ae7139b0f in waitpid () from /lib/libpthread.so.0

+ Trace 182190

Thread 1 (Thread 47806903468960 (LWP 6272))

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



----------- .xsession-errors ---------------------
aborting...
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe358d000
(bug-buddy:6255): GLib-GObject-WARNING **: invalid uninstantiatable type `visited-link-color' in cast to `GObject'
(bug-buddy:6255): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:6255): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:6255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
Failed to read a valid object file image from memory.
--------------------------------------------------

Comment 1 Susana 2007-12-18 22:35:32 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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