Bug#815934: marked as done (rfkill state not restored after reboot)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2019 10:16:26 +0100
with message-id <68b057eb-a388-fcf9-93dd-f094607ef0b7 at debian.org>
and subject line Re: rfkill state not restored after reboot
has caused the Debian Bug report #815934,
regarding rfkill state not restored after reboot
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.)


-- 
815934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815934
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Josua Mayer <josua.mayer97 at gmail.com>
Subject: rfkill state not restored after reboot
Date: Thu, 25 Feb 2016 23:23:31 +0100
Size: 4241
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190317/3d0bc6e8/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: rfkill state not restored after reboot
Date: Sun, 17 Mar 2019 10:16:26 +0100
Size: 8867
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190317/3d0bc6e8/attachment-0001.mht>