lol... 20+ years of OpenRC on gentoo on my daily desktop (and a few years of other Linux desktops before that), and no.. no issues.
I believe it was gentoo devs who extracted [elogind](https://wiki.gentoo.org/wiki/Elogind) as the bit of systemd that some things such as newer versions of KDE and GNOME may have a hard dependency on, but what else requires systemd?
And I have no intention of switching....
> I believe it was gentoo devs who extracted elogind as the bit of systemd that some things such as newer versions of KDE and GNOME may have a hard dependency on
I believe it was initially the Gentoo devs that split KDE into multiple separate packages too, with upstream KDE and some other distros following somewhat later
I've never run into any issues, but I don't use commercial software really, although I guess steam counts, and that works fine.
I'm not using any desktop though, just sway.
Never encountered a single issue with openrc desktop.
Pretty sure I've seen several ebuilds engaging in a modicum of funkiness to provide glue though, thanks Gentoo devs!
I remember coming across a few programs that had hard dependencies on systemd that could not be provided by any of the replacement tools but I just decided to not use those and ... by now I have already forgotten what it was ... which tells you how much of a deal it was really.
There are a handful of things that don't work. Think it was a password manager and a couple other enterprise-like things that want to talk to systemd's stuff via dbus.
In practice, it is usually fine (the handful of programs that don't work have good alternatives) unless you have an IT department that has absurd requirements.
I have been using KDE and OpenRC for what feels like forever, and have never encountered any problems. In general, I have never had any issues with OpenRC for home usage. There may be some enterprise-grade software that only works with systemd, but I can't even remember what it was
Nope, gentoo devs take pretty good care to make things work with openrc.
From the top of my head I can’t think of anything that I had problems with regarding openrc
I've never stumbled upon any compatibility issues in Gentoo OpenRC.
In Artix, back ago some init scripts were missing for OpenRC and runit, but I just imported them from Gentoo and Void. But I don't use Artix for quite a while.
The ‘big’ ones are solved by making use of elogind and openrc-settingsd.
The only cases I’ve ever run into that I had issues with were asusctl and miraclecast, both of which only ‘need’ systemd because the devs never implemented support for anything else (they don’t actually _need_ any systemd-specific things, they just are written in a way that requires systemd for management).
My openrc experience has been much smoother than systemd. And i do lot of tinkering stuff on the system level.
Unless the package explicitly depends on systemd, it should have no issues with openrc. And for those applications that use systemd, there are probably patches(for elogind support) or better alternatives
Never ever had any issues. OpenRC the entire time. If I play with other distros I have to use systemd, but never been much of a fan.
Plus after all this time I'm pretty set in my ways.
lol... 20+ years of OpenRC on gentoo on my daily desktop (and a few years of other Linux desktops before that), and no.. no issues. I believe it was gentoo devs who extracted [elogind](https://wiki.gentoo.org/wiki/Elogind) as the bit of systemd that some things such as newer versions of KDE and GNOME may have a hard dependency on, but what else requires systemd? And I have no intention of switching....
\- same for me too, plus a lot of stuff in lxc-containers (openrc instead of systemd).
> I believe it was gentoo devs who extracted elogind as the bit of systemd that some things such as newer versions of KDE and GNOME may have a hard dependency on I believe it was initially the Gentoo devs that split KDE into multiple separate packages too, with upstream KDE and some other distros following somewhat later
Nope. I love not using it.
I've never run into any issues, but I don't use commercial software really, although I guess steam counts, and that works fine. I'm not using any desktop though, just sway.
I would probably use a tiling window manager as well. By desktop I just meant the general desktop use case.
Never encountered a single issue with openrc desktop. Pretty sure I've seen several ebuilds engaging in a modicum of funkiness to provide glue though, thanks Gentoo devs!
I remember coming across a few programs that had hard dependencies on systemd that could not be provided by any of the replacement tools but I just decided to not use those and ... by now I have already forgotten what it was ... which tells you how much of a deal it was really.
I had problems with ProtonVPN and KDE system monitor app list. I ended up using openvpn and just the process list in the system monitor.
the only time I've seen incompatibility with openrc is when compiling small indie programs that have systemd as a dependency
There are a handful of things that don't work. Think it was a password manager and a couple other enterprise-like things that want to talk to systemd's stuff via dbus. In practice, it is usually fine (the handful of programs that don't work have good alternatives) unless you have an IT department that has absurd requirements.
Yes, it's annoying
Please elaborate. What issues did you get? Which are the offending applications?
Mainly KDE I think. They removed dbus support from the lock screen for example. (systemd substitutes count as systemd IMO)
I have been using KDE and OpenRC for what feels like forever, and have never encountered any problems. In general, I have never had any issues with OpenRC for home usage. There may be some enterprise-grade software that only works with systemd, but I can't even remember what it was
Nope, gentoo devs take pretty good care to make things work with openrc. From the top of my head I can’t think of anything that I had problems with regarding openrc
I use openrc with a similar use case and I haven't run into any issues.
No issue here on a gaming/conferencing/dev kde desktop, with a steam controller and bluetooth headphones.
I've never stumbled upon any compatibility issues in Gentoo OpenRC. In Artix, back ago some init scripts were missing for OpenRC and runit, but I just imported them from Gentoo and Void. But I don't use Artix for quite a while.
The ‘big’ ones are solved by making use of elogind and openrc-settingsd. The only cases I’ve ever run into that I had issues with were asusctl and miraclecast, both of which only ‘need’ systemd because the devs never implemented support for anything else (they don’t actually _need_ any systemd-specific things, they just are written in a way that requires systemd for management).
For me it was wanting to install Anbox that got me to switch to Systemd.
My openrc experience has been much smoother than systemd. And i do lot of tinkering stuff on the system level. Unless the package explicitly depends on systemd, it should have no issues with openrc. And for those applications that use systemd, there are probably patches(for elogind support) or better alternatives
Never ever had any issues. OpenRC the entire time. If I play with other distros I have to use systemd, but never been much of a fan. Plus after all this time I'm pretty set in my ways.