Bug 844556
Summary: | multi-seat udev rules not fully set up prior to multiuser.target | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ravikiran Rajagopal <ravi> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | johannbg, lnykryn, lpoetter, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-11 13:30:52 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: |
Description
Ravikiran Rajagopal
2012-07-31 04:55:22 UTC
udev-settle is kinda obsolete these days. gdm should have no problems with seats that appear during runtime (rather then before gdm is started). When this fails, does the property show up on the device if you check with "udevadm info -q /sys/..."? I am not sure that gdm is the problem. For example, the following, saved as /etc/systemd/system/extra-wait.service and then enabled via systemctl, "fixes" the problem with 100% reliability: =========== [Unit] Description=Extra wait for udevadm to settle After=basic.target udev-settle.service Before=display-manager.service systemd-logind.service multi-user.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sleep 60 [Install] Requires=basic.target RequiredBy=display-manager.service systemd-logind.service multi-user.target =========== Without the workaround above, when it fails, I can see via udevadm that the devices have the correct properties (i.e., are assigned to the right seat). Is there any more information I can supply? I am not sure that gdm is the problem. For example, the following, saved as /etc/systemd/system/extra-wait.service and then enabled via systemctl, "fixes" the problem with 100% reliability: =========== [Unit] Description=Extra wait for udevadm to settle After=basic.target udev-settle.service Before=display-manager.service systemd-logind.service multi-user.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sleep 60 [Install] Requires=basic.target RequiredBy=display-manager.service systemd-logind.service multi-user.target =========== Without the workaround above, when it fails, I can see via udevadm that the devices have the correct properties (i.e., are assigned to the right seat). Is there any more information I can supply? The slep should normally not be necessary, as gdm should notice when seats become available and gain the graphical property. How did you create the rules? Can you create these rules with "loginctl attach"? Can you please paste the output of "udevadm info /dev/dri/card0" (and similar for the other card) once when it is incorrectly assigned, and once when it is correctly assigned? Closing due to lack of response. Apologies, I no longer have access to that machine (as the motherboard died). If the problem persists when I set up a new system, I will open a new bug report. Apologies. |