[Fedora Rawhide] Sometimes works sometimes doesn't with weird error messages about welle.io HOT 11 CLOSED

I assume there is an electrical problem in your NooElec device in combination with a rtlsdr driver issue. Anyway, I close this issue for now and if you have more information we can reopen it.

from welle.io.

Could be the same issue as #64 – different OSes different error reports.

from welle.io.

I suppose QT tries to use Pulse and Pulse somehow fails on Fedora. Does other multimedia software e.g. VLC is working?

from welle.io.

The AppImage behaves a little differently.

My build shows the connect failed, and no matter how much tuning gives no further output on the console, but the tune seems good according to the UI.

The AppImage I downloaded behaves the same on startup, but then on a tune behaves as my build does on Debian. Tries to use Raw audio and fails.

PulseAudioService: pa_context_connect() failed
Audio: Raw audio format not supported by backend, cannot play audio.
RadioController: Number of gain steps: 28

from welle.io.

Are other audio output software is working e.g. VLC or Firefox with Youtube? I assume something is wrong in your pluse installation.

from welle.io.

Sound is working entirely fine with Rhythmbox, Chrome, Firefox, etc. Thus PulseAudio appears to be working fine.

from welle.io.

Mh, maybe something goes wrong with the default audio device selection. You can try just to comment out line 76 - 81.

from welle.io.

This may be an Heisenbug :-( I just tried running it on Fedora and it works fine. This is bizarre. But good.

from welle.io.

Closing this for now. Not tried on Debian recently. If it has a problem I'll reopen or create a new issue.

from welle.io.

A definite Heisenbug here. Welle.IO worked this morning. Now when I start it QtAudioPulse registers with the Fedora sound system, but when I tune, I now get:

r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=05 len=1
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
r82xx_write: i2c wr failed=-4 reg=17 len=1
r82xx_set_freq: failed=-4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4

from welle.io.

And now it is working fine on Fedora Rawhide. I am assuming there is a state of the hardware that is being reached that Welle.IO is not able to reset.

OK, I touched the NooElec unit and the sound stopped and Welle.IO reports an error from the device. dmesg not reporting any change of state. Restart Welle.IO and everything is fine. This is getting quite annoying. Clearly something is right, but there are too many instabilities.

Or maybe I am just getting over hyper. :-)

from welle.io.