Bug 501473 – crash in Open Folder: Starting GNOME after the...

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 501473 - crash in Open Folder: Starting GNOME after the...


Summary:	crash in Open Folder: Starting GNOME after the...


Status:	RESOLVED DUPLICATE of bug 420467

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:

Depends on:
Blocks:

Reported:	2007-12-04 10:21 UTC by Mart Raudsepp
Modified:	2007-12-10 13:59 UTC

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

Description Mart Raudsepp 2007-12-04 10:21:09 UTC

Version: 2.20.0

What were you doing when the application crashed?
Starting GNOME after the system had frozen (from unrelated reasons like plugging in an USB key) the last time


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.2 2007-12-03 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-gentoo-r3 #1 SMP Mon Dec 3 16:40:16 EET 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 382152704 vsize: 382152704 resident: 17596416 share: 12120064 rss: 17596416 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196763521 rtime: 26 utime: 20 stime: 6 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 0x2adc0d768b10 (LWP 5344)]
0x00002adc060b6f5f in __libc_waitpid (pid=5414, stat_loc=0x7fffa83d1670, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 180691

Thread 1 (Thread 0x2adc0d768b10 (LWP 5344))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at gspawn.c line 369
#2 IA__g_spawn_command_line_sync
at gspawn.c line 677
#3 bugbuddy_segv_handle
at gnome-breakpad.cc line 213
#4 <signal handler called>
#5 gnome_vfs_uri_unref
at gnome-vfs-uri.c line 1025
#6 _gnome_vfs_job_destroy_notify_result
at gnome-vfs-job.c line 335
#7 dispatch_job_callback
at gnome-vfs-job.c line 591
#8 IA__g_main_context_dispatch
at gmain.c line 2061
#9 g_main_context_iterate
at gmain.c line 2694
#10 IA__g_main_loop_run
at gmain.c line 2898
#11 IA__gtk_main
at gtkmain.c line 1146
#12 main
at nautilus-main.c line 556
#13 __libc_start_main
at libc-start.c line 227
#14 _start

0x00002adc060b6f5f	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:5343): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffa83d8000
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-12-10 13:59:33 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 420467 ***