-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
Can't open files anymore? #970
Comments
What platform are you running it on (linux, macos)? How was it installed (snap, brew, …)? Can you try running it with |
Sorry for the lack of info. I am using Ubuntu 20.04 (server, SSH access), Running |
Snap restricts access to files only inside the user's home directory by default IIRC. Are you trying to open files from somewhere else maybe? |
I am. This makes sense. Just installed v0.8.5 via the official repos and it runs exactly as expcted now. I guess we solved it. I assume there's no workaround for the Snap package? |
What connections are setup for your snap install, here's what I see on an Ubuntu 21.10 vagrant machine:
The solution is mostly likely asking for "classic" confinement for the snap. But, I haven't cared to do that. There are binaries attached to releases, you could try that way -- https://github.com/tstack/lnav/releases/tag/v0.10.1 |
Thanks. I'm probably gonna slap together a bash install script for the binaries, for future use. |
|
lnav version
v0.10.1
Describe the bug
I used to simply supply a file path to
lnav
and then I could do what I needed. These days I can only open syslogs... Is this intentional? I've been ripping my hair out trying to figure out what's going on.To Reproduce
Run
lnav [path to any plaintext file]
returns what looks like a basic manpage, not a running instance oflnav
with the supplied file loaded.The text was updated successfully, but these errors were encountered: