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
To save you digging through the logfiles to check:
Arch Linux
MacBookPro5,5
Attached are logs before and after I changed the pommed.service file to set After=sound.target, and WantedBy=sound.target
Not the most elegant approach (since it assumes we are using the volume control hotkeys).
The text was updated successfully, but these errors were encountered:
I'm no longer really able to maintain this project properly -- I don't use or even own a mac, and have no way to test on my own. This is not a bug I'm going to be able to fix.
The workaround doesn't seem like a bad idea. Can you elaborate on why you don't think it's elegant? (I'm not disagreeing, I just didn't understand what you wrote.)
For this to work, sound support must be enabled on the machine (boot_nosound_log.txt). Somebody disabling their sound support through kernel options or module blacklisting is an edge-case, so this is just an issue of 'correctness' - and maybe it's enough to assume somebody doing this can also tweak their service file as per documentation...
No problems if I restart the service after boot, so this seems to be a race condition.
boot_fail_log.txt
boot_fixed_log.txt
pommed.service.txt
To save you digging through the logfiles to check:
Arch Linux
MacBookPro5,5
Attached are logs before and after I changed the pommed.service file to set After=sound.target, and WantedBy=sound.target
Not the most elegant approach (since it assumes we are using the volume control hotkeys).
The text was updated successfully, but these errors were encountered: