Bug 475613 – crash in Open Folder: Opened a 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 475613 - crash in Open Folder: Opened a folder


Summary:	crash in Open Folder: Opened a folder


Status:	RESOLVED DUPLICATE of bug 433983

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-09-10 21:17 UTC by vkobrin
Modified:	2007-09-11 09:57 UTC

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

Description vkobrin 2007-09-10 21:17:15 UTC

Version: 2.18.3

What were you doing when the application crashed?
Opened a 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 91308032 vsize: 91308032 resident: 38076416 share: 24174592 rss: 38076416 rss_rlim: 4294967295
CPU usage: start_time: 1189457396 rtime: 1551 utime: 1351 stime: 200 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 -1208854816 (LWP 2570)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 161892

Thread 1 (Thread -1208854816 (LWP 2570))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
#11 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_tree_row_reference_free
from /usr/lib/libgtk-x11-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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_tree_view_set_cursor_on_cell
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_tree_view_set_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#26 ??
from /lib/libglib-2.0.so.0
#27 g_main_loop_run
from /lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 __kernel_vsyscall



----------- .xsession-errors (12 sec old) ---------------------
This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt
Initialising tracker...
throttle level is 0
seahorse nautilus module initialized
--- Hash table keys for warning below:
--> file:///root
(nautilus:2674): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-09-11 09:57:08 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 433983 ***