Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#79017 - [linux] sddm-greater crash
Attached to Project:
Arch Linux
Opened by Alexandre ZANNI (noraj) - Saturday, 08 July 2023, 12:49 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 11 July 2023, 07:31 GMT
Opened by Alexandre ZANNI (noraj) - Saturday, 08 July 2023, 12:49 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 11 July 2023, 07:31 GMT
|
DetailsDescription:
Since linux 6.4.0 (6.4.1 and 6.4.2 too): 1. boot to vanilla kernel 2. enter luks password 3. systemd starts 4. when reaching the graphical target, sddm-greater crashes, I no longer have any video signal, my displays are going into sleep mode While using linux-lts 6.1.38 1. boot to lts kernel 2. enter luks password 3. systemd starts 4. sddm greater displays correctly In journalctl I can see "systemd-coredump[1035]: [🡕] Process 986 (sddm-greeter) of user 975 dumped core." Full stack trace: https://pastebin.com/raw/W4Qfyv3w GPU ``` ➜ lspci -k | grep -A 3 -E "(VGA|3D)" 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c7) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 480 Gaming X 8GB Kernel driver in use: amdgpu Kernel modules: amdgpu ``` |
This task depends upon
You should be checking the journal for signs of GPU driver crashes.
> Full stack trace
Basically useless without debug symbols [1]. It's usually as simple as:
$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)
Then post gdb.txt
[1] https://wiki.archlinux.org/title/Debugging/Getting_traces
However, I can see some warning level logs `journalctl -b -1 -p warning` (boot-1_warnings.log) for amdgpu, sddm-greeter, sddm-helper and sddm. (the 2h timing shift in the log timestamp is due to the hardware clock and the ntp sync in between during the init).
Note: the previous pastebin was actually from the LTS boot, not from the crashing vanilla boot.
Full last boot (journalctl -b -1) logs (boot-1_full.log).
sddm[640]: Loading theme configuration from "/usr/share/sddm/themes/Sweet/theme.conf"
Upstream issue on SDDM tracker: https://github.com/sddm/sddm/issues/1761
See also https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
Im new to the community and have been using arch for about 7 months now so it could be something I just messed up on my end. Your experience does seem extremely similar to mine, so I thought Id share.
[1] https://gitlab.freedesktop.org/agd5f/linux
[2] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
[3] https://gitlab.freedesktop.org/drm/amd/-/issues