Re: [Security-Discuss] recent security updates for 10.2 broke kde?

* Simon Oosthoek <[email protected]> [2006-06-14 20:14:18 +0200]:

> I haven't looked into this in great detail, but I have some suspicions 
> that yesterday's updates broke something making kde non functional. 
> Symptoms are X being started and then being thrown into the text 
> console. Syslog shows a problem with kdm (code 127). A bit of searching 
> didn't help much, there was a hint (in german) about a problem when 
> upgrading while kde was running (this was on an old version of Suse, so 
> I don't believe this much)
> 
> I re-installed kdm and all that depended on it, but that didn't help. 
> When I tried xdm as alternative, I could log on, but kde didn't start 
> (same problem apparently). I haven't had a chance to try another WM, but 
> I do believe I will have my hands full tomorrow with people complaining 
> about broken systems at work (about 14 pc's), so I hope I will be able 
> to look more focused to a solution or a quick fix!
> 
> I'm planning to upgrade real soon now, but I fear I may be forced by 
> this if I can't fix it :-(
> 
> Any hints and suggestions are very welcome!

Update to the new freetype packages that went out last night.  There was
a severe regression we didn't spot due to caching with freetype that was
causing this problem.  The new packages should correct it.

-- 
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}
mysql> SELECT * FROM users WHERE clue > 0;
Empty set (0.00sec)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFEkFa2LrxeMv7jCtQRAlalAJ9qHRv3nVuXZEFriTieaJV36BiFbACgneJn
f897x8KIHTvGbwE4Swurcbs=
=/kGg
-----END PGP SIGNATURE-----