Description of problem: Gnome-Do is very buggy right now, I rarely can keep it running for too long, not sure what is causing the issues. I'm having issues with it using 100% of my Core2Duo, and crashing or going into "Raw Text" mode which makes the program useless. According to a blog post they just released 0.8.3.1 which should fix many of these issues. I would like to request that 0.8.3.1 be put as an update into the Fedora 12 repos. Thanks. Version-Release number of selected component (if applicable): Gnome-Do 0.8.2-5 (Current in Fedora 12 Repos) Gnome-Do 0.8.3.1 (Needed to fix bugs in Fedora 12)
Hey Steve, I'll update to 0.8.3.1 asap. This ticket will be updated once it lands on updates-testing and stable.
*** Bug 547823 has been marked as a duplicate of this bug. ***
gnome-do-0.8.3.1-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/gnome-do-0.8.3.1-1.fc11
gnome-do-0.8.3.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gnome-do-0.8.3.1-1.fc12
gnome-do-0.8.3.1-1.fc12 has been pushed to the Fedora 12 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 gnome-do'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-13660
gnome-do-0.8.3.1-1.fc11 has been pushed to the Fedora 11 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 gnome-do'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-13665
gnome-do-0.8.3.1-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
gnome-do-0.8.3.1-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.