Bug 503988 – crash in Open Folder: running the parted comma...

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 503988 - crash in Open Folder: running the parted comma...


Summary:	crash in Open Folder: running the parted comma...


Status:	RESOLVED DUPLICATE of bug 436071

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-17 04:40 UTC by amitagl27
Modified:	2007-12-17 12:21 UTC

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

Description amitagl27 2007-12-17 04:40:05 UTC

Version: 2.18.1

What were you doing when the application crashed?
running the parted command to partiiton my hard disk


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 84914176 vsize: 84914176 resident: 30380032 share: 17874944 rss: 30380032 rss_rlim: 4294967295
CPU usage: start_time: 1197884316 rtime: 555 utime: 512 stime: 43 cutime:0 cstime: 1 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 -1208977696 (LWP 3092)]
(no debugging symbols found)
0x00c6d402 in __kernel_vsyscall ()

+ Trace 182089

Thread 1 (Thread -1208977696 (LWP 3092))

#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 ??
from /lib/libglib-2.0.so.0
#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 ---------------------
This can cause subtle evils like #48423
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3092): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3092): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Comment 1 André Klapper 2007-12-17 12:21:57 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. You may want to check for a software upgrade.


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