[xubuntu-users] How to get the right information about a "crash"

[Willem Hobers]

Thank you for this very useful information.

Unfortunately I read and answered your previous emails first :-(

As you suggested I tried to google :

/var/log/Xorg.1.log:[  1478.948] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

but did not find something that I seemed useful to me (partly because I 
did not quite understand everything that was reported in those reports).

Launchpad does give some results[1], but I don't know which is the right 
one for my case.

Is there anything I can do, to prevent this crash from occurring again?

Thank you,

Willem

[1] 
https://launchpad.net/+search?field.text=%2Fdev%2Fdri%2Fcard0%3A+failed+to+set+DRM+interface+version+1.4%3A+Permission+denied&field.actions.search=Search

Op 17-07-17 om 23:14 schreef Ralf Mardorf:
> I should explain the command I mentioned.
>
> There are Xorg log files in /var/log.
>
>    [weremouse at moonstudio ~]$ ls -hl /var/log/Xorg*
>    -rw-r--r-- 1 root root 599 Jul 17 22:58 /var/log/Xorg.0.log
>    -rw-r--r-- 1 root root 599 Jul 17 22:58 /var/log/Xorg.0.log.old
>    -rw-r--r-- 1 root root 29K Sep 10  2015 /var/log/Xorg.1.log
>    -rw-r--r-- 1 root root 29K Sep  9  2015 /var/log/Xorg.1.log.old
>
>    [weremouse at moonstudio ~]$ man grep | grep DESCRIPTION -A1
>    DESCRIPTION
>           grep searches the named input FILEs for lines containing a match
>           to the given PATTERN. [snip]
>
> The "EE" is more or less unique for Xorg log files and a starting point
> to find errors in those log files. IOW
>
>    grep EE /var/log/Xorg*log*
>
> does search for entries containing "EE" in all Xorg log files, since
> the asterisks are wildcards.
>
>    grep EE /var/log/Xorg*log* > /tmp/xorglog.txt
>
> ">" redirects the standard output to a file.
>
> Before you post the output, read it, even if you shouldn't understand it.
>
> 1. A log file could contain private data.
>     Unlikely a Xorg log file contains such data, but...
> 2. ...you could google possible error messages and find hints, how to
>     solve the issue.
>
>