For some applications, fuse mount via GVFS are not practical, for example when using wine via Bottles.
In the past I solved this using a CIFS mount via /etc/fstab but this is not really possible with Aeon except using transactional-update shell which is a big no-no according to the documentation.

How can I solve this the Aeon way?

I"m in the process of setting up a new Tumbleweed installation and I"ve set the correct resolution / font size in KDE but the login screen remains tiny. I've been looking online for advice and all I can find is adding certain strings into /etc/sddm.conf or /etc/sddm.conf/d/kde_settings.conf but on my installation neither of these exist. Can someone point me in the right direction please?

I've been running MicroOS for more than a year, with no issues. The system is set to update itself every sunday morning and reboot itself via rebootmgr at 2:30 UTC. The system was set up as minimal and then docker-ce and assorted dependencies. The machine is set up as a single node swarm and runs about 15 containers.

After the update and reboot on Sunday Jan 26th I started getting all sorts of stack traces from docker a few times each day. The dockerd process timedout while talking to the leader (itself?).
I've rolled back to the state as it was on Sunday Jan 19th and disabled automatic updates.

Here's a list of the updated packages on the infamous Jan 26th update:

The following 63 packages are going to be upgraded:

MicroOS-release MicroOS-release-appliance NetworkManager NetworkManager-bluetooth NetworkManager-wwan btrfsmaintenance ca-certificates-mozilla chrony chrony-pool-openSUSE coreutils coreutils-systemd device-mapper dracut glibc glibc-gconv-modules-extra glibc-locale glibc-locale-base iproute2 kernel-default kexec-tools lastlog2 libblkid1 libcbor0_11 libdevmapper-event1_03 libdevmapper1_03 libfdisk1 liblastlog2-2 libmount1 libncurses6 libnm0 libparted-fs-resize0 libparted2 libsmartcols1 libsubid5 libuuid1 libxml2-2 libxml2-tools libxslt1 libzypp login_defs logrotate ncurses-utils parted permctl permissions permissions-config policycoreutils rsync selinux-policy selinux-policy-targeted shadow suse-module-tools suse-module-tools-scriptlets terminfo-base ucode-amd update-bootloader util-linux util-linux-systemd vim-data-common vim-small xen-libs zypper zypper-needs-restarting

The following product is going to be upgraded:

openSUSE MicroOS

20250117-0 -> 20250124-0

The following package requires a system reboot:

kernel-default

63 packages to upgrade.

Any ideas what may have caused this?

Hi all,
if you consider using BTRFS as a filesystem for your next Linux machine: DON'T USE IT!

At least when you rely on a usable and stable system under all circumstances, I would stay away from it. Stay away by miles. A brief explanation what happened to me and why I think this rules BTRFS out:

I wanted to replace my nvme volume (dual boot Windows 11 / Suse Tumbleweed) for a volume with more capacity. So I used Clonezilla, like many times before, to create a complete volume backup. As it turned out, after completing the backup, the target volume was f*cked, for whatever reason. Okay, maybe Clonezilla can't handle BTRFS volumes (according to their website, BTRFS is supported, though!!). But now I realized that the source volume is also broken. I can't read it anymore. And this, my friends, is an ABSOLUTE NO GO!! Creating a backup causes read processes on the source volume, never ever should it happen that it renders a source volume unreadable. Even considered that I used Clonezilla in a wrong way (which I didn't), something like that shouldn't happen. NEVER.

After searching the net I found some more or less similar problems, so it seems that I'm not the only one having this trouble.

I'm an IT pro, in the Windows world, though. A behavior like this would disqualify a file system for any serious use case! If my boss would ask me if we could use this file system for Linux workstations, I'd highly recommend to throw BTRFS out of the windows immediately!

Thanks for reading.

Outside of a VPS provider (like Vultr) that allows you to use your own ISO, what VPS providers currently offer openSUSE as an image choice?

Hello, for a while I've had issues with my main monitor. After an update introduced brightness control it used to flicker so I had to turn it off and on again to fix it. That was anoying, but I didn't bother fixing it. But after the update to nvidia 570(which finally fixed discord screensharing, even audio, yay!) it seemingly boots fine, but then it shuts off on the desktop after 1-2 seconds. It fixes again when I disconnect the hdmi cable connected to it and replug it again, but KDE sets the resolution to 1024x768 (Monitor is 1920x1080) which can be changed. After this procedure it works as it should, even after waking from sleep(Well if the pc does wake up sucessfully). You can see how this is annoying.

Now my question is: Is my monitor dying or is this fixable? My second monitor works perfectly fine, none of the issues occur on it(connected over dvi if that matters). I already tried a second hdmi cable with no luck. I tried wayland but the same thing happened.

Setup: GTX1650S, driver version570.86.16, KDE on x11, newest Tumbleweed snapshot

Hi all, hoping for a bit of insight here. I've recently switched to opensuse having been on debian for the last eight years or so and am really liking it so far. This evening though, I have encountered an issue that i suspect may be related to a recent update.

Some games (so far, Silent Hill 2, Space Marine 2, Hellblade 2 and Robocop) are all crashing on, or shortly after, startup and i'm not entirely sure why. These were all working fine a couple of weeks ago and this doesn't seem to affect any older games. At the point of the crash, I get a Wine C++ Runtime library error stating: Expression "!status && "vkCreateGraphicsPipelines"" from Hellblade (other games don't give this and just crash).

I'm using X11 (with an AMD graphics card), everything is running via steam and proton (tried several versions including the version that was working with these games previously) and my current kernel is 6.13.0-1 (the same thing occurs with 6.12.10-1 which makes me think it may be related to a recently upgraded package).

I've tried booting into a snapshot of the system via grub and launching a game that way to try and identify which date the update may have broken things but am faced with the same issue going back a week. Am i utilising the snapshot functionality correctly? Has anyone else experienced this or can anyone point me in the right direction to troubleshoot further? Any help would be much appreciated.

I'm struggling to install openSUSE Tumbleweed. I'm currently running Arch and Windows, but wanted to try to Tumbleweed as well. Arch and windows are on separate disks each, with their own partitions and arch is also using btrfs. My /boot partition is on the disk on which I want to install OpenSUSE.

No matter what I do (only thing that solved the issue was using ext4), I get a kernel panic:

No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on "UUID=...."

The UUID checks out, double checked on arch. I used the default settings for the partitioning, but deleted the two /boot/... entries on BTRFS, as I want grub to be installed on my existing efi partition. This works as intended, I get a tumbleweed-looking grub, from which I can choose all my operating systems (windows, arch, tumbleweed). However, tumbleweed only starts in recovery mode.

What I tried so far

• Deleted my efi partition, as it might be too small (it is now 1GB), and reinstalled it from arch using a live usb stick
• Tried without/with secure boot
• Installed nvidia drivers in recovery mode, just to make sure, as all my issues with linux I had in the last 10 years were due to my GPU
• Used ext4 as file system: That's the only way I got it running - but I want to btrfs
• Used the grub subvolumes for booting (don't love that, as this way I'm not able to detect windows/arch from the btrfs grub, and not tumbleweed from the efi grub) + didn't solve my issue
• Tried multiple versions of the installer

What is going wrong here? Thanks for any help :)

hello.. running OpenSUSE Tumbleweed with Plasma DE (KDE) and am wondering if anyone advises for or against installing hyprland alongside KDE.

I would like to experiment with it, as it looks interesting and fun, but I don't want to switch over wholesale... are there any dependancy problems or uncomfortable overlaps in DEs, where they might corrupt or interfere with each other?

Thanks, I couldn't find info on this anywhere else!

Hello my PC had a dualboot partition of opensuse tumbleweed and Windows, yesterday I updated windows and this morning when I powered my PC this is what is shown on the screen, there’s a way to solve it?

I run a dual-boot system with Win 10 and previously linux Mint, but now OpenSUSE Slowroll as of yesterday.

While I was pretty sure I pointed at the existing home partition to be used during installation (using Agama), it seems to have created a home within the root partition while the old one remains, I assume unused.

Here is the output of lsblk;

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   1.8T  0 disk  
├─sda1        8:1    0    16M  0 part  
└─sda2        8:2    0   1.8T  0 part /run/media/jacob/Storage
sdb           8:16   0 465.8G  0 disk  
└─sdb1        8:17   0 465.8G  0 part /run/media/jacob/Spare
sdc           8:32   0 931.5G  0 disk  
├─sdc1        8:33   0    16M  0 part  
└─sdc2        8:34   0 931.5G  0 part  
nvme0n1     259:0    0 931.5G  0 disk  
├─nvme0n1p1 259:1    0    16M  0 part  
├─nvme0n1p2 259:2    0   100M  0 part /boot/efi
├─nvme0n1p3 259:3    0   120G  0 part  
├─nvme0n1p4 259:4    0   507M  0 part  
├─nvme0n1p5 259:5    0 613.3G  0 part /run/media/jacob/SN550
├─nvme0n1p6 259:6    0  15.3G  0 part [SWAP]
├─nvme0n1p7 259:7    0    61G  0 part /var
│                                     /usr/local
│                                     /srv
│                                     /root
│                                     /opt
│                                     /home
│                                     /boot/grub2/x86_64-efi
│                                     /boot/grub2/i386-pc
│                                     /.snapshots
│                                     /0
│                                     /
└─nvme0n1p8 259:8    0    61G  0 part /run/media/jacob/ef059065-8eb1-4772-a923-d676a57fdce1

The last partition, nvme0n1p8, is the home partition I used for my Linux Mint installation, and still contains all the data. However, the /home mount point is under nvme0n1p7 partition, which was supposed to be root.

I'd already spent all day customising & setting things up so I'd rather not reinstall if possible.

Is it straight forward to remount home to an existing partition?

Is it possible to merge data within both homes together?

Are either of these likely to break things?

Looking for suggestions on how to tackle this, thanks.

It seems that installing cockpit on microos no longer works. I have tried on bare metal and also on a new install in a virtual machine. The command below complains about no providers for cockpit-system. It it just me or is this the same for everyone?

transactional-update pkg install -t pattern microos-cockpit

Hi all,

I'm making same very bad experiences with BTRFS and Grub2. I wanted to replace my M.2 NVME storage. I used Clonezilla to create a full image of the old storage. I then replaced the storage, restored the old system using Clonezilla again and ... there's no Grub2 bootloader anymore!! Okay, I thought, that's annoying, so put your old storage in place again and just reboot the system. Now guess what happened. NO Grub2 bootloader. The laptop boots straight into Windows!!

When I start a Tumbleweed / KDE live system, I can see all Linux folders, but they appear to be empty, but storage properties counts more than 207.000 files residing on this storage, though. So the files are there, I just cannot access them anymore.

How can I get my data / my installation back? Any ideas? I'm at the verge of despair ...

instructions would be helpful

Hey guys, short post and hopefully easy enough to fix. I just came back to openSUSE and I realized that it installed slightly differently than normal. I chose kde plasma as my desktop. Usually it comes with 3 sessions installed by default, KDE x11, Wayland and Ice WM. Well I only have x11 KDE plasma session, and I cannot for some reason find the package to install the Wayland session. Is this a new thing? is there a problem with Wayland right now?

I’ve been using OpenSUSE Tumbleweed for about 1 year now, and everything is fine, except for some bugs with mesa from time to time.
But since a few weeks ago, I would say after some kernel version 6.12 and even with 6.13, when I wake up the pc in sleep, I have to do it with the power button of the PC because the keyboard and mouse stop responding.

I read something that there was a bug with bluetooth that caused this but it was fixed in kernel version 6.12.8. I tried to remove the bluetooth dongle and it is true that it seemed to work better, but the same thing happened again.

I have tried with the lts version of the kernel and it didn’t happen until a few days ago when they updated the longterm to 6.12.11, so I have the same problem again.

Does it happen to anyone else? Do you know if there is any temporary fix?

Thanks

Hey openSUSE users!

I’ve created SnapshotRestorer, a small Qt application that automatically detects when you’ve booted into a Btrfs snapshot on openSUSE and prompts you to restore it.

Features:

✅ Detects if you're booted into a snapshot using /proc/cmdline

✅ Prompts you with a Yes/No dialog to restore the snapshot

✅ Runs pkexec snapper rollback <ID> if you confirm

✅ Prevents false prompts when booting normally

✅ Works with multi-digit snapshot IDs

Its suppose to eliminate the need to know the ID of the booted Snapshot and opening the Terminal to run snapper rollback. A small convient GUI.

Installation:

Clone the repo and run the install script:

git clone https://github.com/silverhadch/SnapshotRestorer
cd SnapshotRestorer
chmod +x install.sh
./install.sh

Source Code & Contributions:

https://github.com/silverhadch/SnapshotRestorer

This project is licensed under GPLv3. Feel free to contribute or report issues!

Let me know what you think or if you have any suggestions. Would love to hear feedback from other openSUSE users!

I've been using Mullvad VPN app version for awhile now, using RPMrebuild to change the fedora rpm version by fixing dependencies dbus-lib to libdbus-1-3 and libnotify to libnotify4.

Hadn't updated tumbleweed in 2 weeks so did so this morning; since rebooting, Mullvad VPN app says it can't connect to the mullvad system service. I've tried 2 older versions of the app (that previously worked fine) plus the latest beta build, and they all say the same. So I'm guessing its something on the tumbleweed side.

Anyone else encounter this or have any ideas? Thanks.

New install. I use systemdboot on Arch.

I've used Linux over the years on and off and have tried a variety of different distros. I'm moving to Linux now on a more permanent basis and have recently installed Linux Mint. Linux Mint seems fine but I'm not happy with the lack of updates and I'm considering a rolling distro like Tumbleweed.

The impression I get from the internet is the Tumbleweed creates a whole host of issues because of the frequent updates and I'm not sure whether to believe these people or not. Does Tumbleweed break as much as others on Reddit claim? Do you find the constant updates problematic? Is there anything problematic you have found with Tumbleweed? Is it much more complex to use than Linux Mint?

In the company I am working for we have business critical software designed and validated to run on SLES. At the moment the applications are running on SLES 12 SP2 VMs. I would like to:
- get rid of the outdated OS VMs
- migrate the source to a GitLab instance for VCS and CI purposes
- I would like to generate docker images with the software for development and production purposes
- implement CD to distribute the docker image and run them in our production environments using docker

Now, to generate a base image replicating the same environment I would need the corresponding docker image, but as it is not available as a SLES BCI, up until 12SP2 the image needs to be downloaded from SLES repositories as rpm package (thus forcing the user to have a valid subscription) and then via sle2docker can be activated to have it visible within the available images in the docker host of the VM.

What I could not find out is: would this be in compliance with the EULA to run such images on my development infrastructure (non SLES based)? Or given the fact that this version of the OS if out of support I can still use it? Subscription would not be renewable for that OS given it is getting to old, would I still be allowed to use those images as they are.

Apparently there is a KDE bug where for some users, changing NumLock key options via System Settings>Keyboard>NumLock on startup (or even through YaST) the key remains disabled upon landing on the SDDM (login screen) after boot. This issue seems to exist across multiple distros running KDE.

Hardly an earth-shaking issue, but it can be nevertheless irksome. Here is a simple fix I found:

1. Go ahead and make sure you have the NumLock Key's behavior set as you wish through YaST and/or System Settings.

2. Next you'll want to edit the file that resides here: /etc/sysconfig/keyboard

3. In that file, just about half way down, look for the following line KBD_NUMLOCK="bios" (do note it may say KBD_NUMLOCK="no" ... either way go to step 4)

4. Change what's wrapped in the quotes. It should read exactly as follows: KBD_NUMLOCK="yes"

5. Save your changes. If you wish to double check that it saved, you can input into the terminal cat /etc/sysconfig/keyboard and it should print out the contents of that file reflecting your changes.

Reboot your system and enjoy.

After updating the Nvidia drivers to 570 on Tumbleweed (X11, KDE Plasma) I get a blackscreen with a cursor after resuming from suspend.

Any way to fix this?

It works on Wayland.

What I tested and didn't work:

• https://forum.endeavouros.com/t/black-screen-with-mouse-cursor-after-waking-up-from-systemctl-suspend/38384/12
• nvidia-drm.modeset=1 kernel parameter in Grub
• Crtl + Alt + F1/2/... trick
• https://askubuntu.com/a/1411407

I was told offline install was too buggy

My current installation of TW is very broken, so I was thinking of reinstalling TW using webinstall

We are living in the current year!

latest update has nvidia 570 driver, has tumbleweed finally decided to switch to the cutting edge driver? (it's still beta)

btw, it works great, no more flickering for the troubled app under 550!!!

I jumped over this criticim while I was cross checking reviews on distrochoose. Though, I just prefer a smoth OS, I started also to wonder whats up with this attitute in the community giving the the rainbow flair a quick peak look here.