[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Testing, "could not start kdeinit. check your installation" since yesterdays updates



Yup, get the libXft 2.1.7 library and replace that shared object library as
below and it will work, it is only a hack but it works..

I fixed this by using the lib from a box with libXft2 2.1.7 instead of
2.1.8.2-3.

# mv libXft.so.2.1.2 libXft.so.2.1.2-2.1.8.2-3
# scp root@box:/usr/lib/libXft.so.2.1.2 .

Then everything worked again.

Note: I did grab the 2.1.7 deb but when I did the apt-get install / upgrade,
it wiped it out, very nasty!  The worst part is people probably will not see
this until they reboot!

-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz@adelphia.net] 
Sent: Sunday, February 19, 2006 6:20 AM
To: 'debian-changes@lists.debian.org'
Subject: Latest upgrade breaks KDE in Etch?

# startkde
kdeinit: symbol lookup error: /usr/lib/libXft.so.2: undefined symbol:
FT_GlyphSlot_Embolden

Using mirrors.kernel.org as my repo, any way to fix this issue?

# nm -D  libXft.so.2 |grep Glyph
         U FT_GlyphSlot_Embolden



-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org



-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Magnus Pedersen
Sent: Sunday, February 19, 2006 7:16 AM
To: debian-user@lists.debian.org
Subject: Testing, "could not start kdeinit. check your installation" since
yesterdays updates

I am seeing this on two machines.

It dosn't matter if I use kdm or startx, I get that error in a small 
window just before the kde-splasscreen. And my syslog is filled with 
dbuserrors like this:

Feb 19 12:29:35 localhost hcid[6842]: Can't send D-BUS inquiry start 
message

Whats up anyone?

/Magnus
Sorry for my poor english, it is not my first language.


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org





Reply to: