[Desktop-packages] [Bug 1701424] Re: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção.
*** This bug is a duplicate of bug 1706204 *** https://bugs.launchpad.net/bugs/1706204 ** This bug has been marked a duplicate of bug 1706204 package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to blt in Ubuntu. https://bugs.launchpad.net/bugs/1701424 Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. Status in blt package in Ubuntu: New Bug description: I can't install anything on my terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tk8.6-blt2.5 2.5.3+dfsg-3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 23:34:39 2017 DpkgTerminalLog: dpkg: erro ao processar o pacote tk8.6-blt2.5 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-04-13 (77 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: blt Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blt/+bug/1701424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Package changed: fuse (Debian) => fuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/254171 Title: Nautilus can't properly unmount FUSE file systems Status in FUSE: Fix Released Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/fuse/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
According to https://github.com/karelzak/util-linux/pull/705, this issue seems to have been fixed natively in mount/libmount1 from util-linux (since version 2.34). So it should work with Ubuntu 20.04 LTS (focal fossal) and newer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in fuse package in Debian: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Bug watch added: github.com/libfuse/libfuse/issues #246 https://github.com/libfuse/libfuse/issues/246 ** Also affects: fuse (Debian) via https://github.com/libfuse/libfuse/issues/246 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in fuse package in Debian: Unknown Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #133 https://gitlab.gnome.org/GNOME/gvfs/-/issues/133 ** Changed in: nautilus Importance: Medium => Unknown ** Changed in: nautilus Status: Confirmed => Unknown ** Changed in: nautilus Remote watch: GNOME Bug Tracker #607706 => gitlab.gnome.org/GNOME/gvfs/-/issues #133 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
