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 597986 - crash in File Browser:
crash in File Browser:
Status: RESOLVED DUPLICATE of bug 584745
Product: nautilus
Classification: Core
Component: general
2.26.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-10 08:42 UTC by Víctor Daniel
Modified: 2009-10-10 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Víctor Daniel 2009-10-10 08:42:27 UTC
Version: 2.26.4

What were you doing when the application crashed?



Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.30.8-64.fc11.i586 #1 SMP Fri Sep 25 04:30:19 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: eGTK_0.9.9.14
Icon Theme: erectus-blue
GTK+ Modules: canberra-gtk-module, globalmenu-gnome, pk-gtk-module, gnomebreakpad

Memory status: size: 184188928 vsize: 184188928 resident: 33640448 share: 16908288 rss: 33640448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255151543 rtime: 3138 utime: 2661 stime: 477 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xaf6fcb70 (LWP 2329)]
[New Thread 0xb0afeb70 (LWP 2125)]
0x0093d422 in __kernel_vsyscall ()

Thread 1 (Thread 0xb8080760 (LWP 1872))

  • #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 <signal handler called>
  • #7 ??
  • #8 exit
    from /lib/libc.so.6
  • #9 __libc_start_main
    from /lib/libc.so.6
  • #10 _start
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 ----

** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed 
** GConf **: ltable_remove: assertion `node != NULL' failed 
** GConf **: ltable_remove: assertion `node != NULL' failed 
** GConf **: ltable_remove: assertion `node != NULL' failed 


----------- .xsession-errors (7 sec old) ---------------------
warning: .dynamic section for "/lib/libc.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgvfscommon.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libasyncns.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Cosimo Cecchi 2009-10-10 10:44:40 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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