http://bugzilla.suse.com/show_bug.cgi?id=1051354 http://bugzilla.suse.com/show_bug.cgi?id=1051354#c32 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com Flags| |needinfo?(snwint@suse.com) --- Comment #32 from Thomas Blume --- (In reply to Lee Martin from comment #30)

I only installed my 42.3 a few days ago using the initial udev-228-27.2 from the ISO, which created the following /etc/crypttab:

# cat /etc/crypttab cr_-Samsung_SSD_960_PRO_2TB_S3EXNCAHB01257A-part3 /dev/disk/by-id/-Samsung_SSD_960_PRO_2TB_S3EXNCAHB01257A-part3 none none

That is actually bug 1048679.

So, now with a corrected crypttab and the standard udev-228-32.2 I'm fine.

HOWEVER this indicates to me that this Leap 42.3 update around udev is changing many device names at boot versus the ISO installation, so anything dependent on specific device names (like LUKS) is at risk of not working after this update. Therefore a fix of somekind is necessary since imagine LUKs setups to be relatively common on the desktop.

Hm, the only fix I can imagine with an update is to re-add the broken symlinks. The consequence would be to carry something that is broken for a quite long time. I'd prefer if we would document this behaviour and provide an Driver Update for the 42.3 installation system instead. Steffen, would this be feasible? -- You are receiving this mail because: You are on the CC list for the bug.