Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
$ sudo dpkg --configure systemd-timesyncd
dpkg: error processing package systemd-timesyncd (--configure):
package systemd-timesyncd is not ready for configuration
cannot configure (current status 'config-files')
Errors were encountered while processing:
systemd-timesyncd
summary :
$ dpkg -l | grep -v ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-========================================-==========================================-============-=======================================================================================================================
iF linux-headers-5.10.0-21-amd64 5.10.162-1 amd64 Header files for Linux 5.10.0-21-amd64
iU linux-headers-amd64 5.10.162-1 amd64 Header files for Linux amd64 configuration (meta-package)
iF linux-image-5.10.0-21-amd64 5.10.162-1 amd64 Linux 5.10 for 64-bit PCs (signed)
iU linux-image-amd64 5.10.162-1 amd64 Linux for 64-bit PCs (meta-package)
rc systemd-timesyncd 1:247.3-6mx21 amd64 minimalistic service to synchronize local time with NTP servers
/[code]
OK, all this is related to the kernel installtion failed.
3710sudo wrote: Tue Jan 31, 2023 11:39 am
error for systemd-timesyncd
$ sudo dpkg --configure systemd-timesyncd
dpkg: error processing package systemd-timesyncd (--configure):
package systemd-timesyncd is not ready for configuration
cannot configure (current status 'config-files')
Errors were encountered while processing:
systemd-timesyncd
please ignore this one "systemd-timesyncd", b/c it is not installed anyway.
3710sudo wrote: Tue Jan 31, 2023 11:39 am
i've got a reboot when i type
3710sudo wrote: Tue Jan 31, 2023 11:39 am
"sudo dpkg --configure linux-headers-5.10.0-21-amd64",
$ dpkg -l | grep -v ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-========================================-==========================================-============-=======================================================================================================================
iF linux-headers-5.10.0-21-amd64 5.10.162-1 amd64 Header files for Linux 5.10.0-21-amd64
iU linux-headers-amd64 5.10.162-1 amd64 Header files for Linux amd64 configuration (meta-package)
iF linux-image-5.10.0-21-amd64 5.10.162-1 amd64 Linux 5.10 for 64-bit PCs (signed)
iU linux-image-amd64 5.10.162-1 amd64 Linux for 64-bit PCs (meta-package)
the computer reboot each time (i've tried for "sudo dpkg --configure linux-image-5.10.0-21-amd64 linux-headers-5.10.0-21-amd64" and other order "sudo dpkg --configure linux-headers-5.10.0-21-amd64 linux-image-5.10.0-21-amd64")
=> before MX Linux, i've tried to install UBUNTU, and after the installation from USB live, at first boot, the computer were rebooting during the loading of the system. I've tried several installation also LINUX MINT, and always rebooting during the system load!! , i finally give up with UBUNTU but it perhaps a problem with the new BIOS of my motherboard (i think MSI tells is a beta BIOS)
3710sudo wrote: Tue Jan 31, 2023 12:55 pm
the computer reboot each time (i've tried for "sudo dpkg --configure linux-image-5.10.0-21-amd64 linux-headers-5.10.0-21-amd64" and other order "sudo dpkg --configure linux-headers-5.10.0-21-amd64 linux-image-5.10.0-21-amd64")
=> before MX Linux, i've tried to install UBUNTU, and after the installation from USB live, at first boot, the computer were rebooting during the loading of the system. I've tried several installation also LINUX MINT, and always rebooting during the system load!! , i finally give up with UBUNTU but it perhaps a problem with the new BIOS of my motherboard (i think MSI tells is a beta BIOS)
Hmm, never seen suche reboot's ...
anyway would you try to remove all those,
$ sudo apt remove linux-headers-5.10.0-21-amd64 linux-headers-amd64 linux-image-5.10.0-21-amd64 linux-image-amd64
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
/[code]
sudo apt remove linux-headers-5.10.0-21-amd64 linux-headers-amd64 linux-image-5.10.0-21-amd64 linux-image-amd64
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
$ sudo apt remove linux-headers-amd64 linux-image-amd64
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
/[code]
i've made a new clean installation of MX LINUX, and after first update the PC reboot, and now i can't acces to the updater (it aske me « dpkg --configure -a », if i do, the PC reboot), system is clean without any apps such as windscribe...
=> i think my PC have a hardware problem : my motherboard is new under garrantee, i will try also with a old CPU...
Thanks for your help and the time passed fehlix !!!
edit 01 = i change the CPU (replace RYZEN 5 5600G by ATHLON 300G) : no reboot, all the things works well !!!
edit 02 : i found : my power supply (60W) is too low for the 5600G, i change for a 120W power supply
Last edited by 3710sudo on Fri Feb 03, 2023 9:02 am, edited 2 times in total.