IC-705 WiFi to rigctl

in order to dissect the problem, need to know what the cause is and what not.
So first of all selecting the linux environment where closed source drivers are being used.

the windows/surface thig is something different. So if you really want some help, use the open source drivers and re-report. WFVIEW itself presents a picture to a device that shows inges and doesn not in any way control parts of the window you see itself.

I can be QT, it can be your drivers, it can be you yourself.

WFVIEW has been installed far more that 2000 tmes without these issues. I have done dozens without these issues including in several different virtual environments and different linux operating systems as well as windows.

The other team members have done the same with mint, other debian based versions. As far as I know it’s never been reported.

So again: if you want some help, I need to rule out what it’s causing and what not.

The linux envs were both on the pre-built binries as well as built by hand (not using scripts).
The windows envs are all doanloaded from the wfview site.

So again, revert to the open source nvidia drivers and give feedback. And like others have hinted at: be 100% sure you are NOT using wayland because that’s a box of issues you don’t want to know of. (that one DOES produce black screens / parts and has other failures too).

Please send us a log file so that we can see how the program is initializing.

Can you also confirm that this happens both with and without “Use System Theme” checked? Might need to save settings and re launch just to be sure. Stylesheets can be tricky.

From above: “Microsoft Surface Pro’s do not have nVidia GPU’s, cannot use DaVinci Resolve, and no drivers other than those in a clean install are in use.”

As I have mentioned, this problem takes place on 8 diverse machines with varying capabilities, some of which do not have nVidia GPU’s , drivers, or any proprietary drivers of any kind installed. I listed DaVinci Resolve Studio because it uses Qt, is the most graphically intensive program I have ever used, and it’s working just fine on all the machines that can support it. The Surface Pro’s most certainly do not.

Error log from Surface Pro, Mint 21.3 after intermittent black screen and disconnect:
https://termbin.com/6f3x

2 things, firstly you have Opus codec selected, this is pointless when connecting to the radio server as it is only supported by the wfview server, it isn’t likely to be causing this issue, but worth selecting one of the other codecs.

Also you are seeing lots of retransmissions, this means you are getting significant packet loss on your wifi network, depending on the cause of the packet loss, this could potentially cause weird things to happen (including the black screen possibly). UDP audio streaming requires a VERY stable network connection, this is something that is quite difficult to achieve with 2.4 GHz wifi, especially if using consumer-grade wireless access points. You really want to reduce the amount of packet loss though!

You could try reducing the sample rate 16,000 is fine for most things (the default is 48,000), and maybe change to the uLaw codec as that will require ½ the bandwidth of PCM (when Opus isn’t supported, wfview will switch to PCM).

Thanks

Phil

~WRD0001.jpg

Phil,

I set the 705 to Access Point, and connected a Surface directly to 192.168.59.1, which is hard coded on the 705.

I set audio to uLaw 1 ch 8bit, and sample rate to 8000.

No lost UDP packets are in the log, but the screen went black within 10 seconds of connecting. Then this, and wfview is still running. Print Scr restores the full screen for a while.

https://termbin.com/8l5a

ok, so you don’t want to use open source drivers to rule out possible issues at all. I see one common thing: the OS you use. (I was under the impression you were using windows)

Today I have on a random laptop installed the latest mint (multiboot) – used the source and script (which is something I normally don’t do) and it ran for hours and hours with exactly zero issues.

I also did this on the laptop I type this on, on vmware workstation 17.5.1 – same stuff zero issues.

Trouble shooting starts with ruling out what it is not, and from what I read, you don’t want to my help at all. I have seen this before here, with others and it leads to draining energy.

I’m out of this thread.

I have a Microsoft Surface Pro 3 running a stock Mint 21.3. The Surface has only built-in Intel® HD Graphics 4200.

I have not installed, nor am I aware of proprietary drivers for a Surface. Please tell me which non open source drivers you feel should be removed?

I assume all these are running mint with the 5.15xx kernel? Would you try upgrading one of them, like one of the surface machines, to the 6.2 kernel? There are a number of display issues with 5.15 and qt5 as well as a number of documented issues with nvidia 535 and qt5. It would be best if you could revert one of the other machines with nvidia 535 to Nouveau. It would be very useful if you could do what I suggested earlier and set QT_DEBUG_PLUGINS to 1 to see particularly which platform abstraction layer is in use. It would also be helpful it you would run “inxi -Frzzzsy” and post it here. Also are you using any GTK themes that you have installed? GTK based desktops and QT apps can have some unexpected conflicts.

THIS!

Been a victim of this in the past. Something as bland as Window decorations making the entire desktop experience glitch is more likely than You think.

The screenshots do look like some kind of Compositor issue. Is there any useless eye-candy enabled in Mint?

Bob,

I think it would be much more productive to mess with the Surfaces than with the nvidia machines. The nvidia laptops have dual graphics which does not play at all well with nouveau, the desktops are full of added programs and in constant use, and my wife’s computers are strictly off limits.

The Surfaces are not otherwise used so are fair game. I will look into installing the 6.2 kernel, and try the QT setting later today.

This is the inxi from one of the Surfaces:

System:
  Kernel: 5.15.0-101-generic x86_64 bits: 64 Desktop: Cinnamon 6.0.4
    Distro: Linux Mint 21.3 Virginia
Machine:
  Type: Laptop System: Microsoft product: Surface Pro 3 v: 1
    serial: <superuser required>
  Mobo: Microsoft model: Surface Pro 3 v: 1 serial: <superuser required>
    UEFI: American Megatrends v: 3.11.2550 date: 06/12/2018
Battery:
  ID-1: BAT0 charge: 35.8 Wh (100.0%) condition: 35.8/42.2 Wh (84.9%)
CPU:
  Info: dual core model: Intel Core i3-4020Y bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1487 min/max: 600/1500 cores: 1: 1463 2: 1493 3: 1497
    4: 1497
Graphics:
  Device-1: Intel driver: i915 v: kernel
  Device-2: Microsoft LifeCam Front type: USB driver: uvcvideo
  Device-3: Microsoft LifeCam Rear type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 2160x1440~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 4200 (HSW GT2)
    v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2
Audio:
  Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
  Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.0-101-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Marvell 88W8897 [AVASTAR] 802.11ac Wireless driver: mwifiex_pcie
  IF: wlp1s0 state: up mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
  IF: enx00e04c68014a state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Marvell Bluetooth and Wireless LAN Composite Device type: USB
    driver: btusb
  Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 2.1
Drives:
  Local Storage: total: 126.7 GiB used: 87.66 GiB (69.2%)
  ID-1: /dev/sda vendor: SK Hynix model: HFS128G3AMNB-2200A size: 119.24 GiB
  ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade
    size: 7.45 GiB
Partition:
  ID-1: / size: 116.32 GiB used: 87.01 GiB (74.8%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com virginia main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/opencpn-opencpn-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/opencpn-opencpn-jammy.gpg] https://ppa.launchpadcontent.net/opencpn/opencpn/ubuntu jammy main
Info:
  Processes: 231 Uptime: 1d 17h 27m Memory: 3.73 GiB used: 1.51 GiB (40.4%)
  Shell: Bash inxi: 3.3.13

Focusing on one system will help work this out and the surface is good because it doesn’t have the dual GPU. Can you post the /var/log/Xorg.0.log. Also do you see any log events in dmesg when the display issue occurs? Are you using startx on the surfaces or letting the desktop start automatically? If you are using startx manually will you send that output?

How many screens do you have connected?

No log events at all in dmesg, Xorg, or wfview.

One. There have been more on the desktops, but not at present.

This is a complicated problem. In order to find a solution, I think the problem must be simplified. wfview is has a great many balls in the air at the same time.

It could simply go away with an update of any of a number of dependents.

To simplify, the various functions, especially audio, need to be able to be individually disabled. That need will only increase as the program grows.

If there is a way to shut down audio, please let me know.