call to lnusertemp failed (temporary directories full ?).Check your installation

I have had Opensuse 13.164 bits for awhile. Very stable machine, never had a problem.
The machine is not connected to the Internet : I work on this machine and I know for experience that often, just the updates can stuff up everything.
Occasionally, I need to install new sw and I do connect, but that’s rare : I haven’t done it for months.
A couple of days ago I installed Xilinx sw (an FPGA provider) from USB key. All went well. A few days later I got a license for the
sw and everything seemed ok. Powered off, logged in a couple of days later and got the error message above.

From reading other posts about this, I understand that the message is a symptom for some writing permissions wrong. I have no
idea what could have changed them. Maybe during the installation I used root and some unintended commands were pasted in the root window.
Also, there is plenty of space in the hard drive : df -a / returns 34% use
I can log in as root and I can see my files in my /home/enzo

Some post suggested to check permissions in /home/enzo/.kde4

ls -l /home/enzo/.kde4
total 8
drwxr-xr-x 2 enzo users 4096 Apr 24  2014 Autostart
lrwxrwxrwx 1 enzo users   22 Apr 24  2014 cache-linux-tv3i -> /var/tmp/kdecache-enzo
drwx------ 5 enzo users 4096 Apr 24  2014 share
lrwxrwxrwx 1 enzo users   17 Apr 24  2014 socket-linux-tv3i -> /tmp/ksocket-enzo
lrwxrwxrwx 1 enzo users   13 Apr 24  2014 tmp-linux-tv3i -> /tmp/kde-enzo

The share directory sticks out.

Also /var/tmp

ls -l /var/tmp/
total 56
drwxrwxrwx 2 enzo users 4096 Nov 17  2014 .flexlm
drwx------ 2 root root  4096 Sep 13  2015 TmpDir.BtNIXl
drwx------ 4 enzo users 4096 Sep  2 22:31 kdecache-enzo
drwx------ 2 kdm  kdm   4096 Apr 24  2014 kdecache-kdm
drwx------ 4 root root  4096 Sep  4 12:20 kdecache-root
drwx------ 3 root root  4096 Dec  3  2015 systemd-private-3XvW9d
drwx------ 3 root root  4096 Apr  6  2015 systemd-private-7lmz6p
drwx------ 3 root root  4096 Jan 27  2015 systemd-private-cprk6r
drwx------ 3 root root  4096 Mar 15 09:59 systemd-private-jkSRAb
drwx------ 3 root root  4096 Sep  7  2015 systemd-private-xktFZ5
drwxr-xr-x 3 root root  4096 Apr 24  2014 var
drwx------ 4 root root  4096 Jan 22  2015 zypp.d3TOlf
drwx------ 4 root root  4096 Sep 13  2015 zypp.fUoRWZ
drwx------ 4 root root  4096 Oct  5  2015 zypp.zrmb1d

Again kdecache-enzo

Any ideas how to fix it ? A guess at why it happened ?

Thank you.

I have found this:
http://askubuntu.com/questions/138641/message-call-to-lnusertemp-failed-temporary-directories-full-check-your-ins

So far I tried (from the root login) :

chown -R enzo /home/enzo/.kde4
chown -R enzo /var/tmp/kdecache-enzo

They had no effect (I still could not log in).
I also tried to rename /home/enzo/.kde4 hoping it would be re-created, as suggested. It did get re-created, but I still
could not log in.

I also saw this one :
https://forums.opensuse.org/showthread.php/493266-call-to-lnusertemp-failed-(temporary-directories-full-)-Check-your-installation/page2

I tried

chown -R enzo:users /home/enzo/

And it didn’t work either.

Please help.

I found some very interesting errors here :

cat /home/enzo/.xsession-errors-\:0
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
/usr/bin/kde4-config: symbol lookup error: /usr/lib64/libQtDBus.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
/usr/bin/kde4-migrate: symbol lookup error: /usr/bin/kde4-migrate: undefined symbol: _ZN9QListData11detach_growEPii
kde4-config: symbol lookup error: /usr/lib64/libQtDBus.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
kde4-config: symbol lookup error: /usr/lib64/libQtDBus.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
kde4-config: symbol lookup error: /usr/lib64/libQtDBus.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
kde4-config: symbol lookup error: /usr/lib64/libQtDBus.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
startkde: ERROR: Could not locate lnusertemp in 
/usr/bin/startkde: line 254: : command not found
startkde: Call to lnusertemp failed (temporary directories full?). Check your installation.

This is very different from the same file in /root :

cat /home/enzo/.xsession-errors-\:0
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
startkde: Starting up...
.......

Note how startkde fails in for my directory but not root.
Any clues ? This points to the failure. Some symbol is undefined but why not when logging in as root ?

Check space on root partition and home

root files and personal are not used for the same reasons check the dates

I assume that GUI starts but the program fails right??? run program from command line to get detailed error.

I have root and home under the same partition. I know that this is not supposed to happen and
I probably won’t do it again,but that’s the way it is at the moment.
Doing df -a / gives 34% used

root files and personal are not used for the same reasons check the dates

The dates of which files exactly ?

I assume that GUI starts but the program fails right???

Yes, the machine boots and gets to the login screen. If I login as root, no problem. If I log in
as me, it stops with a black screen an a small window containing the message “call to lnusertemp failed…etc.”

run program from command line to get detailed error.

Which program ? startkde ? I can only run it from root and it works fine as I can login.
I know the errors that KDE stumbles upon, they are in the in the .xsession-errors-:0 file.
They only happen if I log in as me,. If I log in as root, the .xsession-errors-:0 file contains
no errors.

I suspect some corruption in the /home.
Question, can I run a fsck if root and /home share the same partition ?

Solved : it was sourcing the recommended Xilinx settings from my .bashrc instead of doing them manually.
Xilinx provides a setting.sh to source before using their tools. But it somehow interferes with starting KDE
if put in the .bashrc file .

BTW, How do I mark a thread as SOLVED ?

By posting something like you did :wink:

BTW, next time do not say things like: “Doing df -a / gives 34% used”, but SHOW what you did and got by copy/paste of the prompt, the command, the output and the next prompt between CODE tags in a post. Example:

henk@boven:~> df -h
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/sda2           20G     5,9G   13G  32% /
devtmpfs           985M      40K  985M   1% /dev
tmpfs              999M      84K  999M   1% /dev/shm
tmpfs              999M      11M  989M   2% /run
tmpfs              999M        0  999M   0% /sys/fs/cgroup
tmpfs              999M      11M  989M   2% /var/lock
tmpfs              999M      11M  989M   2% /var/run
/dev/sda3           92G      69G   23G  76% /home
henk@boven:~>

Then people can see more, even more the you can imagine. E.g. they could have seen that you do not have a separate /home. A fact that now came only at the end of the story. :frowning: