Bug 454463 – crash in Open Folder: Copy Paste

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 454463 - crash in Open Folder: Copy Paste


Summary:	crash in Open Folder: Copy Paste


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-07-07 04:50 UTC by mohit.keswani
Modified:	2007-07-07 21:37 UTC

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

Description mohit.keswani 2007-07-07 04:50:24 UTC

Version: 2.18.1

What were you doing when the application crashed?
Copy Paste


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 102260736 vsize: 102260736 resident: 48295936 share: 25247744 rss: 48295936 rss_rlim: 4294967295
CPU usage: start_time: 1183780920 rtime: 2558 utime: 2290 stime: 268 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 -1208166688 (LWP 29093)]
(no debugging symbols found)
0x00e1d402 in __kernel_vsyscall ()

+ Trace 146259

Thread 1 (Thread -1208166688 (LWP 29093))

#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 ---------------------
--- Hash table keys for warning below:
--> file:///home/mk
(nautilus:29557): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** (nautilus:29093): WARNING **: No description found for mime type "x-directory/smb-share" (file is "DISK%201"), please tell the gnome-vfs mailing list.
(eog:29865): Eog-WARNING **: Exif entry has unsupported size
(eog:29865): Eog-WARNING **: Exif entry has unsupported size
(nautilus:29093): Gtk-CRITICAL **: _gtk_rbtree_reorder: assertion `tree->root->count == length' failed
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 palfrey 2007-07-07 21:37:41 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 ***