WineHQ Bugzilla – Bug 34786 – Dungeons & Dragons Online (ddo) fails to open data files with 1.7.4+

Bugzilla

Last modified: 2013-11-22 12:50:57 UTC

Dungeons & Dragons Online (ddo) fails to open data files with 1.7.4+

Bug 34786 - Dungeons & Dragons Online (ddo) fails to open data files with 1.7.4+


Summary:	Dungeons & Dragons Online (ddo) fails to open data files with 1.7.4+

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.7.4
Hardware:	x86 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:	regression

Depends on:
Blocks:
	Show dependency tree

Reported:	2013-10-23 10:20 UTC by David Philippi
Modified:	2013-11-22 12:50 UTC (History)
CC List:	0 users

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
Log of the error messages from normal wine invocation. (1.07 KB, text/plain) 2013-10-23 10:20 UTC, David Philippi	Details
View All Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description David Philippi 2013-10-23 10:20:21 UTC

Created attachment 46389 [details]
Log of the error messages from normal wine invocation.

Starting with 1.7.4, I get the following error message.

Can't open the data files. Check that they exist and you have permission to write to them.
1.7.3 (gentoo ebuild) works fine, 1.7.4 and git (gentoo wine-9999, 23.10.13) fail with the error above.

Error messages about PyLotro in the log can probably be ignored as this launcher looks normal and at the time of the error message the dndclient.exe process is running.

Comment 1 Austin English 2013-10-23 13:06:05 UTC

Please run a regression test:
http://wiki.winehq.org/RegressionTesting

Comment 2 David Philippi 2013-10-23 14:25:54 UTC

I'd like to do that, even tried it before submitting bug. But even though gentoo git ebuild runs fine, I couldn't get it to compile. I'm using AMD64 multilib setup which makes things a little bit more complex.

Tried to apply the gentoo patches and copied the configure line executed in an ebuild run. Configure went well and then I got some assembler error...
That was the point when I gave up, hoping that the bug might ring a bell and get marked duplicate of something I don't recognize. ;-)

If some 64bit gentoo user can give me a todo list (or someone else strong hints) I'll happily do it. Didn't find anything really usefull during a couple of hours experimenting and while I can code in C/C++ myself, I've never dug into multilib stuff.

Comment 3 David Philippi 2013-10-23 14:30:01 UTC

Forgot to mention: before copying stuff out of the ebuild I tried it with the instructions I found on winehq but that ended with gstreamer/png headers not being found. CTRL-Z on the ebuild to copy out the lines at least got me into compiling but duplicating everything done there got a bit complex.
If need be, I can try to find out what the gentoo specific commands do and wheter I can use them without the usual ebuild environment variables set and so on.

Comment 4 Austin English 2013-10-24 00:22:55 UTC

(In reply to comment #3)
> Forgot to mention: before copying stuff out of the ebuild I tried it with the
> instructions I found on winehq but that ended with gstreamer/png headers not
> being found. CTRL-Z on the ebuild to copy out the lines at least got me into
> compiling but duplicating everything done there got a bit complex.
> If need be, I can try to find out what the gentoo specific commands do and
> wheter I can use them without the usual ebuild environment variables set and so
> on.

Works fine on my gentoo machine, with a 64-bit multilib profile and the emul-linux-x86* packages.

If you need help compiling wine, please use the forums.

Comment 5 David Philippi 2013-11-12 10:30:04 UTC

I can report this bug as fixed. I didn't manage to regression test it yet, but starting my holidays I went with testing HEAD first and it's gone.

I've asked on the gentoo forums how to setup my branch for bisect, if wanted I can still do it for this bug later on. Otherwise I'll just keep the git checkout around for possible future use.

Comment 6 Alexandre Julliard 2013-11-22 12:50:57 UTC

Closing bugs fixed in 1.7.7.