The problem with this being broken is that we do have users that use OMLx in VirtualBox and we have in the past stated publicly that we support this. Latest chromium-browser-stable-102.0.5005.115-1 in Cooker/main and Rolling/main/testing repos seems to be broken in VirtualBox. This is the Konsole output from Cooker VirtualBox VM:
Cooker-vbox-chromium-browser-stable.txt (8.9 KB)
Cooker and Rolling/testing users should know what to do in this situation.
Can’t confirm. Works fine for me on bare metal cooker box.
More info: I should have mentioned that my chromium-browser-stable are in VirtualBox VM’s. On hardware I normally use google-chrome-stable. So I just installed chromium-browser-stable on Cooker and Rolling hardware systems and it is indeed working.
The Konsole output looks horrible whether chromium-browser-stable is working or not working. For sake of curiosity here is Konsole output from Cooker hw system:
Cooker-hw-chromium-browser-stable.txt (7.5 KB)
Edit: Changed title and first post to reflect this issue is specific to VirtualBox.
Problem in VirtualBox persists with chromium-browser-stable-103.0.5060.53-1. Konsole output looks about the same:
chromium-stable.txt (9.1 KB)
Edit: I do not necessarily assume this is a problem with chromium-browser-stable package, it could be something else. Am using OM virtualbox-6.1.32-1 in Rock/4.3. I have not filed a bug report because I would like to see a new working version of VBox in Cooker first in case that is the problem.