Hide Forgot
Description of problem: I installed package rhn-setup na Fedora 25, but I don't register system to Spacewalk/Satellite and after it the service PackageKit Daemon stoped work: >> systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: failed (Result: core-dump) since Út 2016-11-22 11:45:25 CET; 27s ago Main PID: 7153 (code=dumped, signal=TRAP) ... systemd[1]: Starting PackageKit Daemon... ... PackageKit[7153]: daemon start ... packagekitd[7153]: You need to register this system by running `rhn_register` before using this option ... packagekitd[7153]: failed to setup context: Proces potomka skončil s kódem 1 ... systemd[1]: packagekit.service: Main process exited, code=dumped, status=5/TRAP ... systemd[1]: Failed to start PackageKit Daemon. ... systemd[1]: packagekit.service: Unit entered failed state. ... systemd[1]: packagekit.service: Failed with result 'core-dump'. Version-Release number of selected component (if applicable): PackageKit-1.1.4-1.fc25.x86_64 How reproducible: always Steps to Reproduce: 1. dnf install rhn-setup 2. systemctl restart packagekit.service 3. systemctl status packagekit.service Actual results: servive packagekit.service doesn't start when system is not register Expected results: service start if the system is not registered
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
This issue is resolved in Fedora 27.