You are not logged in.
Presumably some residue from incompletely removed packages, but there is something claiming to be systemd-udevd in the log. Check for /lib/systemd/systemd-udevd and /ur/lib/systemd/systemd-udevd and remove that, and restart.
The other udevd logs (apparently competing with the extraneous systemd-udevd) belong to the eudev package, which I would have thought you installed as replacement. If not, then you have to chase up which binary is involved and where it comes from. Something like this (as root) perhaps:
# find /bin /sbin /lib /usr -name '*udev*[ 1.648553] systemd-udevd[197]: starting version 3.2.14I don't think you should run both udev and eudev!! (It looks like you do)
Get rid of systemd-udevd first. But if that doesn't fix it we should look further.
Which permissions does it have/get and which permissions would you want?
Do you use eudev?
Maintainer: Marco d'Itri <md@linux.it> ... hubris and deliberate intent to cause trouble.
Afaict, assuming you have eudev installed, the mode for /dev/dri/renderD128 would be set b.m.o line 42 in /lib/udev/rules.d/50-udev-default.rules.
Answer about seatd and elogind would start with asking which "service managment" you are using; (apparently not sysvinit?)
About apt using ipv4 there's web results like this, suggesting by example:
sudo apt-get -o Acquire::ForceIPv4=true install pkg
sudo apt-get -o Acquire::ForceIPv4=true update
sudo apt-get -o Acquire::ForceIPv4=true upgrade
sudo apt-get -o Acquire::ForceIPv4=true dist-upgrade
sudo apt-get -o Acquire::ForceIPv4=true install kshMaintaner: Anibal Monsalve Salazar <anibal@debian.org>
Like for sed, maintainer Clint Adams <clint@debian.org>, the only motivations for those moves are hubris and deliberate intent to cause trouble.
Are you using excalibur?
Then the firmware-iwlwifi package installs the firmware to the wrong place; it installs into /usr/lib/firmware/intel whereas the kernel like always will want it in /lib/firmware/intel. If that's the case, please lodge a bug report to debian about it, as well as doing your own hands-on to make it work.
You are probably right even though that "decision" is obviously not a reason for changing the installation pathname.
Apparently many debian packagers have decided to install stuff at different pathnames than before, which means that any script or program that has used full path is no longer working.
Likewise all existing documentation using the old pathnames is then outdated and wrong.
The problem you run into is that debian firmware package maintainers have recently decides to install the firmware in a different directory from what the kernel looks in.
It boggles my mind how they could think that that would be a good idea.
You will need some manual hands-on to fix it.
If you have the disk image you can mount that on som other system and run that update command there. Or even patch the initrd directly (unpack, patch, pack).
Because the .desktop file uses full pathname.
Welcome back.
Just to note, I run daedalus with pure ALSA and firefox-esr but I have to run it under apulse for working audio. I do this by moving the binary /usr/lib/firefox-esr/firefox-esr to the filename firefox-esr.orig and then set it as a link to my start script (named firefox-esr.apulse). Here's that script:
#!/bin/sh
exec /usr/bin/apulse /usr/lib/firefox-esr/firefox-esr.orig "$@"The only "problem" with it is that firefox-esr updates replaces the link with its new binary, so I need to repeat moving it and restoring the link after update.
Possibly you can installl openjdk-8-jdk-headless from ceres first ?
Perhaps it gets better if you change "hw" to "plughw"... or maybe just remove that asound.conf (since it doesn't disagree with the default about which the default card is)
EDIT: note that the difference between "hw" and "plughw" is the absence/presence of audio format translations. "hw" tells ALSA to channel audio direclty to the card without translations while "plughw" tells it to insert audio format conversions as needed.
All installer ISO include (on the ISO) all firmware available in the repositories.
Choose the "1 Install" method.
"ManSpeed" ?
That looks like a "portmonnaie" word of MinSpeed and MaxSpeed.
There is a "man synaptics" to read.
And of course Debain bookworm, which underpins Devuan daedalus, had that major repository change of moving all firmware into the new non-free-firmware section. That change still causes confusion for everyone who whould expect only the traditional repository point changes at an upgrade.
In other words, there need to be a sources.list line naming the non-free-firmware section, e.g. by itself, like:
deb http://deb.devuan.org/merged daedalus non-free-firmwareor together with other sections, for example like
deb http://deb.devuan.org/merged daedalus main contrib non-free-firmwareAll Devuan derivatives are likely to have the same issue.
Unplug the mouse, run "tail -f /var/log/syslog > capture.log", then plug in the mouse and then type ctrl-C to stop the tail. Then drop in the log into a code box here.
"file manager"?
That's quite a useless piece of software.
It's so much easier to just type commands in a terminal (window).
1. Yes: sudo umount $HOME/.xsession-errors un-does the mount and brings back the old $HOME/.xsession-errors file... (you may want to remove it and then "touch the pathname" before you mount so it comes back without any random old log lines)
2. For this option, you'd need to create that $HOME/bin/logrot.sh script, make it executable, and then edit crontab to have that line (or your preferred variant thereof). This option only keeps a single backup named $HOME/.xsession-errors.1 as it reuses that pathname each time.
3. For this option you'd need to install logrotate and then configure that.. as per its "man" pages. I don't know exactly.
1. One option is to mount /dev/null onto it, like
sudo mount -obind /dev/null $HOME/.xsession-errorsThough doing this will discard all errors as they occur and that might be too forceful.
2. Another option is to drop a small script into $HOME/bin/logrot.sh, like
#!/bin/sh
#
# This script limits a file to a given number of lines, by moving it
# to a backup name when longer.
#
# $1=filename
# $2=max number of lines (defaults to 1000)
[ -r "$1" ] || exit 1 # The pathname is not readable
[ $(wc -l < $1) -lt ${2:-1000} ] && return 0 # The file is short enough
mv $1 $1.1 && touch $1 # Back it up and leave an emptyand then also add a crontab -e entry like this
37 5 * * * $HOME/bin/logrot.sh $HOME/.xsession-errors 2000so as to run that script once a day (at 5:37) and then "rotate" the file if it is longer than 2000 lines.
3. Another option is to use something like logrotate and configure that to bother about your $HOME/.xsession-errors
"Firefox" needs to be run by "apulse" so as to direct its audio through pure ALSA.
E.g. insert "apulse" first on the "Exec" line of the ".desktop" file(s) in use for starting "firefox".
Yeah, the core problem is that the ISO is not available as a mountable partition to the installer, but instead the installer would need to search for it as an image file among the available drives and partitions. It's a whole new use case collective that the installer is (was) not prepared for.
Otoh it's not terribly complicated to add such a search to it; possibly something coming out sooninsh.
Having had a sniff at Ventoy I see that it uses an exfat filsystem, which is not included in preamble.gz. Perhaps it's sufficient to add that ...
EDIT: no it's not sufficient.