Bug 545693 – 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 545693 - 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-07-31 14:14 UTC by raedcharrouf
Modified:	2008-07-31 17:29 UTC

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

Description raedcharrouf 2008-07-31 14:14:56 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 86994944 vsize: 86994944 resident: 32616448 share: 17350656 rss: 32616448 rss_rlim: 4294967295
CPU usage: start_time: 1217513637 rtime: 386 utime: 371 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bb3940 (LWP 21137)]
[New Thread 0xb4b3db90 (LWP 21191)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 204274

Thread 1 (Thread 0xb6bb3940 (LWP 21137))

#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 (38 sec old) ---------------------
** (nautilus:20735): WARNING **: Hit unhandled case 46 (Se ha alcanzado el tiempo de espera establecido) in fm_report_error_loading_directory
** (nautilus:20735): WARNING **: Hit unhandled case 46 (Se ha alcanzado el tiempo de espera establecido) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:21137): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Publico»), avise a la lista de correo de gnome-vfs.
** Message: Hit unexpected error "Acceso denegado" while doing a file operation.
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-07-31 17:29:30 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 ***