With the new X11 packages in slackware-current, X11 starts but KDE's window manager kwin fails to start.
Apparently, the current kwin binary is expecting a libxcb-sync.so.0 symlink that is no longer created.
So either kwin must be rebuild or add this symlink to libxcb-sync.so.1.0.0.

check out Aliens Bog http://alien.slackbook.org/blog/ Just updated KDE for current

You could always create it with ln -sv

Saying that it could solve problems some time, I don't think that's a goog idea. Version changes in shared lib means the maintainer of the lib think there is in-compatible changes in the ABI or API, apps should recompile with the new one.

Hello guys,

Even on my -current box, on Alien's KDE 4.12.5 after the latest upgrades I can login to X but once in a KDE session, there are no title bars, can't move or resize any app. I tried reverting to Compiz as the WM from settings but same issue. Going back to Kwin threw an error that the Kwin WM can't be started. (BTW I did an install-new, then an upgrade-all.)
I tried upgrading KDE to Alien's 4.13.2 but it reproduces same error.

Any suggestions on what needs to be done as of now?

Regards.

This is a temporary fix. As root:-
AlienBob has now released KDE 4.13.3 with an update to fix this problem.

1 members found this post helpful.

Thanks a lot buddy, that fixes the issue for now.
So if I update KDE to 4.13.3, do I need to revert the changes done in this symlinking?

Regards.

Yes, once the problem is fixed correctly, you need to delete the symlink you created.

To elaborate a bit on the problem with creating such a symlink, it's generally not a problem if the app linking the library isn't using any function that was removed from or changed in the API -- in other words, if the only reason for the bump in the shared object major version (e.g. libwhatever.so.1 --> libwhatever.so.2) was something *added* to the API, then you shouldn't see any problems at all with a symlink. However, if there was a *change* to the API (e.g. a function that used to expect one argument now expects two arguments) or a *removal* from the API, then anything linking that library which uses the changed/removed API is going to go apeshit - that's why it's a bad idea to fake the old library version with a symlink unless you happen to know that it's not a bad idea :-)

3 members found this post helpful.

Ah, it makes good sense. Thanks for taking time in explaining, Robby.

Regards.

Far better explanation than I could have given :-). All I know it's not a particularly good fix (certainly not a permanent one) but can get you out of a hole now and again.

I have the same problem PrinceCruise described above when I upgraded KDE to 4.13.3 using AlienBob's packages. I also lost my virtual desktops and cannot create new ones. I added the symlink as described above, but no joy. Did not work for me. What am I doing wrong?

The fix for my post above was to download and install AlienBob's newest kde-workspace package (kde-workspace-4.11.11-i486-2alien.txz) from his K-Town repository. Now, all is well and joy abounds.

My -current install was in shambles after the crossroads of Pat's xorg and Eric's KDE updates. I chose to take the path of least resistance. Un-blacklisted the "alien" in /etc/slackpkg/blacklist. Ran slackpkg update, install-new, upgrade-all today. This effectively got me the latest kernel update, rolled KDE back to 4.10.5 and now all is well. Presumably Pat will upgrade the KDE version in current in the near future.

Praise Bob

The latest KDE in my ktown repository has been fine for days. I got the fixes in fast as several people have been confirming here and on my blog. No reason to revert to the Slackware originals.

Eric

1 members found this post helpful.

Great. I've been rather harried for a week or so and have not checked your blog. Will give them a shot this weekend. Always been a fan of your work.