On Sat, Jan 20, 2018 at 08:07:05AM -0500, Ryan Marsaw wrote:
>
> Is your no-audio problem consistent, or does it happen intermittently?
Consistent, with all versions of 58 from beta3 (the earliest
available) to the release, and also with the binary of beta16 (that
was on my most recent build).
For building from source, I had tried betas also on other, slower,
machines with development LFS versions and got the same problem. On
one of those boxes I've now gone back to an 8.1 system, installed 58
with pulse, and again no sound. I'm currently rebuilding firefox
for alsa on that one.
> I
> _sometimes_ get no sound with Firefox using PulseAudio. What works for me when
> the sound isn't working is by closing Firefox, and then re-setting my default
> sink for PulseAudio. For example: running
>
> "pactl list short sinks," and then
> "pacmd set-default-sink <sink #>"
>
> Restarting Firefox then re-enables sound.
> I cannot determine what exactly causes the sound issue, but the steps listed
> above always "fixes" the sound problems (in my case!).
>
Hmm, I remember that sound seemed to go on one of my machines - and
I had trouble getting it back. But I think that parole uses pulse,
and that has no problem with sound. Hmm, based on what you wrote,
maybe that was mistaken.
But I've stopped the build-for-alsa script, it hadn't got very far.
root@ac4tv /home/ken #pactl list short sinks
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
After pulseaudio --start I get the same result
I also note that it warns that ~/.config/pulse/cookie does not
exist, and although ps aux shows pulseaudio --start as if it is
running, the cookie is not created.
So maybe this is a pulse problem.
>
> >
> > For rustc, the line 'channel = "stable"' needs to be deleted for
> > recent versions. For firefox, use ./mach build (or ./mach build
> > --verbose) and (DESTDIR=/some/where ) ./mach install.
> >
> >
> The line doesn't need to be deleted; It needs to be only moved from the header
> named "[install]" to the newly-added header "[rust]"
> I noticed this when my first attempt to build Rust 1.23.0 failed at the
> install
> phase. After looking at the example config.toml file I saw that "channel="
> moved places.
>
> Therefore, the new config.toml should look like this:
>
> cat <<EOF > config.toml
> # see config.toml.example for more possible options
> [llvm]
> targets = "X86"
>
> [build]
> # install cargo as well as rust
> extended = true
>
> [install]
> prefix = "/usr"
> docdir = "share/doc/rustc-1.23.0"
>
> [rust]
> channel = "stable"
> EOF
>
I got an error message in maybe 1.22.1 (I think the build aborted,
but it was a long time ago). Seems to be happy enough without
forcing a channel, and maybe stable is the default for a release ?
Thanks for your comments so far.
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
