X.org server

/var/log/Xorg.0.log

See:
http://linux.overshoot.tv/wiki/xorg_server
http://linux.overshoot.tv/wiki/xorg_server_logs

If X is started as a user (startx), then you might find the logs at:
~/.local/share/xorg/Xorg.0.log

/var/log/Xorg.N.log

You may notice various log files where the value of N is incremented:

Xorg.0.log
Xorg.1.log
Xorg.2.log
Xorg.3.log

The first file (Xorg.0.log) corresponds to the first X11 session opened, usually on VT7 (tty7).
The logs for the second X11 session (usually on VT8), will be logged in Xorg.1.log, etc.

/etc/conf.d/xdm

Configure the display manager.

For example, if you use KDM as your display manager, set:

DISPLAYMANAGER="kdm"

See also:
http://linux.overshoot.tv/wiki/display_manager

X.Org Server logs

Check the X.org Server logs for errors:

fgrep '(EE)' /var/log/Xorg.0.log

The timestamp in front of each log entry corresponds to the number of seconds since the server was started.

$DISPLAY is not set or cannot connect to the X server

Error:

$ startkde
$DISPLAY is not set or cannot connect to the X server.

Solution:
Do not use startkde directly. Use startx and configure it to startkde.

Make sure that X Windows is properly installed, configured and running.
Try:

$ startx
bash: startx: command not found

The result shows that X Windows is not properly installed.
Check your system installation guide to install X Server.

In you home directory, create a file named .xinitrc with this simple line:

exec startkde

https://wiki.gentoo.org/wiki/Xorg/Guide

What is .xsession-errors?

Sat, 01/16/2016 - 11:35 - augustin

What is .xsession-errors?
What is the content for?
Should users ever need to be concerned about it?

Context for me asking:
I just experienced an abnormal growth of that file, which filled up my filesystem:
#5417: knotify4 fills up filesystem with .xsession-errors

knotify4 fills up filesystem with .xsession-errors

Sat, 01/16/2016 - 11:33 - augustin

My /home directory was getting filled.

I tried to make space but the space was occupied straight away.
I found a 8.8G file in /home/user/ :

-rw------- 1 user adm 8.8G 2016-01-16 10:16 .xsession-errors

I deleted it but the space was filling up again.
In iotop, I found the process that was filling it (process with highest DISK WRITE speed).
I killed it, and the growth stopped, but I didn't reclaim the space.

the process was knotify or knotify4.
iotop does not leave any output on the console, so I am not sure.

Syndicate content