http://bugs.winehq.org/show_bug.cgi?id=18672
--- Comment #9 from Nikolay Sivov bunglehead@gmail.com 2009-06-01 04:00:05 --- (In reply to comment #8)
thank you for your insight, and for including the +ole trace; unfortunately I'm afraid my still limited competence of Wine prevents me from fully understanding your remark.
Hi, Stefano.
Use this first of all http://wiki.winehq.org/FAQ. It has lot of common questions answered.
I posted a registry export file which contains a registration entry for class your app is requesting. It looks like it's a minimal needed info to start.
You could easily apply it running: --- regedit pbrush.reg ---
Full ole log seems to be unnecessary but you can always use the FAQ on available debug channels and command lines.
Does this mean that the bug will be resolved via somehow circumventing it, rather than addressing it directly? Thank you for clarifying.
I don't think that it's a hack actually. The commit your app is failing on makes an internal Wine test pass, so these changes are reasonable. It works without it cause a problem with registration info loss is hidden by always-successful return code (S_OK).