[BUG] Issues with shown packages (malfunctionning source filtering?)
Please confirm these before moving forward
- [X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
- [X] I have checked the FAQ section for solutions
- [X] This issue is about a bug (if it is not, please use the correct template)
Describe your issue
On start-up 'Installed Packages' is displaying only PIP packages even though Winget + Local are selected as well.
If I then deselect Local, Winget packages are also displayed:
I can then select Local to see all three:
I tried resetting Settings but problem persists. Customised Settings:
Steps to reproduce the issue
No response
WingetUI Log
[WingetUI Log.txt](https://github.com/marticliment/WingetUI/files/14468695/WingetUI.Log.txt)
Package Managers Logs
[WingetUI Package Managers.txt](https://github.com/marticliment/WingetUI/files/14468696/WingetUI.Package.Managers.txt)
Relevant information
No response
Screenshots and videos
No response
I have the same issue, although for me it seems to me caused by the Search mode options in the Filters dropdown rather than the Sources dropdown.
What happens is that on startup 3.0-beta0 opens at the Discover Packages tab. Package window is empty. The Filters dropdown is already open and it shows these selections underneath Search mode:
Package Name
Package ID
Both
Show Similar Packages
Exact Match
None of these are pre-selected. If I go to the Installed Packages tab the Filters dropdown closes and only Pip and PSWindowsUpdate packages are showing. I then have to open the Filters dropdown. The Show Similar Packages and Exact Match options have disappeared. None of the other three options are pre-selected, which seems to be the problem. I have to click on Package Name or Package ID or Both to get all my packages to show.
Marti, can you change WingetUI's behaviour so that one of these three options is already pre-selected? Thanks.
...for me it seems to me caused by the
Filtersdropdown ...
Can confirm that selecting a Search mode in Filters causes all packages to be displayed as expected.
Switching any source off / on also works for me.
@marticliment Confirm as having the same issue on this end
With the release of 3.0.0.-beta1 three days ago, I no longer have this issue. All my packages are displayed when I select the Installed Packages tab. When I open the Filters dropdown, under Search mode I see that Both has been pre-selected.
I am still able to reproduce the issue, so I will maintain this issue open
This issue has been fixed as of 3.1.0