Bug 486164 – crash in Home 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 486164 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 417962

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-10-12 21:48 UTC by wtassinari
Modified:	2007-10-13 22:54 UTC

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

Description wtassinari 2007-10-12 21:48:48 UTC

What were you doing when the application crashed?



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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 100012032 vsize: 100012032 resident: 43450368 share: 26996736 rss: 43450368 rss_rlim: 4294967295
CPU usage: start_time: 1192223144 rtime: 4334 utime: 3896 stime: 438 cutime:188 cstime: 37 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 -1208785184 (LWP 2586)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 169838

Thread 1 (Thread -1208785184 (LWP 2586))

#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 ??
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 (8 sec old) ---------------------
Done.
18:42:21 : Yum Config Setup
18:42:22 : Yum Version : 3.2.5
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Yum Extend)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
18:42:22 : GUI Setup Completed
18:42:23 : Enabled repositories : updates,fedora,liquuid,livna,skype
18:42:25 : Configuração do Yum : Set de Transação
18:42:26 : Configuração do Yum : RPM Bd.
18:42:26 : Setup Yum : Repositories.
18:42:26 : Setup Yum : Package Sacks
18:42:26 : Setup Yum : Updates
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 Christoph Wolk 2007-10-13 13:26:12 UTC

Thank you for reporting this bug. It looks like this is the same issue as bug 433983.

Comment 2 Christian Kirbach 2007-10-13 22:54:19 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 417962 ***