Free tools Windows power users keep installed
One-click scans. No signup required.
If you use openSUSE Leap’s transactional system role, install and update software with transactional-update, not ordinary YaST or direct Zypper package management. Its root filesystem is read-only, and changes are made transactionally rather than applied immediately. First identify your Leap release and system role: not every Leap installation is immutable, and the commands documented for Leap 15.6 should not automatically be assumed to apply to every release.
Identify your Leap release and system role first
Before changing packages, establish which release is installed and whether the machine is using the transactional, read-only-root role. The official transactional-role instructions cited here are for Leap 15.6; check the documentation for your installed release if its commands or behavior differ. Release and repository compatibility also matter, particularly when upgrading between releases. See the openSUSE Leap Start-Up documentation.
Keep the complete output from the failed command, along with the release, system role, enabled repositories, and command you ran. Without the exact error, it is not possible to tell whether the cause is a missing package, repository or connectivity issue, signature warning, dependency conflict, or another problem.
Choose the package-management path for your system
| System setup | Package-management path | How changes take effect | Recovery approach |
|---|---|---|---|
| Leap 15.6 transactional system role | transactional-update for software management, rather than YaST or direct Zypper management |
Changes target a system snapshot; follow the reboot or boot flow to use the new state. Automatic restart behavior depends on local configuration. | transactional-update rollback, following the release-note instructions |
| Ordinary Leap installation | Use the supported Zypper or YaST workflow for that installation | Do not assume the transactional snapshot and reboot behavior applies. | For Btrfs/Snapper setups, use the appropriate Snapper workflow; this is distinct from transactional-update rollback. |
The openSUSE Leap 15.6 Release Notes say: “To work with transactional updates, always use the command transactional-update instead of YaST and Zypper for all software management.” That guidance is specifically for the transactional system role, where immediate-write assumptions do not apply.
Recommended Free Tools
#1 Best Overall
Install, remove, or update software in the transactional role
For the documented Leap 15.6 transactional role, run the relevant command below. Replace PACKAGE_NAME with the package’s actual name; these commands do not establish that a package exists for every Leap release or repository.
sudo transactional-update upupdates the system using the regular-release update method.sudo transactional-update pkg in PACKAGE_NAMEinstalls a package.sudo transactional-update pkg rm PACKAGE_NAMEremoves a package.
These operations work transactionally. Once a change completes, follow the machine’s boot or reboot notification to make the new snapshot active. The Leap 16.0 transactional-update configuration manual describes configurable reboot methods: behavior can use rebootmgr or fall back to systemd, while a none setting leaves rebooting to the operator. Check your local configuration rather than assuming a transaction will restart the machine automatically.
If Zypper says the filesystem is read-only
On the transactional role, a read-only root is expected; it is not by itself proof that the system is broken. Do not switch to direct Zypper or YaST package management to force an immediate change. Use the transactional commands documented for your installed release. If you did not intend to use a read-only-root system, confirm the system role and consult the instructions for that Leap release before changing package-management settings.
If Leap cannot find a package or reports a repository problem
For an ordinary Zypper setup
If a package should be available from a configured repository but is not found, the Leap 15.6 reference recommends refreshing repository metadata:
Rank #3
- openSUSE is a Linux-based operating system for your PC, Laptop or Server. You can surf the Web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!
- You can surf the Web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!
- Run
zypper refresh. - If that does not resolve the issue, run
zypper refresh -fdbto force a complete refresh and rebuild, including raw metadata. - Check that the relevant repository is enabled, compatible with your Leap release, reachable, and actually supplies the package.
These are ordinary Zypper troubleshooting steps, not instructions to bypass transactional-role package management. For a transactional system, verify and use the supported workflow for that role and release. The Leap reference on managing software with command-line tools covers Zypper, repositories, and metadata refresh.
When refresh does not explain the error
A refresh is relevant to stale or incomplete repository metadata; it is not a general fix for every installation failure. Check the full command output before attributing a package error to metadata. A package may not be supplied by any enabled repository, or its repository may not match the installed Leap release. The Start-Up documentation discusses checking release and repository compatibility, including third-party repositories, during release upgrades.
Do not use a distribution upgrade command as a generic repair
The Leap 16.0 configuration manual distinguishes up, which uses zypper up and is intended for regular releases such as Leap, from dup, intended for rolling distributions such as Tumbleweed. An update failure on Leap is not, by itself, a reason to switch to dup. Confirm your release and local configuration before changing update methods.
Undo a failed transactional update carefully
The Leap 15.6 Release Notes document transactional-update rollback for the transactional system role. Their procedure requires booting into the next-to-last snapshot first; you may optionally supply a snapshot ID. Follow the release-note procedure for your system rather than treating rollback as a universal fix for package errors.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
On an ordinary Leap installation using Btrfs and Snapper, snapshot recovery is a related but separate mechanism. Zypper can create snapshots around filesystem changes, so use the Snapper workflow appropriate to that setup instead of conflating it with transactional-update rollback. The Leap command-line reference covers Btrfs and Snapper.
Treat repository signing-key warnings as a security decision
Do not automatically trust an unfamiliar signing key just to get an installation or update through. The transactional-update configuration manual says automatic import of keys for new repositories is disabled by default for security reasons. Verify the repository’s identity and the key’s provenance before deciding whether to trust it; a signature prompt is not a generic error to dismiss.
Quick Recap
Official documentation
- openSUSE Leap 15.6 Release Notes — transactional system-role package management and rollback.
- openSUSE Leap 15.6 Reference: Managing software with command line tools — Zypper, repositories, refresh, and Btrfs/Snapper.
- transactional-update.conf(5), Leap 16.0 manual — update method, reboot behavior, and repository key-import settings.
- openSUSE Leap 15.6 Start-Up documentation — release and repository checks in upgrade contexts.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
