You are not logged in.
Pages: 1
Sure. GNOME is the largest, Ambxst installer is the smallest that I know of.
Many projects, and especially smaller community one, are created with systemd in mind, which is a deal breaker for many people who use them and who want to get away from systemd.
Are there plans to create a compatibility layer for other init systems so that projects created for systemd can work with them, without having to patch and repackage them?
Similar post: Seamless Devuan Project
I just found out that this is a recurring thread. https://dev1galaxy.org/viewtopic.php?pid=63022#p63022
This is definitely a Devuan problem, since I tested Debian with KDE Plasma and everything worked.
Here's something interesting. KDE developers don't recommend using KDE Plasma on Debian.
https://www.youtube.com/watch?v=AZgaUtqz2nU&t=2800s
...you're on your own; your bug-reports will be automatically closed...
WirePlumber, PipeWire, PulseAudio, ALSA, and OSS are all running on startup (and people say BSDs' audio systems are a mess).
jack-bridge could be used in the future, maybe by SonicDE. https://dev1galaxy.org/viewtopic.php?id=7567
I think that systemd developers and their slaves are intentionally bloating their projects, to implicitly dissuade people from debugging and hacking them.
This is a fresh install of Devuan Excalibur 6.1 with OpenRC, and KDE Plasma running over Wayland.
Sound from Firefox works, but sounds from files and system sounds don't work, sound volume can't be adjusted, and the Audio Volume widget displays "Connection to the Sound Service Lost" and retrying doesn't fix it.
In the Search section of Discover, Discover only displays items in "Application Addons" and "Plasma Addons". Connection to the Internet works on the rest of the system.
Lomiri packages are banned because they depend on systemd.
One of the dependency chains is:
%any Lomiri app% > qml-module-lomiri-content > libcontent-hub1 > liblomiri-app-launch0 > dbus-user-session > systemdThanks, both of you. Now, I see the use case of Devuan.
You should add
Packages from Debian's repositories are not incompatible, but they shouldn't be used without careful consideration.
or something along those lines to https://www.devuan.org/os/packages
The manual process of removing systemd dependencies from packages is either difficult or tedious, given the long delays between Debian and Devuan releases, and it doesn't yield desirable results, given that Debian and Devuan packages aren't compatible.
Excerpt from https://www.devuan.org/os/packages
Devuan package repositories are exclusive. Other repositories, including Debian, Ubuntu, Mint etc, should not be used directly.
Have you looked into using Portage to automatically remove systemd dependencies from packages and, in the fashion of Calculate Linux, distribute those compiled systemd-free packages as binaries?
The current development of Devuan (and other forks of corporatized operating systems) is the same as the process of "de-bloating" proprietary operating systems, common among Windows users.
Related topic
All of the lines already have "non-free-firmware" appended after "main". # apt install firmware-amd-graphics did work. Thanks!
That didn't help, but during boot, I caught a glimpse of "ERROR" and "radeon" and this is what my # "nano /var/log/kern.log" said
[drm] radeon kernel modesetting enabled.
[drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 or later requires firmware installed
See https://wiki.debian.org/Firmware for information about missing firmware
[drm] linux how to see bootamdgpu kernel modesetting enabled.The Wiki doesn't say why the firmware is missing but the "Firmware missing from Debian" section did point me to the right place.
Now which "/tree/amdgpu/oland_*.bin" should I install?
My system has an AMD Radeon R7 240 graphics card, amdgpu module and modules that use it are loaded, VDPAU packages are installed but "vdpauinfo" returns
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1and "grep -i vdpau /var/log/Xorg.0.log" returns nothing
To fix this, should I add "export VDPAU_DRIVER=radeonsi" to the ".bashrc" file?
Pages: 1