Bug 2188071

Summary: F38 LXQt comes with weston wm as default at first boot after install
Product: [Fedora] Fedora Reporter: Geraldo Simião <geraldo.simiao.kutz>
Component: spin-kickstartsAssignee: Neal Gompa <ngompa13>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: admiller, bruno, dustymabe, jgrulich, kde-sig, kevin, m, ngompa13, pierluigi.fiorini, rdieter, travier, vpavlin
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-04 12:30:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Login screen for the first boot after a fresh install
none
weston session started
none
Correct LXQt session started after change at login screen none

Description Geraldo Simião 2023-04-19 16:22:19 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0
Build Identifier: 

After booting the live image (Fedora-LXQt-Live-x86_64-38-1.6.iso) and finishing the installation process, when the first boot happens weston apears as the default session at sddm login screen. If the user doesn't notice this and don't change to the habitual lxqt desktop, he's got started a weston wm session.

Reproducible: Always

Steps to Reproduce:
1.New installation with Fedora-LXQt-Live-x86_64-38-1.6.iso
2.First boot after anaconda has finished the installation
3.login with the user created at installation time, without any further changes
Actual Results:  
We land at a weston wm session, not a LXQt desktop.

Expected Results:  
Starting a default LXQt desktop session, as one would expect from a spin called "LXQt spin"

After logout from the first weston session, and selecting the correct lxqt desktop session at the login screen, we start correctly a lxqt session, and this stay selected after reboot (the lxqt session at login). So the weston sessionas default only happens one time, at first boot after fresh install.
Comment 1 Geraldo Simião 2023-04-19 16:23:24 UTC 
Created attachment 1958317 [details]
Login screen for the first boot after a fresh install
Comment 2 Geraldo Simião 2023-04-19 16:24:57 UTC 
Versions installed with the golden iso:
    sddm-0.19.0^git20230404.e652433-1.fc38.x86_64
    sddm-wayland-generic-0.19.0^git20230404.e652433-1.fc38.noarch
    sddm-themes-0.19.0^git20230404.e652433-1.fc38.noarch
Comment 3 Geraldo Simião 2023-04-19 16:26:25 UTC 
Created attachment 1958318 [details]
weston session started
Comment 4 Geraldo Simião 2023-04-19 16:28:19 UTC 
Created attachment 1958319 [details]
Correct LXQt session started after change at login screen

If we change to lxqt desktop a login secreen it starts correctly a lxqt session
Comment 5 Neal Gompa 2023-04-19 16:33:00 UTC 
This is because the LXQt spin kickstart doesn't have an opinionated selection for sddm like the KDE and Sway spins do.

Switching to the correct component.
Comment 6 Geraldo Simião 2023-04-19 16:34:46 UTC 
Thanks Neal for adjusting this ticket.
Comment 7 Neal Gompa 2023-04-23 13:23:29 UTC 
Fix for F38: https://pagure.io/fedora-kickstarts/pull-request/958

Fix for F39: https://pagure.io/fedora-comps/pull-request/835
Comment 8 Timothée Ravier 2023-07-04 12:30:52 UTC 
Both fixes above have been merged.