Created attachment 1405194 [details] screenshot Description of problem: As shown in the attached picture. Version-Release number of selected component (if applicable): gnome-software-3.27.92-0.fc27.kalev_copr0.x86_64 PackageKit-1.1.9-0.fc27.kalev_copr0.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1405197 [details] journal
Looks like something going wrong in the the snap plugin. I don't work on the snap code, can you file this upstream at https://gitlab.gnome.org/GNOME/gnome-software please?
Sure,will report a bug later,but it seems that there is no Pycharm shown when I try to reproduce this in another VM now.There is no snap subpackage pulled in any more,maybe cause you have disabled it from your repo?
Created attachment 1405659 [details] screenshot
I haven't changed the packaging yet, but talked to Richard and I think we're going to disable the dep that pulls it in. It's a conditional dep, only installing gnome-software-snap when someone has snapd installed. I guess you had that in your other installation.
According to the screenshot you don't have the gnome-software-snap package installed right? So that's why Pycharm is not showing in GNOME Software?
you must mean comment4.yes,there is no gnome-software-snap on that test machine,but I'm also not able to install Pycharm successfully on a machine with gnome-software-snap installed.Please see the screenshot from comment0.
Thanks Inie! I didn't notice that. Due to <insert technical reasons> [1] [2] you can't install snaps using classic confinement (i.e. not sandboxed) on Fedora at this time. I'm trying to work out the best way of handling this, I think there's two options: 1. Intercepting the error from snapd and showing something appropriate to the user. Would you be happy with a message along the lines of "This snap requires classic confinement which requires additional support to be enabled <web link>". And the web link would go to a page that explains how to make the symlink and why. 2. Disabling classic confined snaps in GNOME Software if we detect we can't install them. Needs a GNOME software fix and possibly a snapd fix [3] to make this nice. Has the downside of snaps you know exist (shown on webpages / links from developers website) not being visible. [1] https://bugs.launchpad.net/snapd/+bug/1736939 [2] https://forum.snapcraft.io/t/classic-snaps-not-working-on-fedora-27-and-others/2636 [3] https://github.com/snapcore/snapd/pull/4805
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.