Bug 529266 – crash in Open Folder: I was just trying to acc...

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 529266 - crash in Open Folder: I was just trying to acc...


Summary:	crash in Open Folder: I was just trying to acc...


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-04-21 19:49 UTC by plok
Modified:	2008-04-22 17:28 UTC

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

Description plok 2008-04-21 19:49:00 UTC

Version: 2.20.0

What were you doing when the application crashed?
I was just trying to access a folder on the network


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 Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 203702272 vsize: 203702272 resident: 133677056 share: 17608704 rss: 133677056 rss_rlim: 4294967295
CPU usage: start_time: 1208710189 rtime: 68901 utime: 60659 stime: 8242 cutime:6089 cstime: 781 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 0xb6c07720 (LWP 3421)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195805

Thread 1 (Thread 0xb6c07720 (LWP 3421))

#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 (303 sec old) ---------------------
(K3bDevice::Device) /dev/hda: READ 10 failed!
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) /dev/hda: READ 10 failed!
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) /dev/hda: READ 10 failed!
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-22 17:28:46 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 ***