ntfs-3g "Transport endpoint is not connected", fuse implicated

Bug #1072270 reported by skierpage on 2012-10-28
This bug affects 19 people
Affects Status Importance Assigned to Milestone
fuse (Ubuntu)

Bug Description

Since upgrading to 12.10 Quantal, three times after coming out of standby my WIndows NT drives have reported
  cannot access /mnt/WindowsVistadrive: Transport endpoint is not connected
The problem goes away on reboot.

Participants in the arch forum report exactly this problem, see https://bugs.archlinux.org/task/30568 , and say fuse 2.9.2 fixes it. Perhaps someone could package this for 12.10.

I was able to `sudo umount` one of my Windows drives and `sudo remount` it and that restarted the /sbin/mount.ntfs-3g daemon.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: fuse 2.9.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Sat Oct 27 20:58:17 2012
MarkForUpload: True
 PATH=(custom, no user)
SourcePackage: fuse
UpgradeStatus: Upgraded to quantal on 2012-10-20 (7 days ago)

skierpage (skierpage) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fuse (Ubuntu):
status: New → Confirmed
Lee Hyde (anubeon) wrote :

I have a sneaky suspicious that this is what causes my NTFS data partition to crash every couple of days. Rather annoying actually, as I keep my Firefox, Thunderbird and a few other software profiles on it and the crash wrecks my desktop requiring a reboot.

I hope that fuse 2.9.2 gets packaged for Quantal soon.

Lixin Chin (wstfgl) wrote :

Direct link to the fuse patch from the archlinux bug report which purports to fix this issue:


Looks like fuse 2.9.2 is packaged for debian sid (http://packages.debian.org/sid/fuse), I wonder if that package would work under ubuntu quantal?

abece (abece) wrote :

I switched back to the "precise" versions of fuse and ntfs-3g in the meantime.

sudo sh -c "sed s/quantal/precise/g /etc/apt/sources.list > /etc/apt/sources.list.d/ubuntu_precise.sources.list"
sudo sh -c "echo 'Package: fuse libfuse2 sshfs ntfs-3
Pin: release n=precise
Pin-Priority: 1002' > /etc/apt/preferences.d/precise_fuse"
sudo apt-get update
sudo apt-get upgrade

Lixin Chin (wstfgl) wrote :

I've tried install the fuse and libfuse2 packages from debian sid (2.9.2-2) under amd64. Using the same ntfs-3g as currently in ubuntu 12.10.

It's only been a couple of days, but so far so good.

DavidZemon (david-zemon) wrote :


Do you see any reason to undo your fix when (if?) canonical ever posts their own patch? When 13.04 comes out, I'll be doing a fresh install so this will only affect me for another 5 months.

Thank you, by the way, for your fix. It is *very* appreciated.


This issue appears each time i do a clean-build on java projects, while having tomcat working on the same folders.
Tomcat locks some folders/files, fuse adds hidden file .fuse...... .
The clean-build removes the folder containing the lock file.
Fuse crashes.

Is there anything we can do to speed up resolution of this bug? It's pretty annoying, and I'm just waiting until I lose some data...was lucky so far..

Jose Gómez (adler-dreamcoder) wrote :

I have this error every couple of days, especially anytime that I try something disk-intensive, like compile the Linux kernel or decompressing the kernel sources.

Jose Gómez (adler-dreamcoder) wrote :
Jose Gómez (adler-dreamcoder) wrote :

Just updated fuse to 2.9.2-3 from the Debian builds at http://ftp.us.debian.org/debian/pool/main/f/fuse

I'll report any new crashes (or lack of them) after the update.

which packages did you install? fuse, fuse-utils, libfuse2?

Lixin Chin (wstfgl) wrote :

Two months using fuse and libfuse2 2.9.2-2 from debian sid, and no problems.

Hopefully this gets fixed officially soon. Ubuntun 13.04 looks like its going to be using fuse 2.9.0 which has this bug as well.

Sebastian Geiger (lanoxx) wrote :

I am noticing this bug since about two weeks, it started to appear on my notebook about two weeks ago. Today I experienced it the first time on my desktop computer too.

Both are running Ubuntu 12.10 with the latest updates.

This bug is highly annoying since I have mounted the MyDocuments folder into my home folder from an NTFS drive and it contains all my personal data.

A fix for this is highly appreciated.

Sebastian Geiger (lanoxx) wrote :

I should mention that this bug appreard about 5 or 6 times in two weeks already, and it seems that the only way to recover is to reboot. Simply remounting the device does not help.

Sebastian Geiger (lanoxx) wrote :

There is a related entry about this bug in the arch forum:


Many people confirm that this is fixed in 2.9.2, also this fix has been available since Oktober last year, which is four month ago.

I don't know what the proper course of action is here - should we open a separate "package 2.9.2 for Raring" bug? will that help, or will it be just as ignored as this one?

Jack Marshall (jxmac18) wrote :

Also to lend my weight - have same problem with latest release/updates of ubuntu/fuse 2.9.0-lubuntu2:

Feb 27 02:52:49 Warlock-mint kernel: [57298.889386] mount.ntfs[1064]: segfault at 7f268e1d1890 ip 00007f268ddef9bc sp 00007fff99f2f820 error 4 in libfuse.so.2.9.0[7f268dde8000+28000]

Only exhibited when running "find" across the filesystem and mounted under virtualbox.

Same problem here with 12.10 and fuse 2.9.0-1ubuntu2; most often after coming out of suspend, but sometimes just randomly for no apparent reason. Will try the debian 2.9.2 update, but this needs fixing ...

OK so now this happened the first time during a backup script running, yay. could someone PLEASE bump the importance of this bug?

Teo (teo1978) wrote :

So does the new version of fuse (whatever it is) really fix the issue?
how do I install it?

And when on earth will Canonical distribute the fix for Ubuntu? It's been months since this bug has been reported and it's f***ing critical. Just *deciding* the importance of bugs like this shouldn't take that long.

maybe we need to file another bug, with a needs-upgrade tag or so? I think there's a special tag for that (it's not needs-packaging), but it seems impossible to find a list of "proper" bug tags.

Lixin Chin (wstfgl) wrote :

To everyone looking for a "quick fix" to this issue:

Grab the packages 'fuse' and 'libfuse2' from the debian package archive. Get the package for your appropriate architecture (probably amd64 if you're using 64-bit, else i386).


I've been using versions 2.9.2-2, but the latest appears to be 2.9.2-4, not sure what's changed, but it's probably minor.

Install both packages "sudo dpkg -i ..."

Reboot, and you should be good to go. I've had no problems since installing 2.9.2 back in February, and I've used my ntfs filesystem on a daily basis since then.

Disappointing that 13.04 was allowed to release with such a glaring bug still present.

tags: added: raring
Lixin Chin (wstfgl) on 2013-04-29
tags: added: ntfs

I found the list of official tags, I think 'upgrade-software-version' is applicable, tagging as such.

tags: added: upgrade-software-version
Teo (teo1978) wrote :

I thought I had this "fixed" with the workaround as per comment #26.

Now, after the upgrade to 13.04, this is screwed up againg.

Did the upgrade uninstall the fixed package and reinstall the broken version again, or is it that the supposed fix was never a fix at all?

Teo (teo1978) wrote :

Actually, I see in Synaptic that the currently installed version of both fuse and libfuse is 2.9.2-4, so it appears that it's not fixed at all in that version.

Does anyone know if and where the upstream bug has been reported?

Teo (teo1978) wrote :

Now ntfs-3g has crashed immediately after reboot, yet my ntfs partition is mounted and working :O
(usually when it crashes, the ntfs partition becomes unaccessible)

Robert Ancell (robert-ancell) wrote :

Christoph, could you open a new bug to request the upgrade with the version to upgrade to and then tag that with upgrade-software-version. You can link the upgrade request to this bug.

tags: removed: upgrade-software-version

Robert, I think the need for pacakge upgrade has been superseded in the meantime by fuse 2.9.2-4 already being packaged in Saucy.

Furthermore, Matteo apparently still encounters this even with the upgraded package. I'm not sure that that is not a different bug, as I and, judging by the comments, some others, have not encountered the bug since upgrading.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers