This happened after yesterday’s update.
After booting the system I get problems with KDEinit and KDEconnector.
Help please.
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb17d150900 (LWP 11059))]
Thread 3 (Thread 0x7fb179c65700 (LWP 11062)):
#0 0x00007fb17f445ae9 in poll () from /lib64/libc.so.6
#1 0x00007fb17da90e36 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007fb17da90f5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007fb17f9cbeab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007fb17f97750b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007fb17f7c2006 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007fb17fc45565 in ?? () from /usr/lib64/libQt5DBus.so.5
#7 0x00007fb17f7c3352 in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007fb17e414fab in start_thread () from /lib64/libpthread.so.0
#9 0x00007fb17f4506af in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7fb17b0d2700 (LWP 11061)):
#0 0x00007fb17f445ae9 in poll () from /lib64/libc.so.6
#1 0x00007fb17e441cc7 in ?? () from /usr/lib64/libxcb.so.1
#2 0x00007fb17e4438fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3 0x00007fb17b300898 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4 0x00007fb17f7c3352 in ?? () from /usr/lib64/libQt5Core.so.5
#5 0x00007fb17e414fab in start_thread () from /lib64/libpthread.so.0
#6 0x00007fb17f4506af in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fb17d150900 (LWP 11059)):
[KCrash Handler]
#5 0x00007fb17e41a81a in pthread_rwlock_unlock () from /lib64/libpthread.so.0
#6 0x00007fb17d8b7fb9 in CRYPTO_THREAD_unlock () from /usr/lib64/libcrypto.so.1.1
#7 0x00007fb17d82fb98 in ERR_load_ERR_strings () from /usr/lib64/libcrypto.so.1.1
#8 0x00007fb17d830d29 in ?? () from /usr/lib64/libcrypto.so.1.1
#9 0x00007fb17d84ec29 in ?? () from /usr/lib64/libcrypto.so.1.1
#10 0x00007fb17e41c9d7 in __pthread_once_slow () from /lib64/libpthread.so.0
#11 0x00007fb17d8b8009 in CRYPTO_THREAD_run_once () from /usr/lib64/libcrypto.so.1.1
#12 0x00007fb17d84f113 in OPENSSL_init_crypto () from /usr/lib64/libcrypto.so.1.1
#13 0x00007fb17d83023e in ERR_get_state () from /usr/lib64/libcrypto.so.1.1
#14 0x00007fb17d830369 in ERR_clear_error () from /usr/lib64/libcrypto.so.1.1
#15 0x00007fb17d84eb19 in ?? () from /usr/lib64/libcrypto.so.1.1
#16 0x00007fb17e41c9d7 in __pthread_once_slow () from /lib64/libpthread.so.0
#17 0x00007fb17d8b8009 in CRYPTO_THREAD_run_once () from /usr/lib64/libcrypto.so.1.1
#18 0x00007fb17d84f33b in OPENSSL_init_crypto () from /usr/lib64/libcrypto.so.1.1
#19 0x00007fb17d7be3c8 in ?? () from /usr/lib64/libcrypto.so.1.1
#20 0x00007fb17d84ebb0 in ?? () from /usr/lib64/libcrypto.so.1.1
#21 0x00007fb17e41c9d7 in __pthread_once_slow () from /lib64/libpthread.so.0
#22 0x00007fb17d8b8009 in CRYPTO_THREAD_run_once () from /usr/lib64/libcrypto.so.1.1
#23 0x00007fb17d84f250 in OPENSSL_init_crypto () from /usr/lib64/libcrypto.so.1.1
#24 0x00007fb17d6bcbd4 in libssh2_init () from /usr/lib64/libssh2.so.1
#25 0x00007fb17eccce3b in ?? () from /usr/lib64/libgit2.so.28
#26 0x00007fb17ec66309 in ?? () from /usr/lib64/libgit2.so.28
#27 0x00007fb17e41c9d7 in __pthread_once_slow () from /lib64/libpthread.so.0
#28 0x00007fb17ec66386 in git_libgit2_init () from /usr/lib64/libgit2.so.28
#29 0x00007fb18152a1bc in KTextEditor::EditorPrivate::EditorPrivate(QPointer<KTextEditor::EditorPrivate>&) () from /usr/lib64/libKF5TextEditor.so.5
#30 0x00007fb18152cee0 in KTextEditor::EditorPrivate::self() () from /usr/lib64/libKF5TextEditor.so.5
#31 0x0000559adf703917 in ?? ()
#32 0x0000559adf6ffac2 in ?? ()
#33 0x0000559adf6f9cac in ?? ()
#34 0x00007fb17f378b7b in __libc_start_main () from /lib64/libc.so.6
#35 0x0000559adf6fb69a in _start ()
[Inferior 1 (process 11059) detached]
Nothing works. Even Yast doesn’t work:
Unfortunately, the Ruby program ended unexpectedly.
If your installation is based on the automatically generated partition layout YaST recommends during setup, you should be able to roll back to a btrfs snapshot before the last update. However, I never tried that myself (because I avoid btrfs for any installs which, in my case, are ext4 only). I just often read forum posts from btrfs proponents who claim that in case of botched system updates/upgrades, you could try and »boot into« an older snapshot.
One deleterious side effect of »rewinding« to older snapshots may be that any other changes you’ve done yourself manually in one of those btrfs partitions/volumes/subvolumes may disappear because they happened after the snapshot. Maybe this link can give you an idea the functionality of snapper etc. But first, please back up any important data to external/independent storage before thinking about experimenting with snapshots.
Last but not least: Why did that last update mess up your installation? Are your repositories correct? Using the »zypper lr« command, here are mine:
Job for firewalld.service failed because a fatal signal was delivered causing the control process to dump core.See "systemctl status firewalld.service" and "journalctl -xe" for details.
alex@linux-1fj7:~> systemctl status firewalld.service
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Mon 2019-05-20 02:29:21 MSK; 11s ago
Docs: man:firewalld(1)
Process: 3410 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS (code=dumped, signal=SEGV)
Main PID: 3410 (code=dumped, signal=SEGV)
alex@linux-1fj7:~> journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
#3 0x00007f6e72cb5667 n/a (libglib-2.0.so.0)
#4 0x00007f6e72cb4ccd n/a (libglib-2.0.so.0)
#5 0x00007f6e72bd8fab start_thread (libpthread.so.0)
#6 0x00007f6e72b096af __clone (libc.so.6)
I do not understand what is going on? I have no words. Bravo, Tumbleweed programmers.