Bug 2171200
| Summary: | Entry in /usr/lib/systemd/system/abrtd.service causes systemd to show livesys.service error even when livesys disabled/removed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Dodson <jwadodson> |
| Component: | abrt | Assignee: | Michal Srb <msrb> |
| Status: | ASSIGNED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 38 | CC: | abrt-devel-list, abrt-sig, mgrabovs, michal.toman, msrb |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Still a problem in FC38 I commented this line out of /etc/systemd/system/multi-user.target.wants/abrtd.service After=livesys.service to work around the problem, it's back in the version of that file dated 2023 Jun 30 10:00 abrt-2.17.1-1.fc38.x86_64 python3-abrt-2.17.1-1.fc38.x86_64 ? Can someone PLEASE fix it or comment it out in the distributed version? Can we make it conditional? Thank you for the bug report. The fix will be included in the next abrt release ;) Any idea when that will be? Oh & also when /var/tmp/abrt will not be "recreated" (if it's now unused)? If removed /var/tmp/abrt is recreated each night following a systemd restart. |
Description of problem: Entry in /usr/lib/systemd/system/abrtd.service causes systemd to show livesys.service error even when livesys disabled/removed. # livesys.service has been added because of live distributions mounting tmpfs # to /var/tmp after abrtd.service was started which was hiding /var/tmp/abrt # which was created before the mount to tmpfs happened After=livesys.service Version-Release number of selected component (if applicable): abrt-2.15.1-6.fc37.x86_64 (This is probably really a systemd problem, 251.11-2.fc37) How reproducible: Always unless that line is commented out. Steps to Reproduce: 1. Remove all trace of livesys after installation (otherwise it generates other "messages" by just being there & it should be removed right?). 2. systemctl -all |grep livesys livesys.service not-found inactive dead livesys.service 3. The "problem" is also manifested by Actual results: Uninstalled systemd objects should not give an error status Expected results: The ability to run systemctl -all & see no errors/services in error states, when you've ironed out all the mysteries & unnecessary components. Additional info: It would seem that systemd needs a better system of ordering or checking for unused/installed components that require ordering or "Conflicts=" (which also generate a similar effect. Or merely "noting silently that an uninstalled/non-conflicting package does not need to be considered in it's logic" - but that's probably a recipe for more subtle bugs. BTW, in the systemctl documentation there is no mention of "Yellow" dots - are they real in the systemctl output or have I screwed my terminal colour scheme? It seems they are services that "ain't really there". Is this too philosophical?