plasma-branding-Kalpa-20260530-1.1 does not wok on my Kalpa

English Install/Boot/Login
1

Hello, only to report, since i overcame my actual issue booting in a previous working snapshot. Yesterday new system snapshot updated ‘plasma-branding-Kalpa-20250926-1.2’ with ‘plasma-branding-Kalpa-20260530-1.1’. At today boot, system does not present the login screen, it is fully black with a mouse pointer (that can move), but no way to have the login to insert the credentials.
As said, i temporary solved booting in a previous running snapshot. Is it only my problem or any other Kalpa users noted the same ? Thanks.

2

All my Kalpa installs broke as well. Looks like an issue cutting over from MicroOS to a dedicated Kalpa product.

Basic steps to complete it, will vary depending how it was originally set up

  1. At a tty go to /etc/products.d and fix the baseproductsymlink to point at Kalpa.prod and reboot. If Kalpa.prod doesn’t exist then jump to 3 and fix it after installing the packages but before rebooting.
  2. Your system should still be ‘broken’ but from here log into a tty and execute a transactional-update dup
  3. You’ll know if you’re fixed as SDDM will now have a turtle background. If SDDM still doesn’t look right you’ll probably have to install a few packages manually through transactional-update shell
  • kalpa-themes-sddm
  • kalpa-themes
  • patterns-kalpa-base

When resolving conflicts remove anything related to Opensuse-branding and MicroOS.
Exit and reboot. This should finish the transition, run a final transactional-update dup just to make sure.

Be aware that the KDE theme defaults will have changed so if you liked Breeze you’ll need to switch back to it in system settings.

3

@xanders Don’t use shell, use run or just pkg install, then can run apply (maybe) else reboot…

Maybe @sfalken can advise further…

4

Yes, there is potentially breakage that will be caused, with the new plasma-branding-Kalpa, patterns-kalpa and kalpa-themes as I work towards a beta release.

I ran as much testing as I could, but obviously there are things that got missed.

@xanders advice is mostly ok, except for step 3.

I advise running transactional-update dup -i which will put your dup transaction into “interactive” mode, and allow you to resolve conflicts.

I will be around all day, and as always, I’m in the Kalpa matrix channel for questions/troubleshooting https://matrix.to/#/#kalpa:opensuse.org

1 Like
5

thanks to all for the info, updates, suggestions.
Frankly speaking, I prefer to wait for an ‘official snapshot’ that could fix this issue, instead of do myself manual change. My system is anyway running good, just using a previous snapshot, as said. Again thanks.

6

There’s no way around having to do some manual intervention with this change, unless you wish to reinstall.

7

understood. thanks

8

I’m doing back up of some documents, files before starting to try fixing the issue, as by above hints. Some questions arose, in the meantime:
1- I do not have Kalpa.prod under /etc/products.d . will it be created after the ‘transactional-update dup -i’ ? Is it mandatory to have this file and change the symlink to point at it (instead of baseproduct)?
2 - these changes apply just for the running snapshot or to all snapshots? To know if, doing something wrong, I screw up my full system or just the running snapshot.
3 i also joined the matrix channel as suggested by sfalken
thanks

9

Do you have Kalpa-releaseinstalled? that is the package that provides /etc/products.d/Kalpa.prod

This will apply to every snapshot after making these changes

1 Like
10

thanks for the provided clarifications.
I will install ‘Kalpa-release’ as first step, thank you

11

the changes were successful, my Kalpa system is fully back :slight_smile:
Thanks to You all for the given support