Bug 670795 - Fedora Rawhide Live Image fails to complete autologin and give a desktop
Summary: Fedora Rawhide Live Image fails to complete autologin and give a desktop
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 19
Hardware: Unspecified
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-19 12:23 UTC by Narendra K
Modified: 2015-02-18 13:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:31:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages (1.57 MB, text/plain)
2011-01-19 13:35 UTC, James Laska
no flags Details
/var/log/gdm/:0-greeter.log (846.67 KB, text/plain)
2011-01-19 13:37 UTC, James Laska
no flags Details
/var/log/:0-greeter.log (105.13 KB, text/plain)
2011-01-19 16:23 UTC, James Laska
no flags Details

Description Narendra K 2011-01-19 12:23:05 UTC
Description of problem:

Fedora Rawhide Live Image failed to autologin and provide a desktop. I used the image - http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/desktop-x86_64-20110117.16.iso.

I could switch to text console (control+alt+F2) and get a shell.


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

gdm version - 2.94.1 Release:1.fc15


How reproducible: Always.


Steps to Reproduce:

Boot into the Live Image from the link mentioned in description.



Actual results: Live Image fails to give a desktop.


Expected results:Live Image should give a desktop.


Additional info:

Comment 1 Narendra K 2011-01-19 12:27:07 UTC
This issue impacts the Network Device Naming Fedora Test day scheduled to be held on 27th of this month - https://fedorahosted.org/fedora-qa/ticket/159

Comment 2 James Laska 2011-01-19 13:33:22 UTC
Confirmed this behavior.  It seems gdm keeps failing to present the greeter.

Manual workaround is to boot (or change to) runlevel 3, login as 'liveuser' and start the desktop manually (`startx`).

I'm attaching /var/log/messages which shows gdm troubles.  The highlight is shown below ...


Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 0: /usr/libexec/gdm-simple-greeter() [0x4331b9]
Jan 19 13:30:18 localhost pam: gdm-password[1443]: DEBUG(+): Got callback for signal 15
Jan 19 13:30:18 localhost pam: gdm-password[1404]: DEBUG(+): Worker finished
Jan 19 13:30:18 localhost pam: gdm-password[1417]: DEBUG(+): Worker finished
Jan 19 13:30:18 localhost pam: gdm-password[1443]: DEBUG(+): Caught signal 15, shutting down normally.
Jan 19 13:30:18 localhost pam: gdm-password[1456]: DEBUG(+): Worker finished
Jan 19 13:30:18 localhost pam: gdm-password[1508]: DEBUG(+): Worker finished
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 1: /usr/libexec/gdm-simple-greeter() [0x43331a]
Jan 19 13:30:18 localhost pam: gdm-password[1443]: DEBUG(+): GdmSignalHandler: Caught termination signal - calling fatal func
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 2: /lib64/libpthread.so.0(+0xf3d0) [0x7f11fded43d0]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 3: /lib64/libglib-2.0.so.0(g_logv+0x229) [0x7f11fb5c2159]
Jan 19 13:30:18 localhost pam: gdm-password[1443]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 4: /lib64/libglib-2.0.so.0(g_log+0x83) [0x7f11fb5c24e3]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 5: /lib64/libgobject-2.0.so.0(g_object_ref+0x47) [0x7f11fb88fd67]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 6: /usr/libexec/gdm-simple-greeter() [0x42efe9]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 7: /usr/libexec/gdm-simple-greeter() [0x42f93e]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 8: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f11fb5b9483]
Jan 19 13:30:18 localhost pam: gdm-password[1443]: DEBUG(+): Worker finished
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 9: /lib64/libglib-2.0.so.0(+0x43c60) [0x7f11fb5b9c60]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 10: /lib64/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f11fb5ba2d2]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 11: /usr/lib64/libgtk-x11-2.0.so.0(gtk_main+0xa7) [0x7f11fd9960c7]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 12: /usr/libexec/gdm-simple-greeter() [0x4132f4]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 13: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f11fb1eee7d]
Jan 19 13:30:18 localhost gdm-simple-greeter[2166]: Frame 14: /usr/libexec/gdm-simple-greeter() [0x412d49]

Comment 3 James Laska 2011-01-19 13:35:02 UTC
Created attachment 474261 [details]
/var/log/messages

Comment 4 James Laska 2011-01-19 13:37:36 UTC
Created attachment 474264 [details]
/var/log/gdm/:0-greeter.log

Attaching gdm :0-greeter.log which is a bit less noisy

Comment 5 James Laska 2011-01-19 16:23:33 UTC
Created attachment 474309 [details]
/var/log/:0-greeter.log

Replacing /var/log/gdm/:0-greeter.log with a new version with appropriate debuginfo packages installed.  The backtrace should be more usable now.

Comment 6 James Laska 2011-01-20 20:42:50 UTC
The reported problem is resolved by the latest gdm in rawhide (http://koji.fedoraproject.org/koji/buildinfo?buildID=215039).

Comment 7 Narendra K 2011-01-24 19:29:48 UTC
I booted into the Live image 20110123. The autologin succeeded and desktop is seen. But there is one issue that i observed, when the System Tools -> Terminal is clicked, it does not succeed in giving a shell.

Is this related or i should file a new bug ?

Comment 8 Narendra K 2011-01-24 19:30:43 UTC
I had to switch to the text console (control+alt+F2) to get a shell.

Comment 9 Fedora Admin XMLRPC Client 2011-06-21 15:29:48 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:31:42 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:34:30 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:37:25 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

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

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

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

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

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

Comment 18 Fedora End Of Life 2013-04-03 20:15:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 19 Fedora End Of Life 2015-01-09 21:47:06 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 20 Fedora End Of Life 2015-02-18 13:31:28 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.