Bug 466982 – crash in Open Folder: jag startade programet s...

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 466982 - crash in Open Folder: jag startade programet s...


Summary:	crash in Open Folder: jag startade programet s...


Status:	RESOLVED DUPLICATE of bug 445429

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-08-15 15:12 UTC by Pajari87
Modified:	2007-08-22 18:41 UTC

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

Description Pajari87 2007-08-15 15:12:45 UTC

Version: 2.18.3

What were you doing when the application crashed?
jag startade programet sedan stängde det ner sig 


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

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 85598208 vsize: 85598208 resident: 33783808 share: 20676608 rss: 33783808 rss_rlim: 4294967295
CPU usage: start_time: 1187189969 rtime: 282 utime: 263 stime: 19 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 -1208211744 (LWP 2764)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 155420

Thread 1 (Thread -1208211744 (LWP 2764))

#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/libc.so.6
#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:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2764): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2764): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Comment 1 Susana 2007-08-22 18:41:42 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 445429 ***