Gqrx pulseaudio error connection refused

Hi,

I’m experiencing a similar, but slightly different issue. I am trying to set up an application written in GnuRadio & ported to the RPi4. Basically, to receive FM radio & cast it to an amp with a bluetooth dongle in the garage (only way to get FM radio into the garage). This is for when there is no internet access from the property. It all works via my USB soundcard plugged into an amp, & via the HDMI to a portable TV. But, switching to Bluetooth device showed a connection, but the sound continued through the previously activated device, not the bluetooth device. The only limited success was with the hadphones, as these did show up in VLC (the other two devices did not), but the audio was phased on/off every couple of seconds.

I tried various things, none of which worked, and eventually purged pulse completely. Success! of sorts… VLC & Rythmbox did not pick up any pf the devices at all now. However, using the browser on YouTube or the national broadcaster player worked fine — through whichever bluetooth device I selected. My GnuRadio application worked OK as well — except it just stopped running after a few minutes. I will try again and check the CPU usage at some point, in case it is a throttling issue. That is when I discovered GQRX had gone. I had to re-install it. And when I tried to run it, it complained about the missing pulse audio files.

So, there you have it. GQRX seems to depend on Pulseaudio, but pulseaudio doesn’t work correctly with bluetooth — it makes the connection but fails to route the audio through to the device. I have wasted a lot of time in the past with pulseaudio & midi, and don’t have the will to go down that rabbit hole again, because it is extremely flaky even on a PC, and that has been compounded in the RPi from what I can tell — and there is very limited documentation about how it works, how it should work, or how to fix problems when it doesn’t. The best advice I have read is to purge it and avoid it. But, for some reason, som key applications rely on it to work.

If I get any further with this, I’ll let you know (if you are still following this thread) — and likewise, if you have any further info, I’d appreciate knowing where you eventually got to with this. There are instructables & YouTube videos about setting up the RPi for RTL-SDR, but I found it more useful to get things working on a linux laptop first, then trying to replicate that on the RPi.

On the laptop I used Mint Cinnamon 19.4, and it was all sweet — but Ubuntu 18.4 was a bit of nightmare (so steer clear). There is a huge load of discrepancies between the GnuRadio version, the QT & Python versions libraries, and the cmake utility — and it looked like the only way round that would be to set up a full blown development environment with IDE and build everything from scratch from G/C++ up to ensure all the versions work together. One of the issues is that nobody is looking after at least one part of that chain anymore, so there is a break in one layer of compatibility from what I can tell. Mint seems to use the last compatible set of libraries, whereas Ubuntu uses the latest release of GnuRadio.

GQRX is built out of GnuRadio — so there are implications for that moving forwards.

I would suggest (& may try) the Ubuntu build for the RPi, but given what I said above, I suspect that is going to be more frustrating than the Raspberry Debian build — and at least that seems to have a full set of compatible libraries ported to ARM that means GnuRadio works & anything written using it elsewhere just ports across without any obvious issues. The pulseaudio thing appears to be a feature within GQRX, because GnuRadio seems to work without the pulse libraries installed.

Of course, I could be talking BS, but that is where I got to.

Arch Linux

You are not logged in.

#1 2010-01-26 09:55:07

[PulseAudio] Connection refused

Hi, I am trying to install PulseAudio, but so far I have little luck.

I followed the ArchWiki, however I keep getting the message: Connection failed: connection refused (both in pavucontrol and mplayer). Here is some relevant info:

I removed (and blacklisted) the snd-pcm-oss module. PulseAudio is running in user-mode. The packages I have installed are: pulseaudio, paprefs, pavucontrol, pavumeter, gstreamer0.10-pulse and alsa-plugins. Also I setup gstreamer to use pulse (using gconftool) I tried to install gnome-media-pulse from AUR, only it fails to replace gnome-media:

Both PulseAudio and Avahi-daemon are running.

Here is what mplayer says:

I have no clue on what to try next. Btw ALSA withouth Pulse works fine.

#2 2010-01-27 03:33:00

Re: [PulseAudio] Connection refused

Are you running mplayer as root? Running pulse as user means you should only use apps which run as user to access it.

Last edited by ngoonee (2010-01-27 03:33:21)

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Источник

Почему я получаю эту ошибку «Ошибка подключения к PulseAudio»?

У меня есть компьютер, на котором работает Mythbuntu 12.04. Он имеет внешнее USB-устройство Kenwood Digital Audio.

Когда я открываю pavucontrol, я получаю это сообщение:

Если я делаю так, как предлагает сообщение, и запускаю start-pulseaudio-x11, я получаю такой вывод:

Файл журнала ошибок, созданный с помощью этих инструкций, на Pastebin.

Как мне исправить эту ошибку?

6 ответов

Решение этой проблемы было найдено в ходе решения другой моей проблемы с Pulseaudio и Flash.

Сначала мне нужно было полностью очистить и переустановить Pulseaudio. Один из способов сделать это — запустить команду:

Затем, после того, как у меня было хорошее начало, я обнаружил эту странную запись в /etc/pulse/client.conf , У этого была линия, которая сказала:

Кажется, что now не является допустимым вариантом. Я понятия не имею, откуда взялся этот вариант, так как я думал, что начал заново после переустановки.

Я изменил это на yes и затем все равно прокомментировал это.

Перезагрузился, и тогда я смог открыть pavucontrol без ошибок.

Урок, который я извлек из этого, заключается в том, что очистка приложения может быть не такой полной, как можно было бы предположить.

Там могут быть сообщения об ошибках, что файлы не могут быть найдены. Это нормально. Затем мы запускаем пульс и запускаем его снова:

Там тоже ошибки могут быть сообщены как:

Но после перезагрузки у меня все заработало. Pavucontrol работает нормально с тех пор снова.

Я предполагаю, что вы пытались удалить

/.pulse / * и перезапустить звуковой сервер?

Источник

I am running gqrx through a SSH tunnel like this:
ssh -Y -C 192.168.1.120 gqrx

When I press the Start DSP button it crashes with the error that can be seen on the last line:

Of course, running gqrx locally works OK. The problem is when I run it over SSH. Firefox on the other hand runs OK over SSH and also I can hear sound on the remote machine.

The text was updated successfully, but these errors were encountered:

../src/pulseaudio/pa_sink.cc: pa_simple_new() failed: Connection refused

Perhaps you don’t have pulseaudio running on the computer?

pulseaudio is running on both computers
Also, on both computers I can run gqrx local.

Still, something needs to be configured. Sorry, but you’ll have to figure this one out for yourself if you want it resolved quickly, because I don’t have experience with this nor do I have time to research it.

Try searching for «pulseaudio ssh connection refused» — I’m sure others have had similar problems.

Note that firefox could be using alsa directly.

Note that firefox could be using alsa directly.

Indeed, on Xubuntu the firefox package depends on libasound2 so it is not using pulseaudio. If you can’t find any solution you could rebuild gqrx with portaudio support.

Any updates here? It seems to be a usage/configuration issue and not a gqrx issue.

On paragraph «Piggybacking on X11 forwarding» it is explained how to forward the pulseaudio data from the remote source to the client. This procedure is valid for all the pulseaudio based applications, however it would be great to include these info in the gqrx documentation

@fbraghiroli — thanks for the info!

The wiki here on github is enabled and open to everybody to edit, so feel free to add a page with this note.

I had a somewhat similar problem. I was testing sound using pulse server. It was working just as expected through ssh until I added ‘-X’ or ‘-Y’ option. The solution to the problem was setting PULSE_SERVER environment variable to IP of the computer with speakers(which could be the host you are connecting to).
export PULSE_SERVER=192.168.10.200
Same problem arises if you use vglconnect instead of «ssh -X». And the same solution solves it.

Источник

Gqrx pulseaudio error connection refused

Ok so I’ve been running into an error with my new raspberry pi 4.

I’m trying to use gqrx, I installed it via the add/remove software option since attempting too directly from the website the old way always gave me far more errors than this one ever since buster released.

So i get it installed, and it seemed like it worked at first. problem was there was no audio, I tried to switch to the analog function since I’m trying to run it through a Bluetooth speaker via its auxiliary/headphone jack, problem with that is as soon as i check the analog option it gets stuck at 2% volume, and soon as i try to raise the volume it immediately disables the analog AND hdmi options so neither is checked.

After this I just straight up reinstalled raspbian to see if maybe something some how got corrupted in the install(has happened before and figured no big deal since I didn’t have anything else on the pi) soon as I did this I’d get the pulseaudio error mentioned in the title and gqrx won’t start at all.

I then attempted something I read online about the error about completely uninstalling and reinstalling pulseaudio through terminal, and after doing that it went right back to the other issue where the analog and hdmi would get stuck at 2% volume and any attempts at increasing it would disable them.

When the issue with the volume being stuck on 2% happens, gqrx “technically” runs, as in its picking up signals can change frequencies etc, and I’m sure if i just recorded and saved a session and played it back as a file it’d probably work (haven’t tested this yet of course), but when I get the pulseaudio error it just stops the program from even starting.

Re: Pulseaudio error connection refused.

Re: Pulseaudio error connection refused.

Anyone? I’m still not quite sure what I’d need to do to fix this.

Re: Pulseaudio error connection refused.

Anyone? I’m still not quite sure what I’d need to do to fix this.

Most support and advice in these forums is offered by volunteers donating their own free time. Maybe noone with both the skills and inclination to respond has logged on in the 24 hours or so since your query. (It is a weekend in Europe and the Americas.)

Your area of concern, pulseaudio and gqrx, is very narrow — perhaps there are a limited number of volunteers with overlapping interests.

And as a practicality, these forums have an Unanswered Topics search. By your own action your question would have been suppressed from the results of that search.

This might be relevant, although it may not offer a solution::https://github.com/csete/gqrx/issues/693

Re: Pulseaudio error connection refused.

Anyone? I’m still not quite sure what I’d need to do to fix this.

And as a practicality, these forums have an Unanswered Topics search. By your own action your question would have been suppressed from the results of that search.

I. actually didn’t realize that, sorry. I’ll keep that in mind next time I need help, I’m used to forums where questions for help get buried and forgotten after leaving the first page.

I’ll try the link you sent and see if it helps with anything.

Re: Pulseaudio error connection refused.

Re: Pulseaudio error connection refused.

Make sure pulseaudio is installed:

sudo apt-get install pulseaudio

Then open a terminal and start the server:

Make sure gqrx is installed:

sudo apt-get install gqrx-sdr

Then gqrx should work fine. I just tried it.

Re: Pulseaudio error connection refused.

Make sure pulseaudio is installed:

sudo apt-get install pulseaudio

Then open a terminal and start the server:

Make sure gqrx is installed:

sudo apt-get install gqrx-sdr

Then gqrx should work fine. I just tried it.

Just Tried this now.

It showed that pulseaudio was already installed and the newest verison, same with gqrx. When I attempted pulseaudio -D, it said «Daemon Startup failed»

unfortunately the issue with it always reverting to 2% volume anytime I attempt to click analog or hdmi is still there, and soon as I try to increase the volume it disables both.

Re: Pulseaudio error connection refused.

This is probably a really dumb question but, since I’m still new to linux based systems like rasbian. is there a way to run gqrx without pulseaudio at all? Or install it without having pulseaudio installed with it? Every time i try to uninstall pulseaudio it automatically removes gqrx with it, and from what I’ve been seeing so far the issue is directly related to pa itself, since soon as I remove it the analog and hdmi options work normally again, allowing me to select them and increase/decrease volume on them normally again.

For what I’m wanting to use gqrx for(a portable sdr I can take with me and control through vnc on my phone, with a speaker directly connected to the 3.5mm jack on the pi) pulseaudio isn’t really something I think I need anyway.

Re: Pulseaudio error connection refused.

I’m experiencing a similar, but slightly different issue. I am trying to set up an application written in GnuRadio & ported to the RPi4. Basically, to receive FM radio & cast it to an amp with a bluetooth dongle in the garage (only way to get FM radio into the garage). This is for when there is no internet access from the property. It all works via my USB soundcard plugged into an amp, & via the HDMI to a portable TV. But, switching to Bluetooth device showed a connection, but the sound continued through the previously activated device, not the bluetooth device. The only limited success was with the hadphones, as these did show up in VLC (the other two devices did not), but the audio was phased on/off every couple of seconds.

I tried various things, none of which worked, and eventually purged pulse completely. Success! of sorts. VLC & Rythmbox did not pick up any pf the devices at all now. However, using the browser on YouTube or the national broadcaster player worked fine — through whichever bluetooth device I selected. My GnuRadio application worked OK as well — except it just stopped running after a few minutes. I will try again and check the CPU usage at some point, in case it is a throttling issue. That is when I discovered GQRX had gone. I had to re-install it. And when I tried to run it, it complained about the missing pulse audio files.

So, there you have it. GQRX seems to depend on Pulseaudio, but pulseaudio doesn’t work correctly with bluetooth — it makes the connection but fails to route the audio through to the device. I have wasted a lot of time in the past with pulseaudio & midi, and don’t have the will to go down that rabbit hole again, because it is extremely flaky even on a PC, and that has been compounded in the RPi from what I can tell — and there is very limited documentation about how it works, how it should work, or how to fix problems when it doesn’t. The best advice I have read is to purge it and avoid it. But, for some reason, som key applications rely on it to work.

If I get any further with this, I’ll let you know (if you are still following this thread) — and likewise, if you have any further info, I’d appreciate knowing where you eventually got to with this. There are instructables & YouTube videos about setting up the RPi for RTL-SDR, but I found it more useful to get things working on a linux laptop first, then trying to replicate that on the RPi.

On the laptop I used Mint Cinnamon 19.4, and it was all sweet — but Ubuntu 18.4 was a bit of nightmare (so steer clear). There is a huge load of discrepancies between the GnuRadio version, the QT & Python versions libraries, and the cmake utility — and it looked like the only way round that would be to set up a full blown development environment with IDE and build everything from scratch from G/C++ up to ensure all the versions work together. One of the issues is that nobody is looking after at least one part of that chain anymore, so there is a break in one layer of compatibility from what I can tell. Mint seems to use the last compatible set of libraries, whereas Ubuntu uses the latest release of GnuRadio.

GQRX is built out of GnuRadio — so there are implications for that moving forwards.

I would suggest (& may try) the Ubuntu build for the RPi, but given what I said above, I suspect that is going to be more frustrating than the Raspberry Debian build — and at least that seems to have a full set of compatible libraries ported to ARM that means GnuRadio works & anything written using it elsewhere just ports across without any obvious issues. The pulseaudio thing appears to be a feature within GQRX, because GnuRadio seems to work without the pulse libraries installed.

Of course, I could be talking BS, but that is where I got to.

Источник

PulseAudio: Unable to connect: Connection refused #255

Output of the audio debugging script.

Your OS (including version) where you are running AlexaPi:

Raspbian GNU/Linux 8.0 (jessie)
(Linux raspberrypi 4.9.24-v7+)
Running AlexaPi in /opt

Your hardware platform and model you are running on:

Raspberry Pi 2 Model B

Python release ( python2 —version ):

Description of problem:
Alexapi doesn’t seem to have the permission to run the script at startup, I have to restart it manually otherwise I have pulseaudio error.
AlexaPi is already part of pulse-access and everything (except the «users» group) as I followed the systemwide pulse audio tutorial.
ALEXA PI WORKS FINE WHEN LAUNCHED MANUALLY WITH USER PI

The program also gets a related (I assume) error when I check alexapi status :
‘raspberrypi python[798]: ERROR: URLError: [Errno 111] Connection refused’

Expected:

Problem-relevant config.yaml entries:

Steps to reproduce:

Traceback (if applicable):

Additional info:

The text was updated successfully, but these errors were encountered:

Hello,
Are you shure to be in the audio group?

If it’s not working, are you shure that the pulseaudio server is running?

Pi user is already part of «audio» group.

Also systemctl status pulseaudio.service gives me :
● pulseaudio.service — PulseAudio Daemon Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled) Active: active (running) since dim. 2017-06-11 09:57:58 CEST; 1min 19s ago Main PID: 586 (pulseaudio) CGroup: /system.slice/pulseaudio.service └─586 /usr/bin/pulseaudio —system —realtime —disallow-exit —no-cpu-limit
Thanks for helping though

Edit :
The debug (main.py) shows me a bunch of errors (See main post) but at least Alexa «works».
Tried reinstalling VLC (as root and all) because the first error appears to be VLCHandler but still nothing when AlexaPi boots up normally.

Hello,
How do you start AlexaPi?
You must start it as pi alexapi user, not as root .

@Hinoy @EmerickH AlexaPi (the service) is run under the user alexapi so you need to make sure you do sudo adduser alexapi pulse-access .

@EmerickH I do start it as Pi, sadly not helping
It just runs on boot, I followed the tutorial.
@renekliment I tried that, didn’t do much sadly.
Just to let you guys know, I figured it might not come from how my sounds cards and all because Alexa starts, works for a bit, stops working but 2 HOURS later she finally react and become fluid again answering to everything smoothly. Then it crashes again at some point.
juin 12 22:18:43 raspberrypi python[789]: INFO: AVS token: Obtained successfully juin 12 22:18:43 raspberrypi python[789]: ERROR: URLError: [Errno 111] Connection refused juin 12 22:18:44 raspberrypi python[789]: ERROR: URLError: [Errno 111] Connection refused juin 13 14:02:44 raspberrypi python[789]: ERROR: URLError: [Errno 111] Connection refused juin 13 14:02:44 raspberrypi python[789]: ERROR: URLError: [Errno 111] Connection refused juin 13 14:02:44 raspberrypi python[789]: ERROR: URLError: [Errno 111] Connection refused juin 13 14:02:54 raspberrypi python[789]: INFO: AVS token: Requesting a new one juin 13 14:03:04 raspberrypi python[789]: INFO: AVS token: Obtained successfully
It’s really random and makes no sense to me

Eveything now works in debug mode. But not in AlexaPi service. Whats the difference between the two?

Yes @renekliment, you’re right.
Effectively the AlexaPi service uses alexapi user and when you start it manually, it’s with the pi user, that’s the difference.
@Hinoy, try sudo adduser alexapi audio

I figured part of the reason for the issue and I guess it’s linked to what you guys said !
Basically when the Raspberry boots up it fails but when I do a restart of the service it’s back to normal (like in debug everything works)
I’ll do that in the next hour or so and come back before, hopefully, closing the issue (thanks to both of you)

alexapi was already part of both pulse-access and audio. I even added to every group pi as except users, not enough, same error. I m going to keep digging on my side.

@Hinoy can you give us your AlexaPi.service file?
It should be in /etc/systemd/system/ /usr/lib/systemd/system/AlexaPi.service

I am sorry there is no such thing here . I have a .service (including pulseaudio) but no alexapi.service
BUT I have a alexapi.service.d (a folder), which is empty.
(FYI the installer was set to default location)
But anyway I tried a locate AlexaPi.service and found those :
pi@raspberrypi:

$ sudo updatedb pi@raspberrypi:

$ locate AlexaPi.service /etc/systemd/system/AlexaPi.service.d /etc/systemd/system/default.target.wants/AlexaPi.service /opt/AlexaPi/src/scripts/AlexaPi.service /usr/lib/systemd/system/AlexaPi.service
I assumed it was the second one so here it is :
https://pastebin.com/WsFiZt2Y
Shall I modify the user to pi to make things easier ? Or is alexapi user really usefull ?
Thanks for everything by the way (Thanks to you, and what you told me about user perm, I got alexa working for my college exam with a service restart as pi)

@Hinoy, no sorry it’s the /usr/lib/systemd/system/AlexaPi.service one (it was very tired 😄 )

If it’s not working, look at theses lines in /usr/lib/systemd/system/AlexaPi.service :

If ?? is alexapi , try to change it to pi , if it’s not change to alexapi .
Don’t forget to do systemctl daemon-reload after changing!

Not very clean but you can try to add in /etc/rc.local :

before exit 0 line

Not working (same error as before really).

Not working with the following errors : (Never seen them before)
juin 17 17:18:12 raspberrypi systemd[1]: Started Alexa client for all your devices. juin 17 17:18:18 raspberrypi python[850]: Home directory not accessible: Permission denied juin 17 17:18:18 raspberrypi python[850]: Home directory not accessible: Permission denied juin 17 17:18:46 raspberrypi python[850]: Home directory not accessible: Permission denied juin 17 17:18:46 raspberrypi python[850]: Home directory not accessible: Permission denied juin 17 17:18:46 raspberrypi python[850]: INFO: Magic Mirror HTTP Server — :5055 juin 17 17:18:46 raspberrypi python[850]: INFO: Checking Internet Connection . juin 17 17:18:47 raspberrypi python[850]: INFO: Connection OK juin 17 17:18:47 raspberrypi python[850]: INFO: AVS token: Requesting a new one juin 17 17:18:49 raspberrypi python[850]: INFO: AVS token: Obtained successfully juin 17 17:18:49 raspberrypi python[850]: ERROR: URLError: [Errno 111] Connection refused juin 17 17:18:49 raspberrypi python[850]: Home directory not accessible: Permission denied juin 17 17:18:50 raspberrypi python[850]: ERROR: URLError: [Errno 111] Connection refused juin 17 17:18:50 raspberrypi python[850]: Home directory not accessible: Permission denied
That’s a new error.

Not working(Same error as before), I assume because the restart happens too early (service not started already) because restarting after works though.

Closing due to inactivity. Feel free to reopen.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

pulse audio output error: PulseAudio server connection failure: Connection refused

live@pra64:~$ pulseaudio --start
E: [pulseaudio] main.c: Не удалось запустить демон.

Страницы: [1]   Вверх

Moderator: Forum moderators

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/
ldconfig
apulse
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/librtaudio.so.6 CubicSDR

[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libairspySupport.so)
  duplicate entry for airspy (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libairspySupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libaudioSupport.so)
  duplicate entry for audio (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libaudioSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libbladeRFSupport.so)
  duplicate entry for bladerf (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libbladeRFSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libHackRFSupport.so)
  duplicate entry for hackrf (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libHackRFSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libLMS7Support.so)
  duplicate entry for lime (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libLMS7Support.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libosmosdrSupport.so)
  duplicate entry for osmosdr (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libosmosdrSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libRedPitaya.so)
  duplicate entry for redpitaya (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libRedPitaya.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libremoteSupport.so)
  duplicate entry for remote (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libremoteSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librtlsdrSupport.so)
  duplicate entry for rtlsdr (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librtlsdrSupport.so)
[ERROR] SoapySDR::loadModule(/usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libuhdSupport.so)
  duplicate entry for uhd (/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/libuhdSupport.so)

[ERROR] avahi_service_browser_new() failed: Bad state

root# apulse gqrx
Controlport disabled
"Pulseaudio error: Connection refused"