gzdoom seldomly starts (X connection to :0.0 broken)

Need help running G/Q/ZDoom/ECWolf/Zandronum/3DGE/EDuke32/Raze? Did your computer break? Ask here.

Moderator: GZDoom Developers

Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!

If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.

We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Post Reply
ThinkSome
Posts: 20
Joined: Thu Aug 26, 2021 2:48 pm

gzdoom seldomly starts (X connection to :0.0 broken)

Post by ThinkSome »

gzdoom 4.6.0 and 4.6.1 with freedoom both only seldomly start.

Code: Select all

GZDoom <unknown version> -  - SDL version
Compiled on Aug 20 2021

OS: Gentoo/Linux, Linux 4.9.210-gentoo-x86_64 on x86_64
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
 adding /usr/share/doom/gzdoom.pk3, 634 lumps
 adding /usr/share/doom/game_support.pk3, 2514 lumps
 adding /usr/share/doom/freedoom2.wad, 3649 lumps
 adding /usr/share/doom/game_widescreen_gfx.pk3, 94 lumps
I_Init: Setting up machine state.
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
  Family 6, Model 58, Stepping 9
  Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX F16C HyperThreading
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
  Opened device ALSA Default
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
  EFX enabled
ID out of range. Using default device.
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 174.94 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
Adding dehacked patch freedoom2.wad:DEHACKED
Patch installed
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
===========================================================================
This is Freedoom, the free content first person shooter.

Freedoom is freely redistributable under the terms of the modified BSD
license. Check out the Freedoom website for more information:

    https://freedoom.github.io/
============================================================================
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver x11
X connection to :0.0 broken (explicit kill or server shutdown).
When it starts (about once every 20 attempts), the last line is gone and the following resumes:

Code: Select all

GL_VENDOR: Intel Open Source Technology Center
GL_RENDERER: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
GL_VERSION: 4.2 (Core Profile) Mesa 21.1.4 (Core profile)
GL_SHADING_LANGUAGE_VERSION: 4.20

...

Any ideas what could be wrong / how to fix this (besides the outdated kernel)? All other SDL / OpenGL games start immidiatelly.
Top
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: gzdoom seldomly starts (X connection to :0.0 broken)

Post by _mental_ »

Most likely, it's the same problem as in this topic. Also, do "all other games" use modern OpenGL?
Top
ThinkSome
Posts: 20
Joined: Thu Aug 26, 2021 2:48 pm

Re: gzdoom seldomly starts (X connection to :0.0 broken)

Post by ThinkSome »

_mental_ wrote:Most likely, it's the same problem as in this topic. Also, do "all other games" use modern OpenGL?
I'm not sure. But -glversion 3.3 does fix my problem. Thanks.
Top
Post Reply

Return to “Technical Issues”