Description of problem:
i started gnome-control-center with alt-f2
Version-Release number of selected component:
Thread no. 1 (10 frames)
#2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2416
#6 __glXSendErrorForXcb at glx_error.c:83
#7 __glXIsDirect at glxcmds.c:601
#8 create_context at winsys/cogl-winsys-glx.c:658
#9 _cogl_winsys_display_setup at winsys/cogl-winsys-glx.c:784
#10 cogl_display_setup at ./cogl-display.c:130
#11 cogl_renderer_check_onscreen_template at ./cogl-renderer.c:227
#12 clutter_backend_x11_get_display at x11/clutter-backend-x11.c:736
#13 clutter_backend_real_create_context at ./clutter-backend.c:301
#15 _clutter_backend_create_context at ./clutter-backend.c:751
Created attachment 657689 [details]
Created attachment 657690 [details]
Created attachment 657691 [details]
Created attachment 657692 [details]
Created attachment 657693 [details]
Created attachment 657694 [details]
Created attachment 657695 [details]
Created attachment 657696 [details]
Created attachment 657697 [details]
Created attachment 657698 [details]
Created attachment 657699 [details]
This is a delayed error, I think? glXCreateNewContext doesn't require a round-trip, but glXIsDirect does (the first time). So I think what's happening is creating the context fails, and then we send the IsDirect reply without first draining the reply queue to look for the error from CNC,
I'm at a loss to explain why CreateNewContext fails though. How reproducible is this for you?
I was thinking that by this time the bug can no longer be reproduced but i was wrong. control-center keeps crashing. 3 of 3 consecutive tries.
I have the same problem, please tell me how I can provide info to help tracking this problem down and fix it.
This is the one program that should never fail!!! I've upgraded to Satirical Cow, FC18, and my life is now over! I can't configure or do anything now. I apparently can't switch to KDE either.
~$ export GDK_SYNCHRONIZE=1
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
(gnome-control-center:6722): Gdk-ERROR **: The program 'gnome-control-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 196 error_code 11 request_code 152 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
It crashes in cogl trying to initialise clutter.
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.