Hi
I have 2 identical MiniPCs. I want to create a Proxmox HA-cluster but I also need one of the MiniPCs as MediaCenter with video output.
I first tried iGPU passthrough but unfortunaely this doesen't work due to the famous AMD reset-bug.
My second take at this, is to install the Desktop Environement on top of Proxmox. I have done that via tasksel. KDE Plasma is running. However Plasma or parts of it, e.g. the Network-Manager and Discover think the DE is offline. My understanding is that this is the case because Network Manager does not see the vmbr0.
I tried to edit /etc/NetworkManager/NetworkManager.conf and set managed=false to managed=true under [ifupdown]. This only makes my ethernet interfaces visible to network-manager but not the vmbr0.
How can I fix that and get Plasma to a state that it correctly reflects online/offline status?
Here some logs:
Also after installing Plasma my logs get flooded with these messages (dmesg):
And these (journalctl):
What is this and how can I correct whatever is wrong?
I shortly tried with GNOME and with GNOME I do not see the drkonqi-coredump logs. I don't linke GNOME though and would prefere to have Plasma everywhere.
Thank you very much for your help and time.
I have 2 identical MiniPCs. I want to create a Proxmox HA-cluster but I also need one of the MiniPCs as MediaCenter with video output.
I first tried iGPU passthrough but unfortunaely this doesen't work due to the famous AMD reset-bug.
My second take at this, is to install the Desktop Environement on top of Proxmox. I have done that via tasksel. KDE Plasma is running. However Plasma or parts of it, e.g. the Network-Manager and Discover think the DE is offline. My understanding is that this is the case because Network Manager does not see the vmbr0.
I tried to edit /etc/NetworkManager/NetworkManager.conf and set managed=false to managed=true under [ifupdown]. This only makes my ethernet interfaces visible to network-manager but not the vmbr0.
How can I fix that and get Plasma to a state that it correctly reflects online/offline status?
Here some logs:
Code:
root@gateway:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface enp195s0 inet manual
iface enp196s0 inet manual
iface wlp194s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.137/24
gateway 192.168.1.1
bridge-ports enp195s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
source /etc/network/interfaces.d/*
root@gateway:~#
Code:
root@gateway:~# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
# managed=false
managed=true
root@gateway:~#
Also after installing Plasma my logs get flooded with these messages (dmesg):
Code:
[ 2720.923048] audit: type=1400 audit(1758206290.422:484): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12104 comm="cupsd" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
[ 2720.923312] audit: type=1400 audit(1758206290.422:485): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/cupsd" name="/etc/paperspecs" pid=12104 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2720.924271] audit: type=1400 audit(1758206290.423:486): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12104 comm="cupsd" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
[ 2720.925752] audit: type=1400 audit(1758206290.425:487): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12104 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested="create" denied="create" addr=none
[ 2720.929202] audit: type=1400 audit(1758206290.428:488): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12105 comm="dbus" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
[ 2720.929216] audit: type=1400 audit(1758206290.428:489): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12105 comm="dbus" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
[ 2720.929304] audit: type=1400 audit(1758206290.428:490): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="/usr/sbin/cupsd" pid=12105 comm="dbus" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
And these (journalctl):
Code:
Sep 18 16:41:41 gateway systemd[11470]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
Sep 18 16:41:44 gateway plasmashell[1762]: org.kde.plasma.nm.libs: Wireless scan on "wlp194s0" failed: "Scanning not allowed while unavailable"
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 18 16:41:52 gateway systemd[11470]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
Sep 18 16:41:54 gateway plasmashell[1762]: org.kde.plasma.nm.libs: Wireless scan on "wlp194s0" failed: "Scanning not allowed while unavailable"
What is this and how can I correct whatever is wrong?
I shortly tried with GNOME and with GNOME I do not see the drkonqi-coredump logs. I don't linke GNOME though and would prefere to have Plasma everywhere.
Thank you very much for your help and time.