On This Page...
In the majority of cases, simply describing your issue will not provide enough information for someone to identify it’s cause and advise you on how to resolve it. It is important to include any system logs that may be relevant to your issue to ensure that neither your time nor the other person’s time is wasted. The following is a list of the most common system logs and where/how to obtain them. The logs are listed in the order of importance.
The systemd journal can only be accessed using the journalctl command. You can export your system’s journal from the last three boots using these commands:
su journalctl -b -0 > /tmp/journal journalctl -b -1 > /tmp/journal.last journalctl -b -2 > /tmp/journal.2last exit
Your session log is located in your /home directory:
You can find your Xorg logs here:
LightDM’s logs can be found here:
OTHER LOG PROVIDERS
journalctl --since "10 minutes ago"
is very helpfull also for problems after new installation:
cnchi logs under: /var/log/cnchi now?
/var/log/cnchi/cnchi-XXXXXXXX-XXXXXX.log /var/log/cnchi/install_id /var/log/cnchi/pacman-XXXXXXXX-XXXXXX.log /var/log/cnchi/postinstall-XXXXXXXX-XXXXXX.log
A good way to get information about a particular program:
journalctl -f /usr/bin/"Executable"
And nice to poste a pastebin the smart way:
"command" | curl -F [email protected] https://ptpb.pw/?u=1
System summary example:
lspci > log.txt && lsusb >> log.txt && dmesg >> log.txt && cat log.txt | curl -F [email protected] https://ptpb.pw/?u=1
This will give out a link (like this: https://ptpb.pw/Ggwg3per) you can post onto the forum, this will include all the output of:
lspci (list your pci devices) lsusb (same for usb) and dmesg (bootup messages) and make it aviable.
for html style look:
journalctl -b | ccat --html > boot_log.html