Comment # 44 on bug 1169783 from
(In reply to Jacob W from comment #43)
> I had this issue too, but my setup is more standard and oddly enough, I had
> it *much* worse than others. I only have /home encrypted via LUKS. Paritions
> are standard for TW (meaning / is btrfs with default TW setup).
> 
> So while I could not get the password prompt to work at all, even if
> disabling plymouth via grub, I also had the "pleasure" of having all my
> snapshots removed! I could not rollback because all snapshots disappeared
> from grub and from /.snapshots in recovery mode.
> 
> After much cursing (which helps a lot in these types of situations & I
> highly recommend it), many reboots and trial and error, including editing
> crypttab because the man page has wrong info re the password entry, by some
> miracle, I finally got my snapshots to show up in grub again. I took no
> further risks, and immedietly proceeding to rollback, locked every package
> that has anything to do with plymouth, and zypper dup again. Now my system
> works fine.
> 
> I hate plymouth with a passion. Years ago I had a similar situation but
> without the disappearing snapshots (I reported a bug, but plymouth
> maintainer decided to ignore it after some time).
> 
> There was talk awhile back of removing plymouth from openSUSE. This needs to
> be done, not just talked about.
> 
> I'm most definitely not risking more horrors & decided not to "retry" to get
> logs.

Plymouth have ability to delete .snapshots? Maybe this have to be filed in a
separate bug/feature request to limit plymouth permission?


You are receiving this mail because: