Hi, On Sat, Dec 07, 2019 at 08:24:02PM +0000, n...@nexnode.net wrote: > I have (only just) noticed that I can no longer use luakit, as it > appears to not function any longer. > I have made sure to try without any pre-existing configuration, a > clean reinstall, and my observation has been seconded by someone else > on IRC.
The bug is known but currently unfixed upstream, https://github.com/luakit/luakit/issues/804. I had hoped that reverting to single-process webkit could resolve the problem, but alas, it doesn't, http://bugs.debian.org/945509. So, while disbling adblock will probably fix the empty page thing, you'll still have excessive CPU usage, which I find unacceptable. Since I can't live without luakit and only allow javascript on more or less trusted sites, I went for downgrading webkit. Personally, I just restored /usr/lib/<arch>/(libwebkit2gtk-4.0.so.37.37.6,libjavascriptcoregtk-4.0.so.18.13.7,webkit2gtk-4.0/) from a backup, removed the corresponding libraries coming from the current package and ran ldconfig, which unsurprisingly fixes things. A less hacky way would be to add something like http://snapshot.debian.org/archive/debian/20191015T025215Z/ stable main to /etc/apt/sources.list and downgrade webkit, probably pinning it for the time being. That's certainly no permanent solution but, as long as you're aware of the security implications and control which javascript you accept, I guess it's acceptable. I'll backport the upstream fix (presumably as a new version for backports) when it becomes available. -- Markus
