Bug 1462065 - GNOME on Wayland session locks up when logging in from gdm
Summary: GNOME on Wayland session locks up when logging in from gdm
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-16 04:52 UTC by Link Dupont
Modified: 2018-05-29 11:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:33:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl output from boot and login through GDM to wayland GNOME session (301.56 KB, text/x-vhdl)
2017-06-16 04:52 UTC, Link Dupont
no flags Details

Description Link Dupont 2017-06-16 04:52:35 UTC
Created attachment 1288255 [details]
journalctl output from boot and login through GDM to wayland GNOME session

Description of problem:
I have a Clevo P670SE (System76 Oryx Pro). It has a hybrid GPU. I have disabled the hybrid GPU in the BIOS and run only on the discrete GPU.

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1)

GDM starts up fine. The 'GNOME on Xorg' session runs fine. The 'GNOME (on wayland)' session locks up with graphical glitches (looks like garbage GPU buffer stuff) immediately after logging in. I've attached the journalctl boot log. There is a flood of this message hitting the log:

Jun 15 21:35:28 oryx kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 00006000 [GPFIFO GPPTR] ch 26 [00bc230000 Xwayland[1639]] subc 0 mthd 0000 data 00000000

If I run a GNOME session like so: dbus-run-session -- gnome-shell --display-server --wayland, the desktop starts up correctly. This exact same hardware configuration ran the wayland session correctly in F25.

Version-Release number of selected component (if applicable):
gdm-3.24.2-1.fc26.x86_64
xorg-x11-server-Xwayland-1.19.3-4.fc26.x86_64
libwayland-server-1.13.0-1.fc26.x86_64
gnome-session-wayland-session-3.24.1-1.fc26.x86_64
libwayland-client-1.13.0-1.fc26.x86_64
libwayland-cursor-1.13.0-1.fc26.x86_64
mesa-libwayland-egl-17.1.2-2.fc26.x86_64
ibus-wayland-1.5.16-2.fc26.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Log into 'GNOME' session
2.
3.

Actual results:
Session locks up, requiring a hard reset of the computer

Expected results:
Session to log into the gnome desktop

Additional info:

Comment 2 Fedora End Of Life 2018-05-03 08:13:48 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Comment 3 Fedora End Of Life 2018-05-29 11:33:41 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


Note You need to log in before you can comment on or make changes to this bug.