Summary: | /etc/init.d/timidity is starting Timidity as the wrong user (?) - alsa dmix | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joël <world.root> |
Component: | New packages | Assignee: | Jeremy Huddleston (RETIRED) <eradicator> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | sound |
Priority: | High | ||
Version: | 2004.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joël
2004-06-16 00:38:32 UTC
I have had THE worst luck getting dmix to work correctly with my test system... but I did get it to work, and timidity played nice with it... I'm guessing that your sound card doesn't have friendly dmix support or something, but the root/non-root issue is really puzzling... what about adding your user to the 'audio' group (don't forget to logout/login after)? I agree it's quite strange.. the whole point of dmix was to compensate for those soundcards by mixing in software :-) Yes, my user already belongs to group 'audio'. Clearly, there's something strange when Timidity is started as root. Should I add root to the 'audio' group too ? what happens when you start xmms as root and run mpgq23 as root (not through aoss)? If I run xmms as root, it hangs until pmidi is stopped. Whether I run timidity as root or user, doesn't matter in this case. If I run xmms as user, it does work simultaneously with pmidi, but *only* if I started timidity as user too. You're going to have to talk to the alsa devs upstream to get this straightened out. I can't reproduce this problem. dmix is very touch-and-go, so I am betting that is the problem rather than timidity. |