Recently a bug has appeared when I am using mullvad browser. It causes my panel to crash/disappear and I get a popup saying panel has crashed too many times, auto restart has been disabled until next login.
Might be a Mullvad Browser bug. If you boot into sysmaint mode and run sudo journalctl | grep 'segfault', do you see crashes attributed to lxqt-panel? If so, can you share the output lines here?
No, only one in libQt6Core.
That library is used by lxqt-panel. Can you share the output line?
localhost kernel: UITgreadWorker[5582]: segfault at 20 ip 0000722d0ede44eb sp 0000722ce7ffe880 error 4 in libQt6Core.so.6.8.2[1e44eb,72dp0eccd000+346000] likely on CPU 1 (core 1, socket 0)
The panel has crashed due to browser multiple times not just once as displayed in this log. I am not able to remember if I was experiencing a panel crash on the time this was logged.
Hmm, that crash looks unrelated. I installed Mullvad Browser on a freshly instaleld, fully updated Kicksecure VirtualBox VM, and cannot immediately reproduce the crash. Does it happen frequently or rarely?
1 Like
I am not on a VM. It happens consistently after using the browser for about five minutes. Began about two weeks ago. I have the same bug on system detailed in thread you solved earlier about Qterminal/Brave. Could that be causing this?
I don’t think that’s the same bug. That bug was caused by inappropriate fontconfig cache symlinks being created by Chromium, and I don’t see any symlinks in ~/.cache/fontconfig on my end after running Mullvad Browser.
I tried to reproduce again by browsing with Mullvad for a little over five minutes and still didn’t manage to make it happen. It’s possible the issue only occurs when graphics acceleration is enabled. Could you try forcing software rendering by following the instructions here:
(Note that these instructions are in with the NVIDIA documentation since that’s when they are usually needed, but they can mostly be used even if you aren’t using NVIDIA graphics. You can omit the Nouveau-related steps if you aren’t using NVIDIA hardware.)
This is most likely a Mullvad Browser bug, so I would suggest discussing on their forums if they have forums. I probably won’t spend much more time debugging this since it doesn’t appear to be a Kicksecure bug.