Bug 508523 – crash in File Browser: I just pushed the right ...

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 508523 - crash in File Browser: I just pushed the right ...


Summary:	crash in File Browser: I just pushed the right ...


Status:	RESOLVED DUPLICATE of bug 355018

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-01-10 14:50 UTC by javiercano
Modified:	2008-01-10 20:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description javiercano 2008-01-10 14:50:18 UTC

Version: 2.18.3

What were you doing when the application crashed?
I just pushed the right buttom over a folder and click on Properties... using the gnome file browser (is still called Nautilus? :))


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.18-5-powerpc64 #1 SMP Sun Dec 23 04:13:32 UTC 2007 ppc64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 94609408 vsize: 94609408 resident: 26517504 share: 18653184 rss: 26517504 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199976536 rtime: 367 utime: 330 stime: 37 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 0xf7fba000 (LWP 4682)]
(no debugging symbols found)
0x0f1772a4 in waitpid () from /lib/libpthread.so.0

+ Trace 184798

Thread 1 (Thread 0xf7fba000 (LWP 4682))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
#5 <signal handler called>
#6 strcmp
from /lib/libc.so.6
#7 ??
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_tree_model_row_deleted
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
#23 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 nautilus_file_emit_changed
#29 nautilus_directory_emit_change_signals
#30 nautilus_file_changed
#31 ??
#32 ??
from /usr/lib/libgnomevfs-2.so.0
#33 ??
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#35 ??
from /usr/lib/libglib-2.0.so.0
#36 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#37 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#38 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** 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 Cosimo Cecchi 2008-01-10 20:56:58 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 355018 ***