Page 1 of 1

gdm could not write a new authorization entry to disk

Posted: 2. May 2017, 21:12
by tharpa
I think the title sums it up. I got to a command line.

What should I do from there?

Solved:Re: gdm could not write a new authorization entry to

Posted: 2. May 2017, 21:32
by tharpa

Code: Select all

sudo spi --clean
did the trick.

Re: gdm could not write a new authorization entry to disk

Posted: 2. May 2017, 21:55
by gapan
So your hard drive was full?

Re: gdm could not write a new authorization entry to disk

Posted: 7. May 2017, 20:11
by tharpa
gapan wrote:So your hard drive was full?
No, not at all. But yet, it temporarily fixed the problem.

I have a LibreOffice Calc spreadsheet with a lot of chained formulas. When I do work on that, is when the problem recurs.

Today, sudo spi --clean is not helping.

The earliest problem message I can see on the terminal is /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf: line 53: echo: write error: No space left on device.

Re: gdm could not write a new authorization entry to disk

Posted: 7. May 2017, 20:22
by gapan
tharpa wrote:The earliest problem message I can see on the terminal is /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf: line 53: echo: write error: No space left on device.
So, your hard drive is full.

[SOLVED]gdm could not write a new authorization entry to dis

Posted: 7. May 2017, 21:16
by tharpa
gapan wrote: So, your hard drive is full.
Thanks. I got out of the immediate jam by

Code: Select all

find /tmp -ctime +10 -exec rm -rf {} +
But my sda1, which is the problem, is still up to 90% of 15 G.

I want to find what is using up my sda1 space. This seems to be a fairly common question on the web, but I cannot find any straight answers. The Disk Usage Analyzer seems to look at the entire file system, but I do not see any way of using it to find out info about sda1.

Edit:
OK, the problem seems to be resolved for now. perbh at linuxquestions (slackware) suggested

Code: Select all

/usr/bin/find /tmp -mindepth 1 -maxdepth 1 -print0 | /usr/bin/xargs -0r /bin/rm -rf
Now my sda1 is only 66% used, so the problem appears to be resolved.