WayfireWM / WayfireWM/wayfire

Screen is black when I close and open the lid. Turns back on only bu switchig to text console and back.

Open
#2,190 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

easy enhancement PRs-welcome
Dominant language
C++
Stars
3.1k
Forks
237
Avg merge
1h 43m
Merged PRs (30d)
1

Description

Mos likely this is because of my laptop hadware - partially. Because it switch screen black without asking OS unlike all my previous ones. (OLED screen ). But here is the thing - I implemeneted the lid workaround suggested here.

  1. Autostart: swayidle timeout 0 'output-power-management -d' resume 'output-power-management -e'
  2. On acpid lid action I call pkill -USR1 swayidle.

With this setting when I open the lid I can wage up just touching any key or even touchpad. But - only in the case when I did not inhibit idle using Alt-B in idle plugin.

Not sure if it is an issue with wayfire, wlroots or even wayland itself - with Xorg/compiz things were working fine.

Also thinking about workaround - like change behvavior of idle plugin instead of inhibiting idle (or as additional shortcut maybe) add a possibity to increase DPMS timeout for some signifficant value. Maybe even ipc script - not sure if there is a dpms timeout set in ipc protocol

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the black-screen behavior with the reported swayidle, acpid lid action, and idle-plugin inhibition setup. Read the idle plugin and IPC protocol entry points mentioned in the report, and compare behavior across Wayfire, wlroots, and Wayland. Done means identifying the responsible component and documenting or implementing an agreed fix or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.