SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.
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?
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 :-)
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?
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.