Your message dated Sat, 25 Oct 2008 18:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#496269: fixed in gvfs 0.2.5-1.1
has caused the Debian Bug report #496269,
regarding gvfs-fuse: reports ENOTCONN after heavy use
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496269
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gvfs-fuse
Version: 0.2.5-1
Severity: grave

I have all of my music on a remote machine, which I mount using gvfs
(sftp via nautilus).  I have the Amarok 2 beta (from experimental)
installed.  One of the directories that I have told Amarok is part of my
collection is a symlink to the gvfs-fuse mount.  When I tell Amarok to
rescan my collection, it gets about 2% in, and then it completes
quickly.

When I check the symlink manually, I see:

  lakeview ok % ls -l ~/audio/castro
  lrwxrwxrwx 1 bmc bmc 54 2008-07-31 13:45 /home/bmc/audio/castro -> 
../.gvfs/sftp on castro/media/data/bmc/finished/music/
  lakeview ok % ls -l ~/audio/castro/
  ls: cannot access /home/bmc/audio/castro/: Transport endpoint is not connected

Obviously, Amarok "completes" the scan of my music due to the fact that
it is receiving ENOTCONN.

The only way I can unbreak gvfs-fuse is to log out and log back in
again, but the same thing happens again if I try to scan my music via
Amarok.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-rc3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gvfs-fuse depends on:
ii  libc6                         2.7-13     GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.1-3    simple interprocess messaging syst
ii  libfuse2                      2.7.3-5    Filesystem in USErspace library
ii  libglib2.0-0                  2.16.5-1   The GLib library of C routines
ii  libgvfscommon0                0.2.5-1    userspace virtual filesystem - lib

gvfs-fuse recommends no packages.

gvfs-fuse suggests no packages.

-- no debconf information

--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: gvfs
Source-Version: 0.2.5-1.1

We believe that the bug you reported is fixed in the latest version of
gvfs, which is due to be installed in the Debian FTP archive:

gvfs-backends_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/gvfs-backends_0.2.5-1.1_i386.deb
gvfs-bin_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/gvfs-bin_0.2.5-1.1_i386.deb
gvfs-fuse_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/gvfs-fuse_0.2.5-1.1_i386.deb
gvfs_0.2.5-1.1.diff.gz
  to pool/main/g/gvfs/gvfs_0.2.5-1.1.diff.gz
gvfs_0.2.5-1.1.dsc
  to pool/main/g/gvfs/gvfs_0.2.5-1.1.dsc
gvfs_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/gvfs_0.2.5-1.1_i386.deb
libgvfscommon-dev_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/libgvfscommon-dev_0.2.5-1.1_i386.deb
libgvfscommon0_0.2.5-1.1_i386.deb
  to pool/main/g/gvfs/libgvfscommon0_0.2.5-1.1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams <[EMAIL PROTECTED]> (supplier of updated gvfs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 25 Oct 2008 09:29:53 -0400
Source: gvfs
Binary: libgvfscommon0 libgvfscommon-dev gvfs gvfs-fuse gvfs-backends gvfs-bin
Architecture: source i386
Version: 0.2.5-1.1
Distribution: unstable
Urgency: high
Maintainer: Sebastien Bacher <[EMAIL PROTECTED]>
Changed-By: Clint Adams <[EMAIL PROTECTED]>
Description: 
 gvfs       - userspace virtual filesystem - server
 gvfs-backends - userspace virtual filesystem - backends
 gvfs-bin   - userspace virtual filesystem - binaries
 gvfs-fuse  - userspace virtual filesystem - fuse server
 libgvfscommon-dev - userspace virtual filesystem - development files
 libgvfscommon0 - userspace virtual filesystem - library
Closes: 496269
Changes: 
 gvfs (0.2.5-1.1) unstable; urgency=high
 .
   * NMU
   * Apply upstream SVN r1819 - "(reindex_file_handle_for_path): Steal the old
     file handle record from the global hash table before replacing its path,
     not after."
   * Apply upstream SVN r1822: "(vfs_create): Hold the file handle lock while
     opening the stream."
   * Apply upstream SVN r1844: "Don't call statvfs on /."
   * Apply upstream SVN r1854: "Avoid a race between the subthread and the
     main thread in the case of dbus going bye-bye."
   * Apply part of r2052: "Set st_blocks & co so that du works."
   * Apply upstream SVN r2056: "Attempt to prevent potential race conditions in
     the FUSE backend when file handles get closed while still in use in
     another thread, if that ever happens."  closes: #496269.
Checksums-Sha1: 
 776474374083836f0f476c4279535cb8878a7172 1573 gvfs_0.2.5-1.1.dsc
 8ecb34011d17bc22c0f737432bd8b555783ce54d 7453 gvfs_0.2.5-1.1.diff.gz
 48e39d39e63d42425e206ed6af711997d4e0c67c 62970 
libgvfscommon0_0.2.5-1.1_i386.deb
 c85157c8876c21884ff7d1c72ccecc3ccfc3ea22 40050 
libgvfscommon-dev_0.2.5-1.1_i386.deb
 f1ef94904e436fe6e856fd9b03c74977278c481a 405142 gvfs_0.2.5-1.1_i386.deb
 155d004beb4696493b63f55d6a4abc6176ead332 49846 gvfs-fuse_0.2.5-1.1_i386.deb
 9b53897a93855caa13d613fa05945a145c56acf8 769894 
gvfs-backends_0.2.5-1.1_i386.deb
 e6c72d3792017df49ac8e3f9a83fa65f166c768a 70678 gvfs-bin_0.2.5-1.1_i386.deb
Checksums-Sha256: 
 d85b22fda16a521c94965693614e0a2c7fd58b76cf6bb87111a55e35ff1959ed 1573 
gvfs_0.2.5-1.1.dsc
 6de8517824cd0ed2cad8544213930469d93e637aaf0d02b3f71e785a846661d6 7453 
gvfs_0.2.5-1.1.diff.gz
 81c906702c61cc2810145305506e2f194b493d18871f9825cf9844f7ac57cf6b 62970 
libgvfscommon0_0.2.5-1.1_i386.deb
 2a655c403d9a694124e4738982a1ee0885f508353b74dec01b1a240374edae92 40050 
libgvfscommon-dev_0.2.5-1.1_i386.deb
 61963472f7606bb5766838365e8eed4c3952e4b16baf0f9e8b43798486cde704 405142 
gvfs_0.2.5-1.1_i386.deb
 11bb7118c80282d0e32080da9a7d1c27dd52ec0782d7a77c897db437e09b5706 49846 
gvfs-fuse_0.2.5-1.1_i386.deb
 d06f3d58cf52549c40bcc73396585a573a97588cd9bea04042478d75d7f93235 769894 
gvfs-backends_0.2.5-1.1_i386.deb
 9802615055e18e4766732d0657cca3cf46066c189066ab8c1b8ff00079a3ef82 70678 
gvfs-bin_0.2.5-1.1_i386.deb
Files: 
 c8427a1ce80dce493073bbb723a5124c 1573 libs optional gvfs_0.2.5-1.1.dsc
 b66e9aa891a655618e22fb3a1c43c692 7453 libs optional gvfs_0.2.5-1.1.diff.gz
 c7ea2a261553a8fe812e33d83e7dbe94 62970 libs optional 
libgvfscommon0_0.2.5-1.1_i386.deb
 a874f89fe7e3a1311491e42d8d41ee36 40050 libdevel optional 
libgvfscommon-dev_0.2.5-1.1_i386.deb
 1997ef969a8e11784aa4a6e574529e47 405142 libs optional gvfs_0.2.5-1.1_i386.deb
 f592f449981f08ebf2ad706b811ec973 49846 libs optional 
gvfs-fuse_0.2.5-1.1_i386.deb
 a34b9e070be780e5a10389c322f20983 769894 libs optional 
gvfs-backends_0.2.5-1.1_i386.deb
 51a9f81849fa97df433108948304b124 70678 libs optional 
gvfs-bin_0.2.5-1.1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Debian!

iD8DBQFJA2je5m0u66uWM3ARAp3XAJoCLgM9GX56YEz3NgSu9EuwHK1rrgCfSRaP
EO7/+SBAvi0u1KVKQ1hI30I=
=0Iad
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to