How-to guides
Apps and updates
Manage packages and understand the difference between updating the system and upgrading to a new version.
Install apps with Vega
Open Vega and go to the software area. Search for the app, check its source and review the operation before confirming. Vega manages RPM packages via Zypper and Flatpak apps when that support is available.
RPMs are part of the distribution's package system. Flatpaks use their own repositories and runtimes. The same app may appear from more than one source; choose the one you intend to keep to avoid duplicate installations.
On the Desktop, the Software area also has three showcases with cards to install the most wanted apps in one click: Popular (browsers, chat, music and video, creative tools, office, games and utilities), Developers (languages, build tools, IDEs, containers and databases) and Windows apps. Cards for apps that are already installed are disabled. Microsoft Edge and .NET come from Microsoft's official repository: on the first install, Vega adds the repository and shows the signing key for you to approve.
Enable Flatpak and Flathub
Flatpak is not installed by default. In Vega → Software, click Enable Flatpak. Flathub apps then show up in the search and in the showcases.
For administrators, installing, updating and removing Flathub apps through Vega does not ask for a password: Flatpak itself authorizes it through your session. On computers with supervised accounts, read the Parental controls guide first.
Windows programs
First, look for a native alternative: there is almost always a Linux version or an equivalent program. For Windows programs, use Vega → Software → Windows apps on the Desktop:
- Click Enable Windows apps. Vega installs Wine, Winetricks and 7-Zip, and also Bottles if Flatpak is enabled.
- If you see 32-bit program support is off, click Turn on 32-bit support and restart. The openSUSE Leap 16 kernel ships with this support turned off by default to reduce the attack surface, and almost all Windows programs need it. Vega adds
ia32_emulation=1to the boot parameters, with a snapshot. - Install the listed programs in one click, with no password. For any other program, use Run a Windows program and choose the
.exeor.msiinstaller downloaded from the vendor's site.
The programs stay in your account, in a Wine environment of Vega's own, and show up in the applications menu. Listed programs are removed with the Remove button on their card. Not every program works in Wine: check compatibility at appdb.winehq.org. Programs with anti-cheat, banking security modules and programs that depend on their own drivers usually do not work.
Update the installed system
- Connect the computer to the network and to a power source.
- Open the Vega updates area and refresh the list of available updates.
- Read the summary and confirm the changes you want.
- Wait for the result. Restart if the tool asks you to or if an update needs a new boot to take effect.
If you prefer the terminal, the update flow for RPM packages is:
sudo zypper refresh
sudo zypper update
The first command refreshes the repository metadata; the second presents the updates for confirmation. They do not update Flatpak apps. Do not run another package operation through Vega at the same time.
Take care of package sources
Keep the repositories that match the base of your installation. Do not add repositories from another Leap version to get a single package. If an unknown key or an unexpected change of source appears, check the project's announcement before accepting.
Updating is not upgrading to a new version
16.1 is supported only as a fresh installation: there is no migration path from the test releases or from the Leap 16.0 base (see the 16.1 limits). Do not change the repository addresses or use a distribution upgrade as a shortcut.
Backup and recovery
Keep your important files on another device before major changes. Snapshots, when configured, help recover the system, but they do not replace an independent copy of the data. Server 16.1 uses ext4 and does not offer the Desktop's Snapper rollback flow.
References: management with Vega and 16.1 limits (in Portuguese).