starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: device and device_id is null for monitors connected to hub #302

New Issue
Closed
opened 2026-01-05 14:49:36 +01:00 by adam · 1 comment
adam commented 2026-01-05 14:49:36 +01:00
Owner
Copy Link

Originally created by @nilzen on GitHub (Feb 27, 2024).

Describe the bug
My laptop monitor is detected correctly with a device and device_id property but the two monitors that are connected to a Dell dock isn't detected correctly and cannot be adressed in monitor index preferences.

Screenshots and Videos
image

Operating System

OS Name:                   Microsoft Windows 11 Enterprise
OS Version:                10.0.22631 N/A Build 22631
Originally created by @nilzen on GitHub (Feb 27, 2024). **Describe the bug** My laptop monitor is detected correctly with a `device` and `device_id` property but the two monitors that are connected to a Dell dock isn't detected correctly and cannot be adressed in monitor index preferences. **Screenshots and Videos** ![image](https://github.com/LGUG2Z/komorebi/assets/201781/54abd613-8788-4286-9c60-67f157c06fe0) **Operating System** ``` OS Name: Microsoft Windows 11 Enterprise OS Version: 10.0.22631 N/A Build 22631 ```
adam added the bug label 2026-01-05 14:49:36 +01:00
adam closed this issue 2026-01-05 14:49:36 +01:00
adam commented 2026-01-05 14:49:36 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Feb 27, 2024):

Thanks for the report! Unfortunately docks do not report hardware information to the standard Win32 monitor hardware information APIs, which is why these two properties are explicitly Option<T> types: 1a8b6a7398/komorebi/src/monitor.rs (L32)

In cases like this, you can use monitor_index_preferences instead, which assigns indices for each monitor based on their position on the virtual screen that Windows creates for all monitors, see this thread for more: https://github.com/LGUG2Z/komorebi/issues/275#issuecomment-1292321480.

Closing this ticket as there is no path forward to reading monitor hardware data from proprietary docking hubs.

@LGUG2Z commented on GitHub (Feb 27, 2024): Thanks for the report! Unfortunately docks do not report hardware information to the standard Win32 monitor hardware information APIs, which is why these two properties are explicitly `Option<T>` types: https://github.com/LGUG2Z/komorebi/blob/1a8b6a7398b12b3686b80c6228875a79e7165a26/komorebi/src/monitor.rs#L32 In cases like this, you can use [`monitor_index_preferences`](https://komorebi.lgug2z.com/schema#monitor_index_preferences) instead, which assigns indices for each monitor based on their position on the virtual screen that Windows creates for all monitors, see this thread for more: https://github.com/LGUG2Z/komorebi/issues/275#issuecomment-1292321480. Closing this ticket as there is no path forward to reading monitor hardware data from proprietary docking hubs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#302
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?