Bug 578782
Summary: | Some gnome games crash when started | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> |
Component: | mesa | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | airlied, ajax, bskeggs, mclasen, otaylor, rstrode, sanjay.ankur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-09 14:01:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Backes
2010-04-01 11:26:28 UTC
Please remove quadrapassel bug; I filed it already in 578777 (network error when submitting 578777, so I repeated it in the submission for 578782) After having updated to gnome-games-extra-2.30.0-1.fc13.i686, gnibbles still crashes: gnibbles failed to create drawable (gnibbles:2376): Clutter-WARNING **: Unable to create a new stage: the glx backend does not support multiple stages. (gnibbles:2376): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnibbles:2376): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_set_color: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_set_size: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_set_user_resizable: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_container_add_actor: assertion `CLUTTER_IS_CONTAINER (container)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_set_size: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_ensure_viewport: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): ClutterX11-CRITICAL **: clutter_x11_set_stage_foreign: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_realize: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_show: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_set_size: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_container_add_actor: assertion `CLUTTER_IS_CONTAINER (container)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_map: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnibbles:2376): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_set_size: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_container_add_actor: assertion `CLUTTER_IS_CONTAINER (container)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_set_size: assertion `CLUTTER_IS_ACTOR (self)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_ensure_viewport: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_redraw: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_show_cursor: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnibbles:2376): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_set_key_focus: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnibbles:2376): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnibbles:2376): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnibbles:2376): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_stage_set_key_focus: assertion `CLUTTER_IS_STAGE (stage)' failed (gnibbles:2376): Clutter-CRITICAL **: clutter_actor_hide: assertion `CLUTTER_IS_ACTOR (self)' failed My video card: 02:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) Driver: nouveau Moving to nouveau, test-wise. The games themeselves work fine on e.g. Intel, so this is likely caused by limitations of the gl support in nouveau. *** Bug 578777 has been marked as a duplicate of this bug. *** Not exactly a nouveau "bug". I can confirm that I see the problem also, and that if you actually install the nouveau 3d drivers (mesa-dri-drivers-experimental) things work fine. Not sure where exactly this should be assigned, but I fail to see a good reason why clutter shouldn't just use GL software rendering in the absence of hardware accel. Matthias? Oh, I had no idea that things work fine with mesa-dri-drivers-experimental. Thats great to know. As for software rendering in clutter, no idea, Owen can probably answer that better than I can. There are a few questions here, I think: - Are the mesa-dri-drivers-experimental good enough to install by default ? - Can clutter detect the lack of suitable GL support in a better way, that we can perhaps handle by offering to install the drivers ? I would be hesitant to install the nouveau 3d drivers by default at this stage, there's still a number of issues in them. They do work fine for a lot of apps already however. Every other GL app falls back to software rendering just fine, I have no idea why clutter fails to do so. Owen points out that this might be the same as bug 575825 Owen also asks if setting LIBGL_ALWAYS_SOFTWARE=1 works around this problem. (In reply to comment #10) > Owen also asks if setting LIBGL_ALWAYS_SOFTWARE=1 works around this problem. Actually, that wasn't my question, my question was whether you could trigger this crash on non-NVIDIA hardware with LIBGL_ALWAYS_SOFTWARE=1. > Actually, that wasn't my question, my question was whether you could trigger
> this crash on non-NVIDIA hardware with LIBGL_ALWAYS_SOFTWARE=1.
Oh, good point. That is indeed the case. Fails in the same way on my Intel hardware with LIBGL_ALWAYS_SOFTWARE=1.
Seems almost certainly the same as bug 575825, so marking as a duplicate. *** This bug has been marked as a duplicate of bug 575825 *** |