Posts by webman

webman · Installation

Hi!

Thanks, yes, any pipe would do ....

Forgot to set it "marked"

Regards,
Manfred

webman · Installation

Hello!

That night was really toooo long.
What lead me into the wrong directlion, was the "ip" command.
Its ignoring the TERM settings and requires to add commandline arguments.
This is really a mess - if they wont better output, they should use a real GUI for that.
Using "ip -c=never" does it, but its a mess.

Regards,
Manfred

webman · Installation

Hello!

I try to use xcalbur and setup two (K)VMs for it.
After struggle with setup in (K)VM (the setup crashes directly at the beginning and then continues),
I missed OpenSSH-server in the first disk ("server"). After a lot of disk-changes (the other ISOs) I try
to use it using ssh. Its not to understand, that no sshserver is in the basic system!

With ssh running; I got a big wonder: An "export TERM=xterm-mono" does not prevent apps to show
colored output, which is for some colors unreadable for me.
Should I go back to daedalus or is there a "workaround" ?

Thanks,
Manfred

webman · Installation

Hi!

Thank you.
But why? LXC is enough and the problems depend on devuan startup problems (not solved)
and would not be different using incus. No containers (and additionally, no (k)vms) are coming
up at boot and the cgroups dont work in containers.
Although is see lcxfs running, the problem goes away, if I restart it (which, naturally, dont help
for the boottime).
Never have had such a problem the years before (using only debian).

Regards,
Manfred

webman · Installation

Thanks!

But this does not help, because in a pure container, there is NO pgp.
I have had that problem earlier and it looks, the bug with lxc-templates has never been solved, a continuing PITA
(and there is really a lot more with this - but I dont try to mix everything).
There has been an older post of mine in galaxy:

https://dev1galaxy.org/viewtopic.php?id=6683

where 'fsmithre' posted this link to the key:

https://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2023.05.28_all.deb

Now I used this on the lxc-host and downloaded it using curl and then moved it into the container,
where I installed it using:

dpkg -i /ops/install/local/misc/devuan-keyring_2023.05.28_all.deb

apt update

succeeds now.
The devuan pages about the keys ars a mysterious for me and are not of any help.
But thanks for yours

Regards,
Manfred

And this forum adds to the nightmare, you have to study about to post a link the right way!

The following errors need to be corrected before the message can be posted:

    [url] was opened within itself, this is not allowed

(I rewotre the url to use code instead ....
No wonder, Linux has sooo many users ....
After 40 years of IT, Linux became my biggest annoyance.

webman · Installation

Hello !

I installed a lxc-container, but I cannot install software in it.
I am doing it on a debian host (debian 11, kernel 6.1).
Because I need basic software (like nano), after setting up the container, I usually install same packages (like nano) using
chroot and start with apt update:

chroot /var/lib/lxc/devu5t2/rootfs apt update

But this failes with this message:

Get:1 http://deb.devuan.org/merged daedalus InRelease [43.0 kB]
Get:2 http://deb.devuan.org/merged daedalus-updates InRelease [32.7 kB]
Err:1 http://deb.devuan.org/merged daedalus InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
Err:2 http://deb.devuan.org/merged daedalus-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.devuan.org/merged daedalus InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
W: GPG error: http://deb.devuan.org/merged daedalus-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
E: The repository 'http://deb.devuan.org/merged daedalus-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

How can I proceed?
This is - sad to say - not really new to me and seems to show a peristent bug.
Edit:
The keyring is installed:

$ acp devuan-keyring
devuan-keyring:
  Installed: 2023.05.28
  Candidate: 2023.05.28

BTW, this shows (over and over again), that a secure OS requires direct internet access:
GPG has to proxy configuration, an "open pain".

Some help would be great!

Thanks,
Manfred

webman · Hardware & System Configuration

Hello!

I am just buff when I see:

$ apt install -V --assume-no tomcat10
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 tomcat10 : Depends: systemd (>= 238) but it is not installable or
                     systemd-tmpfiles
            Recommends: libtcnative-1 (>= 1.2.18) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Not to mention, that I've run apt update directly before.

Anone an idea?

Thanks,
Manfred

webman · Hardware & System Configuration

Hi!

Thanks!
I runned "dpkg-reconfigure lightdm". No questions, no problems, no changes, but an interesting side-effect:
The root-user - via ssh - has the wong keyboard, until reboot.

I've already done bevore, what you recommended ("update-rc.d lightdm defaults").
Earlier and now, it gives me:

update-rc.d lightdm defaults
insserv: warning: current start runlevel(s) (empty) of script `lightdm' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `lightdm' overrides LSB defaults (0 1 6).

I can run startx for user and root, but in both cases, there is no lightdm and no fast userswitching.
If I start lightdm, it works. The use cannot start lightdm, I gave him sudo, then it works.

There is something bad in startup/order. There is no xorg nor lightdm logfile - I deleted them completely
immidiately before reboot.
The bootlog has this interesting part (could post full, but nothing about X/GUI/Lightdm in it), ercerpt:

Starting Setting kernel variables: sysctl.
Starting: AppArmorLoading AppArmor profiles...Skipping profile in /etc/apparmor.d/disable: usr.sbin.squid
done.
.
Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts ... (warning).
invoke-rc.d: could not determine current runlevel
invoke-rc.d: could not determine current runlevel
invoke-rc.d: could not determine current runlevel
done.
Cleaning up temporary files....
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix.
Setting sensors limits...No sensors found!

(I dont worry about the lmsensors message, its a (K)VM).

Regards,
Manfred

webman · Hardware & System Configuration

Hello!

I am asking why the gui does not start automatically.
I am using daedalus with sysv-init and lightdm.
As root user I can use "startx &" but I do not see a displaymanager running (at least not lightdm):

$ update-alternatives --get-selections | igrep --color "(light)|(manag)|(display)"
desktop-lightdm-background     auto     /usr/share/images/desktop-base/greeter-sapphire-narrow-large.png
desktop-lightdm-background.xml auto     /usr/share/images/desktop-base/lightdm.xml
lightdm-greeter                auto     /usr/share/xgreeters/lightdm-gtk-greeter.desktop
lightdm-gtk-greeter.conf       manual   /etc/lightdm/lightdm-gtk-greeter.conf-devuan-sapphire
x-session-manager              auto     /usr/bin/startxfce4
x-window-manager               auto     /usr/bin/xfwm4

I have installed lightdm:

apt-cache policy lightdm
lightdm:
  Installed: 1.26.0-8+devuan1
  Candidate: 1.26.0-8+devuan1
  Version table:
 *** 1.26.0-8+devuan1 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
        100 /var/lib/dpkg/status

But:

$ service lightdm status
lightdm is not running ... failed!

and in services:

$ service --status-all | igrep --color "|(disp)|(light)|(sess)|(xorg)|(window)"
 [ ? ]  alsa-utils
.....
 [ - ]  lightdm
.....

I followed the instructions contained in "/etc/init.d/lightdm" and changed it, without success:

# To start lightdm even if it is not the default display manager, change
# HEED_DEFAULT_DISPLAY_MANAGER to "false."
HEED_DEFAULT_DISPLAY_MANAGER="false"

Something should invoke startx at boot, or not?
On my debian desktop (debian 11) lightdm is running.
On both boxes, xfwm4 is the window manager.
Could someone please shed some light onto this?

Using:

Linux host1 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
Devuan GNU/Linux 5 (daedalus)
SysV init version: 3.06

This is a KVM box running devuan with zfs on root
using Virtio display, like lshw shows:

/0/100/2 /dev/fb0 display Virtio 1.0 GPU

(edited) If I use "startx/startxfce4" from user or root, fast userswitching is not available,
but works, if lightdm has been started manually.

Thanks so far,
Manfred

webman · Hardware & System Configuration

Hi Ralph!

Not completely true - because host, and therefore the container, is using kernel 5.10.
The mentioned new test-container (replicated by zfs), has been directly created on
devuan host using kernel 6.5 and does not have that problem running on the debian
host with kernel 5.10.
And indeed, it is strange - there will be no users, but services running as non-root.
I keep it in mind, when my new squid will come (which uses ping and so far I remember
right, form the non-root running process).

Regards,
Manfred

webman · Hardware & System Configuration

Hi All !

Found someone, who knows the bug.
Part of the message appears, if ipv6 has been disabled (everywhere in my infra), and I know this.
Came to the idea, to supply the "-4" switch (not neccessary) - and this show a complete different message:

$ pc2 -4 192.168.26.88
ping: socktype: SOCK_RAW
ping: socket: Operation not permitted                            <===
ping: => missing cap_net_raw+p capability or setuid?  <===

This was the same as in an older forum message with the same symptom, but this was hardware,
not a container. I compared working and non-working container, with no ideas.
But the leads to another websearch, which reveals the bug in a googl group:

I've installed mantic from the images repo multiple times and created multiple users, I've set lxc.apparmor.profile = unconfined, but nothing that I do will allow ordinary users to use "ping".
.....
I've tracked this down. It is a setting in sysctl. For whatever reason it is set like this:
net.ipv4.ping_group_range = 1 0
Changing to what most distros have:
net.ipv4.ping_group_range = 0 2147483647 <===
and ping is available again.
NB. This was from -d ubuntu -r mantic from the default images repository.

After I set this value into sysctl.conf and applied, it works!
Have never seen or used it and like the poster said:

from the default images repository

So this came from install sources.
I just duplicated another working container using zfs send/recv (from devu5 container on devu5 hardware) to
debian (where the devuan container live). The only change I had to do, was to replace:

lxc.include = /usr/share/lxc/config/devuan.common.conf
to:
lxc.include = /usr/share/lxc/config/debian.common.conf

So its not the "copying" of the container.

But thanks for all help!
Regards,
Manfred

webman · Hardware & System Configuration

Thanks for the replies!

@ralf, the interfaces are defined in the containers config file like this:

lxc.net.0.type = veth
lxc.net.0.name = eth0
lxc.net.0.veth.pair = ct-eth0
lxc.net.0.link = hovmbr
lxc.net.0.flags = up

#lanbr - optional, but now under test

lxc.net.1.type = veth
lxc.net.1.name = eth1
lxc.net.1.veth.pair = ct-eth1
lxc.net.1.link = lanbr
lxc.net.1.flags = up

Both end up in a bridge of the host (the first terminates at the host).
This usually works always and I rarely need others (but used macvtap, hardware).
All containers using this schema (debian + devuan), the debian'eses are working.
Using 'ip link' they appear like an ethernet interface.
Exact the same works on a devuan5 container on a devuan hardware.
For root, it works. For other usual users not (added another one for testing).
The users are only in their own and in the users group.
All firewall restriction have been removed on container AND host.
No ping is going out, ether which interface (destionation addr will be used).
A tcpdump does not show any outgoing packets (not even arp).
And the shown destination address has been random (though existing, running node),
it effects all - the routes are correct too (root has no different routing and it works).
---
@trinidad, that address is not my gateway, have never been it and something
linke wlan is NOT present.

Regards,
Manfred

webman · Hardware & System Configuration

Yes, ok.
But containers should be - at a degree - run on different kernels.

The container has been created by zfs send/recv, which worked in my experience.
BTW, the other containers, using debian 10/11/12 use exactly this same kernel.
Why should ping work with them?
Why can I even install a devuan-lxc on the same box?

Thanks,
Manfred

webman · Hardware & System Configuration

Hello!

I am seeing this in '/var/log/boot':

$ cat $logs/boot
(Nothing has been logged yet. If you're still seeing this message your current init system might not write bootup messages to the system console at all.)

Listing services show, that the service is enabled, but not running:

$ /etc/init.d/bootlogd status
bootlogd is not running ... failed!

The latter is an indicator of "something wrong" - I get the same message on my hardware,
where bootlogd works - where, at the moment after it has been run, it stops and causes
this message. So, this type of "status" is just not worth a penny.
This behavior is the same for all my containers.
No good work or containers without boot-logging!

A hint could be, how an equivalent to kernel commandline argument "debug" can be set.

Some help would be good!
Thanks,
Manfred

Environment:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 5 (daedalus)
Release:	5
Codename:	daedalus
---
Linux devu5test 5.10.0-0.bpo.9-amd64 #1 SMP Debian 5.10.70-1~bpo10+1 (2021-10-10) x86_64 GNU/Linux
---
bootlogd:
  Installed: 3.06-4devuan3

webman · Hardware & System Configuration

Hello!

Probably someone could shed some light onto this:

ping -c2 192.168.26.252
ping: socktype: SOCK_DGRAM
ping: socket: Address family not supported by protocol

System:

~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 5 (daedalus)
Release:	5
Codename:	daedalus
Linux devu5test 5.10.0-0.bpo.9-amd64 #1 SMP Debian 5.10.70-1~bpo10+1 (2021-10-10) x86_64 GNU/Linux

This not an exception - I am "on the road" to replace my debian infra with devuan and starting
with containers. All behave the same.
Wether on debian 10/11/12 lxc-containers have that problem.
There are no firewall/iptables restrictions in use making this tests.
I read in another thread (from 2024 in galaxy) that this even happend on hardware,
which - at least - my first and only hardware installtion does not have.
I generally install iputils-ping. it has nothing to do with interfaces and routes, I use
always the same structures.

Thanks,,
Manfred

webman · Documentation

Thanks a lot !

Regards,
Manfred

webman · Installation

Hi!

Alter I installed xfce4 (apt install xfce4), I tried to start ist using
>startxfce4
got the message 'xinit' not found.
That is strange, because -- on debian's -- I never used another way.
Any hints would be great.

It doesn't change, after I discovered, that xfce4 does not come with
lightdm, I installed that. xfce4 starts, when I invoke lightdm.

So: How to start it?
- using startxfce4 --or--
- lightdm

Thanks,
Manfred

webman · Documentation

Hello!

I am wondering on a new installation, that I found UDEV in addition to EUDEV on daedalus today.
Can someone shed probably some light onto this?

apt list --installed | igrep "(e|u)dev"

eudev/stable,now 3.2.12-4+deb12u1 amd64 [installed]
libeudev1/stable,now 3.2.12-4+deb12u1 amd64 [installed]
libgudev-1.0-0/stable,now 237-2 amd64 [installed,automatic]
udev/stable,now 1:3.2.9+devuan4 amd64 [installed]

I probably misunderstood someone sometime ;-)
so that I always remove UDEV.

Thanks,
Manfred

webman · Installation

Hi All!

Thanks for the answers.
I have had many changes, at least after removing mate, then re-installed xfce
(was no able to switch between desktops) and finally lightdm, due to fast user-switching.
For me, the mentioned variant using "defaults" was not working, but

update-rc.d lightdm disable

The question came up, because I do not understand the starup sequence for the desktop.

Thanks and solved,
Manfred

webman · Installation

Hello!

I do no longer want Xorg to start automatically (I installed xfce4).
Which service do I have to change?

Thanks,
Manfred

webman · Installation

Hi!
I am reading invoke-rc.d: could not determine current runlevel already on my last install
and faceing it at my current install again. So I have two setups with this error and I do not
know, where to look for it.
I am not a specialist, but one mentioned (together with other hints):

The service’s startup script is not working properly.

https://hatchjs.com/invoke-rc-d-could-n … -runlevel/
The message is in bootlog and appears between:

Starting Setting kernel variables: sysctl.
Starting: AppArmorLoading AppArmor profiles...done.
.
Configuring network interfaces...invoke-rc.d: could not determine current runlevel
invoke-rc.d: could not determine current runlevel
done.
Cleaning up temporary files....

And a mysterious DOT in a single line - WHO logs????
The network is ok.

The first computer does not start my LXC (container) which is set to autostart.
At this box, I tracked the occurence better (and I am just in an eraly state after
the networked setup) and it appears, after I installed some firmware packages
(amd64-microcode firmware-amd-graphics firmware-linux firmware-linux-free firmware-linux-nonfree firmware-realtek)
But the error persists if I remove (including purge) the packages and reboot.

For the first box, the problem may cause this:

$ ls /var/lib/lxcfs
ls: cannot access '/var/lib/lxcfs/sys': Input/output error
ls: cannot access '/var/lib/lxcfs/cgroup': Input/output error
total 0
dr-xr-xr-x 2 root root 0 2024-07-19 09:23:27 proc/
?????????? ? ?    ?    ?                   ? cgroup
?????????? ? ?    ?    ?                   ? sys

I am using fresh network install of devuan daedalus with kernel 6.1.0-23-amd64
Can someone help?
Thanks,
Manfred

webman · Hardware & System Configuration

Hi!

Just stumpled over this ...
Yes, I told them!

Regards,
Manfred

webman · Hardware & System Configuration

Hi!

Thanks for your investigation.
Not sure, if bridge-utils are really need, but I use them because its an easier way then "ip-link".
I usually use 'ifquery' ether with '--list' or '--state' but it does not show my second bridge, even
though 'ip link' shows it.
I know the problem with the member ports and on my current workstation the solution was to
give it a dummy address ("0.0.0.0"). The bridges are for containers and LXC, so there is no
definitiv port at computer start - which was never a problem to me.
But there is "/etc/network/if-pre-up.d/bridge -> /lib/bridge-utils/ifupdown.sh*"
which should solve the problem (that ip link is not persistent) and read "interfaces".
I have two comparable computers (hardware and VM), both Devuan5. If I look into /var/log/boot:

Starting: AppArmorLoading AppArmor profiles...done.
Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts ... (warning).
invoke-rc.d: could not determine current runlevel
if-up.d/mountnfs[eth1]: waiting for interface lanbr before doing NFS mounts ... (warning).
invoke-rc.d: could not determine current runlevel

Note: waiting for interface lanbr ....
I am even not capable to write everthing, I saw. But a internet search for

"2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP>"

Exactly this is part of my experience, were the bridge and even sometime
a hardware inferace shows this strange status!
This earch gives tons of similar messages, a hint of apparmor bug, of Kernel 6.1 bug and more.
You remove a VF from a dual-nic and suddenly, the other(!) port does not get carrier! I changed the NIC with the exact same from another computer (shown in the log-excerpt above) with not changes and the other box does not have that problem.
The whole story started with unexpected behavior of a kvm-guest, which had no traffic. But then I made the same, step-by-step on this host itself (create bridge, create macvlan) and everythings works - repeated this using LXC, works.
I made a port mirror on the hardware-switch - no packages came out, if the VM runs ..... but you see the packets on the host.
Something drops them. Due to the probability, this could be some of the "same subnet" things, I used a complete different, 10.10.10. ... (have enough free port on other computers). No change.
Now I removed systemtap, xtables-common, libvirt*, qemu*, xrdp, x2go, xfce4. Upgraded to kernel 6.5 - no changes.
There is no wait-message for the bridge and the assigned interface does not become member (can be done manually, after login). Even "/etc/network/interfaces.d/" is not read (was successful with: "/etc/network/if-pre-up.d/lanbr"
(my script with name of the bridge - but the membership problem remains). So the bridge can be created, but get no member ports.
Time to reinstall and hope.
I remember, what was the first fault on this box:
On shutdown, after the first boot (zfs on root), installed the usual way using chroot (like one of the other
boxes from the logs above, were the same things works), I got:
~ "cannot unmount /var/log" .....

Thanks anyway and
best regards,
Manfred

webman · Hardware & System Configuration

Thanks!

Was not the whole truth so, but probably the most important pointer!
Had to remove everything named apparmor so,
the boot was error-free and new install too!

Regards,
Manfred

webman · Hardware & System Configuration

Hello!

After I had some problems with KMV - in this context I saw apparmor errors
about KVM - I thought to remove apparmor temporarely. The docs does not
show me, how to disable (tried: /etc/init.d/apparmor stop), so I uninstalled it.
But the errors (while starting a VM) continue.
So I re-installed apparmor and another pain begins, which my bootlog shows (datetime column removed):

 Starting: AppArmorLoading AppArmor profiles...AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.man at line 53: Could not open 'local/usr.bin.man'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper at line 75: Could not open 'local/usr.lib.libvirt.virt-aa-helper'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.libvirtd at line 144: Could not open 'local/usr.sbin.libvirtd'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/sbin.dhclient at line 74: Could not open 'local/sbin.dhclient'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.ntpd at line 86: Could not open 'local/usr.sbin.ntpd'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.tcpdump at line 68: Could not open 'local/usr.bin.tcpdump'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lsb_release: File exists
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lightdm-guest-session: File exists
 AppArmor parser error for /etc/apparmor.d/sbin.dhclient in profile /etc/apparmor.d/sbin.dhclient at line 74: Could not open 'local/sbin.dhclient'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/nvidia_modprobe: File exists
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/usr.bin.lxc-start: File exists
 AppArmor parser error for /etc/apparmor.d/usr.bin.man in profile /etc/apparmor.d/usr.bin.man at line 53: Could not open 'local/usr.bin.man'
 AppArmor parser error for /etc/apparmor.d/usr.bin.tcpdump in profile /etc/apparmor.d/usr.bin.tcpdump at line 68: Could not open 'local/usr.bin.tcpdump'
 AppArmor parser error for /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper in profile /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper at line 75: Could not open 'local/usr.lib.libvirt.virt-aa-helper'
 AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in profile /etc/apparmor.d/usr.sbin.libvirtd at line 144: Could not open 'local/usr.sbin.libvirtd'
 AppArmor parser error for /etc/apparmor.d/usr.sbin.ntpd in profile /etc/apparmor.d/usr.sbin.ntpd at line 86: Could not open 'local/usr.sbin.ntpd'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lxc-containers: File exists
 /sbin/apparmor_parser: Unable to add "/usr/bin/lxc-start".  Profile already exists
 /sbin/apparmor_parser: Unable to add "lsb_release".  Profile already exists
 /sbin/apparmor_parser: Unable to add "kmod".  Profile already exists
 /sbin/apparmor_parser: Unable to add "nvidia_modprobe".  Profile already exists
 /sbin/apparmor_parser: Unable to add "chromium".  Profile already exists
 /sbin/apparmor_parser: Unable to add "/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session".  Profile already exists
 /sbin/apparmor_parser: Unable to add "lxc-container-default".  Profile already exists
 At least one profile failed to load ... failed!
 failed.

I do not know, why this hapens and how to repair it!

Thanks,
Manfred

The officially official Devuan Forum!

#1 Re: Installation » [SOLVED] Get rid of colored output in excalibur » 2026-10-11 19:08:57

#2 Re: Installation » [SOLVED] Get rid of colored output in excalibur » 2026-10-11 15:05:38

#3 Installation » [SOLVED] Get rid of colored output in excalibur » 2026-10-11 13:59:19

#4 Re: Installation » cannot install devuan container -- the public key is not available » 2026-06-13 21:28:10

#5 Re: Installation » cannot install devuan container -- the public key is not available » 2026-06-02 21:52:36

#6 Installation » cannot install devuan container -- the public key is not available » 2026-06-02 14:56:08

#7 Hardware & System Configuration » Cannot install Tomcat10 - depends on systemd » 2026-01-11 23:03:23

#8 Re: Hardware & System Configuration » GUI does not start automatically » 2025-10-17 15:30:08

#9 Hardware & System Configuration » GUI does not start automatically » 2025-10-17 10:38:52

#10 Re: Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-06-02 02:19:06

#11 Re: Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-06-01 21:14:36

#12 Re: Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-06-01 19:13:24

#13 Re: Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-05-31 16:33:58

#14 Hardware & System Configuration » bootlog is dysfunctional in devuan LXC-containers » 2025-05-31 16:13:38

#15 Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-05-31 15:54:09

#16 Re: Documentation » Please clarification: UDEV -OR- EUDEV -OR- BOTH on devuan » 2025-05-27 23:37:29

#17 Installation » Looking for the "right way" to install xfce4 » 2025-05-25 18:05:37

#18 Documentation » Please clarification: UDEV -OR- EUDEV -OR- BOTH on devuan » 2025-05-25 17:34:32

#19 Re: Installation » [SOLVED] Remove auto-start of X, want to start manually » 2024-12-10 03:36:56

#20 Installation » [SOLVED] Remove auto-start of X, want to start manually » 2024-12-09 18:41:20

#21 Installation » After installing firmware, runlevel is unknown » 2024-07-21 17:36:26

#22 Re: Hardware & System Configuration » Systemtap packaging error - cannot be used » 2024-07-08 14:11:28

#23 Re: Hardware & System Configuration » Looking for the RIGHT way to create a bridge » 2024-07-07 21:17:33

#24 Re: Hardware & System Configuration » How to repair APPARMOR? » 2024-07-07 20:53:21

#25 Hardware & System Configuration » How to repair APPARMOR? » 2024-07-06 21:55:36

Board footer