Bug 1305 - QT 5.10.1 and 5.11.2 breaks device list updates on MacOS
Summary: QT 5.10.1 and 5.11.2 breaks device list updates on MacOS
Status: RESOLVED FIXED
Alias: None
Product: PulseView
Classification: Unclassified
Component: UI (show other bugs)
Version: unreleased development snapshot
Hardware: x86 Mac OS X
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-11 14:48 CEST by vpalmu
Modified: 2022-11-27 11:30 CET (History)
3 users (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vpalmu 2018-10-11 14:48:11 CEST 
Tested with pulseview version 0.5.0-git-8e9e525 on osx 10.12.6 Sierra. Tested with fx2lafw, dreamsourcelab-dslogic and rigol-ds (over network) drivers.

When compiled with qt 5.10.1 from homebrew the new device selection has a bug where, after selecting the driver and options and hitting "Scan for devices using the driver above" button, the device selection box contents don't refresh until I alt-tab to another window.

This doesn't happen with qt 5.9.3 from homebrew, also qt 5.5 doesn't suffer from this bug.

Reproduce:
1 Install qt 5.10.1 from homebrew
2 clone sigrok-util
3 edit the sigrok-osx-native script and change QTVER to "qt"
4 compile
5 open pulseview
6 connect a supported device
7 go to the connect to device screen
8 select driver and options
9 hit scan devices
10 wait
11 alt-tab to another application and back
12 observe that the device has appeared on the list
Comment 1 vpalmu 2018-10-11 15:37:10 CEST 
I was unable to test with qt 5.11.2 when I installed it with homebrew it also pulled glib 2.58.2 due to dependencies and as per bug #1281 linking with glib 2.58 fails on osx.
Comment 2 vpalmu 2018-10-11 15:54:08 CEST 
Forcing homebrew to use older glib 2.56.1 I was able to compile pulseview with qt 5.11.2 and sadly the same bug still affects it. So currently all versions of qt >5.9.3 seem to suffer from this bug.
Comment 3 Gerhard Sittig 2018-10-11 18:02:36 CEST 
This appears to be an issue in upstream Qt, filed on 2018-09-28
https://bugreports.qt.io/browse/QTBUG-70599
Comment 4 Ryan Govostes 2019-03-18 17:32:34 CET 
(In reply to Gerhard Sittig from comment #3)
> This appears to be an issue in upstream Qt, filed on 2018-09-28
> https://bugreports.qt.io/browse/QTBUG-70599

The upstream bug appears to be resolved in Qt 5.12. I built Pulseview against Qt 5.12.1, and attached a device that gets automatically detected as "Saleae Logic". I then opened the "Connect to Device" window and selected the "Saleae Logic Pro" driver, "USB" interface, and clicked "Scan".

Nothing appeared in the device list, even after command-tab to another app and back.

In the console, I do see:

    sr: usb: Neither VID:PID nor bus.address was specified.

So it's inconclusive to me whether Qt 5.12 resolves the problem or not.
Comment 5 Uwe Hermann 2019-03-18 17:35:19 CET 
The correct driver for a Saleae Logic is "fx2lafw", saleae-logic16 or saleae-logic-pro are different drivers for different hardware.
Comment 6 Ryan Govostes 2019-03-18 18:46:17 CET 
(In reply to Uwe Hermann from comment #5)
> The correct driver for a Saleae Logic is "fx2lafw", saleae-logic16 or
> saleae-logic-pro are different drivers for different hardware.

It's the same result selecting that driver. Same console message also.
Comment 7 vpalmu 2022-11-27 11:30:51 CET 
No longer an issue with the nightly builds nor with the Qt6 version being worked on.