Bug 496429 – crash in Home Folder: seeing property of usb m...

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 496429 - crash in Home Folder: seeing property of usb m...


Summary:	crash in Home Folder: seeing property of usb m...


Status:	RESOLVED INCOMPLETE

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-11-13 12:58 UTC by kuenishi
Modified:	2007-11-13 22:31 UTC

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

Description kuenishi 2007-11-13 12:58:05 UTC

What were you doing when the application crashed?
seeing property of usb memory disk icon, which appeared at desktop(automatically mounted on /somewhere/ with vfat32). and tried to see "Volume" tab.


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

System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MidnightBlackPlastic
Icon Theme: OSX

Memory status: size: 393879552 vsize: 393879552 resident: 35082240 share: 18161664 rss: 35082240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194953215 rtime: 433 utime: 317 stime: 116 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 0x2b0880ed2bc0 (LWP 3847)]
(no debugging symbols found)
0x00002b087a459c7f in waitpid () from /lib/libpthread.so.0

+ Trace 177408

Thread 1 (Thread 0x2b0880ed2bc0 (LWP 3847))

#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 (818 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
** Message: volume = 0
--------------------------------------------------

Comment 1 André Klapper 2007-11-13 22:31:18 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