Unable to mount NTFS partition when LOOP-AES-UTILS is installed

Bug #731228 reported by NooP
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
loop-aes-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: loop-aes-utils

When the package loop-aes-utils is installed, the mount command is unable to mount a NTFS partition. The mount command does not return any error message either on console or system logs, simply returning to the prompt without even telling it can't mount the NTFS partition.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: loop-aes-utils (not installed)
ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13
Uname: Linux 2.6.32-29-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Mar 8 12:47:35 2011
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: loop-aes-utils

NooP (noop)
tags: added: loop-aes-utils
removed: apport-bug
Revision history for this message
Michael Schmidt (ice-crowley) wrote :

I have the same problem here.

The /sbin/mount replacement of the loop-aes-utils packages breaks the complete fuse system.
I just did an strace -f on the fuse project's hello.c example code and found fuse uses the --no-canonicalize option in it's mount calls which is not understood by the loop-aes-utils version.

The mount call correctly reports this problem to stderr, but the cloned process execve'ing is detached from this filedescriptor. This is probably a bug in libfuse2.

Revision history for this message
danmb (danmbox) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Someone needs to backport --no-canonicalize to loop-aes-utils's mount, as it is now required by the fuse security updates. If someone can prepare debdiffs, attach them here, and subscribe ubuntu-security-sponsors, they will get pushed out as a security update.

Thanks!

Changed in loop-aes-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Douglas Baigrie (dbaigrie) wrote :

The same issue is also preventing the gvfs-fuse-daemon from mounting the $HOME/.gvfs directory

This breaks a number of things that rely on this method to gain access to network resources over GVFS when not using GIO. i.e. Openoffice/Libreoffice.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.