Bug 495088 – crash in Open Folder: Just wanted to know how ...

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 495088 - crash in Open Folder: Just wanted to know how ...


Summary:	crash in Open Folder: Just wanted to know how ...


Status:	RESOLVED DUPLICATE of bug 479101

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-08 19:36 UTC by kai
Modified:	2007-11-09 15:29 UTC

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

Description kai 2007-11-08 19:36:20 UTC

Version: 2.18.3

What were you doing when the application crashed?
Just wanted to know how much free space is left on my usb memory stick. 
Do not worry about responding; I am only sending this because you guys 
seem to think it is important. Thanks for your effort!!!



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: 372154368 vsize: 372154368 resident: 28749824 share: 16760832 rss: 28749824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194487302 rtime: 355 utime: 287 stime: 68 cutime:58 cstime: 16 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 0x2b749614dbc0 (LWP 3771)]
(no debugging symbols found)
0x00002b748f6d4c7f in waitpid () from /lib/libpthread.so.0

+ Trace 176413

Thread 1 (Thread 0x2b749614dbc0 (LWP 3771))

#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 (32 sec old) ---------------------
** 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
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 palfrey 2007-11-09 15:29:05 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 479101 ***