Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

phosh lock screen breaks after rotating the screen at least once #686

Open
2 tasks done
k8ieone opened this issue Dec 25, 2024 · 6 comments
Open
2 tasks done

phosh lock screen breaks after rotating the screen at least once #686

k8ieone opened this issue Dec 25, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@k8ieone
Copy link

k8ieone commented Dec 25, 2024

Device info (please complete the following information)

  • Device: PineTab2
  • Kernel Version : 6.12.3-danctnix1-1-pinetab2
  • UI: Phosh

Describe the bug
The lock screen issues described in #680 persist even after setting GSK_RENDERER to gl.

The phosh lockscreen doesn't show up if the device has been rotated at least once. The device still responds over SSH, the screen just stays blank.

To Reproduce
Steps to reproduce the behavior:

  1. Install phosh
  2. Lock the screen
  3. Confirm the lock screen works
  4. Unlock the device and rotate the screen
  5. Lock the screen again and observe as the lock screen never presents

Expected behavior
The lock screen should work every time.

Before submitting a bug report, please be sure that you have done the following:

  • I have checked for updates (pacman -Syu) and installed the updates but the problem persisted.
  • I am not using Megi's multiboot image, which is unsupported by the developer.
@k8ieone k8ieone added the bug Something isn't working label Dec 25, 2024
@Danct12
Copy link
Member

Danct12 commented Dec 25, 2024

Please attach journalctl to your bug report (using GitHub's file upload feature).

@k8ieone
Copy link
Author

k8ieone commented Dec 25, 2024

Dec 25 14:53:55 Stan systemd[3419]: vte-spawn-e511a9ca-fe73-47ee-8afe-20890f7ac9a8.scope: Consumed 2.477s CPU time, 106.5M memory peak.
Dec 25 14:53:56 Stan systemd[3419]: dbus-:[email protected]: Consumed 7.644s CPU time, 85.8M memory peak.
** FIRST ATTEMPT - SCREEN LOCK SHOWS **
Dec 25 14:53:58 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:53:58 Stan feedbackd[3603]: Failed to set led pattern: Failed to open /sys/devices/platform/led-0/leds/white:flash/pattern: Permission denied
Dec 25 14:53:58 Stan feedbackd[3603]: Failed to set led pattern: Failed to open /sys/devices/platform/led-0/leds/white:flash/pattern: Permission denied
** MORE ATTEMPTS - ROTATING THE SCREEN VARIOUS WAYS, STILL WORKS **
Dec 25 14:54:01 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:07 Stan phosh[3563]: Failed to load background image: Error opening file /usr/share/backgrounds/gnome/adwaita-d.jxl: No such file or directory
Dec 25 14:54:09 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:12 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:18 Stan phosh[3563]: Failed to load background image: Error opening file /usr/share/backgrounds/gnome/adwaita-d.jxl: No such file or directory
Dec 25 14:54:20 Stan phosh[3563]: Failed to load background image: Error opening file /usr/share/backgrounds/gnome/adwaita-d.jxl: No such file or directory
Dec 25 14:54:23 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:23 Stan syncthing[3429]: [KRXVT] INFO: Joined relay relay://192.52.34.94:22067
Dec 25 14:54:25 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:29 Stan phosh[3563]: Failed to load background image: Error opening file /usr/share/backgrounds/gnome/adwaita-d.jxl: No such file or directory
Dec 25 14:54:31 Stan phosh[3563]: Failed to load background image: Error opening file /usr/share/backgrounds/gnome/adwaita-d.jxl: No such file or directory
** LAST ATTEMPT - THIS IS WHERE THE SCREEN STAYED BLANK **
** I TURNED THE SCREEN ON AND OFF MULTIPLE TIMES, BUT THE LOCK SCREEN REFUSES TO SHOW UP **
Dec 25 14:54:31 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:32 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:32 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout
Dec 25 14:54:40 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout
Dec 25 14:54:47 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout
Dec 25 14:54:47 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:49 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:51 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:52 Stan systemd-logind[3309]: Power key pressed short.
Dec 25 14:54:56 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout
Dec 25 14:55:03 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout
Dec 25 14:55:10 Stan kernel: bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout

@k8ieone
Copy link
Author

k8ieone commented Dec 25, 2024

I also added annotations to explain what was going on with the device. The weird thing is that this doesn't happen consistently.

The only suspicious message that showed up when the lock screen failed is bes2600_wlan mmc2:0001:1: bes2600_pwr_enter_lp_mode, wait pm ind timeout but I don't know if that could be related.

@Danct12
Copy link
Member

Danct12 commented Dec 25, 2024

BES2600 errors shouldn't be related. Can you switch to another tty?

@k8ieone
Copy link
Author

k8ieone commented Dec 25, 2024

Switching to a TTY doesn't work after the lock screen fail.

@k8ieone
Copy link
Author

k8ieone commented Jan 12, 2025

I thought the issue was gone after the last kernel + phosh update because it hasn't happened for a really long time, but I just ran into it again today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants