Laptop screen does not wake up when external monitor is disconnected with Shikane h

[kush4gra]

Hyprland version

v0.56.1

Is this a regression?

yes

What's the bug?

using shikane , where i have 2 profiles
profile A (monitor + laptop )-> monitor is enabled, laptop screen is disabled
profile B (laptop fallback) -> only laptop screen

when i disconnect external monitor, laptop screen doesnt wake up
relevant issue in shikane https://gitlab.com/w0lff/shikane/-/work_items/27

Once I remove the external monitor, since laptop screen was already off, there is no output, Hyprland creates FALLBACK and advertise it as Head, now shikane sees FALLBACK and edp-1 (laptop display)
but since laptop profile config only have edp-1, the display doesnt turn on

    [[profile.output]]
    enable = true
    search = ["m=EF25QBA63.B", "s=", "v=EDO"]
    position = "0,0"
    scale = 1.0
    transform = "normal"
    adaptive_sync = false

    [[profile.output]]
    enable = false
    search = ["n=FALLBACK"]

using this as laptop config in shikane does the trick

MR: #15775

Reproduction steps

1. have 2 profiles as mentioned above
2. switch to laptop profile by removing ext monitors

Attachments

No response

I acknowledge that:

• I have searched all (open and closed) discussions and issues and my problem is not there.

• I have read the Code of Conduct and agree to follow it.

• I wrote this request with my own hands, my own keyboard, and in my own words.

[Vladimir-csp]

I've encountered kanshi crashing, probably trying to bring up FALLBACK output up while it is created and destroyed in quick sequence.

This is after disconnecting a dock with two DP displays:

Aug 05 20:09:39 hostname kanshi[3825]: applying profile 'generic_1external'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile output '*' on connected head 'DP-5'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile output 'eDP-1' on connected head 'eDP-1'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile 'nomad'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile output 'eDP-1' on connected head 'eDP-1'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile 'generic_1external'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile output '*' on connected head 'FALLBACK'
Aug 05 20:09:39 hostname kanshi[3825]: applying profile output 'eDP-1' on connected head 'eDP-1'
Aug 05 20:09:39 hostname kanshi[3825]: wl_display#1: error 0: invalid object 7
Aug 05 20:09:39 hostname systemd[3400]: kanshi.service: Main process exited, code=exited, status=1/FAILURE
Aug 05 20:09:39 hostname systemd[3400]: kanshi.service: Failed with result 'exit-code'.
Aug 05 20:09:39 hostname systemd[3400]: kanshi.service: Scheduled restart job, restart counter is at 1.
Aug 05 20:09:39 hostname systemd[3400]: Starting kanshi.service - Kanshi Wayland output manager...
Aug 05 20:09:39 hostname systemd[3400]: Started kanshi.service - Kanshi Wayland output manager.
Aug 05 20:09:39 hostname kanshi[437343]: applying profile 'nomad'
Aug 05 20:09:39 hostname kanshi[437343]: applying profile output 'eDP-1' on connected head 'eDP-1'
Aug 05 20:09:40 hostname kanshi[437343]: configuration for profile 'nomad' applied

Is it a viable idea to not have FALLBACK output If an output management app is active?

[kush4gra]

yes, I applied the fix and its working for me, but i am not too clear on what other consequences it can have