"Couldn't find or load the file skings/gartoon/bar_bg.jpg", it says. "This activity is incomplete. Exit it and report the problem to the authors." It's quite challenging to exit without a mouse cursor to locate the "OK" to click on :-) Even more so if you're in the default full screen mode, because then that's the "only" way to exit :-) Version-Release number of selected component (if applicable): gcompris-8.4.5-1.fc9 and gcompris-8.4.5-1.fc10 How reproducible: Every time
Thanks for reporting this! Actually there is a nasty bug in gcompris-8.4.5, which causes it to look for its file under "share/gcompris/boards" instead of under "/usr/share/gcompris/boards" Notice the small but huge "/usr/" difference, a fixed gcompris is currently building, see: http://koji.fedoraproject.org/koji/taskinfo?taskID=635574 http://koji.fedoraproject.org/koji/taskinfo?taskID=635584 http://koji.fedoraproject.org/koji/taskinfo?taskID=635590 As soon as these builds are completed, I'll push this as an update for F-8 and F-9. One important note, once you've had the gcompris crash this causes, you need to purge your gcompris settings: "rm -r ~/.config/gcompris"
gcompris-8.4.5-2.fc9 has been submitted as an update for Fedora 9
gcompris-8.4.5-2.fc8 has been submitted as an update for Fedora 8
gcompris-8.4.5-2.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gcompris'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-4917
FTR, gcompris-8.4.5-1 still won't start, but updating to 8.4.5-2 fixes it :-) (mocking at my own poor wording in the bug report subject) I had to remove ~/.config/gcompris indeed. Thanks!
gcompris-8.4.5-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
gcompris-8.4.5-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.