If that's where they are, then yes. In the process of creating bash-statemgr it was briefly called "profilemgr" and state data was kept in ~/.config/<name>/profiles. I must have moved my own states in the process and forgotten about the original location.
Sorry for the confusion.
Search Criteria
Package Details: alsaequal-mgr 2013.7.10-1
Package Actions
| Package Base: | alsaequal-mgr |
|---|---|
| Description: | Save and restore named alsaequal states. |
| Upstream URL: | http://xyne.archlinux.ca/projects/alsaequal-mgr |
| Category: | system |
| Licenses: | |
| Submitter: | Xyne |
| Maintainer: | Xyne |
| Last Packager: | Xyne |
| Votes: | 16 |
| First Submitted: | 2012-09-01 02:23 |
| Last Updated: | 2015-01-15 05:29 |
Latest Comments
Comment by Xyne
Comment by karol_007
Do you mean ~/.config/alsaequal/states? I don't have ~/.config/alsaequal/profiles.
Comment by Xyne
The backend of this package has been moved to bash-statemgr. That package provides an openbox pipe menu generator that can use alsaequal-mgr to manage save states through openbox.
The location of the state directory has changed. Copy your old states from ~/.config/alsaequal/profiles to ~/.config/statemgr/alsaequal.
Comment by Xyne
@rwd2
It now defaults to $HOME/.config/
Comment by rwd2
I get "error: /usr/bin/alsaequal-mgr requires XDG_CONFIG_HOME to be set". Shouldn't alsaequal-mgr use defaults when XDG_CONFIG_HOME is not set? See https://mailman.archlinux.org/pipermail/arch-general/2013-February/032980.html