https://bugs.winehq.org/show_bug.cgi?id=48943
Bug ID: 48943
Summary: assasins creed 2 (uplay) camera spinning with
dualshock 4
Product: Wine
Version: 5.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: animegirl(a)stronzi.org
Distribution: ---
Created attachment 66918
--> https://bugs.winehq.org/attachment.cgi?id=66918
log
latest archlinux, latest wine-staging.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49020
Bug ID: 49020
Summary: Seg fault in wineserver in req_get_thread_context
Product: Wine
Version: 5.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: harry+winehq(a)unheit.net
Regression SHA1: c4dab9b76eb7397f6e5325ff4bdf792cf500e571
Distribution: ---
Seg fault of wineserver at server/thread.c:1851
Program terminated with signal SIGSEGV, Segmentation fault.
#0 req_get_thread_context (req=<optimized out>, reply=<optimized out>) at
thread.c:1928
1928 context->cpu = thread_context->regs.cpu;
(gdb) bt
#0 req_get_thread_context (req=<optimized out>, reply=<optimized out>) at
thread.c:1928
#1 0x5668ad25 in call_req_handler (thread=<optimized out>) at request.c:312
#2 0x566925c1 in thread_poll_event (fd=0x58748ca0, event=1) at thread.c:387
#3 0x56667186 in main_loop_epoll () at fd.c:490
#4 0x56667444 in main_loop () at fd.c:951
#5 0x56655ac5 in main ()
This is from wine-staging, line number is different. Code at this point is the
same.
thread_context is always NULL at this point.
Commit that introduced this bug is c4dab9b76eb7397f6e5325ff4bdf792cf500e571.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49000
Bug ID: 49000
Summary: update to 5.6 breaks libtool in usage of GNU autoconf
./configure
Product: Wine
Version: 5.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: noel.kuntze+bugs.winehq(a)thermi.consulting
Distribution: ---
When updating to 5.6, paths that are generated by libtool or GNU autoconf
(unknown which specifically) in third party programs, specifically by the
./configure script of GNU autoconf programs contain trailing newlines now. This
breaks the generated .libs/lb-*.c files.
A short excerpt of the troublesome section:
#if __GNUC__ < 4 || (__GNUC__ == 4 && __GNUC_MINOR__ < 5)
# define externally_visible volatile
#else
# define externally_visible __attribute__((externally_visible)) volatile
#endif
externally_visible const char * MAGIC_EXE = "%%%MAGIC EXE variable%%%";
const char * LIB_PATH_VARNAME = "PATH";
const char * LIB_PATH_VALUE =
"Z:\\home\\thermi\\UNITS\\Contauro_AG\\strongswan\\src\\libstrongswan\\.libs
;";
const char * EXE_PATH_VARNAME = "PATH";
const char * EXE_PATH_VALUE = "Z:\\usr\\x86_64-w64-mingw32\\lib
;Z:\\usr\\x86_64-w64-mingw32\\bin
;Z:\\usr\\local\\lib
;Z:\\usr\\local\\bin
;Z:\\home\\thermi\\UNITS\\Contauro_AG\\strongswan\\src\\libstrongswan\\.libs
;Z:\\usr\\local\\lib\\ipsec
;";
^ this is not valid C code (with Wine 5.5, there are no newlines between the
paths and the ; chararacters. That then is valid C code).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49021
Bug ID: 49021
Summary: When logging into a character, from the character
selection screen, it freezes after loading page is
done.
Product: Wine-staging
Version: 5.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eaglecomputers.ok(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
5.7 does not allow WoW to run, at least on the retail BFA. I have not checked
classic. If I revert to 5.6, everything works as expected, and the game works.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46545
Bug ID: 46545
Summary: WINEPREFIX doesn't work when ends with "windows"
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paleozogt(a)gmail.com
Distribution: ---
Created attachment 63407
--> https://bugs.winehq.org/attachment.cgi?id=63407
wine default prefix
Setting WINEPREFIX to something that ends with "windows" (e.g., $HOME/windows)
causes wineboot to create a broken wine instance.
In particular, C:\ won't exist, for example:
> ~ wine cmd /C dir 'C:\'
> Volume in drive C has no label.
> Volume Serial Number is 0000-0000
>
> Directory of C:
>
> File not found.
whereas with the default prefix C:\ is fine:
> ~ wine cmd /C dir 'C:\'
> Volume in drive C has no label.
> Volume Serial Number is 0000-0000
>
> Directory of C:
>
> 1/28/2019 11:31 AM <DIR> Program Files
> 1/28/2019 11:31 AM <DIR> Program Files (x86)
> 1/28/2019 11:31 AM <DIR> ProgramData
> 1/28/2019 11:31 AM <DIR> users
> 1/28/2019 11:31 AM <DIR> windows
> 0 files 0 bytes
> 5 directories 90,299,498,496 bytes free
Setting WINEPREFIX to other values seems to work fine (e.g., $HOME/win). Why
is "windows" special? Are there any other special values that WINEPREFIX
shouldn't use?
See the attached console log for more details.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39807
Bug ID: 39807
Summary: Cannot install a programm
Product: Wine
Version: 1.7.55
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: msrom(a)mail.ru
Distribution: ---
Created attachment 53142
--> https://bugs.winehq.org/attachment.cgi?id=53142
log
Cannot install the ABBYY Aligner
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39224
Bug ID: 39224
Summary: Warcraft 3: Sound rustles without -opengl
Product: Wine
Version: 1.7.50
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
If Warcraft 3 is started without the -opengl option I'm hearing at the
startscreen besides the normal music a quiet rustle.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39570
Bug ID: 39570
Summary: Multiple application crash handlers fail to load
symbol information using 'dbghelp.SymLoadModule64',
reporting 'dbghelp:validate_addr64 Unsupported address
0xfffffffffxxxxxxx'
Product: Wine
Version: 1.7.54
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
the issue/question was raised in
https://bugs.winehq.org/show_bug.cgi?id=32237#c15
--- quote ---
I did try 2012 this time and I end up crashing
fixme:dbghelp:validate_addr64 Unsupported address fffffffff33a0000
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x7bc3db51
What's wrong with the address?
--- quote ---
Searching the Internet reveals this pattern/message many times - also in Wine
Bugzilla - but no or even incorrect explanation - until now ;-)
On 64-bit Linux machines, the Wine loader allows 32-bit dlls being mapped at
high >2GB, >3GB address ranges in 32-bit processes, not having certain (design)
restrictions of 32-bit process address space layout on 64-bit Windows machines
(even with /LARGEADDRESSWARE).
Good case, 32-bit Wine builtin dll mapped < 2 GiB virtual address space range:
--- snip ---
...
0009:Call PE DLL (proc=0x7e1b6838,module=0x7e1b0000
L"wsock32.dll",reason=PROCESS_ATTACH,res=0x1)
...
0027:Call dbghelp.SymLoadModule64(ffffffff,00000000,0b36a960
"C:\\windows\\system32\\wsock32.dll",0b36a988
"wsock32.dll",7e1b0000,00000000,0000e000) ret=005eff32
0027:trace:dbghelp:SymLoadModuleEx (0xffffffff (nil)
"C:\\windows\\system32\\wsock32.dll" "wsock32.dll" 7e1b0000 0000e000 (nil)
00000000)
...
0027:trace:dbghelp:SymLoadModuleExW (0xffffffff (nil)
L"C:\\windows\\system32\\wsock32.dll" L"wsock32.dll" 7e1b0000 0000e000 (nil)
00000000)
...
0027:trace:dbghelp:elf_load_file Processing elf file
'L"/home/focht/projects/wine/wine.repo/install/bin/../lib/wine/wsock32.dll.so"'
at 7e1a2000
...
0027:Ret dbghelp.SymLoadModule64() retval=7e1b0000 ret=005eff32
--- snip ---
Bad case, 32-bit Wine builtin dll mapped near end of 4 GiB virtual address
space range:
--- snip ---
...
0009:Call PE DLL (proc=0xf734e3fc,module=0xf72f0000
L"winex11.drv",reason=PROCESS_ATTACH,res=(nil))
...
0027:Call dbghelp.SymLoadModule64(ffffffff,00000000,0b36a960
"C:\\windows\\system32\\winex11.drv",0b36a988
"winex11.drv",f72f0000,ffffffff,00090000) ret=005eff32
0027:trace:dbghelp:SymLoadModuleEx (0xffffffff (nil)
"C:\\windows\\system32\\winex11.drv" "winex11.drv" fffffffff72f0000 00090000
(nil) 00000000)
"winex11.drv",ffffffff,2d053b40,0000000c) ret=edbc2fa6
...
0027:trace:dbghelp:SymLoadModuleExW (0xffffffff (nil)
L"C:\\windows\\system32\\winex11.drv" L"winex11.drv" fffffffff72f0000 00090000
(nil) 00000000)
0027:fixme:dbghelp:validate_addr64 Unsupported address fffffffff72f0000
...
0027:Ret dbghelp.SymLoadModule64() retval=00000000 ret=005eff32
--- snip ---
In this specific case, the game registered an own crash handler which dumps
various debugging information in case of a crash.
'dbghelp.SymLoadModule64' is called by the custom crash handler.
Source:
https://source.winehq.org/git/wine.git/blob/1fa7710ff92dd9555b2b4753e22ce5f…
--- snip ---
656 DWORD64 WINAPI SymLoadModule64(HANDLE hProcess, HANDLE hFile, PCSTR
ImageName,
657 PCSTR ModuleName, DWORD64 BaseOfDll, DWORD
SizeOfDll)
658 {
659 return SymLoadModuleEx(hProcess, hFile, ImageName, ModuleName,
BaseOfDll, SizeOfDll,
660 NULL, 0);
661 }
--- snip ---
So how does high DWORD of 'BaseOfDll' parameter get the 0xffffffff value?
A few caller frames up in the app crash handler:
--- snip ---
...
005F06D6 8B55 D0 MOV EDX,DWORD PTR SS:[EBP-30]
005F06D9 8B45 CC MOV EAX,DWORD PTR SS:[EBP-34]
005F06DC 8B4D F8 MOV ECX,DWORD PTR SS:[EBP-8]
005F06DF 52 PUSH EDX
005F06E0 99 CDQ
005F06E1 52 PUSH EDX ; high DWORD BaseOfDll
005F06E2 50 PUSH EAX ; low DWORD BaseOfDll
005F06E3 8B45 FC MOV EAX,DWORD PTR SS:[EBP-4]
005F06E6 50 PUSH EAX
005F06E7 51 PUSH ECX
005F06E8 8B4D E8 MOV ECX,DWORD PTR SS:[EBP-18]
005F06EB 56 PUSH ESI
005F06EC E8 EFF7FFFF CALL A_Slower.005EFEE0
...
--- snip ---
'winex11.drv' -> 0xf72f0000
Since the highest bit in low 32-bit 'BaseOfDll' DWORD is set, the 'CDQ'
instruction copies the sign (bit 31) of the value in the EAX register into
every bit position in the EDX register.
Voila - you get the 0xffffffff EDX value which is then propagated through the
caller chain as high 32-bit 'BaseOfDll' DWORD to 'dbghelp.SymLoadModule64',
leading to symbol load failure and fixme/warning messages.
This should be fixed, allowing symbol information even for dlls mapped in high
address range to be loaded.
$ wine --version
wine-1.7.54-261-g61c49bd
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=32237
Bug #: 32237
Summary: A slower speed of light: Game crashes after Intro
Product: Wine
Version: 1.5.14
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fox6x6x6(a)gmail.com
Classification: Unclassified
Created attachment 42525
--> http://bugs.winehq.org/attachment.cgi?id=42525
wine output
The game starts normally and you can watch the Intro, but after that the game
crashes.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.