Bug 516145 – crash in Home Folder: Kommando root# df ausgef...

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 516145 - crash in Home Folder: Kommando root# df ausgef...


Summary:	crash in Home Folder: Kommando root# df ausgef...


Status:	RESOLVED DUPLICATE of bug 436071

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-12 23:31 UTC by ka5179-727
Modified:	2008-02-13 00:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description ka5179-727 2008-02-12 23:31:03 UTC

What were you doing when the application crashed?
Kommando root# df ausgeführt



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 84115456 vsize: 84115456 resident: 23461888 share: 13074432 rss: 23461888 rss_rlim: 4294967295
CPU usage: start_time: 1202858993 rtime: 185 utime: 169 stime: 16 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 -1209149728 (LWP 3008)]
(no debugging symbols found)
0x0014f402 in __kernel_vsyscall ()

+ Trace 189014

Thread 1 (Thread -1209149728 (LWP 3008))

#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 ??
#14 ??
#15 ??
#16 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 nautilus_directory_emit_done_loading
#22 ??
#23 ??
#24 ??
from /usr/lib/libgnomevfs-2.so.0
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
from /lib/libpthread.so.0
#32 ??
#33 ??
from /lib/libpthread.so.0
#34 ??
#35 ??
#36 ??
from /usr/lib/libgnomevfs-2.so.0
#37 ??
#38 ??
#39 ??
#40 g_slice_alloc
from /lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** (nautilus:3008): WARNING **: Possibly invalid new URI 'file:///root# df'
This can cause subtle evils like #48423
--- Hash table keys for warning below:
--> file:///root
(nautilus:3108): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:3008): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3008): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3008): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3008): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-02-13 00:23:42 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 ***