This is getting stranger:
Darrell, you were correct, aplay will play .wav files just
fine. I rebuilt
both arts and tdemultimedia - no change. From the command line,
both 'play' and
'aplay' work fine, but TDE will not play any sound. I open
kcontrol -> Sound
System -> [Test Sound] and I get nothing. I click the litte |>
next to any sound
event file - same result, no sound.
Checking .xsession-errors, each time I try playing the a
sound, I get the
following:
unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server [tdeinit] Got EXEC_NEW 'artsd' from launcher. [tdeinit] artsd is executable. Launching. unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server [artsd] There are already artsd objects registered, looking if
they are active...
unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) unable to connect to sound server [artsd] ... cleaned 5 unused mcop global references.
server status: running, will suspend in 6 s real-time status: no real-time support server buffer time: 53.288 ms buffer size multiplier: 1 minimum stream buffer time: 53.288 ms auto suspend time: 7 s audio method: alsa sampling rate: 44100 channels: 2 sample size: 16 bits duplex: half device: default fragments: 10 fragment size: 940 [tdeinit] Got EXT_EXEC 'knotify' from launcher. artsd: symbol lookup error: /opt/trinity/lib/libarts_xine.so.0:
undefined
symbol: ao_new_port [tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. [tdeinit] /opt/trinity/bin/artsd is executable. Launching. [artsd] There are already artsd objects registered, looking if
they are active...
unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-02e1-52f9c6c6) [artsd] ... cleaned 5 unused mcop global references.
Checking /tmp/tdesocket-david/localhost.localdomain-02d0-
52f9c6b6, it is there
and easily accessible, so I don't know what that unix_connect
error is all
about. The bottom line, something is active very differently
with this set of
package regarding sound. Let me know if you have any other
thoughts. We'll look
at this more later.
Just so it is clear. After update from the packages built on 1/29 to packages built on 2/8, sound event notifications no longer work in TDE. Using play or aplay from the command line in konsole, both WORK FINE:
02:37 valhalla:~> aplay /opt/trinity/share/sounds/KDE_Window_Open.wav Playing WAVE '/opt/trinity/share/sounds/KDE_Window_Open.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Stereo 02:37 valhalla:~> play /opt/trinity/share/sounds/KDE_Startup_1.ogg
/opt/trinity/share/sounds/KDE_Startup_1.ogg:
File Size: 124k Bit Rate: 125k Encoding: Vorbis Channels: 2 @ 16-bit Samplerate: 44100Hz Replaygain: off Duration: 00:00:07.95
In:100% 00:00:07.95 [00:00:00.00] Out:382k [ | ] Hd:0.1 Clip:3 play WARN rate: rate clipped 2 samples; decrease volume? play WARN dither: dither clipped 1 samples; decrease volume? Done.
However, as soon as any sound event in TDE is triggered (such as on shade), I get the following dumped into the .xsession-errors file:
unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-04ac-52f9cdd8) (The previous message was repeated 2 times.) unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-04e5-52f9cde2) [tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. [tdeinit] /opt/trinity/bin/artsd is executable. Launching. [artsd] There are already artsd objects registered, looking if they are active... [artsd] ... cleaned 5 unused mcop global references.
/opt/trinity/bin/artsd: symbol lookup error: /opt/trinity/lib/libarts_xine.so.0: undefined symbol: ao_new_port unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-04e5-52f9cde2) (The previous message was repeated 1 times.) unix_connect: can't connect to server (unix:/tmp/tdesocket-david/localhost.localdomain-05c9-52f9e0cf) [tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. [tdeinit] /opt/trinity/bin/artsd is executable. Launching. [artsd] There are already artsd objects registered, looking if they are active... [artsd] ... cleaned 5 unused mcop global references.
/opt/trinity/bin/artsd: symbol lookup error: /opt/trinity/lib/libarts_xine.so.0: undefined symbol: ao_new_port
So where is TDE trying to make the call for the sound event resulting in the unix_connect error?
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 don't know about the above messages, but seems arts is not starting or is not loading completely.
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.
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'.
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.
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
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.
-
Darrell Anderson -
David C. Rankin