| Summary: | Suspect new version of mutter causes gnome wayland session to fail to start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill <thetaeridanus> |
| Component: | mutter | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | fmuellner, otaylor, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:52:14 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: | |
|
Description
Bill
2016-10-21 08:57:14 UTC
My attempt to back out the mutter update was via dnf history undo which couldn't find 3.22.1-3.fc25.x86_64 but just doing dnf downgrade mutter reverted back to 3.22.1-2.fc25.x86_64. This has resolved the problem described above: echo $XDG_SESSION_TYPE wayland Do you have two GPUs? See bug 1375247 why the behavior you are seeing might be intended in that case ... The machine is a Dell Latitude E6540 with hybrid graphics. It has Intel and AMD. It seems to work ok with an external monitor with mutter 3.22.1-2.fc25.x86_64 Maybe suggest that the GDM menu should indicate that the default gnome session isn't available or else make it still work for an x11 login after logging out. It only seems to work the very first time after boot. It's a bit of a nuisance as I was in the middle of trying to diagnose a problem with Libreoffice Impress running on gnome wayland session with an external monitor plugged in. https://bugzilla.redhat.com/show_bug.cgi?id=1386948 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |