Bug 533930 – 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 533930 - 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-19 21:24 UTC by ox1d0
Modified:	2008-05-20 07:27 UTC

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

Description ox1d0 2008-05-19 21:24:42 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: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: vitality-black
Icon Theme: black-white_2-Neon

Memory status: size: 61358080 vsize: 61358080 resident: 22470656 share: 15609856 rss: 22470656 rss_rlim: 4294967295
CPU usage: start_time: 1211232146 rtime: 592 utime: 552 stime: 40 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 0xb6bfc720 (LWP 5001)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198160

Thread 1 (Thread 0xb6bfc720 (LWP 5001))

#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 ---------------------
This can cause subtle evils like #48423
** (nautilus:31989): WARNING **: Possibly invalid new URI 'smb://fatbyte/Soporte/respaldos/Herrera HP/Mis documentos/Mis%20v%C3%ADdeos'
This can cause subtle evils like #48423
(bug-buddy:4465): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
Initializing gnome-mount extension
(nautilus:5001): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
(nautilus:5071): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
(nautilus-connect-server:5964): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
(bug-buddy:8933): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-20 07:27:51 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 ***