-
Notifications
You must be signed in to change notification settings - Fork 46
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
Share folders on external storage with user groups doesn't work #1161
Comments
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
Hello @SchVinzenz |
Hello @marcelklehr, thanks for your answer. |
Which version of recognize are you using?
7.1.0
Enabled Modes
Object recognition, Face recognition, Video recognition, Music recognition
TensorFlow mode
Normal mode, GPU mode
Downstream App
other, please specify below
Which Nextcloud version do you have installed?
Nextcloud Hub 8 (29.0.4)
Which Operating system do you have installed?
Ubuntu Server 24.04
Which database are you running Nextcloud on?
MariaDB 10.11.8
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
40GiB (VM)
What processor Architecture does your CPU have?
x86_64 (TrueNas VM)
Describe the Bug
If I have installed the "Recognition" app and want to share an external storage with a user group using the share function, this does not work. The share is displayed and the users in the group receive a notification that a folder has been shared with them, but they cannot open it (folder not found).
As soon as I deactivate the Recognition app, I can share the folder without any problems and it is displayed for all users.
Expected Behavior
If I share a folder on an external storage, it should be displayed for the user. If the Recognition app is activated, the user receives a notification that a folder has been shared with them, but they cannot view it.
To Reproduce
--
Debug log
No response
The text was updated successfully, but these errors were encountered: