Am Montag, 2. Juli 2018 schrieb Gene Heskett:
On Sunday 01 July 2018 22:14:45 Mike Bird wrote:
On Sun July 1 2018 18:48:27 William Morder
wrote:
Then I will send you a screenshot of my own run
levels, or
somebody else can do so; or you can do some research on how to
set the run levels in sysv-rc-conf.
I'm sorry if I seem to be dogging you today Bill but I do not
recommend messing with sysv-rc-conf. Debian and its major
derivatives automatically enable everything that is installed and
so there is no need to enable and disable services in runlevels as
there is in other distros.
Nor does the runlevel change when TDE is started, and the OP said
that sound was working until he starts TDE.
Yes, I can hear system noises before I login. Login and they become
muted and firefox is silent, until I stop whatever FF is playing and
issue the alsoctl restore command, which reports a can't do that,
system is busy, but when I restart FF playing whatever, it then
works till the next reboot.
IIRC OP did not say which
sound system was working before TDE and which sound system he is
using in TDE.
Alsa seems to be the tool of choice. I have had some of Leonart P's
stuff installed but could not make it work w/o a lot of fiddling, so
I took it back out, sometimes with rm. Apt-get seems not to be very
good at cleaning up the messes it has installed.
Maybe I can't see the forest because of all the trees, but I can't
see any logical reason why starting tde should mute the sound
system, perhaps someone could clarify why that is so, requiring an
intervention by alsactl before it works again.
The most likely explanation for his problem is
that they are
different and that there is a problem with the sound system he is
using in TDE.
Alternatively, if the before TDE sound system and during TDE sound
systems are the same, the most likely explanation is a problem
with the TDE configuration of that sound system.
In practice there is not much difference between these two cases.
The place to look is the configuration of his current TDE sound
system.
I just did, and turned off the remote access and the timeout, we'll
see at the next reboot. Usually at about 30 day intervals. 14 days
uptime right now.
> --Mike