Message: previous - next
Month: February 2014

Re: [trinity-devel] Latest Build broke ALSA sound (play works - aplay screaches)

From: "David C. Rankin" <drankinatty@...>
Date: Tue, 11 Feb 2014 13:35:39 -0600
On 02/11/2014 01:04 PM, Darrell Anderson wrote:
> Yeah, Linux is ready for the desktop....


> You have tested sound with the aplay and play commands, which 
> validates your hardware and alsa. Start an alternate desktop to at 
> least isolate the problem to only Trinity.

I'll see if I can find another small sound capable dt to test with. Currently I
have TDE and Fluxbox, so options are slim.

> I don't know about the above messages, but seems arts is not 
> starting or is not loading completely.

That is the crux of it. artsd is not handling sound events (period).

> Another idea is permissions. I quite often log into my desktop as 
> root to test permissions issues. Not tdesu, actually logging in as 
> root. I don't prescribe to any aspect of the anti-root religion and 
> logging in as root is a quick way to determine whether a problem is 
> permissions related.

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.

> Also try with a fresh profile. I have a couple of testing accounts 
> I use to try various things without touching my normal accounts. 
> With the testing accounts often I 'mv ~/.trinity ~/.trinity.bak' 
> and then start Trinity. That creates a new ~/.trinity profile 
> directory. When I finish testing I 'rm ~/.trinity' and then 'mv 
> ~/.trinity.bak ~/.trinity'.

Since this is virtualbox, I'll just create users doug, sally, ben and jerry and
have totally different profiles :)

> With a fresh profile directory you should hear the stupid login 
> sound file if arts is loading correctly. This at least narrows the 
> issue to your profile or Trinity in general.

My normal profile has the startup sound file enabled and that was the first clue
after upgrade that something broke :(

> When I have arts issues I delete the tdesycoca cache files, 
> ~/.mcop, and all the Trinity socket and temporary files. This is a 
> big reason I don't use graphical logins. I can exit X and be back 
> to the command line without worrying that the login manager and X 
> are still running. Provides an easy way to debug and delete files.
> I also just now remembered there is an arts config file. Once upon 
> a time in the KDE3 days that file caused problems with one of the 
> options, but I no longer remember the details. Anyway, try renaming 
> ~/.trinity/share/config/kcmartsrc.
> And yeah, the tdemultimedia conversion to cmake never was completed.
> Darrell

I know, you told me earlier and I switched to autotools during round 1 of this
R14 build. I'll report back. I hate sound problems, but users will want sound to
play... Grrr.

David C. Rankin, J.D.,P.E.