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 620854 - crash in File Manager: I tried to open a proper...
crash in File Manager: I tried to open a proper...
Status: RESOLVED DUPLICATE of bug 534093
Product: nautilus
Classification: Core
Component: general
2.30.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-07 15:42 UTC by timmazid
Modified: 2010-06-07 16:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description timmazid 2010-06-07 15:42:30 UTC
Version: 2.30.1

What were you doing when the application crashed?
I tried to open a properties window for a file.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-4-amd64 #1 SMP Mon Apr 5 21:14:10 UTC 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 694296576 vsize: 694296576 resident: 43462656 share: 24940544 rss: 43462656 rss_rlim: 18446744073709551615
CPU usage: start_time: 1275923950 rtime: 15250 utime: 13104 stime: 2146 cutime:144 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f3e0748f710 (LWP 13970)]
0x00007f3e214c7b4d in __libc_waitpid (pid=13971, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f3e22744800 (LWP 13220))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_type_check_instance
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_handlers_disconnect_matched
    from /usr/lib/libgobject-2.0.so.0
  • #7 remove_pending
    at fm-properties-window.c line 5322
  • #8 is_directory_ready_callback
    at fm-properties-window.c line 5349
  • #9 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1886
  • #10 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
    at nautilus-main.c line 544

	Inferior 1 [process 13220] will be detached.

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


---- Critical and fatal warnings logged during execution ----

** Eel **: eel_timed_wait_stop: assertion `wait != NULL' failed 


----------- .xsession-errors ---------------------
(polkit-gnome-authentication-agent-1:13224): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
Failed to play sound: File or data not found
MCS->Xfconf settings migration complete
Unable to open desktop file /usr/share/applications/kde/amarok.desktop for panel launcher: No such file or directory
Initializing nautilus-gdu extension
(gnome-panel:13206): Gdk-WARNING **: /tmp/buildd/gtk+2.0-2.20.1/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800044 (Iceweasel)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(nautilus:13220): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
41	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-06-07 16:12:36 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 534093 ***