Description of problem: when invoking "/usr/share/applications/org.gnome.Shell.PortalHelper.desktop" returns "404 Not Found" when entering the required URL : http://nmcheck.gnome.org/, return the 404 Not Found response suggest that this package be removed. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3.
Source RPM: when invoking from "/usr/share/applications/org.gnome.Shell.PortalHelper.desktop" returns "404 Not Found" => (none)Whiteboard: (none) => MGA10-TOO
Thanks for the report. I got nowhere with /usr/share/applications/org.gnome.Shell.PortalHelper.desktop in a terminal. But the second link did indeed return 404. Assigning to Gnome.
Assignee: bugsquad => gnome
By principle we target Cauldron, and set MGA9TOO if we can fix it there too. You mention removing a package, we can not do that in a released Mageia, or how did you mean remove? To remove a dependency for of one package for another could be OK.
Whiteboard: MGA10-TOO => MGA9TOOCC: (none) => friVersion: 9 => Cauldron
(In reply to Morgan Leijström from comment #2) > By principle we target Cauldron, and set MGA9TOO if we can fix it there too. > > You mention removing a package, we can not do that in a released Mageia, or > how did you mean remove? > > To remove a dependency for of one package for another could be OK. I meant: remove it from cauldron. I put the MGA9-TOO as the issue is also in MGA9, should anyone not running cauldron wish to check. aside. I am working through cauldron finding as many repairable issues as I can in anticipation of a short Mga10 pre-release iso testing cycle. Things like missing icons, applications that dont work; either through a Mageia packaging / dependency / library issue, or in this case, an external resource no longer being available. I am aware that cauldron is a moving target, but it is getting very much more stable.
Thank you for all testing :) OK. So for now I add this to the tracker bug for packages to obsolete for mga10. We still wish final verdict from GNOME maintainers: fix or remove. Or are we simply not using it correctly?
Status comment: (none) => Obsolete in mga10?Blocks: (none) => 32127
(In reply to Morgan Leijström from comment #4) > Thank you for all testing :) > > OK. > > So for now I add this to the tracker bug for packages to obsolete for mga10. > > We still wish final verdict from GNOME maintainers: fix or remove. > Or are we simply not using it correctly? the resource it attempts to access is no longer current, so yes, fix or remove
it seems the online resource is now available
Hardware: All => x86_64Status: NEW => RESOLVEDResolution: (none) => WORKSFORME