F
frankvw2019
Guest
I realize this is more a snap issue than a Picard issue but it’s a real problem for me and it drives me crazy.
As per the official snap philosophy that a snap application may not have access to anything that doesn’t live in the user’s home directory or possibly a USB stick, I can’t get my freshly installed Picard to access things like /data and /data2 (where I have my ecrypted data filesystems mounted). Very secure - I can’t access any of my music!
If it were up to me I’d just prefer to give all my snap applications full rootfs access, but that’s not possible without doing really ugly things (the software equivalent to ramming a crowbar into the works) so I’ll settle for any way to give Picard access to /data and /data2. How do I do that?
2 posts - 2 participants
Read full topic
Continue reading...
As per the official snap philosophy that a snap application may not have access to anything that doesn’t live in the user’s home directory or possibly a USB stick, I can’t get my freshly installed Picard to access things like /data and /data2 (where I have my ecrypted data filesystems mounted). Very secure - I can’t access any of my music!
If it were up to me I’d just prefer to give all my snap applications full rootfs access, but that’s not possible without doing really ugly things (the software equivalent to ramming a crowbar into the works) so I’ll settle for any way to give Picard access to /data and /data2. How do I do that?
2 posts - 2 participants
Read full topic
Continue reading...