Linux

47929 readers

1154 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

OpenSuse Tumbleweed: Update to KDE6 - Throws you back to login screen mid update/upgrade (feddit.de)

submitted 7 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Halfway through the installation it throws me back to the login screen. When I try to continue the update/upgrade it does it again.

I already did a rollback with snapper and forgot to note at which package it exactly happened.

So anyone trying to update, beware that the update might not get through.

I'll wait a week and then try again.

Update

Ashged on reddit:

*Yeah, unfortunately the update doesn't work within KDE. No idea if/when they'll make a fix for that.

The update however works outside KDE, in an IceWM desktop or a TTY. For best results, first log out of KDE, then using Ctr+Alt+F1 go a text based enviroment. Log in there, use sudo zypper dup, then after it finishes, reboot and log in to your regular KDE desktop. Plasma 6 should upgrade succesfully.*

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Can't we isolate DEs somehow? They've been always the most complicated and fragile part that brings down the whole system.

I wish I could containerize them easily, but it's so hard.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago)

It's easy enough to containerize an entire DE - but if you did that, you be basically running everything from inside the container - at which point you're back to square one. You're just shifting the problem from the host to the container, and the solution to fix both is the same: restore from a snapshot, reinstall, or actually try and fix the issue.

Also, a DE shouldn't bring down the whole system btw - you should always be able to switch to a second TTY to recover, and/or have a backup lightweight DE that you can switch to from your logon screen. Unless of course something really broke and caused a kernel panic and your system is fully frozen (which should be a rare occurrence on Linux-friendly hardware).

Anyways, a realistic solution would be to use an immutable distro, such as one of the Fedora Atomic/uBlue distros. The kind of breakage mentioned by OP won't be possible in such a distro, because your entire system gets updated as a single image, so it either works or it doesn't (an atomic operation), and in the event it doesn't work, you can always switch back to a previous image from the boot menu instantly. You can "pin" known good images, and this sort of image operations makes it easy to switch between latest testing/stable image version, or even switch between entire DEs with a single command. So if your KDE 6 is broken, not only can you just go back to KDE 5 with a single reboot, you can also switch to a GNOME image, or rebase to something else entirely, without messing up anything, without creating a dependency hell.