kioslaves and asynchronous kpasswdserver calls

[Michael Leupold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I committed a new asynchronous interface for kpasswdserver last week. It 
fixes timeout issues if the user doesn't answer the password dialog within 
the D-Bus timeout interval. Changes on the clientside went directly into 
KIO::SlaveBase so all kioslaves can directly benefit from the changes - as 
long as they have a QCoreApplication (the kioslave waits for kpasswdserver's 
response in a QEventLoop).

Right now I'm adding QCoreApplication to all kioslaves in trunk (only those 
that use kpasswdserver; excluding extragear and playground; I'll notify the 
maintainers separately). I'm trying to be as cautious as possible, 
testdriving each of them. If you still notice some regression, please tell 
me so I can try to figure out what's going on.

Regards,
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJ7HWAlfpzINIAlVsRAnq9AJ9141Gur2Mon2BA8JVla21vR6QKwQCdFiDB
PAMwI3BWdiUVntxKbZfS0qs=
=ihZ0
-----END PGP SIGNATURE-----