| Bug ID | 90182 |
|---|---|
| Summary | Qt Applications won't start on the dedicated GPU (SIGABRT) |
| Product | Mesa |
| Version | 10.5 |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | paul@konecny.at |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 115334 [details] GLXINFO of radeon Hi, I was trying to test the new kdenlive development build I noticed that it wouldn't even start with DRI_PRIME=1 kdenlive. I immediatedly got a SIGABRT Same happened with an easy example program from the Qt project "openglunderqml" "LANG=C R600_DEBUG=cs DRI_PRIME=1 QSG_INFO=1 '/home/paul/hybrid test/build-openglunderqml-Desktop-Debug/openglunderqml' QML debugging is enabled. Only use this in a safe environment. openglunderqml: dri2.c:518: dri2_allocate_textures: Assertion `drawable->textures[statt]' failed. Abgebrochen (Speicherabzug geschrieben)" As Xonotic worked more or less ok on the radeon I filed a bug report at the Qt project https://bugreports.qt.io/browse/QTBUG-45686 Laszlo Agocs from the Qt project states the following: "Might be a difficult one and not just because we lack any such hw to test on. Cannot do much when glXMakeCurrent() crashes deep inside the driver. Any chance for a backtrace with symbols? In the absence of that running with QSG_INFO=1 could be helpful too. Anyway, it's most likely happening in QGLXContext::queryDummyContext() where we attempt to make a pbuffer surface current in order to query a few GL things. Other apps may not rely on pbuffers and thus may not exhibit the issue." I'm not a programmer so please go easy on me. If you need additional info let me know (and maybe tell me how to fetch it for you ;) ) Thanks! Hardware: HP EliteBook 850 G1 with Intel (HD4400) / AMD (HD8750M, OLAND) hybrid graphics Software: ArchLinux (Antergos) Linux 3.19.3 mesa 10.5.4 Intel / Radeon exact glxinfo outputs are attached Qt 5.4.1
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
