Bug ID 1202840
Summary system crash after update of "filesystem"
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS openSUSE Tumbleweed
Status NEW
Severity Critical
Priority P5 - None
Component Basesystem
Assignee screening-team-bugs@suse.de
Reporter ub22@gmx.net
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Falkon/22.08.0 Chrome/87.0.4280.144 Safari/537.36
Build Identifier: 

After filesystem update at snapshot 20220821 and now 20220826 - my system
crashed. Also in the shell a command like ls don't work anymore like
/usr/bin/ls not found. Only Hard reset works - but base system crash so they
can't find the initrd anymore.

Possible steps to fix the Issue:
* Disable TPM 2.0 in UEFI BIOS (so in other way a read only snapshoot don't
work)
* Boot previous read only snapshoot
* open a super user terminal and execute "snapper rollback && reboot"
* After login at first the "Systemeinstellungen" must be opened and the path to
the backup must be set. Afterwards the ~/.local/share/kwalletd/kdewallet.kwl
must be restored from previous backup
* open a super user terminal again and run "zypper ref ; unmount ~/bin ; 
zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin"
* But this time als 
( 13/283) Installing: filesystem-84.87-7.1.x86_64
..................................................................................................................[error]
Installation of filesystem-84.87-7.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): r
( 13/283) Installing: filesystem-84.87-7.1.x86_64
..................................................................................................................[error]

Same issue as before
# ls
bash: /usr/bin/ls: No such file or directory


After successfull update I plane at the next boot to enable TPM 2.0 again
  (not done till now).



Reproducible: Always

Steps to Reproduce:
1. zypper (d)up or update over KDE update tool
2. NFS and bind mounts (e.g. ~/bin for the main user)
3. See also above
Actual Results:  
System crash again and I need to repeat the procedure :-(

Expected Results:  
zypper up/dup runs propperly at least on all automatic graphical updates

Beside the data loss (kwallet) the replay takes a while.

Additional there are since some years, time to time updates from "filesystem"
hanging on PC (I expect due to NFS and bind mounts)! This us not accepteable
for a standard user.


You are receiving this mail because: