Hey all,

I recently ran...

slackpkg update
slackpkg upgrade-all
slackpkg install-new

Everything seemed okay until I rebooted. The login screen seems different from last time, apart from that I was able to login but when I try and run 'startx' I received the following error message...

xauth: file /home/user/.serverauth.767 does not exist

/usr/bin/X: error while loading shared libraries: libxshmfence.so.1: cannot open shard object file: No such file or directory
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Can anyone help me with this error? I am 99% certain the update I recently ran has caused this as it was working fine before that.

I am a noob with Linux in general but am trying to learn more and get better.

Thanks.

libxshmfence.so.1 is installed by package libxshmfence-1.1 that is shipped only in Slackware current at time of writing.

In a Slackware version 14.1 no software should require this as a dependency, so you probably have a mix of packages coming from Slackware current and Slackware 14.1, which is bad.

Maybe you uncommented a mirror for Slackware current instead of Slackware14.1 in /etc/slackpkg/mirrors?

Please confirm that (or not) and tell us what are your Slackware version and architecture (32 or 64 bit).

1 members found this post helpful.

Damn I think you are probably correct. A collegue normally gives me the .iso file and my mirror is pointing to the file in my local directory.

Should I just uncomment one of the ftp mirrors for Slackware14.1 and try updating again or has the damage already been done?

EDIT: I am using 14.1 32 bit

You can try to update again with a good mirror, issuing also "slackpkg clean-system" to remove packages possibly shipped in current but not in 14.1 (assuming that you have only genuine Slackware packages. Else in the list of packages that should be removed uncheck only those you want to keep that are *not* shipped in Slackware).

If that doesn't go well, reinstall Slackware 14.1

1 members found this post helpful.

Also note that the correct order of commands is:
To make sure you cater for any new dependencies that might have been added in an updated version of a package.

2 members found this post helpful.

I just discovered this same problem tonight when working on my Slackware current machine. I haven't started the X server since upgrading to current and had no idea that it wasn't functioning correctly.

But, I followed the advice in the above posts and everything came up the way it should. Hail Bob!

1 members found this post helpful.

Don't forget to at least look at the package list from a run of:

slackpkg clean-system

Sometimes, removing packages is necessary as well...

2 members found this post helpful.

The first time I run slackpkg on a system I run slackpkg update gpg then the following commands.

2 members found this post helpful.

hmm looks like I am having also the exact same issue.

I had started http://www.linuxquestions.org/questi...05#post5310605

but will move over here. 64 bit clean install i update and bang startx borked exact same error.

Rob

Can you try adding "915.modeset=1" to your kernel line in lilo or grub conf?

okay just saved that to a text file in my /root going to just keep it at stable and upgrade all if that borks will try above. if that doesn't will adjust mirror to current and try again and if it borks try the above fix and report back

okay stable didn't bork it i can tell as not only can't i startx where I still have an xsession started (xcfe here) I can't launch a terminal a browser nada with a window of anykind)

now changing mirror to current and working to break it again

just completed
slackpkg update
slackpkg install-new

now onto
slackpkg upgrade-all

okay I am completely upgraded to current and don't think there is going to be an issue this time.

I think I made a 24 hour no sleep 3am missed slackpkg install-new which broke some dependencies

but going to reboot to make sure. and just in case already appended your suggest to kernel options in lilo and touched lilo so I can get back to here in case all else fails

issue resolved on my end that HAD to be the culprit. will promise to repeat 50 RTFM's before bedtime tonight