Bug 460611 – crash in Open Folder: starting up

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 460611 - crash in Open Folder: starting up


Summary:	crash in Open Folder: starting up


Status:	RESOLVED DUPLICATE of bug 439593

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:

Duplicates:	460613 (view as bug list)
Depends on:
Blocks:

Reported:	2007-07-26 15:07 UTC by charles.hayes
Modified:	2007-07-30 00:22 UTC

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

Description charles.hayes 2007-07-26 15:07:06 UTC

Version: 2.18.1

What were you doing when the application crashed?
starting up


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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 64737280 vsize: 64737280 resident: 13799424 share: 10211328 rss: 13799424 rss_rlim: 4294967295
CPU usage: start_time: 1185488782 rtime: 23 utime: 19 stime: 4 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208133920 (LWP 3035)]
(no debugging symbols found)
0x00440402 in __kernel_vsyscall ()

+ Trace 150712

Thread 1 (Thread -1208133920 (LWP 3035))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/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_changes_with_size
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 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#14 g_signal_emit
from /lib/libgobject-2.0.so.0
#15 gtk_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_map
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_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#23 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib/libgobject-2.0.so.0
#25 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#27 g_signal_emit
from /lib/libgobject-2.0.so.0
#28 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#34 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /lib/libgobject-2.0.so.0
#36 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#38 g_signal_emit
from /lib/libgobject-2.0.so.0
#39 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#45 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#46 g_closure_invoke
from /lib/libgobject-2.0.so.0
#47 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#49 g_signal_emit
from /lib/libgobject-2.0.so.0
#50 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgtk-x11-2.0.so.0
#53 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#56 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#57 g_closure_invoke
from /lib/libgobject-2.0.so.0
#58 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#59 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#60 g_signal_emit
from /lib/libgobject-2.0.so.0
#61 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib/libgtk-x11-2.0.so.0
#63 ??
#64 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#65 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#66 g_closure_invoke
from /lib/libgobject-2.0.so.0
#67 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#68 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#69 g_signal_emit
from /lib/libgobject-2.0.so.0
#70 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#71 ??
from /usr/lib/libgtk-x11-2.0.so.0
#72 ??
#73 ??
#74 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#75 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#76 g_closure_invoke
from /lib/libgobject-2.0.so.0
#77 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#78 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#79 g_signal_emit
from /lib/libgobject-2.0.so.0
#80 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#81 nautilus_window_show_window
#82 nautilus_window_info_show_window
#83 ??
#84 ??
#85 ??
#86 ??
#87 ??
from /lib/libglib-2.0.so.0
#88 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#89 ??
from /lib/libglib-2.0.so.0
#90 g_main_loop_run
from /lib/libglib-2.0.so.0
#91 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#92 main
#0 __kernel_vsyscall



----------- .xsession-errors (7 sec old) ---------------------
(bug-buddy:3112): libglade-WARNING **: Error loading image: Couldn't recognize the image file format for file '/usr/share/bug-buddy/bug-buddy.png'
(bug-buddy:3112): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `pixbuf'
(bug-buddy:3112): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
(bug-buddy:3112): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
(bug-buddy:3112): Gtk-WARNING **: Error loading theme icon for stock: Couldn't recognize the image file format for file '/usr/share/icons/gnome/24x24/actions/gtk-find.png'
(bug-buddy:3112): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
(bug-buddy:3112): Gtk-WARNING **: Error loading theme icon for stock: Couldn't recognize the image file format for file '/usr/share/icons/gnome/22x22/apps/gtk-help.png'
(bug-buddy:3112): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-07-27 01:29:17 UTC

*** Bug 460613 has been marked as a duplicate of this bug. ***

Comment 2 Pedro Villavicencio 2007-07-27 16:27:21 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance.

Comment 3 André Klapper 2007-07-30 00:22:31 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 439593 ***