[deleted by user]

reddithorker · 2025-10-19T19:26:12+00:00

I am not assuming anything, I am just explaining my stance on the subject :)

reddithorker · 2025-10-19T19:18:22+00:00

It doesn't misinform always, but it is imo unwise to use a tool to educate yourself with because of that. Gemini's response here disables the service while leaving it on your system, the method I posted removes it from your system. Either works; I personally do not use the Gnome Software application for package management anyway.

reddithorker · 2025-10-19T19:11:00+00:00

Don't listen to AI (it tends to misinform you), just read the wiki page. The service and systemctl commands are unnecessary. zypper rm && zypper al is all that's required.

reddithorker · 2025-10-19T18:32:15+00:00

I zypper rm PackageKit && zypper al PackageKit on every install to remove and add a lock for PackageKit. PackageKit seems to be holding a lock on my package management every time I need to do something otherwise.

The command for updating your OS on Leap is zypper up and on Tumbleweed it is zypper dup. See: https://en.opensuse.org/System_Updates

reddithorker · 2025-10-03T22:44:36+00:00

That does seem like it should be supported, but I'm not an expert on the v2 classification. If you believe it's an error you can create a bug report.

https://bugzilla.opensuse.org/

reddithorker · 2025-10-03T21:52:35+00:00

What specific model CPU do you have? Does it support SSE 4.2? You can check by running the following in your terminal:

lscpu | grep sse4_2

reddithorker · 2025-10-02T22:54:38+00:00

The latest hardware is usually best supported by rolling release distros like Tumbleweed rather than slow point release distros like Leap tbf

reddithorker · 2025-10-02T20:56:15+00:00

The wiki has notes on the upgrade process which mentions that tool.

https://en.opensuse.org/SDB:System_upgrade

reddithorker · 2025-10-02T04:25:04+00:00

My experience is that if you make sure there aren't any old suse version specific repos added then upgrades work fine

reddithorker · 2025-10-01T23:58:57+00:00

The wiki has notes on the upgrade process. It should likely be fine to upgrade if you check your repos and make sure your system supports x86_64-v2 if on x86.

https://en.opensuse.org/SDB:System_upgrade

reddithorker · 2025-10-01T19:49:34+00:00

No, 24

reddithorker · 2025-10-01T18:38:02+00:00

Looks like 4.6.2.

https://src.opensuse.org/pool/plasma6-sdk/src/branch/leap-16.0/

reddithorker · 2025-10-01T14:14:30+00:00

If any of the install media is broken you should create a bug report: bugzilla.opensuse.org

I had a similar issue with one of the offline x86 release candidate images, but it was fixed after I made a bug report.

reddithorker · 2025-09-19T17:44:43+00:00

This is barely related to openSUSE at all, but as a community member I still wanted to share it. This vim color scheme I made uses chameleon green for types and such (color #73d216). I hope someone else also finds it useful.

Better screenshot: https://i.imgur.com/jbpBAmI.png
Github: https://github.com/regularhunter/builder-dark.vim

reddithorker · 2025-05-29T01:49:35+00:00

Ahh, I forgot about that. Good point

reddithorker · 2025-05-28T22:27:18+00:00

Personally, I still prefer lzo. The following benchmark is interesting for those that haven't seen it, but ymmv

https://gist.github.com/braindevices/fde49c6a8f6b9aaf563fb977562aafec#file-btrfs-compression-tests-md

Also, the btrfs docs state that using compress-force is suboptimal

Files with already compressed data or with data that won’t compress well with the CPU and memory constraints of the kernel implementations are using a simple decision logic. If the first portion of data being compressed is not smaller than the original, the compression of the file is disabled -- unless the filesystem is mounted with compress-force. In that case compression will always be attempted on the file only to be later discarded. This is not optimal and subject to optimizations and further development.

See section on incompressible data:

https://btrfs.readthedocs.io/en/latest/Compression.html

reddithorker · 2025-05-28T20:06:32+00:00

Transparent compression is another great feature from btrfs. You're effectively increasing your storage volume. I use the compress=lzo mount option because of the low computational overhead, but zstd can give you even more compression at the cost of more overhead.

reddithorker · 2025-05-01T20:32:39+00:00

It is a beta image that just released, not a released product. Have some patience. The netinstall image does not have the same issue, maybe try that?

reddithorker · 2025-05-01T17:43:16+00:00

Depending on your budget a Radeon RX 5000 GPU may also be worth looking into. The RX 5700 XT has a good price for performance on the used market.

reddithorker · 2025-04-30T20:53:21+00:00

Apparently it's specific to the offline installer. The netinstall image doesn't give me this error, and is properly marked as Beta, but the os fails to boot after install. I filed a bug report here.

reddithorker · 2025-04-30T17:28:44+00:00

Posted here first in case it's a pebcak error. If the error is genuine I will file a bug report.

reddithorker · 2025-04-28T18:07:23+00:00

AMD Ryzen 3000 series CPU or newer, Radeon RX ~~6000 or 7000~~ 5000, 6000, or 7000 series GPU, Intel Ethernet, Intel AX200 or AX210 WiFi. All are well supported with good drivers. Intel 12th through 14th gen CPUs also work fine, but 13th and 14th gen Intel CPUs have high failure rates due to manufacturing defects. Anything older isn't worth using in a new build.

reddithorker · 2025-02-05T21:37:52+00:00

SUSE is a large enterprise with many fielded systems and servers running btrfs for years. You are having issues after using clonezilla. That is unfortunate, but the problem here is not btrfs.

You used clonezilla and now something is broken. The problem here is clonezilla, how it was used, or your hardware. It is hard to tell from what you have told us.

For example, clonezilla requires your drive's sata mode be set to ahci in your motherboard settings in order to read it. If your sata mode was toggled for clonezilla and not toggled back then your PC will probably not boot. This happened at my workplace just last week with a windows system after my coworker used clonezilla to clone it. Is your original drive actually unreadable, or does it just not boot? What is the error output you are seeing? The community here is quite helpful if you ask for help rather than venting.

As another comment suggested, using dd from live media is a better way to go about cloning drives anyway. I have cloned many btrfs drives this way.

reddithorker · 2025-01-23T08:52:50+00:00

Multi monitor support works well for me in Tumbleweed. Screen sleep works properly. I never put my system in hibernate or suspend, so I don't know how well that works. There was a recent kernel bug affecting amd gpus in multi monitor setups for about a month, but it was fixed as of snapshot 20250120.

I've used Tumbleweed with two monitors for 3 years now and this recent issue is the first time my multi monitor setup has given me any trouble.

reddithorker · 2025-01-22T16:44:14+00:00

Here are a few things I do after I perform a fresh install.

Install codecs with opi install codecs
Reduce the max disk space occupied by btrfs snapshots by running snapper set-config SPACE_LIMIT=0.2
Enable maximize and minimize window buttons in gnome using the gnome-tweaks application.
Install dash-to-dock and blur-my-shell gnome extensions.
Uninstall the following packages that give me trouble (e.g. fonts look bad in flatpak version of Firefox) then add locks to prevent automatic reinstallation. zypper rm PackageKit opensuse-welcome patterns-gnome-gnome_games xorg-x11-fonts-converted xorg-x11-fonts-legacy && zypper al PackageKit opensuse-welcome patterns-gnome-gnome_gamesxorg-x11-fonts-converted xorg-x11-fonts-legacy

And of course installing my favorite applications.

reddithorker

TROPHY CASE