You are not logged in.
I'm using aur qutebrowser-git package (latest) and since the latest pacman package update this morning qutebroswer just randomly crashes very often. And the time between crashes is completely random. Sometimes it will crash after 5 mins of use, sometimes after 40 mins of use. I don't know the relevancy but youtube is playing in the background while it crashes so I don't know if video playback is relevent.
Anyone else experience this issue? Later today I will try to move to qutebrowser stable instead of the git version, but rather stay on git if there is some simple fix or workaround until the underlying issuse gets resolved.
Offline
Console output after crash
[3540:3573:0719/111016.429833:FATAL:scoped_file.cc(43)] Check failed: . : Bad file descriptor (9)
Trace/breakpoint trap (core dumped)
Offline
Mod note: moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Trace/breakpoint trap (core dumped)
Offline
I got the full core dump stack trace but I dont think it really tells anything interesting nor would I know how to debug it from there. I'm 95% sure it has to do with some interaction between qtwebkit and the current nvidia drivers (both show up in the trace and both were recently updated from pacman). I completely wiped everything related to qutebrowser and reinstalled fresh and it still crashes with the exact same type of segfault. I guess I will just have to wait until either/both qt and nvidia drivers get updated and the issues magically fixes itself.
I'm assuming there is no other broad suggestions anyone else can give, otherwise I will have to reluctantly use google chrome until this issue gets resolved upstream.
Offline
The backtrace ideally tells you what crashes where, why.
Did you enable debuginfod?
What does the backtrace look like?
Offline
Here is the coredumpctl info:
Offline
pyqt6-webengine-debug and qt6-webengine-debug are provided by https://wiki.archlinux.org/title/Debuginfod, if you want to know what crashes there you'll have to use them as it happes deeeeeep in libQt6WebEngineCore.so.6
Do you have the same issues w/ an X11 session (you seem to be running a wayland client)
Offline
it seems im not getting anymore segfaults in qutebrowser after this update:
[2024-07-22T09:02:14-0700] [ALPM] upgraded egl-wayland (2:1.1.14-1 -> 3:1.1.13-1)
So it looks like maybe it was a wayland specific issue (didnt try X11 like you suggested yet). Either way it seems like im all good now.
Offline
https://old.reddit.com/r/archlinux/comm … aded_back/
It looks like someone on reddit had some similar problem with this package, but crashing firefox instead. I think 1.14-1 was just a bad update, at least for people using Nvidia.
Offline