Skip to main content ↑ ↓
Topic: SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution] (Read 481 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution]

I was unable to reconstruct exactly how this broke, but somewhere along today's -Syu, displaymanager-openrc was fragged.
There was no clear error or indicator, Artix just booted to terminal rather than KDE.
After a while, I found the hint
Code: [Select]
xdm              |/etc/X11/startDM.sh: Zeile 9: /etc/init.d/functions.sh: Datei oder Verzeichnis nicht gefunden
(Line 9: / File or Directory not found) in rc.log, and managed to get pacman to tell me that that belonged to displaymanager-openrc.
Trying to reinstall that yielded an error along the lines of "displaymanager-openrc: target not found".
Seeing as the system was trying to start sddm, I opted to install sddm-openrc instead.
On install, it immediately identified a conflict with displaymanager-openrc and offered to remove it.

After installing sddm-openrc and doing
Code: [Select]
rc-update add sddm default
, KDE is now coming up on boot as expected.

Two hours gone because the system just decided it didn't want anymore. I love Linux, but shit like this is what's preventing the fabled year of the Linux desktop.
 

Re: SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution]

Reply #3 –
At a guess you've had that package for a long time and only now has it caused a problem?
And you fixed it. Yay ;)
On Windows you'd likely have had to reinstall the whole OS.

Re: SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution]

Reply #4 –
Quote from: gripped – on
At a guess you've had that package for a long time and only now has it caused a problem?
And you fixed it. Yay ;)
On Windows you'd likely have had to reinstall the whole OS.
That's not what I meant.
Why wasn't this thing deprecated along the way, in such a way that it was auto-replaced by something else?
It happens all the time, after all: "Replace package world/foo-legacy with extras/foo-new-and-shiny?"

The number of people who have multiple DMs installed is probably not too high.
A simple shell script that checks which of the usual desktop managers is installed/running and asks "displaymanager-openrc has been deprecated; foodm has been detected running on your computer. Replace displaymanager-openrc with foodm-openrc?"

It seems like a thing that would've been really easy to automate, and instead it was just left like that, until people run into an open knife years later.

Hell, a simple switch to make pacman throw a noticeable warning if displaymanager-openrc was still installed probably would've helped.

Or, you know...editing displaymanager-openrc's metadata to make it incompatible with all supported DMs, so that whatever you have installed, pacman is like "cannot install foodm 4.2.69 while displaymanager-openrc is installed. Recommended solution: Replace displaymanager-openrc with foodm-openrc."

So many options. And the one chosen was "let them suffer five years down the line >:]".

Re: SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution]

Reply #5 –
Quote from: Renegade – on
It seems like a thing that would've been really easy to automate, and instead it was just left like that, until people run into an open knife years later.

Hell, a simple switch to make pacman throw a noticeable warning if displaymanager-openrc was still installed probably would've helped.

Automating a four-year-old, one-off change is not only brilliant but also revolutionary.
I'm pretty sure all developers are already working on it.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons,fonts} -gnome3 -kde -plasma -wayland "

Re: SSDM-OpenRC-Integration broken by Update (displaymanager-openrc) [with solution]

Reply #6 –
Quote from: lq – on
Quote from: Renegade – on
It seems like a thing that would've been really easy to automate, and instead it was just left like that, until people run into an open knife years later.

Hell, a simple switch to make pacman throw a noticeable warning if displaymanager-openrc was still installed probably would've helped.

Automating a four-year-old, one-off change is not only brilliant but also revolutionary.
I'm pretty sure all developers are already working on it.

What would've been decidedly average is doing that four years ago.
The lack of which is exactly what I was inquiring about.

I'm sure you would've figured that out, were the developers not too busy to help you read.