From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 156 (testing) report (was: Re: IPFire 2.25 - Core Update 156 available for testing)
Date: Wed, 21 Apr 2021 15:26:13 +0100 [thread overview]
Message-ID: <E46BC22A-34A8-4AD3-9822-4A93A0EBD8EA@ipfire.org> (raw)
In-Reply-To: <dd4758e3-3e3e-e1f9-6944-35a2c2c45f93@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
Hello,
I have assigned this ticket to Stephan. He didn’t respond to my last emails where I asked him to fix a couple of things about the updated “ifconfig” command. So I am not sure if he will fix it in time.
So far the update seems to not cause any trouble and we could look at a release as early as next week.
Best,
-Michael
> On 21 Apr 2021, at 13:25, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> It has been found that if IPFire has the wio addon installed and has one of the themes darkdos, ipfire-legacy or maniac selected in Core Update 155 and then the upgrade to Core Update 156 is carried out, that after reboot when you select Status - Who is Online? that you get an Internal server error message screen.
>
> It was flagged up in the forum by someone with ipfire-legacy. I have confirmed that it occurs with darkdos and maniac as well.
>
> ipfire and ipfire-rounded are confirmed to not show the problem.
>
> From the error log it looks like wio is trying to access a directory that no longer exists after the upgrade. The error log is in the bug report.
>
> This has been raised as bug#12612.
>
> Regards,
>
> Adolf.
>
>
> On 20/04/2021 23:14, Peter Müller wrote:
>> Hello development folks,
>>
>> Core Update 156 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testing)
>> is running here for about 24 hours by now, with no issues known so far.
>>
>> Tested IPFire functionalities in detail:
>> - IPsec (N2N connections only)
>> - Squid (authentication enabled, using an upstream proxy)
>> - OpenVPN (RW connections only)
>> - IPS/Suricata (with Emerging Threats community ruleset enabled)
>> - Guardian
>> - Quality of Service
>> - DNS (using DNS over TLS)
>> - Dynamic DNS
>> - Tor (relay mode)
>>
>> Looking forward to this Core Update.
>>
>> Thanks, and best regards,
>> Peter Müller
>>
>>
prev parent reply other threads:[~2021-04-21 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <161882580503.27807.11098110518344373131.ipfire@ipfire.org>
2021-04-19 16:48 ` IPFire 2.25 - Core Update 156 available for testing Adolf Belka
2021-04-20 7:54 ` Adolf Belka
2021-04-20 21:14 ` Core Update 156 (testing) report (was: Re: IPFire 2.25 - Core Update 156 available for testing) Peter Müller
2021-04-21 12:25 ` Adolf Belka
2021-04-21 14:26 ` Michael Tremer [this message]
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=E46BC22A-34A8-4AD3-9822-4A93A0EBD8EA@ipfire.org \
--to=michael.tremer@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