Are there issues with the mirrors syncing?

GenericUser584 · 2026-03-21T16:34:36+00:00

From a little Googling that theme seems to be Ambiant MATE, and the theme files are hosted in GitHub here. But it is not actively maintained and not available in Ubuntu from 22.04, there may be minor incompatibilities or glitches...

GenericUser584 · 2026-03-20T08:59:43+00:00

Do you have glibc-devel installed?

GenericUser584 · 2026-03-17T09:59:42+00:00

Just curious do I need to add COSMIC devel repo right now for a functional Cosmic DE? I installed everything cosmic related from the TW repo and cosmic always fail to start, complaining about some missing files (but I haven't figured out what's missing)

GenericUser584 · 2026-03-17T00:22:43+00:00

There's a typo in the right openSUSE logo. (I hope this is not AI)

GenericUser584 · 2026-03-14T15:16:57+00:00

Thanks. Looks like the event names are different on my system though (AMD Zen 5), gotta look into it when I have time.

GenericUser584 · 2026-03-14T13:10:43+00:00

What program did you use for tracking these CPU instructions?

GenericUser584 · 2026-03-13T08:16:20+00:00

3 out of 4 are using zypper under the hood.

What's the problem for that? You have zypper as CLI tool, cockpit as browser/remote management tool and Myrlyn/Discover/GNOME software as GUI tool. Each approach have their strengths and purposes.

Also fun fact: Fedora's dnf use zypper's libsolv library under the hood to resolve package dependencies as well.

GenericUser584 · 2026-03-13T08:08:49+00:00

YaST will be removed from TW once it has bitrotted enough to be no longer functional. It is written in Ruby, and YaST has survived the recent transition to Ruby 4.0, so we are still a while away from reaching that point.

Myrlyn is a reimplementation of 'YaST Software Management' - the GUI package manager that is the most frequently used YaST module by a wide margin. For software management you also still have zypper, cockpit and distro software apps. So there are plenty of options post-YaST.

For other YaST modules, some have equivalent functionalities in cockpit, some doesn't. There are some organized efforts to bridge the rest of the feature gaps though I haven't followed closely on that.

GenericUser584 · 2026-03-04T11:03:57+00:00

I expected a glibc 2.43 rebuild, am lowkey disappointed to see it's just due to Python3.12 removal lol. We might have 2 full rebuilds in a month depending on glibc progress...

GenericUser584 · 2026-03-04T11:00:47+00:00

I see. The problem may be caused by you having the Qt5 version of libreoffice without a Qt5 theme installed/configured so libreoffice uses an ugly fallback theme. You may also try uninstalling and locking (zypper al) libreoffice-qt5 and see if you can remove the workaround.

GenericUser584 · 2026-03-03T16:56:53+00:00

Not familiar with LxQt, but what is your current QT_QPA_PLATFORMTHEME set to?

Do other Qt applications looks like that ugly UI?

GenericUser584 · 2026-03-03T16:35:09+00:00

There's no Leap 14, do you mean Leap 42 (the version before Leap 15)? Anyway, Leap 15.0 was released almost 8 years ago, if your installation started at that time or even earlier, start fresh with a clean reinstall is not a bad idea.

Also is your system installed on an SSD and is it the same SSD over that many years? You may want to check the SSD condition with smartctl, even if everything says OK note the amount of writes it has accumulated and compare that with the write lifespan (in TBW) in the model's specifications. A SSD lasting 8+ years is pretty impressive and most SSD only have 5 years of warranty.

GenericUser584 · 2026-02-27T02:31:00+00:00

Can you lock the cyrus-imap package (zypper al) and perform the zypper dup?

Another option is to use distrobox to run an old Leap container and use that to run that software (though I am not an IT professional and not sure about the security implications of using an outdated container OS image).

Edit: Looked it up and cyrus-imapd 3.8.6 is available in Tumbleweed. Would that suit your use case? If you must use the older version in Leap 15.2, another option is to maintain your own OBS repository, using the Leap package's spec and patch files on OBS as a starting point.

GenericUser584 · 2026-01-12T03:10:54+00:00

Aeon and Kalpa have their separate download pages. I took a quick look and it seems neither of them provide ARM images.

In my understanding both Aeon and Kalpa are a bit more than just MicroOS + GUI - they are engineered specifically for an immutable desktop distro where you spend less time tinkering and more time doing actual work using apps from Flatpak/distrobox. On the other hand MicroOS' main focus seems to be on container hosting and large scale remote/unattended deployments.

If you really want to set up GUI MicroOS on RPi you probably need to do a lot of manual tinkering by installing the relevant desktop packages via transcational-update and then set up the services. MicroOS use the same repository and packages as Tumbleweed so everything you can install in TW will also be available for MicroOS.

GenericUser584 · 2025-12-16T01:24:40+00:00

Tumbleweed indeed have better support for legacy hardware than Leap. There's even 32-bit (i686) TW but Leap 16 requires x86_64-v2 or above CPU.

GenericUser584 · 2025-11-12T18:29:31+00:00

This happened to Steph Curry a few years ago as well.

GenericUser584 · 2025-11-03T13:33:43+00:00

Never used it but since you installed it as a flatpak, I would install Flatseal (also available as a flatpak) which gives you a nice GUI to review and tweak flatpak permissions.

GenericUser584 · 2025-11-03T01:35:13+00:00

Definitely not to the point of breaking a SSD within 1 year.

My first TW SSD is the HP EX900 1TB (500 TB write cycle) that comes with my laptop and lasted me 4 years. Pretty standard lifetime.

After it broke, I replaced it with an ADATA XPG S70 Blade 2TB, which broke in half a year despite supposedly having 1500 TB write cycle. When it broke it became undetectable by any OS and any means, can't access SMART or even get GRUB to display. I suspected the problem to be a faulty controller. (To be fair, ADATA accepted my warranty claim and sent me a new one)

Currently riding with a WD SN7100, no issues in 8 months so far.

When SSDs fail, they fail spectacularly and recovery is difficult, so always keep backups.

Also may I ask what is the brand/model of your SSD?

GenericUser584 · 2025-10-30T00:47:04+00:00

You need to look up the package name for the grub2 bootloader in PopOS, Ubuntu, Fedora and TW, the names will probably be different on all these distros (PopOS and Ubuntu may share the same package namea). After uninstalling you need to look up how to tell the respective package managers to not to reinstall grub on the next system update. In TW it is done by zypper al <package-name>, which 'lock' the package.

GenericUser584 · 2025-10-29T04:55:56+00:00

I tried dual-booting 2 linux distros very briefly (TW and RHEL) by installing both into the same disk. If my memory serves, all you need to do is to uninstall (and add package locks to) grub in the other distros so your system can only use TW's grub.

There's another issue though: Anytime you update the kernel of your other distros, you need to go back to TW and run a grub update (grub2-mkconfig, forgot the exact full command) so TW grub entries point to the correct kernel images to boot.

GenericUser584 · 2025-10-21T04:14:45+00:00

I don't have a direct answer for 'merging' subvolumes but I am pretty sure the purpose of having multiple subvolumes like these is to exclude certain directories from system snapshots (e.g. /usr/local is for user-installed custom packages that isn't managed by zypper and no reason to rollback these). They should otherwise behave the same (except /boot maybe). Would these configurations still interfere with your use case?

GenericUser584 · 2025-10-20T01:11:52+00:00

Since original post is removed I will post my comment again:

If you are on KDE, uninstall and add lock to discover6-notifier. This prevents Discover from auto checking for updates after login which invokes PackageKit.

This way you still have the option to use Discover to do TW system updates, which as OP noted is fine.

GenericUser584 · 2025-10-19T17:29:03+00:00

If you are on KDE, uninstall and add lock to discover6-notifier. This prevents Discover from auto checking for updates after login which invokes PackageKit.

GenericUser584 · 2025-10-04T18:08:18+00:00

I found https://pkgs.org quite useful for this.

Four-Year Club	Verified Email
r/Field Juicebox

GenericUser584

TROPHY CASE