abrt 1.0.3 detected a crash. How to reproduce ----- 1.install wine package. su - -c 'yum install wine.i686' 2. download winetest from winehq. wget http://test.winehq.org/builds/winetest-latest.exe 3.run the user32:win test from testsuite. wine winetest-latest.exe user32:win Comment ----- when running the wine test suite metacity crashes. despite this wines tests complete successfuly. metacity is automaticaly respawned after the crash. Attached file: backtrace cmdline: metacity component: metacity executable: /usr/bin/metacity kernel: 2.6.31.9-174.fc12.x86_64 package: metacity-2.28.0-14.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted)
Created attachment 384499 [details] File: backtrace
Can you try this after running metacity --sync --replace From a terminal? The --sync tells metacity not to do X operations asynchronously, so the X error will have a backtrace that actually shows what operation metacity tried to do; right now the backtrace here only indicates that some previous operation triggered an X error. If you can't get it to happen with --sync, then try it with just '--replace' and report here what gets printed by metacity to the terminal when it crashes. It will be say something like: Unexpected X error: <...> serial <...> error_code <...> request_code <..> minor_code <..> Knowing the request code may help identify the source of the problem.
(In reply to comment #2) --sync --replace just caused a segmentation fault, replace on it's own gave the error. [ams@hal ~]$ metacity --sync --replace Segmentation fault (core dumped) [ams@hal ~]$ metacity --replace Bug in window manager: Unexpected X error: BadAlloc (insufficient resources for operation) serial 56011 error_code 11 request_code 53 minor_code 0)
Ah, yes, the segfault is: https://bugzilla.gnome.org/show_bug.cgi?id=557514 What you could do to get a synchronized backtrace is log in from a different computer via ssh and do: DISPLAY=:0 gdb --args metacity --replace (gdb) r <hit control-c> (gdb) meta_set_syncing(1) (gdb) r <reproduce the crash>L (gdb) bt (if you do this from the same computer, it will be hard to interact with the desktop to get the backtrace when metacity is crashed) Request 53 is XCreatePixmap, and the error code is BadAlloc, so what happened was Metacity tried to create a window bigger than the screen. Do you have the metacity compositor on? If so, it's pretty likely any large window might crash the compositor this way - the metacity compositor isn't very well tested and we can't reall support it. (If you don't know what the metacity compositor is, you probably don't have it on, since it has to be turned on by editing a GConf key.) If you don't have the compositor on,I suspect what happened is that Wine created a truly large window, and in the process of drawing the border for that window, Metacity tried to allocate a temporary pixmap that was too big, and that crashed. There's not a ton we can do about this; it's possible that Metacity should put a hard limit on window sizes - maybe no bigger than twice the size of the display in both directions.
*** Bug 591227 has been marked as a duplicate of this bug. ***
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.