Hello Fellow Slackware Users,

I have come across this bug in wine and so far it seems only to effect Slackware:

http://bugs.winehq.org/show_bug.cgi?id=15895

Does Slackware have a different filesystem or similar that would introduce issues on wine?

The wine was installed using the Slackbuilds.org script.

Thank,
Murdock

I just gave it a try and I am able to reproduce this every single time too. It could be many things... I've already tried in three diferent filesystems (by symlinking ~/wine/drive_c/windows/temp to different places) and that didn't make a difference.

I'm using wine 1.1.5 and even tried using the native rsaenh, msisip and wintrust dlls with no success.

That's weird it does it here too along with a million errors of:

Hello,

I haven't myself tried it on other distros yet, but so far, from the bug report, it seems that it works fine for those who did.

It's a mystery to me what difference Slackware has from other distributions regarding Wine. Hopefully, the developers will figure something out.

Murdock

Weird I use wine regularly on Slackware 12.1 and have no such problems.

Hello,

I use Wine regularly as well and it does not give me any issues...this is a real mystery since other distros do not have this problem and Slackware is probably the most "Vanilla" disto out there.

Murdock

Unlikely. I think you are jumping to conclusions too quickly - developers hasn't confirmed that it is a slackware bug.

I am running Wine 1.1.5 built from source with a modified SlackBuild - no issues for me... works on two very dissimilar systems.

This looks like a non-issue. So far, no-one's claimed to have tested Wine on both Slackware and another distro. However, anyone who can confirm that the problem a) exists and b) affects Slackware but not some other distro should ask the following:

Which patches do the other distro apply to Wine?

After applying those patches to Wine, building it on the Slackware system, and then reinstalling, does the problem persist?

If not, the problem is easy to isolate.

I'm not a wine user, but I've added myself to the CC list on that bug, just in case it turns out to be something specific to us.

Hello,

So far, Theoffset (second posting on thread) and myself were able to reproduce this bug. However, Astrogeek did not seem to have any problems at all, as well as users of other distros as stated in the bug log.

Astrogeek: what modification did you do to the slackbuild script?

Murdock

I used the SlackBuild.org script which was written for wine 1.0 and I simply changed the version number to 1.1.5 and changed the MD5 sum in the slack.info file (from memory, on a different machine at the moment).

I use wine for a single application so do not give it a regular workout, but it does not exhibit the problem you describe or any others that I know of.

[EDIT]Incidentally, regarding other distros - I also compile my own wine under Mandriva 200/6/7 and built my Wine-1.1.5 on Slack from the same tarball I used for Mandriva and have no problems with either distro, FWIW.[/EDIT]

There is no indication whatsoever that they were using other distros.

Thanks for the update, Astrogeek.

Just one last question before I leave this thread for the time being, did you download that very binary on the bug log and try running it?

Dugan: one of the testers used Fedora 9 or 10.

Murdock

No I did not, but I will be at one of those machines in the next few hours and will try it exactly as you describe in the bug report and post back later.