From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 128 testing report
Date: Thu, 07 Mar 2019 16:28:00 +0000 [thread overview]
Message-ID: <e57ae7ca-2777-d4b6-33fb-dd9008f8a8e3@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Hello,
Core Update 128 is running for about two days here by now.
So far, I did not observe any usual or buggy behaviour. RAM
consumption seems to be more volatile after the upgrade, possible
due to updated Tor version.
Accessing the WebUI via TLS 1.3 works fine and by default
with Firefox 60.5.1esr.
I can confirm bug #11973 is fixed after upgrading and rebooting
the machine.
Thanks, and best regards,
Peter Müller
reply other threads:[~2019-03-07 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e57ae7ca-2777-d4b6-33fb-dd9008f8a8e3@ipfire.org \
--to=peter.mueller@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