Comment # 4 on bug 1206684 from Thomas Schulte

Same issue on my openSUSE TW running via VMware Fusion Player on a MacBook Air
M2. The latest zypper package was installed on Dec 13 already and no issues
occurred afterwards. I was even able to run another "zypper dup" today, but I
noticed various segfaults afterwards. At least Zypper, YaST and chkstat were
affected.

I managed to rollback to the Dec 13 Btrfs snapshot and upgraded all available
packages in heaps. It seems that "libgcc_s1-13.0.0+git197351-4.1.aarch64" is
broken, because downgrading it to an older DVD/ISO version helps:

> suse:~ # zypper ref
> Segmentation fault (core dumped)
> 
> suse:~ # rpm -q libgcc_s1 
> libgcc_s1-13.0.0+git197351-4.1.aarch64
> 
> suse:~ # rpm -Uvh --oldpackage /mnt/aarch64/libgcc_s1-12.2.1+git537-1.1.aarch64.rpm 
> Verifying...                          ################################# [100%]
> Preparing...                          ################################# [100%]
> Updating / installing...
>    1:libgcc_s1-12.2.1+git537-1.1      ################################# [ 50%]
> Cleaning up / removing...
>    2:libgcc_s1-13.0.0+git197351-4.1   ################################# [100%]
> 
> suse:~ # zypper ref
> Repository 'Haupt-Repository (OSS)' is up to date.                                                                                                                                            
> Repository 'Hauptaktualisierungs-Repository' is up to date.                                                                                                                                   > All repositories have been refreshed.

All other packages on my system are up-to-date.