Created attachment 759883 [details]
lel

Description of problem:
Many, and many "x-caja-desktop" windows after login, I don't know what cause the problem, but isn't the first time I have this problem, and the windows still open and open again even if you kill the process, never stop, just reboot your desktop.


Version-Release number of selected component (if applicable):

mate-applets-1.6.1-1.fc18.x86_64
mate-backgrounds-1.6.0-1.fc18.noarch
mate-bluetooth-1.6.0-1.fc18.x86_64
mate-bluetooth-libs-1.6.0-1.fc18.x86_64
mate-calc-1.6.0-1.fc18.x86_64
mate-character-map-1.6.0-4.fc18.x86_64
mate-control-center-1.6.0-1.fc18.x86_64
mate-corba-1.4.1-1.fc18.x86_64
mate-desktop-1.6.1-6.fc18.x86_64
mate-desktop-extra-release-18-1.fc18.noarch
mate-desktop-libs-1.6.1-6.fc18.x86_64
mate-dialogs-1.6.0-1.fc18.x86_64
mate-file-archiver-1.6.0-1.fc18.x86_64
mate-file-manager-1.6.1-4.fc18.x86_64
mate-file-manager-extensions-1.6.1-4.fc18.x86_64
mate-file-manager-image-converter-1.6.0-1.fc18.x86_64
mate-file-manager-open-terminal-1.6.0-1.fc18.x86_64
mate-file-manager-sendto-1.6.0-1.fc18.x86_64
mate-icon-theme-1.6.0-1.fc18.noarch
mate-image-viewer-1.6.0-1.fc18.x86_64
mate-keyring-1.6.0-2.fc18.x86_64
mate-keyring-pam-1.6.0-2.fc18.x86_64
mate-media-1.6.0-2.fc18.x86_64
mate-menu-editor-1.6.0-1.fc18.noarch
mate-menus-1.6.0-1.fc18.x86_64
mate-menus-libs-1.6.0-1.fc18.x86_64
mate-netspeed-1.6.0-1.fc18.x86_64
mate-notification-daemon-1.6.0-1.fc18.x86_64
mate-panel-1.6.0-1.fc18.x86_64
mate-panel-libs-1.6.0-1.fc18.x86_64
mate-polkit-1.6.0-1.fc18.x86_64
mate-power-manager-1.6.1-1.fc18.x86_64
mate-screensaver-1.6.0-1.fc18.x86_64
mate-session-manager-1.6.0-3.fc18.x86_64
mate-settings-daemon-1.6.0-1.fc18.x86_64
mate-system-log-1.6.0-1.fc18.x86_64
mate-system-monitor-1.6.0-1.fc18.x86_64
mate-terminal-1.6.1-5.fc18.x86_64
mate-text-editor-1.6.0-1.fc18.x86_64
mate-themes-1.6.0-1.fc18.noarch
mate-themes-extras-3-1.6.1-1.fc18.noarch
mate-utils-1.6.0-1.fc18.x86_64
mate-window-manager-1.6.1-1.fc18.x86_64

This bug was also present in Mate 1.4 and 1.5.X


Steps to Reproduce:
I don't do this to get the bug, but I know that you maybe can get this problem if you.
1. Make a "sudo caja" or "su -c caja"
2. Close caja and then Log off
3. Log in, and Booala, Caja fill your RAM.