Bug 494768 – crash in Open Folder: Opening File Browser

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 494768 - crash in Open Folder: Opening File Browser


Summary:	crash in Open Folder: Opening File Browser


Status:	RESOLVED DUPLICATE of bug 473686

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-11-07 21:26 UTC by brian.rector
Modified:	2007-11-08 18:04 UTC

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

Description brian.rector 2007-11-07 21:26:13 UTC

Version: 2.18.3

What were you doing when the application crashed?
Opening File Browser


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 97751040 vsize: 97751040 resident: 29896704 share: 22265856 rss: 29896704 rss_rlim: 4294967295
CPU usage: start_time: 1194456081 rtime: 2209 utime: 1990 stime: 219 cutime:3 cstime: 3 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 -1208244512 (LWP 13088)]
[New Thread -1220834416 (LWP 26462)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176165

Thread 1 (Thread -1208244512 (LWP 13088))

#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 (161421 sec old) ---------------------
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
fixme:xrender:X11DRV_AlphaBlend not a dibsection
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-11-08 18:04:37 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 473686 ***