VPKEdit is frozen on startup

[mattiskung]

Describe the Bug

A few months ago a bug occured that whenever i start up VPKEdit its just stuck on a white screen and it being not responsive in task manager

ive tried reinstalling it a few times but it doesn't work

To Reproduce

i have no clue what caused this so i cant say how to reproduce it

VPKEdit Version

5.0 but also on previous versions

Operating System

Windows 10

[craftablescience]

When the white screen bug happened, did you make any changes to your Steam installation?

[mattiskung]

When the white screen bug happened, did you make any changes to your Steam installation?

I don't really remember but I dont think so

[IsaacShoebottom]

I can also report a similar issue on Arch Linux, as whenever I open a vpk file with the GUI application the window never renders and is simply an empty looking window when hovered over with KDE's taskbar.

Here are some logs as far as it gets when the GUI is opening a vpk from the command line.

$ vpkedit pak12_dir.vpk                                                                                                                                                                          
QEGLPlatformContext: Failed to create context: 3009
Warning: fallback to QtQuick software backend.
QList("/usr/bin", "/usr/lib/vpkedit", "")
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QEGLPlatformContext: Failed to create context: 3009
QRhiGles2: Failed to create temporary context
QEGLPlatformContext: Failed to create context: 3009
QRhiGles2: Failed to create context
Failed to create QRhi for QBackingStoreRhiSupport

and here is what it looks like when examined from the taskbar

This is using the AUR vpkedit-bin package, so it should be the same binaries released on GitHub

[craftablescience]

@IsaacShoebottom try setting QT_QPA_PLATFORM=xcb. I think your issue is Linux-specific and likely even system-specific, probably unrelated to the Windows issue

[IsaacShoebottom]

@IsaacShoebottom try setting QT_QPA_PLATFORM=xcb. I think your issue is Linux-specific and likely even system-specific, probably unrelated to the Windows issue

This does work, so its probably not the issue originally opened. It could be an NVIDIA issue, as this disables the app from running under wayland. This environment variable runs the app under xwayland.

[craftablescience]

This disables the app from running under wayland. This environment variable runs the app under xwayland.

Yes that's partly why I asked if it fixed the issue. This issue is specific to your system configuration, please Google your error messages for more information.

[Thespikedballofdoom]

I'm getting this issue too and googling isn't leading me anywhere helpful, more than that running with sudo makes it inexplicably work (without the env var)

[craftablescience]

@Thespikedballofdoom open ~/.config/craftablescience/vpkedit.conf and set disable_steam_scanner to true. Do you still get the issue?

@mattiskung if you want to try this as well, on Windows the config option is stored in the registry at HKEY_CURRENT_USER\Software\craftablescience\vpkedit\disable_steam_scanner, or you can load an older version of the program that works and check this option:

[Thespikedballofdoom]

It doesn't unfortunately. I have a second similar linux install where it is also working with no env vars and no sudo, it is also CachyOS/wayland/KDE, the only difference is its hardware. I'll try to replicate on a fresh install as soon as I can.