Bug 1008035 - Gnome-shell in Fedora 20 Alpha is unusable
Gnome-shell in Fedora 20 Alpha is unusable
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-13 17:04 EDT by Mykola Dvornik
Modified: 2015-06-29 08:22 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 08:22:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gnome-shell debug session will backtraces for all threads (89.08 KB, text/plain)
2013-12-10 11:20 EST, Kurt Miller
no flags Details

  None (edit)
Description Mykola Dvornik 2013-09-13 17:04:59 EDT
Description of problem:

Gnome-shell restarts constantly until 'Something went wrong. Log Out'. Many gnome3 components sigfault, e.g. gnome-tweak-tool, gnome-control-center, etc. When Dark Themes is used a few applications are still grey or partially grey, i.e. gnome-terminal, gnome-tweak-tool.

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


How reproducible:


Steps to Reproduce:
1. Start fedora 20 Alpha RC2 with Gnome-shell on X.
2. Click on any of the system icons in the top right corner of the shell.

Actual results:

gnome-shell restarts, some of the gnome-specific application sigfault

Expected results:

To see expected behavior and smooth gnome-shell experience.

Additional info:
Comment 1 Kurt Miller 2013-12-10 11:19:16 EST
I am experincing a persistant, reproducable, showstopper segfault in gnome-shell in Fedora 20 beta. I'm currently running:

gnome-shell.x86_64  from @updates-testing

Pressing the windows key is all that is needed to trigger the sefault:

Program received signal SIGSEGV, Segmentation fault.
_cogl_pipeline_flush_gl_state (ctx=ctx@entry=0x22ae800, pipeline=pipeline@entry=0x326b040,
    framebuffer=framebuffer@entry=0x254fe10, with_color_attrib=with_color_attrib@entry=1, unknown_color_alpha=<optimized out>)
    at driver/gl/cogl-pipeline-opengl.c:1447
1447      if (progend->pre_paint)
(gdb) p progend
$1 = (const CoglPipelineProgend *) 0x0

This is a null pointer dereference.

There is a problem tracker for this problem at:


The full backtrace is in the screen session log file I'm attaching.
Comment 2 Kurt Miller 2013-12-10 11:20:33 EST
Created attachment 834847 [details]
gnome-shell debug session will backtraces for all threads
Comment 3 Fedora End Of Life 2015-05-29 05:23:59 EDT
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 4 Fedora End Of Life 2015-06-29 08:22:24 EDT
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

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.