-
Notifications
You must be signed in to change notification settings - Fork 172
Description
There is an annoying bug or "bug" in Chromium: issues.chromium.org/issues/371926650 that manifests when WaveDrom runs on linux.
When WaveDrom starts, it (chromium) opens a series of popups demanding user to unlock all their keyrings.
Solution: for some platforms this behavior can be supressed by adding --password-store=basic to the argument list.
Note that as per report above adding this not necessarily resolve this behavior on all Linux platforms, but on some it should.
I'd also add, that if user has set the autologin feature at their desktop, or provided credentials to the unlock popup, all user credentials stored at .local/share/keyrings/ possibbly could be accessible from this very Chromium instance. On linux distros with permissive SE policies it makes for a de-facto root access. Ostensibly needed to use GPU acceleration. I am not sure of the accuracy and severity of the above: take it as my impression from skimming the past year CVEs for Chromium.
./wavedrom-editor
[0828/011131.623359:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0828/011131.623976:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[249165:249165:0828/011132.169508:ERROR:network_service_instance_impl.cc(613)] Network service crashed, restarting service.
[249165:249165:0828/011135.657207:ERROR:secret_portal_key_provider.cc(200)] Keyring unlock cancelled: 2
[249529:249529:0828/011431.678102:ERROR:gpu_blocklist.cc(71)] Unable to get gpu adapter
[249165:249165:0828/011431.678346:ERROR:service_client.cc(36)] Unexpected on_device_model service disconnect: The device's GPU is not supported.