Hi Michael,

On 25/05/2021 13:35, Michael Tremer wrote:
> Okay, thank you for double-checking.
> 
> I assume this is a fresh installation?
No, this was a working Core Update 156 vm that I cloned and changed to Testing and did the update. The error message came up when rebooting after the upgrade.

> 
> Can you try loading the inotify Python module on a Python 3 shell?
I will give that a try and come back with what I find.

Regards,
Adolf.
> 
> -Michael
> 
>> On 25 May 2021, at 12:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 25/05/2021 12:18, Michael Tremer wrote:
>>> Hello,
>>> Is this problem still happening with the recent builds?
>> I just tried it now, 13:30 in Netherlands, and got the same result.
>>
>> This is on my VirtualBox vm testbed.
>>
>> Regards,
>> Adolf.
>>> Best,
>>> -Michael
>>>> On 21 May 2021, at 14:26, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> After updating and doing the reboot I got the following message on the boot screen.
>>>>
>>>> Starting Unbound DHCP Leases Bridge...
>>>> Traceback (most recent call last):
>>>> File "/usr/sbin/unbound-dhcp-leases-bridge", line 35, in <module>
>>>> import inotify.adapters
>>>> ModuleNotFoundError: No module named 'inotify'                          [FAIL]
>>>>
>>>> The prior message was Starting DHCP Server...    [OK]
>>>>
>>>> The following message was Starting SSH Server...    [OK] which is interesting as the ssh connection would not work until I had pressed Save in the ssh WUI page
>>>>
>>>> Regards,
>>>>
>>>> Adolf.
>>>>
>>>>
>