Bug 488368 – crash in Home Folder:

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 488368 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 485771

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-10-19 17:53 UTC by volney
Modified:	2007-10-19 22:22 UTC

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

Description volney 2007-10-19 17:53:04 UTC

What were you doing when the application crashed?



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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 91332608 vsize: 91332608 resident: 35721216 share: 21516288 rss: 35721216 rss_rlim: 4294967295
CPU usage: start_time: 1192819727 rtime: 575 utime: 540 stime: 35 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 -1208670496 (LWP 4582)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171490

Thread 1 (Thread -1208670496 (LWP 4582))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 ??
#6 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /lib/libgobject-2.0.so.0
#8 ??
from /lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#10 g_signal_emit
from /lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_combo_box_set_active
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 nautilus_file_emit_changed
#20 nautilus_directory_emit_change_signals
#21 nautilus_file_changed
#22 ??
#23 ??
from /usr/lib/libgnomevfs-2.so.0
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
from /lib/libpthread.so.0
#31 ??
#32 ??
from /lib/libpthread.so.0
#33 ??
#34 ??
#35 ??
from /usr/lib/libgnomevfs-2.so.0
#36 ??
#37 ??
#38 ??
#39 g_slice_alloc
from /lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (224 sec old) ---------------------
Sample Rate    : 11025

Time: 00:00.74 [00:00.67] of 00:01.41 ( 52.7%) Output Buffer:  35.52K
Time: 00:01.41 [00:00.00] of 00:01.41 ( 100.0%) Output Buffer:  67.58K
Done.
Input File     : '/usr/share/amsn/skins/default/sounds/type.wav'
Sample Size    : 16-bit (2 bytes)
Sample Encoding: signed (2's complement)
Channels       : 1
Sample Rate    : 11025

Time: 00:00.74 [00:00.67] of 00:01.41 ( 52.7%) Output Buffer:  35.52K
Time: 00:01.41 [00:00.00] of 00:01.41 ( 100.0%) Output Buffer:  67.58K
Done.
--------------------------------------------------

Comment 1 Christian Kirbach 2007-10-19 21:59:12 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 André Klapper 2007-10-19 22:22:29 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 485771 ***