The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » AppArmor not available as kernel LSM.. » 2018-08-06 23:21:12

Well this is the solution:

$ sudo mkdir -p /etc/default/grub.d
$ echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=1 security=apparmor"' \
  | sudo tee /etc/default/grub.d/apparmor.cfg
$ sudo update-grub
$ sudo reboot

#2 Other Issues » AppArmor not available as kernel LSM.. » 2018-08-06 22:11:43

Replies: 2

well apparmor failed in boot after kernel update to 4.9.0-7-amd64, this is output when trying to start:

$ sudo /etc/init.d/apparmor start
/etc/init.d/apparmor: 130: /etc/init.d/apparmor: systemd-detect-virt: not found
[....] Starting AppArmor profiles:[info] AppArmor not available as kernel LSM..

I'm looking for a solution, and any help.

#3 Re: Other Issues » Backported Liquorix kernels » 2018-07-17 20:54:59

Actually did some digging and MXLinux draws systemd from the debian repositories, I don't actually have access to it through either the MXLinux or AntiX repositories, so if you keep debian repositories off your system those "hooks" should be directed to devuan repositories...  I think, please correct me if I'm wrong.


#4 Re: Other Issues » Backported Liquorix kernels » 2018-07-17 20:16:58

Thanks for pointing that out.

That's fine, my instruction won't cause a problem if all he wants is kernels, and pins low priority.

Also MXLinux uses sysv init not systemd, and keeping sysdemd-sysv pinned at -1 should help, also if you keep MX repositories at 100 they rarely will pull anything in unless specified, dependencies will come from Devuan repositories as a priority, and you can pin lower if you want, but I've not had anything odd pulled even at 250.

I don't know, I'm not that stubborn I guess as long as openrc or sysv init keeps working I'll continue to be happy...  But I can understand wanting to avoiding systemd creep.

Is using elogind from devuan repositories a faux paux?

Oh also you could add this line to /etc/apt/preferences.d/avoid-systemd

Package: systemd-sysv
Pin: origin ""
Pin-Priority: -1

Edit: I went back to my initial post and edited the pin-priority for mx repo to 100.  That's a relatively safer place to start.

#5 Re: Other Issues » Backported Liquorix kernels » 2018-07-17 17:20:25

Yes it is possible, How I would do it is add the mx17 repository, then pin the kernel and headers you're interested in.

Try adding the one you want to /etc/apt/sources.list.d/:

deb stretch main non-free
deb stretch test


wget -qO - | sudo apt-key add - 

Then pin in /etc/apt/preferences.d/:

Package: *
Pin: origin ""
Pin-Priority: 100

I personally have the full mxrepos for all their tools, I pin the repository around 100, and usally have their testing commented out and use devuan backports...  If you want to use mx repos fully then you may also want to list antiX repos...  well good luck, I hope this helps.

So add mx17 repos and just install the packages you want

Edit: I edited pin priority to 100

#6 Re: Desktop and Multimedia » DEs on testing/unstable » 2018-07-08 14:58:22

Did you try a

apt dist-upgrade

after, it might help resolve the held dependencies.

Also you can try using aptitude, it can give better control with the software dependencies.

#7 Re: Desktop and Multimedia » On acsii, plasma and the power button. » 2018-07-08 05:04:44

Hi, I'd like to share my experience and solution, I had great difficulties with SDDM power buttons.  I tried all the solutions above, goofed around with sddm.conf files, grub files, etc... I thought I'd try lightdm and even had difficulty with lightdm not working with elogind but it did work with consolekit.

Anyway If you want to keep SDDM and elogind try

apt install openrc

I think the parallel loading of openrc solved any init order issues that may be causing the problem.

Board footer

Forum Software