Registered Member
|
Anyone experiencing issues after the latest upgrade? (https://www.kde.org/announcements/plasma-5.4.3.php).
Am on Fedora 22 64b, Nvidia graphics driver, until then perfectly running system is driving me mad after yesterday's upgrade. What's happening at the boot time is that the progress bar on the splash screen freezes for about a minute or two, as the desktop finally comes up, no elements on the workspace respond to click attempts and the system stalls effectively. Something seems to be cookin' under covers though but I can't even use keyboard to switch to another terminal.... After a while I seem to be able to click on widgets but there's no reply. Clicking on anyhting like the konsole, kwrite etc will yield "KDEInit could not launch xxxxx". Waiting another 5 to 10 minutes, the system seems to recover, responding very lazy..... hard to collect any data to debug this. Anyway, if I'm lucky and manage to trigger journalctl I can spot DBUS errors, tons of segfaults, some errors to systray, hundreds of errors like "...no icon sets..." etc. Again it's hard to export these 'cause the system is half dead, but I'll try to get exact outputs as soon as I can. I tend to think it has to with the systray daemon as the systray does not seem to get updated, e.g. my kwallet that should load int the systray will never appear showing "bad window" errors.... but that could be just a victim of something else.... Did common stuff like removing .config/ , .kde/ , .cache/ to no avail.... |
|
My personal experience is that if the SNI daemon (and a host, ie. SNI plasmoid!) isn't running or responding, *every* systray user is going wild, flooding the dbus daemon and running at 100% CPU.
Not related to a particular update, though - has always been like that, but the update could have broken SNI daemon or host for you. |
Registered Member
|
I keep getting these repeatedly:
Foud that xembedsniproxy cannot load:
As I do not require the XEmbed system tray icons I'm gonna remove that from /etc/xdb/autostart to start with... Kmix seems to broken as well:
And The Power management too as the configuration applet yields "Power management configuration cannot be loaded..." even though the service is running. The service is running, stopping that however gives me Plasma crash.... |
|
This is the killer, it means kded5 cannot be started (veeeery bad) and is likely to be restarted over and over again. It's also a critical element for the SNI stuff, so probably causing those issues as follow up. Check
QMetaObject should be in Qt5Core. Maybe this is an old file (linking Qt4) and the new one is somewhere up in LD_LIBRARY_PATH (eg. /usr/lib64/ or something) In any case, this very much looks like an installation error. (Full disk, broken libQt5Core.so, etc.?) |
Registered Member
|
Thanks for your notes luebking!
This was a clean fresh install of KDE5 a year ago... without any major issues until now. It's Lenovo T420. Anyways, I managed to bring my system back to kinda responsive mode now. - I re-installed all kf5-* packages as I had noted a dependency issue on these - removed xembedsniproxy.desktop from the autostart - removed System Tray widget from my panel - uninstalled kmix package to mitigate crashes on that one - re-installed powerdevil-5* -re-installed qt5-qtbase* It's booting fast now and I can work with the system as usual, the kded errors bounce regularly though, on hourly basis:
Here goes my lib dependencies to libpowerdevilcore.so.2:
Here is the start of my .xsession-errors:
I'll continue putting the pieces back together, at least I can work with box now.... |
Registered Member
|
So I received new kernel update (4.2.6) and updates to QT5 (5.5.1-8) which magically fixes most of my issues. I no longer see the kded5 errors, power management is back as well as xembedsniproxy.... system tray gets loaded almost properly, the only thing is that it will not show icons for GTK apps... that's minor though
|
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]