The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » installing Appimagelauncher » 2023-09-27 21:34:23

It always used to be the case that one used a dummy library to satisfy 'imaginary' systemd dependencies lookups.
On my Daedalus system I note I have the liblogind-compat and liblogind0 packages installed but not the libsystemd0 package.
The description oft the former is
"The libelogind0 library is ABI compatible with libsystemd0.
This package provides the necessary symlinks to allow binaries linked against libsystemd0
to work with libelogind0. For full details of the compatibility see README.Debian."

#2 Re: Desktop and Multimedia » Browsers won't launch » 2023-09-14 19:31:12

AFAIK Wayland is only available if you use KDE or Gnome, other DMs default to X (I use Cinnamon and X).
Maybe the issue you are having with Firefox is Wayland/rootless start related.
Maybe it's not showing your apps on your default screen.

Are you starting them from a terminal or from Gnome? Starting them from a terminal may show some useful information.

#3 Re: Desktop and Multimedia » [SOLVED] Shotwell dependency confusion » 2023-09-14 19:11:12

I also upgraded from Chimaera, using Cinnamon as DM and (automatically upgraded) Shotwell is working.
I note both my version of Shotwell and my Depends libraries differ from Dutch Master in that the version numbers are higher.

marjorie@grendel:~$ apt show shotwell
Package: shotwell
Version: 0.30.17-1+b1
Priority: optional
Section: gnome
Source: shotwell (0.30.17-1)
Maintainer: Jörg Frings-Fürst <>
Installed-Size: 6,699 kB
Depends: libc6 (>= 2.34), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.2.4), libexif12 (>= 0.6.21-1~), libgcr-base-3-1 (>= 3.8.0), libgcr-ui-3-1 (>= 3.8.0), libgdata22 (>= 0.15.0), libgdk-pixbuf-2.0-0 (>= 2.25.2), libgee-0.8-2 (>= 0.10.1), libgexiv2-2 (>= 0.10.4), libglib2.0-0 (>= 2.49.5), libgphoto2-6 (>= 2.5.10), libgphoto2-port12 (>= 2.5.10), libgstreamer-plugins-base1.0-0 (>= 1.0.0), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.21.5), libgudev-1.0-0 (>= 146), libjson-glib-1.0-0 (>= 1.5.2), libpango-1.0-0 (>= 1.18.0), libpangocairo-1.0-0 (>= 1.14.0), libraw20 (>= 0.16.0), libsoup2.4-1 (>= 2.41.90), libsqlite3-0 (>= 3.5.9), libunity9 (>= 3.4.6), libwebkit2gtk-4.0-37 (>= 2.25.1), libxml2 (>= 2.7.4), shotwell-common (= 0.30.17-1), dconf-cli, default-dbus-session-bus | dbus-session-bus, librsvg2-common
Replaces: shotwell-common (<< 0.26.2-1)
Tag: implemented-in::c, interface::graphical, interface::x11, role::program,
 uitoolkit::gtk, use::organizing, use::viewing, works-with-format::jpg,
 works-with::image, works-with::image:raster, x11::application
Download-Size: 1,863 kB
APT-Manual-Installed: no
APT-Sources: daedalus/main amd64 Packages
Description: digital photo organizer

#4 Re: Desktop and Multimedia » Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver » 2023-08-26 19:55:47

deepforest wrote:

are you mean this script?
how use it?
now i am on Deadalus and cant chek it.
but i can do it in future if you talk me how to use those script.

OK. I'm assuming that the only problem we are trying to address is with nvidia-persistenced.

My modiified nvidia-persistenced init script is as follows:

#!/bin/sh -e
# NVIDIA Persistence Daemon Init Script
# Copyright (c) 2013 NVIDIA Corporation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# This is a sample System V init script, designed to show how the NVIDIA
# Persistence Daemon can be started.
# This sample does not rely on any init system functions, to ensure the
# widest portability possible.
# chkconfig: 2345 99 01
# description: Starts and stops the NVIDIA Persistence Daemon
# processname: nvidia-persistenced
# Provides:         nvidia-persistenced
# Required-Start:   $local_fs
# Required-Stop:    $local_fs
# Default-Start:    2 3 4 5
# Default-Stop:     0 1 6
# Short-Description: Starts and stops the NVIDIA Persistence Daemon
# Description:      Starts and stops the NVIDIA Persistence Daemon


# Gracefully exit if the package has been removed.
test -x $NVPD_BIN || exit 0

# Get the value of the PID
if [ -f ${NVPD_PIDFILE} ]; then
 read -r NVPD_PID < "${NVPD_PIDFILE}"
# Is the daemon already running?
 if [ "${NVPD_PID}" ] ;then 
  if [ -d /proc/${NVPD_PID} ]
# Daemon is running, so stop it then start anew instance
    case "${1}" in
      echo "NVIDIA Persistence Daemon already running" 
# Daemon not running, but there is a stale PID
    echo "NVIDIA Persistence Daemon, stale PID removed"			
    unset NVPD_PID
    rm -rf "${NVPD_RUNTIME}"

case "${NVPD_ACTION}" in
  echo "Starting NVIDIA Persistence Daemon"
# Execute the daemon as the intended user
  ${NVPD_BIN} --user ${NVPD_USER}
   echo "Stopping NVIDIA Persistence Daemon"
# Stop the daemon - its PID should have been read in
   [ ! -z "${NVPD_PID}" ] && kill ${NVPD_PID} &> /dev/null
   $0 stop
   sleep 2
   $0 start
  *) echo "usage: $0 {start|stop|restart}"

exit 0

1) With your mouse select all of the script and then copy it, using the "Control" and "c" keys together.

I use Cinnnamon, sudo and the gedit editor and will illustrate using these. If you use su -  rather than sudo and another text editor just change to suit.

2) Open a terminal window.

3) in the terminal type:

sudo gedit /etc/init.d/nvidia-persistenced

This should open the nvidia-persistenced init code in the editor.

4) Select all the text with your mouse.

5) Press the 'Control' and' v' keys together to paste my version in place of the existing text.

6) Save the updated code. In 'gedit' there is a save button.

7) Close gedit.

7) in the terminal restart nvidia-persistenced by typing:

sudo service nvidia-persistenced restart

8) Close the terminal.

#5 Re: Hardware & System Configuration » [Solved] Howto hibernate » 2023-08-24 22:36:20

I have Daedalus with Cinnamon/Ligthdm setup on a 6-core AMD Ryzen 5 5600G and a MSI MPG B550 GAMING PLUS motherboard.
I have a large swap partition like yours on my main LVM2 RAID1 SSDs

Hibernate using pm-utils (sudo pm-hibernate) works well.
I have buttons set up to call this from my panel (Shutdown Menu with Icons applet).
I have pm-hibernate in my sudoers file so I don't need to enter a password to hibernate.
One reason I use pm-utils rather than the built-in hibernate is that way I can call screen-lock when hibernating (and enforce unlock when I resume).

Suspend (sudo pm-suspend) sort of works but I find that with recent kernels and/or my bios it has proven unstable after waking.
Strangely it is also quite slow to waken compared to how it used to be when it worked properly. Not much faster than waking from hibernate.

Automatic activation, through the Cinnamon Power Management settings times out to suspend so I don't use it.
The settings do include a Hybrid sleep and Hibernate after suspend options, but not direct to hibernate. I've not tried the other options.

#6 Re: Desktop and Multimedia » Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver » 2023-08-24 14:58:18

deepforest wrote:

Something progress in my question
This … dia-guide/
not working at Ceres but working at Deadalus smile

PS at Ceres working this solution

apt install nvidia-legacy-340xx-driver 

but have issue with

nvidia-persistenced failed to initialize

If you use apt to install nvidia-legacy-340xx-driver it may well pull in the original unpatched /etc/init.d/nvidia-persistenced.
Have you tried replacing it with my patched version and then restarting it?

:~$ sudo service nvidia-persistenced restart

#7 Re: Desktop and Multimedia » nvidia-persistenced failed to initialize » 2023-08-24 14:51:30

Not sure what you mean by Debian Ceres 340.108 driver.
Ceres is the Devuan equivalent of Debian Sid.
Playing around with bleeding edge stuff (Sid/Ceres) is asking for trouble.
I would only suggest doing it if you have such new hardware that you can't get it working any other way.
And isn't Nvidia 340.108 a legacy driver? Not exactly new hardware.

#8 Re: Desktop and Multimedia » nvidia-persistenced failed to initialize » 2023-08-22 21:10:32

Not sure about OpenRC, the nvidia supplied nvidia-persistenced is a standard sysVinit script to go in /etc/init.d and I use sysVinit.
In my linked post I include a copy of my patched version.
If you replace the supplied /etc/init.d/nvidia-persistenced with this it should just work and not throw up any errors.
It worked fine on my PC. This PC has AMD not Nvidia graphics but my Nvidia card was still working on another machine last time
I checked.
O course they may have changed the original since 2020, but I doubt it - my 2020 version was originally written in 2013!

#9 Re: Desktop and Multimedia » nvidia-persistenced failed to initialize » 2023-08-21 18:45:59

I thought I'd explained this in my linked 2020 post at

The nvidia supplied init (/etc/init.d/nvidia-persistenced) file was borked.
As most other distributions (such as vanilla debian) use a systemd .service file, not a sysvinit init file to initialise they wouldn't get this problem.

I think I've identified the problem, though I'm unclear why it got triggered during an install. The problem occurs when there is an existing nvidia-persistence running on the system. When this is the case starting nvidia-persistenced fails with the above error message (as it can't get a lock on the PID file).

I've therefore added/modified a few line of code to correct this: if a running nvidia-persistenced exist it stops it and then starts a new instance. This ensures that nvidia-persistenced starts in its enabled state as that is the default.

This was 4 years ago (and 10 years since that file was created) so maybe it's now something else.

#10 Re: Desktop and Multimedia » nvidia-persistenced failed to initialize » 2023-08-18 17:03:23

Indeed. It may however be helpful (albeit not essential), but it seems only on machines/servers that don't run X persistently.

"Under Linux systems where X runs by default on the target GPU the kernel mode driver will generally be initalized and kept alive from machine startup to shutdown, courtesy of the X process. On headless systems or situations where no long-lived X-like client maintains a handle to the target GPU, the kernel mode driver will initilize and deinitialize the target GPU each time a target GPU application starts and stops. In HPC environments this situation is quite common. Since it is often desirable to keep the GPU initialized in these cases, .. " … index.html

#11 Re: Desktop and Multimedia » nvidia-persistenced failed to initialize » 2023-08-18 14:33:55

nvidia-persistenced has no real purpose unless you want to use CUDA.

If you don't need CUDA then you can just delete it, nvidia works fine without it.

There was (is still?) a bug in the code that dates back to 2014 that can lead to it not initialising properly.

See my post dating back to April 2020.

#12 Re: ARM Builds » [SOLVED] Clock does not update. Daedalus, arm64 Rasp Pi. NTP server not running » 2023-08-17 20:09:30

ExposeGlobalistsMadness wrote:

So what are common Devuan users to do?  Starting up ntp fails again (sudo service ntp start), even though the clock somehow updated automatically much later during this same session!

I use chrony. It seems to work reliably.

NB. the comparisons shown on this page are with ntp not with ntpsec.

#13 Re: Off-topic » make desktop looks like windows 11 » 2023-08-17 13:15:25

vanbinsbergen wrote:

I made a desktop choice at installation. That i remember. Which one, i don't :-)

I'm gonna check it out, i'll let you know if it worked for further generations who stumble upon this post.

If you have Cinnamon then there an option Menu>Preferences>System Info that will tell you about your system.

Also in a console/terminal you can run neofetch, or for absolutely everything inxi -F (if not already installed both come in packages with the same names).

On my system neofetch provides this:

marjorie@grendel:~$ neofetch
   ..,,;;;::;,..                   marjorie@grendel 
           `':ddd;:,.              ---------------- 
                 `'dPPd:,.         OS: Devuan GNU/Linux 5 (daedalus) x86_64 
                     `:b$$b`.      Host: MS-7C56 1.0 
                        'P$$$d`    Kernel: 6.1.0-11-amd64 
                         .$$$$$`   Uptime: 1 day, 15 hours, 59 mins 
                         ;$$$$$P   Packages: 2892 (dpkg) 
                      .:P$$$$$$`   Shell: bash 5.2.15 
                  .,:b$$$$$$$;'    Resolution: 1920x1200 
             .,:dP$$$$$$$$b:'      DE: Cinnamon 5.6.8 
      .,:;db$$$$$$$$$$Pd'`         WM: Mutter (Muffin) 
 ,db$$$$$$$$$$$$$$b:'`             WM Theme: Blue-mint (Menta) 
:$$$$$$$$$$$$b:'`                  Theme: TraditionalGreen [GTK2/3] 
 `$$$$$bd:''`                      Icons: menta [GTK2/3] 
   `'''`                           Terminal: gnome-terminal 
                                   CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz 
                                   GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
                                   Memory: 5729MiB / 13876MiB 

#14 Re: Installation » Devuan 5 daedalus gnome wayland doesn't work with nvidia » 2023-08-14 20:01:12

You can certainly do it from Bullseye (11) to Chimaera (4).
The instructions are here: … o-chimaera

The instructions you quote for Stretch (10) to Beowulf (3) are the 'official' Devuan instructions. … to-beowulf
and should also still work, at least on bare metal, as the source and destinations systems are both essentially frozen.
This does assume that the repositories are still there: Beowulf is now quite old.

If you coming from Bullseye (or earlier) you can convert that and then upgrade to Daedalus: although the upgrade process to Daedalus hasn't yet been formally documented several of us have done it and reported back to the Forum as to how we did it. It's pretty straightforward.

As to converting from Bookworm to Daedalus there aren't as yet any instructions for this on the Devuan site.
I have seem some discussion of the issues on the Devuan DNG list and it doesn't seem quite as straightforward if systemd is already installed (as you seem to have found).
The problem seems to be with removing systemd at Pid 1, and not locking the system.
Others more involved than me may be able to better answer how, if at all, this can be done.
And if it is possible then no doubt the instructions on how to do it will be published when Daedalus goes live.

#15 Re: Installation » Devuan 5 daedalus gnome wayland doesn't work with nvidia » 2023-08-14 11:17:57

Just surmising that there's no one here who:

1) has chosen Gnome as their DM and
2) has an Nvidia graphics card and
3) has chosen to try Wayland and has got it working successfully.

#16 Re: Installation » Devuan 5 daedalus gnome wayland doesn't work with nvidia » 2023-08-08 14:09:59

On your second point nvidia-persistenced has no real purpose unless you want to use CUDA.

If you don't need CUDA then you can just delete it, nvidia works fine without it.

There was (is still?) a bug in the code that dates back to 2014 that can lead to it not initialising properly. Nothing to do with systemd, just poor code.

See my post dating back to April 2020.

#17 Re: Other Issues » Ceres AMD64 unable to install wine32 » 2023-07-27 15:59:16

Bookworm is now on version 12.1 which is usually taken as a sign that initial bugs have been sorted and sysadmins. can safely upgrade.

So I would expect Daedalus, which exactly the same packages as Bookworm in most cases should equally be ready, apart from the installation isos which are still being tested.

Most security updates appear on Daedalus as soon as they appear on Bookworm since Devuan merges Bookworm packages with the very limited number of 'devuan modified' packages. For example the Zenbleed AMD firmware patch appeared very quickly.

For myself, having upgraded my desk PC from Chimaera to Daedalus a few weeks ago without issue I've now upgraded my two others machines, one a mail server and all seems good.

#18 Re: Off-topic » Zenbleed - CVE-2023-20593 » 2023-07-26 13:26:19

I'm not affected personally as my AMD 5600G is Zen3 not Zen2,

Nevertheless a AMD-microcode fix for Chimaera, Daedalus and Unstable landed this morning as a security update.

However as the end of that security-tracker ( … 2023-20593) it says:

3.20230719.1 ships the first batch of fixes, only for 2nd gen Epyc CPUs, further
CPUs to follow in later releases

This is the one we have now got. Epyc is a database CPU.

So there are still fixes to come for the other Zen2 (Ryzen) CPUs which aren't fixed yet.

More info here: … bleed.html

If you haven't got the microcode fix there is a workaround mentioned in this article:


It is highly recommended to use the microcode update.

If you can’t apply the update for some reason, there is a software workaround: you can set the chicken bit DE_CFG[9].

This may have some performance cost.


You can use msr-tools to set the chicken bit on all cores, like this:

# wrmsr -a 0xc0011029 $(($(rdmsr -c 0xc0011029) | (1<<9)))

#19 Re: Devuan » Devuan 5 Daedalus Release (Debian 12 - Bookworm) | Looking for info » 2023-07-17 10:31:57

GNUser wrote:

Yesterday I upgraded from Chimaera to Daedalus without any issues. Here are the steps I followed:

Edit /etc/apt/sources.list to point to daedalus
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get dist-upgrade # at the end there are some errors having to do with old version of linux kernel
$ sudo apt-get autoremove --purge # this removes the packages that caused errors
$ sudo apt-get dist-upgrade # now it completes without any errors
$ sudo apt-get autoclean

I'm assume that we will be providing a note on how to upgrade as well as how to install from new and how to convert from Debian.
So I thought it might be useful to document my experience and any trip hazards I encountered.

I upgraded just over a week ago, using the same steps as described above.
Where it asked about if I wanted to accept new default config files I chose to keep those I already had.
I was already using the most recent backported 6.1 kernel prior to the upgrade.
A simple replace edit of sources list is however not entirely sufficient as you should add the 'non-free firmware' to each line.
With that change I had no problems in the upgrade as such.

I use unattended-upgrades to install any security package updates daily.
I had to change the line  "o=Devuan,n=chimaera-security" to  "o=Devuan,n=daedalus-security" in /etc/apt/apt.conf.d/50unattended-upgrades.

My motherboard (a MSI B550) use a custom chip to monitor fan speeds in particular.
There is a corresponding kernel module but it was not loaded. I ran

sudo modprobe nct6687.ko

to load it and then sensors could see it.

Grub no longer runs osprober by default. If you have been using it to create grub menu items to boot to alternative OS on your machine you will need to as root restore it in the file /etc/default/grub by un-commenting the line


and then run update-grub as root.

Also relating to grub the menu on my PC now works with my usb keyboard (it didn't on Chimaera).

rsyslog creates fewer log files, such as /var/log/mail.{info,warn,err}. The messages are still there in /var/log/mail.log.
If you have another program reading any of these, e.g. fail2ban, you will need to get it to read /var/log/mail.log instead.
Similarly /var/log/{messages,debug,daemon.log} are also no longer being updated. Their messages are still there in /var/log/syslog.
All these (and their log-rotated counterparts) can now be removed.
Logrotate itself is working as expected on my PC.

Just for info. I run Cinnamon. After the upgrade Gnome programs (such as Evolution and System Monitor) now duplicate the Max/Min/Close symbols and Title that are in the Window Title Bar in the top line of the program. Nothing fatal but it looks odd.

There are some changes in Bookworm (and hence Daedelus) that don't affect my PC but might others e.g. the packages that set the system clock and reduced accessibility support.
Changes to Bookworm (and by default Daedulus) are covered in the release notes' Chapter 5 Issues to be aware of for bookworm … on.en.html

#20 Re: Devuan » Some Newbie Questions about Devuan on Desktop » 2023-07-11 22:37:21

I upgraded to Daedalus two day ago.

I use dnscrypt-proxy. It was previously running on Chimaera.

The package version installed and running is 2.0.45+ds1-1+devuan1

So clearly a Devuan compliant version.

There are a number of packages in Debian that have had to be modified to run without systemd. I assume that this is one of them.

#21 Re: Installation » Synaptic suddenly won't start on Chimeara » 2023-07-05 22:59:03

From the user Desktop (I use Cinnamon) Synaptic is authorised to open a root graphics session (gtk) through pkexec (which is what pops up the authorisation requester) and behind that is polkit.
Might be worth having a look in /var/log/auth.log to see if it's throwing errors.

On my PC a recent synaptic session was logged in /var/log/auth.log like this:

Jul  3 17:33:18 grendel polkitd(authority=local): Operator of unix-session:1 successfully authenticated as unix-user:marjorie to gain ONE-SHOT authorization for action com.ubuntu.pkexec.synaptic for unix-process:13922:214554138 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:marjorie)
Jul  3 17:33:18 grendel pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Jul  3 17:33:18 grendel pkexec[13925]: marjorie: Executing command [USER=root] [TTY=unknown] [CWD=/home/marjorie] [COMMAND=/usr/sbin/synaptic]

My software stack is:
Host: grendel
Kernel: 6.1.0-0.deb11.7-amd64 x86_64
compiler: gcc v: 10.2.1
Desktop: Cinnamon 4.8.6
tk: GTK 3.24.24
wm: muffin 4.8.1
dm: LightDM 1.26.0
Distro: Devuan GNU/Linux 4 (chimaera)

#22 Re: Hardware & System Configuration » Logrotate on Daedalus » 2023-06-27 18:58:34

There are some changes to how logging works in Bookworm mentioned in the release notes, see sections 5.17-5.19.

It's not clear how these changes propagate through to Daedalus when it's either a new install (as I surmise yours was originally) or if you upgrade from Chimaera. … em-logging

#23 Re: Hardware & System Configuration » [SOLVED] Unclaimed display controller » 2023-04-24 22:32:27


You have posted the output of lshw as an image - the font is tiny and I, at least, find it unreadable, so it's hard to help you further.

This is my output of the same command on my PC posted  with code delimiters.

I'm running a AMD B550 motherboard with a AMD Ryzen 5 5600G with Radeon Graphics.

sudo lshw -C video
       description: VGA compatible controller
       product: Cezanne
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:30:00.0
       version: c9
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:37 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(size=256) memory:fcb00000-fcb7ffff memory:c0000-dffff

Can you do the same, please?

Also it would be helpful if you can say what you are aiming for in video,

#24 Re: Hardware & System Configuration » Grub problem after installing new Kernel » 2023-03-29 11:12:48

Is grub failing completely?
Usually you can successfully boot into the previous kernel from the grub menu.

#25 Re: Installation » [SOLVED] fail2ban banactions, convert from iptables to nftables » 2023-03-10 14:12:26

Hi Ralph. Yes, perhaps I'm just not very good at expressing my understanding of this.

The Debian wiki says:

Starting with Debian 10 Buster, nf_tables is the default backend when using iptables, by means of the iptables-nft layer (i.e, using iptables syntax with the nf_tables kernel subsystem). This also affects ip6tables, arptables and ebtables.

You can switch back and forth between iptables-nft and iptables-legacy by means of update-alternatives (same applies to arptables and ebtables).

So I suspect that in the default installation the fail2ban configuration assumes that iptables is installed, calls iptables and uses iptables-nft to translate.
Not quite the same thing as going nftables native.

Hence it seems that the simplest solution for the OP is, as you have said, to reinstall iptables.

Board footer

Forum Software