Bug 959793
Summary: | isdn.service failed to start on boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Lightfoot <BobLfoot> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | ignatenko, johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, robatino, systemd-maint, than, twegener, vpavlin, west, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | systemd-201-2.fc18.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-15 08:34:13 UTC | 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: | |||
Bug Depends On: | |||
Bug Blocks: | 834090 |
Description
Robert Lightfoot
2013-05-05 19:02:03 UTC
systemd enables isdn by default, reassign to correct component (In reply to comment #1) > systemd enables isdn by default, reassign to correct component So systemd should not enable isdn by default? It is in this (outdated) list https://fedoraproject.org/wiki/Starting_services_by_default Should it have some condition where it doesn't even try to start unless it's configured? Not sure what the bug is about. If it is about isdn enabling itself by default after installation, then this should be fixed in the isdn package (and it should mirgate to the recommended macro-based spec file snippets). If it is about isdn failing to start, then this also needs to be fixed in the isdn package. Hence, reassigning. (In reply to comment #3) > Should it have some condition where it doesn't even try to start unless it's > configured? From looking at /usr/libexec/isdn, this should work: ConditionPathExists=/etc/sysconfig/isdncard (In reply to comment #4) > If it is about isdn enabling itself by default after installation, then this > should be fixed in the isdn package (and it should mirgate to the > recommended macro-based spec file snippets). isdn4k-utils.spec already uses the macros. So I guess comment #1 is a request to delete this line from 90-default.preset: enable isdn.service AH, sorry, I missed that, isdn.service is indeed listed. Hmm, should we remove it? ISDN maintainers, what's your take on this? I'd be happy to remove it from the preset file. Lennart, ISDN card is not configured during the installation, imo it doesn't make sense to enable it by default. isdn.service is enable in 90-default.preset, so it should be fixed in systemd package, please remove isdn.service from preset file. reassign to correct component thanks OK, I disabled isdn.service in the preset fiels for F18 and F19. This will be included in the next rebuild. Clean install FC19 Beta TC4. Bug present. (In reply to comment #9) > Clean install FC19 Beta TC4. > Bug present. This is expected. F19 Beta TC4 has systemd-203. This bug is fixed in systemd-204-2.fc19. https://admin.fedoraproject.org/updates/FEDORA-2013-7859/systemd-204-2.fc19 systemd-201-2.fc18.7 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.7 systemd-201-2.fc18.7 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 914871 has been marked as a duplicate of this bug. *** Is this a regression? I am running FC20-3.12.6-300. I noticed the message FAILED TO START ISDN SERVICES after having troubles updating nfs-utils and firefox - both of which occurred during a yum update today that failed to remove firefox and nfs-utils. I got past that by using the command setenforce permissive, then successfully rebooted after removing the downrev firefox version. It was after that reboot that I noticed the above message. |