--===============1732310662== Content-Type: multipart/signed; boundary="20090909125700+0200-14346194-16312368152701953"; micalg=pgp-sha1; protocol="application/pgp-signature" --20090909125700+0200-14346194-16312368152701953 Content-Transfer-Encoding: quoted-printable Hi all, Over trying to play with/upgrade components to find out what's behind the https://bugs.kde.org/show_bug.cgi?id=3D206215 bug, it seems that one of the "boiler room" components of KDE developed issues that are not being reported upwards, but affect the entire KDE desktop. Here is how the problems manifest, the phenotype, if you will: - Delay in starting the KDE components that are not standalone, such as the krunner (both when called over menu or ALT+F2) or Kontact. When typing things into the krunner, the delay strikes again after the first character, then disappears for this instance of the krunner. - Kmail complains about some of the certificates of servers it is connecting to, because KDE does not have the CAcert.org root certificate, apparently. So I accept them forever, but that forever only lasts until the application is started the next time, and sometimes not even that long. So clearly the "accept it forever" is not being stored. - The screen cannot be unlocked, the kscreenlocker needs to be killed with -9 from a console to get back to the screen. It is likely that it waits for the erratic timeout to display the password dialog, by which time the password timeout has already run out, and so the password dialog is not even displayed anymore. - knetworkmanager is not working, the system log showing "NetworkManager: connection_get_settings_cb(): Couldn't retrieve connection settings: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.." (Note: At first I was thinking about the dbus causing issues, but it seems to work fine, and the NetworkManager seems to work (it connects to the wired network over DHCP). So I assume it is the "the reply timeout expired" part of the above message that is responsible for the issues.) - The delay does not affect components like the system monitor, or even the system settings - unless specific components of the system settings are being called. Components affected include KDE Resources and KDE Service Manager. But when trying to enter the KDE Service Manager, there is finally an error message: "Unable to contact KDED." Now that would appear to be a potentially good reason for all of the above, only that "ps uaxw | grep kded" shows greve 11626 0.1 0.8 154824 18084 ? R 12:30 0:00 kdeinit4= : kded4 [kdeinit] greve 11965 0.0 0.5 32524 10204 ? S 12:31 0:00 kded [kd= einit] --new-startup which seems to imply that the KDED was started, and ought to be running, although the status of the kded is sleeping for unknown reasons. All of this is on Debian sid/experimental, and there have been numerous libary updates, including for the glibc, so I have been thinking this might be an odd result from some incompatibility, causing me to reinstall the libraries that contain the KDED, namely kdelibs5 kdelibs4c2a which did not help. Attempting to recompile from source and subsequent reinstallation of=20 kdelibs5_4.3.1-1_i386.deb kdelibs5-data_4.3.1-1_all.deb kdelibs5-dbg_4.3.1-1_i386.deb kdelibs5-dev_4.3.1-1_i386.deb kdelibs-bin_4.3.1-1_i386.deb libplasma3_4.3.1-1_i386.deb kdelibs_3.5.10.dfsg.1-2_all.deb kdelibs4c2a_3.5.10.dfsg.1-2_i386.deb kdelibs4-doc_3.5.10.dfsg.1-2_all.deb kdelibs-data_3.5.10.dfsg.1-2_all.deb also did not resolve the issue, in fact kded now refuses to start with=20 kded: symbol lookup error: /usr/lib/libkdeinit_kded.so: undefined s= ymbol: _ZNK18KUniqueApplication9classNameEv which is odd considering that this library is part of the same kdelibs4c2a package that kded itself is packaged in. Somehow the recompilation managed to create binary incompatibility between a library and the corresponding application, it seems. So I've reinstalled the latest pre-packaged versions, which again allows to execute the kded, but KDE does not seem to be able to talk to it. Any input you might have to help with this issue would be appreciated. Best regards, Georg =2D-=20 Georg C. F. Greve http://fsfe.org/about/greve http://blogs.fsfe.org/greve --20090909125700+0200-14346194-16312368152701953 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQCVAwUBSqeJ/Ck9sUy32wQcAQIy8gP+IMZDkMlcS08pKFf+euz5rQ32miVEvoQo +36Yt0OXAcQV9ExBnL+0htXcd99VkCIkB8EikmREspd1UtmEF2Ru4doo2Q2OJJfd CIHz+coFPHZfi8iG9JE+d0wv1Ze1+080p4b+c/kJrLldYoECDqQe5+5o/0C5u8vW I986CaAXyGg= =DYFF -----END PGP SIGNATURE----- --20090909125700+0200-14346194-16312368152701953-- --===============1732310662== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. --===============1732310662==--