Bug 521286 – crash in File Browser:

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 521286 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 439977

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-03-09 00:49 UTC by avilesluis
Modified:	2008-03-10 11:09 UTC

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

Description avilesluis 2008-03-09 00:49:14 UTC

Version: 2.18.3

What were you doing when the application crashed?



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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 99143680 vsize: 99143680 resident: 22777856 share: 14548992 rss: 22777856 rss_rlim: 4294967295
CPU usage: start_time: 1205011708 rtime: 2569 utime: 2335 stime: 234 cutime:1 cstime: 11 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 -1209104672 (LWP 3123)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191810

Thread 1 (Thread -1209104672 (LWP 3123))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgnome-desktop-2.so.2
#5 ??
from /usr/lib/libgnome-desktop-2.so.2
#6 ??
from /usr/lib/libgnome-desktop-2.so.2
#7 gnome_bg_changes_with_size
from /usr/lib/libgnome-desktop-2.so.2
#8 ??
from /usr/lib/libeel-2.so.2
#9 ??
from /usr/lib/libeel-2.so.2
#10 ??
from /usr/lib/libeel-2.so.2
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libeel-2.so.2
#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 ??
from /usr/lib/libgnome-desktop-2.so.2
#23 ??
from /usr/lib/libeel-2.so.2
#24 ??
from /usr/lib/libeel-2.so.2
#25 ??
#26 ??
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#29 ??
from /lib/libglib-2.0.so.0
#30 g_main_loop_run
from /lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgssapi_krb5.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-10 11:09:34 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 439977 ***