autoremove fails [Solved]

[Huckleberry Finn]

I mean, sometimes (especially new) users add ppas to MX (thinking MX is based on Debian, and also *buntu ...) then that breaks this or that sooner or later:

viewtopic.php?f=104&t=44747

[dolphin_oracle]

can you post your /etc/lsb-release file please

[dolphin_oracle]

the error originally reported said a syntax error at line 355 of the grub.cfg.new file. I don't know if that error matches up with the grub.cfg.new file that was attached, but I would look at the boot parameters on your slackware install. they don't look correct to me, and I think os-prober part of the grub config is doing some sanity checks on the file.

[brad]

can you post your /etc/lsb-release file please

Code: Select all

cat /etc/lsb-release
PRETTY_NAME="MX 21 Bullseye"
DISTRIB_ID=MX
DISTRIB_RELEASE=21.2.1 
DISTRIB_CODENAME="bullseye"
DISTRIB_DESCRIPTION="MX 21 Bullseye"

[brad]

the error originally reported said a syntax error at line 355 of the grub.cfg.new file. I don't know if that error matches up with the grub.cfg.new file that was attached, but I would look at the boot parameters on your slackware install. they don't look correct to me, and I think os-prober part of the grub config is doing some sanity checks on the file.

A few days ago a check all the /etc/grub.d/* /etc/default/grub /boot/grub/grub.cfg and /boot/grub/grub.cfg.new and the syntax error line 355 was like now a } or even # (which made no sense to me).

Thanks for pointing that because for long time I remember lilo reported an error which I always ignored because booted OK. I will check out.

Code: Select all

Writing boot sector.
/boot/boot.0808 exists - no boot sector backup copy made.
One warning was issued.

I corrected lilo and I will update-grub again in MX.
No, the same:

Code: Select all

update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-19-amd64
Found initrd image: /boot/initrd.img-5.10.0-19-amd64
Found linux image: /boot/vmlinuz-5.10.0-17-amd64
Found initrd image: /boot/initrd.img-5.10.0-17-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found Slackware 15.0 x86_64 on /dev/sda1
Found Ubuntu 20.04.5 LTS (20.04) on /dev/sda2
Found Slackware 15.0 x86_64 on /dev/sda6
Found Alpine Linux v3.14 on /dev/sda7
Found Void Linux on /dev/sda8
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 355
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

i removed os-prober, mx-installer and update-grub as expected no errors:

Code: Select all

update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-19-amd64
Found initrd image: /boot/initrd.img-5.10.0-19-amd64
Found linux image: /boot/vmlinuz-5.10.0-17-amd64
Found initrd image: /boot/initrd.img-5.10.0-17-amd64
Found memtest86+ image: /boot/memtest86+.bin
done

slackware (sda6) and salix (sda1)

the MX (sda5) boot from ubuntu's grub (sda2)

Code: Select all

blkid
/dev/sda1: LABEL="Salix" UUID="20474804-df7b-415d-8dfb-5ed749e836fc" BLOCK_SIZE="512" TYPE="xfs" PARTLABEL="SALIX" PARTUUID="f7d1edf9-cb98-4a68-8599-dd7104569fc5"
/dev/sda2: LABEL="Ubuntu" UUID="3d0b9c53-4319-4452-9759-ac25caeb8923" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="UBUNTU" PARTUUID="09a61372-edf1-41d2-a3ab-1e0dd55e6c25"
/dev/sda3: LABEL="UbuntuHome" UUID="0c26e2a9-92eb-48d3-8d41-e73346243205" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="HOME" PARTUUID="faed34a4-bba9-47af-abd3-bdba9eeb49be"
/dev/sda4: UUID="4fc272fb-183a-4495-b2f3-529911e18667" TYPE="swap" PARTLABEL="SWAP" PARTUUID="3ad109e0-c26e-46aa-97da-2a8b0a12fbb9"
/dev/sda5: LABEL="MX19" UUID="3ceb66dd-0410-40aa-8f51-c4e4803a7a66" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="MX19" PARTUUID="d2fec215-2690-40a6-ac7e-628491ded3b0"
/dev/sda6: LABEL="Slack" UUID="3c01fc70-25d9-49d8-91b2-58564cc1b3a0" BLOCK_SIZE="4096" TYPE="ext4" PTTYPE="dos" PARTLABEL="SLACK" PARTUUID="689383cd-5fa3-4d61-906e-8a5ef08be760"
/dev/sda7: LABEL="Alpine" UUID="931d1e16-98ba-47e8-bee6-4afb9eb5386a" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="ALPINE" PARTUUID="0a1ad008-b924-423a-af31-f8a6ee47e004"
/dev/sda8: LABEL="Void" UUID="0cefd1ac-473f-4f96-8dc7-8155777582a4" BLOCK_SIZE="4096" TYPE="ext4" PTTYPE="dos" PARTLABEL="VOID" PARTUUID="c24443b8-7d39-4daa-9d16-8d1284334d47"
/dev/sda9: PARTLABEL="boot" PARTUUID="410058a3-dfbc-4662-a638-891d29fe4d76"

[dolphin_oracle]

the slackware boot entry has

Code: Select all

vga = normal append = "

at the end of the linux line, so maybe some issue with slackware's lilo boot parameters.

in my tests, I would guess the error would not be triggered if the extra " wasn't hanging out at the end. I'm pretty sure the syntax error is because grub is looking for a closing " but getting a closing } before one is found. the salix entries do not have the " at the end of the linux line.

[brad]

the slackware boot entry has

Code: Select all

vga = normal append = "

at the end of the linux line, so maybe some issue with slackware's lilo boot parameters.

in my tests, I would guess the error would not be triggered if the extra " wasn't hanging out at the end. I'm pretty sure the syntax error is because grub is looking for a closing " but getting a closing } before one is found. the salix entries do not have the " at the end of the linux line.

awesome! I see what you mean. So is coming from os-prober script when reads lilo.conf. Look what i found in lilo

Code: Select all

# Kernel command line options that apply to all installed images go
# here.  See 'kernel-parameters.txt' in the Linux kernel 'Documentation'
# directory. I.g. for start into 'init 5' write:  append="5"
append = ""

yay, it worked. I replaced quotation marks "" with apostrophes '' and no lilo complains.

Code: Select all

update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-19-amd64
Found initrd image: /boot/initrd.img-5.10.0-19-amd64
Found linux image: /boot/vmlinuz-5.10.0-17-amd64
Found initrd image: /boot/initrd.img-5.10.0-17-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found Slackware 15.0 x86_64 on /dev/sda1
Found Ubuntu 20.04.5 LTS (20.04) on /dev/sda2
Found Slackware 15.0 x86_64 on /dev/sda6
Found Alpine Linux v3.14 on /dev/sda7
Found Void Linux on /dev/sda8
done

I believe we are done here. Thanks a lot, great job!

[dolphin_oracle]

is that the salix one or the slackware one? and how do they compare to each other?

[brad]

is that the salix one or the slackware one? and how do they compare to each other?

slackware.

and how do they compare to each other? I do not understand what you mean.

[dolphin_oracle]

is that the salix one or the slackware one? and how do they compare to each other?

slackware. Salix boots from extlinux.

and how do they compare to each other? I do not understand what you mean.

I was just wondering how the "append = " line looks in the salix boot files, since its shows up in your Mx grub config, but wihtout the extra "