Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1679801
| Summary: | udev not tagging efifb fb0 as master-of-seat | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeremy Linton <jeremy.linton> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | extras-orphan, jonathan, lnykryn, msekleta, pbrobinson, ssahani, s, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-02 20:07:56 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: | 245418 | ||
BTW: SDDM & the rpi in this config works in a basic F29 install, its only after doing an upgrade does it start to fail. Not sure if it was SDDM that caused the problem or systemd-udev or something else irritating the problem (its not the kernel, booting the older kernel displays the same problem). udev is now part of systemd As this problem was reproduced on x86, was causing a lot of problem, I'm going to dupe this against the gdm changes to remove the master-of-seat check. *** This bug has been marked as a duplicate of bug 1683197 *** |
Description of problem: It seems that the window managers (sddm/gdm) are now activly checking the CanGraphical property from logind. This means they fail to start X on seats that don't have this properly. The efifb device exports a perfectly functional graphical framebuffer which tends to get taken over by native linux drivers (amdgpu/etc). If that doesn't happen then X can go ahead and start on the efifb device anway but with fixed resolution/color depth. AKA switching the DM to xdm allows normal login. Version-Release number of selected component (if applicable): F29, sddm 0.18.0-1, systemd-udev 239-11. kernel-4.20.10-200 How reproducible: 100% with UEFI-Rpi firmware and latest fedora. I suspect its probably reproducable on any UEFI system where a dedicated kernel module doesn't take over the efifb device. AKA modprobe.blacklist=amdgpu or noveau leaves the efifb in place, and it never gets cangraphcial set. Steps to Reproduce: 1. Grab RPI+upstream EDK2 firmware for rpi, build/install machine with f29 2. check `loginctl show-seat seat0` CanGraphical=XXX 3. Note `loginctrl seat-status seat0` /sys/devices/platform/efi-framebuffer.0/graphics/fb0 graphics:fb0 "EFI VGA" Actual results: # loginctl show-seat seat0 Id=seat0 ActiveSession=4 CanMultiSession=yes CanTTY=yes CanGraphical=no ... Expected results: Cangraphical should be set on working fbX devices.