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


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-05-22 14:41 UTC by adrian
Modified:	2008-05-22 17:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description adrian 2008-05-22 14:41:01 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 61739008 vsize: 61739008 resident: 23740416 share: 15650816 rss: 23740416 rss_rlim: 4294967295
CPU usage: start_time: 1211466963 rtime: 230 utime: 212 stime: 18 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c0d720 (LWP 3180)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198385

Thread 1 (Thread 0xb6c0d720 (LWP 3180))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors (195 sec old) ---------------------
** (gnome-settings-daemon:3077): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No existe el fichero o el directorio
Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/clientes/.metacity/sessions/default0.ms: Failed to open file '/home/clientes/.metacity/sessions/defau
Initializing gnome-mount extension
seahorse nautilus module initialized
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized

(synaptic:3208): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-22 17:48:34 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 522534 ***