To clarify things. We are talking LUKS encryption, so that is first thing after boot, if I'm not mistaken.
Also kernel 6.1.0-18-amd64,  6.1.0-27-amd64 does not.

term.log has a bunch of lines like this

W: Possible missing firmware /lib/firmware/i915/..

But that should result in either working or not working hardware and not in sometimes not working hardware?
(Plus those were there before)

kernel changed form 6.1.0-18-amd64 to 6.1.0-27-amd64. (give me some minutes to test that)
Previous kernel doesn't has the problem.

OK, no idea where this setting came from:

# Restrict access to the admin pages...
<Location /admin>
  Require group printer-admins

I never had a group called "printer-admins"

adding "cups-admins" to this does the trick.

I guess putting "lpadmins" there as first action would have done the trick.

Sorry for starting this and then taking this long to reply.
But I can confirm that things re working better with the updated version of FF-esr (but the problems started when 115.9 was the up to date version).
I am aware of the "same as the IE shit" situation.
Using chrome(ium) is not my prefered way. Is there even the equivalent to the script/add blocking plugin system for chrome?

Thank you, very much for generating a easy and understandable explanation from my unsorted clutter.

As to the problem itself, that is addressed in this debian bugs:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1038930
https://bugs.debian.org/cgi-bin/bugrepo … ug=1055771
First one has a working patch, second has not.
Both aren't fixed yet.

So with the first answer in my bug #1412 do actually have no idea where the right place is to post this..

So do I open a Devuan bug for this and if necessary the maintainers will bush it upstream, if necessary? (devuan -> debian -> radicale).

OK, that seems the wrong way to do it. I searched bugs.devuan.org for radicale:
"There is no maintainer for radicale. This means that this package no longer exists (or never existed). Please do not report new bugs against this package."

Meanwhile on my installation:

# apt-cache search radicale
python3-radicale - simple calendar and addressbook server - python3 module
radicale - simple calendar and addressbook server - daemon

Same result for my chimeara (server) and daedalus(desktop) installation.

So, first upgrad my server to deadalus and then if the problem still exists a bug repost to debian (since there is no devuan maintainer) ?

Sadly the patch didn't work. I do have an idea where the problem lies, but don't know how to fix it.
The startscript defines this variable:

CALDIR=/var/lib/$NAME

That's the default path for storing the calendar-files,
which later on is used in the script as location for the calendar file, which is odd, since you can define that in
/etc/radicale/config.
Where I did this:

[storage]
# Folder for storing local collections, created if not present
filesystem_folder = /data/ordnung/radicale/collections

I do find that a bit off. Why define the storage path i the init-script, if there is config file for that?

also the init-sscript has this comment:

# Description:          Start/Stop the Radicale CalDAV and CardDAV
#                       server, configurable via /etc/default/radicale.

and /etc/default/radicale looks like this:

# Defaults for radicale calendar server (sourced from /etc/init.d/radicale)

# If you want radicale to be started as a system service,
# enable it using the command 'update-rc.d radicale enable'

# Options for radicale on startup
# Note that most options can be specified in /etc/radicale/config
RADICALE_OPTS="--daemon"

# Make initscript verbose, override system default
# (Note: This is ONLY about the initscript!)
VERBOSE=yes

If that seems a bit confused, you are right, I am...

I get, that is the "package by package" way to do it. But kicad has also several other packages like kicad-library, kicad-foodprints and some.
The thought was to have those covered, too without to remember the "-t daedalus-backports" option every time.

Another question I'm not entirely sure of. If there are updates in the backport package, will that be covered by?:

apt update && apt upgrade