Bug 558429 – crash in File Browser: Estaba intentando accede...

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 558429 - crash in File Browser: Estaba intentando accede...


Summary:	crash in File Browser: Estaba intentando accede...


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-10-29 18:16 UTC by guillermoniveyro
Modified:	2008-10-31 14:43 UTC

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

Description guillermoniveyro 2008-10-29 18:16:11 UTC

Version: 2.20.0

What were you doing when the application crashed?
Estaba intentando acceder en una red de windows para leer unos archivos de video


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

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 459280384 vsize: 459280384 resident: 31248384 share: 16871424 rss: 31248384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225303527 rtime: 162 utime: 150 stime: 12 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 0x2b4eb5eb6240 (LWP 3123)]
(no debugging symbols found)
0x00002b4eaf3acedf in waitpid () from /lib/libpthread.so.0

+ Trace 208888

Thread 1 (Thread 0x2b4eb5eb6240 (LWP 3123))

#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 <signal handler called>
#5 ??
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 ??
#8 ??
#9 ??
from /usr/lib/libgnomevfs-2.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
#15 __libc_start_main
from /lib/libc.so.6
#16 ??
#17 ??
#18 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (10 sec old) ---------------------
(nautilus:3123): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:3123): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:3123): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:3123): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-10-31 14:43:33 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 ***