https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c25 --- Comment #25 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Fabian Vogt from comment #24)

(In reply to Fabian Vogt from comment #23)

...

(In reply to Fabian Vogt from comment #22)

...

(In reply to Josef Reidinger from comment #21)

...

(In reply to Fabian Vogt from comment #20)

...

(In reply to Ancor Gonzalez Sosa from comment #18)

...

We have still not unified the YaST Bootloader and YaST Storage code, as we stated we should do in several comments. But we have implemented something that should fix the main problem described in this bug report.

Starting with yast2-storage-ng 4.3.34, new swap devices will have a pre-generated UUID, which means that UUID will be used by the YaST Bootloader proposal if that's the default method. See more details at https://github.com/yast/yast-storage-ng/pull/1192

Submitted to TW as https://build.opensuse.org/request/show/858102

I'm trying to verify that this is fixed, but apparently none of the openQA tests has "resume=" as part of the kernel cmdline or embedded in the initrd at all anymore. I verified that with a local install.

Is that intentional?

Well, we have now flag that decide if we propose resume or not. But for opensuse it should propose it for x86_64 for non server roles if I remember correctly. It is part of feature to not propose hibernation on servers.

I tried the "generic desktop" role and even checked the "expand swap to ram" box, but didn't get "resume=". In openQA, it doesn't seem to be in any test, so also GNOME, KDE and so on, with several file systems.

I found "# Do not propose resume on virtuals (jsc#SLE-12280)", so it's probably expected that it doesn't work in VMs. I'll try to fake real HW.

Still didn't work. It seems like "propose_hibernation" is only enabled on SLED?

that is strange, default should be true and base for SLE specify it false and SLED then re-enable it. Are you sure that you have swap partition at all? Or if you can, provide logs from your attempt and I can check it. -- You are receiving this mail because: You are on the CC list for the bug.