Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto tagging is broken #39

Open
traverseda opened this issue Oct 1, 2017 · 2 comments
Open

Auto tagging is broken #39

traverseda opened this issue Oct 1, 2017 · 2 comments

Comments

@traverseda
Copy link

traverseda commented Oct 1, 2017

Tagsistant (tagfs) v.0.8.1a (codename: Berlin)
Build: 565.20141118.000022 FUSE_USE_VERSION: 26
FUSE library version: 2.9.7
fusermount version: 2.9.7
using FUSE kernel interface version 7.19

extract v1.4

Tried tagsistant out with my music library. Although everything I tried is recognized by vlc/easytag/etc, it only worked on one of my test files. A floss file that included a cover picture field, containing 200000 bytes of miscellaneous image data. Tagsistant proceeded to freak out, added a bunch of new stuff to the file: namespace, and crash. This is especially concerning since the default setup recommends you run as root!

On subsequent re-runs I added only one sample file at a time, and it didn't crash. I'm not sure exactly what caused that crash.

I will note that the mediainfo command/library works on all the media I tried it with, and is presumably what everyone else is using.

You should probably remove auto-tagging from the list of features if it only works under very-specific circumstances. You should also definitely update the instructions to not have it run as root by default.

@StrumentiResistenti
Copy link
Owner

Hi, where did you got the information that running as root is the recommended setup? The recommended setup is the exact opposite, but FUSE must be first configured to allow filesystem mounting by non-root users. However that's a FUSE related issue that holds for every filesystem developed on top of FUSE. If I left some misleading information on the guide about running as root, please point me to it and I'll fix it.

Usually auto tagging is not as broken as you experienced. Having a more detailed log of what happened on your files could help me focusing the bug. Could you please post an excerpt of your logs, grepping tagsistant rows only? Thank you.

@zkol
Copy link

zkol commented Jul 10, 2020

I guess the misconception about root can easily happen if one start with trying out the samples on the landing page (and not the ones from the 0.8.1 manual) as non-root user as I did first.

The role of root for automount is mentioned on page 2 of the manual and in one question of the FAQ. But if the misconception is still established using /etc/fstab and automount as root might be seen as option and not as recommendation.

Beside the answer in this issue it is mainly the title of the FAQ entry ("Why I need to be root to use Tagsistant?") that sounds like a recommendation of mounting as root. But the answer says that it is not needed and lists no restrictions of not being root.

After reading all of this and trying to install tagsistant (which failed for me) I am still not sure: Are there any known issues/restrictions/bugs that are associated with trying to mount a tagsistant repo as non-root user?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants