Bug 449305 – crash in Open Folder: alt-tabbing between fire...

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 449305 - crash in Open Folder: alt-tabbing between fire...


Summary:	crash in Open Folder: alt-tabbing between fire...


Status:	RESOLVED DUPLICATE of bug 440327

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-06-19 23:00 UTC by gnomebug
Modified:	2007-07-18 15:49 UTC

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

Description gnomebug 2007-06-19 23:00:39 UTC

Version: 2.18.1

What were you doing when the application crashed?
alt-tabbing between firefox and a gnome-terminal


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: Bluecurve-Grape
Icon Theme: gnome

Memory status: size: 82153472 vsize: 82153472 resident: 24989696 share: 18325504 rss: 24989696 rss_rlim: 4294967295
CPU usage: start_time: 1182293937 rtime: 129 utime: 109 stime: 20 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 -1208588576 (LWP 2875)]
(no debugging symbols found)
0x005fe402 in __kernel_vsyscall ()

+ Trace 142284

Thread 1 (Thread -1208588576 (LWP 2875))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libeel-2.so.2
#9 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#88 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#89 g_cclosure_marshal_VOID__ENUM
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 (14 sec old) ---------------------
localuser:shawna being added to access control list
SESSION_MANAGER=local/shawna:/tmp/.ICE-unix/2752
Window manager warning: Failed to load theme "Smokey": Failed to find a valid file for theme Smokey
(nautilus:2875): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------

Comment 1 André Klapper 2007-06-23 21:58:32 UTC

Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 2 gnomebug 2007-06-25 16:13:14 UTC

It seems that the system was installed with memory clocked too high (133mhz instead of 100mhz)
causing the crashes.  Thank you for your diligent focus in fixing gnome bugs!  I believe this is the
reason that we have such solid OSS!


-Eric

Comment 3 André Klapper 2007-07-18 15:49:37 UTC

Anyway, what we need is a better stacktrace...

*** This bug has been marked as a duplicate of 440327 ***