GNOME Bugzilla – Bug 724977
gnome-shell crashed with SIGSEGV in g_simple_async_result_complete()
Last modified: 2014-03-12 18:27:22 UTC
Open bug in launchpad.net: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/850365 Comment 0 in launchpad.net: "The crash happened just after boot + login, he did it all himself :)" Comment 7 in launchpad.net "It also affects 14.04-dev (gnome-shell 3.10, linux 3.13)"
+ Trace 233222
In launchpad: "This bug affects 26 people."
Created attachment 271481 [details] [review] StTextureCache: don't crash if we fail to allocate a framebuffer It's possible that FBO creation fails due to hw limits or the driver not exposing the EXT_framebuffer_object extension. In that case, just give up on creating square icons. This is not a complete fix, because the trace shown should not go through this path, but at least it would rule out the "weird driver" case.
Review of attachment 271481 [details] [review]: OK.
Attachment 271481 [details] pushed as ac76940 - StTextureCache: don't crash if we fail to allocate a framebuffer Closing because this is technically fixed, as in, the shell does not crash anymore, but please file a new bug as soon as you have more information on the real underlying cause of this.