Getting KDE installed and have a session I can select in SDDM
Actual Behavior
No available session.
Environment
Relevant Log Output
Code of Conduct
I agree to follow this project's Code of Conduct
### Description
Hello.
I download an ISO from this github action: https://github.com/Antergos-NeXT/antergos-iso/actions/runs/31129619700
And when SDDM is loaded, there is no available session. See attached screenshot.
<img width="1280" height="800" alt="Image" src="https://github.com/user-attachments/assets/c8c2b499-936f-4934-85ce-b20c3999bd3d" />
### Steps to Reproduce
1. Grab ISO from this github action: https://github.com/Antergos-NeXT/antergos-iso/actions/runs/31129619700
2. Install it keeping default options in Calamares
3. Reboot and try to log in.
### Expected Behavior
Getting KDE installed and have a session I can select in SDDM
### Actual Behavior
No available session.
### Environment
### Relevant Log Output
```shell
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
i have launched an 2nd build at https://github.com/Antergos-NeXT/antergos-iso/actions/runs/31308904030
cause i think that is a package issue or something.
also could you kindly do an 2nd install the wrapper saves the log to /home/antergos/antergos-install.log if you can find it would you kindly send the log or find the error and paste it here it would be helpful
but please dont reboot after install
also could you kindly do an 2nd install the wrapper saves the log to /home/antergos/antergos-install.log if you can find it would you kindly send the log or find the error and paste it here it would be helpful
but please dont reboot after install
I used the last created ISO and I got a bug in package selection step. Desktop environments are missing. See attached screenshot.
So is this the source of this issue?
I used the last created ISO and I got a bug in package selection step. Desktop environments are missing. See attached screenshot.
<img width="1280" height="800" alt="Image" src="https://github.com/user-attachments/assets/78d5576b-23df-4a67-bfa9-fc4be8323c18" />
So is this the source of this issue?
it wont show in that step but try to install it normally
what the? well i recently changed packagechooser to netinstall-add instead of netinstall-select
in this commit right here https://github.com/Antergos-NeXT/antergos-packages/commit/61031fc3ff686f987042ee97bbf5fb6677dca532
it wont show in that step but try to install it normally
Well, after install, same missing desktop selection in SDDM. And the log you asked for.
[antergos-install.log](https://github.com/user-attachments/files/30873710/antergos-install.log)
@FredBezies
sorry for not responding but i found the actual culprit for #14. it was never package names — plasma is a legit installable group. the real bug was in calamares itself.
we run TWO packagechooser instances (DE chooser + DM chooser, both using netinstall-add). upstream calamares tags all of that netinstall data with the same hardcoded "packageChooser" source string. so when the DM chooser writes its groups, it prunes EVERYTHING tagged packageChooser — including the DE's groups. result: KDE never makes it into packageOperations, nothing gets installed, and SDDM has no session to show. exactly the mess you saw.
the fix is a real source patch (we own the fork anyway), not a config workaround:
each chooser now tags its data with its OWN instance id (packagechooser@de / packagechooser@dm) and only prunes its own stale groups.
DE groups now survive the DM merge, both reach the packages step.
so the packages repo build is now calamares 3.4.2-9 (3.4.2-w0k3 for the funny factor, shows in About dialog + --version). #13 stands: ntp-dinit added to the Init Services group.
local build of the patched calamares finished clean. once this is pushed and CI republishes [antergos-pkgs], a fresh ISO build should have both KDE installing and a correct clock. nothing you need to redo on your end — just retest when the new ISO drops.
if you have any problems in the new iso reopen the issue :3
@FredBezies
sorry for not responding but i found the actual culprit for #14. it was never package names — plasma is a legit installable group. the real bug was in calamares itself.
we run TWO packagechooser instances (DE chooser + DM chooser, both using netinstall-add). upstream calamares tags all of that netinstall data with the same hardcoded "packageChooser" source string. so when the DM chooser writes its groups, it prunes EVERYTHING tagged packageChooser — including the DE's groups. result: KDE never makes it into packageOperations, nothing gets installed, and SDDM has no session to show. exactly the mess you saw.
the fix is a real source patch (we own the fork anyway), not a config workaround:
- each chooser now tags its data with its OWN instance id (packagechooser@de / packagechooser@dm) and only prunes its own stale groups.
- DE groups now survive the DM merge, both reach the packages step.
so the packages repo build is now calamares 3.4.2-9 (3.4.2-w0k3 for the funny factor, shows in About dialog + --version).
#13 stands: ntp-dinit added to the Init Services group.
local build of the patched calamares finished clean. once this is pushed and CI republishes [antergos-pkgs], a fresh ISO build should have both KDE installing and a correct clock. nothing you need to redo on your end — just retest when the new ISO drops.
if you have any problems in the new iso reopen the issue :3
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Hello.
I download an ISO from this github action: https://github.com/Antergos-NeXT/antergos-iso/actions/runs/31129619700
And when SDDM is loaded, there is no available session. See attached screenshot.
Steps to Reproduce
Expected Behavior
Getting KDE installed and have a session I can select in SDDM
Actual Behavior
No available session.
Environment
Relevant Log Output
Code of Conduct
another issue huh?
lets troubleshoot then wait here while i think of an fix
i have launched an 2nd build at https://github.com/Antergos-NeXT/antergos-iso/actions/runs/31308904030
cause i think that is a package issue or something.
also could you kindly do an 2nd install the wrapper saves the log to /home/antergos/antergos-install.log if you can find it would you kindly send the log or find the error and paste it here it would be helpful
but please dont reboot after install
I used the last created ISO and I got a bug in package selection step. Desktop environments are missing. See attached screenshot.
So is this the source of this issue?
what the? well i recently changed packagechooser to netinstall-add instead of netinstall-select
in this commit right here https://github.com/Antergos-NeXT/antergos-packages/commit/61031fc3ff686f987042ee97bbf5fb6677dca532
it wont show in that step but try to install it normally
Well, after install, same missing desktop selection in SDDM. And the log you asked for.
antergos-install.log
thanks let me look into that log now
@FredBezies
sorry for not responding but i found the actual culprit for #14. it was never package names — plasma is a legit installable group. the real bug was in calamares itself.
we run TWO packagechooser instances (DE chooser + DM chooser, both using netinstall-add). upstream calamares tags all of that netinstall data with the same hardcoded "packageChooser" source string. so when the DM chooser writes its groups, it prunes EVERYTHING tagged packageChooser — including the DE's groups. result: KDE never makes it into packageOperations, nothing gets installed, and SDDM has no session to show. exactly the mess you saw.
the fix is a real source patch (we own the fork anyway), not a config workaround:
so the packages repo build is now calamares 3.4.2-9 (3.4.2-w0k3 for the funny factor, shows in About dialog + --version).
#13 stands: ntp-dinit added to the Init Services group.
local build of the patched calamares finished clean. once this is pushed and CI republishes [antergos-pkgs], a fresh ISO build should have both KDE installing and a correct clock. nothing you need to redo on your end — just retest when the new ISO drops.
if you have any problems in the new iso reopen the issue :3
alright! i think i fixed it closing this issue for now :3