SDDM Greeter Crash due to illegal opcode #2045
Comments
|
Your hardware is below our minimum requirements, and our copy of SDDM is unmodified. I'm afraid no action will be taken here. |
|
I understand that you won't take action, and I'm not asking for you to change that decision. However, the "minimum requirements" stated on the website are an x86_64 4-core 2GHz processor (https://docs.bazzite.gg/General/Installation_Guide/Installing_Bazzite_for_Desktop_or_Laptop_Hardware/). Under that requirement, an even older Celeron processor, the J1900 should work, but we both know it likely never would. I recognize that my hardware is likely missing some processor flag that Bazzite requires, but I have no clue exactly what Bazzite actually requires. May I suggest an update to the documentation that more clearly states what the system requirements are? Perhaps a quad-core 2GHz processor of at least Intel X generator or above? Or a quad-core 2GHz processor released after ? Besides, if running at 2GHz is really all that Bazzite needed, I could overclock the CPU if I really wanted to. That wouldn't change the result, though. It was a long shot that maybe Bazzite had mistakenly added a requirement for a processor flag that you didn't intend to require. However, I do still think the ticket I created is valid at least insofar as providing some clarification on system requirements. |
Also, to add more information for you. I installed Fedora 41 Kinoite, and it works perfectly. In fact, I'm writing this reply from the machine in question. So somewhere between Bazzite's stated upsteam of Fedora Atomic Desktop (Kinoite, as stated on the TTY login) and Bazzite itself, the sddm-greeter and/or libopenjph packages were changed. I still strongly suggest that Bazzite more clearly state system requirements, especially if they're going to change from upstream's requirements. State: idle fedora:fedora/41/x86_64/kinoite |
|
I am running Aurora on similarly specced system just fine. Had SDDM crash on boot due to ublue-os/aurora#7, after removing heif packages (see ublue-os/main#695 (comment)) system boots OK. |
Describe the bug
After a fresh install of Bazzite 41 on a small embedded PC, the SDDM Greeter crashes on start, and logs show an illegal opcode being trapped by the kernel from libopenjph.so.0.18.0. Restarting SDDM and rebooting exhibit the same issue. Logging in on a terminal works, though.
What did you expect to happen?
To see the SDDM greeter for logging in.
Output of
rpm-ostree statusState: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable Digest: sha256:f2e05718699e41134705227f9176379bb7740ac9cba232c42e6116398db797ee Version: 41.20250101 (2025-01-01T10:51:25Z) ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable Digest: sha256:f2e05718699e41134705227f9176379bb7740ac9cba232c42e6116398db797ee Version: 41.20250101 (2025-01-01T10:51:25Z) LayeredPackages: plasma-workspace-x11Hardware
/proc/cpuinfo
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 122
model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
stepping : 1
microcode : 0x42
cpu MHz : 898.580
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 24
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 pti cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts vnmi umip rdpid md_clear arch_capabilities
vmx flags : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs ept_violation_ve ept_mode_based_exec tsc_scaling
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass rfds bhi
bogomips : 2995.20
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
The machine is a small embedded device from Amazon made by a company called Kodlix. Intended for use playing some retro games on the TV. Quad core Intel Celeron J4105 with an Intel UHD 600 GPU and 4GB of RAM.
Extra information or context
Looked through other bugs, and tried layering the plasma-workspace-x11 suggested elsewhere. Made no change, so I reverted. Below are the logs from journalctl that appear to be most relevant. I also ran updates using 'ujust update', and the bug still occurs.
Jan 02 08:53:25 bazzite sddm-greeter-qt6[4024]: Loading file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml...
Jan 02 08:53:25 bazzite sddm-helper-start-wayland[4014]: "QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav\n"
Jan 02 08:53:25 bazzite kernel: traps: QQuickPixmapRea[4099] trap invalid opcode ip:7f97f42e748d sp:7f97ff2d3cc0 error:0 in libopenjph.so.0.18.0[348d,7f97f42e4000+43000]
Jan 02 08:53:25 bazzite audit[4024]: ANOM_ABEND auid=4294967295 uid=981 gid=977 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=4024 comm="QQuickPixmapRea" exe="/usr/bin/sddm-greeter-qt6" sig=4 res=1
Jan 02 08:53:25 bazzite systemd-coredump[4100]: Process 4024 (sddm-greeter-qt) of user 981 terminated abnormally with signal 4/ILL, processing...
Jan 02 08:53:25 bazzite audit: BPF prog-id=123 op=LOAD
Jan 02 08:53:25 bazzite audit: BPF prog-id=124 op=LOAD
Jan 02 08:53:25 bazzite audit: BPF prog-id=125 op=LOAD
Jan 02 08:53:25 bazzite systemd[1]: Started [email protected] - Process Core Dump (PID 4100/UID 0).
Jan 02 08:53:25 bazzite audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-4100-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 02 08:53:25 bazzite audit: BPF prog-id=126 op=LOAD
Jan 02 08:53:25 bazzite audit: BPF prog-id=127 op=LOAD
Jan 02 08:53:25 bazzite audit: BPF prog-id=128 op=LOAD
Jan 02 08:53:25 bazzite audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@1-4100-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 02 08:53:25 bazzite systemd[1]: Started [email protected] - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Jan 02 08:53:26 bazzite systemd-coredump[4101]: [🡕] Process 4024 (sddm-greeter-qt) of user 981 dumped core.
Jan 02 08:53:26 bazzite systemd[1]: [email protected]: Deactivated successfully.
Jan 02 08:53:26 bazzite audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-4100-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 02 08:53:26 bazzite systemd[1]: [email protected]: Consumed 984ms CPU time, 137.8M memory peak.
Jan 02 08:53:26 bazzite sddm-helper-start-wayland[4014]: Stopping... "kwin_wayland"
Jan 02 08:53:26 bazzite audit: BPF prog-id=125 op=UNLOAD
Jan 02 08:53:26 bazzite audit: BPF prog-id=124 op=UNLOAD
Jan 02 08:53:26 bazzite audit: BPF prog-id=123 op=UNLOAD
Jan 02 08:53:26 bazzite sddm-helper[3988]: pam_unix(sddm-greeter:session): session closed for user sddm
The text was updated successfully, but these errors were encountered: