Bug 1462646

Summary: Modesetting on nvidia-drm ends gnome X11 session
Product: [Fedora] Fedora Reporter: Aditya Shah <aditya-shah>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: ofourdan, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:32:05 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:
Attachments:
Description Flags
Modesetting X log
none
X log without modesetting none

Description Aditya Shah 2017-06-19 07:17:15 UTC
Created attachment 1289017 [details]
Modesetting X log

Well weird bug. Setting modeset=1 for nvidia-drm causes the gnome-session to immediately exit on X11. The bug is weird because if you boot without modesetting and then reload module with modesetting from Wayland session, and then login to X11 session, everything works fine. But if modesetting is enabled during boot, you can't login to X11 session, as after 1/2 a sec. of entering the password the screen goes black for a moment and you are back on login screen. But now login to Wayland, reload module without modesetting and log back in using X11, you can get in. I tried looking through Xorg.0.log of both crashed and working sessions, both are similar, no discrepancies in either.

Comment 1 Aditya Shah 2017-06-19 07:18:01 UTC
Created attachment 1289018 [details]
X log without modesetting

Comment 2 Fedora End Of Life 2018-05-03 08:12:22 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:32:05 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.