I have the problem that I am listening to a podcast via the “Podcast” app, the “Blank Screen” switches on and the UI is faulty when I want to reactivate the UI. I can then no longer “swipe” to log in - see screenshot.
I can no longer log in and have to wait a long time. I find that a heavy intervention by an app in the basic functions of the smartphone.
Apr 01 19:50:17 pureos gnome-calls[10216]: gtk_application_uninhibit: assertion ‘cookie > 0’ failed
Apr 01 19:50:17 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Apr 01 19:50:17 pureos phoc[10004]: [backend/drm/atomic.c:57] DSI-1: Atomic commit failed (pageflip): Invalid argument
Apr 01 19:50:17 pureos gsd-color[10125]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Apr 01 19:50:18 pureos phoc[10004]: [backend/drm/atomic.c:57] DSI-1: Atomic commit failed (pageflip): Invalid argument
Apr 01 19:51:00 pureos phoc[10004]: [backend/drm/atomic.c:57] DSI-1: Atomic commit failed (pageflip): Invalid argument
Apr 01 19:51:45 pureos systemd-logind[538]: Power key pressed.
Apr 01 19:51:45 pureos phoc[10004]: [backend/drm/drm.c:972] Skipping pageflip on output ‘DSI-1’
Apr 01 19:51:45 pureos pkexec[11039]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Apr 01 19:51:45 pureos pkexec[11039]: purism: Executing command [USER=root] [TTY=unknown] [CWD=/home/purism] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 186]
Apr 01 19:52:10 pureos gsd-xsettings[10142]: Failed to get current display configuration state: Timeout was reached
Apr 01 19:52:10 pureos gsd-power[10140]: Error setting property ‘PowerSaveMode’ on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
Apr 01 19:52:10 pureos gsd-power[10140]: Error setting property ‘PowerSaveMode’ on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
After the login screen deactivated itself again, I was able to log reactivate the screen again and every thing works as expected - spooky.
I hope someone can find the bug an fix it … 