Bug 496561 – crash in Open Folder: OPen nautils terminal

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 496561 - crash in Open Folder: OPen nautils terminal


Summary:	crash in Open Folder: OPen nautils terminal


Status:	RESOLVED NOTABUG

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

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

URL:
Whiteboard:

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

Reported:	2007-11-13 20:57 UTC by knutjorgen
Modified:	2008-04-23 14:45 UTC

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

Description knutjorgen 2007-11-13 20:57:13 UTC

Version: 2.20.0

What were you doing when the application crashed?
OPen nautils terminal


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.1-49.fc8 #1 SMP PREEMPT Sun Nov 11 13:56:59 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 108085248 vsize: 108085248 resident: 30228480 share: 1351680 rss: 30228480 rss_rlim: 4294967295
CPU usage: start_time: 1194987319 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209039088 (LWP 16553)]
0x00110402 in __kernel_vsyscall ()

+ Trace 177517

Thread 1 (Thread -1209039088 (LWP 16553))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 ??
from /lib/libglib-2.0.so.0
#10 ??
from /lib/libglib-2.0.so.0
#11 g_spawn_async_with_pipes
from /lib/libglib-2.0.so.0
#12 g_spawn_async
from /lib/libglib-2.0.so.0
#13 open_terminal_callback
at nautilus-open-terminal.c line 303
#14 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 nautilus_menu_item_activate
at nautilus-menu-item.c line 85
#20 extension_action_callback
at nautilus-ui-utilities.c line 113
#21 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#25 g_signal_emit
from /lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 ??
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit
from /lib/libgobject-2.0.so.0
#33 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_closure_invoke
from /lib/libgobject-2.0.so.0
#40 ??
from /lib/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#42 g_signal_emit
from /lib/libgobject-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib/libgdk-x11-2.0.so.0
#47 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#48 ??
from /lib/libglib-2.0.so.0
#49 g_main_loop_run
from /lib/libglib-2.0.so.0
#50 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#51 main
at nautilus-main.c line 556
#52 __libc_start_main
from /lib/libc.so.6
#53 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ad/6b23ad944aa05d2c7a04e93dfa9874176df256.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/9a/317b629db430c77f885387232e057142437af2.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/17/b7c6a0e2448b0af3c236c6d152d4efaa5ff2f9.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/91/c3577f45017cd96aefb973ac580e45f33e5770.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/79/8a454329a592b7bf8f8dfa8256530878724e83.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/79/e2ebcbc5720ad8ce323b04817cdcbc3797e386.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/09/572b8307de371f3debd05cdfd4720195bba6cd.debug
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 1 André Klapper 2007-11-13 22:33:54 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: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, eel2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

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

Comment 2 knutjorgen 2007-11-14 04:09:47 UTC

Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.1-49.fc8 #1 SMP PREEMPT Sun Nov 11 13:56:59 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Tango

Memory status: size: 172769280 vsize: 172769280 resident: 29614080 share: 1355776 rss: 29614080 rss_rlim: 4294967295
CPU usage: start_time: 1195013092 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209067760 (LWP 14369)]
0x00110402 in __kernel_vsyscall ()

+ Trace 177580

Thread 1 (Thread -1209067760 (LWP 14369))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 369
#3 IA__g_spawn_command_line_sync
at gspawn.c line 677
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 do_exec
at gspawn.c line 1511
#10 fork_exec_with_pipes
at gspawn.c line 1256
#11 IA__g_spawn_async_with_pipes
at gspawn.c line 608
#12 IA__g_spawn_async
at gspawn.c line 114
#13 open_terminal_callback
at nautilus-open-terminal.c line 303
#14 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2440
#17 IA__g_signal_emit_valist
at gsignal.c line 2199
#18 IA__g_signal_emit
at gsignal.c line 2243
#19 nautilus_menu_item_activate
at nautilus-menu-item.c line 85
#20 extension_action_callback
at nautilus-ui-utilities.c line 113
#21 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#22 IA__g_closure_invoke
at gclosure.c line 490
#23 signal_emit_unlocked_R
at gsignal.c line 2440
#24 IA__g_signal_emit_valist
at gsignal.c line 2199
#25 IA__g_signal_emit
at gsignal.c line 2243
#26 _gtk_action_emit_activate
at gtkaction.c line 872
#27 IA__gtk_action_activate
at gtkaction.c line 899
#28 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#29 IA__g_closure_invoke
at gclosure.c line 490
#30 signal_emit_unlocked_R
at gsignal.c line 2440
#31 IA__g_signal_emit_valist
at gsignal.c line 2199
#32 IA__g_signal_emit
at gsignal.c line 2243
#33 IA__gtk_widget_activate
at gtkwidget.c line 4706
#34 IA__gtk_menu_shell_activate_item
at gtkmenushell.c line 1145
#35 gtk_menu_shell_button_release
at gtkmenushell.c line 669
#36 gtk_menu_button_release
at gtkmenu.c line 2725
#37 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#38 g_type_class_meta_marshal
at gclosure.c line 567
#39 IA__g_closure_invoke
at gclosure.c line 490
#40 signal_emit_unlocked_R
at gsignal.c line 2478
#41 IA__g_signal_emit_valist
at gsignal.c line 2209
#42 IA__g_signal_emit
at gsignal.c line 2243
#43 gtk_widget_event_internal
at gtkwidget.c line 4675
#44 IA__gtk_propagate_event
at gtkmain.c line 2319
#45 IA__gtk_main_do_event
at gtkmain.c line 1539
#46 gdk_event_dispatch
at gdkevents-x11.c line 2351
#47 IA__g_main_context_dispatch
at gmain.c line 2061
#48 g_main_context_iterate
at gmain.c line 2694
#49 IA__g_main_loop_run
at gmain.c line 2898
#50 IA__gtk_main
at gtkmain.c line 1146
#51 main
at nautilus-main.c line 556
#52 __libc_start_main
at libc-start.c line 220
#53 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/f9/7d9d1d043b4894035cb0d83624a61868ceb650.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/19/e316bd7cba19da52c1cf8b8cb106890e8aaa96.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/9a/5ef56a069900c5b72455ac967d946ed726ea74.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ad/6b23ad944aa05d2c7a04e93dfa9874176df256.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/9a/317b629db430c77f885387232e057142437af2.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/17/b7c6a0e2448b0af3c236c6d152d4efaa5ff2f9.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/79/8a454329a592b7bf8f8dfa8256530878724e83.debug
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 3 knutjorgen 2007-11-14 12:14:59 UTC

Added nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, eel2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo and glibc-debuginfo. I later reproduce the error which I have listed as comment two.

Comment 4 knutjorgen 2007-11-15 06:22:45 UTC

It was a configuration clash. The terminal was set to custum. By settting it to
gnome-terminal it now work for me. Thanks.

Comment 5 Cosimo Cecchi 2008-04-23 14:45:55 UTC

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