Computers are so fucking weird.

[swelljoe@mas.to]

Computers are so fucking weird. Every day there's some new thing. Chromium on Linux (Fedora 43) is in some kind of sandbox, so I can't open local files, but only some of them? All of the directories that were created by the desktop (Documents, Downloads, Music, Videos, Pictures, etc.) are accessible, as well as a few hidden directories (.local, .nv, .pki, .var), but nothing else is. I can't even type it in explicitly and fully, it's a 404.

Firefox _can_ reach all files my user has access to.

[swelljoe@mas.to]

Also, I keep killing my editors (Zed and VS Code) trying to open a 32MB file with exactly one really long line of JSON. This doesn't seem like it ought to be "big" to any modern editor on a modern computer with 64GB of RAM, but here we are. jq can pretty print it without any trouble, so I could make a copy that's pre-parsed into individual lines, but it doesn't seem like I ought to have to massage text to even be able to load it.

Back to old reliable Neovim, with `:%!jq .` to format it.

[jumile@mas.to]

@swelljoe That file access problem sounds like the classic sandboxed package issue. Can't recall if it's Snap or AppImage that does it, though.*

Whichever one it is, there's an arcane command - or a GUI/TUI - that can change the access settings for individual packages.

*Sorry, it's been so long since I've used either package type that my memory is rusty. Both make me nope out. 😅

[swelljoe@mas.to]

@jumile yeah, I avoid Snaps and Flatpaks for this reason, among others (though Snap is worse than Flatpak, in my experience...maybe because the packagers are sloppier or maybe because Flatpak has better tools for making sure things are sane).

And, because I avoid Snaps and Flatpaks (and AppImages), Chromium is installed from an RPM. So, that is a very good guess, but not the case here.