Arch Linux

Maximo

Member

Registered: 2023-12-29

Posts: 3

[SOLVED] STEAM won't open. (zenity:nº): Failed to open display

Hi, I'm Max
I'm New here.
I look for a solution to this:

[max@root ~]$ steam
steam.sh[5321]: Running Steam on arch rolling 64-bit
steam.sh[5321]: STEAM_RUNTIME is enabled automatically
setup.sh[5393]: Updating Steam runtime environment...
Authorization required, but no authorization protocol specified


(zenity:5401): Gtk-WARNING **: 17:26:02.867: Failed to open display
steam.sh[5321]: Can't find 'steam-runtime-check-requirements', continuing anyway
[2023-12-29 17:26:03] Startup - updater built Apr 28 2023 18:32:42
[2023-12-29 17:26:03] Startup - Steam Client launched with: '/home/max/.local/share/Steam/ubuntu12_32/steam'
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
Installing breakpad exception handler for appid(steam)/version(0)/tid(5446)
Authorization required, but no authorization protocol specified

src/steamexe/updateui_xwin.cpp (339) : Could not open connection to X
src/steamexe/updateui_xwin.cpp (339) : Could not open connection to X
Installing breakpad exception handler for appid(steam)/version(1.0)/tid(5446)
assert_20231229172603_4.dmp[5451]: Uploading dump (out-of-process)
/tmp/dumps/assert_20231229172603_4.dmp
src/steamexe/main.cpp (1227) : failed to initialize update status ui, or create initial window
src/steamexe/main.cpp (1227) : failed to initialize update status ui, or create initial window
Authorization required, but no authorization protocol specified


(zenity:5448): Gtk-WARNING **: 17:26:03.189: Failed to open display
[max@root ~]$ assert_20231229172603_4.dmp[5451]: Finished uploading minidump (out-of-process): success = yes
assert_20231229172603_4.dmp[5451]: response: CrashID=bp-7d9fd495-f1f4-4e49-bc45-9c8b72231229
assert_20231229172603_4.dmp[5451]: file ''/tmp/dumps/assert_20231229172603_4.dmp'', upload yes: ''CrashID=bp-7d9fd495-f1f4-4e49-bc45-9c8b72231229''

This is what I did previously:

1. install arch linux
2. configure the mirrorlists, locale, languages, keyboard, network, users, and stuff. It's all English because I think it would be more compatible with everything.
3. install NetworkManager, pipewire, ttf-liberation, alsa
4. install dwm and other suckless software
5. install nvidia, nvidia-utils lib32-nvidia-utils
6. install steam with all its dependencies. I even installed (steam-native-runtime and steamcmd)

> multilib enabled

I can login and download libraries with steamcmd, but I cannot run any title.

Firefox, Gimp, and Inkscape work fine

but Steam, Discord, and VLC they all gave me errors

DISCORD:

[max@root ~]$ discord
Discord 0.0.39
Authorization required, but no authorization protocol specified

[6379:1229/174639.181749:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[6379:1229/174639.181782:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
The futex facility returned an unexpected error code.
Aborted (core dumped)
[max@root ~]$

VLC

[max@root ~]$ vlc
VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
XDG_RUNTIME_DIR (/run/user/0) is not owned by us (uid 1000), but by uid 0! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
[0000559f3a111630] vlcpulse audio output error: PulseAudio server connection failure: Connection refused
[0000559f3a1733c0] dbus interface error: Failed to connect to the D-Bus session daemon: Failed to connect to socket /run/user/0/bus: Permission denied
[0000559f3a1733c0] main interface error: no suitable interface module
[0000559f3a041550] main libvlc error: interface "dbus,none" initialization failed
Authorization required, but no authorization protocol specified

[0000559f3a157430] main interface error: no suitable interface module
[0000559f3a041550] main libvlc error: interface "globalhotkeys,none" initialization failed
[0000559f3a041550] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

[0000559f3a157430] skins2 interface error: cannot initialize OSFactory
[0000559f3a0d5710] main playlist: playlist is empty
[0000559f3a157430] [cli] lua interface: Listening on host "*console".
VLC media player 3.0.20 Vetinari
Command Line Interface initialized. Type `help' for help.
>

I do not know if those three applications have anything in common.
I tried to write every useful data I could think of. This is my first time posting here so if I did anything wrong, notify me.
Thanks in advance.
──────▄▀▄─────▄▀▄
─────▄█░░▀▀▀▀▀░░█▄
─▄▄──█░░░░░░░░░░░█──▄▄
█▄▄█─█░░▀░░┬░░▀░░█─█▄▄█

Last edited by Maximo (2024-01-03 20:48:45)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,048

Re: [SOLVED] STEAM won't open. (zenity:nº): Failed to open display

[0000559f3a1733c0] dbus interface error: Failed to connect to the D-Bus session daemon: Failed to connect to socket /run/user/0/bus: Permission denied

4. install dwm and other suckless software

You're starting the session w/ startx/xinit?
Post your xinitrc and see the last link below.

if I did anything wrong, notify me.

You gotta put the cat in [code][/code] tags

Last edited by seth (2023-12-31 15:22:59)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Maximo

Member

Registered: 2023-12-29

Posts: 3

Re: [SOLVED] STEAM won't open. (zenity:nº): Failed to open display

Hello seth. Happy New Year!
This is the prompt from

startx

:

[root@root ~]# startx


X.Org X Server 1.21.1.10
X Protocol Version 11, Revision 0
Current Operating System: Linux root 6.6.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 21 Dec 2023 19:01:01 +0000 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=901d4ede-3db0-41b6-a504-8057f6fdcadb rw zswap.enabled=0 rootfstype=ext4 loglevel=3 quiet

Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Jan  3 12:57:38 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

[root@root ~]#

This is my ~/.xinitrc

 exec dwm 

I don't know what this means:

 [0000559f3a1733c0] dbus interface error: Failed to connect to the D-Bus session daemon: Failed to connect to socket /run/user/0/bus: Permission denied 

[root@root ~]# ls -l /run/user/0/bus
srwxrwxrwx 1 root root 0 Jan  3 12:57 /run/user/0/bus
[root@root ~]#

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: [SOLVED] STEAM won't open. (zenity:nº): Failed to open display

Fix your ~/.xinitrc. Click on the link in seth's signature for instructions.

And don't try to run X as root. Ever.

---

Jin, Jîyan, Azadî

Maximo

Member

Registered: 2023-12-29

Posts: 3

Re: [SOLVED] STEAM won't open. (zenity:nº): Failed to open display

Thank you very much!