I've had this problem for a while, since about two updates ago, but I've just worked around it. I thought maybe now, with the latest version 8.15 out, might be a good time to fix it. I am also using Racket a lot more than I used to
Basically, whenever I try to access the docs from within Racket, the browser simply refuses to display them, saying that they are not readable. Which is strange, because if I open the *.html files in any text editor, they seem perfectly readable to me! I have taken to putting the online link to the docs on my browser's menu bar, so I'm not completely lost, but I do consider this a pretty suboptimal arrangement.
Any ideas?
Using Racket 8.6 under Ubuntu 22.04 Jammy.
Racket is not on my 'Snap' list, so I guess I never installed it that way. Can't remember how I installed it anyway. Maybe script, more likely apt, but no idea really.
If I deinstall everything and install afresh would I be alright? Any preferred procedure?
Jeez, inspired by your question, I tried copying the doc directory from .racket to a different place in the home directory, and from there it works fine! Just what are these browsers up to? Seems ridiculous.
How can I change my Racket settings to point to a different directory now?
Seems like so much senseless hassle...
OK, I see, the problem is not the browsers per se, but the snap installation that does not allow them access to "invisible" directories. Yegads.
I'll have to think about that. Seriously not liking snap ATM.
=====
Anyway, I have loads of other programs installed under snap (emacs, kate, julia, many utilities, etc) and none of them have any problem opening .xxxx directories or files.
Ho-hum, very boring.
IIUC it has none of the app sandbox restrictions of the Snap.
After the initial install, the update experience is similar to Windows or macOS: Periodically, Firefox itself will tell you it can be updated, and do that for you.
Caveat: I haven't yet tried this myself. Because I haven't yet had problems with the Flatpak builds of Firefox on Debian or Fedora. (And if I did, Flatpak lets you easily tweak app sandbox permissions -- more so than Snap, although Snap might have improved in this regard since I last checked c. a year ago, idk.)
That's probably what I'll do, seems the quickest/neatest.
I'm still wondering about the 'sandbox' thing, though, as I said most of my Snap-installed programs have absolutely no problem reading (and writing) 'dot' directories and files. Why should they? We have permissions for that very purpose. Is it just a browser issue? Hijacking permissions seems rather cavalier.
