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.
http://bugs.winehq.org/show_bug.cgi?id=29128
Bug #: 29128
Summary: L.A. Noire fails to launch
Product: Wine
Version: 1.3.33
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: peanuthead_069(a)yahoo.com
Classification: Unclassified
Created attachment 37529
--> http://bugs.winehq.org/attachment.cgi?id=37529
Terminal log of launch attempt.
Well, since no one seems to have tested this game yet, I decided to take
matters into my own hands. The installer now works on 1.3.33, but the game
itself doesn't. All the necessary dependencies are installed already, but still
even the mandatory patch required to activate and launch the game doesn't work.
Even the no-spaces workaround when installing the game showed no signs of the
Noire launching.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47404
Bug ID: 47404
Summary: Across Freelance Translation Software shows
splashscreen but doesn't install
Product: Wine
Version: 4.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 64752
--> https://bugs.winehq.org/attachment.cgi?id=64752
Console output - wine 4.10 (staging)
Hello everyone,
I am trying to get a translation software called Across to run which can be
downloaded for free from:
https://www.my-across.net/en/download
sha256sum Across_v7.0_09618_TranslatorEdition.zip
2272f93d7dc17af660bbf3133a7c9
The application shows a splashscreen but installation does not start.
--
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=46616
Bug ID: 46616
Summary: ABBYY FineReader 14 crashes during installation
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tinywrkbee(a)gmail.com
Distribution: ---
Created attachment 63517
--> https://bugs.winehq.org/attachment.cgi?id=63517
ABBYY FineReader 14 default output
App: ABBYY FineReader 14, trial version, can be dowloaded freely from
https://www.abbyy.com/en-ee/lp/ee-finereader14-download-free-trial/
Wine: Wine: 4.1, WINEARCH=win32, Window 7, winetricks riched20.
Behavior: Crashing during installation.
Steps to reproduce:
Maybe not necessary but I chose the custom installation and disabled everything
except the base application.
Also, I unchecked the option to download updates and every other option in the
same screen.
Logs:
I'm attaching two logs. One with the default output and the second with
WINEDEBUG=+winspool,+localspl,+ntdll,+msi.
Be aware the second log size when extracted is 65MB.
--
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=46863
Bug ID: 46863
Summary: If prefix contains "windows" drive information not
available in 64-bit prefix
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: darktjm(a)gmail.com
Distribution: ---
All of my wine prefixes contain a path element called "windows" (actually, I
use c:\windows, always). When I try to run installers or anything else that
wants drive information, I get weird errors, starting with "Could not find DOS
drive for current working directory" and usually ending with installer failures
such as "The drive or UNC share you selected does not exist or is not
accessible". Usually 64-bit games work fine once I figure out a way to install
them anyway, such as direct extraction or 32-bit installs moved over.
I think I have traced it to dlls/ntdll/directory.c:lookup_unix_name. If the
full unix path has "windows" in it, and redirects are possible (true for
64-bit), the stat is skipped. However, if name_len is 0, it assumes
immediately after that the stat took place, and exits with an error ("drive
root doesn't exist"). To fix, I changed the redirect test to add !name_len
(line 2641 in 4.4):
if(!redirect || !name_len || (!strstr(....
A better fix might be to ignore "windows" if it's part of WINEPREFIX, so that
the longer version of the search isn't always necessary. Since I don't know
the code, I don't know how to skip over WINEPREFIX easily. With this fix, I
can finally run installers in 64-bit prefixes, at least.
This bug has plagued me since I first got 64-bit prefixes working at all for
myself, so around 2.0 or earlier. I only now got around to looking into it
because a particular game requires a particular 3rd party installer to work in
64-bit mode, so my usual tricks don't cut it any more.
--
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.