Skip to content
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

GZDoom can't start anymore - CommandLine Error: Option 'help-list' registered more than once #1405

Closed
Vaults opened this issue Jun 1, 2021 · 3 comments

Comments

@Vaults
Copy link

Vaults commented Jun 1, 2021

Hello there,

Unfortunately the program has completely stopped working for me on Linux Mint 20.1. I can only run GZDoom through WINE. Whenever I boot up the program with every kind of configuration this happens in the logs (I'm using a RX 6900 XT and it started since I installed it into my machine):

GZDoom g4.6.0 - 2021-05-22 16:34:22 +0200 - SDL version
Compiled on May 22 2021

OS: Linux Mint 20, Linux 5.8.8-050808-generic on x86_64
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
 adding /opt/gzdoom/gzdoom.pk3, 633 lumps
 adding /opt/gzdoom/game_support.pk3, 2514 lumps
 adding /home/<user>/.config/gzdoom/Doom2.wad, 2919 lumps
 adding /opt/gzdoom/game_widescreen_gfx.pk3, 98 lumps
I_Init: Setting up machine state.
CPU Vendor ID: AuthenticAMD
  Name: AMD Ryzen 9 3900X 12-Core Processor 
  Family 23 (23), Model 113, Stepping 0
  Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 F16C FMA3 BMI1 BMI2 HyperThreading
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
  Opened device Starship/Matisse HD Audio Controller Analog Stereo
  EFX enabled
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 108.20 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver x11
: CommandLine Error: Option 'help-list' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
Aborted (core dumped)

I'm suspecting it has to do with conflicting LLVM versions. The ones I have installed are

$ apt list --installed | grep -i llvm

libllvm11.0-amdgpu/unknown,now 1:11.0-1247438 amd64 [installed,automatic]
libllvm11.0-amdgpu/unknown,now 1:11.0-1247438 i386 [installed,automatic]
libllvm11/focal-updates,now 1:11.0.0-2~ubuntu20.04.1 amd64 [installed]
libllvm11/focal-updates,now 1:11.0.0-2~ubuntu20.04.1 i386 [installed,automatic]

Is there a known workaround for the time being?

@Vaults Vaults changed the title GZDoom can't boot anymore - CommandLine Error: Option 'help-list' registered more than once GZDoom can't start anymore - CommandLine Error: Option 'help-list' registered more than once Jun 1, 2021
@Vaults
Copy link
Author

Vaults commented Jun 28, 2021

The new AMD drivers for Ubuntu (v21.20) have fixed the issue. I will now close it.

The versions do not conflict any longer which could have been the problem

$ apt list --installed | grep -i llvm

libllvm11/focal-updates,now 1:11.0.0-2~ubuntu20.04.1 amd64 [installed]
libllvm11/focal-updates,now 1:11.0.0-2~ubuntu20.04.1 i386 [installed,automatic]
libllvm12.0-amdgpu/unknown,now 1:12.0-1271047 amd64 [installed,automatic]
libllvm12.0-amdgpu/unknown,now 1:12.0-1271047 i386 [installed,automatic]

@Vaults Vaults closed this as completed Jun 28, 2021
@Vaults
Copy link
Author

Vaults commented Aug 21, 2021

Hi, I'm back 😅

It seems the last version just was okay coincidentally. I'm having the same problem with the AMDGPU (open source variant) on version 21.30.

$ apt list --installed | grep -i llvm

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libllvm11/focal-updates,now 1:11.0.0-2~ubuntu20.04.1 amd64 [installed]
libllvm12.0-amdgpu/unknown,now 1:12.0-1290604 amd64 [installed,automatic]
libllvm12.0-amdgpu/unknown,now 1:12.0-1290604 i386 [installed,automatic]
libllvm12/focal-updates,now 1:12.0.0-3ubuntu1~20.04.3 amd64 [installed,automatic]
libllvm12/focal-updates,now 1:12.0.0-3ubuntu1~20.04.3 i386 [installed,automatic]

@Vaults Vaults reopened this Aug 21, 2021
@Blzut3
Copy link
Member

Blzut3 commented Sep 25, 2021

This shouldn't have anything to do with llvm since GZDoom doesn't depend on it. I believe those messages are coming from the system trying to capture a core dump or something like that. The point it's crashing at is trying to initialize OpenGL or Vulkan depending on your ini settings, so definitely something is up with the drivers.

Try using gzdoom +vid_preferbackend 1 to switch to Vulkan if you haven't already tried that.

GZDoom runs fine on my Radeon Pro W6600, but I took the route of updating the kernel to 5.13 and using the Kisak mesa stable PPA on Ubuntu 21.04. I haven't personally installed the AMD provided drivers in years, but in theory the open source option there should provide similar results. Quite curious.

@coelckers coelckers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants