Bug 1331916 - booted into kernel 4.5.2-300 - no login screen
Summary: booted into kernel 4.5.2-300 - no login screen
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-30 01:54 UTC by Tim Lloyd
Modified: 2017-08-08 14:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 14:23:05 UTC
Type: Bug


Attachments (Terms of Use)
xorg log after multi-user boot and startx (7.34 KB, text/plain)
2016-04-30 01:54 UTC, Tim Lloyd
no flags Details

Description Tim Lloyd 2016-04-30 01:54:15 UTC
Created attachment 1152473 [details]
xorg log after multi-user boot and startx

Hi, I have been running F24 since the alpha release with minimal problems. This morning I noticed a new kernel (4.5.2-300) so rebooted to take advantage of this. The PC reboots but I don't have a display!! I get the fedora icon as usual during bootup but then the screen goes blank - no login prompt. I can ssh from other computers into this PC, the disk are mounted fine and all looks okay

Not sure whether this is an F24 problem though as I can't boot into any of the other kernels.

I was able though to boot from my F24 USB stick into Gnome.

I tried to boot into multi-user mode but startx did not give me a display. I have attached the xorg log file

Comment 1 Paul Sand 2016-04-30 11:48:52 UTC
I have the same symptoms. Booting the system to runlevel 3 works.

Comment 2 Paul Sand 2016-04-30 14:22:22 UTC
There were also upgrades to "selinux-policy" and "selinux-policy-targeted" packages in addition to the kernel upgrade yesterday (4/29). 

Downgrading these packages to previous versions seems to have made things work for me again. (Had to do "dnf downgrade" in runlevel 3.)

Comment 3 Tim Lloyd 2016-04-30 21:31:08 UTC
thanks. All good now.

Is this bug then fixed or do we need new selinux policies?

Comment 4 Paul Sand 2016-05-01 08:03:46 UTC
I think this is a duplicate of Bug 1331619.

Comment 5 Fedora End Of Life 2017-07-25 20:38:47 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 6 Fedora End Of Life 2017-08-08 14:23:05 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.