mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1720] App quits constantly #954
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#954
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @DrLeucine on GitHub (Jan 20, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1720
Before opening the issue, have you...?
Describe the bug
The app quits on me constantly. I am not sure what causes it but when I have 2 monitors connected I lose the ability to lower the brightness and notice that MonitorControl has quit. I believe this has started happening after I updated to Sequoia.
Steps to reproduce
Unfortunately I'm not sure. Could you let me know how to output the crash logs?
Expected behavior
The app should not quit randomly.
Anything else?
No response
Environment Information (please complete the following information)
@vanjasmailovic commented on GitHub (Jan 20, 2025):
Same. The app seems to work right after launching it, but very soon after stops working and the macOS brightness control changes the laptop's screen only (not the external screen).
@waydabber commented on GitHub (Jan 20, 2025):
Hi all, please make sure you are using the latest 4.3.3 version (auto-update will not work).
@waydabber commented on GitHub (Jan 20, 2025):
https://github.com/MonitorControl/MonitorControl/issues/1663
@vanjasmailovic commented on GitHub (Jan 20, 2025):
Updating manually to the latest version solved the problem, thanks!