Skip to content
This repository has been archived by the owner on Sep 15, 2021. It is now read-only.

Monitor disconnections not detected #97

Open
aarobc opened this issue Jan 30, 2021 · 2 comments
Open

Monitor disconnections not detected #97

aarobc opened this issue Jan 30, 2021 · 2 comments

Comments

@aarobc
Copy link

aarobc commented Jan 30, 2021

Maybe this is a misunderstanding on my part, but when I shut off a monitor kanshi doesn't detect it as a change. A similar setup would function fine on autorandr with i3.

current setup:

  • sway-git
  • kanshi (from AUR)
profile dual {
	output DP-3 mode 3840x2160 position 0,0
	output DP-2 mode [email protected] position 3840,0
}

profile 4k {
	output DP-3 mode 3840x2160 position 0,0
}

profile 2k {
	output DP-2 mode [email protected] position 0,0
}

Is this a wayland thing?

@emersion
Copy link
Owner

Can you grab a drm_info dump after turning off the monitor?

@coderkun
Copy link

coderkun commented Mar 14, 2021

I have the same issue. drm_info shows both monitors as “connected” even if I switch off Connector 1.

├───Connectors
│   ├───Connector 0
│   │   ├───Object ID: 95
│   │   ├───Type: HDMI-A
│   │   ├───Status: connected
--
│   ├───Connector 1
│   │   ├───Object ID: 104
│   │   ├───Type: DisplayPort
│   │   ├───Status: connected

Only if I unplug the cable, the status will switch to “disconnected”. Does that mean that this is a dirver issue?

Driver info from `drm_info`:
├───Driver: i915 (Intel Graphics) version 1.6.0 (20201103)
├───Device: PCI 8086:1912 Intel Corporation HD Graphics 530

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants