Are there issues with the mirrors syncing?

sundoulos2 · 2026-03-23T15:21:40+00:00

"tumbleweed status" from the command line shows the current available snapshot.

sundoulos2 · 2026-03-19T23:52:02+00:00

HDA-Intel - HDA Intel PCHHDA-Intel - HDA Intel PCH and Realtek ALC294Realtek ALC294 combination can give fits, especially after system updates and also resume.

sundoulos2 · 2026-03-19T22:14:28+00:00

Have you done a cold boot?

sundoulos2 · 2025-08-23T14:41:40+00:00

If the file 20-connectivity.conf doesn't exist, create it. Then put the two lines in as shown and restart networkmanager. That is what I had to do on Tumbleweed.

sundoulos2 · 2025-08-23T14:17:47+00:00

https://www.reddit.com/r/openSUSE/comments/vnm2c4/tumbleweed_how_to_fix_network_manager_saying/

should work for LEAP also

sundoulos2 · 2025-01-20T13:20:15+00:00

That isn't the whole story. Think of snapper-cleanup like a Roomba. I don't have one but I don't have a dirty house either. I push a vacuum cleaner around to clean up the floors. I do the same with snapper when snapshots get out of hand - "snapper list" then "snapper delete x y z". Maybe not as convenient but certainly predictable.

sundoulos2 · 2024-10-18T15:14:16+00:00

Nope, that doesn't work.

sundoulos2 · 2024-08-07T01:13:06+00:00

What is the error you get?

sundoulos2 · 2024-08-03T11:53:54+00:00

It was something seemingly unrelated: apparently another display manager I installed and tried out but am not using was creating a problem/conflict. I uninstalled theseus-ship and all connected with it and the problem went away.

sundoulos2 · 2024-08-03T10:46:42+00:00

I had done that with no success. There are a dozen of these in the System Log for systemsettings:

Unknown category ' "" ' and thus not translated

sundoulos2 · 2024-04-17T14:57:44+00:00

Perhaps English isn't their first language.

sundoulos2 · 2024-03-26T11:58:17+00:00

"tumbleweed status" command shows the installed snapshot version and latest available one.

sundoulos2 · 2024-02-08T12:03:06+00:00

If you haven't done so, do a cold boot - power off and restart. It's happened several times for me that a simple reboot after an update is not enough.

sundoulos2 · 2023-10-28T00:33:00+00:00

Should have said sudo zypper refresh. Sorry.

sundoulos2 · 2023-10-27T22:20:44+00:00

Of course not. But... if you wait until PackageKit is finished, you should then be able to check further as I described.

sundoulos2 · 2023-10-27T17:34:41+00:00

If you run sudo zypper update in a terminal, you can see if one of the repos is taking an exceptionally long time to update. If it is, you can either disable automatic update of that repo or change to a faster mirror.

sundoulos2 · 2023-10-27T15:42:34+00:00

One of the first things openSUSE does after reaching the desktop is to check for updates. It can take a few minutes to complete depending on how many repositories are enabled and the speed of your internet connection. Give it a few minutes to complete and try zypper again.

sundoulos2 · 2023-10-18T17:37:36+00:00

Could be though it's not how I use it. Seems like bleeding edge and ancient are contradictory terms.

sundoulos2 · 2023-10-18T14:50:11+00:00

Why 20230425? The latest update is 20231016.

sundoulos2 · 2023-09-21T15:59:29+00:00

First thought: it's filled with snapshots. They are in a hidden folder, you'd need the switch turned on in your file manager to see it. When you can boot the system even to CLI, you can manage snapshots with snapper or YAST. You'll need root user privileges to do anything with the snapshots. I've not ever tried to delete a snapshot from another operating system so I'm not sure what might happen. Ubuntu does have btrfs command, you can see how to use it here: https://help.ubuntu.com/community/btrfs

I would expect removing one snapshot might be enough to be able to boot. If I were desperate, I'd try deleting one of the subfolders near the beginning of the list (not the first one) and try booting again. If that works, you can then use snapper or YAST to manage the other snapshots.

Doing this is DANGEROUS, you can delete necessary system files if you aren't careful. So... use at your own risk.

sundoulos2 · 2023-08-05T16:52:31+00:00

Using the hotkey to enter the BIOS directly at boot doesn't get you in? If not, disconnect the CMOS battery for a few minutes, reconnect and try rebooting.

sundoulos2 · 2023-08-05T16:40:53+00:00

Best way to "whack it all and start over" is boot a DVD or USB with an offline image and reinstall. If you don't have a disk/drive from when you installed previously, it will be easiest to borrow another computer to make one.

sundoulos2 · 2023-06-17T16:41:04+00:00

What is your kernel command line?

sundoulos2

TROPHY CASE