I'm closing this bug, since no one else has reported anything similar,
and it was easily fixed by configuration.
Thanks to everyone who responded with their ideas.
Mark
Hi,
Florian Paul Schmidt writes:
> what ALSA pcm device have you configured Audacity to use?
For some reason, it was using "hw:0,1" by default, which is the digital
output of my sound device.
> Does using "hw:0,0" work if set as pcm device in the audacity config?
When I switched it to "hw:0,0"
Leo Famulari writes:
> On Fri, Sep 08, 2017 at 12:24:30PM -0400, Mark H Weaver wrote:
>> Sound output is broken in Audacity on my Thinkpad X200 running GuixSD,
>> at least within GNOME 3 (I haven't tried it anywhere else). It worked
>> in the past. I see the following error messages in Audacity
Hi,
what ALSA pcm device have you configured Audacity to use? From the log
it looks like it tries to use some pcm devices that are commonly
configured in a global alsa.conf (on ubuntu for example in
/usr/share/alsa/alsa.conf (.d). Possibly you do not have these global
definitions available?
On Fri, Sep 08, 2017 at 12:24:30PM -0400, Mark H Weaver wrote:
> Sound output is broken in Audacity on my Thinkpad X200 running GuixSD,
> at least within GNOME 3 (I haven't tried it anywhere else). It worked
> in the past. I see the following error messages in Audacity's
> stdout/stderr:
FYI It'
Sound output is broken in Audacity on my Thinkpad X200 running GuixSD,
at least within GNOME 3 (I haven't tried it anywhere else). It worked
in the past. I see the following error messages in Audacity's
stdout/stderr:
(audacity:893): Gtk-WARNING **: Unable to locate theme engine in module_path:
