Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
08-04-2010, 08:40 AM
|
#1
|
Member
Registered: May 2004
Distribution: Slackware.
Posts: 323
Rep:
|
Call to lnusertemp failed (temp directories full)
I had a fresh install of Slackware 13.1 up and running. I was looking to use an app which could only run on a gnome distro. So I installed gnomeslackbuild. Ran into dependency hell so I gave up the ghost and decided to reinstall.
Re-install resulted in a message "Call to lnusertemp failed(temporary directories full).
Had this before a different machine and sorted with another install at the time.
Tried this but it keeps coming up with the same message. (4 installs later).
Quote:
xset: bad font path element (#23) possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address
Error: Can not create link from "/home/tommy/.kde/cache-zepp" to "var/tmp/kdecache-tommy"
Error: Can not create link from "/home/tommy/.kde/cache-zepp" to "var/tmp/kdecache-tommyIYOyQZ"
startkde: Call to lnusertemp failed (temporary directories full?). Check your installation
|
Any ideas appreciated?
Last edited by tamtam; 08-09-2010 at 05:16 PM.
|
|
|
08-04-2010, 10:47 AM
|
#2
|
Member
Registered: May 2004
Distribution: Slackware.
Posts: 323
Original Poster
Rep:
|
Okay, I went back to Slackware 13. Tried to install and it came back with the same error. I have had Slackware 13 running on this PC since Slack 13 was released. Done a clean install of 13.1 had it running for a while, disliked my installation since installing gnomeslackbuild. Done another clean install. But Why can't I run KDE.
Why does it fail now. Can't get KDE up and running. Can't be a bad burn, I burned both Slackware 13 and 13.1 today. No indication during the install process of a problem. Been running Slackware since verion 10 and never had this problem, well only once and that was not on this PC.
|
|
|
08-04-2010, 01:58 PM
|
#3
|
Moderator
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=15, FreeBSD_12{.0|.1}
Posts: 6,315
|
Quote:
Originally Posted by tamtam
Why does it fail now. Can't get KDE up and running. Can't be a bad burn, I burned both Slackware 13 and 13.1 today.
|
I would guess that you are preserving your home directory or at least the same partition scheme from the "bad" system?
I am not a KDE user so cant be much help with specifics, but things to check:
1. Delete anything like ~/.kde/... in the user home directories.
2. Is /var on a separate partition? If so, check if /var/tmp is actually full/permissions...
3. Force empty of existing partitions before reinstall.
Can you post your partition scheme and how you assign them during reinstall.
Last edited by astrogeek; 08-04-2010 at 02:46 PM.
|
|
|
08-04-2010, 04:47 PM
|
#4
|
Member
Registered: May 2004
Distribution: Slackware.
Posts: 323
Original Poster
Rep:
|
Suspect it may be the CD/DVD Drive that maybe suspect.
partition is simple
20 G /Root
2 G /Swap
210 G /Home
All formatted first time ext3, even tried ext4 file systems.
I have a other partition which is not included in the fstab, this contains permanent data and is not included during set up.
|
|
|
08-09-2010, 05:29 PM
|
#5
|
Member
Registered: May 2004
Distribution: Slackware.
Posts: 323
Original Poster
Rep:
|
Just in case anyone else comes across a similar situation. The case where despite multiple burns and installs to my hard disk I was still presented with the "Call to lnusertemp failed (temp directories full)" full message retaining to missing font directories.
The fault. I was installing to the same partition of my hard drive every time. There must have been some faulty splatters or some thing.
The fix. I re-partitioned the hard drive. originally the first 20 gigs was my root partition. I moved root to beyond the scope of the first 20 Gigs. Here is my partition now.
Quote:
Device Boot Start End Blocks Id System
/dev/sdb1 1 2432 19530752 83 Linux (ubuntu /root)
/dev/sdb2 2432 60802 468853761 5 Extended (possible cause area)
/dev/sdb5 2432 14590 97654784 83 Linux (ubuntu /home)
/dev/sdb6 14590 14736 1170432 82 Linux swap / Solaris
/dev/sdb7 14736 17775 24413184 83 Linux (slackware root)
/dev/sdb8 17775 39659 175779840 83 Linux (slackware /home)
/dev/sdb9 39659 60802 169831424 83 Linux (extra paprtition)
|
Yes, I put ubuntu on the first partition. It installed and is up and running.
The fix is to move install of root to another partition.
|
|
|
06-13-2021, 08:54 PM
|
#6
|
LQ Newbie
Registered: Jun 2007
Location: Baltimore, Md
Distribution: RHEL AS5
Posts: 6
Rep:
|
I found this while searching for this very same problem when a RHEL7 VM that had worked for over a year, suddenly developed this problem. Every reboot and subsequent login as root displayed a small white popup stating: "Call to lnusertemp failed (temp directories full)". Other user accounts could login without a problem.
With careful experimentation, I found that, for good reason, I'd recently added the following to /root/.bashrc:
export TMPDIR=~/tmp
The problem with doing that, was /root/tmp did not exist. Either adding the target directory or commenting that line out immediately solved the problem on subsequent boots. Other testing proved that the same problem could be foisted upon plain user-accounts too.
Additionally, for the post on August 4th 2020: this message:
Error: Can not create link from "/home/tommy/.kde/cache-zepp" to "var/tmp/kdecache-tommy"
Might be indicative of the problem, too. The target of the link seems to be stating 'var', vice '/var'. Not having their target environment from 11 years ago, that is the one thing which jumps out at me.
So, either create the target directory, or don't put that in .bashrc.
Good luck!
|
|
|
All times are GMT -5. The time now is 05:50 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|