Bug 963875 - Issues with gnome
Summary: Issues with gnome
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 18
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-16 17:21 UTC by Luca Giuzzi
Modified: 2014-02-05 21:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 21:24:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Relevant snippet from /var/log/messages (178.50 KB, application/octet-stream)
2013-05-16 17:21 UTC, Luca Giuzzi
no flags Details
Output of lspci (37.50 KB, application/octet-stream)
2013-05-16 17:22 UTC, Luca Giuzzi
no flags Details

Description Luca Giuzzi 2013-05-16 17:21:41 UTC
Created attachment 748961 [details]
Relevant snippet from /var/log/messages

Description of problem:
 After updating the kernel to 3.9.2-200 I am unable to log-in to gnome shell.
 Reverting the kernel to 3.8.11-200 fixes the problem.
 Unfortunately I have not been able to find any detailed information on
 the error by gnome (just a generic "extensions disabled"; is there somewere
 an .Xerrors file to attach).

 On a different machine I have had a different kind of issue with the same kernel, but gnome shell works; thus I sort of suspect it has to do with the rendering infrastructure.

I have the same problem with a test account I created on purpose.

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

F18; kernel-3.9.2-200.fc18.x86_64

How reproducible:


Steps to Reproduce:
1. boot with the new kernel
2. try to log-in into gnome shell
3.
  
Actual results:
 

Expected results:


Additional info:

Comment 1 Luca Giuzzi 2013-05-16 17:22:25 UTC
Created attachment 748962 [details]
Output of lspci

Comment 2 Josh Boyer 2013-05-16 17:52:39 UTC
This is probably fixed by this update:

https://admin.fedoraproject.org/updates/gnome-bluetooth-3.6.1-3.fc18,control-center-3.6.3-2.fc18

Comment 3 Luca Giuzzi 2013-05-16 18:06:51 UTC
I can confirm that that update fixed the problem.

Best,
 luca

Comment 4 Fedora End Of Life 2013-12-21 13:34:23 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 5 Fedora End Of Life 2014-02-05 21:24:20 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.