Bug 697212 - upon boot into gdm, the login screen does not show; pkill gdm restores it
Summary: upon boot into gdm, the login screen does not show; pkill gdm restores it
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 14
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: 2011-04-16 21:25 UTC by Wendell Baker
Modified: 2012-08-16 15:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 15:35:16 UTC
Type: ---


Attachments (Terms of Use)
/var/log/messages from reboot to steady state showing no reason for Actuality #1's bad behavior (85.65 KB, application/octet-stream)
2011-04-16 21:25 UTC, Wendell Baker
no flags Details
Actuality #1 - a photo (with a phone) of the login screen showing no way to login (4.48 MB, image/png)
2011-04-16 21:26 UTC, Wendell Baker
no flags Details
Actuality #2 - a photo (with a phone camera) of the expected gdm login screen (4.48 MB, image/png)
2011-04-16 21:28 UTC, Wendell Baker
no flags Details

Description Wendell Baker 2011-04-16 21:25:39 UTC
Created attachment 492642 [details]
/var/log/messages from reboot to steady state showing no reason for Actuality #1's bad behavior

Description of problem:

Upon reboot to the GNOME login, the login panel does not show any users or allow a login.  See enclosed actualities

The workaround is:
a) switch virtual terminals
b) login on the console
c) sudo pkill Xorg
d) upon restart gdm fires up and you can login

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

$ rpm -q -f /usr/sbin/gdm*
gdm-2.32.0-1.fc14.i686
gdm-2.32.0-1.fc14.i686


How reproducible:

100% deterministic

Steps to Reproduce:
1. reboot 
2. see the effect
3.
  
Actual results:

shown as Actuality #1 (the truncated effect)

Expected results:

shown as Actuality #2 (the proper behavior of gdm)

Additional info:

For completeness, I include the relevant portions of /var/log/messages from a reboot up to steady-state (there is nothing that indicates the problematic behavior of gdm in that output).

Actuality #2 shows wbaker is "already logged in"  This is because of the console login on the other virtual terminal.  That is correct behavior.

Comment 1 Wendell Baker 2011-04-16 21:26:45 UTC
Created attachment 492643 [details]
Actuality #1 - a photo (with a phone) of the login screen showing no way to login

Comment 2 Wendell Baker 2011-04-16 21:28:03 UTC
Created attachment 492644 [details]
Actuality #2 - a photo (with a phone camera) of the expected gdm login screen

Comment 3 Matt Mossholder 2011-05-02 16:14:43 UTC
I'm seeing this occur as well. In my case, I am using LDAP/Kerberos for storing user information and authentication.

Comment 4 Matt Mossholder 2011-05-02 16:17:05 UTC
(In reply to comment #3)
> I'm seeing this occur as well. In my case, I am using LDAP/Kerberos for storing
> user information and authentication.

Oops.. should have mentioned I am seeing this on F15 beta, fully patched as of 02-May-2011.

Comment 5 Fedora Admin XMLRPC Client 2011-06-21 15:32:32 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Admin XMLRPC Client 2011-06-21 15:34:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora Admin XMLRPC Client 2011-06-21 15:37:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Fedora Admin XMLRPC Client 2011-06-21 15:40:28 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Fedora Admin XMLRPC Client 2011-06-21 15:49:57 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 10 Fedora Admin XMLRPC Client 2011-06-21 15:52:29 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 11 Fedora Admin XMLRPC Client 2011-06-21 15:54:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora Admin XMLRPC Client 2011-06-21 15:56:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Fedora End Of Life 2012-08-16 15:35:18 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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