Getting "could not start kdeinit5. check the installation" error after upgrading to tumbleweed

Hi,

I upgraded my openSUSE 13.1 to tumbleweed by following the link https://en.opensuse.org/openSUSE:Tumbleweed_upgrade.
I upgraded through online mode. After the upgrade completes, I restarted my machine.
Login screen came and after provided the credentials and hit enter, it gave “could not start kdeinit5. check the installation”. I can login through command line or through fail safe or IceWM. I couldn’t able to solve this issue. Please help with this. Thank you.

Regards,
Sathish

Please post your repo list:

zypper lr -d

If there’s nothing wrong with the repos, running “sudo zypper dup” should help. Probably the upgrade didn’t run fully through…

Although 13.1 is quite old, I’m not sure upgrading that to Tumbleweed is still supported/tested.

Hi all,

Update:

I logged in to the system through IceWM. In the terminal, I gave “startkde” command. It gave the following error.

*startkde: Starting up…
/usr/bin/kdeinit5: symbol lookup error: /usr/lib64/libharfbuzz.so.0: undefined symbol: FT_Get_Var_Blend_Coordinates
startkde: Could not start kdeinit5. Check your installation.

*I’m not able to debug further. Can anyone explain me what is causing this “undefined symbol: FT_Get_Var_Blend_Coordinates” error?

regards,

Sathish V

I ran zypper lr -d command. The list of repos are as below,

Repository priorities are without effect. All enabled repositories share the same priority.

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

–±-----------------±-----------------±--------±----------±--------±---------±-------±---------------------------------------------------------±-------
1 | repo-debug | repo-debug | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/debug |
2 | repo-non-oss | repo-non-oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss |
3 | repo-oss | repo-oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss |
4 | repo-src-non-oss | repo-src-non-oss | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/src-non-oss |
5 | repo-src-oss | repo-src-oss | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/src-oss |
6 | repo-update | repo-update | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |

Yes, Infinality.
It is incompatible to the latest freetype packages in Tumbleweed.

Remove it, and switch the corresponding packages to the standard versions (e.g. via “zypper dup”).

As I understand it, it shouldn’t even be needed any more.

Ok, you are only using the standard repos.

So please run “sudo zypper dup”.
If there are errors or conflicts, please post them for further help.

Please copy paste the output of;
rpm -qi libharfbuzz0

and

zypper ll

Edit:
zypper dup does not suggest any upgrades or holding back updates for any reason?

Hi,

Thanks for the reply guys.

rpm -qi libharfbuzz0 give me,
*
Name : libharfbuzz0
Version : 1.4.2
Release : 1.1
Architecture: x86_64
Install Date: Thu Mar 16 20:46:30 2017
Group : System/Libraries
Size : 660052
License : MIT
Signature : RSA/SHA256, Fri Jan 27 15:57:26 2017, Key ID b88b2fd43dbdc284
Source RPM : harfbuzz-1.4.2-1.1.src.rpm
Build Date : Fri Jan 27 15:57:08 2017
Build Host : cloud117
Relocations : (not relocatable)
Packager : http://bugs.opensuse.org
Vendor : openSUSE
URL : http://www.freedesktop.org/wiki/Software/HarfBuzz
Summary : An OpenType text shaping engine
Description :
HarfBuzz is an OpenType text shaping engine.
Distribution: openSUSE Tumbleweed
*
**zypper ll **gives me,*There are no package locks defined.

***sudo zypper dup **says all are uptodate. How can I uninstall infinality?

Well, how did you install it in the first place?

Maybe there are some packages with infinality in their name?

rpm -qa |grep -i infinality

Maybe you compiled something yourself and installed it to /usr/local/?
Then delete the files manually.

Maybe the output of “ldd /usr/bin/kdeinit5” will provide further clues…

** ldd /usr/bin/kdeinit5*** outputs,
linux-vdso.so.1 (0x00007fff381da000)
libKF5Crash.so.5 => /usr/lib64/libKF5Crash.so.5 (0x00007f01d2ad7000)
libKF5I18n.so.5 => /usr/lib64/libKF5I18n.so.5 (0x00007f01d2886000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f01d2544000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f01d231a000)
libKF5WindowSystem.so.5 => /usr/lib64/libKF5WindowSystem.so.5 (0x00007f01d20cd000)
libQt5Gui.so.5 => /usr/lib64/libQt5Gui.so.5 (0x00007f01d198a000)
libQt5Core.so.5 => /usr/lib64/libQt5Core.so.5 (0x00007f01d12ba000)
libc.so.6 => /lib64/libc.so.6 (0x00007f01d0f15000)
libKF5CoreAddons.so.5 => /usr/lib64/libKF5CoreAddons.so.5 (0x00007f01d0c80000)
libQt5X11Extras.so.5 => /usr/lib64/libQt5X11Extras.so.5 (0x00007f01d0a7b000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f01d06f2000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f01d04ec000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f01d02e8000)
libQt5Widgets.so.5 => /usr/lib64/libQt5Widgets.so.5 (0x00007f01cfa80000)
libxcb-keysyms.so.1 => /usr/lib64/libxcb-keysyms.so.1 (0x00007f01cf87d000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f01cf5e8000)
libz.so.1 => /lib64/libz.so.1 (0x00007f01cf3d2000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f01cf15b000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f01cef19000)
libm.so.6 => /lib64/libm.so.6 (0x00007f01cec06000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f01ce9ef000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f01ce7d1000)
libicui18n.so.57.1 => /usr/lib64/libicui18n.so.57.1 (0x00007f01ce347000)
libicuuc.so.57.1 => /usr/lib64/libicuuc.so.57.1 (0x00007f01cdf96000)
libpcre16.so.0 => /usr/lib64/libpcre16.so.0 (0x00007f01cdd2d000)
libdouble-conversion.so.1 => /usr/lib64/libdouble-conversion.so.1 (0x00007f01cdb1c000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f01cd806000)
librt.so.1 => /lib64/librt.so.1 (0x00007f01cd5fe000)
/lib64/ld-linux-x86-64.so.2 (0x000056470072b000)
libfreetype.so.6 => /usr/local/lib64/libfreetype.so.6 (0x00007f01cd370000)
libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007f01cd14a000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f01ccf20000)
libxcb-dri3.so.0 => /usr/lib64/libxcb-dri3.so.0 (0x00007f01ccd1d000)
libxcb-present.so.0 => /usr/lib64/libxcb-present.so.0 (0x00007f01ccb1a000)
libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x00007f01cc913000)
libxshmfence.so.1 => /usr/lib64/libxshmfence.so.1 (0x00007f01cc70e000)
libglapi.so.0 => /usr/lib64/libglapi.so.0 (0x00007f01cc4df000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f01cc2cd000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f01cc0ca000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f01cbec4000)
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007f01cbcc2000)
libxcb-glx.so.0 => /usr/lib64/libxcb-glx.so.0 (0x00007f01cbaa4000)
libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007f01cb89f000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f01cb699000)
libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f01cb488000)
libicudata.so.57.1 => /usr/lib64/libicudata.so.57.1 (0x00007f01cb287000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f01cb012000)
*
I am not sure how it was installed. This was my family machine.

*rpm -qa |grep -i infinality *outputs nothing.

As suspected:

Remove /usr/local/lib64/libfreetype*, and it should work.
If this is built for 13.1, it is bound to break the Tumbleweed system anyway.

And just to be sure, check what else may be in /usr/local/lib(64):

ls -l /usr/local/lib*

(and probably also /usr/local/bin/ or other subfolders, /usr/local/ overrides the standard locations…)

wow… After removing the /usr/local/lib64/libfreetype* startkde worked. Now I will try to log out and log in again.

ls -l /usr/local/lib* outputs,

*/usr/local/lib:
total 0

/usr/local/lib64:
total 4
drwxr-xr-x 2 root root 4096 Dec 1 13:23 pkgconfig
*

It worked…!!!lol!lol!

Thank you for the help guys… :shame:

Great! :slight_smile:

I would still recommend to look into /usr/local/bin/ as well. If you (or someone else) compiled and installed freetype manually, there likely are some programs in there as well, which now likely won’t work any more (this may cause problems for other software if it tries to run one of those programs).

Also, there may (and likely will) be other remnants of freetype in /usr/local/…