Bug 894637 - GDM fails to start
Summary: GDM fails to start
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 18
Hardware: arm
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-12 19:45 UTC by Medic Momcilo
Modified: 2014-02-05 14:46 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:46:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Steps I did to prepare filesystem (1.47 KB, application/octet-stream)
2013-01-12 19:45 UTC, Medic Momcilo
no flags Details
/var/log/messages (83.69 KB, application/octet-stream)
2013-01-12 19:46 UTC, Medic Momcilo
no flags Details
/var/log/gdm/:0-greeter.log (107 bytes, application/octet-stream)
2013-01-12 19:47 UTC, Medic Momcilo
no flags Details
/var/log/gdm/:0.log (20.13 KB, application/octet-stream)
2013-01-12 19:48 UTC, Medic Momcilo
no flags Details
/var/log/gdm/:0-slave.log (216 bytes, application/octet-stream)
2013-01-12 19:49 UTC, Medic Momcilo
no flags Details

Description Medic Momcilo 2013-01-12 19:45:09 UTC
Created attachment 677481 [details]
Steps I did to prepare filesystem

Description of problem:
Enabling gdm.service results in 'Oh no! Something has gone wrong.'

Version-Release number of selected component (if applicable):
gdm-3.6.2-5.fc18.armv7hl

How reproducible:
Always

Steps to Reproduce:
1. systemctl disable lightdm.service
2. systemctl enable gdm.service
3. init 5
  
Actual results:
Dreaded 'Oh no!' screen

Expected results:
GDM starts and waits for login

Additional info:

I think same bug is preventing GNOME (fallback mode) to start because GNOME fallback worked on F17 but not on F18 Beta and it fails with same message.

I attached log files and steps I did to prepare filesystem for my device.

Comment 1 Medic Momcilo 2013-01-12 19:46:53 UTC
Created attachment 677482 [details]
/var/log/messages

Comment 2 Medic Momcilo 2013-01-12 19:47:41 UTC
Created attachment 677485 [details]
/var/log/gdm/:0-greeter.log

Comment 3 Medic Momcilo 2013-01-12 19:48:40 UTC
Created attachment 677497 [details]
/var/log/gdm/:0.log

Comment 4 Medic Momcilo 2013-01-12 19:49:20 UTC
Created attachment 677502 [details]
/var/log/gdm/:0-slave.log

Comment 5 Fedora End Of Life 2013-12-21 10:21:14 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 14:46:30 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.