MX Linux Forum

Posted: **Wed May 04, 2022 8:30 am**

I have MX 19.4 installed on a rarely-used spare laptop. I thought it was probably time to update it, so applied all the updates which Synaptic identified.

I noticed that the list included a kernel upgrade, but assumed that was not going to be a deal-breaker, so went ahead.

I was a bit surprised - alarmed - to get an error message saying that some updates could not be completed because of a lack of space and a broken pipe (whatever that is!).

I fear I don't have the expertise to understand the details. So I attach a copy of the detailed report:

Code: Select all

Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../base-files_10.3+deb10u12_amd64.deb ...
Unpacking base-files (10.3+deb10u12) over (10.3+deb10u11) ...
Setting up base-files (10.3+deb10u12) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../gzip_1.9-3+deb10u1_amd64.deb ...
Unpacking gzip (1.9-3+deb10u1) over (1.9-3) ...
Setting up gzip (1.9-3+deb10u1) ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../0-libc-dev-bin_2.28-10+deb10u1_amd64.deb ...
Unpacking libc-dev-bin (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../1-libc6-dev_2.28-10+deb10u1_amd64.deb ...
Unpacking libc6-dev:amd64 (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../2-libc6_2.28-10+deb10u1_amd64.deb ...
De-configuring libc6:i386 (2.28-10) ...
Unpacking libc6:amd64 (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../3-libc6_2.28-10+deb10u1_i386.deb ...
Unpacking libc6:i386 (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../4-linux-libc-dev_4.19.235-1_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.19.235-1) over (4.19.208-1) ...
Preparing to unpack .../5-libc-bin_2.28-10+deb10u1_amd64.deb ...
Unpacking libc-bin (2.28-10+deb10u1) over (2.28-10) ...
Setting up libc6:amd64 (2.28-10+deb10u1) ...
Setting up libc6:i386 (2.28-10+deb10u1) ...
Setting up libc-bin (2.28-10+deb10u1) ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../zlib1g-dev_1%3a1.2.11.dfsg-1+deb10u1_amd64.deb ...
Unpacking zlib1g-dev:amd64 (1:1.2.11.dfsg-1+deb10u1) over (1:1.2.11.dfsg-1) ...
Preparing to unpack .../zlib1g_1%3a1.2.11.dfsg-1+deb10u1_amd64.deb ...
Unpacking zlib1g:amd64 (1:1.2.11.dfsg-1+deb10u1) over (1:1.2.11.dfsg-1) ...
Setting up zlib1g:amd64 (1:1.2.11.dfsg-1+deb10u1) ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../rsyslog_8.1901.0-1+deb10u1_amd64.deb ...
Unpacking rsyslog (8.1901.0-1+deb10u1) over (8.1901.0-1) ...
Preparing to unpack .../liblzma5_5.2.4-1+deb10u1_amd64.deb ...
Unpacking liblzma5:amd64 (5.2.4-1+deb10u1) over (5.2.4-1) ...
Setting up liblzma5:amd64 (5.2.4-1+deb10u1) ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../libgmp10_2%3a6.1.2+dfsg-4+deb10u1_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.2+dfsg-4+deb10u1) over (2:6.1.2+dfsg-4) ...
Setting up libgmp10:amd64 (2:6.1.2+dfsg-4+deb10u1) ...
(Reading database ... 393618 files and directories currently installed.)
Preparing to unpack .../00-tzdata_2021a-0+deb10u4_all.deb ...
Unpacking tzdata (2021a-0+deb10u4) over (2021a-0+deb10u3) ...
Preparing to unpack .../01-vim-tiny_2%3a8.1.0875-5+deb10u2_amd64.deb ...
Unpacking vim-tiny (2:8.1.0875-5+deb10u2) over (2:8.1.0875-5) ...
Preparing to unpack .../02-xxd_2%3a8.1.0875-5+deb10u2_amd64.deb ...
Unpacking xxd (2:8.1.0875-5+deb10u2) over (2:8.1.0875-5) ...
Preparing to unpack .../03-vim-common_2%3a8.1.0875-5+deb10u2_all.deb ...
Unpacking vim-common (2:8.1.0875-5+deb10u2) over (2:8.1.0875-5) ...
Preparing to unpack .../04-libicu63_63.1-6+deb10u3_amd64.deb ...
Unpacking libicu63:amd64 (63.1-6+deb10u3) over (63.1-6+deb10u2) ...
Preparing to unpack .../05-libxml2_2.9.4+dfsg1-7+deb10u3_amd64.deb ...
Unpacking libxml2:amd64 (2.9.4+dfsg1-7+deb10u3) over (2.9.4+dfsg1-7+deb10u2) ...
Preparing to unpack .../06-bind9-host_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking bind9-host (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../07-dnsutils_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking dnsutils (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../08-libbind9-161_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libbind9-161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../09-libisccfg163_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libisccfg163:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../10-libisccc161_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libisccc161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../11-libssl1.1_1.1.1n-0+deb10u1_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1n-0+deb10u1) over (1.1.1d-0+deb10u7) ...
Preparing to unpack .../12-libirs161_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libirs161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../13-libdns1104_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libdns1104:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../14-libisc1100_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libisc1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../15-liblwres161_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking liblwres161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../16-libc-l10n_2.28-10+deb10u1_all.deb ...
Unpacking libc-l10n (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../17-locales_2.28-10+deb10u1_all.deb ...
Unpacking locales (2.28-10+deb10u1) over (2.28-10) ...
Preparing to unpack .../18-xz-utils_5.2.4-1+deb10u1_amd64.deb ...
Unpacking xz-utils (5.2.4-1+deb10u1) over (5.2.4-1) ...
Preparing to unpack .../19-libcupsimage2_2.2.10-6+deb10u5_amd64.deb ...
Unpacking libcupsimage2:amd64 (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../20-cups-ipp-utils_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-ipp-utils (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../21-cups-daemon_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-daemon (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../22-cups-core-drivers_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-core-drivers (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../23-cups-server-common_2.2.10-6+deb10u5_all.deb ...
Unpacking cups-server-common (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../24-cups-common_2.2.10-6+deb10u5_all.deb ...
Unpacking cups-common (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../25-cups-client_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-client (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../26-cups_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../27-cups-bsd_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-bsd (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../28-libcups2_2.2.10-6+deb10u5_amd64.deb ...
Unpacking libcups2:amd64 (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../29-cups-ppdc_2.2.10-6+deb10u5_amd64.deb ...
Unpacking cups-ppdc (2.2.10-6+deb10u5) over (2.2.10-6+deb10u4) ...
Preparing to unpack .../30-libavfilter7_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libavfilter7:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../31-libswscale5_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libswscale5:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../32-libavformat58_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libavformat58:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../33-libavcodec58_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libavcodec58:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../34-libswresample3_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libswresample3:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../35-libpostproc55_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libpostproc55:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../36-libavresample4_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libavresample4:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../37-libavutil56_7%3a4.1.9-0+deb10u1_amd64.deb ...
Unpacking libavutil56:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ...
Preparing to unpack .../38-libwavpack1_5.1.0-6+deb10u1_amd64.deb ...
Unpacking libwavpack1:amd64 (5.1.0-6+deb10u1) over (5.1.0-6) ...
Preparing to unpack .../39-firefox_100.0~mozillabinaries-1mx19+1_amd64.deb ...
Unpacking firefox (100.0~mozillabinaries-1mx19+1) over (97.0.1~mozillabinaries-1mx19+1) ...
Preparing to unpack .../40-libflac8_1.3.2-3+deb10u1_amd64.deb ...
Unpacking libflac8:amd64 (1.3.2-3+deb10u1) over (1.3.2-3) ...
Preparing to unpack .../41-flac_1.3.2-3+deb10u1_amd64.deb ...
Unpacking flac (1.3.2-3+deb10u1) over (1.3.2-3) ...
Preparing to unpack .../42-formatusb_22.04_amd64.deb ...
Unpacking formatusb (22.04) over (21.05.04) ...
Preparing to unpack .../43-gir1.2-webkit2-4.0_2.36.0-3~deb10u1_amd64.deb ...
Unpacking gir1.2-webkit2-4.0:amd64 (2.36.0-3~deb10u1) over (2.34.6-1~deb10u1) ...
Preparing to unpack .../44-gir1.2-javascriptcoregtk-4.0_2.36.0-3~deb10u1_amd64.deb ...
Unpacking gir1.2-javascriptcoregtk-4.0:amd64 (2.36.0-3~deb10u1) over (2.34.6-1~deb10u1) ...
Preparing to unpack .../45-libwebkit2gtk-4.0-37_2.36.0-3~deb10u1_amd64.deb ...
Unpacking libwebkit2gtk-4.0-37:amd64 (2.36.0-3~deb10u1) over (2.34.6-1~deb10u1) ...
Preparing to unpack .../46-libjavascriptcoregtk-4.0-18_2.36.0-3~deb10u1_amd64.deb ...
Unpacking libjavascriptcoregtk-4.0-18:amd64 (2.36.0-3~deb10u1) over (2.34.6-1~deb10u1) ...
Preparing to unpack .../47-intel-microcode_3.20220207.1~deb10u1_amd64.deb ...
Unpacking intel-microcode (3.20220207.1~deb10u1) over (3.20210608.2~deb10u1) ...
Preparing to unpack .../48-libisc-export1100_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libisc-export1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../49-libdns-export1104_1%3a9.11.5.P4+dfsg-5.1+deb10u7_amd64.deb ...
Unpacking libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u7) over (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Preparing to unpack .../50-libexpat1_2.2.6-2+deb10u4_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.6-2+deb10u4) over (2.2.6-2+deb10u2) ...
Preparing to unpack .../51-libfaad2_2.10.0-1~deb10u1_amd64.deb ...
Unpacking libfaad2:amd64 (2.10.0-1~deb10u1) over (2.8.8-3) ...
Preparing to unpack .../52-libjbig2dec0_0.16-1+deb10u1_amd64.deb ...
Unpacking libjbig2dec0:amd64 (0.16-1+deb10u1) over (0.16-1) ...
Preparing to unpack .../53-mariadb-common_1%3a10.3.34-0+deb10u1_all.deb ...
Unpacking mariadb-common (1:10.3.34-0+deb10u1) over (1:10.3.31-0+deb10u1) ...
Preparing to unpack .../54-libmariadb3_1%3a10.3.34-0+deb10u1_amd64.deb ...
Unpacking libmariadb3:amd64 (1:10.3.34-0+deb10u1) over (1:10.3.31-0+deb10u1) ...
Preparing to unpack .../55-libpcap0.8_1.8.1-6+deb10u1_amd64.deb ...
Unpacking libpcap0.8:amd64 (1.8.1-6+deb10u1) over (1.8.1-6) ...
Preparing to unpack .../56-libraptor2-0_2.0.14-1.1~deb10u2_amd64.deb ...
Unpacking libraptor2-0:amd64 (2.0.14-1.1~deb10u2) over (2.0.14-1.1~deb10u1) ...
Preparing to unpack .../57-libsasl2-modules-db_2.1.27+dfsg-1+deb10u2_amd64.deb ...
Unpacking libsasl2-modules-db:amd64 (2.1.27+dfsg-1+deb10u2) over (2.1.27+dfsg-1+deb10u1) ...
Preparing to unpack .../58-libsasl2-2_2.1.27+dfsg-1+deb10u2_amd64.deb ...
Unpacking libsasl2-2:amd64 (2.1.27+dfsg-1+deb10u2) over (2.1.27+dfsg-1+deb10u1) ...
Preparing to unpack .../59-libsdl1.2debian_1.2.15+dfsg2-6~deb10u1_amd64.deb ...
Unpacking libsdl1.2debian:amd64 (1.2.15+dfsg2-6~deb10u1) over (1.2.15+dfsg2-4) ...
Preparing to unpack .../60-libtiff5_4.1.0+git191117-2~deb10u4_amd64.deb ...
Unpacking libtiff5:amd64 (4.1.0+git191117-2~deb10u4) over (4.1.0+git191117-2~deb10u3) ...
Preparing to unpack .../61-libtiff-tools_4.1.0+git191117-2~deb10u4_amd64.deb ...
Unpacking libtiff-tools (4.1.0+git191117-2~deb10u4) over (4.1.0+git191117-2~deb10u3) ...
Preparing to unpack .../62-linux-compiler-gcc-8-x86_4.19.235-1_amd64.deb ...
Unpacking linux-compiler-gcc-8-x86 (4.19.235-1) over (4.19.208-1) ...
Selecting previously unselected package linux-headers-4.19.0-20-common.
Preparing to unpack .../63-linux-headers-4.19.0-20-common_4.19.235-1_all.deb ...
Unpacking linux-headers-4.19.0-20-common (4.19.235-1) ...
Preparing to unpack .../64-linux-kbuild-4.19_4.19.235-1_amd64.deb ...
Unpacking linux-kbuild-4.19 (4.19.235-1) over (4.19.208-1) ...
Selecting previously unselected package linux-headers-4.19.0-20-amd64.
Preparing to unpack .../65-linux-headers-4.19.0-20-amd64_4.19.235-1_amd64.deb ...
Unpacking linux-headers-4.19.0-20-amd64 (4.19.235-1) ...
Preparing to unpack .../66-linux-headers-amd64_4.19+105+deb10u15_amd64.deb ...
Unpacking linux-headers-amd64 (4.19+105+deb10u15) over (4.19+105+deb10u13) ...
Selecting previously unselected package linux-image-4.19.0-20-amd64.
Preparing to unpack .../67-linux-image-4.19.0-20-amd64_4.19.235-1_amd64.deb ...
Unpacking linux-image-4.19.0-20-amd64 (4.19.235-1) ...
Preparing to unpack .../68-linux-image-amd64_4.19+105+deb10u15_amd64.deb ...
Unpacking linux-image-amd64 (4.19+105+deb10u15) over (4.19+105+deb10u13) ...
Preparing to unpack .../69-mx-bootrepair_22.3.04_amd64.deb ...
Unpacking mx-bootrepair (22.3.04) over (21.3.03) ...
Preparing to unpack .../70-mx-cleanup_22.4.06_amd64.deb ...
Unpacking mx-cleanup (22.4.06) over (20.8) ...
Preparing to unpack .../71-mx-installer_22.4mx19_amd64.deb ...
Unpacking mx-installer (22.4mx19) over (21.10.08mx19) ...
Preparing to unpack .../72-mx-live-usb-maker_22.4_amd64.deb ...
Unpacking mx-live-usb-maker (22.4) over (22.1.01) ...
Preparing to unpack .../73-mx-packageinstaller_22.4.3_amd64.deb ...
Unpacking mx-packageinstaller (22.4.3) over (21.10) ...
Preparing to unpack .../74-mx-remastercc_22.4_amd64.deb ...
Unpacking mx-remastercc (22.4) over (19.9) ...
Preparing to unpack .../75-mx-repo-list_22.5_all.deb ...
Unpacking mx-repo-list (22.5) over (21.12.02) ...
Preparing to unpack .../76-mx-snapshot_22.4.01_amd64.deb ...
Unpacking mx-snapshot (22.4.01) over (22.2.05) ...
Preparing to unpack .../77-mx-welcome-data_22.02.02mx19_all.deb ...
Unpacking mx-welcome-data (22.02.02mx19) over (21.10.02mx19) ...
Preparing to unpack .../78-mx-welcome_22.02.02_amd64.deb ...
Unpacking mx-welcome (22.02.02) over (22.01.02) ...
Preparing to unpack .../79-openssl_1.1.1n-0+deb10u1_amd64.deb ...
Unpacking openssl (1.1.1n-0+deb10u1) over (1.1.1d-0+deb10u7) ...
Preparing to unpack .../80-wavpack_5.1.0-6+deb10u1_amd64.deb ...
Unpacking wavpack (5.1.0-6+deb10u1) over (5.1.0-6) ...
Preparing to unpack .../81-mxfb-docs_22.02.19_all.deb ...
Unpacking mxfb-docs (22.02.19) over (21.09.03) ...
Setting up linux-compiler-gcc-8-x86 (4.19.235-1) ...
Setting up libexpat1:amd64 (2.2.6-2+deb10u4) ...
Setting up libc-l10n (2.28-10+deb10u1) ...
Setting up cups-server-common (2.2.10-6+deb10u5) ...
Setting up mx-remastercc (22.4) ...
Setting up libssl1.1:amd64 (1.1.1n-0+deb10u1) ...
Setting up intel-microcode (3.20220207.1~deb10u1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Setting up mx-installer (22.4mx19) ...
Setting up cups-common (2.2.10-6+deb10u5) ...
Setting up rsyslog (8.1901.0-1+deb10u1) ...
Stopping enhanced syslogd: rsyslogd.
Starting enhanced syslogd: rsyslogd.
Setting up linux-libc-dev:amd64 (4.19.235-1) ...
Setting up mx-packageinstaller (22.4.3) ...
Setting up locales (2.28-10+deb10u1) ...
Generating locales (this might take a while)...
  ar_EG.UTF-8... done
  be_BY.UTF-8... done
  bg_BG.UTF-8... done
  ca_ES.UTF-8... done
  cs_CZ.UTF-8... done
  da_DK.UTF-8... done
  de_CH.UTF-8... done
  de_DE.UTF-8... done
  el_GR.UTF-8... done
  en_AU.UTF-8... done
  en_CA.UTF-8... done
  en_GB.UTF-8... done
  en_IE.UTF-8... done
  en_NZ.UTF-8... done
  en_US.ISO-8859-1... done
  en_US.UTF-8... done
  es_AR.UTF-8... done
  es_BO.UTF-8... done
  es_ES.UTF-8... done
  es_MX.UTF-8... done
  es_NI.UTF-8... done
  es_PA.UTF-8... done
  es_PE.UTF-8... done
  es_US.UTF-8... done
  es_VE.UTF-8... done
  et_EE.UTF-8... done
  eu_ES.UTF-8... done
  fa_IR.UTF-8... done
  fi_FI.UTF-8... done
  fr_BE.UTF-8... done
  fr_CA.UTF-8... done
  fr_CH.UTF-8... done
  fr_FR.UTF-8... done
  ga_IE.UTF-8... done
  he_IL.UTF-8... done
  hr_HR.UTF-8... done
  hu_HU.UTF-8... done
  is_IS.UTF-8... done
  it_IT.UTF-8... done
  ja_JP.UTF-8... done
  ko_KR.UTF-8... done
  lt_LT.UTF-8... done
  lv_LV.UTF-8... done
  mk_MK.UTF-8... done
  nb_NO.UTF-8... done
  nl_BE.UTF-8... done
  nl_NL.UTF-8... done
  nn_NO.UTF-8... done
  pl_PL.UTF-8... done
  pt_BR.UTF-8... done
  pt_PT.UTF-8... done
  ro_RO.UTF-8... done
  ru_RU.UTF-8... done
  sk_SK.UTF-8... done
  sl_SI.UTF-8... done
  sq_AL.UTF-8... done
  sr_RS.UTF-8... done
  sv_SE.UTF-8... done
  tr_TR.UTF-8... done
  uk_UA.UTF-8... done
  zh_CN.UTF-8... done
  zh_TW.UTF-8... done
Generation complete.
Setting up libicu63:amd64 (63.1-6+deb10u3) ...
Setting up xxd (2:8.1.0875-5+deb10u2) ...
Setting up libavutil56:amd64 (7:4.1.9-0+deb10u1) ...
Setting up formatusb (22.04) ...
Setting up mx-welcome-data (22.02.02mx19) ...
Setting up libflac8:amd64 (1.3.2-3+deb10u1) ...
Setting up libsasl2-modules-db:amd64 (2.1.27+dfsg-1+deb10u2) ...
Setting up tzdata (2021a-0+deb10u4) ...

Current default time zone: 'Europe/London'
Local time is now:      Wed May  4 13:05:41 BST 2022.
Universal Time is now:  Wed May  4 12:05:41 UTC 2022.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up mariadb-common (1:10.3.34-0+deb10u1) ...
Setting up mxfb-docs (22.02.19) ...
Setting up linux-image-4.19.0-20-amd64 (4.19.235-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.0-18-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.0-18-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-20-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-20-amd64
/etc/kernel/postinst.d/dkms:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-20-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=68e46572-8173-4105-9489-1aa0dc2c1dd7)
I: Set the RESUME variable to override this.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-20-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.19.0-20-amd64 (--configure):
 installed linux-image-4.19.0-20-amd64 package post-installation script subprocess returned error exit status 1
Setting up mx-welcome (22.02.02) ...
Setting up vim-common (2:8.1.0875-5+deb10u2) ...
Setting up flac (1.3.2-3+deb10u1) ...
Setting up mx-bootrepair (22.3.04) ...
Setting up libpcap0.8:amd64 (1.8.1-6+deb10u1) ...
Setting up libjbig2dec0:amd64 (0.16-1+deb10u1) ...
Setting up xz-utils (5.2.4-1+deb10u1) ...
Setting up mx-cleanup (22.4.06) ...
Setting up libfaad2:amd64 (2.10.0-1~deb10u1) ...
Setting up libsdl1.2debian:amd64 (1.2.15+dfsg2-6~deb10u1) ...
Setting up libpostproc55:amd64 (7:4.1.9-0+deb10u1) ...
Setting up libmariadb3:amd64 (1:10.3.34-0+deb10u1) ...
Setting up libsasl2-2:amd64 (2.1.27+dfsg-1+deb10u2) ...
Setting up libisc-export1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libcups2:amd64 (2.2.10-6+deb10u5) ...
Setting up libwavpack1:amd64 (5.1.0-6+deb10u1) ...
Setting up mx-snapshot (22.4.01) ...
Installing new version of config file /etc/mx-snapshot-exclude.list ...
Setting up libswscale5:amd64 (7:4.1.9-0+deb10u1) ...
Setting up libtiff5:amd64 (4.1.0+git191117-2~deb10u4) ...
Setting up mx-live-usb-maker (22.4) ...
Setting up libc-dev-bin (2.28-10+deb10u1) ...
Setting up openssl (1.1.1n-0+deb10u1) ...
Setting up libtiff-tools (4.1.0+git191117-2~deb10u4) ...
Setting up libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libxml2:amd64 (2.9.4+dfsg1-7+deb10u3) ...
Setting up linux-headers-4.19.0-20-common (4.19.235-1) ...
Setting up mx-repo-list (22.5) ...
Setting up cups-ipp-utils (2.2.10-6+deb10u5) ...
Setting up wavpack (5.1.0-6+deb10u1) ...
Setting up linux-kbuild-4.19 (4.19.235-1) ...
Setting up cups-ppdc (2.2.10-6+deb10u5) ...
Setting up libraptor2-0:amd64 (2.0.14-1.1~deb10u2) ...
Setting up libjavascriptcoregtk-4.0-18:amd64 (2.36.0-3~deb10u1) ...
Setting up gir1.2-javascriptcoregtk-4.0:amd64 (2.36.0-3~deb10u1) ...
Setting up libisc1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up vim-tiny (2:8.1.0875-5+deb10u2) ...
Setting up libswresample3:amd64 (7:4.1.9-0+deb10u1) ...
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-4.19.0-20-amd64; however:
  Package linux-image-4.19.0-20-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libavresample4:amd64 (7:4.1.9-0+deb10u1) ...
Setting up libcupsimage2:amd64 (2.2.10-6+deb10u5) ...
Setting up liblwres161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up cups-daemon (2.2.10-6+deb10u5) ...
Restarting Common Unix Printing System: cupsd.
Setting up libwebkit2gtk-4.0-37:amd64 (2.36.0-3~deb10u1) ...
Setting up libisccc161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libc6-dev:amd64 (2.28-10+deb10u1) ...
Setting up libavcodec58:amd64 (7:4.1.9-0+deb10u1) ...
Setting up linux-headers-4.19.0-20-amd64 (4.19.235-1) ...
Setting up libdns1104:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up cups-core-drivers (2.2.10-6+deb10u5) ...
Setting up gir1.2-webkit2-4.0:amd64 (2.36.0-3~deb10u1) ...
Setting up firefox (100.0~mozillabinaries-1mx19+1) ...
Setting up libavformat58:amd64 (7:4.1.9-0+deb10u1) ...
Setting up linux-headers-amd64 (4.19+105+deb10u15) ...
Setting up cups-client (2.2.10-6+deb10u5) ...
Setting up zlib1g-dev:amd64 (1:1.2.11.dfsg-1+deb10u1) ...
Setting up libavfilter7:amd64 (7:4.1.9-0+deb10u1) ...
Setting up libisccfg163:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up cups (2.2.10-6+deb10u5) ...
Updating PPD files for cups ...
Setting up cups-bsd (2.2.10-6+deb10u5) ...
Setting up libbind9-161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libirs161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up bind9-host (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up dnsutils (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Processing triggers for ntp (1:4.2.8p12+dfsg-4) ...
Stopping NTP server: ntpd.
Starting NTP server: ntpd.
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.28-10+deb10u1) ...
Processing triggers for ufw (0.36-1) ...
Processing triggers for systemd (1:241-7~deb10u8+mx19+1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-18-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=68e46572-8173-4105-9489-1aa0dc2c1dd7)
I: Set the RESUME variable to override this.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-18-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-4.19.0-20-amd64
 linux-image-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.19.0-20-amd64 (4.19.235-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-20-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=68e46572-8173-4105-9489-1aa0dc2c1dd7)
I: Set the RESUME variable to override this.

gzip: stdout: No space left on device
cpio: write error: Broken pipe
E: mkinitramfs failure cpio 2 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-20-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.19.0-20-amd64 (--configure):
 installed linux-image-4.19.0-20-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-4.19.0-20-amd64; however:
  Package linux-image-4.19.0-20-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-18-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=68e46572-8173-4105-9489-1aa0dc2c1dd7)
I: Set the RESUME variable to override this.

gzip: stdout: No space left on device
cpio: write error: Broken pipe
E: mkinitramfs failure cpio 2 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-18-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-4.19.0-20-amd64
 linux-image-amd64
 initramfs-tools

The laptop doesn't have any vital files or data on it so this isn't a crisis. I did not take a backup before the update. What ought I to do now either to get the update to complete, or to remain with the earlier setup and (older) kernel?

Posted: **Wed May 04, 2022 8:32 am**

"No space left on device"

Maybe that might have something to do with it?

Posted: **Wed May 04, 2022 9:09 am**

Eadwine Rose wrote: Wed May 04, 2022 8:32 am "No space left on device"

Maybe that might have something to do with it?

Yes, I saw that and I did wonder. But as far as I can tell from a quick look at disk manager, this ought not to be an issue. The laptop is a triple-boot setup (with Win 10 and mint on other partitions). I have a separate boot partition, sda5, of 487.9 MB of which 65.6 MB is free, then MX root (/) on sda7 of 19.6 GB of which 11.5 GB is free, and MX /home sda8 is 9.8 GB of which 9.6 GB is free.

So the only potential space issue would seem to be in the boot partition. Does the kernel version-upgrade re-do the boot/Grub, and if so might that be the problem in terms of space? I have already done previous upgrades, so have various older versions of the kernels (which show under advanced options in Grub). I see I am currently using 4.19.0-18, and the update is offering 4.19.0-20. I still have various earlier versions, back to 4.19.0-9. Would it help to remove one or more older versions of the kernel? If so how exactly do I do that? (Mint's software manager has an easy way of doing so, but I can't see how to remove old versions of the kernels in MXLinux).

Posted: **Wed May 04, 2022 9:32 am**

kernels are just packages, and the package names are "linux-image-$VERSION-" and they should show up in the package managers.

if removing via package manager doesn't work because an update is in progress, I suggest manually deleting any unused kernel initrd-images from the /boot partition manually and then continuing the update with

Code: Select all

sudo apt install -f

Posted: **Wed May 04, 2022 9:35 am**

Maybe the new version of "MX Cleanup" works (it looks upgraded successfully). Kernel removal tool, you'll see the button below..

Posted: **Wed May 04, 2022 9:44 am**

Huckleberry Finn wrote: Wed May 04, 2022 9:35 am Maybe the new version of "MX Cleanup" works (it looks upgraded successfully). Kernel removal tool, you'll see the button below..

It won't work when the APT is in borked state, I think the user needs to follow dolphin_oracle's advice, remove the some old kernels/initrd manually from /boot (make sure you don't delete the running kernel) and then complete the installation.
Run this after freeing space:

Code: Select all

dpkg --configure -a

And then remove the package that provided the kernel that was removed manually.

Posted: **Wed May 04, 2022 1:44 pm**

Apologies for being dim or ignorant.... but I'm already beginning to get confused, especially by this advice from @Adrian "...then remove the package that provided the kernel that was removed manually".

The key facts are that I have these kernels showing up as 'installed'

4.19.0-9
4.19.0-10
4.19.0-17
4.19.0-18

As I understand it, I'm running with 4.19.0-18. The latest update offered me (and tried to install) 4.19.0-20 .... but, I assume, failed to do so because of the broken pipe/lack of space.

Now using File Manager I can see that in /boot I have various packages. They are

initrd.img-4.19.0-9-amd64
initrd.img-4.19.0-10-amd64
initrd.img-4.19.0-10-amd64.old-dkms
initrd.img-4.19.0-17-amd64
initrd.img-4.19.0-17-amd64.old-dkms
initrd.img-4.19.0-18-amd64

There are also equivalent config, System.map, and vmlinuz files for each of these kernel versions and also for 4.19.0-20. So the question is - if I am to manually delete, which do I delete? Just the initrd. package for, say, versions 9 and 10? Or the config, System.map and vmlinuz files for them as well?

And having done that - do I run both the command suggested by @dolphin_oracle and the one suggested by @Adrian - and in which order? And then what exactly does @Adrian 's cryptic instruction require me to do?

Not exactly easy to troubleshoot when you're not entirely clear what you're doing!

Posted: **Wed May 04, 2022 1:50 pm**

IF you cannot just uninstall the images due to the space issue via the regular package manager, then I would remove the initrd* files for whichever kernels you aren't using, but at least two, and then

so something like

Code: Select all

rm /boot/initrd.img-4.19.0-9-amd64 /boot/initrd.img-4.19.0-10-amd64

should free up around better than 100 MB on the /boot partition (about 130 if i remember the sizes on MX19 correctly).

Code: Select all

sudo dpkg --configure -a

which should finish the update.

Posted: **Wed May 04, 2022 2:39 pm**

I don't know if this helps or is relevant, but as well as looking in /boot using the file manager, I have also checked in Synaptic - which also lists the various kernel packages. So I guess in theory I could mark them for deletion using Synaptic. And just out of curiosity I opened the MX Cleanup tool (which I had never looked at before). It does appear to give me the simple click-button option of removing one or more of the 'old' kernel versions.

On the grounds that the simplest method is the one I'm least likely to screw up, should I use that MX Cleanup route rather than manual deletion and terminal commands?

Posted: **Wed May 04, 2022 2:44 pm**

On the grounds that the simplest method is the one I'm least likely to screw up, should I use that MX Cleanup route rather than manual deletion and terminal commands?

Normally yes, before you start to have the problem. However once you have the issue you will not be able to use MX Cleanup or Synaptic to remove old kernels because the entire APT system is clogged because it was not able to install the latest upgrade. That's why you need to remove manually one or two .img files from /boot (make sure you don't remove the one from the current running kernel) and then run that command to fix dpkg (APT system).

The steps are really not that complicated to fix this:
1. Find .img file in /boot that you can get rid of (should not have the same version as your running kernel: uname -r should give you the running kernel name)
2. delete with "sudo rm filename"
3. run: "sudo dpkg --configure -a" to finish the installation that was interrupted.

Posted: **Wed May 04, 2022 6:05 pm**

Well, we seem to be only part-way there.

I followed those three steps, @Adrian, for both the initrd.img-4.19.0-9-amd64 and the initrd.img-4.19.0-10-amd64. Both have disappeared from the list showing in /boot, so they have been removed. The config, System.map and vmlinuz for both of them however remain.

I checked the usage and space in /boot, and sure enough, that had freed up about 120 MB.

Anyway, I then ran the "sudo dpkg --configure -a" command to finish the update - which as I understood it was to install 4.19.0-20 as well as other updates.

And initrd.img-4.19.0-20-amd64 is right there in /boot (as are the config, System.map and vmlinuz for this latest version of the kernel).

Okay, so I restarted, thinking the job was done. Checked which kernel was running. It's still 4.19.0-18.

Closed down, rebooted, looked through the advanced options in Grub. No sign of 4.19.0-20. The 'current' default is still 4.19.0-18. And - get this - the list of other options shows not only 4.19.0.17 (which I haven't touched) but still shows 4.19.0-9 and 4.19.0-10.

So I'm puzzled. If the update is now completed (and 4.19.0-20 is there in /boot) why isn't it now running when I reboot? And if i have indeed removed the initrd.img for 4.19.0-9 and 4.19.0-10, how come they are still listed as options in Grub?

Should I now delete (using the rm command) the config, System.map and vmlinuz that belong with those two older versions of the kernel, if they are now "leftovers"? Or could I now use the MX Cleanup tool to do so - or is something still borked?

And - separate question - when and how will 4.19.0-20 be brought into action?

Sorry that the questions are so basic. But I call it as I see it...

Posted: **Wed May 04, 2022 6:19 pm**

I would use the MX Cleanup to remove the kernels you don't need (it would clear the stuff from the 4.19.0-9-amd64 that you removed manually)

Run "sudo update-grub" than take a look on MX Boot Options to see if you can select the correct kernel.

Basically the procedure worked, there's an issue with selecting the kernel to boot from "sudo update-grub" should take care of that and you can select the desired kernel with MX Boot Options.

I'm working to make MX Cleanup free up space and remove the kernel so you don't have to drop to CLI... but it's not yet ready.

Posted: **Thu May 05, 2022 6:35 am**

Closer.... but no cigar yet!

I have now got rid of 4.19.0-9 and 4.19.0-10. I also checked that 4.19.0-20 is definitely there in /boot.

I ran "sudo update-grub" and rebooted.

MX Boot Options told me I was still running the 4.19.0-18 version of the kernel. But the dropdown list in Boot Options gave me the option to select 4.19.0-20. I did so. A popup appeared saying Grub was being updated. Fine.

So I then rebooted again. And...... it is still running 4.19.0-18! The Grub menu advanced options list on startup shows 4.19.0-18 and 4.19.0-17 as options. No sign of 4.19.0.20 there.

But 4.19.0-20 is listed in Boot Options... and indeed also in the list of kernels in MX Cleanup (which confirms that 4.19.0-18 is running and offers the option to delete kernels 4.19.0-17 and 4.19.0-20).

So why - despite now apparently updating Grub twice - is it still not booting into the latest kernel, 4.19.0-20?

I did notice in Boot Options a tick-box saying "Enable saving last boot choice". It is blank (unticked). When I opted to select 4.19.0-20 and Grub got updated (as noted above), I did not tick that box. Should I have done so? Would that have made 4.19.0-20 the default choice?

Or do I now need to remove 4.19.0-20 (using MX Cleanup, or manually?) since it doesn't seem to want to play nicely, and then try reinstalling it from Synaptic? For obvious reasons I'm trying to keep things simple and not do major surgery on the system!

Posted: **Thu May 05, 2022 6:36 am**

Does some other Linux provide your grub menu?

Posted: **Thu May 05, 2022 7:58 am**

Let me confuse you even more

( In your case it's "Debian 4.19" (to remove) instead of "Debian 5.10" )

Posted: **Thu May 05, 2022 8:16 am**

Ah, @dolphin_oracle you must be psychic, or extremely perceptive.

I did mention in an earlier post that this spare laptop is triple-boot. I set it up some time ago and I'm not sure I can now recall all the exact details of how I did so....

Basically I have Windows 10, Mint 19.3 and MXLinux 19.4 installed. But the booting arrangement is not the typical setup managed only by [one of the] Linux Grubs.

Windows 10 still boots as normal using its own MBR. I have EasyBCD installed in Windows, and that modifies the MBR to enable - or link onward to - the Linux distros. So at the Windows bootup splash screen I have the option to boot into Windows or into the Linux distros. If I choose the latter, it goes to Grub, where I then select either Mint or MX, or their advanced options (and of course the Grub also lists the Win10 as well).

I admit that I cannot now recall, or explain, exactly how Grub is configured or indeed whose Grub (Mint or MX) takes the lead, or has control. I seem to recall that - when I installed or added the two Linux distros, I put Grub into its own separate boot partition.

All I can say is that until this latest episode, I was able to update both Mint and MX entirely normally, each one separately. Each seems - until now - to have managed to take on board their respective kernel updates. I haven't been aware of what either of them have done "under the hood" to update either or both of their Grubs: it has just happened automatically and worked - until the situation arose as described in my OP.

In posting my original message, I did try to keep it simple by only setting out the details of the MXLinux installation/update situation. But the fact that the booting arrangement may well involve another grub, or some other linkages, is obviously a factor...

I hope this helps to explain the wider context. I imagine that you might find it easier to figure things out if I posted up some sort of "inxi" details. What exact command should I use to provide you with better, but technically precise, information about my setup?

Posted: **Thu May 05, 2022 8:24 am**

Just boot Mint and open a terminal

Code: Select all

sudo update-grub

Reboot (into MX).

Posted: **Thu May 05, 2022 12:10 pm**

Huckleberry Finn wrote: Thu May 05, 2022 8:24 am Just boot Mint and open a terminal
Code: Select all
sudo update-grub
Reboot (into MX).

What's the expression in the movies ...? "Well I'll be doggoned!" (or something similar).

Complicated question, detailed explanation - and simple answer. Thankyou, to @dolphin_oracle for his detective work and for prompting me to explain things a bit more fully, to @Adrian for taking the trouble to walk me through some of the tidying-up of old kernel versions, and to @Huckleberry Finn for nailing the final step to solve the problem.

Clearly the Grub which manages the booting of both Mint and MXLinux in my set-up is the Mint Grub. By updating it I have now got the list and the choice of kernels for MXLinux sorted. MX is now running 4.19.0-20 , with 4.19.0-18 and 4.19.0-17 still available as options if needed.

So all is now well. Memo to self: it's probably a good idea to prune down the collection of old kernel versions (in both Mint and MX) after the periodic updates, just to avoid bumping into the problem of a lack of space again. MX Cleanup looks like a very useful tool.

So with renewed thanks, I'm marking this thread solved.

Posted: **Thu May 05, 2022 12:17 pm**

br1anstorm wrote: Thu May 05, 2022 12:10 pm... and to @Huckleberry Finn for nailing the final step to solve the problem.

In fact, that, too was thanks to @dolphin_oracle : "good catch" :)

Posted: **Thu May 05, 2022 12:24 pm**

Huckleberry Finn wrote: Thu May 05, 2022 12:17 pm

br1anstorm wrote: Thu May 05, 2022 12:10 pm... and to @Huckleberry Finn for nailing the final step to solve the problem.
In fact, that, too was thanks to @dolphin_oracle : "good catch" :)

And this @dolphin_oracle guy is the main man who drives, develops, maintains and promotes MXLinux! Huge kudos for that - and I'm deeply appreciative that experts such as him and the others who chipped in took the time and trouble to help a simple and not very knowledgeable user like me. Gives me a very warm feeling about MX and its community.

Posted: **Thu May 05, 2022 12:32 pm**

br1anstorm wrote: Thu May 05, 2022 12:24 pm
Huckleberry Finn wrote: Thu May 05, 2022 12:17 pm

br1anstorm wrote: Thu May 05, 2022 12:10 pm... and to @Huckleberry Finn for nailing the final step to solve the problem.
In fact, that, too was thanks to @dolphin_oracle : "good catch" :)
And this @dolphin_oracle guy is the main man who drives, develops, maintains and promotes MXLinux! Huge kudos for that - and I'm deeply appreciative that experts such as him and the others who chipped in took the time and trouble to help a simple and not very knowledgeable user like me. Gives me a very warm feeling about MX and its community.

its a big team.

MX Linux Forum

"broken pipe" when updating MX 19.4

"broken pipe" when updating MX 19.4 [Solved]

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: "broken pipe" when updating MX 19.4

Re: [SOLVED] "broken pipe" when updating MX 19.4

Re: [SOLVED] "broken pipe" when updating MX 19.4

Re: [SOLVED] "broken pipe" when updating MX 19.4