No, there is no correct backtrace attached yet
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This is evidently not a kernel bug. Mounting, ls, gnomevfs-ls, etc. all
work fine immediately.
I get this bug, too, BTW. I'll have a look at gdb'ing the problem.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Invalid
--
[gutsy] long delay in nautilus on first access to vfat
Confirmed here:
19545 12:28:26 statfs(/media/PittiHD, unfinished ...
[...]
19545 12:29:25 ... statfs resumed {f_type=MSDOS_SUPER_MAGIC, f_bsize=16384,
f_blocks=15254800, f_bfree=559138, f_bavail=559138, f_files=0, f_ffree=0,
f_fsid={0, 0}, f_namelen=260, f_frsize=16384}) = 0 59.423616
--
When booting current gutsy with the feisty kernel, the hang does not
occur, so it is a VFAT specific kernel regression. Sorry for prematurely
closing the kernel task.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Invalid = Confirmed
** Summary changed:
- [gutsy] long delay in
What's the best way to go about getting a backtrace?
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I'd like to help of course, but I don't know how to backtrace it. Would
you be so kind telling me? I really would like to see a fix until gutsy
release since it is an annoying bug :D
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You
the informations have been requested with an uri to a wiki page which
has explanations in the first comment to this bug, users interested to
an issue could read the comments
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this
Could anybody get a backtrace of nautilus while it's hanging? I don't
get the issue on my gutsy installation using a disk partition or an usb
key
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you
I take it the existing backtraces attached to this report aren't good
enough?
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I hope I did it the right way.
** Attachment added: backtrace nautilus
http://launchpadlibrarian.net/9714980/gdb-nautiluspid.txt
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member
I thought maybe something had gone wrong with the upgrade, so I downloaded the
latest daily live CD and it's still happening on the live CD.
Like Xavi Francisco said, the length of time Nautilus hangs is related to the
size of the drive. It's barely noticeable with a 2GB USB flash drive, but
I can also confirm this. I have an Iomega 160GB USB hard drive (FAT32)
and whenever I first try to access it, Nautilus hangs.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of
can confirm this bug too. It did not happen in feisty (though I only
used it to format and then to copy files to it, but there were no hangs
or lags at all). I reinstalled my computer yesterday with gutsy and all
latest updates. Everytime nautilus freezes, which is really anoying,
since nautilus
Yep, this is really annoying. I have 2 500GB drives and 2 250GB drives
that I attach via a USB2.0 hub. I've been using this setup for a while
now, and have just upgraded to gutsy and run into this. It takes several
minutes to open the drives in nautilus.
I assume this has to do with the new
** Changed in: nautilus (Ubuntu)
Target: None = ubuntu-7.10-rc
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I found out that I can access the drives through other programs while
Nautilus is frozen. I have all my music on my external drive and I can
play it off that drive with a media player while Nautilus is frozen. I
can also initially access the drive without any problems using a
different file
Happening here too, a Vantec Nexstar 3 external harddrive/Seagate 500GB.
The delay can be up to 5 minutes, on a Dell Inspiron 6400 (gutsy).
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a
Same problem here with a partition on my main HDD. I think it might be related
to the kernel.
I had feisty installed and I updated the kernel to the gutsy one (see
http://ubuntuforums.org/showthread.php?t=511974) (because my wifi chipset
wasn't supported in feisty). The problem only happened
Same to me here, but I also noticed that the time taken to open the disk
is proportional to the size. So a 1 Gb USB drive takes a few seconds (10
or so) and a 250Gb USB drive takes about 10 minutes to mount. Using HTOP
I could also notice that the kernel process is using 100% of the CPU
while I
I have the same bug. It affects both a Fat32 partition on my internal
SATA hard drive and a Fat32-formatted USB external hard drive.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member
I can reproduce this bug. I Have an external usb disk drive containing a
fat32 partition and a ntfs partition. If I can help please let me know.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you
Same symptom on first access to a FAT32 partition (added per the
standard recommendation for sharing data between dual-boot) on the same
internal SATA drive that gutsy is installed on.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You
Can someone from linux-source look at this? It is still marked as
importance: ''Undecided'. Is it readily reproducible or do just some
people have problems with it?
Imho I think it's quite important, as having to waiting 30-60 seconds to
mount an external drive (during which all other nautilus
opening a linux-source-2.6.22 task, maybe the kernel team knows about
some vfat issue
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received
I think the problem lies within the code that the system call
sys_statfs64 executes, perhaps when it calls the vfs code for the vfat
file system.
I straced sudo nautilus to stop it sending the request to any existing
process:
1. killall gnome-volume-manager
2. Attach drive
3. sudo -i
4. mkdir
I am having this problem too, be it with IDE or SATA drives.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
That doesn't look like a nautilus bug if gnome-volume-manager is have
issues as well. Do you have anything about the drive to
/var/log/messages or /var/log/syslog?
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug
I can't see anything too unusual in those files except that I get two
nm_policy_device_change_check messages every five seconds in syslog.
But this happens whether the drive is plugged in or not.
Attached is a file showing:
(a) what appeared in syslog and messages when I plugged the drive into
I tried emptying the vfat drive completely of all files (including
trash), and it still experienced the delay in first opening nautilus.
I tried reformatting the drive using gparted (which incidentally crashed
when it went to rescan the drives afterwards, and now my external drives
no longer
Re my previous comment, after rebooting, my drives are auto-mounting
again, and now I can confirm a difference in operation between
automounting and manually mounting the drive:
a) If the drive automounts, gnome-volume-manager doesn't spend ages
doing something with it until I try to open it in
No, nautilus doesn't run fsck on the disk. Could you try gnomevfs-ls on
the disk, is it as slow as nautilus? Do you have files which are
thumbnailed on the disk? Does it happen with a blank one?
** Changed in: nautilus (Ubuntu)
Status: Incomplete = New
--
[gutsy] long delay in nautilus
gnomevfs-ls is fast. I tried it on the drive immediately after mounting
it and it works pretty much instantly. If I mount the drive, then try to
open it in nautilus, then run gnomevfs-ls on the drive, it works
straight away, even while nautilus is frozen.
I haven't thumbnailed the files on the
I can add that does it with my vfat usb hdd, but not with my vfat usb
key.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I noticed that the drive light flickers furiously during the delay.
Might nautilus be trying to build a directory listing or run fsck on the
drive?
I tried an strace nautilus folder command, but the process detaches
before the delay starts.
I installed tribe5 from scratch in case it would fix
I have exactly the same problem. When I plug in a vfat external usb HDD,
Nautilus freezes during about 30 secondes before I can do something
(except using other programs like firefox). The window of hdd content
opens, but nothing appears and I have the waiting cursor.
I've attached a backtrace
I have the same problem too. Any fix?
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ditto here too, FAT32 formatted iPod.
--
[gutsy] long delay in nautilus on first access to vfat drive
https://bugs.launchpad.net/bugs/133567
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
Does it happen when using a fileselector? How do you mount the drive?
** Changed in: nautilus
I've attached a backtrace of the command 'nautilus' run on the offending
directory, but it doesn't look very useful. Nautilus doesn't crash, it
just hangs for a long time (in the log, the delay starts after the lines
'Initializing gnome-mount extension; /bin/sh: /usr/bin/esd: not found'
appear) .
39 matches
Mail list logo
