Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34819 - wine does not work for new installation

Attached to Project: Community Packages
Opened by Tianyu Liu (lty1993) - Wednesday, 17 April 2013, 01:27 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 22 April 2013, 13:31 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Florian Pritz (bluewind)
Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
New installed wine does not work. Error message shows below. But, if I install previous version of wine, every thing is fine. Also, I have another laptop installed wine long times before, and I upgraded to newest version, it works fine. I think this bug will happened when it need to create a new wine prefix.

[tanly@Tanly-PC ~]$ winecfg
wine: created the configuration directory '/home/tanly/.wine'
err:process:start_wineboot failed to start wineboot, err 1359
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
err:winecfg:WinMain failed to restart 64-bit L"C:\\windows\\system32\\winecfg.exe", err 1359


Steps to reproduce:
0. install newest version of wine which in Multilib
1. remove ~/.wine
2. start winecfg
3. you will see this bug
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 22 April 2013, 13:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.5.28-2
Comment by Emil (xexaxo) - Thursday, 18 April 2013, 18:16 GMT
Related to x64-86 vs gcc 4.8 vs wine

Namely, gcc is corrupting the heap when build with -O2 or greater
Workaround, rebuild with -O1

http://bugs.winehq.org/show_bug.cgi?id=33307
Comment by Emil (xexaxo) - Sunday, 21 April 2013, 10:31 GMT
From original bugreport - "-fno-builtin-memcpy" is enough
Workaround tested and working

A quick look indicates that wine is using memmove in all cases whenever memcpy is called, to protect itself from the "src and dst must not overlap" case. With more than 4k cases of memcpy, it's unlikely that wine will fix it's code, more likely they will ship with the optimization explicitly disable :P



Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 22 April 2013, 09:41 GMT
Please check wine rel -2.

Loading...