tiger reports problem with securityfs (not recognized as a local filesystem)

Bug #155211 reported by François Marier
8
Affects Status Importance Assigned to Milestone
tiger (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: tiger

Tiger reports the following information:

  --CONFIG-- [con010c] Filesystem securityfs used by securityfs is not recognised as a local filesystem

The fix is to add this line around line 100:

  [ "$1" = "securityfs" ] && LOCAL=0

A similar problem was described here:

  http://<email address hidden>/msg00006.html

This affects the version of tiger in gutsy.

Changed in tiger:
status: New → Confirmed
Revision history for this message
François Marier (fmarier) wrote :

Note that you are constantly emailed (at least once at day) about this until you add the line above to the /usr/lib/tiger/systems/Linux/2/gen_mounts file.

Revision history for this message
François Marier (fmarier) wrote : Hardy update

This problem persists on hardy and in fact, hardy introduces a new unrecognized filesystem:

  fuse.gvfs-fuse-daemon

which needs to be added to the same file.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Revision history for this message
Brinley Ang (brinley) wrote :

Confirming same issue on gutsy also the fix mentioned above resolved the problem for me

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Fixed in 1:3.2.2-6ubuntu1.

Changed in tiger:
importance: Undecided → Medium
status: Confirmed → Fix Released
Revision history for this message
Pablo Hörtner (redtux2000) wrote :

this is also an issue when binding an existing mount to another mountpoint, e.g.:
--CONFIG-- [con010c] Filesystem 'bind' used by '/var/run/saslauthd' is not recognised as a local filesystem

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.