Bug 525138 – crash in Home Folder: I opened a subdirectory ...

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 525138 - crash in Home Folder: I opened a subdirectory ...


Summary:	crash in Home Folder: I opened a subdirectory ...


Status:	RESOLVED DUPLICATE of bug 525181

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-30 16:06 UTC by volker.sturm
Modified:	2008-03-31 18:02 UTC

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

Description volker.sturm 2008-03-30 16:06:05 UTC

What were you doing when the application crashed?
I opened a subdirectory in a windows share mounted via smb. Other subdirectories can be opened. I cannot determine what the problem with this particular directory is.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 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: 80777216 vsize: 80777216 resident: 29630464 share: 16556032 rss: 29630464 rss_rlim: 4294967295
CPU usage: start_time: 1206892930 rtime: 1114 utime: 714 stime: 400 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 0xb6bc2720 (LWP 3935)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193690

Thread 1 (Thread 0xb6bc2720 (LWP 3935))

#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 (19 sec old) ---------------------
seahorse nautilus module initialized
** (nautilus:3758): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Backup«), teilen Sie dies der gnome-vfs-Mailingliste mit.
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3819): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Backup«), teilen Sie dies der gnome-vfs-Mailingliste mit.
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3892): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Backup«), teilen Sie dies der gnome-vfs-Mailingliste mit.
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3935): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Backup«), teilen Sie dies der gnome-vfs-Mailingliste mit.
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-31 18:02:24 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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