You are not logged in.
- Topics: Active | Unanswered
#26 Re: Hardware & System Configuration » [SOLVED] upgrade succesful .. or not? (systemd) » 2026-07-30 17:26:04
thanks , i suppose the upgraded files theat are being pulled like @libpipewire/systemd or something *just one catch
is due to being automatically linked with the debian.system since i had disabled both pulseaduio.pipewire to the best of instructions received.
nothing to be concerned of, i guess, and thanks for the }requiredP{ reading.
much appreciated.
#27 Hardware & System Configuration » [SOLVED] upgrade succesful .. or not? (systemd) » 2026-07-30 10:33:48
- kapqa
- Replies: 6
Hello ,
have discovered the tool "nala" for update/upgrade and trying it out.
today it took some time to finish and left me with this message
Fetched 147.0 MB in 23s (6.4 MB/s)
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│✔ Running dpkg … ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 0:00:00 • 539/539│
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯Warning: unable to delete old directory '/lib/systemd/system': Directory not empty
Warning: unable to delete old directory '/lib/systemd': Directory not empty
Finished Successfully
may question:
am i allowed to delete those folders?
have seen that the upgrades pull quite some packages with "systemd" in namespace in for devuan 7.0 , but have taken notice of them all.
(most will probably be beningn?)
thank you.
#28 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-07-29 07:59:15
if you use windows 11 you can use "rufus" to make a bootable copy of devuan installer onto usb. if you have a dvd drive you could burn the iso onto dvd-(rw), that should function best. if it does not function over dvd, then most certainly a BIOS setting is wrong (can happen out of the gate, like "secure boot is enabled > need to change like if you want it enabled to "custom" instead of "windows uefi") etc.
#29 Re: Hardware & System Configuration » Radeon HD 5770 - free driver does not detect refresh rates above 60Hz » 2026-07-28 17:11:15
since was boasting fruitlessly about these card,
have since remembered shis sharedware, which is very handy on the computer )macinjack(
it maybe wont crank up the refresh rate, but atleast on the monitor here (mostly legacy format) it can operate other resoltuions which are native or not native? on the panel/(monitor; which to some degree very handy since it allows to "simulate" other resoultion to see how they would fit into frame, like 2560x1600 on 22 inch etc.
butt since it not native? resoultion, it looks not that genuine.
(noi AI corrigenda=)
https://ibb.co/60vdy1Td
#30 Re: Other Issues » [SOLVED] nvidia-persistenced daemon issue (sysvinit) » 2026-07-26 18:24:58
do also see error for newer graphics card, thought this is relegated to legacy gpu (nvidia-persistenced error)
Installing:
linux-headers-6.12.95+deb13-amd64
Installing dependencies:
libdw1t64 linux-headers-6.12.95+deb13-common linux-kbuild-6.12.95+deb13 pahole
Summary:
Upgrading: 0, Installing: 5, Removing: 0, Not Upgrading: 1
1 not fully installed or removed.
Download size: 16.4 MB
Space needed: 78.6 MB / 89.7 GB available
Continue? [Y/n]
Get:1 http://deb.devuan.org/merged excalibur/main amd64 libdw1t64 amd64 0.192-4 [255 kB]
Get:2 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-headers-6.12.95+deb13-common all 6.12.95-1 [11.1 MB]
Get:3 http://deb.devuan.org/merged excalibur/main amd64 pahole amd64 1.30-1 [259 kB]
Get:4 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-kbuild-6.12.95+deb13 amd64 6.12.95-1 [1,730 kB]
Get:5 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-headers-6.12.95+deb13-amd64 amd64 6.12.95-1 [3,057 kB]
Fetched 16.4 MB in 4s (4,587 kB/s)
Selecting previously unselected package libdw1t64:amd64.
(Reading database ... 208354 files and directories currently installed.)
Preparing to unpack .../libdw1t64_0.192-4_amd64.deb ...
Unpacking libdw1t64:amd64 (0.192-4) ...
Selecting previously unselected package linux-headers-6.12.95+deb13-common.
Preparing to unpack .../linux-headers-6.12.95+deb13-common_6.12.95-1_all.deb ...
Unpacking linux-headers-6.12.95+deb13-common (6.12.95-1) ...
Selecting previously unselected package pahole.
Preparing to unpack .../pahole_1.30-1_amd64.deb ...
Unpacking pahole (1.30-1) ...
Selecting previously unselected package linux-kbuild-6.12.95+deb13.
Preparing to unpack .../linux-kbuild-6.12.95+deb13_6.12.95-1_amd64.deb ...
Unpacking linux-kbuild-6.12.95+deb13 (6.12.95-1) ...
Selecting previously unselected package linux-headers-6.12.95+deb13-amd64.
Preparing to unpack .../linux-headers-6.12.95+deb13-amd64_6.12.95-1_amd64.deb ...
Unpacking linux-headers-6.12.95+deb13-amd64 (6.12.95-1) ...
Setting up nvidia-persistenced (550.163.01-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up libdw1t64:amd64 (0.192-4) ...
Setting up linux-headers-6.12.95+deb13-common (6.12.95-1) ...
Setting up pahole (1.30-1) ...
Setting up linux-kbuild-6.12.95+deb13 (6.12.95-1) ...
Setting up linux-headers-6.12.95+deb13-amd64 (6.12.95-1) ...
/etc/kernel/header_postinst.d/dkms:
Sign command: /lib/modules/6.12.95+deb13-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
Autoinstall of module nvidia-current/550.163.01 for kernel 6.12.95+deb13-amd64 (x86_64)
Building module(s)............. done.
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-peermem.ko
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-modeset.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-drm.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-uvm.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-peermem.ko.xz
Running depmod.... done.
Autoinstall on 6.12.95+deb13-amd64 succeeded for module(s) nvidia-current.
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Errors were encountered while processing:
nvidia-persistenced
Error: Sub-process /usr/bin/dpkg returned an error code (1)now since the driver is not complete tried with "nvidia-full" only to encounter again the nvidia-persistenced-error.
sudo apt install nvidia-driver-full --no-install-recommends
Installing:
nvidia-driver-full
Installing dependencies:
libcuda1 libnvidia-encode1 nvidia-driver-bin
libcudadebugger1 libnvidia-fbc1 nvidia-driver-libs
libegl-nvidia0 libnvidia-ml1 nvidia-egl-common
libgl1-nvidia-glvnd-glx libnvidia-ngx1 nvidia-egl-icd
libgles-nvidia1 libnvidia-nvvm4 nvidia-opencl-common
libgles-nvidia2 libnvidia-opticalflow1 nvidia-opencl-icd
libglx-nvidia0 libnvidia-pkcs11-openssl3 nvidia-persistenced
libnvcuvid1 libnvidia-ptxjitcompiler1 nvidia-powerd
libnvidia-allocator1 libnvidia-rtcore nvidia-settings
libnvidia-api1 libnvoptix1 nvidia-smi
libnvidia-cfg1 nvidia-cuda-mps nvidia-suspend-common
libnvidia-egl-wayland1 nvidia-detect nvidia-vulkan-common
libnvidia-eglcore nvidia-driver nvidia-vulkan-icd
Recommended packages:
libcuda1:i386 libnvidia-egl-gbm1 nvidia-driver-libs:i386
Summary:
Upgrading: 0, Installing: 40, Removing: 0, Not Upgrading: 0
Download size: 131 MB / 170 MB
Space needed: 482 MB / 85.7 GB available
Continue? [Y/n]
Get:1 http://deb.devuan.org/merged excalibur/non-free amd64 libcudadebugger1 amd64 550.163.01-2 [2,762 kB]
Get:2 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-api1 amd64 550.163.01-2 [375 kB]
Get:3 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-fbc1 amd64 550.163.01-2 [204 kB]
Get:4 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-ngx1 amd64 550.163.01-2 [2,410 kB]
Get:5 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-nvvm4 amd64 550.163.01-2 [21.9 MB]
Get:6 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-opticalflow1 amd64 550.163.01-2 [183 kB]
Get:7 http://deb.devuan.org/merged excalibur/non-free amd64 libnvoptix1 amd64 550.163.01-2 [99.0 MB]
Get:8 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-cuda-mps amd64 550.163.01-2 [190 kB]
Get:9 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-detect amd64 550.163.01-2 [166 kB]
Get:10 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-opencl-common amd64 550.163.01-2 [162 kB]
Get:11 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-opencl-icd amd64 550.163.01-2 [2,765 kB]
Get:12 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-powerd amd64 550.163.01-2 [244 kB]
Get:13 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-driver-full amd64 550.163.01-2 [161 kB]
Fetched 131 MB in 9s (13.9 MB/s)
Extracting templates from packages: 100%
Selecting previously unselected package libnvidia-ptxjitcompiler1:amd64.
(Reading database ... 281657 files and directories currently installed.)
Preparing to unpack .../00-libnvidia-ptxjitcompiler1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ptxjitcompiler1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-pkcs11-openssl3:amd64.
Preparing to unpack .../01-libnvidia-pkcs11-openssl3_550.163.01-2_amd64.deb ...
Unpacking libnvidia-pkcs11-openssl3:amd64 (550.163.01-2) ...
Selecting previously unselected package libcuda1:amd64.
Preparing to unpack .../02-libcuda1_550.163.01-2_amd64.deb ...
Unpacking libcuda1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-eglcore:amd64.
Preparing to unpack .../03-libnvidia-eglcore_550.163.01-2_amd64.deb ...
Unpacking libnvidia-eglcore:amd64 (550.163.01-2) ...
Selecting previously unselected package libglx-nvidia0:amd64.
Preparing to unpack .../04-libglx-nvidia0_550.163.01-2_amd64.deb ...
Unpacking libglx-nvidia0:amd64 (550.163.01-2) ...
Selecting previously unselected package libgl1-nvidia-glvnd-glx:amd64.
Preparing to unpack .../05-libgl1-nvidia-glvnd-glx_550.163.01-2_amd64.deb ...
Unpacking libgl1-nvidia-glvnd-glx:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-egl-common.
Preparing to unpack .../06-nvidia-egl-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-egl-common (550.163.01-2) ...
Selecting previously unselected package libnvidia-egl-wayland1:amd64.
Preparing to unpack .../07-libnvidia-egl-wayland1_1%3a1.1.18-1_amd64.deb ...
Unpacking libnvidia-egl-wayland1:amd64 (1:1.1.18-1) ...
Selecting previously unselected package libegl-nvidia0:amd64.
Preparing to unpack .../08-libegl-nvidia0_550.163.01-2_amd64.deb ...
Unpacking libegl-nvidia0:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-egl-icd:amd64.
Preparing to unpack .../09-nvidia-egl-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-egl-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-libs:amd64.
Preparing to unpack .../10-nvidia-driver-libs_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-libs:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-ml1:amd64.
Preparing to unpack .../11-libnvidia-ml1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ml1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-bin.
Preparing to unpack .../12-nvidia-driver-bin_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-bin (550.163.01-2) ...
Selecting previously unselected package nvidia-driver.
Preparing to unpack .../13-nvidia-driver_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver (550.163.01-2) ...
Selecting previously unselected package libnvidia-cfg1:amd64.
Preparing to unpack .../14-libnvidia-cfg1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-cfg1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-persistenced.
Preparing to unpack .../15-nvidia-persistenced_550.163.01-1_amd64.deb ...
Unpacking nvidia-persistenced (550.163.01-1) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../16-nvidia-settings_550.163.01-1_amd64.deb ...
Unpacking nvidia-settings (550.163.01-1) ...
Selecting previously unselected package libcudadebugger1:amd64.
Preparing to unpack .../17-libcudadebugger1_550.163.01-2_amd64.deb ...
Unpacking libcudadebugger1:amd64 (550.163.01-2) ...
Selecting previously unselected package libgles-nvidia1:amd64.
Preparing to unpack .../18-libgles-nvidia1_550.163.01-2_amd64.deb ...
Unpacking libgles-nvidia1:amd64 (550.163.01-2) ...
Selecting previously unselected package libgles-nvidia2:amd64.
Preparing to unpack .../19-libgles-nvidia2_550.163.01-2_amd64.deb ...
Unpacking libgles-nvidia2:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvcuvid1:amd64.
Preparing to unpack .../20-libnvcuvid1_550.163.01-2_amd64.deb ...
Unpacking libnvcuvid1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-allocator1:amd64.
Preparing to unpack .../21-libnvidia-allocator1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-allocator1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-api1:amd64.
Preparing to unpack .../22-libnvidia-api1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-api1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-encode1:amd64.
Preparing to unpack .../23-libnvidia-encode1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-encode1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-fbc1:amd64.
Preparing to unpack .../24-libnvidia-fbc1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-fbc1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-ngx1:amd64.
Preparing to unpack .../25-libnvidia-ngx1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ngx1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-nvvm4:amd64.
Preparing to unpack .../26-libnvidia-nvvm4_550.163.01-2_amd64.deb ...
Unpacking libnvidia-nvvm4:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-opticalflow1:amd64.
Preparing to unpack .../27-libnvidia-opticalflow1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-opticalflow1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-rtcore:amd64.
Preparing to unpack .../28-libnvidia-rtcore_550.163.01-2_amd64.deb ...
Unpacking libnvidia-rtcore:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvoptix1:amd64.
Preparing to unpack .../29-libnvoptix1_550.163.01-2_amd64.deb ...
Unpacking libnvoptix1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-cuda-mps.
Preparing to unpack .../30-nvidia-cuda-mps_550.163.01-2_amd64.deb ...
Unpacking nvidia-cuda-mps (550.163.01-2) ...
Selecting previously unselected package nvidia-detect.
Preparing to unpack .../31-nvidia-detect_550.163.01-2_amd64.deb ...
Unpacking nvidia-detect (550.163.01-2) ...
Selecting previously unselected package nvidia-vulkan-common.
Preparing to unpack .../32-nvidia-vulkan-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-vulkan-common (550.163.01-2) ...
Selecting previously unselected package nvidia-vulkan-icd:amd64.
Preparing to unpack .../33-nvidia-vulkan-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-vulkan-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-smi.
Preparing to unpack .../34-nvidia-smi_550.163.01-2_amd64.deb ...
Unpacking nvidia-smi (550.163.01-2) ...
Selecting previously unselected package nvidia-opencl-common.
Preparing to unpack .../35-nvidia-opencl-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-opencl-common (550.163.01-2) ...
Selecting previously unselected package nvidia-opencl-icd:amd64.
Preparing to unpack .../36-nvidia-opencl-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-opencl-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-powerd.
Preparing to unpack .../37-nvidia-powerd_550.163.01-2_amd64.deb ...
Unpacking nvidia-powerd (550.163.01-2) ...
Selecting previously unselected package nvidia-suspend-common.
Preparing to unpack .../38-nvidia-suspend-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-suspend-common (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-full.
Preparing to unpack .../39-nvidia-driver-full_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-full (550.163.01-2) ...
Setting up libnvidia-eglcore:amd64 (550.163.01-2) ...
Setting up nvidia-egl-common (550.163.01-2) ...
Setting up libnvidia-ml1:amd64 (550.163.01-2) ...
Setting up nvidia-detect (550.163.01-2) ...
Setting up nvidia-powerd (550.163.01-2) ...
Setting up nvidia-opencl-common (550.163.01-2) ...
Setting up libnvidia-cfg1:amd64 (550.163.01-2) ...
Setting up libnvidia-allocator1:amd64 (550.163.01-2) ...
Setting up libglx-nvidia0:amd64 (550.163.01-2) ...
Setting up libnvidia-egl-wayland1:amd64 (1:1.1.18-1) ...
Setting up libnvidia-pkcs11-openssl3:amd64 (550.163.01-2) ...
Setting up libnvidia-ngx1:amd64 (550.163.01-2) ...
Setting up nvidia-cuda-mps (550.163.01-2) ...
Setting up libgles-nvidia1:amd64 (550.163.01-2) ...
Setting up libnvidia-ptxjitcompiler1:amd64 (550.163.01-2) ...
Setting up nvidia-vulkan-common (550.163.01-2) ...
Setting up libegl-nvidia0:amd64 (550.163.01-2) ...
Setting up nvidia-settings (550.163.01-1) ...
Setting up libnvidia-nvvm4:amd64 (550.163.01-2) ...
Setting up libgles-nvidia2:amd64 (550.163.01-2) ...
Setting up libnvidia-api1:amd64 (550.163.01-2) ...
Setting up libnvidia-rtcore:amd64 (550.163.01-2) ...
Setting up nvidia-suspend-common (550.163.01-2) ...
Processing triggers for nvidia-alternative (550.163.01-2) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link g
roup nvidia has changed slave links
Setting up nvidia-persistenced (550.163.01-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess retur
ned error exit status 1
Processing triggers for hicolor-icon-theme (0.18-2) ...
Setting up libcuda1:amd64 (550.163.01-2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Setting up nvidia-opencl-icd:amd64 (550.163.01-2) ...
Setting up nvidia-egl-icd:amd64 (550.163.01-2) ...
Processing triggers for man-db (2.13.1-1) ...
Setting up libnvoptix1:amd64 (550.163.01-2) ...
Setting up nvidia-vulkan-icd:amd64 (550.163.01-2) ...
Setting up libnvidia-fbc1:amd64 (550.163.01-2) ...
Setting up libgl1-nvidia-glvnd-glx:amd64 (550.163.01-2) ...
dpkg: dependency problems prevent configuration of nvidia-driver-full:
nvidia-driver-full depends on nvidia-persistenced; however:
Package nvidia-persistenced is not configured yet.
dpkg: error processing package nvidia-driver-full (--configure):
dependency problems - leaving unconfigured
Setting up libcudadebugger1:amd64 (550.163.01-2) ...
Setting up nvidia-smi (550.163.01-2) ...
Setting up nvidia-driver-bin (550.163.01-2) ...
Setting up nvidia-driver-libs:amd64 (550.163.01-2) ...
Setting up libnvcuvid1:amd64 (550.163.01-2) ...
Setting up libnvidia-opticalflow1:amd64 (550.163.01-2) ...
Setting up nvidia-driver (550.163.01-2) ...
Setting up libnvidia-encode1:amd64 (550.163.01-2) ...
Processing triggers for glx-alternative-nvidia (1.2.2) ...
Processing triggers for glx-alternative-mesa (1.2.2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Processing triggers for update-glx (1.2.2) ...
Processing triggers for glx-alternative-nvidia (1.2.2) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvi
dia because link group glx is broken
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Processing triggers for initramfs-tools (0.148.4) ...
update-initramfs: Generating /boot/initrd.img-6.12.96+deb13-amd64
Errors were encountered while processing:
nvidia-persistenced
nvidia-driver-full
Error: Sub-process /usr/bin/dpkg returned an error code (1)when i install "nvidia-driver" it goes through (--no-install-recommends) but afterwards no cuda , no opencl??
when install "nvidia-driver-full" it stops because "nvidia-driver-full" depends on "nvidia-persistenced"?
#31 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 14:03:02
i am using somethimes adguard on my miinimall image arm64 pine-a64 running minimal armbian or devuan, like ti better than pihole, but then i uninstall again,since the added value is minimal for my setup; and it adds abit latency;
also it is easier to install;
the raspberry 3 still have a libreelec use soemtimes, since i have bought mpeg-keys for 1-2-3.
#33 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 13:44:22
if you have given already your own, ti is yours.
http://jarnotuovinen.com/devuan-4-chima … berry-pi-3
apt-get install ssh
#34 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 13:33:47
zou could try root toor
or root 1234
but first probably you would need to enable ssh on the machine since with devuan it could be that it is not enabled by default (as it is easy to setup for raspberry pios)
#35 Re: Packaging for Devuan » [SOLVED] Access to Beowulf packages » 2026-07-24 20:14:29
most likely you need to change "deb.devuan.org" to "archive.devuan.org" or similar,
thats the way debian handled it lately, and i needed to do so also during installer if used an older release, but for some reason devuan-installer doesnt like it so muchh and often the install would fail from netinstall; whereas with debian the "archive" is bit more accessible.
#36 Desktop and Multimedia » [SOLVED] Browser (/no longer) playing audio? » 2026-07-22 22:24:08
- kapqa
- Replies: 0
Hello ,
have made a change in audio setup
now only with monitor audio + dac for some time.
would like be unpretentious;
but this thing a bit strange ,
since am sure that with this browser "nightly" could play audio , but now it seems it no longer plays any audio.
previously had firefox-esr + nightly (compiled via instructions from forum)
now have firefox-esr + nightly (had audio) + firefox developer (has audio).
it is bit strange, because am pretty sure it functioned before, and now it seem no longer;
please just ignore this thread if you like because maybe i am just a bit oomm.
the nighly reports (max channel = 0) - am a bit puzzled.
https://ibb.co/GvpTY1DM
https://ibb.co/PGWVwQBz
https://ibb.co/cS2XQjNC
thanks for ignoring.
#38 Re: Hardware & System Configuration » Radeon HD 5770 - free driver does not detect refresh rates above 60Hz » 2026-07-17 09:48:13
have employed or had so both cards, however for use on an old mac pro;
especially the 6770 was sought after at the time, since it could very well perform for mac os x 10.6+ ]
<>
however have sadly no real high refresh monitor so the "advice" is not tested since my monitor dont go over 75hz (on vga analog only, one monitor can do it also via dvi) ] besides older crt monitor but that one is not in use.
the chit-chat give passable responses for technical question, here is what he responded.
Max Resolution & Refresh Rates by PortDisplayPort 1.2 or Dual-Link DVI: 2560 × 1600 at 60Hz is the hard limit. You cannot run a 4K monitor at native resolution on this card.HDMI (Version 1.4a): 1920 × 1200 at 60Hz. Note that while the port can push standard 1080p (1920 × 1080), it is locked to a max of 60Hz over HDMI due to early generation firmware limitations.VGA (Analog): 2048 × 1536 at 85Hz.
that is what my experience would also have told you, if you have a high refresh monitor , and your resolution is not in the listing of the supported refresh modes (normally found in manual) you most probably would have to lower your resolution to achieve higher refresh rate (as was the case for most not-high-end crt probably)
Max Resolution Limits for HD 5770DisplayPort (or Mini-DisplayPort) & Dual-Link DVI: Hard limited to 2560 × 1600 at 60Hz.HDMI: Hard limited to 1920 × 1200 at 60Hz.VGA (Analog): Hard limited to 2048 × 1536 at 85Hz.
at the moment for the older mac am using hd 4870 since found that the card is still capable and function thad better with newer macos ] but that is not what you have asked for.
basically, you will be "locked" into the capabilities of your gpu, and software-overrides wont "squeeze" the direct high-refresh rates say on one of those newer 100hz monitors it would suggest, but could be wrong on this (since it supporting 2560x1600 at 60hz it could or should very well support 1920x1200x100hz, but you most certainly will find difficulty finding it to support 2560-1600x120hz, if such a panel exists on market outside laptop space yet).
#39 Re: Installation » Which Excalibur install problems fixed by 6.1.1? » 2026-07-12 11:20:39
had my own share of issues with dexcalibure 6.1.1 this week ~
had already a triple boot on am4 inplace but decided to make space for devuan since nowadays can live totally without ubuntu since all software also available to some degree on devuan.
however, it took me several times to install-reinstall since the first two attempts failed for reasons not fully understood.
the first time i made usb stick with mkusb ~ the install probably went through ~ but afterwards grub complained something about shim-something, "you need to load the kernel frist"
made probably another attempt , this time usb stick made with "rufus" - standard settings (mbr > bios or uefi) and made sure it booted via uefi; again, went through, but the same error at grub.
it dawned on me, to change probably the UEFI secure boot setting from "standard" to "custom" in BIOS;
but after another attempt, the same RUFUS made usb image, again the error "you need to load kernel first" ~
luckily i have already burned excalbure 6.1.1 onto dvd-rw (very many thanks for that!=) and with the dvd.iso image it went through and booted;
would like to emphasize that for the usb-stick i used also the full 6.1.1.iso and not the net-install;
in general i have had most luck installing linux with burned .iso onto dvd, no matter the distro;with devuan 6.1. especially had more problems installing overall than with other distro, espcially when compared to previous iterations of devuan; but its worth the effort, devuan function just well after setup, glad have found it.
#40 Re: Installation » [SOLVED] UMAX AstraSlim SE - Invalid argument » 2026-07-09 15:41:35
remember some 5-8 years ago when ürchased the first ecotank printer,
that it was difficult sometime to scan with certain programs, not all would function equal, so i tired them through, (all) the different programs that were available,
and not all would function for the scanner for some reason or another; even the epson program itself would not function; so i started installing drivers etc, but since a lot has changed;
have an old samsung all-in-one here (relegated to shelve, since it laser), might aswell test it wout someday to see if can get scanning to function.
sometimes i do chit-chat-with gemini-chatbot since ma curiuos being;
but it warns that the answers can be inaccurate.
To grant your Linux system permissions to use an Epson scanner without root access, you must create a custom udev rule. This assigns the device to the scanner group and sets appropriate read/write permissions.Step 1: Find your Vendor and Product IDOpen a terminal and type lsusb. Look for your Epson device in the list and note down its IDs, which look similar to 04b8:012f (where 04b8 is the Vendor ID and 012f is the Product ID).Step 2: Create the udev RuleOpen a new rule file in your preferred text editor (e.g., Nano) with superuser privileges:sudo nano /etc/udev/rules.d/99-epson-scanner.rulesAdd the following line (replace YOUR_VENDOR_ID and YOUR_PRODUCT_ID with the numbers from Step 1):SUBSYSTEM=="usb", ATTRS{idVendor}=="YOUR_VENDOR_ID", ATTRS{idProduct}=="YOUR_PRODUCT_ID", MODE="0666", GROUP="scanner", ENV{libsane_matched}="yes"
Save the file and exit the text editor.Step 3: Apply and VerifyReload the udev rules for the changes to take effect:sudo udevadm control --reload-rulesUnplug your scanner's USB cable and plug it back in.Check if your user account is in the scanner group (if not, add it using sudo usermod -a -G scanner $USER).Run scanimage -L in your terminal to verify that your Epson scanner is detected.For more technical background on writing hardware rules, you can refer to general guides on Writing udev rules.Could you tell me the exact model of your Epson scanner and which Linux distribution you are using? This will allow me to provide the exact idVendor and idProduct numbers for your device, or help you troubleshoot specific SANE driver issues if they arise.
#41 Re: Hardware & System Configuration » How to set system time? » 2026-07-09 11:59:22
Current default time zone: 'Europe/Rome'
Local time is now: Thu Jul 9 13:45:59 CEST 2026.
Universal Time is now: Thu Jul 9 11:45:59 UTC 2026.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
think the .reg file trick shared by Mr. RedGreen925 is very helpful;
it functioned on 1 computer that i use here quite reliably; however, it takes the windows machine about a half or minute or so to adjust; but otherwise it seem to function; but probably, it needs an internet connection to function.
where i live the UTC "universal" time seem not so much off, so i am not at odds with it;
very mjuch more so with the "current local time" which is affront, so calld "DST" "ora legale" "Sommerzeit" etc ~
basically in small room can get 3 different times depending on where i watch ~
TV gives me like 07.39 (UTC)
my smartwatch on wrist 08.39 (local-time) > since have the wrist-watch not synced for along time.
radio-clock in kitchen-space 09-39 (local-"summer"-time) > the stupid does "align" itself via radio probably
the local-time is most true to the sun since it probaly 15min ahead of loca-tun-time~
and UTC is probably 45min behind suntime ~
whereas the "summer-time" "day-light-saving-time" if full 75minutes "ahead" of sun and a real bummer so doing my best to ignore it ~ but since it is ~ "legal" time, well, not fully to ignore, but thats for another topic.
it would be nice to set the time in BIOS, and that could be it.
#42 Re: Hardware & System Configuration » Invalid PCI Header Signature error » 2026-07-09 07:03:27
its not much of an advice, but you could always try a fresh install,
see no reason why it should not function;
have an older laptop with "carrizo" or "kabini" based graphics and it still function with devuan 7.
sudo dmesg | grep amdgpu
[sudo] password for :
[ 15.624597] amdgpu: Virtual CRAT table created for CPU
[ 15.624676] amdgpu: Topology: Add CPU node
[ 15.625191] amdgpu 0000:00:01.0: initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x17AA:0x5120 0xC9).
[ 15.661524] amdgpu 0000:00:01.0: register mmio base: 0xF0F00000
[ 15.661532] amdgpu 0000:00:01.0: register mmio size: 262144
[ 15.662084] amdgpu 0000:00:01.0: detected ip block number 0 <common_v1_0_0> (vi_common)
[ 15.662095] amdgpu 0000:00:01.0: detected ip block number 1 <gmc_v8_0_0> (gmc_v8_0)
[ 15.662110] amdgpu 0000:00:01.0: detected ip block number 2 <ih_v3_0_0> (cz_ih)
[ 15.662114] amdgpu 0000:00:01.0: detected ip block number 3 <gfx_v8_0_0> (gfx_v8_0)
[ 15.662117] amdgpu 0000:00:01.0: detected ip block number 4 <sdma_v3_0_0> (sdma_v3_0)
[ 15.662120] amdgpu 0000:00:01.0: detected ip block number 5 <smu_v1_0_0> (powerplay)
[ 15.662123] amdgpu 0000:00:01.0: detected ip block number 6 <dce_v1_0_0> (dm)
[ 15.662126] amdgpu 0000:00:01.0: detected ip block number 7 <uvd_v6_0_0> (uvd_v6_0)
[ 15.662129] amdgpu 0000:00:01.0: detected ip block number 8 <vce_v3_1_0> (vce_v3_0)
[ 15.662132] amdgpu 0000:00:01.0: detected ip block number 9 <acp_v2_2_0> (acp_ip)
[ 15.674451] amdgpu 0000:00:01.0: Fetched VBIOS from ROM BAR
[ 15.674456] amdgpu 0000:00:01.0: [drm] ATOM BIOS: 113-C75100-031
[ 15.678025] amdgpu 0000:00:01.0: [drm] UVD is enabled in physical mode
[ 15.680078] amdgpu 0000:00:01.0: Found VCE firmware Version: 52.4 Binary ID: 3
[ 15.680087] amdgpu 0000:00:01.0: [drm] VCE enabled in physical mode
[ 15.680705] amdgpu 0000:00:01.0: vgaarb: deactivate vga console
[ 15.680710] amdgpu 0000:00:01.0: Trusted Memory Zone (TMZ) feature not supported
[ 15.680714] amdgpu 0000:00:01.0: PCIE atomic ops is not supported
[ 15.680764] amdgpu 0000:00:01.0: vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[ 15.680774] amdgpu 0000:00:01.0: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used)
[ 15.680778] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
[ 15.680793] amdgpu 0000:00:01.0: [drm] Detected VRAM RAM=1024M, BAR=1024M
[ 15.680796] amdgpu 0000:00:01.0: [drm] RAM width 128bits UNKNOWN
[ 15.681051] amdgpu 0000:00:01.0: 1024M of VRAM memory ready
[ 15.681056] amdgpu 0000:00:01.0: 7449M of GTT memory ready.
[ 15.681101] amdgpu 0000:00:01.0: [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 15.681666] amdgpu 0000:00:01.0: [drm] PCIE GART of 1024M enabled (table at 0x000000F400E00000).
[ 15.688241] amdgpu: hwmgr_sw_init smu backed is smu8_smu
[ 15.690399] amdgpu 0000:00:01.0: [drm] Found UVD firmware Version: 1.91 Family ID: 11
[ 15.690469] amdgpu 0000:00:01.0: [drm] UVD ENC is disabled
[ 15.693026] amdgpu: smu version 27.18.00
[ 15.699361] amdgpu 0000:00:01.0: [drm] Display Core v3.2.369 initialized on DCE 11.0
[ 15.713298] snd_hda_intel 0000:00:01.1: bound 0000:00:01.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 15.754619] amdgpu 0000:00:01.0: [drm] Using ACPI provided EDID for eDP-1
[ 15.785324] amdgpu 0000:00:01.0: [drm] UVD initialized successfully.
[ 15.984828] amdgpu 0000:00:01.0: [drm] VCE initialized successfully.
[ 15.985930] amdgpu 0000:00:01.0: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6
[ 15.987124] amdgpu: pp_dpm_get_sclk_od was not implemented.
[ 15.987128] amdgpu: pp_dpm_get_mclk_od was not implemented.
[ 15.987316] amdgpu 0000:00:01.0: Runtime PM not available
[ 15.996967] amdgpu 0000:00:01.0: [drm] Using custom brightness curve
[ 15.997483] amdgpu 0000:00:01.0: [drm] Registered 3 planes with drm panic
[ 16.016758] [drm] Initialized amdgpu 3.64.0 for 0000:00:01.0 on minor 0
[ 16.023676] fbcon: amdgpudrmfb (fb0) is primary device
[ 16.699733] amdgpu 0000:00:01.0: [drm] fb0: amdgpudrmfb frame buffer device00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev c9) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device 5120
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupts: pin B disabled, MSI(X) routed to IRQ 60
IOMMU group: 0
Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f0000000 (64-bit, prefetchable) [size=8M]
Region 4: I/O ports at 2000 [size=256]
Region 5: Memory at f0f00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: amdgpu
Kernel modules: amdgpu
00: 02 10 74 98 07 04 10 00 c9 00 00 03 08 00 80 00
10: 0c 00 00 e0 00 00 00 00 0c 00 00 f0 00 00 00 00
20: 01 20 00 00 00 00 f0 f0 00 00 00 00 aa 17 20 51
30: 00 00 fe ff 48 00 00 00 00 00 00 00 0b 01 00 00#43 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-08 20:26:12
for fairness sake,
this is a quite a newer computer, with cpu from amd
whereis amd64-microcode
amd64-microcode:
OPERATING SYSTEM: Linuxmint 22.3
Kernel: 6.17.0-35-generic (x86_64)
Display Server: X Server 1.21.1.11
Compiler: GCC 13.3.0
Security: gather_data_sampling: Not affected
+ ghostwrite: Not affected
+ indirect_target_selection: Not affected
+ itlb_multihit: Not affected
+ l1tf: Not affected
+ mds: Not affected
+ meltdown: Not affected
+ mmio_stale_data: Not affected
+ old_microcode: Not affected
+ reg_file_data_sampling: Not affected
+ retbleed: Not affected
+ spec_rstack_overflow: Mitigation of IBPB on VMEXIT only
+ spec_store_bypass: Mitigation of SSB disabled via prctl
+ spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization
+ spectre_v2: Mitigation of Enhanced / Automatic IBRS; IBPB: conditional; STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not affected
+ srbds: Not affected
+ tsa: Not affected
+ tsx_async_abort: Not affected
+ vmscape: Mitigation of IBPB on VMEXIT not all software made easy.
#44 Re: Installation » [SOLVED] UMAX AstraSlim SE - Invalid argument » 2026-07-08 15:02:33
you still could try the "forever" trick
sudo apt-get remove ipp-usb
reboot, try again, have luck.
#45 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-07 19:52:50
sure , maybe the destroyer will let you know,
in the meantime, applied the "intel-microcode" , rebooted ;
small changes , but probably still inherently unsafe to run the said hardware /
OPERATING SYSTEM: Devuan 6
Kernel: 6.12.95+deb13-amd64 (x86_64)
Display Server: X Server 1.21.1.16
Compiler: GCC 14.2.0
Security: gather_data_sampling: Not affected
+ indirect_target_selection: Not affected
+ itlb_multihit: KVM: Mitigation of VMX unsupported
+ l1tf: Mitigation of PTE Inversion
+ mds: Mitigation of Clear buffers; SMT vulnerable
+ meltdown: Mitigation of PTI
+ mmio_stale_data: Unknown: No mitigations
+ reg_file_data_sampling: Not affected
+ retbleed: Not affected
+ spec_rstack_overflow: Not affected
+ spec_store_bypass: Mitigation of SSB disabled via prctl
+ spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization
+ spectre_v2: Mitigation of Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
+ srbds: Not affected
+ tsa: Not affected
+ tsx_async_abort: Not affected
+ vmscape: Mitigation of IBPB before exit userspace #46 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-07 13:36:37
funnily was about to post a similar topic than "destroyer"
have encountered this both on amd and intel computer, the software says
spec_store_bypass: Mitigation of SSB disabled via prctl
thought this might have caused myself since i had "secure boot" or similar in place, but disabled afterwards for some reason currently unknown.
here is the output for the intel computer; for amd it is similar;
OPERATING SYSTEM: Devuan 6
Kernel: 6.12.95+deb13-amd64 (x86_64)
Display Server: X Server 1.21.1.16
Compiler: GCC 14.2.0
Security: gather_data_sampling: Not affected
+ indirect_target_selection: Not affected
+ itlb_multihit: KVM: Mitigation of VMX unsupported
+ l1tf: Mitigation of PTE Inversion
+ mds: Vulnerable: Clear buffers attempted no microcode; SMT vulnerable
+ meltdown: Mitigation of PTI
+ mmio_stale_data: Unknown: No mitigations
+ reg_file_data_sampling: Not affected
+ retbleed: Not affected
+ spec_rstack_overflow: Not affected
[b]+ spec_store_bypass: Mitigation of SSB disabled via prctl [/b]
+ spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization
+ spectre_v2: Mitigation of Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
+ srbds: Not affected
+ tsa: Not affected
+ tsx_async_abort: Not affected
+ vmscape: Mitigation of IBPB before exit userspace #47 Re: Hardware & System Configuration » How to set system time? » 2026-07-02 18:00:19
i think the confusion stems also from the fact that during installation i set "language: englsish"
but i live somehwere else, and i am however constrained to select a region that has "english mapping" and hence everything goes tupsy turvy;
this is probably a limitating on the lclassic debian-inux installer.
#48 Re: Hardware & System Configuration » How to set system time? » 2026-07-02 15:15:12
would have to guess, but apparently i am able to mess up the time every other time i boot into windows and back , or so ~
there have been kind peopel on this forum who told me how to fix time with windows tricks ]
but those have tricks not lasted that long also use several computer , and what function on one, seem not always stable on another. . it has probably to do aswell with the computers itself; and maybe also language, regional settings may interfere?
maybe some day we can get to to the bottom of it.
#49 Re: Hardware & System Configuration » How to set system time? » 2026-07-02 14:42:10
sudo apt install ntpsec-ntpdate
is valid for devuan 6.0
sudo ntpdate-debian2026-07-02 16:39:31.356971 (+0200) +0.170255 +/- 0.010254 0.debian.pool.ntp.org 37.247.53.178 s2 no-leapbut with dual-boot windows + linux there is still woes, at least on computers that i use.
#50 Re: Hardware & System Configuration » [SOLVED] upgrade to Excalibure partly succesful » 2026-07-01 19:30:07
now i have install "dummy-logind" and it seemed to go through (tasksel > mate-desktop) however at the end there was still error
sudo apt upgrade
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
2 not fully installed or removed.
Space needed: 0 B / 37.0 GB available
Continue? [Y/n]
dpkg: dependency problems prevent configuration of libpam-elogind:amd64:
libpam-elogind:i386 (255.17-2) breaks libpam-systemd and is unpacked but not co
nfigured.
libpam-elogind:amd64 (255.17-2) provides libpam-systemd.
dpkg: error processing package libpam-elogind:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpam-elogind:i386:
libpam-elogind:amd64 (255.17-2) breaks libpam-systemd and is unpacked but not c
onfigured.
libpam-elogind:i386 (255.17-2) provides libpam-systemd.
dpkg: error processing package libpam-elogind:i386 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libpam-elogind:amd64
libpam-elogind:i386
Error: Sub-process /usr/bin/dpkg returned an error code (1)afterwards
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
14 not fully installed or removed.
Space needed: 0 B / 37.0 GB available
Continue? [Y/n]
dpkg: dependency problems prevent configuration of libpam-elogind:amd64:
libpam-elogind:i386 (255.17-2) breaks libpam-systemd and is installed.
libpam-elogind:amd64 (255.17-2) provides libpam-systemd.
dpkg: error processing package libpam-elogind:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of network-manager:
network-manager depends on default-logind | logind; however:
Package default-logind is not installed.
Package libpam-elogind:amd64 which provides default-logind is not configured y
et.
Package logind is not installed.
Package libpam-elogind:amd64 which provides logind is not configured yet.
dpkg: error processing package network-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nm-connection-editor:
nm-connection-editor depends on network-manager; however:
Package network-manager is not configured yet.
dpkg: error processing package nm-connection-editor (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of network-manager-applet:
network-manager-applet depends on nm-connection-editor (= 1.36.0-3+b1); however
:
Package nm-connection-editor is not configured yet.
network-manager-applet depends on network-manager; however:
Package network-manager is not configured yet.
dpkg: error processing package network-manager-applet (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of udisks2:
udisks2 depends on default-logind | logind; however:
Package default-logind is not installed.
Package libpam-elogind:amd64 which provides default-logind is not configured y
et.
Package logind is not installed.
Package libpam-elogind:amd64 which provides logind is not configured yet.
dpkg: error processing package udisks2 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gvfs-daemons:
gvfs-daemons depends on udisks2; however:
Package udisks2 is not configured yet.
dpkg: error processing package gvfs-daemons (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gvfs-backends:
gvfs-backends depends on gvfs-daemons (= 1.57.2-2+deb13u1); however:
Package gvfs-daemons is not configured yet.
dpkg: error processing package gvfs-backends (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gvfs:amd64:
gvfs:amd64 depends on gvfs-daemons (<< 1.57.2-2+deb13u1.1~); however:
Package gvfs-daemons is not configured yet.
gvfs:amd64 depends on gvfs-daemons (>= 1.57.2-2+deb13u1); however:
Package gvfs-daemons is not configured yet.
dpkg: error processing package gvfs:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mate-desktop-environment-core
:
mate-desktop-environment-core depends on gvfs-backends; however:
Package gvfs-backends is not configured yet.
dpkg: error processing package mate-desktop-environment-core (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of caja:
caja depends on gvfs; however:
Package gvfs:amd64 is not configured yet.
dpkg: error processing package caja (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mate-desktop-environment:
mate-desktop-environment depends on mate-desktop-environment-core (= 1.26.0+2);
however:
Package mate-desktop-environment-core is not configured yet.
dpkg: error processing package mate-desktop-environment (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of task-mate-desktop:
task-mate-desktop depends on mate-desktop-environment; however:
Package mate-desktop-environment is not configured yet.
dpkg: error processing package task-mate-desktop (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gvfs-fuse:
gvfs-fuse depends on gvfs (= 1.57.2-2+deb13u1); however:
Package gvfs:amd64 is not configured yet.
dpkg: error processing package gvfs-fuse (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mate-applets:
mate-applets depends on gvfs; however:
Package gvfs:amd64 is not configured yet.
dpkg: error processing package mate-applets (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libpam-elogind:amd64
network-manager
nm-connection-editor
network-manager-applet
udisks2
gvfs-daemons
gvfs-backends
gvfs:amd64
mate-desktop-environment-core
caja
mate-desktop-environment
task-mate-desktop
gvfs-fuse
mate-appletsBoard footer
