Re: [jazzplusplus-devel] New Build Instructions on the Web Site

[Pete S. <pst...@ve...>]

PS = Pete Stieber
PS>> Thanks Kevin.  I'm trying to understand the Jazz++
PS>> zombie process that lives on when I exit Jazz++.
PS>> It looks like it has to do with the ALSA connection.
PS>> When I reboot, the ALSA close message even fails.
PS>> This doesn't happen on the Fedora 8 box I test on.

KC = Kevin Cosgrove
KC> Rather than rebooting, is there an alsa service in
KC> /etc/init.d/... which could be restarted with the
KC> 'service' command?

Thanks for suggesting this Kevin.  I'm a long time Red Hat/Fedora user 
and though the "service" command was specific to Red Hat.

I'm starting to think there is a problem that is independent of Jazz++. 
  I tried restarting ALSA from a cold boot and it also has problems...

# service alsa restart
Doing alsactrl to store mixer settings...          [  OK  ]
Shutting down ALSA sound driver (version 1.0.14): no. (sound is being 
used by pid    6272))                              [FAILED]
ALSA driver (version 1.0.14) is already running.

Process 6272 is the sound mixer applet (/usr/lib/mixer_applet2).

Is this normal.  I thought roo should be able to restart this service.

When I check to see what ALSA version I have installed...

$ rpm -qa | grep alsa
libalsa2-1.0.15-0.rc1.4mdv2008.0
libalsa-data-1.0.15-0.rc1.4mdv2008.0
libalsa2-devel-1.0.15-0.rc1.4mdv2008.0
libalsa-oss0-1.0.14-2mdv2008.0
alsa-utils-1.0.15-0.rc1.1mdv2008.0
alsa-plugins-1.0.14-7mdv2008.0

Should 1.0.14 be mixed with 1.0.15?

I don't want to get too caught up in Mandriva specific problems.  Maybe 
I botched the install?

Any ideas Kevin?

Pete