Bug 457953 – crash in Home Folder: install stardict

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 457953 - crash in Home Folder: install stardict


Summary:	crash in Home Folder: install stardict


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-07-18 13:33 UTC by zjx8609
Modified:	2007-07-28 23:14 UTC

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

Description zjx8609 2007-07-18 13:33:49 UTC

What were you doing when the application crashed?
install   stardict


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 122777600 vsize: 122777600 resident: 41783296 share: 21692416 rss: 41783296 rss_rlim: 4294967295
CPU usage: start_time: 1184763108 rtime: 3812 utime: 3340 stime: 472 cutime:134 cstime: 9 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 -1208903968 (LWP 2662)]
(no debugging symbols found)
0x00197402 in __kernel_vsyscall ()

+ Trace 148834

Thread 1 (Thread -1208903968 (LWP 2662))

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



----------- .xsession-errors (10 sec old) ---------------------
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
窗口管理器警告：Received a _NET_WM_MOVERESIZE message for 0x1402c48 (root - 文); these messages lack timestamps and therefore suck.
窗口管理器警告：Received a _NET_WM_MOVERESIZE message for 0x1402c48 (root - 文); these messages lack timestamps and therefore suck.
窗口管理器警告：Received a _NET_WM_MOVERESIZE message for 0x1402c48 (root - 文); these messages lack timestamps and therefore suck.
窗口管理器警告：Received a _NET_WM_MOVERESIZE message for 0x1402c48 (root - 文); these messages lack timestamps and therefore suck.
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-07-28 23:14:32 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 433983 ***