According to Kyle:
Apparently, Google is not my friend this time, as I can find no
information about this problem, and I appear to be the only one
experiencing it, and only on this machine.
Correction: I actually did find [1], and that appears to be my exact
problem, but it is also unsolved.
I had similar issues on my machine. First I launched mixer and set
everything the way I wanted, then I ran sudo alsactl store. Now the
problem is gone.
Chester
On 09/08/2012 09:59 AM, Frank Wilson wrote:
According to Kyle:
Apparently, Google is not my friend this time, as I can find no
You are not the only one experiencing this problem. This isn't even
unique to archlinux either. Wherever pulseaudio is installed, it brings
with it chaos and destruction. When I do any install of Linux, if the
sound card isn't working it's impossible since I'm totally blind and if
the Linux
Well, I first must say that I have no interest in removing PulseAudio from my
system, as I have had perfectly good results with PulseAudio and accessibility
in the past, and in spite of the bug I am experiencing now on this temporary
machine, there's nothing that works as seamlessly for me as
Finally able to return my attention to this problem.
alsa-store.service and alsa-restore.service are oneshot services with no
[Install] section. Therefore, they cannot be enabled and disabled using
systemctl. They do, however, appear to run as needed, probably as a
dependency when udev loads
According to Kyle:
Apparently, Google is not my friend this time, as I can find no
information about this problem, and I appear to be the only one
experiencing it, and only on this machine.
Correction: I actually did find [1], and that appears to be my exact
problem, but it is also
According to Rodrigo Rivas:
One last idea. Maybe the gnome-settings-daemon is playing dumb with your
sound. I think you can disable the sound plugin of g-s-d using dconf
(org.gnome.settings-daemon.plugins.sound.active).
I tried
dconf write org/gnome/settings-daemon/plugins/sound/active false
On Sat, Aug 18, 2012 at 4:20 AM, Kyle k...@gmx.ca wrote:
According to Rodrigo Rivas:
One last idea. Maybe the gnome-settings-daemon is playing dumb with your
sound. I think you can disable the sound plugin of g-s-d using dconf
(org.gnome.settings-daemon.plugins.sound.active).
I tried
On Sat, Aug 18, 2012 at 8:45 AM, mike cloaked mike.cloa...@gmail.com wrote:
while the volume was at the proper level. At this point, I am totally
stumped. The computer I had that died used a SoundBlaster Live Value, and
although the sound started out muted, restoring the alsa volumes always
Working from the command line in a text-only console using espeakup, all
is well, and sound works as it should. However, starting GDM mutes my
sound card. If I go back to the text console and run
sudo systemctl start alsa-restore
Again, all is well in the text console until I login with GDM.
On Thu, Aug 16, 2012 at 9:28 PM, Kyle k...@gmx.ca wrote:
Working from the command line in a text-only console using espeakup, all
is well, and sound works as it should. However, starting GDM mutes my sound
card. If I go back to the text console and run
sudo systemctl start alsa-restore
According to Rodrigo Rivas:
Have you tried running alsamixer -D hw and see if there are any
muted channels in your hardware?
Master is at 87% normally. Once GDM runs, it zeros out and mutes. Also,
once pulseaudio starts, the Master channel zeros out and mutes.
Also, once I had a similar
On Fri, Aug 17, 2012 at 12:46 AM, Kyle k...@gmx.ca wrote:
According to Rodrigo Rivas:
Have you tried running alsamixer -D hw and see if there are any muted
channels in your hardware?
Master is at 87% normally. Once GDM runs, it zeros out and mutes. Also,
once pulseaudio starts, the
13 matches
Mail list logo
