You are not logged in.

#1 2025-04-08 16:44:17

dazpe
Member
Registered: 2025-04-08
Posts: 5

[SOLVED] Steam core dumping every time I boot it up

Wednesday April 9th, 00:07: I updated the given code in code blocks as requested :)
Wednesday April 9th, 19:20: Fixed it by changing this

nvidia_drm modeset=1 nvidia_drm fbdev=1

into this

nvidia_drm.modeset=1 nvidia_drm.fbdev=1

Thank you so much to those who helped me. This issue was a huge win (and relief) for me.

I wasn't even planning on creating an account for this but here I am.

Before I write my issue I want to provide some context. I switched to Linux from Windows 11 on Friday. To learn programming. Proper desktop development. I have been, quite honestly, non-stop setting up and continuously fixing every single issue that came, one after the other. First were the drivers, took me over 30 hours to set em up with zero experience on Linux and with an ancient GPU (770) with legacy drivers. Sure now I can install them non-problem but before that it was constantly researching, reading, reading the wiki, forums, threads, etc. Then it was screen tearing, missing animations, turned out KDE does NOT play nice with NVIDIA which in turn I clean reinstalled (third time then) with Cinnamon. Now I'm in a very comfy spot with my configuration: everything was fixed. But when I tried installing Steam to play some games, did not work, got the flatpak alternative as well, didn't work. Both failed, both gave me GTK2 and GTK4 theme errors and it always ends in core dump.

I'm an absolute noob here with bash, so if you need me to provide with more context or logs, I will happily try since I want to solve this already.

I have all drivers installed that belong with my GPU:

 $ spl nvidia
lib32-nvidia-470xx-utils
nvidia-470xx-dkms
nvidia-470xx-settings
nvidia-470xx-utils
opencl-nvidia-470xx

I have the multilib uncommented  just as the wiki guided me through. I installed Steam and I want it installed on pacman, currently is just sitting there, I have reinstalled it, uninstalled it, removed cache files, removed orphaned folders, removed orphaned packages (to check it was not any blooting issue). Reinstalled again. Same thing. Same errors always repeat. The usual log is as it follows.

 $ steam
steam.sh[4118]: Running Steam on arch rolling 64-bit
steam.sh[4118]: STEAM_RUNTIME is enabled automatically
setup.sh[4173]: Steam runtime environment up-to-date!
steam.sh[4118]: Log already open
steam.sh[4118]: Using supervisor /home/diego/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-supervisor
steam.sh[4118]: Steam client's requirements are satisfied
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[2025-04-08 18:42:47] Startup - updater built Apr  2 2025 00:27:22
[2025-04-08 18:42:47] Startup - Steam Client launched with: '/home/diego/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[1970-01-01 01:00:00] Process started with command-line: '/home/diego/.local/share/Steam/ubuntu12_32/steam' '-child-update-ui' '-child-update-ui-socket' '8' '-srt-logger-opened'
04/08 18:42:47 minidumps folder is set to /tmp/dumps
[1970-01-01 01:00:00] Using update UI: xwin
04/08 18:42:47 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(4241)
[2025-04-08 18:42:47] Create window
[2025-04-08 18:42:47] Loading cached metrics from disk (/home/diego/.local/share/Steam/package/steam_client_metrics.bin)
[2025-04-08 18:42:47] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2025-04-08 18:42:47] Using the following download hosts for Public, Realm steamglobal
[2025-04-08 18:42:47] 1. [url]https://client-update.steamstatic.com[/url], /, Realm 'steamglobal', weight was 1, source = 'baked in'
04/08 18:42:47 minidumps folder is set to /tmp/dumps
[2025-04-08 18:42:47] Checking for update on startup
[2025-04-08 18:42:47] Checking for available updates...
[2025-04-08 18:42:47] Downloading manifest: [url]https://client-update.steamstatic.com/steam_client_ubuntu12[/url]
[2025-04-08 18:42:47] Manifest download: send request
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadWindow (invalid Window parameter)
Major opcode of failed request:  155 (NV-GLX)
Minor opcode of failed request:  4
Resource id in failed request:  0x3a00002
Serial number of failed request:  47
xerror_handler: X failed, continuing
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadAlloc (insufficient resources for operation)
Major opcode of failed request:  151 (GLX)
Minor opcode of failed request:  5 (X_GLXMakeCurrent)
Serial number of failed request:  0
xerror_handler: X failed, continuing
[2025-04-08 18:42:47] Set percent complete: 0
[2025-04-08 18:42:47] Set status message: Checking for available updates...
[2025-04-08 18:42:47] Set percent complete: -1
[2025-04-08 18:42:47] Manifest download: waiting for download to finish
[2025-04-08 18:42:48] Manifest download: finished
[2025-04-08 18:42:48] Download skipped: /steam_client_ubuntu12 version 1743554648, installed version 1743554648, existing pending version 0
[2025-04-08 18:42:48] Nothing to do
[2025-04-08 18:42:48] Verifying installation...
[2025-04-08 18:42:48] Verifying all executable checksums
[2025-04-08 18:42:48] Set percent complete: -1
[2025-04-08 18:42:48] Set status message: Verifying installation...
[2025-04-08 18:42:49] Verification complete
UpdateUI: skip show logo
[2025-04-08 18:42:49] Destroy window
[2025-04-08 18:42:49] Shutdown
 Steam logging initialized: directory: /home/diego/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xeed88dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xeed87500
/home/diego/.local/share/Steam/steam.sh: line 946:  4240 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"

And please, do tell me if I format wrong anything and I will follow anything you guys say. Thanks!

Last edited by dazpe (2025-04-09 17:21:22)

Offline

#2 2025-04-08 19:24:10

jl2
Member
From: 47° 18' N 8° 34' E
Registered: 2022-06-01
Posts: 1,321

Re: [SOLVED] Steam core dumping every time I boot it up

perhaps https://wiki.archlinux.org/title/OpenGL#Installation (But I'd expect it to whine around if the installation was nonexistant)

X Error of failed request:  BadAlloc (insufficient resources for operation)

This, on the other hand, wines about VRAM/GPU? I don't know if 2 GB VRAM is enough but it should be.

Possibly related to https://bbs.archlinux.org/viewtopic.php?id=291271 (but keep that possible in mind)


Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...

Upload longer text output like this

Offline

#3 2025-04-08 20:09:21

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,973

Re: [SOLVED] Steam core dumping every time I boot it up

Please post the full outputs of

$ lspci -k
$ glxinfo -B   #comes with mesa-utils 
$ glxinfo32 -B #comes with lib32-mesa-utils 
$ vulkaninfo --summary #comes with vulkan-tools

Please separate the outputs in mutiple code blocks to keep the output readable ..


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2025-04-08 21:59:12

dazpe
Member
Registered: 2025-04-08
Posts: 5

Re: [SOLVED] Steam core dumping every time I boot it up

@Lone_Wolf

 $ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: skl_uncore
	Kernel modules: ie31200_edac
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: ahci
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:1d.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #11 (rev f1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:1d.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #12 (rev f1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device f971
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_avs
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 770] (rev a1)
	Subsystem: eVga.com. Corp. Device 2774
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
	Subsystem: eVga.com. Corp. Device 2774
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: xhci_hcd
05:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7971
	Kernel driver in use: r8169
	Kernel modules: r8169
 $ glxinfo -B
name of display: :0
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  155 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x2c00003
  Serial number of failed request:  40
  Current serial number in output stream:  40
 
# Same output for glxinfo32 for some odd reason.

 $ glxinfo32 -B
name of display: :0
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  155 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x2c00003
  Serial number of failed request:  40
  Current serial number in output stream:  40
 $ vulkaninfo --summary
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.309


Instance Extensions: count = 20
-------------------------------
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 9
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 6
--------------------------
VK_LAYER_INTEL_nullhw           INTEL NULL HW                1.1.73   version 1
VK_LAYER_MESA_device_select     Linux device selection layer 1.4.303  version 1
VK_LAYER_MESA_overlay           Mesa Overlay layer           1.4.303  version 1
VK_LAYER_MESA_screenshot        Mesa Screenshot layer        1.4.303  version 1
VK_LAYER_MESA_vram_report_limit Limit reported VRAM          1.4.303  version 1
VK_LAYER_NV_optimus             NVIDIA Optimus layer         1.2.175  version 1

Devices:
========
GPU0:
	apiVersion         = 1.2.175
	driverVersion      = 471.0.2.0
	vendorID           = 0x10de
	deviceID           = 0x1184
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce GTX 770
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 470.256.02
	conformanceVersion = 1.2.6.0
	deviceUUID         = 71fd6dcf-dbcf-6de5-05c4-750211b74a14
	driverUUID         = b67e126b-ca9f-5837-843e-603a6ad11b15
  

The outputs for

glxinfo -B

and

glxinfo32 -B

were present for

glxinfo

by its own too. As i said, I've been troubleshooting Steam for almost 2 days straight. So, what do you think is the root of the issue? And thank you for taking the time for replying and trying to help. It means a lot!

Last edited by dazpe (2025-04-08 22:10:19)

Offline

#5 2025-04-08 22:04:46

dazpe
Member
Registered: 2025-04-08
Posts: 5

Re: [SOLVED] Steam core dumping every time I boot it up

jl2 wrote:

perhaps https://wiki.archlinux.org/title/OpenGL#Installation (But I'd expect it to whine around if the installation was nonexistant)

X Error of failed request:  BadAlloc (insufficient resources for operation)

This, on the other hand, wines about VRAM/GPU? I don't know if 2 GB VRAM is enough but it should be.

Possibly related to https://bbs.archlinux.org/viewtopic.php?id=291271 (but keep that possible in mind)

Hey @jl2, thanks for replying. Well I took a quick look at those threads and they might be loosely connected to my issue, but not quite.

Offline

#6 2025-04-09 13:17:05

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,973

Re: [SOLVED] Steam core dumping every time I boot it up

dazpe wrote:

And thank you for taking the time for replying and trying to help. It means a lot!

yw


It's to early to point to a root cause, but some things can already be removed as possible cause .

The lspci & vulkaninfo output look good and confirm you only have 1 videocard.
(you may be surprised how many people have 2 videocards in their system without realising it).

Glxinfo output should provide basic details about your system, it failing is a bad sign.

Combined this indicates the issue is not with steam but on a lower level .


Please run as root (or with root rights)

# journalctl -b | curl -F 'file=@-' 0x0.st

It will upload your system journal to a public hosting site and output a link. Post that link .

Also post xorg log .

How are you starting cinnamon ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#7 2025-04-09 14:07:20

dazpe
Member
Registered: 2025-04-08
Posts: 5

Re: [SOLVED] Steam core dumping every time I boot it up

Hi @Lone_Wolf, thank you for clarifying some of the confusing output of glxinfo, here's as you requested, the journalctl output:

 # journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/8_73.txt 

I tried requesting xorg log as you asked, and this was the result. I had to do some path checking as well and redo the command lol

 $ tail -f ~/.local/share/xorg/Xorg.0.log | ts
bash: ts: command not found
tail: cannot open '/home/diego/.local/share/xorg/Xorg.0.log' for reading: No such file or directory
tail: no files remaining 
 $ sp -S ts
[sudo] password
error: target not found: ts 
 $ grep -e Log -e tty Xorg.0.log
grep: Xorg.0.log: No such file or directory 
 $ ls ~/.local/share/xorg/Xorg.
Xorg.1.log  Xorg.2.log 
 $ tail -f ~/.local/share/xorg/Xorg.1.log | ts
bash: ts: command not found 
 $ tail -f ~/.local/share/xorg/Xorg.1.log
[   492.480] (II) event3  - Logitech G502 HERO Gaming Mouse: device is a pointer
[   492.481] (II) systemd-logind: got resume for 13:68
[   492.482] (II) event4  - Logitech G502 HERO Gaming Mouse Keyboard: is tagged by udev as: Keyboard
[   492.482] (II) event4  - Logitech G502 HERO Gaming Mouse Keyboard: device is a keyboard
[   492.482] (II) systemd-logind: got resume for 13:66
[   492.483] (II) event2  - Power Button: is tagged by udev as: Keyboard
[   492.483] (II) event2  - Power Button: device is a keyboard
[   492.487] (II) systemd-logind: got resume for 13:65
[   492.488] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   492.488] (II) event1  - Power Button: device is a keyboard

I was trying with 'ts' as the wiki said and ts wasn't found so it worked without 'ts'.

I also tried with grep to find anything related to nvidia in the xorg log:

 $ grep -e nvidia  -e tty ~/.local/share/xorg/Xorg.1.log
[   192.348] Kernel command line: initrd=\initramfs-linux.img root=PARTUUID=ff10b50f-84cf-4d0a-94b8-7786ab2d463f zswap.enabled=0 rw rootfstype=ext4 nvidia_drm modeset=1 nvidia_drm fbdev=1
[   192.356] (**) |   |-->Device "nvidia"
[   192.413] (II) LoadModule: "nvidia"
[   192.413] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   192.414] (II) Module nvidia: vendor="NVIDIA Corporation"
[   192.415] (**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0 {ForceFullCompositionPipeline=On}"
[   192.415] (II) Loading sub module "glxserver_nvidia"
[   192.415] (II) LoadModule: "glxserver_nvidia"
[   192.416] (WW) Warning, couldn't open module glxserver_nvidia
[   192.416] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module does not exist, 0)
[   192.440] (II) NVIDIA(0):     "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
[   192.443] (WW) NVIDIA:     '/var/run/nvidia-xdriver-8b147746' Permission denied
[   192.461] (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
[   192.512] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   492.424] (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"

How are you starting cinnamon ?

Well I don't know what you mean by that, but I will say you mean as the boot itself? I use the main Arch - Linux kernel (not linux-lts) and boot Cinnamon almost instantly
(pretty fast ngl). The only DE I have is Cinnamon at the moment, I had KDE before but as stated it was working horribly with my GPU-

Last edited by dazpe (2025-04-09 14:10:26)

Offline

#8 2025-04-09 14:57:11

Nikolai5
Member
From: North West, England, UK
Registered: 2024-01-27
Posts: 272

Re: [SOLVED] Steam core dumping every time I boot it up

dazpe wrote:

Well I don't know what you mean by that, but I will say you mean as the boot itself? I use the main Arch - Linux kernel (not linux-lts) and boot Cinnamon almost instantly
(pretty fast ngl). The only DE I have is Cinnamon at the moment, I had KDE before but as stated it was working horribly with my GPU-

I think they mean if you were launching cinnamon manually via a command, or a command in a script, or via something like SDDM, we can see in the journal you shared that it's SDDM though.


Ryzen 7 9850X3D | AMD 7800XT | KDE Plasma

Offline

#9 2025-04-09 15:11:43

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,973

Re: [SOLVED] Steam core dumping every time I boot it up

Apr 09 15:50:29 archlinux kernel: Command line: initrd=\initramfs-linux.img root=PARTUUID=ff10b50f-84cf-4d0a-94b8-7786ab2d463f zswap.enabled=0 rw rootfstype=ext4 nvidia_drm modeset=1 nvidia_drm fbdev=1

Apr 09 15:50:29 archlinux kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
Apr 09 15:50:29 archlinux kernel: Failed to initialize the nv-hotplug-helper DRM client (ensure DRM kernel mode setting is enabled via nvidia-drm.modeset=1).
Apr 09 15:50:29 archlinux kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Unloading driver

typo in the kernel parameters, use

nvidia_drm.modeset=1 nvidia_drm.fbdev=1

instead.
(you may not need nvidia_drm.fbdev=1 as that's mainly for newer cards)


about starting cinnamon :
linux kernel can't start GUI environment , for X there are 2 methods used :
boot to graphical target, load a Display Manager (sometimes called login manager) and let the DM start user sessions
boot to multi-user target (tty/console) , user logins to console and runs startx / xinit manually .

You are using the first method with sddm as DM.

Apr 09 15:50:31 archlinux sddm[618]: Initializing...
Apr 09 15:50:31 archlinux sddm[618]: Starting...
Apr 09 15:50:31 archlinux sddm[618]: Logind interface found
Apr 09 15:50:31 archlinux sddm[618]: Adding new display...
Apr 09 15:50:31 archlinux sddm[618]: Loaded empty theme configuration
Apr 09 15:50:31 archlinux sddm[618]: Xauthority path: "/run/sddm/xauth_WBZAMQ"
Apr 09 15:50:31 archlinux sddm[618]: Using VT 2
Apr 09 15:50:31 archlinux sddm[618]: Display server starting...
Apr 09 15:50:31 archlinux sddm[618]: Writing cookie to "/run/sddm/xauth_WBZAMQ"
Apr 09 15:50:31 archlinux sddm[618]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_WBZAMQ -noreset -displayfd 16
Apr 09 15:50:32 archlinux iwd[490]: event: state, old: disconnected, new: autoconnect_quick
Apr 09 15:50:32 archlinux NetworkManager[489]: <info>  [1744206632.1287] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Apr 09 15:50:32 archlinux iwd[490]: udev interface=wlan0 ifindex=3
Apr 09 15:50:32 archlinux NetworkManager[489]: <info>  [1744206632.7400] device (wlan0): set-hw-addr: set MAC address to 96:25:38:F9:E0:2B (scanning)
Apr 09 15:50:32 archlinux sddm[618]: Setting default cursor
Apr 09 15:50:32 archlinux sddm[618]: Could not setup default cursor
Apr 09 15:50:32 archlinux sddm[618]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Apr 09 15:50:32 archlinux kernel: Bluetooth: hci1: Opcode 0x1005 failed: -110
Apr 09 15:50:32 archlinux sddm[618]: Display server started.

Correct the kernel parameter(s), then reboot and test.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#10 2025-04-09 17:12:54

dazpe
Member
Registered: 2025-04-08
Posts: 5

Re: [SOLVED] Steam core dumping every time I boot it up

Oh my god, it was literally fixing that typo.

nvidia_drm.modeset=1 nvidia_drm.fbdev=1

I can't even BEGIN to tell you how grateful I am. I have spent 2 days now on this and the nightmare is finally joever. Thank you smile Marking it as solved!

Offline

Board footer

Powered by FluxBB