uninstalling fuse-utils removes group 'fuse' then tries to use it
Bug #5774 reported by
Chris Moore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fuse (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
fuse-utils.prerm does this:
delgroup $FUSE_GROUP || true
and then
fuse-utils.postrm tries to do this:
dpkg-statoverride --remove /usr/bin/fusermount 2>/dev/null || true
but since group 'fuse' has already been deleted, the dpkg-statoverride fails.
This results in an old statoverride being left in place for group 'fuse' without the group existing, which causes all subsequent dpkg invokations, whether for fuse or for any other package, to fail.
This happened for me once today, but after manually removing the statoverride I couldn't get it to happen again. Installing fuse-utils no longer created the 'fuse' group - I'm not sure why.
Changed in fuse: | |
assignee: | nobody → pitti |
Changed in fuse: | |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
I can confirm it. It is fixed in Debian's package fuse-utils 2.5.2-2 and it fixes bugs #307627, #342826, #310964, #306281 and #307624.
It would be nice to have an update to fuse-utils so that Dapper has a fuse subsystem that actually works ;-). My apologies to suggest it after feature freeze; but didn't need to use it before.