I'll give it a try. But I learned during the original problem I had with sound, root uses a completely different sound scheme than normal users in TDE. root makes use of alsa-raw which bypasses a bulk of the user sound config, so it may work fine and still not be a permission issue.
If true then file a bug report. There should be no reason why root should use arts differently than non-root users.
Since this is virtualbox, I'll just create users doug, sally, ben and jerry and have totally different profiles :)
At this point I say stop and test with real hardware. Virtual machines work great for many things, but your particular problem needs to be resolved with real hardware. Get a second machine, create a second partition. I use all of the above for testing.
Darrell
On 02/11/2014 02:39 PM, Darrell Anderson wrote:
I'll give it a try. But I learned during the original problem I
had with sound, root uses a completely different sound scheme than normal users in TDE. root makes use of alsa-raw which bypasses a bulk of the user sound config, so it may work fine and still not be a permission issue.
If true then file a bug report. There should be no reason why root should use arts differently than non-root users.
I think this has to work this way due to the way polkit/udev, etc.. provide user hardware access while there are no limitation on root access to hardware devices (this is the nitty-gritty where my eyes start crossing...) I'll check further and see if I can confirm the exact differences. (this may be part of the reason root login is discouraged -- I don't know)
I'll check on real hardware, but that should not be an issue since here sound is working on vbox. It shouldn't matter to TDE, since it is just a matter of sound calls being made to moduleX. As long as it is activating/calling moduleX correctly, then sound should play. Since sound does play in everything except TDE, it looks suspect. I'll do all the tests you suggested and a real hardware test. We shall chase it down...
-
Darrell Anderson -
David C. Rankin