problem with kernel removal tool in MX19KDE

[asqwerth]

After I updated my system today (hadn't done so for a month), I opened MX-Cleanup to use the kernel updater tool. I selected the oldest kernel to remove, and the usual terminal popped open to ask me to confirm the packages to be removed. I clicked on yes, it looked like the process started but then 1 second later, the terminal just closed. I tried the tool again, but this time, the terminal did not even pop up at all. Tried a few times to no avail.

Closed MX-Cleanup and reopened it. Again, the first time trying to use the removal tool made the terminal pop up but then disappear within a second of answering yes. Trying the removal tool again leads to no terminal popping up at all.

Code: Select all

System:    Kernel: 5.10.0-15mx-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-15mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-19.4_KDE_x64 patito feo August 16  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: MSI model: H97M-G43(MS-7924) v: 1.0 serial: <filter> 
           BIOS: American Megatrends v: 2.4 date: 07/22/2014 
CPU:       Info: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: 28 cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25599 
           Speed: 2804 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 2804 2: 2877 3: 2965 
           4: 2827 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: Micro-Star MSI driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412 
           class-ID: 0300 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: VGA-1 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.8x10.6") 
           diag: 547mm (21.5") 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
           vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:03.0 
           chip-ID: 8086:0c0c class-ID: 0403 
           Device-2: Intel 9 Series Family HD Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-15mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Micro-Star MSI driver: r8169 v: kernel port: e000 bus-ID: 02:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 5.57 TiB used: 769.96 GiB (13.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD30EZRX-00D8PB0 
           size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
           type: HDD rpm: 5400 serial: <filter> rev: 0A80 scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD30EZRX-00D8PB0 
           size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
           type: HDD rpm: 5400 serial: <filter> rev: 0A80 scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 vendor: A-Data model: SP900 size: 119.24 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> scheme: MBR 
Partition: ID-1: / raw-size: 29.3 GiB size: 28.67 GiB (97.86%) used: 12.54 GiB (43.8%) 
           fs: ext4 dev: /dev/sda4 maj-min: 8:4 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 14.9 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sdc2 maj-min: 8:34 
Sensors:   System Temperatures: cpu: 58.0 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2482 lib: 1383 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://it.mxrepo.com/mx/repo/ buster main non-free
           2: deb http://it.mxrepo.com/mx/repo/ buster ahs
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 223 Uptime: 1h 47m wakeups: 1 Memory: 15.51 GiB used: 2.64 GiB (17.0%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 8.3.0 
           alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 running-in: quick-system-in 
           inxi: 3.3.06 

[dolphin_oracle]

Make sure your updates are actually finished.

Code: Select all

sudo dpkg --configure -a

[Huckleberry Finn]

... Also have you checked whether that kernel and Cpio are still there in /boot/ ?

(or with MXPI ? )

And what if you start it via terminal?

Code: Select all

mx-cleanup-launcher

i.e.

Code: Select all

$ mx-cleanup-launcher 
Starting /usr/bin/mx-cleanup
mx-cleanup version: 22.10.01
logname
lslogins --noheadings -u -o user | grep -vw root
"huck"
Load settings
uname -r
ii  linux-image-4.9.0-326-antix.1-686-smp-pae 4.9.0-326-antix.1-686-smp-pae-1 i386         Linux kernel, version 4.9.0-326-antix.1-686-smp-pae
dpkg -l linux-image-[0-9]\*.[0-9]\* | grep ^ii |
    grep $(uname -r | cut -f1 -d'-') | cut -f3 -d' ' | grep -v --extended-regexp linux-image-$(uname -r)'(-unsigned)?$'
dpkg -l linux-image-[0-9]\*.[0-9]\* | grep ^ii |
    grep -v $(uname -r | cut -f1 -d'-') | cut -f3 -d' '

(The uname -r (and onwards) is when you click the button)

[asqwerth]

Thanks, dolphin and huck, I'll try your suggestions and report back, but it will only be in 2 days' time as it's late here (just got home) and tomorrow I'll be out the whole day.

[asqwerth]

Hi, @dolphin_oracle @Huckleberry Finn

Here is the output. Nothing left unconfigured from a previous update.

Running mx-cleanup-launcher shows the kernel I wanted to remove (5.10.0-12mx-amd64-unsigned) is still there. I can't interpret the output after I clicked on the button and selected to remove the same kernel again. Looks like some dependency is stopping the removal???

Suffice to say nothing much happened thereafter, no further terminal popped up to carry out the removal action.

Code: Select all

                                                         
tuaz@mx19KDE:~
$ sudo dpkg --configure -a

[sudo] password for tuaz: 
tuaz@mx19KDE:~
$ mx-cleanup-launcher
Starting /usr/bin/mx-cleanup
Icon theme "McMuse-dark" not found.
mx-cleanup version: 22.10.01
logname
lslogins --noheadings -u -o user | grep -vw root
"tuaz\nfamily"
Load settings
uname -r
ii  linux-image-5.10.0-12mx-amd64-unsigned 5.10.103-1~mx19+1 amd64        Linux 5.10 for 64-bit PCs
ii  linux-image-5.10.0-13mx-amd64-unsigned 5.10.106-1~mx19+1 amd64        Linux 5.10 for 64-bit PCs
ii  linux-image-5.10.0-14mx-amd64-unsigned 5.10.113-1~mx19+1 amd64        Linux 5.10 for 64-bit PCs
ii  linux-image-5.10.0-15mx-amd64-unsigned 5.10.120-1~mx19+1 amd64        Linux 5.10 for 64-bit PCs
ii  linux-image-amd64-mx                   5.10.120+1mx19    amd64        Metapackage for latest unsigned amd64 kernel backport for MX Linux
dpkg -l linux-image-[0-9]\*.[0-9]\* | grep ^ii |
    grep $(uname -r | cut -f1 -d'-') | cut -f3 -d' ' | grep -v --extended-regexp linux-image-$(uname -r)'(-unsigned)?$'
dpkg -l linux-image-[0-9]\*.[0-9]\* | grep ^ii |
    grep -v $(uname -r | cut -f1 -d'-') | cut -f3 -d' '
env LC_ALL=C.UTF-8 apt-cache depends linux-headers-5.10.0-12mx-amd64| grep 'Depends:' | grep -oE 'linux-headers-[0-9][^[:space:]]+' | sort -u

[Huckleberry Finn]

Just ..

"tuaz\nfamily"

when user name is just "tuaz"

Maybe there's a confusion about that ?

If you select another one (say ..-13 ) does it proceed? (though I think the same will happen)

[Huckleberry Finn]

If you like only, you can try in 2 min. simply:

Create a new user (MX User Manager) , say tuaz2

login with that, run MX Cleanup from menu (as usual) then let's see what happens there (if not: again via terminal)

[Huckleberry Finn]

... Another one:

Icon theme "McMuse-dark" not found.

You can change to any other (preferably the default) (icon) theme for 2 min. and see if anything changes..
_____________________________

These will also be a good feedback for development: username (unmatching) and/or theme may affect or not ...

[dolphin_oracle]

so you are only trying to remove 1 kernel?

let's check something, from the terminal:

Code: Select all

x-terminal-emulator -e bash -c 'apt purge "linux-image-5.10.0-12mx-amd64-unsigned linux-headers-5.10.0-12mx-amd64 linux-headers-5.10.0-12mx-common -s"'

and post output.

that should open a second terminal. are you still using the default konsole terminal?

[asqwerth]

so you are only trying to remove 1 kernel?

let's check something, from the terminal:

Code: Select all

x-terminal-emulator -e bash -c 'apt purge "linux-image-5.10.0-12mx-amd64-unsigned linux-headers-5.10.0-12mx-amd64 linux-headers-5.10.0-12mx-common -s"'

and post output.

that should open a second terminal. are you still using the default konsole terminal?

Yes, only removing 1 kernel. Running that terminal command gives me:

Code: Select all

x-terminal-emulator -e bash -c 'apt purge "linux-image-5.10.0-12mx-amd64-unsigned linux-headers-5.10.0-12mx-amd64 linux-headers-5.10.0-12mx-common -s"'
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/16/panel/"
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/16@2x/panel/"
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/22/panel/"
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/22@2x/panel/"
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/24/panel/"
Invalid Context= "Panel" line for icon theme:  "/usr/share/icons/Numix/24@2x/panel/"
Invalid Context= "Notifications" line for icon theme:  "/usr/share/icons/Numix/48/notifications/"
Invalid Context= "Notifications" line for icon theme:  "/usr/share/icons/Numix/48@2x/notifications/"

Weird because Numix and Numix Circle icon sets are installed on my system in usr/share/icons.

ksnip_20221113-134305.png

Note: as this is MX19 KDE, I'm using mx-updater with Muon, so that's the notification icon in the panel.

I switched back to default Papirus (dark) icons and tried the command again. This time, no error messages. HOWEVER, the second terminal only appeared for a split second and then disappeared again. Argh.

Yes, I use default Konsole. I always use the default terminal that comes with the release. Could it be because I also did install xterminal? I don't use the latter for anything except for logging in to NordVPN [it is necessary for the login process which takes place via internet browser]. On the other hand, xterminal is installed in my other MX19 and 21 XFCE and Plasma installations as well and I haven't faced this issue so far. Though I only have 1 MX19 KDE install.

@Huckleberry Finn I have 2 users on my installs - tuaz and family. Perhaps that is why the output previously listed both users?

Re: Icon theme "McMuse-dark" not found.
This icon set is in $HOME/.local/share/icons. For Plasma I tend to place user-only icon sets here instead of $HOME/.icons because Plasma does not really locate those in the latter location that well in my experience.

Seems strange that a kernel remover tool is checking for icons and panel icons.