Bug 533319 – crash in File Browser: abriendo red

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 533319 - crash in File Browser: abriendo red


Summary:	crash in File Browser: abriendo red


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-15 17:17 UTC by j-badi
Modified:	2008-05-15 19:30 UTC

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

Description j-badi 2008-05-15 17:17:13 UTC

Version: 2.20.0

What were you doing when the application crashed?
abriendo red


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: 80793600 vsize: 80793600 resident: 25288704 share: 15601664 rss: 25288704 rss_rlim: 4294967295
CPU usage: start_time: 1210870411 rtime: 787 utime: 734 stime: 53 cutime:0 cstime: 1 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 0xb6ba7720 (LWP 3137)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197809

Thread 1 (Thread 0xb6ba7720 (LWP 3137))

#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 (9 sec old) ---------------------
Error al enviar la contraseña: Operación en curso
CalDAV Eplugin starting up ...
** (evolution:4055): DEBUG: mailto URL command: evolution %s
** (evolution:4055): DEBUG: mailto URL program: evolution
kbuildsycoca running...
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x66 especificada para 0x2200008 (Configurar).
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x66 especificada para 0x2200008 (Configurar).
kbuildsycoca running...
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x66 especificada para 0x2200008 (Configurar).
kbuildsycoca running...
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x66 especificada para 0x2200008 (Configurar).
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------

Comment 1 Paweł Paprota 2008-05-15 19:30:46 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 522534 ***