Hi,

For an unknown reason, timidity-daemon doesn't start if I set the SERVER_USER as
timidity in /etc/default/timidity (this is the default).

If I set it to root or my username, it starts normally and works as expected.

The timidity system user is in the audio group.

I use pulseaudio (ALSA compatibility enabled).

Cheers,
Julien

- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages timidity-daemon depends on:
ii  adduser                       3.112      add and remove users and groups
ii  timidity                      2.13.2-38  Software sound renderer (MIDI sequ

timidity-daemon recommends no packages.

timidity-daemon suggests no packages.

- -- no debconf information
iEYEARECAAYFAkwLm3IACgkQIQvyq59x1EliAQCdG4W7SPea1ZZuvcAddxf9Y1XH
P60An1RoKnfxwQ1q2HTxeDuc9adje0Cu
=6Gp3
-----END PGP SIGNATURE-----

This seems to be at the heart of the problem...


sudo -u timidity timidity -Os -iA
No protocol specified
xcb_connection_has_error() returned true
Home directory not accessible: Permission denied
No protocol specified
ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
Can't open pcm device 'default'.
Couldn't open ALSA pcm device (`s')


This seems to "fix" things

chown -R timidity: /etc/timidity


which allows a ~timidity/.config/pulse directory (and content) to be created


after which timidity seems to start



having /etc/timidity owned as timidity isnt ideal. but this is the
source of the problem