https://bugs.kde.org/show_bug.cgi?id=410211
Matt Fagnani <matthew.fagn...@utoronto.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|plasmashell segmentation |plasmashell segmentation
|fault when running |fault when Plasma on X
|startplasmacompositor from |autologin froze on the
|VT in Fedora Rawhide |splash screen in Fedora
| |Rawhide
--- Comment #2 from Matt Fagnani <matthew.fagn...@utoronto.ca> ---
David, I was going to log in to Plasma on Wayland from sddm as I usually do,
but the Fedora live image is set to autologin to Plasma on X. I had stopped
sddm, Plasma, and X before I ran startplasmacompositor. I restarted sddm so
that the X amdgpu driver would be used instead of the X modesetting driver
since the system has a Radeon R5 GPU.
I think that the plasmashell crash was more likely to have happened when the
autologin to Plasma on X got stuck on the splash screen and I stopped sddm than
when I ran startplasmacompositor. The trace of the segmentation fault doesn't
appear to have any Wayland-specific functions. The Wayland session appear
normally. I just didn't see drkonqi until the Wayland session started..
plasmashell and drkonqi aborted after I stopped sddm and before I ran
startplasmacompositor the next time I tried to reproduce the crash. The Plasma
on X autologin splash screen freeze has happened several times after restarting
sddm with two Fedora rawhide live images. The circle stopped spinning after a
few seconds, and the desktop didn't appear. I'm sorry about the mixup. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
