Tried to find the line

local dst src key opts opencount major minor

in the new file as a hook or any hint for the patch that shuts down the LVM before the luks container, and failed.

I was able to apply the patch for ASCII, the patch and the description was sufficient for me. But for the new situation in Beowulf I do not understand enough about scripting and scripts to understand in detail what is happening there and how to possibly attack the problem.

To clarify: I got an LVM inside the luks container.

My impression: the new cryptdisks-functions just looks at encrypted volumes and does not take into account that a LVM may be included.

Thanks, Rolf

Remark: I use the classical setup with an un-encrypted boot partition, a system partition which is encrypted, and on top of that a LVM with at least two volumes for root and swap.

This is a feature request. Please add mate-tweak to at least mate-desktop-environment-extra. In Buster, this is done.

Helps to adjust the behaviour.

Is this worth to raise a bug request?

Thanks, Rolf

Tested your proposal on my faulty VBox Beowulf on efi. Works, removing  grub-efi-amd64-signed followed by a  grub-install does the job.

Maybe this post will help others.

Have a nice evening, thank you again, Rolf

BTW: my secondary PC now is on Beowulf. Some questions remain for other threads.

Thank you, that description contains the amount of detail I needed. The grub-efi-amd64-signed really was installed, I must have overlooked that fact in my previous searches.

Then I did grub-install --bootloader-id=debian followed by an update-grub.

Now I have got a non-working devuan efi entry, and a working debian efi entry. In any case, now I am logged in as root on my secondary PC.

I think I spend a grub-install --bootloader-id=devuan later.

Thank you for your help, Rolf

Thanks for the feedback, still no step further. I can't get along with the grub command line. I have looked at some stuff from Ubuntuusers, that was of limited use. I learned how to navigate in the uefi shell, but grub is sealed for me.

Booted my favorite life system Knoppix, and could not find any grub-efi-amd64-signed file wherever. grub-install in efi mode was noit possible since Knoppix does not boot in efi mode. Maybe I have to download an ASCII or Stretch life system.

Thanks, Rolf

Note: tried in a VBox: no encryption, efi with sysvinit and open-rc, both end in the grub command line. The efi installer is broken.

Sorry, there are some things different on xfce compared to Mate.

Good luck, Rolf

Same versions as in my VM where synaptic works.

Check in /usr/share/polkit-1/actions if you got a file named com.ubuntu.pkexec.synaptic.policy in there.

Rolf

My Beowulf netinstall VM with lightdm/Mate works, no issues related to the policykit. i.e. I can call synaptic, work with USB on Mate, shutdown/reboot from Mate and lightdm.

Thanks, Rolf

Update:

Version 3.2.7-6 is in the repository now, fixes the issue.

Thanks, ROlf

I have looked at the thread, and analysed what I have here.

The policykit stuff I have is version 0.105-25, seems to be complete. As authentification agent the package polkit-mate-authentication-agent-1 is installed.

# apt list policykit* --installed
Auflistung... Fertig
policykit-1/testing,now 0.105-25+devuan1 amd64  [Installiert,automatisch] 

# apt list libpolkit* --installed
Auflistung... Fertig
libpolkit-agent-1-0/testing,now 0.105-25+devuan1 amd64  [Installiert,automatisch]
libpolkit-backend-1-0/testing,now 0.105-25+devuan1 all  [Installiert,automatisch]
libpolkit-backend-elogind-1-0/testing,now 0.105-25+devuan1 amd64  [Installiert,automatisch]
libpolkit-gobject-1-0/testing,now 0.105-25+devuan1 all  [Installiert,automatisch]
libpolkit-gobject-elogind-1-0/testing,now 0.105-25+devuan1 amd64  [Installiert,automatisch]

Maybe I need to give the version 0.105-18 a try. Other ideas?

Thanks, Rolf

You might need some firmware. Try to install firmware-linux-free and firmware-linux-nonfree.

Regards, Rolf