Bug 487608 – 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 487608 - crash in File Browser:


Summary:	crash in File Browser:


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:

Duplicates:	487819 (view as bug list)
Depends on:
Blocks:

Reported:	2007-10-17 19:17 UTC by xiscrizioni
Modified:	2007-10-19 01:56 UTC

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

Description xiscrizioni 2007-10-17 19:17:15 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 464572416 vsize: 464572416 resident: 40169472 share: 17616896 rss: 40169472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192630334 rtime: 35702 utime: 21467 stime: 14235 cutime:2492 cstime: 284 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 0x2b9baff72b60 (LWP 10358)]
[New Thread 0x42804950 (LWP 16899)]
(no debugging symbols found)
0x00002b9ba9804c7f in waitpid () from /lib/libpthread.so.0

+ Trace 170920

Thread 1 (Thread 0x2b9baff72b60 (LWP 10358))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 strcmp
from /lib/libc.so.6
#4 ??
#5 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#6 ??
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 nautilus_file_emit_changed
#22 nautilus_directory_emit_change_signals
#23 nautilus_file_changed
#24 ??
#25 ??
from /usr/lib/libgnomevfs-2.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 ??
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (38894 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-10-17 23:11:32 UTC

Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 2 Jens Granseuer 2007-10-18 21:11:46 UTC

*** Bug 487819 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-10-19 01:56:49 UTC

same issue as bug 485771

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