yaap's questions

On an Xubuntu 22.04 freshly installed, I got this error message when the XFCE desktop starts, just after a successful login:

I don't even know how to start to debug this message. I looked at ~/.xsession-errors and /var/log/syslog but there are lots of error messages and I don't know which one is the cause of this graphical error message.

Hints:

• I do not have the same error message with another graphical environment (such as Mate).
• I had a similar issue (maybe the same?) on my Ubuntu 20.04 with XFCE before I format to install Xubuntu 22.04, so maybe it is related to my XFCE customization (1 panel with menu, windows buttons, status indicators, and time - Microsoft style), or to my hardware?

Where should I look? Is it an issue from XFCE or from the system itself which is reported by XFCE?

TL;DR

Does anyone have a working netplan configuration that sets a dynamic IPv4 and a static IPv6 under Ubuntu Server 20.04?

What works

My provider (OVH) gave me a server with this configuration in /etc/netplan/50-cloud-init.yaml out of the box:

# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        ens3:
            dhcp4: true
            match:
                macaddress: xx:yy:zz:aa:bb:cc
            mtu: 1500
            set-name: ens3

So the server is obtaining an IPv4 address through DHCP. Everything works here.

The issue

But, they also gave a static IPv6 (found from the web console management for this server) which is not present in the netplan configuration.

I tried to add it manually, using snippet like:

network:
    version: 2
    ethernets:
        ens3:
            dhcp6: false
            match:
                name: ens3
            addresses:
              - "dead:beef:404:200::cafe/128"
            gateway6: "dead:beef:404:200::1"

But nothing works: if the IPv4 works I have no IPv6, and if I get an IPv6 it revokes my IPv4 and I lose access to the server.

The try

I just tried this exact configuration in /etc/netplan/60-test-askubuntu.yaml after renamed all other files with .yaml.bak:

network:
    version: 2
    ethernets:
        ens3:
            dhcp6: false
            addresses:
              - "2001:41d0:206:cd1d::6153/128"
            gateway6: "2001:41d0:206:cd1d::1"
            dhcp4: true
            mtu: 1500

Result: the IPv4 is still working but I guess it will fail when the DHCP bail will be expired. The IPv6 address is set, but the gateway is not set so I cannot ping6 an IPv6 address:

user@server:/etc/netplan$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:23:28:1f brd ff:ff:ff:ff:ff:ff
    inet 51.210.xx.yy/32 scope global dynamic ens3
       valid_lft 86396sec preferred_lft 86396sec
    inet6 2001:41d0:206:cd1d::6153/128 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe23:281f/64 scope link 
       valid_lft forever preferred_lft forever
user@server:/etc/netplan$ ip route
default via 51.210.8.1 dev ens3 proto dhcp src 51.210.xx.yy metric 100 
51.210.8.1 dev ens3 proto dhcp scope link src 51.210.xx.yy metric 100 
user@server:/etc/netplan$ ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from par21s12-in-f14.1e100.net (172.217.22.142): icmp_seq=1 ttl=51 time=6.16 ms
64 bytes from par21s12-in-f14.1e100.net (172.217.22.142): icmp_seq=2 ttl=51 time=6.19 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 6.161/6.177/6.194/0.016 ms
user@server:/etc/netplan$ ping6 google.com
ping6: connect: Network is unreachable
user@server:/etc/netplan$ ip route
default via 51.210.8.1 dev ens3 proto dhcp src 51.210.xx.yy metric 100 
51.210.8.1 dev ens3 proto dhcp scope link src 51.210.xx.yy metric 100 
user@server:/etc/netplan$ ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:41d0:206:cd1d::6153 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium

Question

Does anyone have a working netplan configuration for a dynamic IPv4 and a static IPv6?

It works when I set it manually using ip addr and ip route but I want a permanent configuration using netplan.

I encounter the exact same problem as here except I'm not able to recover using the proposed solution.

Could not load 'vboxdrv' after upgrade to Ubuntu 16.04 (and I want to keep secure boot)

I have followed the recommended solution and everything seems fine but still the module could not be loaded.

The key seems correctly loaded:

$ sudo mokutil --list-enrolled
[key 1]
[…]
[key 2]
SHA1 Fingerprint: 0f:6f:8e:7a:39:d0:27:33:7d:eb:e0:62:cf:38:b1:af:4c:82:98:c4
Certificate:
[…]
        Issuer: CN=modssign
[…]
        X509v3 extensions:
            X509v3 Subject Key Identifier: 
                83:83:25:5B:D6:6E:A0:BB:87:44:A9:8C:EA:47:58:DD:07:B9:A6:C7
            X509v3 Authority Key Identifier: 
                keyid:83:83:25:5B:D6:6E:A0:BB:87:44:A9:8C:EA:47:58:DD:07:B9:A6:C7
[…]

And the module is signed with this key:

$ sudo modinfo vboxdrv
filename:       /lib/modules/3.16.0-77-generic/misc/vboxdrv.ko
version:        5.1.0 r108711 (0x00260000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     32F3C607C8086AE6187D18B
depends:        
vermagic:       3.16.0-77-generic SMP mod_unload modversions 
signer:         modssign
sig_key:        83:83:25:5B:D6:6E:A0:BB:87:44:A9:8C:EA:47:58:DD:07:B9:A6:C7
sig_hashalgo:   sha256

But the module still failed to insert:

$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

Do you have any idea? I thought I had correctly follow all the steps (including enrolling the new key at boot, etc)

More technical information:

• Ubuntu 14.04.4 LTS freshly updated
• Linux 3.16.0-77-generic
• Virtualbox 5.1.0 r108711 freshly downloaded from the Virtualbox.org website

Thanks in advance for your hints!

Edit of 2016-08-23:

I think the issue is due to the fact my certificate is never loaded by the kernel at boot.

The certificate loaded by the kernel is 4a94:

$ sudo dmesg | grep 'Loaded X.509 cert'
[    1.126207] Loaded X.509 cert 'Magrathea: Glacier signing key: 4a94aff5eff7b539906b3f2a9d0cca00dac4cbb0'

And all modules are well loaded because they are signed with this specific key (4a94):

$ sudo modinfo ip_tables | grep sig_key
sig_key:        4A:94:AF:F5:EF:F7:B5:39:90:6B:3F:2A:9D:0C:CA:00:DA:C4:CB:B0

But even if my certificate is shown in mokutil --list-enrolled, it seems to not be loaded at boot.

How could I add my certificate to the kernel at boot sequence? Do I have to rebuild a new kernel with my certificate in it?