Just built a new custom 2.6.37.2 kernel with CONFIG_FUSE_FS=y rather
than CONFIG_FUSE_FS=m as I'd been using. It didn't make a difference
whether FUSE is compiled into the kernel or as a module.
# apt-cache showpkg libfuse2
Package: libfuse2
Versions:
2.8.4-1ubuntu1.3
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick-updates_main_binary-amd64_Packages)
(/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_maverick-security_main_binary-amd64_Packages)
Description Language:
File:
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick-updates_main_binary-amd64_Packages
MD5: 5d223263b75b2a98a7218dd5a0a8aaa7
2.8.4-1ubuntu1
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages)
(/var/lib/dpkg/status)
Description Language:
File:
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages
MD5: 5d223263b75b2a98a7218dd5a0a8aaa7
The latest 2.8.4-1ubuntu1.3 package fails in both cases, while the older
2.8.4-1ubuntu1 package works in both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727220
Title:
Command "fuse" returned error 1 (with TrueCrypt)
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
