Bug 539459 – crash in File Browser: Trying to open directory...

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 539459 - crash in File Browser: Trying to open directory...


Summary:	crash in File Browser: Trying to open directory...


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-06-21 13:58 UTC by Piotr Iwaniuk
Modified:	2008-06-21 21:35 UTC

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

Description Piotr Iwaniuk 2008-06-21 13:58:09 UTC

Version: 2.20.0

What were you doing when the application crashed?
Trying to open directory on smb network. Directory probably contained some video files.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 112259072 vsize: 112259072 resident: 42893312 share: 21037056 rss: 42893312 rss_rlim: 4294967295
CPU usage: start_time: 1214046314 rtime: 2184 utime: 1930 stime: 254 cutime:350 cstime: 94 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b4a720 (LWP 4040)]
[New Thread 0xb58ffb90 (LWP 7693)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201015

Thread 1 (Thread 0xb6b4a720 (LWP 4040))

#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

Comment 1 A. Walton 2008-06-21 21:35:58 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 ***