Quantcast
Channel: Active questions tagged 22.04 - Ask Ubuntu
Viewing all articles
Browse latest Browse all 4439

The "timidity.service" service fails to start if it is run automatically at system startup

$
0
0

After creating the timidity.service file and the related symlink to start the service automatically at system reboot, I rebooted the system and gave the following input:

sudo systemctl status timidity

Output:

× timidity.service - TiMidity++ Daemon     Loaded: loaded (/lib/systemd/system/timidity.service; disabled; vendor preset: enabled)     Active: failed (Result: exit-code) since Mon 2024-10-07 16:34:46 CEST; 50s ago    Process: 635 ExecStart=/usr/bin/timidity -iA Os (code=exited, status=1/FAILURE)   Main PID: 635 (code=exited, status=1/FAILURE)        CPU: 31msott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: Started TiMidity++ Daemon.ott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: jack_client_new: deprecatedott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Cannot connect to server socket err = No such file or directoryott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Cannot connect to server request channelott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: jack server is not running or cannot be startedott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlockott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlockott 07 16:34:47 netcom-Vostro-15-3510 timidity[635]: Couldn't open output deviceott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: timidity.service: Main process exited, code=exited, status=1/FAILUREott 07 16:34:46 netcom-Vostro-15-3510 systemd[1]: timidity.service: Failed with result 'exit-code'.

My username is associated with the audio group.

Symlink:

/usr/lib/systemd/system/multi-user.target.wants/timidity.service

Service:

/usr/lib/systemd/system/timidity.service

Contains:

[Unit]Description=TiMidity++ DaemonAfter=sound.targetRequires=sound.target[Service]ExecStart=/usr/bin/timidity -iA OsType=simple[Install]WantedBy=multi-user.target

I also tried changing the "timidity.service" file to the following:

[Unit]Description=TiMidity++ DaemonAfter=pulseaudio.serviceRequires=pulseaudio.service[Service]ExecStart=/usr/bin/timidity -iA OsType=simple[Install]WantedBy=multi-user.target

But after rebooting the system again, the error is the same.

Trying to start the service manually from the terminal with the system already started, the service starts correctly.

What am I doing wrong?


Viewing all articles
Browse latest Browse all 4439

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>