on my dekstop PC plasma5 keeps crashing during login with a segfaullt in libsoprano
the log just shows:
**kded5[4371]: segfault at 7fbdc9406350 ip 00007fbd829740a2 sp 00007ffc528014b0 error 7 in libsoprano.so.4.3.0[7fbd82930000+1160[/b]00]
on my laptop logging in seems to work but when the screenlocker activates i cannot unlock the screen (nothing shows up in logs and screenlocker just shows authentication failed message)**
Strange. Plasma5 or kded5 should not use libsoprano at all. That was only used by KDE4’s Nepomuk which has been dropped over a year ago, in KDE 4.13 already.
But apparently some kded5 plugin tries to use it, no idea which one that could be.
And as libsoprano uses Qt4, it will crash the Qt5 based kded5.
Do you see this with a fresh user account as well?
Run kdebugdialog and enable all debugging output, then run “kded5” in a terminal window. It should print which plugins it tries to load then, this should show which one is crashing.
OTOH, even if kded5 crashes, this should not affect the desktop itself.
Try to run plasmashell in a terminal window as well, maybe there’s a message why it crashes.
on my laptop logging in seems to work but when the screenlocker activates i cannot unlock the screen (nothing shows up in logs and screenlocker just shows authentication failed message)
Seems to be a PAM issue.
You are probably using the old and deprecated pam_unix2.so, Plasma5’s screenlocker doesn’t work with that.
Have a look into /etc/pam.d/ whether there are .rpmnew files and replace the originals with them.
Or replace pam_unix2.so with pam_unix.so manually in /etc/pam.d/common-*.**
i had no time today to check on the pc problem, but the laptop works now after replacing the pam files
Fine.
Regarding your kded5 crash, it might be related to this bug (that actually was/is in KDE4 already too):
https://bugs.kde.org/show_bug.cgi?id=344519
As libsoprano is the culprit that pulls in Qt4 in your case, it would probably be helpful to know what packages on your system require libsoprano (to find out which kded plugin causes the crash so that you can uninstall it).
So maybe post the output of this:
rpm -e --test libsoprano4
But kded5’s debug output should tell as well I think.
before trying today i did a zypper up, and now login just works so i guess one of the updates in the last 2 days fixed the problem for me.
so i can just provide the output of rpm -e
rpm -e --test libsoprano4
error: Failed dependencies:
libsoprano.so.4()(64bit) is needed by (installed) libkde4-4.14.8-1.1.x86_64
libsoprano.so.4()(64bit) is needed by (installed) kdelibs4-4.14.8-1.1.x86_64
Hm. Probably one of the KDE4 packages got not replaced by the KF5 version at first?
Good to hear that it’s fixed though.
so i can just provide the output of rpm -e
Well, it’s normal that you have kdelibs4 (necessary for KDE4 applications), and kdelibs4 still contains the old Nepomukv1 so requires libsoprano. But that shouldn’t cause a problem.
I am getting the same kded5 crash on login after an upgrade. Here is the crash debug information:
Application: kded5 (kded5), signal: Segmentation fault
Using host libthread_db library “/lib64/libthread_db.so.1”.
[Current thread is 1 (Thread 0x7f6b7df4f780 (LWP 20840))]
Thread 2 (Thread 0x7f6b70e6f700 (LWP 20841)):
#0 __lll_lock_wait () at …/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1 0x00007f6b7ae324bb in __GI___pthread_mutex_lock (mutex=0x7f6b7df89908 <_rtld_local+2312>) at …/nptl/pthread_mutex_lock.c:115
#2 0x00007f6b7dd69032 in tls_get_addr_tail (ti=0x7f6b7db48da0, dtv=0x1a35cc0, the_map=0x7f6b7df87b40) at dl-tls.c:765
#3 0x00007f6b7d7e61a0 in __GI___call_tls_dtors () at cxa_thread_atexit_impl.c:83
#4 0x00007f6b7ae30492 in start_thread (arg=0x7f6b70e6f700) at pthread_create.c:343
#5 0x00007f6b7d896a4d in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 1 (Thread 0x7f6b7df4f780 (LWP 20840)):
[KCrash Handler]
#4 ref (this=<optimized out>) at /usr/include/QtCore/qatomic_x86_64.h:121
#5 QHash (this=0x7f6b5e5338a0 <(anonymous namespace)::typeHash>) at /usr/include/QtCore/qhash.h:281
#6 __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/src/debug/soprano-2.9.4/soprano/node.cpp:422
#7 _GLOBAL__sub_I_node.cpp(void) () at /usr/src/debug/soprano-2.9.4/soprano/node.cpp:572
#8 0x00007f6b7dd769fa in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffcb471f78, env=env@entry=0x1a15bb0) at dl-init.c:72
#9 0x00007f6b7dd76ae3 in call_init (env=0x1a15bb0, argv=0x7fffcb471f78, argc=1, l=<optimized out>) at dl-init.c:30
#10 _dl_init (main_map=main_map@entry=0x1aa8e00, argc=1, argv=0x7fffcb471f78, env=0x1a15bb0) at dl-init.c:120
#11 0x00007f6b7dd7ac65 in dl_open_worker (a=a@entry=0x7fffcb471518) at dl-open.c:558
#12 0x00007f6b7dd768b4 in _dl_catch_error (objname=objname@entry=0x7fffcb471508, errstring=errstring@entry=0x7fffcb471510, mallocedp=mallocedp@entry=0x7fffcb471507, operate=operate@entry=0x7f6b7dd7a9a0 <dl_open_worker>, args=args@entry=0x7fffcb471518) at dl-error.c:187
#13 0x00007f6b7dd7a46b in _dl_open (file=0x1aa8c68 “/usr/lib64/qt5/plugins/kded_printmanager.so”, mode=-2147483647, caller_dlopen=<optimized out>, nsid=-2, argc=1, argv=0x7fffcb471f78, env=0x1a15bb0) at dl-open.c:642
#14 0x00007f6b781c0fbb in dlopen_doit (a=a@entry=0x7fffcb471730) at dlopen.c:66
#15 0x00007f6b7dd768b4 in _dl_catch_error (objname=0x1a1ca30, errstring=0x1a1ca38, mallocedp=0x1a1ca28, operate=0x7f6b781c0f60 <dlopen_doit>, args=0x7fffcb471730) at dl-error.c:187
#16 0x00007f6b781c156d in _dlerror_run (operate=operate@entry=0x7f6b781c0f60 <dlopen_doit>, args=args@entry=0x7fffcb471730) at dlerror.c:163
#17 0x00007f6b781c1051 in __dlopen (file=<optimized out>, mode=<optimized out>) at dlopen.c:87
#18 0x00007f6b7b5cddc0 in QLibraryPrivate::load_sys (this=0x1aa8b20) at plugin/qlibrary_unix.cpp:223
#19 0x00007f6b7b5c5d65 in QLibraryPrivate::load (this=0x1aa8b20) at plugin/qlibrary.cpp:529
#20 0x00007f6b7b5c634b in QLibraryPrivate::loadPlugin (this=0x1aa8b20) at plugin/qlibrary.cpp:577
#21 0x00007f6b7b5bb030 in QPluginLoader::load (this=<optimized out>) at plugin/qpluginloader.cpp:232
#22 0x00007f6b7ba58bba in KPluginLoader::load (this=this@entry=0x7fffcb471be0) at /usr/src/debug/kcoreaddons-5.10.0/src/lib/plugin/kpluginloader.cpp:184
#23 0x00007f6b7ba58cda in KPluginLoader::instance (this=this@entry=0x7fffcb471be0) at /usr/src/debug/kcoreaddons-5.10.0/src/lib/plugin/kpluginloader.cpp:166
#24 0x00007f6b7ba58d17 in KPluginLoader::factory (this=this@entry=0x7fffcb471be0) at /usr/src/debug/kcoreaddons-5.10.0/src/lib/plugin/kpluginloader.cpp:111
#25 0x00007f6b7db5acf0 in Kded::loadModule (this=this@entry=0x1a93100, module=…, onDemand=onDemand@entry=false) at /usr/src/debug/kded-5.10.0/src/kded.cpp:404
#26 0x00007f6b7db5b887 in Kded::initModules (this=this@entry=0x1a93100) at /usr/src/debug/kded-5.10.0/src/kded.cpp:271
#27 0x00007f6b7db5c010 in Kded::recreateDone (this=this@entry=0x1a93100) at /usr/src/debug/kded-5.10.0/src/kded.cpp:575
#28 0x00007f6b7db5cf93 in Kded::recreate (this=0x1a93100, initial=<optimized out>) at /usr/src/debug/kded-5.10.0/src/kded.cpp:548
#29 0x00007f6b7db5d371 in kdemain (argc=1, argv=0x7fffcb471f78) at /usr/src/debug/kded-5.10.0/src/kded.cpp:818
#30 0x00007f6b7d7d08c5 in __libc_start_main (main=0x4007c0 <main(int, char**)>, argc=1, argv=0x7fffcb471f78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffcb471f68) at libc-start.c:289
#31 0x00000000004007f9 in _start () at …/sysdeps/x86_64/start.S:118
Apparently the error is caused by kde-print-manager, I removed the package and the constant crashes disappeared.
Hm. kde-print-manager is the KF5 version and should not pull in libsoprano4.
But you probably still had kde4-print-manager installed?
There was a problem with the obsoletes there apparently so the KDE4 version might not have been replaced by the KF5 version automatically.
Should be fixed already meanwhile though.
I was also getting the same kded5 crash windows popping up after upgrading to plasma5-5.3. I would get over twenty seg-fault windows popping up whenever I started my system. Also, apps would take a long time to launch and I would usually get at least one kded5 segfault window when launching any app. If I started an app from Konsole, it would launch immediately with no error. I could only type one letter into the Kickoff menu search and one of those seg-fault windows would pop up and I couldn’t type any more. Same with krunner.
I right clicked on the KDE kickoff menu icon in the lower left and chose ‘Alternatives’ and switched from Application Menu cascading menus to Application Launcher and all my problems went away.
The printer icon on the right side of the panel by the digital clock also was giving me a plugin error when I clicked on it, but after changing my menu type, it shows my printer as idle and no error. I was totally surprised that this one small change solved all of my problems.
That is a very useful rpm command (for those of us trying to understand dependencies) ! Thanks for posting that.
I don’t think that switching the application launcher by itself solves any such problem.
But maybe the cache was reconstructed (kbuildsycoca5), maybe even as result of the switch, so the KF5 plugins were found/loaded now, and preventing the crash.
Would also explain why the printer plasmoid could now be loaded, although it couldn’t before.
I’m pretty sure that it will still work if you switched back to Kicker (“Application Menu based on cascading menus”). 
You’re right. I switched back to cascading menus and everything is still working.
Well, it’s actually kded(5) that takes care of keeping the “System Configuration Cache” (sycoca) up to date when corresponding files on the hard disk change/get added or removed via package installations.
So if kded5 just crashes on startup, the cache is not refreshed any more.
KickOff (the other application launcher that was already the default in KDE4) might have run the refresh explicitely when it was first started, which fixed your issue.
Running “kbuildsycoca5” should have fixed it too, then.
This happens when you upgrade from the currently-shipped OpenSuSE to ‘tumbleweed’ (either by yast upd, or by ‘update’ from DVD) but does not happen if you ‘install’ from DVD (and re-format your installation partition). So there is something not right about the supersedes RPMs which needs fixing before the new OpenSuSE gets shipped. I can’t get bugzilla to work for me; can anyone report it there on my behalf ?
Correct, there were some “Obsoletes” missing, so not all KDE4 packages got correctly replaced by their Plasma5 counterparts (kde4-print-manager as mentioned e.g.).
This has been fixed already though (the known cases at least). Unfortunately it takes a while until the fixed packages are in the repo, they should be part of the next snapshot.
But there’s no need for a bug report, at least not now.
PS: a new snapshot has been released just now, and the “fixed” (with correct Obsoletes) kde-print-manager package is now in the repo.
So there should be no problem any more even if you upgrade from 13.2 (unless something else has been forgotten/went wrong)