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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 441944

Product:	gnome-desktop
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Desktop Maintainers
QA Contact:	Desktop Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-09-18 20:04 UTC by amanda.austin
Modified:	2008-11-19 18:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description amanda.austin 2008-09-18 20:04:05 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.26.3-14.fc8 #1 SMP Wed Sep 3 03:17:52 EDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 603193344 vsize: 603193344 resident: 37101568 share: 18264064 rss: 37101568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1221768159 rtime: 48 utime: 36 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 139981992281984 (LWP 6034)]
0x0000003823a0e0bf in waitpid () from /lib64/libpthread.so.0

+ Trace 206956

Thread 1 (Thread 139981992281984 (LWP 6034))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_spawn_sync
from /lib64/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /lib64/libglib-2.0.so.0
#3 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_utf8_find_prev_char
from /lib64/libglib-2.0.so.0
#6 g_markup_parse_context_parse
from /lib64/libglib-2.0.so.0
#7 get_as_slideshow
at gnome-bg.c line 1744
#8 get_pixbuf
at gnome-bg.c line 1223
#9 gnome_bg_changes_with_size
at gnome-bg.c line 382
#10 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libeel-2.so.2
#11 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libeel-2.so.2
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit
from /lib64/libgobject-2.0.so.0
#16 gtk_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#17 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_container_forall
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#23 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit
from /lib64/libgobject-2.0.so.0
#27 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#29 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#30 gtk_container_forall
from /usr/lib64/libgtk-x11-2.0.so.0
#31 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#32 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#33 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit
from /lib64/libgobject-2.0.so.0
#36 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#37 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#38 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#39 gtk_container_forall
from /usr/lib64/libgtk-x11-2.0.so.0
#40 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#41 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#42 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#44 g_signal_emit
from /lib64/libgobject-2.0.so.0
#45 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#46 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#47 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#48 gtk_container_forall
from /usr/lib64/libgtk-x11-2.0.so.0
#49 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#50 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#51 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#53 g_signal_emit
from /lib64/libgobject-2.0.so.0
#54 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#55 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#56 map
at nautilus-desktop-window.c line 153
#57 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#58 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#59 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#60 g_signal_emit
from /lib64/libgobject-2.0.so.0
#61 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#62 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#63 nautilus_window_show
at nautilus-window.c line 1313
#64 nautilus_spatial_window_show
at nautilus-spatial-window.c line 324
#65 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#66 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#67 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#68 g_signal_emit
from /lib64/libgobject-2.0.so.0
#69 gtk_widget_show
from /usr/lib64/libgtk-x11-2.0.so.0
#70 nautilus_window_show_window
at nautilus-window.c line 685
#71 finish_loading_if_all_metadata_loaded
at fm-directory-view.c line 9017
#72 directory_ready_callback
at nautilus-desktop-directory.c line 135
#73 ready_callback_call
at nautilus-directory-async.c line 1270
#74 call_ready_callbacks_at_idle
at nautilus-directory-async.c line 1877
#75 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#76 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#77 g_main_loop_run
from /lib64/libglib-2.0.so.0
#78 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#79 main
at nautilus-main.c line 565
#80 __libc_start_main
from /lib64/libc.so.6
#81 _start
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (17 sec old) ---------------------
[Warn 20:02:43.916] Could not read plugins directory /usr/share/gdm/gnome-do/plugins: 
                    Directory '/usr/share/gdm/gnome-do/plugins' not found. 
[Info 20:02:45.418] Universe contains 364 objects. 
Initializing nautilus-share extension
36
[Info 20:02:46.038] Binding key '<Super>space' for 
                    '/apps/gnome-do/preferences/key_binding'. You may change this 
                    keybinding with Configuration Editor (gconf-editor). 
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200004 (Do)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Initializing gnome-mount extension
Initializing nautilus-flac-converter extension
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
Initializing nautilus-image-converter extension
--------------------------------------------------

Comment 1 A. Walton 2008-09-19 00:03:00 UTC

Looks like a crash in GnomeBG, reassigning to Gnome-Desktop.

Comment 2 Cosimo Cecchi 2008-09-24 12:03:14 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 and reopen this bug or report a new one. Thanks in advance!

Comment 3 Vincent Untz 2008-09-24 12:07:38 UTC

gnome-desktop part of the stack trace looks fine, reopening.

Comment 4 palfrey 2008-11-19 18:00:38 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 441944 ***