You are not logged in.
Take GDM and gnome out of the equation.
xinit an xterm, https://wiki.archlinux.org/index.php/Xinit#xinitrc and run steam there. See what problems remain.
Because of the hybrid system you might be running GDM on wayland and gnome on either and and steam on an X11 server, all accessing the same input devices at the same time.
Offline
Take GDM and gnome out of the equation.
xinit an xterm, https://wiki.archlinux.org/index.php/Xinit#xinitrc and run steam there. See what problems remain.Because of the hybrid system you might be running GDM on wayland and gnome on either and and steam on an X11 server, all accessing the same input devices at the same time.
I'm sorry Seth, although I consider myself a good "power user", I don't think my current skills reached what do you meant. If get what you meant, I should I edit my xinitrc appending "xterm" to the end of the file (do zsh works?) and then restart the system, which wil automatically start xterm (or zsh?) at startup. Then I run steam from that openned terminal and this will start steam on a separete X display which will be free from gnome and GMD. Am I right?
Offline
No.
You need to disable GDM and/or boot the multi-user.target.
Your xinitrc should not simply tail w/ "xterm" but "exec xterm" should be the first line starting w/ "exec" at the end of the file (because nothing ofterwards will be executed)
Ensure xinit & xterm are installed.
At the multi-user.target log in as your regular user and run "xinit"
Xterm will automatically run your default shell, you cannot start "zsh" in the xinitrc.
Offline
Ok, Done. The game ran flawessly, smoothly and successfully for 3 hours or more. So, indeed it is something related to GDM or gnome. Maybe if I strip out wayland from my system? If so, how to properly do that? At first, it doesn't seems to be a good idea:
$ sudo pacman -Rs wayland wayland-protocols
[sudo] password for jeco:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing wayland breaks dependency 'wayland' required by egl-wayland
:: removing wayland breaks dependency 'wayland' required by freerdp
:: removing wayland breaks dependency 'wayland' required by gst-plugins-bad
:: removing wayland breaks dependency 'wayland' required by gtk3
:: removing wayland-protocols breaks dependency 'wayland-protocols' required by gtk3
:: removing wayland breaks dependency 'wayland' required by intel-media-sdk
:: removing wayland breaks dependency 'wayland' required by lib32-wayland
:: removing wayland breaks dependency 'wayland' required by libva
:: removing wayland breaks dependency 'wayland' required by mesa
:: removing wayland-protocols breaks dependency 'wayland-protocols' required by vlc
:: removing wayland breaks dependency 'wayland' required by wpebackend-fdoI'm pretty sure I need mesa and gtk3. Any other idea? Any more logs or testes that could help to understand that?
Last edited by jecogeo (2020-05-04 23:48:24)
Offline
Removing the wayland package isn't a good idea, but as a next step you could try to use GDM on Xorg and there select Gnome on Xorg to see whether this is more wayland or gnome related.
https://wiki.archlinux.org/index.php/GD … rg_backend (and there just explicitly select gnome on xorg)
Offline
I have great news. After +- 15 hours of playing I can confirm the problem is solved. Indeed it was related to wayland. I'll summarize the solutions for future reference:
Part of the issue was due to overheating. Solution: replace bbswitch and bumblebee with PRIME.
usb ports were still disconnecting, system hanging and ultimetely leading to system shutdown. Solution: Use GDM on Xorg and Gnome on Xorg
I'd like to say thanks to seth for being so patient and so helpfull. I hope I can be as usefull to others in this forum.
Offline