On Sun, May 27, 2012 at 03:08:56PM +0800, Guo Yixuan wrote: > On 05/03/2012 12:03 PM, Olly Betts wrote: >> You could try rebuilding boinc-manager against libwxgtk2.8-dbg >> instead of libwxgtk2.8-dev - this build has wx's debug checks on, which >> can spot a lot of incorrect uses of the wx API, so this might help to >> determine whether this is boinc-manager or wx at fault. > > I recompiled boinc with "--enable-debug" and "--enable-wx-debug", and > attached boincmgr's output (version: 7.0.25+dfsg-2). One log is taken > when boinc-client is running, and the other without boinc-client. > > By diff this two logs (stripping the timestamp first), I guess that this > part maybe of interest.
Thanks for trying that. It doesn't mean much to me, unfortunately - looks like this is a log from boinc rather than wx. Assuming you successfully built with the wx debug version (looks like boinc's configure will fall back to the non-debug version with a warning if it can't find the debug one), then it looks like we didn't catch any wx API misuse issues. However, I noticed that Ubuntu have recently included a patch for this menubar issue: http://trac.wxwidgets.org/ticket/13280 That sounds like it might fix the boinc issue, so I've included in it a new wxwidgets2.8 upload I've just made to unstable. Can you try 2.8.12.1-10 at see if that solve this issue? Cheers, Olly -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
