Yes please. If your snap is creating and reading it, any chance the file name can contain the snap name and thus it is clear that the snap owns it?
Ok! let us know whenever that happens so we drop the granted privileges.
I am not quite sure if I am properly understanding this comment, but yes please, make the required changes and upload a new revision so we can move fw with the request.
@ogra Can you please support ? As now we found an issue with the snap that when we add personal files like - $HOME/.local/share/data/bconf/data.conf"- then it wont read or write the file, but when we just remove the file name and keep - $HOME/.local/share/data/bconf - then it works fine and read and write the personal files well and snap works fine.
Hey there
Can anyone please help me out in this issue?
yaml -
dot-local-share-bconf:
interface: personal-files
write:
- $HOME/.local/share/data/bconf/data.conf ```
if we read and write directory then it works perfectly but when read and write specific file it doesnot work.
For other solution we are trying to drop personal-files interface and try to write in $HOME(non-hidden files) for the directory but it doesnot work it says that no access to write file in directory.
May we get the directory path for $HOME which has writable access and easy accessible for users.
we have tried below...
``` $HOME/$USER/Documents/MqttDesk/share/data/bconf
/home/$USER/Documents/MqttDesk/share/data/bconf
/home/$USER/$SNAP/MqttDesk/share/data/bconf ```
@emitorino Iam sorry for that.
Let me explain it again.
there is issue when we read & write $HOME/.local/share/data/bconf/data.conf
so we are trying to drop the dot files access for snap.
We need help into the right absolute path for HOME -plug interface where we can keep the file and read & write from that directory path. As we are trying to access the multiple different paths but getting no permission to write access errors .
Can you please suggest the right absolute path which does have write access to home -plug?
Actually , we have succeeded in that for the dot files plug interface, but issues is that we are using one more file into same directory for licencing usage and we have to include that file too with personal-file plug interface. We have tried snappy-debug too and received the same information .
Atlast we would upload the snap in few minutes again for review.
System files - Auto connections/read
1./sys/devices/virtual/dmi/id/bios_vendor
2./sys/devices/virtual/dmi/id/product_serial
3./sys/devices/virtual/dmi/id/product_name
Hi @newbee_snap - so there are a couple simplifications I think you can make - for the personal-files instance, you could just declare a single write location of the directory as follows:
Which will then allow you to write whichever files you require within this directory as in this case.
However, as mqttdesk is not the clear owner of this path (ie there is no mqttdesk path component here) +1 from me for use of this personal-files instance as I have declared it above, BUT not for auto-connect of this. If instead this could be located within a path such as ~/.local/share/mqttdesk/data/bconf or similar then I think it would be appropriate for this to be auto-connected.
Regarding the system-files instances, +1 from me for auto-connect and use of these paths for mqttdesk.
Can you please update the snap yaml to make this change to combine the two personal-files instances down to a single one as above? And can other @reviewers please vote too? Thanks.
Please find the below updated snap yaml & we have dropped the request for personal-files, so we dont need personal-files permission.
We need below interface requested for snap. Please review them .
System files & Hardware-observe- Auto connections/read
1./sys/devices/virtual/dmi/id/bios_vendor
2./sys/devices/virtual/dmi/id/product_serial
3./sys/devices/virtual/dmi/id/product_name
4.Hardware observe- Auto connections/read
@newbee_snap sorry for all the back-and-forth - can you please just make one more adjustment? Please remove the read- prefix on the names for these system-files instances?
Once this is done, +1 from me for use-of and auto-connect of these 3 system-files instances, plus auto-connect of hardware-observe as well for mqttdesk.
Can anyone please look into it for approval?
Iam struggling to get approve for store for many days. I know there may be many request for reviews and permissions.
Please look into this.
Apologize for the delay. I went ahead and checked your snap latest revision, and I dont see what’s being discussed here already applied. Can you please upload a new revision, including all changes requested so we can move fw with granting the accesses required?
My votes for the process are: +1 for use of the personal-files interface (but not for auto-connect since the snap is not the clear owner of such dir).+1 for use and auto-connect of the 3 system-files instances requested. +1 for auto-connect of hardware-observe
App upload has been done and as discussed above to @alexmurray that personal files interface has been dropped and only system-files 3 instances & hardware-observe has been used and need to allow for those only. Thanks