| Summary: | [abrt] gnome-shell-3.1.4-2.gite7b9933.fc16: prepare_depthbuffer: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||||||||||||||||||
| Component: | clutter | Assignee: | Peter Robinson <pbrobinson> | ||||||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 16 | CC: | abdelmalek_alg, alevy, banaan2, browning48ky, bugzilla, darshan.ddu, felipevsw, gbauman, gdesmott, itamar, jlmeram89, maxamillion, mcaspers, metherid, otaylor, pbrobinson, rakel1984, rderooy, rui.gouveia, samkraju, samuel-rhbugs, selliott4, theo148, walters | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||
| Whiteboard: | abrt_hash:dfbb42a3e795b3fca3f05ae67f61859d9dfbde58 | ||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2013-02-13 20:54:52 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Charles R. Anderson
2011-08-29 16:19:11 UTC
Created attachment 520423 [details]
File: maps
Created attachment 520424 [details]
File: backtrace
Package: gnome-shell-3.0.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I am unsure as to how this crash happened. Package: gnome-shell-3.0.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Don't know Package: gnome-shell-3.0.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- No idea what happened. Package: gnome-shell-3.0.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I have no idea what happened, submitting a backtrace. On my Fedora 15 64 bit system I get precisely the same crash when attempting to run FlightGear in fullscreen mode. I have some additional that may be helpful.
As mentioned in the attached backtrace the crash is on line 208 of brw_misc_state.c. The crash is is in then prepare_depthbuffer() function in the /usr/lib64/dri/i965_dri.so library, which is in the mesa-dri-drivers package.
Here is the entire small function in question with the crashing line marked with "// CRASH"
static void prepare_depthbuffer(struct brw_context *brw)
{
struct intel_context *intel = &brw->intel;
struct gl_context *ctx = &intel->ctx;
struct gl_framebuffer *fb = ctx->DrawBuffer;
struct intel_renderbuffer *drb = intel_get_renderbuffer(fb, BUFFER_DEPTH);
struct intel_renderbuffer *srb = intel_get_renderbuffer(fb, BUFFER_STENCIL);
if (drb)
brw_add_validated_bo(brw, drb->region->buffer); // CRASH
if (drb && drb->hiz_region)
brw_add_validated_bo(brw, drb->hiz_region->buffer);
if (srb)
brw_add_validated_bo(brw, srb->region->buffer);
}
On that line "drb->region" is a null pointer, so the attempt to dereference it to get "drb->region->buffer" crashes.
Is it reasonable for "drb" to be set, but for "drb->region" to be null? Should the "if" statement on the preceding line be "if (drb && drb->region)"? I'm not familiar enough with the code in question to know. Perhaps this bug should be reassigned to a Mesa component.
Also, not all fullscreen OpenGL applications crash on the same system. On my Fedora 13 system FlightGear works correctly in fullscreen mode. Unfortunately, my Fedora 13 system has a different graphics card (Intel crashed, Nvidia worked), so it's not a controlled experiment.
One other data point that I should have mentioned in my previous comment - I get the same crash when logged into "KDE Plasma Workspace" from the console, so it seems likely that gnome-shell is not directly involved. (In reply to comment #8) > One other data point that I should have mentioned in my previous comment - I > get the same crash when logged into "KDE Plasma Workspace" from the console, so > it seems likely that gnome-shell is not directly involved. Hi Steven, This scratch build fixed a similar bug for me (bug 735794), YMMV http://koji.fedoraproject.org/koji/taskinfo?taskID=3325495 Alon Package: gnome-shell-3.1.92-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Just login to F16 Package: gnome-shell-3.2.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This crash occurred while I was playing Alien Arena (3D acceleration seemed to stop working altogether until a reboot). Package: gnome-shell-3.2.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- playing nexuiz. *** Bug 756219 has been marked as a duplicate of this bug. *** putting ThinkPad on port-replicator with external DVI-D monitor attached backtrace_rating: 4 Package: gnome-shell-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 555019 [details]
File: backtrace
I used wine to play starcraft 2 backtrace_rating: 4 Package: gnome-shell-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 557441 [details]
File: backtrace
After resuming from suspension: the laptop woke up in a docking station with two different external monitors connected. When it suspended, it was running without any external device (on batteries in a cafe). Waking up the screen was weird and it seemed to detect the crash & attempt again screen initialization multiple times. I've hit ctrl+alt+backspace to restore operation, re-logged in and it didn't immediately seem to recover, but "tried again" and worked. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 558587 [details]
File: backtrace
Resuming from suspended laptop. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 560725 [details]
File: backtrace
Returning from a full screen SPICE session (RHEV) backtrace_rating: 4 Package: gnome-shell-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Created attachment 561728 [details]
File: backtrace
My laptop (Lenovo X200s) was docked with an external screen. The external screen was my main display and the laptop screen was off. I put the laptop to sleep, undock it and unsuspend later. The laptop sreen was black. I hit the Ctrl+{1,2,3} keys to try to get the screen back. After a while I got the gnome-screensaver unlock screen diaog. I entered my password and then I've been told the Shell was crashed.
I re-entered my password in GDM but for some reason the Shell was failing and so I've been logged into the fallback mode. I had to reboot to get the Shell working again.
backtrace_rating: 4
Package: gnome-shell-3.2.2.1-1.fc16
OS Release: Fedora release 16 (Verne)
Created attachment 562169 [details]
File: backtrace
Backtrace analysis of bugs across components suggests the actual bug is in component clutter, cogl or mesa instead of component gnome-shell, reassigning to clutter. Bugs which were found to be similar to this bug: gnome-shell: bug #756219 totem: bug #771965 This comment is automatically generated. *** Bug 771965 has been marked as a duplicate of this bug. *** I resumed from suspend. Before suspending, it was in a docking station with an external monitor and ethernet cable. I tried running gnome-shell manually after this and it still segfaults. I'm currently running metacity so I can shut things down nicely before rebooting. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Created attachment 582235 [details]
File: backtrace
I'm pretty sure it's either Mesa or the kernel. After this happened again, I was running metacity just so I could close applications nicely before rebooting. I tried running glxgears to test if 3d worked at all and as soon as it tried to draw, it crashed. See bug 821583, it crashes in the same function. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |