Bug 533107 – 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 533107 - 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-05-14 13:23 UTC by jmiguel35013
Modified:	2008-05-14 16:51 UTC

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

Description jmiguel35013 2008-05-14 13:23:56 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: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 82440192 vsize: 82440192 resident: 27193344 share: 15679488 rss: 27193344 rss_rlim: 4294967295
CPU usage: start_time: 1210771412 rtime: 215 utime: 202 stime: 13 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 0xb6bc7720 (LWP 20961)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197704

Thread 1 (Thread 0xb6bc7720 (LWP 20961))

#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 ---------------------
[200] [201] [202] [203] [204] [205] [206] [207] [208] [209] [210] [211] [212]
[213] [214] [215] [216] [217] [218] [219] [220] [221] [222] [223] [224] [225]
[226] [227] [228] [229] [230] [231] [232] [233] [234] [235] [236] [237] [238]
[239] [240] [241] [242] [243] [244] [245] [246] [247] [248] [249] [250] [251]
[252] [253] [254] [255]
mktexpk: /home/jmiguel/.texmf-var/fonts/pk/modeless/adobe/helvetic/phvro8r.540pk: successfully generated.
** (update-notifier:3533): WARNING **: no cdrom: disk
(nautilus:3526): Eel-WARNING **: No extension, not implemented yet
seahorse nautilus module initialized
Initializing gnome-mount extension
(nautilus:20961): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-14 16:49:54 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 3550 ***

Comment 2 Cosimo Cecchi 2008-05-14 16:51:06 UTC


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