ok well… i try to explain more in detail:
As you see here:
d’ag. 10 19:01:33 sancho kwin_x11[795]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow)>
at “>” at he end is made a cut.
To get the full log without “>” which is a result of copy&paste from the terminal do this:
type: journalctl -b1 > ~/journal.txt
this will create a file journal.txt in your home folder.
Then:
type: cat ~/journal.txt
This will load the whole file into the terminal in plain text.
To open the file in plasma in a gui for example:
type: kate ~/journal.txt
this will open kate text editor. Then you can copy&paste it.
Use ``` at the beginning and at the end of the code on the forum like this:
```
Put here the text of the journal.txt
```
This should look like this:
Jul 14 22:18:38 Bolobi systemd[1]: Finished Reboot.
Jul 14 22:18:38 Bolobi systemd[1]: Reached target Reboot.
Jul 14 22:18:38 Bolobi systemd[1]: Shutting down.
Jul 14 22:18:38 Bolobi audit: AUDIT1334 prog-id=62 op=UNLOAD
Jul 14 22:18:38 Bolobi audit: AUDIT1334 prog-id=61 op=UNLOAD
Jul 14 22:18:38 Bolobi audit: AUDIT1334 prog-id=58 op=UNLOAD
Jul 14 22:18:38 Bolobi audit: AUDIT1334 prog-id=57 op=UNLOAD
Jul 14 22:18:38 Bolobi systemd[1]: Hardware watchdog 'SP5100 TCO timer', version 0
Jul 14 22:18:38 Bolobi systemd[1]: Set hardware watchdog to 10min.
Jul 14 22:18:38 Bolobi kernel: watchdog: watchdog0: watchdog did not stop!
Jul 14 22:18:38 Bolobi systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 14 22:18:38 Bolobi systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jul 14 22:18:38 Bolobi haveged[326]: haveged: Stopping due to signal 15
Jul 14 22:18:38 Bolobi haveged[326]: haveged starting up
Jul 14 22:18:38 Bolobi systemd-journald[328]: Journal stopped
Here are also good information that will help to solve the problem better, I highly recommend to read it because it is essential to detect problems.
Anyway… providing good information in a readable format is the half way of solving a problem.