From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on Core Update 157 testing
Date: Tue, 25 May 2021 13:33:43 +0200 [thread overview]
Message-ID: <af528d62-15ac-e6c0-e925-81e493541ee1@ipfire.org> (raw)
In-Reply-To: <86D00446-92B7-4FDA-AA54-982994D1F155@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
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.
>>
>>
>
next prev parent reply other threads:[~2021-05-25 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 12:14 ummeegge
2021-05-21 12:29 ` Tom Rymes
2021-05-21 13:08 ` Michael Tremer
2021-05-21 13:19 ` Adolf Belka
2021-05-21 13:21 ` Peter Müller
2021-05-21 16:57 ` ummeegge
2021-05-25 11:17 ` Michael Tremer
2021-05-21 13:26 ` Adolf Belka
2021-05-25 10:18 ` Michael Tremer
2021-05-25 11:33 ` Adolf Belka [this message]
2021-05-25 11:35 ` Michael Tremer
2021-05-25 11:42 ` Adolf Belka
2021-05-25 11:49 ` Michael Tremer
2021-05-25 20:12 ` Adolf Belka
2021-05-23 16:15 ` Core Update 157 (testing) report Peter Müller
2021-05-25 10:25 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af528d62-15ac-e6c0-e925-81e493541ee1@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox