On Tue, Apr 21, 2020 at 05:24:08PM +0200, Erazem Kokot wrote: > > If that doesn't help either, can you show your ":open qute://configdiff" > > please? Often, one of the content.* settings is the offender ;-) > > https://pastebin.com/ubLey68W
Nothing looks suspicious there. > I've tested removing the blocklists and globally enabling Javascript, > but neither worked. > I also moved the qutebrowser config directory, so the browser used its > default settings, but that didn't work either. > > Is there anything else that --temp-basedir changes/removes? There's ~/.local/share/qutebrowser with things like cookies and such. Florian -- [email protected] (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
