Bug 534384 – crash in File Browser: Using Nautilus for acces...

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 534384 - crash in File Browser: Using Nautilus for acces...


Summary:	crash in File Browser: Using Nautilus for acces...


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-22 17:22 UTC by sky
Modified:	2008-05-22 17:47 UTC

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

Description sky 2008-05-22 17:22:43 UTC

Version: 2.20.0

What were you doing when the application crashed?
Using Nautilus for accessing a Samba server


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: Wasp
Icon Theme: Wasp

Memory status: size: 89968640 vsize: 89968640 resident: 35069952 share: 17645568 rss: 35069952 rss_rlim: 4294967295
CPU usage: start_time: 1211471198 rtime: 2369 utime: 2239 stime: 130 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 0xb6be9720 (LWP 2705)]
[New Thread 0xb5ee4b90 (LWP 7580)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198399

Thread 1 (Thread 0xb6be9720 (LWP 2705))

#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 (556 sec old) ---------------------
[Info 19:11:23.560] Updated first results for 'v'. 
[Info 19:11:23.562] Updated first results for 'w'. 
[Info 19:11:23.563] Updated first results for 'x'. 
[Info 19:11:23.564] Updated first results for 'y'. 
[Info 19:11:23.566] Updated first results for 'z'. 
[Info 19:11:23.568] Updated first results for 'a'. 
[Info 19:12:23.328] Updated "File Indexer" Item Source. 
[Info 19:12:23.332] Updated "Firefox Bookmarks" Item Source. 
[Info 19:12:23.344] Updated "GNOME Special Locations" Item Source. 
[Info 19:12:23.344] Updated "Recent Files" Item Source. 
[Info 19:12:23.344] Updated "Internal GNOME Do Items" Item Source. 
[Info 19:12:23.345] Updated "GNOME Do Item Sources" Item Source. 
[Info 19:12:23.474] Updated "Applications" Item Source. 
[Info 19:12:23.476] Updated first results for 'b'. 
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-22 17:47:40 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 ***