[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#902966: pstore: crypto_comp_decompress failed
To
: Ben Hutchings <
ben@decadent.org.uk
>
Cc
:
902966@bugs.debian.org
Subject
: Bug#902966: pstore: crypto_comp_decompress failed
From
: Vincas Dargis <
vindrg@gmail.com
>
Date
: Fri, 17 Aug 2018 16:10:25 +0300
Message-id
: <
[🔎]
ffe75489-b29d-c4f6-905a-c16a46954685@gmail.com
>
Reply-to
: Vincas Dargis <
vindrg@gmail.com
>,
902966@bugs.debian.org
In-reply-to
: <
[🔎]
aadcdf4d-c8e5-5354-f5ba-e3a04f14df0e@gmail.com
>
References
: <
[🔎]
aadcdf4d-c8e5-5354-f5ba-e3a04f14df0e@gmail.com
> <
[🔎]
aadcdf4d-c8e5-5354-f5ba-e3a04f14df0e@gmail.com
> <20180704031057.GA3832@debian>
Why is this bug marked as Done? Issue still persists with 4.17.0-2-amd64 on ASUS N551JM laptop.
If users (upgrading from Strech) are expected to execute these workarounds, maybe there should be
NEWS entry of some sort?
Reply to:
debian-kernel@lists.debian.org
Vincas Dargis (on-list)
Vincas Dargis (off-list)
References
:
Bug#902966: pstore: crypto_comp_decompress failed
From:
Esokrates <esokrarkose@gmail.com>
Prev by Date:
Re: Intalling Kernel 4.16
Next by Date:
Re: [pkg-cryptsetup-devel] Bug#874364: Keyboard layout set in GNOME or with localectl does not apply to initramfs LUKS prompt immediately
Previous by thread:
Bug#902966: pstore: crypto_comp_decompress failed
Next by thread:
linux_4.9.110-3+deb9u2_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Index(es):
Date
Thread