Fable breaks from wine 1.1.10 to 1.1.11

fcmartins · Post by **fcmartins** » Sun Mar 15, 2009 4:25 pm

Hi,

I guess I should open a bug in bugzilla. Some questions: I installed 1.1.10 and 1.1.11 through PlayOnLinux. Does this make a difference for the bug reporting?

I have the output from the terminal (backtrace below). What could I do to provide more useful information?

I suppose the next step would be to do a bisect but I've never done it and I suspect I'll need quite a bit of time.

=>0 0x7e5384d7 (0x002fd644)
1 0x7e56d2b5 (0x002fd694)
2 0x7e542667 (0x002fd6b4)
3 0x7e4f7edd (0x002fd714)
4 0x7e52be2e (0x002fda24)
5 0x7e5041bd (0x002fda64)
6 0x7e5e7a1f in d3d9 (+0x7a1f) (0x002fda94)
7 0x=>0 0x7e5384d7 (0x002fd644)

vitamin · Post by **vitamin** » Sun Mar 15, 2009 5:34 pm

fcmartins wrote:Hi,

I guess I should open a bug in bugzilla. Some questions: I installed 1.1.10 and 1.1.11 through PlayOnLinux. Does this make a difference for the bug reporting?

Yes, you should only use vanilla Wine to report any bugs to Wine bugzilla.

If you know that things broke between one version and another, try to do regression testing as described here: http://wiki.winehq.org/RegressionTesting
Or at least find a downloadable demo version that shows the same problem.

fcmartins · Post by **fcmartins** » Tue Mar 17, 2009 4:16 pm

I've done the bisect and reported the bug http://bugs.winehq.org/show_bug.cgi?id=17774.

However, I have no way that I can see to add a bug to the appdb entry for Fable and right now I can't even add a comment. I'm logged in and when I press "Post new comment", it asks again for the login and then returns with the error: No class defined.

James McKenzie · Post by **James McKenzie** » Tue Mar 17, 2009 9:22 pm

fcmartins wrote:

I've done the bisect and reported the bug http://bugs.winehq.org/show_bug.cgi?id=17774.

However, I have no way that I can see to add a bug to the appdb entry for Fable and right now I can't even add a comment. I'm logged in and when I press "Post new comment", it asks again for the login and then returns with the error: No class defined.

Try again, the server was down for hardware maintenance.

James McKenzie

fcmartins · Post by **fcmartins** » Wed Mar 18, 2009 1:50 am

Well, I still had the issue, but logging out and in again fixed it.

Something else, I could not cc the author of the patch in the bug report, I got a message like "address not recognised" or something like that.

Latter, I saw another name in the copyright section of wine3d files, Stefan Dosinger, which I suppose is the current maintainer. Should I try to reach the developer or bug triage is working well enough (I indicated the DirectX component)?

austin987 · Post by **austin987** » Sat Mar 21, 2009 7:07 pm

On Wed, Mar 18, 2009 at 1:50 AM, fcmartins <[email protected]> wrote:

Well, I still had the issue, but logging out and in again fixed it.

Something else, I could not cc the author of the patch in the bug report, I got a message like "address not recognised" or something like that.

Henri uses two different addresses, one for patches, one for bugzilla.

Latter, I saw another name in the copyright section of wine3d files, Stefan Dosinger, which I suppose is the current maintainer. Should I try to reach the developer or bug triage is working well enough (I indicated the DirectX component)?

No, it should be fine. D3D is a _fast_ moving component. The bug may
not show activity immediately, but you should try more recent versions
to see if it gets fixed.

--
-Austin

fcmartins · Post by **fcmartins** » Sun Mar 22, 2009 6:30 am

Weird: I could swear I tried it either with 1.1.16 or 1.1.17 (from wine deb repository) before trying git bisect and now Fable "works" with both (1.1.17 deb and 1.1.16 from git). Then I compiled wine 1.1.14 (which I reported in this forum not working for Fable) and indeed Fable crashes.

THEN, after 1.1.14 crash, I try again with 1.1.17 and it stopped working!

All the time, I've always been using the same wine prefix (exclusively for Fable) and the same Fable install (it's quite time consuming to redo it).

I noticed that wine updates the prefix (there is a message claiming it). So, one of the wine versions I tried (1.1.10, I guess) has (positively) updated the prefix, and then 1.1.14 has made a broken update to the prefix.

So, what exactly is being updated in the prefix by wine, when it encounters a prefix from a different version?

fcmartins · Post by **fcmartins** » Sun Mar 22, 2009 8:56 am

ok, there is some system brittleness going on. Starting Fable with wine 1.1.17 after an X restart has worked out always fine. In a non-fresh login it might crash but not in a manner I can reproduce. I don't think this is a wine issue.