Problem: After the recent system update one day ago, Vivaldi and Brave are not receiving certain keyboard inputs when run through Firejail. What works is Ctrl + Tab to open a new tab. What doesn't work are keyboard entries into the F6/F8 URL address bar, Ctrl + F12 (settings) or Ctrl + Q (Quit) for example.
For years I run all browsers through Firejail like this:
firejail --noprofile --caps.drop=all --nonewprivs vivaldi-stable
The --nonewprivs
option is just in place because --seccomp
throws up an error.
In the case of Firefox I do use a more restricting profile instead of the --noprofile
option and everything does still work. Falkon Browser (KDE) works fine with the line above. Ungoogled-Chromium via Flatpak works fine.
When I run Vivaldi without --caps.drop=all --nonewprivs
the errors would be:
[39:39:0424/170924.501957:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2:2:0424/170926.192789:ERROR:CONSOLE(1)] "syncDetachedTabInformation: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/bundle.js (1)
Question 1: What could prevent keystrokes to properly reach the browser windows of Vivaldi and Brave, while it did work fine before the update. I suspect it has something to do with input methods somehow having been changed?
Another thing I've noticed that was changed since the recent update is the way Ctrl+Shift+U and a number to use Unicode symbols/smileys/superscript etc. are interpreted. The old input method required to press all buttons simultaneously and then add the four letter number at the end to get the symbol. Now it's much more user-friendly with a 'mode switch' to the u being stored and now being able to add the number without holding down all the keys at the same time.
Question 2: what exactly caused such a change? Is it that the update reset parts of the Budgie Desktop Settings / Keyboard to certain defaults which changed the input method? Or is it a part of the DE or within Gnome? What exactly?
Another thing I've noticed that bugged me after the update is how much CPU the process 'budgie-wm' seems to use by simply moving the mousepointer and having no programmes started at all. It would go from 0,1 to 0,3% to about 22-25% on all four threads by moving the mouse pointer from left to right.
To escape all of this for the time being I tried to simply revert to the last working version before the update via sudo eopkg hs -t 1015
but it causes this error:
Downloading 2 / 91
Package colord found in repository Solus
colord-1.4.5-19-1-x86_64.eopkg [cached]
Downloading 3 / 91
System error. Program terminated.
<type 'exceptions.Exception'>: Repo item python-urlgrabber not found
Question 3: How do I properly revert? I know usually the best is to move forward, but this update broke too many things for me. How do I find out what applications did use python-urlgrabber and potentially remove them, as I may not need them.