Red Hat Bugzilla – Bug 1008035
Gnome-shell in Fedora 20 Alpha is unusable
Last modified: 2015-06-29 08:22:24 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):
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.
gnome-shell restarts, some of the gnome-specific application sigfault
To see expected behavior and smooth gnome-shell experience.
I am experincing a persistant, reproducable, showstopper segfault in gnome-shell in Fedora 20 beta. I'm currently running:
gnome-shell.x86_64 188.8.131.52-3.fc20 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>)
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.
Created attachment 834847 [details]
gnome-shell debug session will backtraces for all threads
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'
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.
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.