Description of problem: After enabling core dumps, I've noticed a new core file in my home directory each new time I log in. It is from the metacity from the previous session. Version-Release number of selected component (if applicable): metacity-2.14.0-1 How reproducible: 100% Steps to Reproduce: 1. Add 'ulimit -c unlimited' to .bash_profile 2. Log in; log out 3. Log in; look for core file Actual results: #0 meta_compositor_unref (compositor=0x0) at compositor.c:162 162 if (compositor->repair_idle) #1 0x0000000000419bd5 in meta_display_close (display=0x6d9c20) at display.c:926 926 meta_compositor_unref (display->compositor); #2 0x000000000042b258 in main (argc=1, argv=0x7fffff89cee8) at main.c:505 505 meta_display_close (tmp->data); #3 0x000000376d71d084 in __libc_start_main () from /lib64/libc.so.6
FWIW (I didn't change this setting): [tim@cyberelk ~]$ gconftool-2 -g '/apps/metacity/general/compositing_manager' false
I'm getting this as well, on a plain old i386 Athlon.