Comment 3 for bug 1924882

If booting an older kernel version does not fix the problem then next please attach photos of the problem.

Although I suspect this is a kernel regression in 5.8.0-50 because I've seen a couple of other similar reports today. Plus your kernel log is showing some graphics errors:

[ 12.084441] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:0:00000000
[ 12.084691] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 12.186937] i915 0000:00:02.0: [drm] gnome-shell[838] context reset due to GPU hang
[ 14.901681] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [838]
[ 14.901755] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
...
[ 30.006257] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [1452]
[ 30.006329] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 30.108370] i915 0000:00:02.0: [drm] gnome-shell[1452] context reset due to GPU hang
[ 47.677368] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:3f5a7c3e, in glmark2 [1836]
[ 47.677437] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 47.779415] i915 0000:00:02.0: [drm] glmark2[1836] context reset due to GPU hang
[ 76.803381] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:c07fffff, in glmark2 [1836]
[ 76.803441] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 76.905854] i915 0000:00:02.0: [drm] glmark2[1836] context reset due to GPU hang