The YaST Qt interface is started by default when using the desktops KDE, icewm, and others. It is also used when invoking YaST from a remote terminal. Start the software manager from the YaST Control Center by +
![]() |
The YaST software manager can install packages or patterns from all currently-enabled repositories. It offers different views and filters to make it easier to find the software you are searching for. Change the view by clicking and selecting a view listed below. The selected view opens in a new tab.
The package search interface is the default view of the software manager. Enter a search term and press Enter. Refine your search by specifying where to and by changing the .
Lists all patterns available for installation on your system.
Lists all packages sorted by groups such as , , or .
Lists all packages sorted by groups and subgroups, for example ++.
Filter to list packages by repository. In order to select more than one repository, hold the Ctrl key while clicking on repository names. The “pseudo repository” lists all packages currently installed.
Filter to list all packages needed to add a new system language.
![]() | Finding Packages Not Belonging to an Active Repository |
|---|---|
To list all packages that do not belong to an active repository, choose ++ and then choose +. This is for example useful if you have deleted a repository and would like to make sure no packages from that repository remain installed. | |
Search for packages as described in Section 3.2.1, “Searching Packages or Patterns”.
The packages found are listed in the right pane. Select a package for installation or removal by right-clicking it and choosing or . If the relevant option is not available, check the package status indicated by the symbol in front of the package name—hit Shift+F1 for help.
![]() | Applying an Action to All Packages Listed |
|---|---|
To apply an action to all packages listed in the right pane, choose an action from +. | |
To install a pattern, right-click the pattern name and choose . It is not possible to delete patterns.
If your choice results in a dependency conflict that cannot be automatically solved, you need to manually solve this conflict as described in Section 3.2.3, “Checking Software Dependencies”.
In order to select more packages, repeat the steps mentioned above. Once you are finished click to start the installation.
![]() | Reviewing the Package Selection |
|---|---|
YaST maintains a list with all actions that will be carried out when starting the installation. To review this list, choose +. By default, all packages that will change status, are listed. Use the check boxes under to filter these list. Hit Shift+F1 for details on the status flags. In order to revert the status for a package, right-click it and select if the package was scheduled to be deleted or updated, or if it was scheduled for installation. To abandon all changes and close the software manager, click and | |
Certain packages are dependent on other packages, such as shared libraries. YaST automatically resolves these dependencies. On the other hand, some packages cannot co-exist with others on the system. In this cases, a list of packages that have automatically been chosen for installation, update or removal is presented. Accept them by clicking continue.
Once all selected packages are installed or removed, the YaST package manager automatically terminates.
![]() | Installing Sources |
|---|---|
Installing source packages with the YaST software manager is not possible at the moment. Use the command line tool zypper for this purpose. For more information, see Section 7.1.2.1, “Installing Source Packages”. | |
![]() | Updating packages |
|---|---|
To update all packages from a certain repository, choose the repository as described in Section 3.2.1, “Searching Packages or Patterns” and then choose ++. To update all installed packages, choose ++ Choosing instead of will “update” all selected packages to the version from the repository with the highest priority, even if this means actually downgrading the package. This option is for example useful to ensure that the package selection will originate from a certain repository. | |
Most packages are dependent on other packages. If a package, for example, uses a shared library, it will be dependent on the package providing this library. On the other hand some packages cannot coexist with each other (you can for example only install one mail transfer agents, sendmail or postfix), causing a conflict. When installing or removing software, the software manager makes sure no dependencies or conflicts remain unresolved, hence ensuring system integrity.
In case there is just one simple solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved automatically. If solving a conflict involves a vendor or architecture change, it also needs to be solve manually. Once you start the installation by clicking , you will get an overview of all actions triggered by the automatic resolver which you need to confirm.
By default, dependencies are automatically checked. A check is performed every time you change a package status (for example by marking a package for installation or removal). This is generally useful, but can become cumbersome when manually resolving a dependency conflict. To disable it, uncheck +. Manually perform a dependency check with +. A consistency check is always performed when you confirm your selection with .
To review a package's dependencies, right-click it and choose . A map showing the dependencies opens. Packages that are already installed are displayed in a green frame.
![]() | Manually Solving Package Conflicts |
|---|---|
Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, the software manger, all your changes and start again. | |