Bug#920018: marked as done (Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2019 12:51:45 +0000
with message-id <E1go6O9-000Ffz-9K at fasolo.debian.org>
and subject line Bug#920018: fixed in systemd 240-5
has caused the Debian Bug report #920018,
regarding Memory Leak in journald?  Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
920018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920018
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Sven Hartge <sven at svenhartge.de>
Subject: Memory Leak in journald?  Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory
Date: Mon, 21 Jan 2019 17:17:23 +0100
Size: 110477
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190128/db6d67ef/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Martin Pitt <mpitt at debian.org>
Subject: Bug#920018: fixed in systemd 240-5
Date: Mon, 28 Jan 2019 12:51:45 +0000
Size: 5100
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190128/db6d67ef/attachment-0003.mht>