New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archlinux Segfault when launching applications #1022
Comments
Not sure if it's the same issue, but 3.13.7 segfaults when starting Neverball under KDE on Gentoo, whereas 3.13.0 works fine. |
Found the bug potentially if running under // HACK! HACK HACK HACK
// To avoid stutter when toggling the overlay on
int curLayer = frameInfo.layerCount++;
FrameInfo_t::Layer_t *layer = &frameInfo.layers[ curLayer ];
auto tex = vulkan_get_hacky_blank_texture();
layer->scale.x = g_nOutputWidth == tex->width() ? 1.0f : tex->width() / (float)g_nOutputWidth; The segmentation fault happens when accessing This function runs when However, by re-adding the initialization function in that // Oh no.
pOutput->temporaryHackyBlankImage = vulkan_create_debug_blank_texture(); at 3094 in Also, there's a race condition when launching gdp for debugging that causes another error. And another one where if you close the child of gamescope, it doesn't close. Don't know if I'll raise an issue about those though. |
Looks like today arch maintainers decided to update gamescope to 3.13.7-1, now I also have segmentation fault even when running Downgrading to 3.13.3-1 solved this issue. |
I've also run into this issue after pulling in more recent commits into my fork |
I found the offending commit, the regression was introduced with fe3dbc6, so the last good commit is 31ad691. I tested with a RX6600, kernel 6.6.1 and mesa git 898700ca647, I get the following log:
|
The issue is fixed on my side with 3.13.8 |
I'm using
gamescope-git
from the aur. With help I've been able to get the segfault debugging information.The segfault happens when an application/game is launched with
gamescope
(thegamescope
package from archlinux works fine). For this debugging information I usedgamescope -- glxgear
.EDIT:
System Information
The text was updated successfully, but these errors were encountered: