Bug 631744 – crash in File Manager: I was using a two-panels...

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 631744 - crash in File Manager: I was using a two-panels...


Summary:	crash in File Manager: I was using a two-panels...


Status:	RESOLVED DUPLICATE of bug 602500

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-10-09 11:24 UTC by Rémi Letot
Modified:	2010-10-09 17:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description Rémi Letot 2010-10-09 11:24:11 UTC

Version: 2.30.1

What were you doing when the application crashed?
I was using a two-panels view (launched with F3), one with a local folder and the other via sftp on a remote server. The focus was on the remote panel, and I double-clicked on a folder in the local pane. That's where nautilus crashed, and I can see on the greyed out widow that the focus was not yet on the local pane.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.36-rc6-686 #1 SMP Mon Oct 4 10:25:13 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 271519744 vsize: 271519744 resident: 85999616 share: 19238912 rss: 85999616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1286435998 rtime: 13675 utime: 12495 stime: 1180 cutime:1213 cstime: 183 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb00f9b70 (LWP 31904)]
0xb7794424 in __kernel_vsyscall ()

+ Trace 224068

Thread 1 (Thread 0xb669d760 (LWP 2732))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 nautilus_file_peek_display_name
at nautilus-file.c line 3726
#7 nautilus_file_get_display_name
at nautilus-file.c line 3749
#8 selection_changed_callback
at nautilus-information-panel.c line 1124
#9 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gmarshal.c line 77
#10 IA__g_closure_invoke
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gclosure.c line 767
#11 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 3248
#12 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 2981
#13 IA__g_signal_emit_by_name
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 3075
#14 nautilus_window_report_selection_changed
at nautilus-window-manage-views.c line 116
#15 nautilus_window_info_report_selection_changed
at nautilus-window-info.c line 151
#16 fm_directory_view_send_selection_change
at fm-directory-view.c line 2313
#17 display_selection_info_idle_callback
at fm-directory-view.c line 2916
#18 g_idle_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 4065
#19 g_main_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 1960
#20 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2513
#21 g_main_context_iterate
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2591
#22 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2799
#23 IA__gtk_main
at /build/buildd-gtk+2.0_2.20.1-1+b1-i386-jmql5R/gtk+2.0-2.20.1/gtk/gtkmain.c line 1219
#24 main
at nautilus-main.c line 544


	Inferior 1 [process 2732] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (1564 sec old) ---------------------
(<unknown>:31024): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:31024): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:31024): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:31024): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:31024): Gdk-WARNING **: XID collision, trouble ahead
  (parent won, so we're not deferring)
  (parent won, so we're deferring)
  (processing deferred in-call)
  (child won, so we're deferring)
  (child won, so we're not deferring)
  (processing deferred in-call)
--------------------------------------------------

Comment 1 Cosimo Cecchi 2010-10-09 17:28:55 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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