Created attachment 518834 [details] screenshot of boinc-manager's window Description of problem: boinc-manager's menu bar is displayed in a *very* poor way (screenshot attached) Version-Release number of selected component (if applicable): Version : 6.10.58 Release : 3.r22930svn.fc14 How reproducible: 100% Steps to Reproduce: 1. run boinc-manager 2. see the menu bar Actual results: menu bar is displayed incorrectly (almost not) Expected results: menu bar is displayed correctly Additional info: Sorry for bad component, I wasn't able to find boinc-manager in the list. I've tried some other wxGTK-based apps and they run without any problems.
*** Bug 719876 has been marked as a duplicate of this bug. ***
Confirming, filed upstream at http://boinc.berkeley.edu/trac/ticket/1130
There is a simple workaround -- if you resize the window, whole menu bar appears.
Same problem here. Fedora 16 x86_64 boinc-manager-6.10.58-3.r22930svn.fc15.x86_64
Should not we close this bugreport as UPSTREAM?
Any news?
ping?
I have this bug also. It was present in Fedora 16 and is also present in Fedora 17. As the reporter indicated, resizing the BOINC Manager window returns the complete menu bar to view.
@milos - there seems to be a fix upstream: http://boinc.berkeley.edu/trac/changeset?reponame=boinc&new=25702%40trunk&old=25701%40trunk could you patch the fedora package to include that fix? -- sven
I already did that -- there is a scratch build available in Koji, I will submit it as an update soon (hopefully today).
boinc-client-7.0.29-1.r25790svn.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-9859/boinc-client-7.0.29-1.r25790svn.fc17
boinc-client-7.0.29-1.r25790svn.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to comment #12) > boinc-client-7.0.29-1.r25790svn.fc17 has been pushed to the Fedora 17 stable > repository. If problems still persist, please make note of it in this bug > report. I can confirm that the new build resolves this bug. Thanks for fixing.