Bug 479168 – crash in Home Folder: just click 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 479168 - crash in Home Folder: just click folder


Summary:	crash in Home Folder: just click folder


Status:	RESOLVED DUPLICATE of bug 433983

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:	2007-09-22 04:03 UTC by vv
Modified:	2007-10-21 17:03 UTC

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

Description vv 2007-09-22 04:03:21 UTC

What were you doing when the application crashed?
just click 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: 132571136 vsize: 132571136 resident: 40353792 share: 23347200 rss: 40353792 rss_rlim: 4294967295
CPU usage: start_time: 1190390763 rtime: 10261 utime: 9387 stime: 874 cutime:457 cstime: 296 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 -1209002272 (LWP 2654)]
[New Thread -1212908656 (LWP 14797)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164572

Thread 1 (Thread -1209002272 (LWP 2654))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
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 gtk_tree_view_set_cursor_on_cell
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_tree_view_set_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Compiling: main.cpp
Process terminated with status 1 (0 minutes, 1 seconds)
3 errors, 0 warnings
/home/victor/Development/TestCDTAPI/main.cpp:73: 警告：未使用的变量 ‘DeviceNum’
/home/victor/Development/TestCDTAPI/main.cpp:72: 警告：未使用的变量 ‘Found’
/home/victor/Development/TestCDTAPI/main.cpp:77: 错误：‘nl’ 在此作用域中尚未声明
/home/victor/Development/TestCDTAPI/main.cpp: In function ‘void AutoScanDevice()’:
-------------- Build: Debug in TestCDTAPI ---------------
Compiling: main.cpp
Linking console executable: bin/Debug/TestCDTAPI
/home/victor/Development/TestCDTAPI/main.cpp:73: 警告：未使用的变量 ‘DeviceNum’
/home/victor/Development/TestCDTAPI/main.cpp:72: 警告：未使用的变量 ‘Found’
/home/vi
** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 André Klapper 2007-10-21 17:03:27 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 ***