Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Mon Oct 06, 2014 6:47 pm Post subject: timidity++ cannot start using its systemd service |
|
|
The timidity service always fails whether I start it manually or automatically:
localhost ~ # systemctl status timidity
● timidity.service - TiMidity++ Daemon
Loaded: loaded (/usr/lib64/systemd/system/timidity.service; disabled)
Active: failed (Result: exit-code) since Mon 2014-10-06 20:45:16 EET; 3s ago
Process: 4274 ExecStart=/usr/bin/timidity -iA $TIMIDITY_OPTS (code=exited, status=2)
Main PID: 4274 (code=exited, status=2)
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...strings
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...rectory
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...ng name
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...rectory
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...rectory
Oct 06 20:45:16 localhost timidity[4274]: ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.0.27.2/work/alsa-lib-1.0.27.2/src/...default
Oct 06 20:45:16 localhost systemd[1]: timidity.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 06 20:45:16 localhost timidity[4274]: Can't open pcm device 'default'.
Oct 06 20:45:16 localhost timidity[4274]: Couldn't open ALSA pcm device (`s')
Oct 06 20:45:16 localhost systemd[1]: Unit timidity.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
I can run the exact same command in the terminal:
ExecStart=/usr/bin/timidity -iA $TIMIDITY_OPTS
and timidity starts just fine
I'm running this command temporarily to get things going but I'd like to fix my timidity++ service
thanks |
|