From kde-core-devel  Thu Mar 01 09:01:45 2007
From: Thomas Zander <zander () kde ! org>
Date: Thu, 01 Mar 2007 09:01:45 +0000
To: kde-core-devel
Subject: kded & qt-bleeding borkd
Message-Id: <200703011001.46339.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=117273963026361
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1464775.BYZB6Jzauj"

--nextPart1464775.BYZB6Jzauj
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I'm not sure if people are interrested in this bugreport; but I was a bit=20
frustrated that I can't try if a bug is still in qt-bleeding (rsync last=20
night)...

After a clean compile of trunk and qt-bleeding-x11 all update last night I=
=20
start with an empty KDEHOME and get a continues "Waiting for already runnin=
g=20
kbuildsycoca to finish."
Starting krita I get the same, and after a timeout I get a crash in kded.

Since I share the sources dirs between my beta and my trunk compile trees, =
I'm=20
pretty sure its a qt-bleeding bug. basically since thats the only thing tha=
ts=20
different.  My instinct tells me its probably a dbus issue.  Anyone able to=
=20
look into this?
Please let me know if/when this is fixed :)

=2D-=20
Thomas Zander

--nextPart1464775.BYZB6Jzauj
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBF5pZ6CojCW6H2z/QRAsaiAKCuHadXEvRxnMXBR9EQ9hLemkt/FgCgxGPD
JQVwTLOJGn0Z03U7b189KMY=
=rwji
-----END PGP SIGNATURE-----

--nextPart1464775.BYZB6Jzauj--