qt5-webengine crashing after mesa update

megapink · 2021-12-21 20:49:45

Basically, qutebrowser starts, but trying to open a new page or closing an existing one crashes it.

Please, see the logs and details here, but let me know if I can provide something else:

https://github.com/qutebrowser/qutebrowser/issues/6903

The maintainer has suggested this is a graphics driver problem, so I have uninstalled xf86-video-intel and xf86-video-vesa and rebooted, but that didn't do anything.

I am using stumpwm for my window manager, no DE's installed.

Suggestions, please?

Last edited by megapink (2021-12-21 21:34:24)

jasonwryan · 2021-12-21 21:03:19

Which intel card? Can you post an xorg.log from a crashed session?

Trilby · 2021-12-21 21:10:00

And what was updated? I don't believe qutebrowser has had an update real recently - mesa was updated today though. Does (temporarily, for testing) downgrading mesa help?

megapink · 2021-12-21 21:22:29

jasonwryan wrote:

Which intel card? Can you post an xorg.log from a crashed session?

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])

ehh, it's a dell e6410, I think the exact model is something like intel GMA ..., I guess I will reboot to bios and check if the above is insufficient.

Here's the log https://pastebin.com/J6Q8u4AC
but please note that it's not Xorg crashing, only qutebrowser.

megapink · 2021-12-21 21:24:24

Trilby wrote:

And what was updated? I don't believe qutebrowser has had an update real recently - mesa was updated today though. Does (temporarily, for testing) downgrading mesa help?

I haven't done a full system upgrade in a few months before yesterday. But downgrading mesa does help!

downgrading package mesa (21.3.1-1 => 21.2.1-1)

megapink · 2021-12-21 21:26:31

So now do I report this to mesa bugtracker?

Trilby · 2021-12-21 21:29:16

That narrows down the problem at least. You may want to update your thread title as this occurs with multiple browsers and is specific to a new version of mesa.

That said, both browser are qt5-webengine which interacts with mesa on intel cards in all sorts of horrible ways. If you wanted you could try weaver browser (in AUR) to see if qt6-webengine fares any better. This may help determine whether this is specifically a qt5-webengine / mesa interaction issue. Disclosure: I'm the author of weaver ... I'd say try any qt6-webengine browser, but I don't know of any others yet.

EDIT: FWIW bugs resulting from qt5-webengine's poor graphics memory handling have never been handled by mesa, but always assigned to the qt5 people ... who mostly ignore them. So I don't think a bug report against mesa would be warranted yet, and I'm more confident that it'd not likely be productive.

Last edited by Trilby (2021-12-21 21:31:06)

megapink · 2021-12-21 21:58:55

Trilby wrote:

That narrows down the problem at least. You may want to update your thread title as this occurs with multiple browsers and is specific to a new version of mesa.
That said, both browser are qt5-webengine which interacts with mesa on intel cards in all sorts of horrible ways. If you wanted you could try weaver browser (in AUR) to see if qt6-webengine fares any better. This may help determine whether this is specifically a qt5-webengine / mesa interaction issue. Disclosure: I'm the author of weaver ... I'd say try any qt6-webengine browser, but I don't know of any others yet.
EDIT: FWIW bugs resulting from qt5-webengine's poor graphics memory handling have never been handled by mesa, but always assigned to the qt5 people ... who mostly ignore them. So I don't think a bug report against mesa would be warranted yet, and I'm more confident that it'd not likely be productive.

Well, I have installed weaver. It seemed to run OK. Then I upgraded mesa to the new version. Trying to launch weaver did nothing, no error no anything.

I though I would reboot just to be sure... and I get "Dependency failed for /home". Dependency failed for Local File Systems.

I can give root password for maintenance, so yeah, nothing mounts to /home now.

Dang, bruh, I just hope I didn't lose my home, that would suck.

I did pacman -Rs weaver-fossil, rebooted and same thing. But that wouldn't be something in the pkgbuild would it that would cause it?

I guess I will go get those journalctl logs on a flashdrive and upload it soon.

once · 2021-12-21 22:00:19

mesa-21.3.2 updated few days ago.

jasonwryan · 2021-12-21 22:01:22

The dependency failure for local filesystems sounds like an umnounted /boot for a kernel upgrade. From a chroot, compare `pacman -Q linux-lts` and `uname -r`

megapink · 2021-12-21 22:09:27

jasonwryan wrote:

The dependency failure for local filesystems sounds like an umnounted /boot for a kernel upgrade. From a chroot, compare `pacman -Q linux-lts` and `uname -r`

The output is the same, linux-lts 4.19.14-1. I failed to mention that I have been running that kernel for a while (I have told pacman to ignore linux and linux-lts packages), because youtube videos would cause kernel panic on the newer kernels. Now that I think of it, it could have something to do with mesa crashing qt5, huh.

I tried booting linux, which happens to be linux 5.10.11.arch1-1 - both commands, too, yield the same output.

Last edited by megapink (2021-12-21 22:11:15)

jasonwryan · 2021-12-21 22:11:52

megapink wrote:

I tried booting linux, which happens to be linux 5.10.11.arch1-1 - both commands, too, yield the same output.

Are you doing partial updates? The current vanilla kernel is 5.15.10.

megapink · 2021-12-21 22:13:28

jasonwryan wrote:

megapink wrote:
I tried booting linux, which happens to be linux 5.10.11.arch1-1 - both commands, too, yield the same output.
Are you doing partial updates? The current vanilla kernel is 5.15.10.

Yes, I've told pacman to ignore linux-lts and linux packages (and headers I think too). But I have been running only the lts version so far.

Last edited by megapink (2021-12-21 22:13:55)

megapink · 2021-12-21 22:30:43

So here's journalctl -xs output: https://pastebin.com/nZCKXf2q

I can mount my home by hand, the data is all there, so that's good.

megapink · 2021-12-21 23:35:07

I have missed the glaring "Failed to start file system check", did fsck and now I am back in business!

Trilby · 2021-12-22 00:44:46

megapink wrote:

Well, I have installed weaver. It seemed to run OK. Then I upgraded mesa to the new version. Trying to launch weaver did nothing, no error no anything.

Did you pass it a url on the command line? If not, it will exit silently. Alternatively is there another core dump listed by `coredumpctl list` for weaver when it did nothing?

Last edited by Trilby (2021-12-22 00:46:22)

megapink · 2021-12-22 10:46:41

Trilby wrote:

megapink wrote:
Well, I have installed weaver. It seemed to run OK. Then I upgraded mesa to the new version. Trying to launch weaver did nothing, no error no anything.
Did you pass it a url on the command line? If not, it will exit silently. Alternatively is there another core dump listed by `coredumpctl list` for weaver when it did nothing?

Oh, I see, OK. So yeah, it turns out both work (I can actually browse pages), but with the later mesa, weaver segfaults on close.

Here's the dump:

https://drive.google.com/file/d/13ATysz … sp=sharing

And here's the info:

https://pastebin.com/E2E0XiF6

dogknowsnx · 2021-12-23 15:15:15

Some Intel related regressions have been introduced with mesa 21.3 and are being worked on (the 'iris' driver has still to be fixed afaik).

Downgrading mesa to 21.2.5 or explicitely calling the 'i965' driver 'solves' the issue (flickering) for me (Intel HD 620)...

megapink · 2021-12-24 10:57:45

dogknowsnx wrote:

Some Intel related regressions have been introduced with mesa 21.3 and are being worked on (the 'iris' driver has still to be fixed afaik).
Downgrading mesa to 21.2.5 or explicitely calling the 'i965' driver 'solves' the issue (flickering) for me (Intel HD 620)...

Cool, thanks for the info!

Demon · 2022-01-06 13:29:05

Thanks for this! I downgraded mesa to 21.2.5 and web page flickering went away!

Arch Linux

#1 2021-12-21 20:49:45

qt5-webengine crashing after mesa update

#2 2021-12-21 21:03:19

Re: qt5-webengine crashing after mesa update

#3 2021-12-21 21:10:00

Re: qt5-webengine crashing after mesa update

#4 2021-12-21 21:22:29

Re: qt5-webengine crashing after mesa update

#5 2021-12-21 21:24:24

Re: qt5-webengine crashing after mesa update

#6 2021-12-21 21:26:31

Re: qt5-webengine crashing after mesa update

#7 2021-12-21 21:29:16

Re: qt5-webengine crashing after mesa update

#8 2021-12-21 21:58:55

Re: qt5-webengine crashing after mesa update

#9 2021-12-21 22:00:19

Re: qt5-webengine crashing after mesa update

#10 2021-12-21 22:01:22

Re: qt5-webengine crashing after mesa update

#11 2021-12-21 22:09:27

Re: qt5-webengine crashing after mesa update

#12 2021-12-21 22:11:52

Re: qt5-webengine crashing after mesa update

#13 2021-12-21 22:13:28

Re: qt5-webengine crashing after mesa update

#14 2021-12-21 22:30:43

Re: qt5-webengine crashing after mesa update

#15 2021-12-21 23:35:07

Re: qt5-webengine crashing after mesa update

#16 2021-12-22 00:44:46

Re: qt5-webengine crashing after mesa update

#17 2021-12-22 10:46:41

Re: qt5-webengine crashing after mesa update

#18 2021-12-23 15:15:15

Re: qt5-webengine crashing after mesa update

#19 2021-12-24 10:57:45

Re: qt5-webengine crashing after mesa update

#20 2022-01-06 13:29:05

Re: qt5-webengine crashing after mesa update

Board footer