Bug 1401339 - next boot fails on F25 when lightdm enabled
Summary: next boot fails on F25 when lightdm enabled
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Alternative GTK desktop environments
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-04 23:06 UTC by Jim Bean
Modified: 2017-12-12 10:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:55:30 UTC
Type: Bug


Attachments (Terms of Use)
/proc/cpuinfo (3.03 KB, text/plain)
2016-12-07 01:32 UTC, Jim Bean
no flags Details
/var/log/lightdm/lightdm.log (4.61 KB, text/plain)
2016-12-08 04:05 UTC, Jim Bean
no flags Details

Description Jim Bean 2016-12-04 23:06:44 UTC
Description of problem:
next boot fails on F25 when lightdm enabled

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.install new F25 and do all updates
2.systemctl disable gdm.service
3.systemctl enable lightdm.service
4.reboot

Actual results:
two slightly different login screens are presented and accepted.
system freezes with standard background presented. no error messages

Expected results:


Additional info:
lightdm worked fine on F24

Comment 1 Jim Bean 2016-12-07 01:32:52 UTC
Created attachment 1228767 [details]
/proc/cpuinfo

Comment 2 Jim Bean 2016-12-07 01:35:15 UTC
I did the same experiment on an HP laptop and lightdm works fine there
so the problem is hardware dependant.

The problem machine is a fairly old Microway desktop with a solid state disk.
A newer video card is installed.
Intel 4 core processor.

Comment 3 Jim Bean 2016-12-08 04:05:51 UTC
Created attachment 1229314 [details]
/var/log/lightdm/lightdm.log

Comment 4 Fedora Admin XMLRPC Client 2017-05-19 15:31:47 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2017-07-05 20:38:49 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora End Of Life 2017-11-16 18:37:12 UTC
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.

Comment 7 Fedora End Of Life 2017-12-12 10:55:30 UTC
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.


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