Bug 483833 – crash in Open 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 483833 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 439977

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-10-05 18:10 UTC by druberry
Modified:	2007-10-06 10:39 UTC

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

Description druberry 2007-10-05 18:10:45 UTC

Version: 2.18.3

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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 343298048 vsize: 343298048 resident: 261607424 share: 32493568 rss: 261607424 rss_rlim: 4294967295
CPU usage: start_time: 1191571343 rtime: 10969 utime: 8836 stime: 2133 cutime:2 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 -1208748320 (LWP 2469)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168074

Thread 1 (Thread -1208748320 (LWP 2469))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgnome-desktop-2.so.2
#5 ??
from /usr/lib/libgnome-desktop-2.so.2
#6 ??
from /usr/lib/libgnome-desktop-2.so.2
#7 gnome_bg_create_pixmap
from /usr/lib/libgnome-desktop-2.so.2
#8 ??
from /usr/lib/libeel-2.so.2
#9 ??
from /usr/lib/libeel-2.so.2
#10 ??
from /usr/lib/libeel-2.so.2
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libeel-2.so.2
#17 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgnome-desktop-2.so.2
#23 ??
from /usr/lib/libeel-2.so.2
#24 ??
from /usr/lib/libeel-2.so.2
#25 ??
#26 ??
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#29 ??
from /lib/libglib-2.0.so.0
#30 g_main_loop_run
from /lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall



----------- .xsession-errors (26 sec old) ---------------------
(bug-buddy:9058): Gtk-WARNING **: Icon cache '/usr/share/icons/Bluecurve/icon-theme.cache' is invalid
(bug-buddy:9058): Gtk-WARNING **: Icon cache '/usr/share/icons/Bluecurve/icon-theme.cache' is invalid
(bug-buddy:9058): Gtk-WARNING **: Icon cache '/usr/share/icons/Bluecurve/icon-theme.cache' is invalid
(bug-buddy:9058): Gtk-WARNING **: Icon cache '/usr/share/icons/Bluecurve/icon-theme.cache' is invalid
(bug-buddy:9058): Gtk-WARNING **: Icon cache '/usr/share/icons/Bluecurve/icon-theme.cache' is invalid
--------------------------------------------------

Comment 1 Susana 2007-10-06 10:39:21 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 439977 ***