Probably user tries to report an issue of non-working system, but doing that like: “I booted it up and it does not work. Any thoughts?”
Are you trying to report about freezing of a LiveCD session or freezing of an installed and loaded OS copy session? If about LiveCD, than what is the exact image name are you talking about?
Why kernel is 5.10? Are you using unstable development builds? Are you skilled enough to figure out issue of which component you may have? Also ISOs builds daily, try newest one (Tags · manjaro-plasma/download · GitHub). Or try latest stable (Manjaro - KDE Plasma) based on
5.13 kernel family.
In bug report please try to be more specific: try to find errors and warnings at least in general logs, one of useful source is
but before use, learn it:
journalctl --sync --priority=3 --boot=0 --catalog
journalctl --sync --priority=4 --boot=0 --catalog
journalctl --sync --priority=3 --boot=0 --catalog --dmesg
journalctl --sync --priority=4 --boot=0 --catalog --dmesg
improve argument usage and try it with the arguments you learned.
Change your system clock to make it show you seconds also. Remember exact start time of the freezing effect and try to list journal a bit ahead that time:
journalctl --sync --boot=0
Try to find any logged info about that freezing visual effect. Most possible reason is GPU-related issue.
What exactly you did right before freeze (executing somewhat, some app shows you somewhat, switch to somewhat?) or it is completely unpredictable and random event?
May be some software could be executed in more detailed logging/“debug” mode to see what is going on under the hood, but it will be so much info, that actual event could be hidden and it will be hard to find it there, especially if you did not the exact time of the event.
ls --almost-all -1 -l --human /var/lib/systemd/coredump
Core dumps lands there in installed OS copy (I do know about LiveCD sessions). If it is not empty, than it is not a low priority issue.