Bug 2007742
Summary: | Selecting Xorg doesn't work as when you login you still end up with Wayland | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> | ||||||||
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 35 | CC: | anton4linux, awilliam, caillon+fedoraproject, ego.cordatus, fzatlouk, geraldo.simiao.kutz, gnome-sig, mclasen, pbrobinson, philip.wyett, pwhalen, rhughes, robatino, rstrode, rwarsow | ||||||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | https://ask.fedoraproject.org/t/we-are-testing-a-new-common-issues-category-and-process/18916 AcceptedBlocker https://fedoraproject.org/wiki/Common_F35_bugs#gnome-xorg-fail | ||||||||||
Fixed In Version: | gdm-41.0-2.fc35 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | |||||||||||
: | 2009044 (view as bug list) | Environment: | |||||||||
Last Closed: | 2021-10-01 00:15:01 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: | 1891955 | ||||||||||
Attachments: |
|
Description
Peter Robinson
2021-09-24 18:06:40 UTC
Hardware is a Lenovo Carbon X1 gen 6 Proposed as a Blocker for 35-final by Fedora user pbrobinson using the blocker tracking app because: Xorg should be a working option for Workstation Confirmed this on AArch64 as well. It works in Beta but once upgraded it will no longer honour the Xorg selection at log in. I was able to get into X11 by logging in, logging out and then selecting the X11 session again. (In reply to František Zatloukal from comment #4) > I was able to get into X11 by logging in, logging out and then selecting the > X11 session again. Doesn't work for me, I've tried a number of times, and it should work the first time as expected. +7 in https://pagure.io/fedora-qa/blocker-review/issue/481 , marking accepted. For a criterion I'd say we can probably count it as covered by Beta criterion "Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops." - in this instance, "logging in" isn't exactly working as intended. The footnote defines it as "Logging in must transfer the user from the login screen/prompt to their working environment", which is slightly vague. (In reply to František Zatloukal from comment #4) > I was able to get into X11 by logging in, logging out and then selecting the > X11 session again. Yes, here too. I tested with an F35 beta 1.2 iso and other iso too. First login only on Wayland, but second time I can log into a X11 sesssion. Created attachment 1826720 [details]
session x11 sucsses second time login
Created attachment 1826721 [details]
X11 session failed to login at first time
so i just did a fresh f35 install and can't reproduce. Can someone set Enable=true in the [debug] section of /etc/gdm/custom.conf, reboot, reproduce, and then attach the full, unfiltered output of journalctl -b ? when this happens, do you guys have a file called /run/gdm/custom.conf ? if so, can you attach that file ? (In reply to Ray Strode [halfline] from comment #11) > when this happens, do you guys have a file called /run/gdm/custom.conf ? if > so, can you attach that file ? No file called that on my current session, will retry and get debug once I've finished calls and meetings Geraldo and Paul if you could post logs too that'd be great! I've new installed last week and now it's full updated (Intel Skylake and i915) I see the following: I'm in general able to log in to X when I choose to do so by explicit choose X under the the "wheel" in the login screen But when I log out and login again I get wayland *even* when X is highlighted (but not clicked) To get X again I explicitly need to click X Created attachment 1827182 [details] journalctl -b0 from 2 subseq. logins into X with debug=on in /etc/gdm/custom.conf as declared in comment 14 1. a login with exclicit set X, 2. a log out and 3. a login without clicking X again (but controlled it's highlighted) => leads to wayland (In reply to Ray Strode [halfline] from comment #11) > when this happens, do you guys have a file called /run/gdm/custom.conf ? if > so, can you attach that file ? no and no ! ;-) - with debug=on in /etc/gdm/custom.conf - ls -lRa /run/gdm/ /run/gdm/: total 4 drwx--x--x. 3 root gdm 80 28. Sep 22:39 . drwxr-xr-x. 48 root root 1220 28. Sep 22:39 .. -rw-r--r--. 1 root root 5 28. Sep 22:39 gdm.pid drwx------. 2 gdm gdm 40 28. Sep 22:39 greeter /run/gdm/greeter: total 0 drwx------. 2 gdm gdm 40 28. Sep 22:39 . drwx--x--x. 3 root gdm 80 28. Sep 22:39 . FEDORA-2021-bfcc9cd095 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bfcc9cd095 FEDORA-2021-bfcc9cd095 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bfcc9cd095` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bfcc9cd095 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Thanks for the fix, gdm-41.0-2.fc35 fixes the issue. dito here, gdm-41.0-2.fc35 fixes the issue. thanks Confirmed here too, with gdm-41.0-2.fc35. All is working as expected. FEDORA-2021-bfcc9cd095 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |