Hide Forgot
Description of problem: mate-panel will not run if mate-file-manager-schemas is not installed (of course it is normally installed with @mate-desktop). Nevertheless sometimes one may not want to install all of @mate-desktop to have a basic desktop with a mate-panel. So I would like to suggest adding Requires: mate-file-manager-schemas to mate-panel.spec, so that mate-panel will work out of the box. How reproducible: 100% Steps to Reproduce: 1. do a basic-desktop install 2. install mate-panel 3. try to run mate-panel from a basic-desktop session Actual results: $ mate-panel (mate-panel:13461): GLib-GIO-ERROR **: Settings schema 'org.mate.caja.desktop' is not installed Trace/breakpoint trap Expected results: mate-panel to run Additional info: After installing mate-file-manager-schemas it runs normally.
mate-panel-1.6.1-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-panel-1.6.1-4.fc19
mate-panel-1.6.1-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-panel-1.6.1-4.fc20
mate-panel-1.6.1-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-panel-1.6.1-4.fc18
Package mate-panel-1.6.1-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-panel-1.6.1-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16511/mate-panel-1.6.1-4.fc20 then log in and leave karma (feedback).
mate-panel-1.6.1-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mate-panel-1.6.1-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mate-panel-1.6.1-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.