SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think there's something still out of date on your machine; look for an old libGL. Also, in addition to checking binaries with "ldd", use "readelf -d" (especially if you think something needs to be recompiled). ldd shows all the libraries loaded by a binary, even if they are loaded by some other library. readelf -d only shows the libraries that are directly linked by the binary. If a broken dependency is an indirect one, recompiling the binary isn't going to help.
Yes, kwin is directly linked with libxcb-sync: (on a rebuilt KDE 4.13.3)
Have your run "install-new" to set up the new Glamor. This is obviously glamor-egl that segfaults. I had an issue like this some time ago but unfortunately cannot remember how I fixed it.
I use git packages I make myself for libdrm, mesa, glamor and xf86-video-ati, with -current and once the proper symlink are set, X11 starts well. Maybe you could try that.
For kwin, it's is definitely linked in -current and in AlienBOB's packages to "libxcb-sync.so.0" :
Indeed, that's what I did, as I indeed use AlienBob's packages.
I assumed it was the same for standard -current packages as there are many threads about this, but it seems I was wrong.
Pat just pushed a new mesa package that (hopefully) fixes all of this on a stock -current installation.
That said, there's quite a bit of hardware that nobody on the team has, so if you know that we missed something in the mesa build that your particular hardware needs, we'd like to hear about it.
To be honest, since I compile my own mesa and have been going on for years, I've never checked the options that Slackware's Mesa is compiled with since the first time I did it.
At the time I filled the bug, I thought I just missed something obvious caused by my relative lack of knowledge.
Anyway, I'll do that again if the same situation occurs again.
I am having a very similar problem as the OP with an X segfault but with NVIDIA 173.14.39 propriety driver. I'm not sure whether it was the Xorg upgrade or mesa which caused this behavior. The nouveau driver works. I use slack-current.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,134
Rep:
Since the "upgrade" I've had several minor problems, and, yes, all the up to the minutes files have been installed.
Since the upgrade shutting down the xorg server takes tens seconds or longer before you get back to a command prompt, IF it shuts down at all. Often it just hangs the computer with a black screen and I have to cut the power and restart the computer.
The keyboard, upon starting xorg (startx) has disappeared once. As it didn't work the only way to shut down the computer was to the cut the power (reset).
The mouse, upon starting xorg, has disappeared 3 times, and, BTW, Ctrl, Alt, Backspace no longer works, so, again, it was necessary to reset the computer.
A few times xorg has refused to start, with both KDE and Xfce, and issued this error message:
Quote:
hostname:Hostname lookup failure
XAuth: file /home/username/.serverauth.955 does not exist
(EE)
Fatal server error:
(EE) cannot move old log file "/var/log/Xorg.0.log"
to "/var/log/Xorg.0.log.old"
(EE)
(EE)
Please consult The X.Org Foundation Support at http://wiki.x.org
for help
(EE)
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
Finally, for a second time, I ran "upgradepkg --reinstall --install-new" on all the "upgraded" packages and so far so good, but it is still very early in the day.
Last edited by cwizardone; 07-21-2014 at 09:04 AM.
Reason: Typo.
I am having a very similar problem as the OP with an X segfault but with NVIDIA 173.14.39 propriety driver. I'm not sure whether it was the Xorg upgrade or mesa which caused this behavior. The nouveau driver works. I use slack-current.
NVidia's proprietary driver does not use glamor, libdrm or mesa, so I suggest checking if a newer version, support xorg-server 1.5.2, is available and installing it.
Thanks rvdboom, I did suspect it was xorg. Nvidia announced 173.14.39 would be the final release of the 173xx legacy line. Interestingly, they released in response to an ABI mismatch with xorg-1.14.x; however, they said it would be good for xorg-1.15 as well. It looks like a return to slack 14.1 for me then. Odd that I haven't found anyone else with the same problem though.
cwizardone, I'm not sure if you posted in response to me or not, but I did try reinstalling the upgrades though with no success. Nonetheless, thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
