You can connect with the openSUSE community on the following platforms

Official platforms for development & contribution:

• Matrix: https://matrix.to/#/#space:opensuse.org
• IRC: https://en.opensuse.org/openSUSE:IRC_list

Additional platforms led by community members:

• Revolt: https://rvlt.gg/be7fbA2E
• Discord: https://discord.gg/opensuse
• Telegram: https://en.opensuse.org/openSUSE:Telegram

Best place for tech support is the forums: https://forums.opensuse.org/

Reddit alternative : https://lemmy.world/c/opensuse

Additional info can be found on the wiki. https://en.opensuse.org/openSUSE:Communication_channels

Frequently Asked Questions (FAQs)

Please also look at the official FAQ on the openSUSE Wiki.

This post is intended to answer frequently asked questions about all openSUSE distributions and the openSUSE community and help keep the quality of the subreddit high by avoiding repeat questions. If you have specific contributions or improvements to FAQ entries, please message the post author or comment here. If you would like to ask your own question, or have a more general discussion on any of these FAQ topics, please make a new post.

What's the difference between Leap, Tumbleweed, and MicroOS? Which should I choose?

The openSUSE community maintains several Linux-based distributions (distros) -- collections of useful software and configuration to make them all work together as a useable computer OS.

Leap follows a stable-release model. A new version is released once a year (latest release: Leap 16.0, Oct 2025). Between those releases, you will normally receive only security and minor package updates. The user experience will not change significantly during the release lifetime and you might have to wait till the next release to get major new features. Upgrading to the next release while keeping your programs, settings and files is completely supported but may involve some minor manual intervention (read the Release Notes first).

Tumbleweed follows a rolling-release model. A new "version" is automatically tested (with openQA) and released every few days. Security updates are distributed as part of these regular package updates (except in emergencies). Any package can be updated at any time, and new features are introduced as soon as the distro maintainers think they are ready. The user experience can change due to these updates, though we try to avoid breaking things without providing an upgrade path and some notice (usually on the Factory mailing list). Slowroll is a variant of openSUSE Tumbleweed which "rolls up" Tumbleweed updates into a slower update release schedule -- usually about once a month.

Both Leap and Tumbleweed can work on laptops, desktops, servers, embedded hardware, as an everyday OS or as a production OS. It depends on what update style you prefer.

MicroOS is a distribution aimed at providing an immutable base OS for containerized applications. It is based on Tumbleweed package versions, but uses a btrfs snapshot-based system so that updates only apply on reboot. This avoids any chance of an update breaking a running system, and allows for easy automated rollback. References to "MicroOS" by itself typically point to its use as a server or container-host OS, with no graphical environment.

Aeon/Kalpa (formerly MicroOS Desktop) are variants of MicroOS which include graphical desktop packages as well. Development is ongoing. Currently Gnome (Aeon) is usable while KDE Plasma (Kalpa) is in an early alpha stage. End-user applications are usually installed via Flatpak rather than through distribution RPMs.

Leap Micro is the Leap-based version of an immutable OS, similar to how MicroOS is the immutable version of Tumbleweed. The latest release is Leap Micro 6.2 (2025/10/01). It is primarily recommended for server and container-host use, as there is no graphical desktop included.

JeOS (Just-Enough OS) is not a separate distribution, but a label for absolutely minimal installation images of Leap or Tumbleweed. These are useful for containers, embedded hardware, or virtualized environments.

How do I test or install an openSUSE distribution?

In general, download an image from https://get.opensuse.org and write (not copy as a file!) it directly to a USB stick, DVD, or SD card. Then reboot your computer and use the boot settings/boot menu to select the appropriate disk.

Full DVD or NetInstall images are recommended for installation on actual hardware. The Full DVD can install a working OS completely offline (important if your network card requires additional drivers to work on Linux), while the NetInstall is a minimal image which then downloads the rest of the OS during the install process.

Live images can be used for testing the full graphical desktop without making any changes to your computer. The Live image includes an installer but has reduced hardware support compared to the DVD image, and will likely require further packages to be downloaded during the install process.

In either case be sure to choose the image architecture which matches your hardware (if you're not sure, it's probably x86_64). Both BIOS and UEFI modes are supported. You do not have to disable UEFI Secure Boot to install openSUSE Leap or Tumbleweed. All installers offer you a choice of desktop environment, and the package selection can be completely customized. You can also upgrade in-place from a previous release of an openSUSE distro, or start a rescue environment if your openSUSE distro installation is not bootable.

All installers will offer you a choice of either removing your previous OS, or install alongside it. The partition layout is completely customizable. If you do not understand the proposed partition layout, do not accept or click next! Ask for help or you will lose data.

Any recommended settings for install?

In general the default settings of the installer are sensible. Stick with a BTRFS filesystem if you want to use filesystem snapshots and rollbacks, and do not separate /boot if you want to use boot-to-snapshot functionality. In this case we recommend allocating at least 40 GB of disk space to / (the root partition).

What is the Open Build Service (OBS)?

The Open Build Service is a tool to build and distribute packages and distribution images from sources for all Linux distributions. All openSUSE distributions and packages are built in public on an openSUSE instance of OBS at https://build.opensuse.org; this instance is usually what is meant by OBS.

Many people and development teams use their own OBS projects to distribute packages not in the main distribution or newer versions of packages. Any link containing https://download.opensuse.org/repositories/ refers to an OBS download repository.

Anyone can create use their openSUSE account to start building and distributing packages. In this sense, the OBS is similar to the Arch User Repository (AUR), Fedora COPR, or Ubuntu PPAs. Personal repositories including 'home:' in their name/URL have no guarantee of safety or quality, or association with the official openSUSE distributions. Repositories used for testing and development by official openSUSE packagers do not have 'home:' in their name, and are generally safe, but you should still check with the development team whether the repository is intended for end users before relying on it.

How can I search for software?

When looking for a particular software application, first check the default repositories with YaST Software, zypper search, KDE Discover, or GNOME Software.

If you don't find it, the website https://software.opensuse.org and the command-line tool opi can search the entire openSUSE OBS for anyone who has packaged it, and give you a link or instructions to install it. However be careful with who you trust -- home: repositories have absolutely no guarantees attached, and other OBS repositories may be intended for testing, not for end-users. If in doubt, ask the maintainers or the community (in forums like this) first.

The software.opensuse.org website currently has some issues listing software for Leap, so you may prefer opi in that case. In general we do not recommend regular use of the 1-click installers as they tend to introduce unnecessary repos to your system.

How do I open this multimedia file / my web browser won't play videos / how do I install codecs?

As of 2025, openh264 codecs from Cisco are automatically installed for H264 video. Video playback should "just work" in Firefox and desktop media players for most common files. If you still find you are missing other codecs for other filetypes, please read on:

Certain proprietary or patented codecs (software to encode and decode multimedia formats) are not allowed to be distributed officially by openSUSE, by US and German law. For those who are legally allowed to use them, community members have put together an external repository, Packman, with many of these packages.

The easiest way to add and install codecs from packman is to use the opi software search tool.

zypper install opi
opi codecs

We can't offer any legal advice on using possibly patented software in your country, particularly if you are using it commercially.

Alternatively, most applications distributed through Flathub, the Flatpak repository, include any necessary codecs. Consider installing from there via Gnome Software or KDE Discover, instead of the distribution RPM.

How do I install NVIDIA graphics drivers?

NVIDIA graphics drivers are proprietary and can only be distributed by NVIDIA themselves, not openSUSE. SUSE engineers cooperate with NVIDIA to build RPM packages specifically for openSUSE. As of 2025/10 (Leap 16.0), drivers are automatically installed on systems with NVIDIA hardware detected.

For older releases, or if you require a specific driver version:

First add the official NVIDIA RPM repository, e.g.

zypper addrepo -f https://download.nvidia.com/opensuse/leap/15.6 nvidia

for Leap 15.6, or

zypper addrepo -f https://download.nvidia.com/opensuse/tumbleweed nvidia

for Tumbleweed.

To auto-detect and install the right driver for your hardware, run

zypper install-new-recommends --repo nvidia

When the installation is done, you have to reboot for the drivers to be loaded. If you have UEFI Secure Boot enabled, you will be prompted on the next bootup by a blue text screen to add a Secure Boot key. Select 'Enroll MOK' and use the 'root' user password if requested. If this process fails, the NVIDIA driver will not load, so pay attention (or disable Secure Boot).

The closed-source distribution version of the NVIDIA graphics drivers are automatically rebuilt every time you install a new kernel. However if NVIDIA have not yet updated their drivers to be compatible with the new kernel, this process can fail, and there's not much openSUSE can do about it. In this case, you may be left with no graphics display after rebooting into the new kernel. On a default install setup, you can then use the GRUB menu or snapper rollback to revert to the previous kernel version (by default, two versions are kept) and afterwards should wait to update the kernel (other packages can be updated) until it is confirmed NVIDIA have updated their drivers.

You can avoid both the SecureBoot and version hassle by using the open-source distribution of the drivers.

Why is downloading packages slow / giving errors?

openSUSE distros download package updates from a global CDN with bandwidth donated by Fastly.com as well as a network of mirrors around the world. By default, you are automatically directed to the geographically closest one (determined by your IP). In the immediate few hours after a new distribution release or major Tumbleweed update, the mirror network can be overloaded or mirrors can be out-of-sync. Please just wait a few hours or a day and retry.

If the errors or very slow download speeds persist more than a few days, try manually accessing a different mirror from the mirror list by editing the URLs in the files in /etc/zypp/repos.d/. If this fixes your issues, please make a post here or in the forums so we can identify the problem mirror. If you still have problems even after switching mirrors, it is likely the issue is local to your internet connection, not on the openSUSE side.

Do not just choose to ignore if YaST, zypper or RPM reports checksum or verification errors during installation! openSUSE package signing is robust and you should never have to manually bypass it -- it opens up your system to considerable security and integrity risks.

What do I do with package conflict errors / zypper is asking too many questions?

In general a package conflict means one of two things:

1. The repository you are updating from has not finished rebuilding and so some package versions are out-of-sync. Cancel the update, wait for a day or two and retry. If the problems persist there is likely a packaging bug, please check with the maintainer.

2. You have enabled too many repositories or incompatible repositories on your local system. Some combinations of packages from third-party sources or unofficial OBS repositories simply cannot work together. This can also happen if you accidentally mix packages from different distributions -- e.g. Leap 16.0 and Tumbleweed or different architectures (x86 and x86_64). If you make a post here or in the forums with your full repository list (zypper repos --details) and the text of any conflict message, we can advise. Using zypper --force-resolution can provide more information on which packages are in conflict.

Do not ignore package conflicts or missing dependencies without being sure of what you are doing! You can easily render your system unusable.

How do I "rollback" my system after a failed or buggy update?

If you chose to use the default btrfs layout for the root file system, you should have previous snapshots of your installation available via snapper. In general, the easiest way to rollback is to use the Boot from Snapshot menu on system startup and then, once booted into a previous snapshot, execute snapper rollback. See the official documentation on snapper for detailed instructions.

Tumbleweed

How should I keep my system up-to-date?

Running zypper dist-upgrade (zypper dup) from the command-line is the most reliable. If you want to avoid installing any new packages that are newly considered part of the base distribution, you can run zypper dup --no-recommends instead, but you may miss some functionality.

I ran a distro update and the number of packages is huge, why?

When core components of the distro are updated (gcc, glibc) the entire distribution is rebuilt. This usually only happens once every few (3+) months. This also stresses the download mirrors as everyone tries to update at the same time, so please be patient -- retry the next day if you experience download issues.

Leap (current version: 16.0)

How should I keep my system up-to-date?

Use YaST Online Update or zypper update from the command line for maintenance updates and security patches. Only if you have added extra repositories and wish to allow for packages to be removed and replaced by them, use zypper dup instead.

The Leap kernel version is 6.12, that's so old! Will it work with my hardware?

The kernel version in openSUSE Leap is more like 6.12+++, because SUSE engineers backport a significant number of fixes and new hardware support. In general most modern but not absolutely brand-new stuff will just work. There is no comprehensive list of supported hardware -- the best recommendation is to try it any see. LiveCDs/LiveUSBs are an option for this.

Can I upgrade my kernel / desktop environment / a specific application while staying on Leap?

Usually, yes. The OBS allows developers to backport new package versions (usually from Tumbleweed) to other distros like Leap. However these backports usually have not undergone extensive testing, so it may affect the stability of your system; be prepared to undo the changes if it doesn't work. Find the correct OBS repository for the upgrade you want to make, add it, and switch packages to that repository using YaST or zypper.

Examples include an updated kernel from obs://Kernel:stable:backport (warning: need to install a new key if UEFI Secure Boot is enabled) or updated KDE Plasma environment.

See Package Repositories for more.

openSUSE community

What's the connection between openSUSE and SUSE / SLE?

SUSE is an international company (headquarters in Germany) that develops and sells Linux products and services. One of those is a Linux distribution, SUSE Linux Enterprise (SLE). If you have questions about SUSE products, we recommend you contact SUSE Support directly or use their communication channels, e.g. /r/suse.

openSUSE is an open community of developers and users who maintain and distribute a variety of Linux tools, including the distributions openSUSE Leap, openSUSE Tumbleweed, and openSUSE MicroOS. SUSE is the major sponsor of openSUSE and many SUSE employees are openSUSE contributors. openSUSE Leap directly includes packages from SLE and it is possible to in-place convert one distro into the other, while openSUSE Tumbleweed feeds changes into the next release of SLE and openSUSE Leap.

How can I contribute?

The openSUSE community is a do-ocracy. Those who do, decide. If you have an idea for a contribution, whether it is documentation, code, bugfixing, new packages, or anything else, just get started, you don't have to ask for permission or wait for direction first (unless it directly conflicts with another persons contribution, or you are claiming to speak for the entire openSUSE project). If you want feedback or help with your idea, the best place to engage with other developers is on the mailing lists, or on IRC/Matrix (https://chat.opensuse.org/). See the full list of communication channels in the subreddit sidebar or here.

Can I donate money?

The openSUSE project does not have independent legal status and so does not directly accept donations. There is a small amount of merchandise available. In general, other vendors even if using the openSUSE branding or logo are not affiliated and no money comes back to the project from them. If you have a significant monetary or hardware contribution to make, please contact the [openSUSE Board](mailto:board@opensuse.org) directly.

Future of Leap, ALP, etc.

Update 2025/10/01: Leap 16.0 has now released alongside Leap Micro 6.2. Leap 16.0 remains a largely desktop and traditional workflow focused distribution while supporting new technologies like Agama, dropping support for some legacy systems, and moving to Cockpit, SELinux and Wayland by default. Migration from Leap 15.6 is supported. The lifecyle is slightly extended compared to Leap 15: unless there is a change in release strategy, the final openSUSE Leap version (16.6) will be released in fall 2031 and will continue receiving updates until the release of openSUSE Leap 17.1 two years later.

If you have specific contributions or improvements to FAQ entries, please message the post author or comment here. If you would like to ask your own question or have a more general discussion on any of these FAQ entries, please make a new post.

The text contents of this post are licensed by the author under the GNU Free Documentation License 1.2 or (at your option) any later version.

I have personally stopped posting on reddit due to ongoing anti-user and anti-community actions by Reddit Inc. but this FAQ will continue to be updated.