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 498583 - crash in Home Folder: noting
crash in Home Folder: noting
Status: RESOLVED DUPLICATE of bug 436071
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-20 19:42 UTC by arnopps
Modified: 2007-11-24 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description arnopps 2007-11-20 19:42:10 UTC
What were you doing when the application crashed?
noting


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 119042048 vsize: 119042048 resident: 42725376 share: 26112000 rss: 42725376 rss_rlim: 4294967295
CPU usage: start_time: 1195587127 rtime: 9956 utime: 9565 stime: 391 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208387872 (LWP 3801)]
[New Thread -1210754160 (LWP 4137)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208387872 (LWP 3801))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 nautilus_file_compare_for_sort
  • #6 fm_icon_view_compare_files
  • #7 ??
  • #8 ??
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 nautilus_directory_emit_done_loading
  • #23 ??
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
    from /lib/libpthread.so.0
  • #33 ??
  • #34 ??
    from /lib/libpthread.so.0
  • #35 ??
  • #36 ??
  • #37 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 g_slice_alloc
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall


----------- .xsession-errors (310 sec old) ---------------------
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-11-24 18:40:04 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 436071 ***