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 596466 - Crash in nautilus_file_management_properties_dialog_show at nautilus-file-management-properties.c line 377
Crash in nautilus_file_management_properties_dialog_show at nautilus-file-man...
Status: RESOLVED DUPLICATE of bug 594302
Product: nautilus
Classification: Core
Component: Preferences
2.26.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 603298 606186 609503 609582 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-26 21:45 UTC by Mark D.
Modified: 2010-05-10 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Mark D. 2009-09-26 21:45:35 UTC
Version: 2.26.3

What were you doing when the application crashed?
Opening nautilus-file-management-properties


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.26.3 2009-07-22 (Gentoo)
BugBuddy Version: 2.26.0

System: Linux 2.6.29-gentoo-r1 #2 SMP Tue Apr 21 23:38:41 PDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 320389120 vsize: 320389120 resident: 13516800 share: 10313728 rss: 13516800 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254001501 rtime: 9 utime: 6 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus-file-management-properties'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f1737996750 (LWP 7834)]
0x00007f1731d6a525 in __libc_waitpid (pid=7835, stat_loc=0x7fff3f9d9ef0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f1737996750 (LWP 7834))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 369
  • #4 <signal handler called>
  • #5 nautilus_file_management_properties_dialog_show
    at nautilus-file-management-properties.c line 377
  • #6 main
    at nautilus-file-management-properties-main.c line 58
0x00007f1731d6a525	32	in ../sysdeps/unix/sysv/linux/waitpid.c
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


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

** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** GLib-GObject **: g_object_set_data_full: assertion `G_IS_OBJECT (object)' failed 
** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed 
** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 
** GLib-GObject **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 
** GLib-GObject **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed 


----------- .xsession-errors (2432 sec old) ---------------------
(nautilus-file-management-properties:6508): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus-file-management-properties:6508): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(nautilus-file-management-properties:6508): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus-file-management-properties:6508): GLib-GObject-CRITICAL **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(nautilus-file-management-properties:6508): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
32	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220004a (Mozilla Fi)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (nautilus:6054): WARNING **: Hit unhandled case g-io-error-quark:13 in fm_report_error_renaming_file
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-11-29 14:29:45 UTC
*** Bug 603298 has been marked as a duplicate of this bug. ***
Comment 2 Fabio Durán Verdugo 2009-11-29 14:31:39 UTC
maybe this related with bug 594302
Comment 3 Akhil Laddha 2010-01-06 10:12:24 UTC
*** Bug 606186 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2010-02-10 07:51:38 UTC
*** Bug 609503 has been marked as a duplicate of this bug. ***
Comment 5 Akhil Laddha 2010-02-11 04:10:39 UTC
*** Bug 609582 has been marked as a duplicate of this bug. ***
Comment 6 Cosimo Cecchi 2010-05-10 11:22:01 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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