Bug 463890 – crash in Open Folder: nothing, logged in!

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 463890 - crash in Open Folder: nothing, logged in!


Summary:	crash in Open Folder: nothing, logged in!


Status:	RESOLVED DUPLICATE of bug 452775

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:	469073 (view as bug list)
Depends on:
Blocks:

Reported:	2007-08-06 06:55 UTC by shailesh.thakur
Modified:	2007-08-25 15:56 UTC

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

Description shailesh.thakur 2007-08-06 06:55:48 UTC

Version: 2.18.1

What were you doing when the application crashed?
nothing, logged in!


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: Clearlooks
Icon Theme: Fedora

Memory status: size: 84283392 vsize: 84283392 resident: 24219648 share: 19369984 rss: 24219648 rss_rlim: 4294967295
CPU usage: start_time: 1186383278 rtime: 41 utime: 37 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209133344 (LWP 25801)]
(no debugging symbols found)
0x00daa402 in __kernel_vsyscall ()

+ Trace 153117

Thread 1 (Thread -1209133344 (LWP 25801))

#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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnome-desktop-2.so.2
#5 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnome-desktop-2.so.2
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnome-desktop-2.so.2
#7 gnome_bg_changes_with_size
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#43 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#52 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#53 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#54 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
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 ---------------------
Initializing nautilus-open-terminal extension
Initializing nautilus-search-tool extension
Initializing gnome-mount extension
(nautilus:25738): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
Initializing nautilus-open-terminal extension
Initializing nautilus-search-tool extension
Initializing gnome-mount extension
(nautilus:25760): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
Initializing nautilus-open-terminal extension
Initializing nautilus-search-tool extension
Initializing gnome-mount extension
(nautilus:25801): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------

Comment 1 palfrey 2007-08-22 13:35:23 UTC

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

Comment 2 Susana 2007-08-25 15:56:32 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 452775 ***