abrt detected a crash. How to reproduce ----- 1. 2. 3. Comment ----- Turning compositing (/apps/metacity/general/compositing_manager) on. Additional information ====== Attached files ---- backtrace cmdline ----- metacity component ----- metacity executable ----- /usr/bin/metacity kernel ----- 2.6.31.1-56.fc12.x86_64 package ----- metacity-2.28.0-1.fc12 reason ----- Process was terminated by signal 11
Created attachment 364346 [details] File: backtrace
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Are you running with multiple independent screens? (Sometimes known as Zaphod-mode. The way this would look is that you'd have multiple monitors and you could move the pointer between them but you couldn't drag windows between them.) There's an obvious logic bug in the code: MetaCompScreen *info = meta_screen_get_compositor_data (screen); if (info != NULL && info->all_damage) { XFixesUnionRegion (xdisplay, info->all_damage, info->all_damage, damage); XFixesDestroyRegion (xdisplay, damage); } else info->all_damage = damage; The info != NULL should apply to everything. But I'm not sure how you'd end up there with info == NULL. My only idea is that if you have multiple independent screens, compositing might only have been enabled for one of them.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.