Bug 1030649 - Gnome freezes immediately after login while displaying background
Summary: Gnome freezes immediately after login while displaying background
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 21:02 UTC by Jim Bean
Modified: 2014-02-13 15:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-13 15:29:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
tail of Dmesg (41.01 KB, text/plain)
2013-11-14 21:02 UTC, Jim Bean
no flags Details

Description Jim Bean 2013-11-14 21:02:36 UTC
Created attachment 824143 [details]
tail of Dmesg

Description of problem:
After login gnome normally displays a series of background images of increasing size. When it freezes one of the smaller images is displayed, the keyboard is inactive and the only way out is to reboot. Sometimes after a LONG time the login will complete.

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


How reproducible:


Steps to Reproduce:
1.boot
2.login
3.

Actual results:


Expected results:


Additional info:
Attached Dmesg from an instance where the login did complete.
Nouveau seems to be finding bogus cache errors.
This machine is dual booted to F18 which never experiences the problem.

Comment 1 Jim Bean 2014-01-11 23:35:19 UTC
After downloading gnome classic that can be selected. This problem never happens in gnome classic.

It seems that no attention is being paid to this, It is a serious problem since there is no exit except to try booting again, and again ...

Comment 2 Jim Bean 2014-02-10 20:51:50 UTC
I haven't seen this problem for some time and never on F20.
It looks like somebody fixed it and kept quiet.
regards Jim Bean

Comment 3 Florian Müllner 2014-02-13 15:29:51 UTC
OK, let's assume it's fixed then.


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