Request for explanation of error message

[Mike Marchywka]

On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:
> On 29/07/2019, Paul Smith <paul at mad-scientist.net> wrote:
> > On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
> >> > The first one is simple enough.  It might have been because your disk
> >> > is full, in which case it's a symptom not a cause.  What are the
> >> > permissions on these files?  Run this command:
> >> >
> >> >    ls -ald /tmp /tmp/.tX0-lock
> >> >
> >> > and let us know the results.
> >>
> >> "
> >> bret at bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
> >> ls: cannot access '/tmp/.tX0-lock': No such file or directory
> >> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
> >
> > This looks correct.  That most likely means that this error is a
> > symptom of your disk being full, and not the cause of the problem.
> >
> > After you have cleared out space on your disk, please keep an eye on
> > the size of the /var/log/lightdm/x-0.log file.  If it continues to
> > grow, send along the last 50 or so lines of output from that file and
> > we'll see what it has to say.
> >
> 
> I have posted a message, that is awaiting moderation - a few kB too large.
> 
> If you look at this output;
> 
> "
> bret at bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
> 
> X.Org X Server 1.19.6
> Release Date: 2017-12-20
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> vt.handoff=1
> Build Date: 03 June 2019  08:10:35AM
> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
> http://www.ubuntu.com/support)
> Current version of pixman: 0.34.0
> 	Before reporting problems, check http://wiki.x.org
> 	to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> 	(++) from command line, (!!) notice, (II) informational,
> 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> "
> 
> that last line is an endless loop.

If googling the IOPL error did not work  there is stuff like this too, 

http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html

you could lsof and grep for the process, check what it has open,  or just make the changes and see what happens.

I guess you could itry  " ps ax -f | grep lightdm " and see if it is root or has the right user for any needed  permissions. 


I guess it managed to write a few lines before even with "no" disk space :)




> 
> > Also, you did show you're using an 18.04.2 based system, but if you're
> > using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
> > the output of the "lsb_release -a" command which would tell us (I
> > think) if you're using a spin or similar.
> >
> > What distribution did you actually install here?
> >
> 
> I had posted the output, in response to a previous post by Ralf;
> 
> "
> bret at bret-MD34045-2521:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 18.04.2 LTS
> Release:        18.04
> Codename:       bionic
> "
> 
> It is UbuntuMATE - I believe that had posted that way much earlier in
> the thread.
> 
> Also,
> 
> "
> "
> uname -v
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
> bret at bret-MD34045-2521:~$ uname -a
> Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
> 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> "
> "
> 
> Now, I need to see what I can do before the log file crashes my system again.
> 
> I think that a defect exists in the creating of the log -file -
> whatever is inputting to the log file should not be in an endless
> loop. It ism destructive.
> 
> >
> > --
> > ubuntu-users mailing list
> > ubuntu-users at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >
> 
> 
> -- 
> Bret Busby
> Armadale
> West Australia
> ..............
> 
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
> 
> ....................................................
> 
> -- 
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-- 

mike marchywka
306 charles cox
canton GA 30115
USA, Earth 
marchywka at hotmail.com
404-788-1216
ORCID: 0000-0001-9237-455X