problem with kernel removal tool in MX19KDE

Help with the version of MX KDE officially released by the Development Team.
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.
Message
Author
User avatar
dolphin_oracle
Developer
Posts: 20032
Joined: Sun Dec 16, 2007 1:17 pm

Re: problem with kernel removal tool in MX19KDE

#11 Post by dolphin_oracle »

ok let's just check the removal command without trying to open another terminal window.

Code: Select all

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"
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Developer
Posts: 10383
Joined: Wed Apr 11, 2018 5:09 pm

Re: problem with kernel removal tool in MX19KDE

#12 Post by fehlix »

dolphin_oracle wrote: Sun Nov 13, 2022 8:21 am ok let's just check the removal command without trying to open another terminal window.

Code: Select all

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"
won't work. hint: remove the quotes
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Developer
Posts: 20032
Joined: Sun Dec 16, 2007 1:17 pm

Re: problem with kernel removal tool in MX19KDE

#13 Post by dolphin_oracle »

that's the command that mx-cleanup uses. mayhap therein lies the problem. well, without the -s anyway.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Developer
Posts: 10383
Joined: Wed Apr 11, 2018 5:09 pm

Re: problem with kernel removal tool in MX19KDE

#14 Post by fehlix »

dolphin_oracle wrote: Sun Nov 13, 2022 2:07 pm that's the command that mx-cleanup uses. mayhap therein lies the problem. well, without the -s anyway.
ru sure?
I do see this,

Code: Select all

    system("x-terminal-emulator -e bash -c 'apt purge " + headers_installed.join(QStringLiteral(" ")).toUtf8() + " " +
           list.join(QStringLiteral(" ")).toUtf8() +  " " + common.toUtf8() + "; apt-get install -f'");
which won't present double quotes to bash. Probably something else on MX19 or the konsole causing this, but I don't have currently a MX19-KDE to test ...
I would as first test reconfig x-terminal-emulator, to something else. IIRC, in apt-notifier, some extra hopps have been made to handle konsole calls.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Developer
Posts: 20032
Joined: Sun Dec 16, 2007 1:17 pm

Re: problem with kernel removal tool in MX19KDE

#15 Post by dolphin_oracle »

:bagoverhead: @fehlix duh, you're right.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
asqwerth
Developer
Posts: 7232
Joined: Sun May 27, 2007 5:37 am

Re: problem with kernel removal tool in MX19KDE

#16 Post by asqwerth »

sorry, dolphin and @fehlix for the long delay in responding.
Been busy with work, life, and also upgrading my Neon and Fedora installs to the next release as there were some issues.
dolphin_oracle wrote: Sun Nov 13, 2022 8:21 am ok let's just check the removal command without trying to open another terminal window.

Code: Select all

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"
Well, I did the above without the quotation marks and the packages were apparently purged. I updated grub after that. And the "12" kernel still shows.

Code: Select all

sudo 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
[sudo] password for tuaz: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gir1.2-vte-2.91 ipset libappindicator1 libdbusmenu-glib4 libdbusmenu-gtk4 libindicator7
  libipset11 libllvm10 libmono-corlib4.5-cil libmono-i18n-west4.0-cil libmono-i18n4.0-cil
  libmono-posix4.0-cil libmono-security4.0-cil libmono-system-configuration4.0-cil
  libmono-system-core4.0-cil libmono-system-data4.0-cil libmono-system-enterpriseservices4.0-cil
  libmono-system-numerics4.0-cil libmono-system-runtime-serialization-formatters-soap4.0-cil
  libmono-system-security4.0-cil libmono-system-transactions4.0-cil libmono-system-xml4.0-cil
  libmono-system4.0-cil libmono-webbrowser4.0-cil libokular5core8 libstartup-notification0
  libvpx6 libvte-2.91-0 libvte-2.91-common linux-headers-5.10.0-13mx-amd64
  linux-headers-5.10.0-13mx-common linux-image-5.10.0-13mx-amd64-unsigned mono-4.0-gac mono-gac
  mono-runtime mono-runtime-common mono-runtime-sgen stunnel4 vlc-plugin-access-extra xsltproc
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  linux-headers-5.10.0-12mx-amd64* linux-headers-5.10.0-12mx-common*
  linux-image-5.10.0-12mx-amd64-unsigned*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Purg linux-headers-5.10.0-12mx-amd64 [5.10.103-1~mx19+1]
Purg linux-headers-5.10.0-12mx-common [5.10.103-1~mx19+1]
Purg linux-image-5.10.0-12mx-amd64-unsigned [5.10.103-1~mx19+1]
tuaz@mx19KDE:~
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-15mx-amd64
Found initrd image: /boot/initrd.img-5.10.0-15mx-amd64
Found linux image: /boot/vmlinuz-5.10.0-14mx-amd64
Found initrd image: /boot/initrd.img-5.10.0-14mx-amd64
Found linux image: /boot/vmlinuz-5.10.0-13mx-amd64
Found initrd image: /boot/initrd.img-5.10.0-13mx-amd64
Found linux image: /boot/vmlinuz-5.10.0-12mx-amd64
Found initrd image: /boot/initrd.img-5.10.0-12mx-amd64
Found memtest86+ image: /boot/memtest86+.bin
done
tuaz@mx19KDE:~
$ 
Curioser and curioser. A check of the /boot folder shows that yep, the "12" kernel vmlinuz and initrd (and other related) files are still there.

But before I did the above, I tried the MX-cleanup tool again and managed to snap a screenshot just before the popup terminal disappeared. Here it is:
Screenshot_20221202_134539-crop.png
After the last line in the screenshot, I think a few more lines appeared then the terminal disappeared.

The line about not being able to acquire a lock, not sure how that is possible. I had just completed an apt full-upgrade via terminal, there was no lock stopping that. And that update was fully completed. Neither muon or repo manager or Synaptic were open.

Also note that this was not the first screenshot. I had tried many times before getting this. The other screenshots were activated too late and didn't get anything, or showed fewer lines in the terminal (too early). By then, any possible apt process [eg mx-updater checking for updates?] should have been completed.

I'm sure I could manually delete the spare kernels using Synaptic, as I have done in the past, but I have ample disk space and am more interested in solving this puzzle.

Just recently checked my MX19 XFCE install. No problems using cleanup to remove kernel.
You do not have the required permissions to view the files attached to this post.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Adrian
Developer
Posts: 8270
Joined: Wed Jul 12, 2006 1:42 am

Re: problem with kernel removal tool in MX19KDE

#17 Post by Adrian »

What's weird is that the linux-image-5.10.0-12mx-amd64-unsigned was passed directly to /bin/bash, not to apt purge, I think it might be because of the line break? I need to check the quote to see if we strip that.

Not sure about the lock, maybe an automatic process took it, we might need to check for the lock and take it before trying to run the command to be able to fail nicer for users.

Post Reply

Return to “MX KDE Official Release”