Bug 513947 – crash in Open Folder: crying for my a broken h...

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 513947 - crash in Open Folder: crying for my a broken h...


Summary:	crash in Open Folder: crying for my a broken h...


Status:	RESOLVED DUPLICATE of bug 425157

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:	2008-02-02 20:08 UTC by paladini.marco
Modified:	2008-02-03 16:32 UTC

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

Description paladini.marco 2008-02-02 20:08:10 UTC

Version: 2.18.3

What were you doing when the application crashed?
crying for my a broken heart


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.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 105013248 vsize: 105013248 resident: 42442752 share: 19476480 rss: 42442752 rss_rlim: 4294967295
CPU usage: start_time: 1201978170 rtime: 5848 utime: 5289 stime: 559 cutime:1106 cstime: 106 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 -1208555808 (LWP 3082)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187865

Thread 1 (Thread -1208555808 (LWP 3082))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 nautilus_connect_background_to_file_metadata
#11 ??
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 fm_directory_view_begin_loading
#19 ??
#20 ??
#21 ??
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors (4525 sec old) ---------------------
(nm-applet:3120): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(nm-applet:3120): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(nm-applet:3120): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(nm-applet:3120): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-03 16:32:26 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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