Bug 1635905 - Emacs is marked as proprietary software in Gnome-Software
Summary: Emacs is marked as proprietary software in Gnome-Software
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 21:21 UTC by seb
Modified: 2019-01-14 09:13 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-04 09:04:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (70.94 KB, image/png)
2018-10-03 21:21 UTC, seb
no flags Details
screenshot 2019-01-05 23:04:01 (75.51 KB, image/png)
2019-01-05 22:06 UTC, seb
no flags Details

Description seb 2018-10-03 21:21:39 UTC
Created attachment 1490324 [details]
screenshot

Description of problem:

Emacs is marked as proprietary software in Gnome-Software

See attached screenshot.


Version-Release number of selected component (if applicable):

1:26.1-6.fc29

Comment 1 Jan Synacek 2019-01-04 09:04:10 UTC
I don't see it in Fedora 29. It was probably fixed in gnome-software.

Comment 2 seb 2019-01-05 22:04:48 UTC
I still see it in Fedora 29.
I attach a screenshot taken right now.

Comment 3 seb 2019-01-05 22:06:02 UTC
Created attachment 1518730 [details]
screenshot 2019-01-05 23:04:01

Comment 4 Jan Synacek 2019-01-14 09:13:59 UTC
I installed F29 from scratch and I don't see it. You can try the following to see if anything changes (I tried to order them from least intrusive to most):
- Change the localization to US.
- Clear the gnome data and settings. (I'm not sure where exactly gnome stores everything, but ~/.config should be a good start.)
- Similarly, just to make sure all the settings are not applied, move your home folder to a temporary directory and create a new one.
- Clear everything under /var/cache/.
- Reinstall F29 on a reformatted disk.


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