You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated MonitorControl to the latest version (if applicable)
Describe the bug
I am using mackup (https://github.com/lra/mackup) to backup my .dotfiles including preferences and settings of installed apps. The program works the way, that it duplicates the original preference files from the ~/Library/ directories to a specified directory and then create a symlink to this file back into the directory. For MonitorControl it takes these steps:
Duplicate ~/Library/Preferences/me.guillaumeb.MonitorControl.plist into ~/.dotfiles
Delete original ~/Library/Preferences/me.guillaumeb.MonitorControl.plist
Symlink ~/.dotfiles/me.guillaumeb.MonitorControl.plist back to ~/Library/Preferences/me.guillaumeb.MonitorControl.plist
MonitorControl however deletes this symlink and recreates the preferences automatically with the same filename but with the symlink stripped from it. This way mackup throws an error and-more important-does not backup the preferences for MonitorControl.
Steps to reproduce
Install mackup via brew install mackup
Create config file for monitorcontrol (following the docs) at ~/.mackup/monitorcontrol.cfg with
[application]
name = MonitorControl
[configuration_files]
Library/Preferences/me.guillaumeb.MonitorControl.plist
Run backup via mackup backup
Symlink is created and the shortly after removed again and replaced by the original file without symlink
Expected behavior
Option: Change content of .plist file without recreating it every time
Option: When recreating .plist file, keep symlink status intact
Anything else?
I know, this is not per se a bug with MonitorControl; more an unexpected behaviour with the .plist file. If this is better suited as a discussion post, please feel free to move it over. Thanks a lot for your consideration!
Environment Information (please complete the following information)
- macOS version: 14.0 Sonoma
- Mac model: Macbook Pro, M1 Pro
- MonitorControl version: v4.1.0 Build 7034 (installed via Homebrew)
- Monitor(s): -
- Apple Silicon/M1: yes
The text was updated successfully, but these errors were encountered:
MonitorControl is managing userdefaults via the normal system calls only so I am not sure what to do with this, but will leave it open, maybe somebody has an idea. :)
@wohfab Found this thread via Google. This doesn't seem to have anything to do with MonitorControl or the apps themselves, but rather how macOS Sonoma (and perhaps even latest Ventura) handles symlinks for plists and the like (broken). Many apps via Mackup are currently experiencing major issues. See lra/mackup#1924
Before opening the issue, have you...?
Describe the bug
I am using
mackup
(https://github.com/lra/mackup) to backup my.dotfiles
including preferences and settings of installed apps. The program works the way, that it duplicates the original preference files from the~/Library/
directories to a specified directory and then create a symlink to this file back into the directory. For MonitorControl it takes these steps:~/Library/Preferences/me.guillaumeb.MonitorControl.plist
into~/.dotfiles
~/Library/Preferences/me.guillaumeb.MonitorControl.plist
~/.dotfiles/me.guillaumeb.MonitorControl.plist
back to~/Library/Preferences/me.guillaumeb.MonitorControl.plist
MonitorControl however deletes this symlink and recreates the preferences automatically with the same filename but with the symlink stripped from it. This way
mackup
throws an error and-more important-does not backup the preferences for MonitorControl.Steps to reproduce
mackup
viabrew install mackup
monitorcontrol
(following the docs) at~/.mackup/monitorcontrol.cfg
withmackup backup
Expected behavior
.plist
file without recreating it every time.plist
file, keep symlink status intactAnything else?
I know, this is not per se a bug with MonitorControl; more an unexpected behaviour with the
.plist
file. If this is better suited as a discussion post, please feel free to move it over. Thanks a lot for your consideration!Environment Information (please complete the following information)
The text was updated successfully, but these errors were encountered: