X11 20161031 updates breaking Slackware-14.1

414N · 11-02-2016, 04:48 AM

Greetings,
I just installed the aforementioned updates on my working place Slackware 14.1 box using slackpkg and had some xcb-related issues, so I'm sharing this hoping to help someone having a similar experience.
After a system restart (to make sure the new version of the kernel was picked up), KDM wouldn't automatically startup (I'm using runlevel 4 by default).
After a quick investigation, the first error I saw in the logs was this

Code:

undefined symbol "xcb_wait_for_reply64"

, which led me thinking there were errors related to libxcb. As I later found out, my slackpkg run didn't find the libxcb-1.11 version in the patches/ directory, so I was still using libxcb-1.9.2.
After manually updating the package, KDM started but kwin crashed as soon as the desktop appeared, rendering all windows without borders and refusing any keyboard input in any window. Turns out kwin was searching for the libxcb-sync.so.0 shared library, while the recent patches install libxcb-sync.so.1. I had no time to recompile all of kwin and KDE-related packages that may need that older version, so I went with the good-ol' symlink trick:

Code:

ln -s /usr/lib64/libxcb-sync.so.1 /usr/lib64/libxcb-sync.so.0

and this brought me back my desktop.

Anyone had the same issue?

phenixia2003 · 11-02-2016, 08:27 AM

Hello,

I can't reproduce this on a 14.1 VM. Maybe there's something wrong on your side (missing package, or something like that).

the attached file packages-list-141-2.txt contains the (sorted) list of package installed on the VM on which I tried to reproduce your issue.

--
SeB

phenixia2003 · 11-02-2016, 10:51 AM

Hello,

Quote:

Originally Posted by 414N

Turns out kwin was searching for the libxcb-sync.so.0 shared library, while the recent patches install libxcb-sync.so.1.

I guess that you're talking about kwin/kde5 since kwin/kde4 from 14.1 is not linked to libxcb-sync.so :

Code:

$ ldd /usr/bin/kwin|grep libxcb-sync
<nothing>

$ tar xf kwin-5.7.4-x86_64-1alien.txz -C kwin
ldd kwin/usr/bin/kwin_x11|grep libxcb-sync
libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x00007f9054512000)

Edit:

I think I understood your issue. You don't use kde from 14.1 but alienbob kde 4.14.3 for 14.1 :

Code:

$ wget http://alien.slackbook.org/ktown/14.1/latest/x86_64/kde/kde-workspace-4.11.17-x86_64-1alien.txz
$ mkdir kde-workspace

$ tar xf kde-workspace-4.11.17-x86_64-1alien.txz -C kde-workspace

$ ldd kde-workspace/usr/bin/kwin |grep libxcb-sync
        libxcb-sync.so.0 => /usr/lib64/libxcb-sync.so.0 (0x00007fcee3c10000)

--
SeB

414N · 11-02-2016, 03:26 PM

Yes, apologies for not telling earlier but I didn't think about it when I first posted: I'm using Alien's "ktown" KDE4 packages instead of the default ones coming in Slackware-14.1.
Guess Alien's packages should be recompiled then, after the recent patches...

dgrames · 11-02-2016, 07:49 PM

Thanks 414N, your link fix did the trick for me.
Thanks, Don

Skaendo · 11-02-2016, 08:30 PM

Excuse my ignorance here, but what is the difference between Eric's KDE4 packages and the ones that come in Slack?

bassmadrigal · 11-02-2016, 11:11 PM

Quote:

Originally Posted by Skaendo

Excuse my ignorance here, but what is the difference between Eric's KDE4 packages and the ones that come in Slack?

During the 14.2 development, Eric released updated 14.1 packages for KDE4. It bumped the stock KDE 4.10.5 to 4.14.3.

duaneP777 · 11-06-2016, 09:01 AM

I just ran into the libxcb issue this morning when updating my Slackware64-14.1 laptop. In my case, I found I had aliens libxcb-1.9.1 installed, and pulling libxcb-1.11.1 from a slackware mirror, removepkg the 1.9.1 and installing 1.11.1 fixed the problem - Thanks 414N!

I didn't have the KDE issue because I use XFCE4.

I do use multilib and Slackpkg+. Apparently, aliens mirror does not have the updated libxcb yet, which caused the problem for me.

Alien Bob · 11-06-2016, 03:06 PM

Quote:

Originally Posted by duaneP777

I just ran into the libxcb issue this morning when updating my Slackware64-14.1 laptop. In my case, I found I had aliens libxcb-1.9.1 installed, and pulling libxcb-1.11.1 from a slackware mirror, removepkg the 1.9.1 and installing 1.11.1 fixed the problem - Thanks 414N!

I didn't have the KDE issue because I use XFCE4.

I do use multilib and Slackpkg+. Apparently, aliens mirror does not have the updated libxcb yet, which caused the problem for me.

You're correct. My custom libxcb package for Slackware 14.1 is no longer needed. I carried a modified package for a long time, compiled with additional configuration parameters "--enable-xinput --enable-xkb" as required by SDDM. The new libxcb package in the /patches/packages section of Slackware 14.1 has those configure parameters applied, which is probably caused by Pat having copied the configure script from Slackware 14.2 or -current.

Consequently I have removed my custom libxcb package from the Slackware 14.1 section of my own repository. Next time you run "slackpkg update ; slackpkg upgrade-all" (using slackpkg+ extension) you will not be bothered by my old package.

duaneP777 · 11-06-2016, 04:52 PM

Quote:

You're correct. My custom libxcb package for Slackware 14.1 is no longer needed. I carried a modified package for a long time, compiled with additional configuration parameters "--enable-xinput --enable-xkb" as required by SDDM. The new libxcb package in the /patches/packages section of Slackware 14.1 has those configure parameters applied, which is probably caused by Pat having copied the configure script from Slackware 14.2 or -current.

Consequently I have removed my custom libxcb package from the Slackware 14.1 section of my own repository. Next time you run "slackpkg update ; slackpkg upgrade-all" (using slackpkg+ extension) you will not be bothered by my old package.
__________________
--
Eric Hameleers

It is good to know the full story. Thanks, AlienBob!