Can you get access to the files on the disk? You might try deleting some of the user pulseaudio configs. On 5/27/16, Mark Peveto <southernprince73@xxxxxxxxx> wrote: > Oh, I'm sure it's good information, friend, I'm just not having much > luck. Think tha'ts more on my end. I'm not as good at this as I should be. > > Mark Peveto > Registered linux number 600552 > Sent from sonar using thunderbird. > > On 05/26/2016 02:11 PM, Willem Venter wrote: >> Hi. >> Pulseaudio takes complete control of the audio device, so when other >> devices try to use the soundcard through alsa things break. >> >> A work around I use is playing sound using dmix. This means a bit more >> processing and possibly a little latency for programs using pulse, but >> on the other hand it's better than broken sound. >> >> Remove package pulseaudio-alsa, which provides compatibility layer >> between ALSA applications and PulseAudio. After this your ALSA apps >> will use ALSA directly without being hooked by Pulse. >> Edit /etc/pulse/default.pa. >> Find and uncomment lines which load back-end drivers. Add device >> parameters as follows. Then find and comment lines which load >> autodetect modules. >> load-module module-alsa-sink device=dmix >> load-module module-alsa-source device=dsnoop >> # load-module module-udev-detect >> # load-module module-detect >> >> After rebooting pulseaudio won't grab the sound device, but instead >> plays it through dmix. >> >> hth >> Willem >> >> On 5/26/16, Mark Peveto <southernprince73@xxxxxxxxx> wrote: >>> Here's the error I was talking about earlier. >>> >>> Back story: I'm trying to get console speech. Since i can't right now, >>> I'm doing this from a terminal, which reads badly. Once I type sudo >>> espeakup, it'll read the top of the console screen, and the login prompt >>> asking for a username. After that it gives an error which i'll post. I >>> know it's a pulseaudio problem. Most suggest I get rid of pulseaudio, >>> and if that's the only solution there is, I guess i'll have to, but that >>> creates more problems when it comes to having the system rediscover new >>> sound drivers. Long explanation short, it jacks things up! >>> >>> Error follows. >>> >>> [southernprince@roxie ~]$ sudo espeakup >>> [sudo] password for southernprince: >>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273, >>> function pa_simple_write(). Aborting. >>> >>> It should be noted here that the error does not appear until I start to >>> type. It reads the login prompt, and once i hit the s for >>> southernprinc, my username, the error appears. If I could figure out >>> how, I might turn keyecho off, which I wanna do anyway, but I don't know >>> if that'd help anything. >>> >>> There ya have it folks. >>> >>> _______________________________________________ >>> Speakup mailing list >>> Speakup@xxxxxxxxxxxxxxxxx >>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >>> >> _______________________________________________ >> Speakup mailing list >> Speakup@xxxxxxxxxxxxxxxxx >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@xxxxxxxxxxxxxxxxx > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
