Bug 536262 – 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 536262 - 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-06-02 15:06 UTC by soria.jesus
Modified:	2008-06-02 19:00 UTC

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

Description soria.jesus 2008-06-02 15:06:00 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 Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Xfce-curve
Icon Theme: GartoonRedux

Memory status: size: 98586624 vsize: 98586624 resident: 34091008 share: 22663168 rss: 34091008 rss_rlim: 4294967295
CPU usage: start_time: 1212413232 rtime: 438 utime: 384 stime: 54 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 0xb6a85940 (LWP 2690)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199409

Thread 1 (Thread 0xb6a85940 (LWP 2690))

#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 ---------------------
Mon Jun  2 10:48:49 2008
 CConn:       connected to host 192.168.1.6 port 5900
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 6 (8bpp) rgb222
 CConn:       Using ZRLE encoding
 CConn:       Throughput 20384 kbit/s - changing to hextile encoding
 CConn:       Throughput 20384 kbit/s - changing to full colour
 CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
 CConn:       Using hextile encoding
Advertencia del gestor de ventanas: Received a _NET_WM_MOVERESIZE message for 0x400009d (Documento ); these messages lack timestamps and therefore suck.
** (nautilus:2690): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Mis%20documentos»), avise a la lista de correo de gnome-vfs.
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-02 19:00:11 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 ***