Here is my diary entry for the solution I found when I had problems like this. 01 Sep 2017 Today's Contents Linux <#01Sep2017Linux> Back to Table Of Contents <#TableOfContents> Linux .xsession-errors is still causing problems. Xserver - X Window System display server <https://www.x.org/archive/X11R6.8.0/doc/Xserver.1.html>. Perhaps the audit level has been mis-set. Should be level 1. Can't figure out if it is set, or where it is set. Interesting file to look at is/var/log/Xorg.0.log. Using config file /etc/Xaa/xorg.conf. Maybe I should be looking at kde. Huge .xsession-errors <https://ubuntuforums.org/showthread.php?t=1517991>. Here is one suggestion. Had the same problem with 11GB .xsession-errors. Fixed it with a solution I found to disable the recent history too. rm .xsession-errors touch .xsession-errors sudo chattr -i .xsession-errors Simply delete the file. Create an empty file. Set the immutable attribute. Which makes the file protected against writing and deleting. Nothing can be logged. Note that until you logout the file space deleted is not unallocated because the file is being held open. I did it. If I break X when I reboot, then I don't know what I will do. 38: rm -f .xsession-errors 39: touch .xsession-errors 40: lsattr .xsession-errors -------------e-- .xsession-errors 41: sudo chattr -i .xsession-errors [sudo] password for steve: 42: lsattr .xsession-errors -------------e-- .xsession-errors 43: sudo chattr +i .xsession-errors 44: lsattr .xsession-errors ----i--------e-- .xsession-errors 45: rm .xsession-errors rm: remove write-protected regular empty file '.xsession-errors'? n I rebooted, and I think it worked. 6: lsof -nP | grep 'deleted' 7: df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 19478204 16789308 1676416 91% / 9: dir -l .xsession-errors -rw-rw-r-- 1 steve steve 0 Sep 1 22:47 .xsession-errors 10: lsattr .xsession-errors ----i--------e-- .xsession-errors The following is from the man page ofchattr. A file with the 'i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file and no data can be written to the file. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute. On 7/29/2018 4:51 PM, Richard Klein wrote:

Now it's cleared itself up; I've got 443.9GB free space in my Home folder.  I guess it just needed some time to refresh the filesystem?

On Sun, Jul 29, 2018 at 4:25 PM Richard Klein <rich@richardklein.org <mailto:rich@richardklein.org>> wrote:

I found today that my Home folder is full.  The culprit seems to have been a roughly 1/2 terabyte .xsession-errors file.  I deleted it, but 'emptying the trash' didn't seem to be clearing any space.  I found that everything I'd thought I'd deleted recently seemed to still be sitting in $uname/.local/share/Trash.  I selected everything in that folder and typed shift+delete.  Now nothing shows in the Trash folder, but my Home folder is still full.  I rebooted, and that's still the case.  What now?

[code] Debian-Precision:~$ uname -a Linux Debian-Precision 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux [/code]

-- Rich

_______________________________________________ WLUG mailing list -- wlug@lists.wlug.org To unsubscribe send an email to wlug-leave@lists.wlug.org

-- Steven Greenberg Email: steve@ssgreenberg.name 251 Holland Rd. Phone: (774)241-0095 Fiskdale, Massachusetts 01518-1231 Web: www.ssgreenberg.name Other Email: s.greenberg@ieee.org ssg@alum.mit.edu

And after using the computer for another hour or two yesterday, it locked up; the pointer still tracked the mouse, but I couldn't click on anything or get any response from the keyboard. I got a new SSD last week that's waiting to be installed, so I'll probably punt and do a fresh OS install when I do that. On Mon, Jul 30, 2018 at 1:21 PM brad <bkn@ithryn.net> wrote:

On Jul 29, 2018, at 16:51, Richard Klein <rich@richardklein.org> wrote:

Now it's cleared itself up; I've got 443.9GB free space in my Home folder.

I guess it just needed some time to refresh the filesystem?

sort of …

Some — perhaps all — filesystems will not actually delete the data if there is a running process which has the file open. In your case ~/.xsession-errors is a file that X uses to log errors, so if you were running a GUI that file probably will not get deleted until X restarts.

On Sun, Jul 29, 2018 at 4:25 PM Richard Klein <rich@richardklein.org> wrote:

...

I found today that my Home folder is full. The culprit seems to have been a roughly 1/2 terabyte .xsession-errors file. I deleted it, but 'emptying the trash' didn't seem to be clearing any space. I found that everything I'd thought I'd deleted recently seemed to still be sitting in $uname/.local/share/Trash. I selected everything in that folder and typed shift+delete. Now nothing shows in the Trash folder, but my Home folder is still full. I rebooted, and that's still the case. What now?

[code] Debian-Precision:~$ uname -a Linux Debian-Precision 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux [/code]

-- Rich

_______________________________________________ WLUG mailing list -- wlug@lists.wlug.org To unsubscribe send an email to wlug-leave@lists.wlug.org