Bug 521250 – 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 521250 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 355018

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-03-08 20:26 UTC by Francisco Espinoza
Modified:	2008-03-10 11:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Francisco Espinoza 2008-03-08 20:26:05 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: GartoonRedux

Memory status: size: 68845568 vsize: 68845568 resident: 22061056 share: 14860288 rss: 22061056 rss_rlim: 4294967295
CPU usage: start_time: 1205007767 rtime: 169 utime: 155 stime: 14 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 0xb6c2b6c0 (LWP 3255)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 191781

Thread 1 (Thread 0xb6c2b6c0 (LWP 3255))

#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 strcmp
from /lib/i686/cmov/libc.so.6
#7 g_str_equal
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libeel-2-2.20.so
#9 ??
#10 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
CachingBackend: <#Flower1> removed!
Removing last instance from session
TODO: remove self.path: /home/francisco/.config/Screenlets/Flower/default/
delete
Removing entry for FlowerScreenlet from global tempfile /tmp/screenlets/screenlets.running
Entry not found. Will (obviously) not be removed.
Advertencia del gestor de ventanas: Received a _NET_WM_MOVERESIZE message for 0x2200006 (CPUMeterSc); these messages lack timestamps and therefore suck.
Couldn't read /home/francisco/.gnokiirc config file.
Couldn't read /home/francisco/.gnokiirc config file.
(xgnokii:3379): Gtk-WARNING **: horizontal scrolling not implemented
(xgnokii:3379): Gtk-WARNING **: horizontal scrolling not implemented
(nautilus:3255): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-10 11:06:03 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 355018 ***