Who is openSUSE Kalpa for?
It is NOT for everyone. Your highly customizable Tumbleweed & Leap Desktops are Safe and will remain the best choice for those who want to tinker with their Desktop.
It should be perfect for lazy developers, who no longer want to mess around with their desktop and just ”get stuff done”, especially if they develop around containers.
It should also appeal to the same audience now more used to an iOS, Chromebook or Android-like experience where the OS is static, automated & reliable and the Apps are the main thing the user cares about.
To deep dive on the origins and WHY openSUSE Aeon/Kalpa check out the following workshop:
Kalpa should be reliable, predictable & immutable, just like openSUSE MicroOS.
Kalpa should be less customizable than regular openSUSE Tumbleweed/Leap.
Kalpa should be small, but not at the expense of functionality. Printing, Gaming, Media Production and much more should all work.
Kalpa should just work “out of the box” without the need for additional configuration to get key functionality like software installation and web browsing working. All features offered by default should work - features that don't work shouldn't be offered/visible/available to users.
How to Download and Install
- Installation media is currently only available under the projects old name of 'MicroOS Desktop'
- Download the openSUSE MicroOS base ISO image from https://en.opensuse.org/Portal:MicroOS/Downloads
- Write the ISO on a USB drive and start the installation process.
Ways to Install Applications in Order of Preference
Now that you have installed Kalpa, you probably want to install software.
Because it provides only a minimal base system with a Desktop Environment, it is designed to come with only basic configuration tools by default.
For this reason, All Applications, Browsers, Codecs needed for specific apps, etc are provided by flatpaks from Flathub.
To make this process even easier for users, the Flathub repository of all available flatpaks have been integrated with Discover. This way, you can simply search and find all your favorite apps in a seamless and integrated way.
While there are other ways to install software, it is important to remember that it is STRONGLY recommended to install software in the following order of preference:
- Flatpaks from your software center of choice or Flathub
- RPM's in a user distrobox distrobox-enter
- RPM's in a root distrobox distrobox-enter -r
- RPM's via transactional-update -- for drivers, kernel modules, strictly what you need for your host operating system to work.
To reiterate: EVERYTHING should be done via flatpaks or be installed in a distrobox if a package is not available as a flatpak. Using transactional-update is strictly what you need for your host operating system to work (exotic drivers, specialized vpn services).
Note: distrobox is shipped by default w/ Kalpa. It allows users to install any linux distribution inside your terminal. For those who want to run GUI apps via a distrobox can do so with a special export command so that apps feel more native and integrated with the system. Check out the [distrobox section] to learn more about this convenient way to launch distrobox based apps from your host menu launcher.
An Introduction to transactional-update
openSUSE Kalpa does not use zypper like openSUSE Tumbleweed or openSUSE Leap to install RPM packages and use them directly. openSUSE Kalpa uses transactional-update with zypper under the hood.
Most of the time, you should not need to use any of these commands interactively, as Kalpa has automatic system updates via a the transactional-update.service systemd service.
transactional-update - Example Commands
Commands for transactional-update are listed below. NOTE: Remember to reboot after the command is finished to see the changes!
- sudo transactional-update pkg install package_name install a rpm package
- sudo transactional-update pkg remove package_name remove an rpm package
- sudo transactional-update dup perform a system upgrade to the next release
- sudo transactional-update shell open a shell of the next snapshot (you can use zypper commands there). This should only be used for debugging purposes. Any bug report that can only be reproduced by using transactional-update shell is almost certain to be closed as WONTFIX.
- sudo transactional-update rollback snapshot_number roll the system back to the numbered snapshot. Use 'last' instead of the snapshot number to roll back to the last working snapshot. Do not use snapper for rollbacks.
transactional-update - Automatic Update
By default transactional-update.timer handles automated system updates. This is set to daily which means that the task will be executed each day at 00:00:00.
In the event this might be at a time when the computer is off, as the timer is set to Persistent=true, then the update will then take place the first chance it can.
Some of the reasons why it may not be able to trigger an update could be:
- the computer was off
- the internet connection was disturbed - at time it is scheduled to.
To avoid automated reboots:
Please check the Troubleshooting part Unexpected reboot
This should not cause issues due to the way transactional-update works since the new packages are installed on a new snapshot for which to take effect you must reboot.
To track if transactional-update is able to upgrade, and run correctly you can use journalctl:
$ sudo journalctl -u transactional-update.service
You can also use journalctl with the -f flag to tail the logs in real time.
transactional-update - --Final Words About Snapshots and Boot Behavior
By default, each transactional-update command produces a seperate, self-contained, snapshot that includes the changes requested by the transactional-update command.
This snapshot is BASED ON THE LAST KNOWN GOOD/BOOTED SNAPSHOT. The last of the snapshots produced by multiple transactional-update commands then takes effect when rebooting.
In other words sudo transactional-update pkg install $pkg1 followed by sudo transactional-update pkg install $pkg2 and then rebooting results in a system that has $pkg2 installed, but NOT $pkg1.
This is the expected, and sensible default behaviour - Kalpa always wants to move from the last known good/booted snapshot to it's new state in the smallest, least disruptive way possible.
This is especially sensible when you think the default/expected behaviour is that Kalpa updates itself automatically and most users should not be using transactional-update interactively at all. With transactional-update dup happening regularly in the background automatically, Kalpa wants to make sure it's updating only to the latest clean system update state, not some weird hybrid of previous unbooted, unchecked, intermediate transactional-update dup that never got booted.
However, when ignoring this best practice and using transactional-update interactively, there may be times where you wish to run transactional-update against an existing unbooted, unknown-if-good snapshot.
For this use transactional-update --continue
sudo transactional-update pkg install $pkg1 followed by sudo transactional-update --continue pkg install $pkg2 will install $pkg1, then $pkg2 in the same snapshot that included $pkg1, marking that combined snapshot as the next boot target.
If problems occur however, there is no additional complexity figuring out whether it was $pkg1 or $pkg2 that broke anything, as users will need to rollback to the snapshot before $pkg1 was installed to return to the last known good state.
KDE Discover + Flathub Integration
KDE is currently in an ALPHA stage.
- In Discover, the Flathub repository is enabled upon first login, and some flatpaks are installed by default (Mozilla Firefox and kCalc), kate (text-editor) is still provided via RPM in the base image (it is not fully operable via flatpak as of yet).
- Note: For theming, normal global theme installations don’t work in KDE Plasma, you can however install components directly via discover.
Adding Additional Repositories
To add repositories run zypper as usual:
# sudo zypper ar -g -r <REPO-URL>
Then refresh with:
# sudo transactional-update
Packages will now be available from `transactional-update`.
Distrobox can be used like toolbox (which is included on the server version of MicroOS by default), but has some other advantages for desktop usage. Please refer to https://github.com/89luca89/distrobox for all options.
This section describes known issues on openSUSE Kalpa and their solutions.
Set your hostname with the following command:
# sudo hostnamectl set-hostname <new name>
Reboot and hostname change will take effect.
Depending on your daily use case, the Timer may not trigger the automatic update process successfully even with persistent=true because it adds a randomized delay at each boot with RandomizedDelaySec=
If you want automatic daily updates to your system, you may find that you need to adjust that delay mentioned.
Edit transactional-update.timer (creates override.conf)
# sudo systemctl edit transactional-update.timer
Edit the line under the [Timer] section -
The example above is for a randomized delay of max 5 minutes. (Default value is 2h)
Change the time to your use case. You can use this as reference.
Due to the nature of openSUSE Kalpa being tied to openSUSE Tumbleweed at present, we suffer from the same bug that Tumbleweed does when it comes to setting up Printers in the Plasma Desktop. YaST is not present within openSUSE Kalpa, so doing it using YaST is also not possible.
To setup your printers:
- Open Firefox (or other web browser) and navigate to http://localhost:631
- Click on `Administration` in the top bar
- Click on `Add Printer`
- User will be `root` and you will need to enter your root password
- You should now be able to setup your printers.
Please see: https://bugzilla.opensuse.org/show_bug.cgi?id=1192461 and https://bugzilla.opensuse.org/show_bug.cgi?id=1212995 for further information.
Steam Proton, Bottles, WINE, Lutris, not working from flatpaks
If you run into issues using WINE, and WINE based programs in flatpaks, it is likely due to an SELinux issue, and can be checked by running:
# sudo getsebool selinuxuser_execmod
If that returns 'selinuxuser_execmod --> disabled', you will need to enable it. This can be done temporarily (resets on next boot) with
# sudo setsebool selinuxuser_execmod 1
Or can be set Persistent with:
# sudo setsebool -P selinuxuser_execmod 1
The openSUSE Security team is reviewing this default policy, and you are enabling this at your own risk. See https://bugzilla.opensuse.org/show_bug.cgi?id=1206292 for further information.
Team Fortress 2 missing audio
If you run into audio issues with Team Fortress 2, it is likely due to an SELinux issue, and can be checked by running:
# sudo getsebool selinuxuser_execheap
If that returns 'selinuxuser_execheap --> disabled' you will need to enable it. This can be done temporarily (resets on next boot) with
# sudo setsebool selinuxuser_execheap 1
Or can be set Persistent with:
# sudo setsebool -P selinuxuser_execheap 1
Android Studio emulator not working from flatpak
If you run into issues using Android studio emulator in flatpaks, it is likely due to an SELinux issue, and can be checked by running:
# sudo getsebool selinuxuser_execstack
If that returns 'selinuxuser_execstack --> disabled' you will need to enable it. This can be done temporarily (resets on next boot) with
# sudo setsebool selinuxuser_execstack 1
Or can be set Persistent with:
# sudo setsebool -P selinuxuser_execstack 1
The openSUSE Security team is reviewing this default policy, and you are enabling this at your own risk. See https://bugzilla.opensuse.org/show_bug.cgi?id=1206789 for further information.
Place for questions
- Telegram: https://t.me/openSUSE_kalpa
- Matrix: https://matrix.to/#/#kalpa:opensuse.org
- Discord: https://discord.gg/openSUSE
Telegram, Matrix and Discord are all bridged with each other, so conversation will flow cross-platform
For "official", up to date news about Kalpa development
- Mastodon: https://fosstodon.org/@kalpa