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

Running lnav with snap cannot access files in /etc/ or /usr #1166

Closed
jay-sridharan opened this issue Jun 21, 2023 · 3 comments
Closed

Running lnav with snap cannot access files in /etc/ or /usr #1166

jay-sridharan opened this issue Jun 21, 2023 · 3 comments
Labels

Comments

@jay-sridharan
Copy link

lnav version
v0.11.1 is the latest

Describe the bug
Custom formats are not read from /etc/ or /usr/ because the snap is running in strictly confined mode.

To Reproduce
Steps to reproduce the behavior:

  • Install lnav through sudo snap install lnav
  • Add a custom format to /etc/lnav/formats/new-format/new-format.json
  • Run lnav -d debug.log <random_file>
  • Note that new-format.json is not loaded.

This is because the system-files interface is not used in the snapcraft.yaml. Something like this

plugs:
  etc-lnav:
    interface: system-files
    read:
    - /etc/lnav

Alternatively, the confinement should be changed to classic so that the package has access to system files.

@piotr-dobrogost
Copy link
Sponsor

Previous issues where classic confinement was mentioned: #970, #525

@tstack
Copy link
Owner

tstack commented Jun 25, 2023

I've added the plug as you mentioned, but it seems to need a manual review, which they are taking their time doing...

@tstack
Copy link
Owner

tstack commented Jul 1, 2023

The request was approved, so I think this should work now.

@tstack tstack closed this as completed Jul 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants