Yesterday I installed the latest huge TW 20190713 snapshot update. I had to update more than 7000 packages with "zypper dup" Immediately after installing the update, multiple commands started to crash, e.g. rpm, cp, getfacl, vim and others. Rebooting did not fixed the problem. Several programs already crash on booting. In /var/lib/systemd/coredump/ I found core dumps for smbd, system-journal, system-udevd. "dmesg" shows "Bad RIP value" messages. E.g. [12662.324058] systemd-journal[18780]: segfault at 0 ip 0000000000000000 sp 00007ffd64331e28 error 14 in systemd-journald[561ebb49c000+6000] [12662.324063] Code: Bad RIP value. I tried to debug the root cause. I started with the simple commands. The seem to crash, if ACL functions are used. E.g. # cp /etc/motd /tmp/ [...OK...] # cp -p /etc/motd /tmp/ cp: overwrite '/tmp/motd'? y Segmentation fault (core dumped) # getfacl / Segmentation fault (core dumped) GDB shows, that the programs crash if the access the ACL function acl_get_file. For instance getfacl and Samba crash here: # gdb /usr/bin/getfacl [...] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007ffff7bac436 in acl_get_file () from /lib64/libacl.so.1 #2 0x00005555555575db in do_print (walk_flags=<optimized out>, unused=<optimized out>, st=0x7fffffffcc10, path_p=0x7fffffffccf0 "/") at tools/getfacl.c:469 # gdb core.smbd.0.a5557045f77e4a24b8a02fae64aa0734.16515.1563363628000000 /usr/sbin/smbd [...] Core was generated by `/usr/sbin/smbd --foreground --no-process-group'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007fdd427bc549 in __GI_abort () at abort.c:79 #2 0x00007fdd421f54ab in dump_core () from /usr/lib64/libsmbconf.so.0 #3 0x00007fdd422193fb in smb_panic_s3 () from /usr/lib64/libsmbconf.so.0 #4 0x00007fdd427406ff in smb_panic () from /usr/lib64/libsamba-util.so.0 #5 0x00007fdd4274095d in ?? () from /usr/lib64/libsamba-util.so.0 #6 <signal handler called> [...] I could solve the "getfacl" issue by recompiling and installing the "acl" packages (acl, libacl1, libacl-devel). Unfortunately this does not fix the problems of cp, smbd, vim etc. I found the LTO discussion here. Could this be the root cause? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org