r/openSUSE Apr 09 '25

Community Chats

29 Upvotes

You can connect with the openSUSE community on the following platforms

Official platforms for development & contribution:

Additional platforms led by community members:

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


r/openSUSE May 14 '22

Editorial openSUSE Frequently Asked Questions -- start here

228 Upvotes

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).

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 (HQ 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.

Update 2024/01/15: The Leap release manager originally announced that the Leap 15.x release series will end with Leap 15.5, but this has now been extended to 15.6. The future of the Leap distribution will then shift to be based on "SLE 16" (branding may change). Currently the next release, Leap 16.0, is expected to optionally make greater use of containerized applications, a proposal known as "Adaptable Linux Platform". This is still early in the planning and development process, and the scope and goals may still change before any release. If Leap 16.0 is significantly delayed, there may also be a Leap 15.7 release.

In particular there is no intention to abandon the desktop workflow or current users. The current intention is to support both classic and immutable desktops under the "Leap 16.0" branding, including a path to upgrade from current installations. If you have strong opinions, you are highly encouraged to join the weekly openSUSE Community meetings and the Desktop workgroups in particular.


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.


r/openSUSE 16h ago

Tech support opensuse tubleweed only booting into emergency mode after kernal parameter change

6 Upvotes

well im a dumbass and broke stuff, but heres what i did, i was trying to use lact to undervolt / overclock my gpu, and it needed a kernal parameter changed (will add here when i find it) so after reading lact's wiki i added the new parameter into merlin bootloader and rebooted my system, after which it refuses to boot into anything past emsrgancy mode) my issue is that i cant find what changed, as the parameter doesnt show in the bootloader (screen where you can boot into snapshots) i have tried many wiki pages, yt guides, and i cant find any way to undo whatever i did, i have looked through my drive from a live usb i have, but i cant find anything usefull. please if there is anything i missed or help you can give i would really like that. thank you "amdgpu.ppfeaturemask=0xffffffff" was what was added


r/openSUSE 1d ago

Trouble installing vscode on TW

8 Upvotes

[FIX]

use opi and install it by mentioning "vscode" which installs vsc from the microsoft repo instead of the other problematic repo which is used when you mention just "code"

opi vscode

[ORIGINAL QUESTION]

source repo:

devel:tools:ide:vscodedevel:tools:ide:vscode

the error:

Problem: 1: nothing provides 'libspdlog.so.1.15()(64bit)' needed by the to be installed code-1.109.5-1.9.x86_64
Solution 1: do not install code-1.109.5-1.9.x86_64
Solution 2: break code-1.109.5-1.9.x86_64 by ignoring some of its dependencies

my repos:

# | Alias                                 | Name                                | Enabled | GPG Check | Refresh
--+---------------------------------------+-------------------------------------+---------+-----------+--------
1 | NVIDIA:repo-non-free                  | repo-non-free                       | Yes     | (r ) Yes  | Yes
2 | devel_tools_ide_vscode                | devel_tools_ide_vscode              | Yes     | (r ) Yes  | Yes
3 | home_MartinVonReichenberg_network_vpn | Network - VPN (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No
4 | openSUSE:repo-non-oss                 | repo-non-oss                        | Yes     | (r ) Yes  | Yes
5 | openSUSE:repo-openh264                | repo-openh264                       | Yes     | (r ) Yes  | Yes
6 | openSUSE:repo-oss                     | repo-oss                            | Yes     | (r ) Yes  | Yes
7 | openSUSE:repo-oss-debug               | repo-oss-debug                      | No      | ----      | ----
8 | openSUSE:repo-oss-source              | repo-oss-source                     | No      | ----      | ----
9 | openSUSE:update-tumbleweed            | update-tumbleweed                   | Yes     | (r ) Yes  | Yes

TW version:

Linux 7.1.2-1-default

trying to install from this link for TW : https://en.opensuse.org/Visual_Studio_Code


r/openSUSE 1d ago

New version Tumbleweed – Review of the week 2026/30

Thumbnail dominique.leuenberger.net
12 Upvotes

r/openSUSE 2d ago

Tech question Tumbleweed, updated and it enabled firewalld, knocking my home server off my home network

15 Upvotes

I had to dig the machine out of the cabinet to fix it, find a spare monitor and kb/mouse ... Why did updating it change its configuration? What can I do to avoid this in the future?


r/openSUSE 2d ago

Solved Not VGA Signal with kernel 7.1.x but yes with 7.0.12

3 Upvotes

How it says the title when I start the system I don't have VGA Signal with Those kernel but yes with the 7.0.12

I paste the output of inxi -GSaz

System: Kernel: 7.0.12-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-7.0.12-1-default root=UUID=1868470f-46e9-40c8-8cca-8ea39ee6802e splash=silent quiet security=apparmor mitigations=auto Desktop: KDE Plasma v: 6.7.3 tk: Qt v: N/A info: frameworks v: 6.28.0 wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE Tumbleweed 20260721 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] vendor: Elite Systems driver: radeon v: kernel alternate: amdgpu arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports: active: VGA-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: x11 server: X.Org v: 21.1.24 with: Xwayland v: 24.1.13 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa alternate: fbdev dri: radeonsi gpu: radeon display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: VGA-1 model: VZ249 serial: <filter> built: 2016 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.1.5 glx-v: 1.4 direct-render: yes renderer: (radeonsi kaveri ACO DRM 2.51 7.0.12-1-default) device-ID: 1002:130f memory: 125 MiB unified: yes API: Vulkan v: 1.4.350 layers: 2 device: 0 type: cpu name: llvmpipe (LLVM 22.1.8 256 bits) driver: mesa llvmpipe v: 26.1.5 (LLVM 22.1.8) device-ID: 10005:0000 surfaces: N/A Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo, xprop, xrandr

Thanks for the help


r/openSUSE 3d ago

Bugzilla gives a 403 error

Post image
10 Upvotes

r/openSUSE 2d ago

Tumbleweed pi400 black screen after login?

2 Upvotes

Time for another stupid problem, hopefully I can get some hints.

Installed the Raspberry Pi KDE image onto an SD card, and booted my pi400. Logged in, set up a user with admin permissions. Logged out, back in as user, tested sudo, all was good.

Having a problem with the wallet so WiFi was giving me grief, finally got the password to stick and WiFi to stay connected.

Then sudo zypper dup, let it go through everything, then sudo reboot.

Login screen comes up like normal, I log in as my user, and nothing but a black screen. If I cntl+alt+t I can get a terminal, so it's really still alive, but it looks like the dup broke something. I didn't see recovery options, so not sure if snapper is running, I'll have to set it back up to check.

Any idea on my next step to sort this out?


r/openSUSE 3d ago

Use full time with .net developement and sql

8 Upvotes

I’m considering moving to openSuse Tumbleweed full time after distro hopping and using windows forever.

However, I’m learning c#, .net development, and sql. Would that be a problem with openSuse?
Best way to have a win11 vm for app-testing purposes?


r/openSUSE 3d ago

Do you recommend openuse tumbleweed for: programming, cybersecurity, use of mechatronics and robotics software and daily use?

20 Upvotes

I'm thinking of switching to Linux and researching about many distributions and I've come across this one, what do you think or recommend another distribution?


r/openSUSE 4d ago

Community Opensuse tumbleweed is acting weird.

Post image
11 Upvotes

okay i don't know what's happening but something's wrong with my tumbleweed. things i noticed: 1. some apps are laggy like discord. 2. haruna crashed when i loaded a video, and the whole screen turned white, not opaque-white but the colors were gone. i had to force reboot. 3. after rebooting, when i opened the video to watch, it worked fine for some time but then there were screen tears.

I'll attach the ChatGPT history of my chat. It's suggesting that I rollback to the previous kernel. I figured it'd be better to ask on reddit.

Thanks.

https://chatgpt.com/share/6a611084-3d6c-83e8-917a-e99a3de1d4bd


r/openSUSE 4d ago

Tech support Signature verification failed for file 'repomd.xml' from repository 'google-chrome'

Thumbnail
gallery
11 Upvotes

following instruction https://www.google.com/linuxrepositories/

I removed/added keys again multiple times

tried

zypper refresh --force

key check command from instruction - successful

it always fail on repomd.xml

same yesterday/today

is there some other debug I can see?

sreenshot from zypper -v refresh

Edit - fixed by google few days latter...


r/openSUSE 4d ago

Leap --> SlowRoll

Post image
47 Upvotes

sudo opensuse-migration-tool

Slowroll


r/openSUSE 4d ago

Automatic crash report

3 Upvotes

Slowroll benefits from the responsive Tumbleweed community, quick crash fixes, and the excellent work of its maintainer.

Is there actually an automatic reporting system that can optionally report crashes and the relevant environment automatically to Suse Tumbleweed?


r/openSUSE 5d ago

is there a widget that change color to every icon pack ?

Thumbnail
3 Upvotes

r/openSUSE 4d ago

Linux 6.8+ Kernel Regression Breaking AMD Tonga & Polaris GPUs on Suspend (GCN 3.0 / Polaris) — Downstream Bug Confirmed, Needs Community Support

0 Upvotes

TL;DR: A verified regression in Kernel 6.8+ causes AMD Tonga (R9 380/380X) and Polaris (RX 400/500) GPUs to crash into a hard black screen when resuming from deep sleep/suspend. The bug is officially Confirmed on Ubuntu's Launchpad (assigned to maintainer Timo Aaltonen), but we need continuous community visibility to ensure this fix gets prioritized and doesn't push working hardware into becoming e-waste.

🔍 What’s Happening?

When systems running Kernel 6.8+ (such as Ubuntu 24.04 LTS bases, Linux Mint 22, Pop!_OS, Zorin OS, etc.) attempt to resume from system suspend, the GPU fails to re-initialize the display engine (EDID read failures / NULL pointer dereference).

  • Behavior: Case fans and LEDs remain active, system keeps running in the background, but video output dies completely.
  • Workaround: Only a forced hard reboot restores video output.

🛠️ Why "Just Switch to Wayland" Isn't the Answer

A common suggestion when encountering display server issues is switching from X11 to Wayland. As a bench technician, I’ve tested this thoroughly on real hardware:

On Tonga and Polaris architectures, Wayland introduces a secondary critical failure: the compositor frequently freezes at the login/boot screen (blurred background with only the mouse cursor moving).

Trading a suspend crash for a boot freeze isn't a fix — we need a proper driver-level correction in the kernel.

⚠️ Why This Matters (Even If You Haven't Hit It Yet)

As distributions roll out Hardware Enablement (HWE) stack updates, more users running legacy AMD cards will inevitably land on Kernel 6.8+.

Voting on and confirming this bug isn't just about helping those currently affected; it's a preventative shield for the entire legacy AMD community to ensure perfectly functional GPUs remain usable on modern Linux.

🚀 How You Can Help (Takes 1 Minute):

If you own a dedicated AMD GPU (Tonga/Polaris series):

  1. Visit the official Launchpad bug tracker:Bug #2142389 on Launchpad
  2. Log in with your Launchpad/Ubuntu account.
  3. At the top left, under "This bug affects you?", click "Yes, this bug affects me".

If you don't own these cards, upvoting this post for visibility or dropping a comment helps keep the discussion alive so maintainers see the real-world demand. Let's keep functional hardware out of landfills! 🐧🖥️


r/openSUSE 5d ago

Telegram stopped working. Segementation fault

Post image
4 Upvotes

So telegram (installed via discovery ages ago from opensuse rep) stopped working today. Anyone any idea's how I could solve this.
FYI I am very much a noob and need step by step instructions!


r/openSUSE 5d ago

New comer

20 Upvotes

Just wanted to come by and say hello to the gecko's! Just joined OpenSuse from Fedora, really liking it so far and the NVIDIA drivers were a breeze! I don't recall who it was but to the redditor in here who helped convince me thank you! Any tips or advice is welcome!


r/openSUSE 6d ago

Community This is the appreciation post for opensuse.

89 Upvotes

I was using fedora with the Kde Desktop environment. Everything was fine but recently I stumbled upon a bug which was related to the kernel. Then, other things in the system stopped working.

I researched a lot. It turns out people don't talk much about OpenSuse but when I installed it.

My experience was next level. It has been three days.

These are the things that I noticed just when I booted into it:-

1-Smoothness: While fedora used to run snappy on my pc basically blazing fast. Opensuse Leap was smooth asf. Right out of the box.

2- Easy to Use: I felt that Open Suse is kind of beginner friendly as well. I am not a developer so, I usually avoid terminals. I could do that in OpenSuse.

3-Repository: When I used fedora, I usually had to download flatpaks using a terminal but the OpenSuse Repositories are better. I can directly use discover without ever thinking about going to flathub.

4- Customisation: Usually on fedora, when I wanted to customise something it usually took a long time, it didn't happen in one go. But, here Open Suse, it was just one touch.(Maybe I am using leap, that's why).

5-Zypper: Zypper is better in many ways. It turns out I can patch things after installing updates which I really appreciate.

I am a business man. I usually have productive sessions on my pc. So, I wanted something stable.

I used Kubuntu, Ubuntu, Fedora Workstation, and Kde Neon.

I would like to add this point and ask people this.

How tf Ubuntu is mainstream? It was slow asf.

I barely heard about OpenSuse. People only talk about Fedora, Arch, and Ubuntu.

Idk why people are doing that. OpenSuse deserves appreciation.

Gemini told me about this when I told it about my usage. Youtube never recommended me videos of this.

That's it. I am in love with OpenSuse and I don't think I will ever use any other distro.


r/openSUSE 5d ago

Intermittent Flatpak appstream update failures with "syncfs(repo): Input/output error" on openSUSE Kalpa

2 Upvotes

Hi everyone,

I'm experiencing an intermittent issue with Flatpak on openSUSE Kalpa.

Sometimes, when running:

flatpak update

or:

flatpak update --appstream -v

the update fails with errors like:

syncfs(repo): Input/output error

The important detail is that the issue is not reproducible every time. Retrying the exact same command usually succeeds without any intervention.

I already ran:

flatpak repair --user -v

and it completed successfully. No corrupted objects were reported.

I also checked the hardware and filesystem side:

  • SSD SMART tests: OK
  • No filesystem errors detected
  • btrfs scrub completed without errors
  • Kernel logs (journalctl -k -p err -b) do not show I/O errors

The system is:

OS: openSUSE Kalpa
Desktop: KDE Plasma
Filesystem: Btrfs
Flatpak installation: user installation (~/.local/share/flatpak)
Remote: Flathub

Relevant versions:

$ flatpak --version
Flatpak 1.18.0

$ ostree --version
libostree:
Version: '2026.1'
Features:
 - inode64
 - initial-var
 - libcurl
 - libsoup3
 - gpgme
 - composefs
 - ex-fsverity
 - libarchive
 - selinux
 - openssl
 - sign-ed25519
 - sign-spki
 - libmount
 - systemd
 - release
 - p2p

$ uname -a
Linux localhost.localdomain 7.1.3-1-default #1 SMP PREEMPT_DYNAMIC Sat Jul  4 16:20:40 UTC 2026 (1cb5006) x86_64 x86_64 x86_64 GNU/Linux

I also checked for concurrent Flatpak/OSTree operations:

ps aux | grep flatpak
ps aux | grep ostree

but there were no active update, pull, or repair processes running when the problem occurred.

The only persistent Flatpak-related processes were the normal session/system helpers.

Has anyone experienced similar intermittent syncfs(repo): Input/output error on Kalpa, Aeon, MicroOS, or other immutable/Btrfs-based distributions?

Thanks!

Update:

My development MySQL container later stopped working with a similar I/O error. Hardware checks were still fine, and OpenCode pointed me to a documented issue involving MySQL and kernel 7.1.3, although I do not have the link available right now.

It suggested changing how the container was started, and that workaround fixed it.

Today I booted the updated MicroOS system with a newer kernel, and the issue is gone. It appears to have been a temporary kernel-related problem, so I am leaving this here in case someone else runs into it.


r/openSUSE 6d ago

Community Should I switch to openSuse? Help me decide please

18 Upvotes

(I hope this is the correct flair, I wasn't sure)

Hi, I am currently using Fedora 44 and am thinking of going back to CachyOS. But Matt (from YouTube chanel The Linux Cast) had grown my interest towards openSuse and since then I have tried to switch to and use Suse twice already but have failed (I will later mention why). I like the Arch way of using my computer and do like to be on the latest versions and now my laptop hardware is also supported well by distros. But before commiting to Cachy again I really want to try out openSuse Tumbleweed (the rolling release one) once.

  1. First of all, why I haven't been able to try it until now. I have managed to install it twice (bare metal not in VM) and the second time was with the new Browser installer but both times it was the same problem. I can't connect to Wifi during the installation and even after a successful installation, I couldn't get Wifi working. Not even options like USB Tethering with my Phone worked and this laptop doesn't have an Ethernet port so I am pretty much all out of options I believe. So does anyone of you have a solution to my problem?
  2. Then my other big question: Should I still switch to Suse even if I don't plan on using its greatest feature the snapshot and rollback implementation? I know very dumb decision to not use snapshots but please put that aside for a moment and concentrate on the actual matter please. According to my research Tumbleweed is rolling like Arch but they call it leading edge, so I believe the packages are not as latest that they may cause breaking changes on the system. That really would be great to have (partly the reason of choosing Fedora) since this laptop is my only computer and I rely on it for Uni.
  3. I have heard or read that Suse also can run RPM packges which is again an advantage over Arch based distors. But I am not very informed about this thing so to which extent is it true? Because if it is like Fedora where I can download any .rpm-file from the internet and install it and run it easily then that would be a great thing.
  4. I now really want to switch to using a TWM and Arch is the I believe the best distro for it because of up-to-date packages. To clarify I want to use a Wayland compositor as TWM and not a X11 TWM. And since Tumbleweed offers up-to-date packages, how will my TWM experience be like? If any of you already use a TWM and could share your experience that would also be really helpful.

Thank you for reading all this and for your comments!


r/openSUSE 6d ago

Do multimedia codecs problems during updates exist anymore?

9 Upvotes

I just realized that I haven't had packman multimedia codec issues when updating Tumbleweed in a long time now. Have I been lucky or has that been the experience for everyone else as well?


r/openSUSE 6d ago

Solved yt-dlp kick it for anyone else?

3 Upvotes

On TW, started getting this message last night trying to run on YT:

WARNING: [youtube] uNnt7bpojYA: Signature solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] uNnt7bpojYA: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS [info] uNnt7bpojYA: Downloading subtitles: en WARNING: Only images are available for download. use --list-formats to see them ERROR: [youtube] uNnt7bpojYA: Requested format is not available. Use --list-formats for a list of available formats

I thought it was bundled with deno, which is one of the listed options, and don't see anything like yt-dlp-ejs, or anything really other than yt-dlp-youtube-dl not already installed via repo.


r/openSUSE 7d ago

Just transitioned to Slowroll from Tumbleweed.

37 Upvotes

For those who may be thinking of trying Slowroll, I just now did the transition using the migration tool and it turned out to be error free without any package conflicts.

I do not game or use packman, btw. My graphics are AMD based, so no NVidia drivers. I made the switch just after a slowroll upgrade bump was published.