I recently started to find issues with Firefox-esr 115.
The problem I was finding is that on the Guardian Newspaper site the Comments section wasn't loading, and it wasn't even listing how many comments there were in the headlines page. It was working OK with the latest Firefox on my Android devices and on an (now a bit old - 109) Ungoogled Chromium.
Initially I suspected it was one of my ad-blockers and then maybe my bad-site URL filters, however it does seem to be a new display feature now being used on some websites.

Installing the Firefox PPA and using the latest version (then 127) seemed to sort it.

There is a new firefox-esr version coming out that will be based on Firfox 128. Not sure when this will hit the repositories. but I have version 128 from the Firefox PPA

 deb [signed-by=/etc/apt/keyrings/packages.mozilla.org.asc] https://packages.mozilla.org/apt mozilla main

The instructions on how to install the latest version automatically are here:
https://support.mozilla.org/en-US/kb/in … tributions

However there is an issue in that Firefox 118 has a new section in Settings:

Web Site Advertising Preferences
[X] Allow web sites to perform privacy-preserving ad measurement
This helps sites understand how their ads perform without collecting data about you.

And this is enabled by default.

Will Debian (or failing that Devuan) change this default behavior for the firefox-esr that will land in the Debian/Devuan repositories?

To be honest I too find searching the forum archive for something can be hard - what would be nice, for me, is the ability to surface just the relevant posts when you search by keyword and author rather than the whole threads that include those posts. It's always worth asking on the forum for solutions at the start - its quite possible someone may remember how a problem has been solved before you are forced to do it all yourself.

This is the /etc/init.d/nftables I have from several year back when I set up my new mailserver.

It's always worked to date.

Author was: Arturo Borrero Gonzalez <arturo@debian.org>

I think it differs from the current official version in default start and stop.
The 'official' version now has:

# Default-Start:
# Default-Stop:      0 1 2 3 4 5 6

mine is here:

#!/bin/sh
### BEGIN INIT INFO
# Provides:          nftables
# Required-Start:    $local_fs $network $remote_fs $syslog
# Required-Stop:     $local_fs $remote_fs $syslog
# Default-Start:     S	
# Default-Stop:      0 6
# Short-Description: nftables firewall service
# Description:       nftables firewall system service
### END INIT INFO

# Author: Arturo Borrero Gonzalez <arturo@debian.org>

# Do NOT "set -e"

CONF=/etc/nftables.conf

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="firewall service"
NAME=nftables
BIN=/usr/sbin/nft
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$BIN" ] || exit 0

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

VERBOSE=yes

do_start()
{
	# Return
	#  0 if start OK
	#  2 if start NOK

	# nft v0.4 return 0 if ENOENT $CONF
	if [ ! -r "$CONF" ] ; then
		echo "E: No such $NAME $DESC config file $CONF" >&2
		return 2
	fi

	$BIN -f $CONF || return 2
}

do_stop()
{
	# Return
	#   0 if stopped
	#   1 if already stopped
	#   2 if could not be stopped
	if ! do_status ; then
		$BIN flush ruleset || return 2
	fi
}

do_status()
{
	# Return
	#   0 if no rules
	#   1 if rules
	if [ "$($BIN list ruleset 2>/dev/null | wc -l)" = "0" ] ; then
		return 0
	fi

	return 1
}

case "$1" in
  start)
	[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
	do_start
	ret="$?"
	case "$ret" in
		0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
		2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
	esac
	exit $ret
	;;
  restart|force-reload)
	[ "$VERBOSE" != no ] && log_daemon_msg "Restarting $DESC" "$NAME"
	do_start
	ret="$?"
	case "$ret" in
		0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
		2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
	esac
	exit $ret
	;;
  stop)
	[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
	do_stop
	ret="$?"
	case "$ret" in
		0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
		2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
	esac
	exit $ret
	;;
  status)
	if ! do_status ; then
		[ "$VERBOSE" != no ] && log_daemon_msg "Status of ${DESC}: rules loaded" "$NAME"
		[ "$VERBOSE" != no ] && log_end_msg 0
		exit 0
	else
		[ "$VERBOSE" != no ] && log_daemon_msg "Status of ${DESC}: no rules loaded" "$NAME"
		[ "$VERBOSE" != no ] && log_end_msg 1
		exit 1
	fi
	;;
  *)
	echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
	exit 3
	;;
esac

Firefox 102.15 is still the version in (my) Daedulus repository this morning. I assume that the rollover to 115.4 won't happen till November. Where did you get it?

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.

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.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
# DEALINGS IN 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
#
### BEGIN INIT INFO
# 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
### END INIT INFO

NVPD=nvidia-persistenced
NVPD_BIN=/usr/bin/${NVPD}
NVPD_RUNTIME=/var/run/${NVPD}
NVPD_PIDFILE=${NVPD_RUNTIME}/${NVPD}.pid
NVPD_USER=nvpd
NVPD_ACTION=${1}

# 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
   then
    case "${1}" in
     start)
      echo "NVIDIA Persistence Daemon already running" 
      NVPD_ACTION=restart
      ;;
     *)
      ;;
    esac
# Daemon not running, but there is a stale PID
   else
    echo "NVIDIA Persistence Daemon, stale PID removed"			
    unset NVPD_PID
    rm -rf "${NVPD_RUNTIME}"
  fi
 fi
fi

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

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.

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

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.
https://dev1galaxy.org/viewtopic.php?pid=20903#p20903
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!

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, .. "

https://docs.nvidia.com/deploy/driver-p … index.html

I use chrony. It seems to work reliably.

https://chrony-project.org/comparison.html

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

You can certainly do it from Bullseye (11) to Chimaera (4).
The instructions are here:
https://www.devuan.org/os/documentation … o-chimaera

The instructions you quote for Stretch (10) to Beowulf (3) are the 'official' Devuan instructions.
https://www.devuan.org/os/documentation … 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.

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.

https://dev1galaxy.org/viewtopic.php?pid=20903#p20903