gru-kevin gnome lock screen freezes sometimes during wake events #265

Open
opened 2020-12-22 04:17:06 +01:00 by SolidEva · 5 comments
SolidEva commented 2020-12-22 04:17:06 +01:00 (Migrated from github.com)
[suspend-lockscreen.log](https://github.com/SolidHal/PrawnOS/files/5727577/suspend-lockscreen.log)
SolidEva commented 2020-12-23 23:13:14 +01:00 (Migrated from github.com)

To recreate, let system suspend/lock while lid is open.

To recreate, let system suspend/lock while lid is open.
SolidEva commented 2020-12-24 00:37:19 +01:00 (Migrated from github.com)

recreated on blobby kernel with dptx blob for "sane" comparison:
log:
blobby-suspend-log-gru-kevin.txt

recreated on blobby kernel with dptx blob for "sane" comparison: log: [blobby-suspend-log-gru-kevin.txt](https://github.com/SolidHal/PrawnOS/files/5737477/blobby-suspend-log-gru-kevin.txt)
SolidEva commented 2020-12-24 00:41:20 +01:00 (Migrated from github.com)

Issue recreation steps:

  1. Boot system, wait 60 seconds
  2. manually suspend system with the lid left open
  3. wait ~15 seconds
  4. press a key to wake the system
  5. observe backlight turn on, but no other signs of life on the display
  6. wait 1-2 min
  7. observe backlight turn off
  8. press a key to wake system
  9. observe expected lock screen
Issue recreation steps: 1) Boot system, wait 60 seconds 2) manually suspend system with the lid left open 3) wait ~15 seconds 4) press a key to wake the system 5) observe backlight turn on, but no other signs of life on the display 6) wait 1-2 min 7) observe backlight turn off 8) press a key to wake system 9) observe expected lock screen
SolidEva commented 2020-12-24 03:35:50 +01:00 (Migrated from github.com)

spent too long trying to trace the behavior with perf. Couldn't recreate the issue while running perf. Seems to be some kind of race condition

spent too long trying to trace the behavior with perf. Couldn't recreate the issue while running perf. Seems to be some kind of race condition
cvmiller commented 2021-02-17 00:37:24 +01:00 (Migrated from github.com)

I see this occasionally as well. Quite by accident, After wake up I saw the desktop was visible, but nothing responded (no mouse, no clicks). I typed in my password (to unlock the screen) and it "unlocked" and I could use the desktop/mouse/etc.

I see this occasionally as well. Quite by accident, After wake up I saw the desktop was visible, but nothing responded (no mouse, no clicks). I typed in my password (to unlock the screen) and it "unlocked" and I could use the desktop/mouse/etc.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ev4/PrawnOS#265
No description provided.