I think an update on "Tumbleweed – Review of the week xx" from DimStar
would makes sense.
Myself I read carefully every week and I think a warning coming from
Dominique would be the best channel.
Message could be:
Warning: Tumbleweed users using LUKS encrypted devices reported
plymouth related issues. Current workaround identified is to disable
plymouth at boot time with "plymouth.enable=0" on kernel command line.
rgds
Paul
On Mon, Feb 15, 2016 at 1:31 PM, Ludwig Nussel
Robert Schweikert wrote:
On 02/12/2016 09:09 AM, Fabian Vogt wrote:
I've got a similiar issue (starting from kernel 4.4 IIRC) I haven't got around to debug yet. My lenovo ThinkPad X250 (Broadwell Graphics) hangs at the same point (doesn't display that message though) and just nothing happens. What works for me is to append "plymouth.enable=0" to the kernel cmdline. I'm using an encrypted LVM setup as well, maybe it's related.
Appears to be related, adding "plymouth.enable=0" does the trick.
With plymouth disabled the passphrase is requested right after the the initial message.
How can we communicate such issues so the next one who gets hit knows where to look for first?
cu Ludwig
-- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org