Crash when loading some tabs on VNC server host
Since the Firefox 99 update loading some pages (for example, the Gmail sign-in page) using Firefox on my Linux Mint machine, that I'm running a VNC remote desktop session on, results in a crash.
Crash report ID: bp-5dc1e89d-dc1f-40f2-9dbe-7f4380220419
I've tried running Firefox in safe-mode and the crash doesn't happen, but turning off hardware acceleration, swapping to default themes, removing all extensions, and completely removing Firefox and the .mozilla folder and then re-installing Firefox have not changed the crash behaviour in the absence of the safe-mode flag.
I would appreciate help in identifying what other paths of investigation I can take.
Chosen solution
This seems to have been a problem with the way that the vncserver was configured to startup, probably something to do with missing a step that provided environment settings for the X Window System. I'm not entirely sure exactly what the problem was however because I overcame it by switching from tightvncserver to tigervncserver as my VNC server package, which uses a different default configuration which worked out of the box for me.
Read this answer in context 👍 0All Replies (3)
Try downloading another copy of Firefox, run it from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Are you running X11 or Wayland? What desktop?
Operating System: openSUSE Tumbleweed 20220414
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.2-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600
Modified by jonzn4SUSE
Fresh download of Firefox extracted and run from the resulting folder shows the same behaviour, crashing when the Gmail sign-in page is loaded (bp-aabe826b-5b23-43d0-b04d-315fd0220419).
I'm running X11 using the mate desktop (~/.vnc/xstartup calls mate-session which is at version 1.24.0).
Chosen Solution
This seems to have been a problem with the way that the vncserver was configured to startup, probably something to do with missing a step that provided environment settings for the X Window System. I'm not entirely sure exactly what the problem was however because I overcame it by switching from tightvncserver to tigervncserver as my VNC server package, which uses a different default configuration which worked out of the box for me.