[GH-ISSUE #71] v1.5.0 can't detect LG 34UM95-P Ultrawide monitor #66

Closed
opened 2026-05-05 04:56:05 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @gxfxyz on GitHub (May 7, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/71

Hello,

Firstly thank you for your good work. I've been waiting for a new release for a while.

I just upgraded MonitorControl to the latest v1.5.0 version. But I found it can't detect my LG 34UM95-P Ultrawide monitor in this version.

Screen Shot 2019-05-07 at 14 58 10
Screen Shot 2019-05-07 at 14 58 25

After I downgraded it to v1.4.0, it's working again.

Screen Shot 2019-05-07 at 14 59 43
Screen Shot 2019-05-07 at 15 00 01

So I guess this issue is related to the recent changes of LG Ultrawide monitors support in v1.5.0.

Let me know if you need more information. Thank you!

@reitermarkus

Originally created by @gxfxyz on GitHub (May 7, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/71 Hello, Firstly thank you for your good work. I've been waiting for a new release for a while. I just upgraded MonitorControl to the latest v1.5.0 version. But I found it can't detect my LG [34UM95-P](https://www.lg.com/global/business/monitor/monitor-products/lg-34UM95-P) Ultrawide monitor in this version. ![Screen Shot 2019-05-07 at 14 58 10](https://user-images.githubusercontent.com/43481676/57336307-4c7db900-70da-11e9-93e5-4a244939c643.png) ![Screen Shot 2019-05-07 at 14 58 25](https://user-images.githubusercontent.com/43481676/57336318-556e8a80-70da-11e9-83a5-2073222a40f1.png) After I downgraded it to v1.4.0, it's working again. ![Screen Shot 2019-05-07 at 14 59 43](https://user-images.githubusercontent.com/43481676/57336524-10972380-70db-11e9-94e4-0615c1ac25d2.png) ![Screen Shot 2019-05-07 at 15 00 01](https://user-images.githubusercontent.com/43481676/57336525-1260e700-70db-11e9-8936-276d5f0b0623.png) So I guess this issue is related to the recent changes of LG Ultrawide monitors support in v1.5.0. Let me know if you need more information. Thank you! @reitermarkus
gitea-mirror 2026-05-05 04:56:05 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@reitermarkus commented on GitHub (May 10, 2019):

This is hopefully fixed with the latest commit in DDC.swift.

<!-- gh-comment-id:491365510 --> @reitermarkus commented on GitHub (May 10, 2019): This is hopefully fixed with the latest commit in `DDC.swift`.
Author
Owner

@gxfxyz commented on GitHub (May 16, 2019):

Can confirm this has been fixed in v1.5.2. Thank you guys for this great app! 👍

<!-- gh-comment-id:493236728 --> @gxfxyz commented on GitHub (May 16, 2019): Can confirm this has been fixed in v1.5.2. Thank you guys for this great app! 👍
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#66
No description provided.