Bug 1769967 - gnome-software is recommending non-free software with large colourful banners
Summary: gnome-software is recommending non-free software with large colourful banners
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-07 20:02 UTC by Colin Macdonald
Modified: 2020-09-14 16:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
If this bug requires documentation, please select an appropriate Doc Type value.
Last Closed: 2020-09-14 16:01:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of propietary software banner (97.69 KB, image/png)
2019-11-07 20:02 UTC, Colin Macdonald
no flags Details

Description Colin Macdonald 2019-11-07 20:02:53 UTC
Created attachment 1633789 [details]
screenshot of propietary software banner

Gnome Software is showing non-FLOSS software in a very prominent way: first screen, big colourful banner under Featured Applications.

Its mostly likely that this is b/c I have enabled the "flathub.org" flatpak repo and so its not really Fedora's fault per se.  But even so, surely Gnome Software should actively only Free/Open Source Software?  (even if it makes it possible to search for and install proprietary software).

Comment 1 Michael Catanzaro 2019-11-24 22:13:16 UTC
It's not coming from Flathub. I discovered: https://gitlab.gnome.org/GNOME/gnome-software/issues/749

Comment 2 Chris Murphy 2019-11-24 23:53:33 UTC
Workstation WG tracking issue
https://pagure.io/fedora-workstation/issue/111

Comment 3 Richard Hughes 2020-09-14 16:01:23 UTC
> surely Gnome Software should actively only Free/Open Source Software

Na, not if you installed a repo with nonfree software in it.


Note You need to log in before you can comment on or make changes to this bug.