https://bugs.winehq.org/show_bug.cgi?id=48602
Bug ID: 48602
Summary: Kindle for PC installer 1.26.55076 crashes on
execution
Product: Wine
Version: 5.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bug.reporter(a)mail.sheugh.com
Distribution: ---
Created attachment 66439
--> https://bugs.winehq.org/attachment.cgi?id=66439
Text output from ./KindleForPC-installer-1.26.55076.exe
This is a new Wine installation, and this is the first application I tried to
run. I am going to add some things just in case it is relevant.
It is desired to install the latest Kindle for Windows version
following generally the advice set out here:
https://ajreissig.com/kindle-linux-read-kindle-books-linux-system/
Option 3 of the guidance "Conversion" was followed.
An additional complication is that Kindle offers books sourced
from both www.amazon.com and from www.amazon.co.uk, hence for
at least the initial installation, www.amazon.com will be used.
The first attempt, with the most recent download from Amazon,
failed. The version before build 38420 from filehippo appeared
to function correctly, but timed out when I attempted to
register the application. I later found that Amazon had emailed
a one-time code to me to allow completion of the registration.
Although Q4Wine is installed, for test purposes, the commandline
will be used to execute the attempted re-installation of the
latest Kindle Application.
cd ~/.wine/drive_c/Program\ Files/
./KindleForPC-installer-1.26.55076.exe
chmod to make the file executable
The execution fails after opening a window offering the choice of a cancel or
opening the wine debug. There are some warning messages.
Wine offered to install wine mono and that seemed to complete ok.
Wine then offered to install gecko
Clicking Ok produced a bunch of fixme messages.
The execution appears to have hung.
I will have a look at the things Wine complained about and attempt a reinstall.
sha1sum ./KindleForPC-installer-1.26.55076.exe
d3407d11d8fcd2f146516b5fd96fa2fcaf73ffcb
./KindleForPC-installer-1.26.55076.exe
--
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=44076
Bug ID: 44076
Summary: LA NOIRESteam Version crash at startup
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 59792
--> https://bugs.winehq.org/attachment.cgi?id=59792
LA NOIRE Wine 2.21-staging terminal log
Hello,
I installed LA NOIRE Steam version, it crashed at start.
I joined you terminal log and backtrace.
nota: I installed Dotnet 3.5, directx9 and vcredist.
--
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=32336
Bug #: 32336
Summary: finereader 11 trial version install fails and
rollbacks
Product: Wine
Version: 1.5.18
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
Created attachment 42679
--> http://bugs.winehq.org/attachment.cgi?id=42679
Log: install ABBYY FineReader 11
We have a similar bug for ABBYY finereader 10: Bug 27325
However, +msi console log is different between ABBYY finereader 10 and ABBYY
finereader 11, I'm not sure if this bug is a duplication.
1. Download trial version from
http://download.abbyy.cn/dist/fr11/ABBYY_FineReader_11_Chinese.exe
2. run the outer installer, it will extract and run the inner installer
$ wine ABBYY_FineReader_11_Chinese.exe
3. click "安装 ABBYY FineReader 11" of the inner installer
4. the install wizard will ask you to install MSXML6, either install it or skip
it.
5. run the real ABBYY FineReader installer
There is something wrong and the installation will be rollback.
Here is a workaround:
1. run the outer installer and extract the inner installer
2. run the inner installer with DISABLEROLLBACK=1
$ msiexec /I ABBYY\ FineReader\ 11.msi TRANSFORMS="C:\Temp\ABBYY FineReader
11\2052.mst" /Liwrmo\!vepacu "C:\users\fracting\Temp\ABBYY FineReader 11.log"
LAUNCH_FROM_SETUP=1 DISABLEROLLBACK=1
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=39847
Bug ID: 39847
Summary: Installation ABBYY Aligner2
Product: Wine
Version: 1.8
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 53196
--> https://bugs.winehq.org/attachment.cgi?id=53196
log
Cannot install application ABBYY Aligner2
--
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=44077
Bug ID: 44077
Summary: Overwatch: Within the first minute of game play the
entire OS stops rendering (requires hard reboot)
Product: Wine-staging
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sander.smid(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
wine-2.21 (Staging)
Linux oribi 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64
GNU/Linux
Graphics: Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/580]
Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded:
modesetting,fbdev,nv,vesa,nouveau)
Resolution: 1920x1200(a)59.95hz
OpenGL: renderer: AMD Radeon RX 480 Graphics (AMD POLARIS10 / DRM
3.18.0 / 4.13.12-1-ARCH, LLVM 5.0.0)
version: 4.5 Mesa 17.2.5
env WINEPREFIX="/games/BattleNet" /usr/bin/wine
/games/BattleNet/drive_c/Program\ Files\ \(x86\)/Overwatch/Overwatch.exe
--
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=45899
Bug ID: 45899
Summary: Tray icons don't react when you left click or right
click on them
Product: Wine-staging
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: guih.rox(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
All programs with a tray icon that I've tested so far with Wine Staging 3.16
don't work when you try to interact with it, by trying to left or right
clicking on it.
This is not reproducible with Vanilla Wine however.
There's a small program called TurnFlash
(https://www.nirsoft.net/utils/tflash2.html) that can be used to observe this
behavior:
Download link: https://www.nirsoft.net/utils/tflash210.zip
SHA-1 sum for tflash.exe: 15f877867b45d51a2a8257494bb3128f1b0d087f
After you run it, you should get no output from wine, but you'll see a blue
icon added to the system tray of your Desktop Environment (in my case, it's KDE
Plasma 5.13.5).
The first thing I tried was checking checked my journal using `journalctl -f`,
this is the message I got:
Sep 27 03:22:06 arch plasmashell[970]: QQuickItem::stackAfter: Cannot stack
StatusNotifierItem_QMLTYPE_345(0x558c6fb48b50, parent=0x558c6caa47b0,
geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_345(0x558c6f972d20), which
must be a sibling
After that, I tried left clicking the tray icon -- it did nothing at all, and
no logs. But right clicking it made the following message show up in the
journal:
Sep 27 03:24:36 arch plasmashell[970]: Could not find DBusMenu interface,
falling back to calling ContextMenu()
I should mention that I get the exact same messages using Vanilla Wine, the
only difference is that interacting with the tray icon works perfectly fine.
--
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=45291
Bug ID: 45291
Summary: Dauntless Open Beta : Cant play Intro Video resulting
in not responding black screen
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: asembus(a)gmail.com
Distribution: ---
Tried to test the open beta version for dauntless with addtional dotnet
installation. the launcher works fine but when the game start it doesnt show
intro video and ends up with black screen.
i've read the log and it seems the error is caused when the video cannot be
shown
[2018-06-02T11:11:33,434][ 0][LogMediaUtils][Error]Cannot play
file://../../../Archon/Content/MoviesPackaged/MediaExample.mp4, because none of
the enabled media player plug-ins support it:
--
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=48132
Bug ID: 48132
Summary: Elite Dangerous launcher broken (regression since
wine-staging-4.20)
Product: Wine-staging
Version: 4.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 65724
--> https://bugs.winehq.org/attachment.cgi?id=65724
screenshots
The Elite Dangerous launcher is broken, when using wine-staging-4.20. It's
using 100 % of one CPU core, freezes after the first click and is graphically
broken (see attached screenshots).
It's a regression. Everything is fine when using either wine-4.20 or
wine-staging-4.19.
Something suspicious on the shell: 0065:fixme:d3d9:shader_validator_stub2
./wine-staging-4.20/patches/patchinstall.sh DESTDIR=wine-4.20 --all -W
uxtheme-CloseThemeClass -W uxtheme-GTK_Theming
Tested workarounds: Use d9vk or gallium-nine.
https://github.com/Joshua-Ashton/d9vk/releases (needs a Vulkan capable GPU)
https://github.com/iXit/wine-nine-standalone (needs a Radeon-GPU or a very,
very recent Intel-GPU)
winetricks galliumnine
--
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=44089
Bug ID: 44089
Summary: Strider crashes after loading screen
Product: Wine
Version: 2.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: strider(a)strycore.com
Distribution: ---
Created attachment 59805
--> https://bugs.winehq.org/attachment.cgi?id=59805
backtrace of the crash
While the main menu works fine, when starting a game, the game crashes. This is
a regression that started in Wine Staging 2.16, when the deferred context patch
(https://dev.wine-staging.com/patches/181/) was introduced. I had a build of
Wine Staging 2.15 with that patch enabled and I noticed crashes starting with
that build and onward until the latest tested, Staging 2.21.
--
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=48612
Bug ID: 48612
Summary: Left mouse button doesn't work in Mass Effect
Andromeda.
Product: Wine-staging
Version: 5.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail.aermakov(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Left mouse button doesn't work(can't fire) in game Mass Effect Andromeda in
wine+staging 5.1. But wine 5.1 without staging patches works with mouse fine.
--
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=48089
Bug ID: 48089
Summary: Origin update hangs with Esync enabled
Product: Wine-staging
Version: 4.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 65647
--> https://bugs.winehq.org/attachment.cgi?id=65647
+server
When Origin has an update available to be installed and Esync is enabled by
passing WINEESYNC=1 envar, the updater hangs and never finishes.
Disabling Esync solves the issue and allows Origin to complete the update.
Attaching +server log.
How to reproduce:
1) Create a prefix (64-bit will do)
2) Install DXVK using winetricks (app doesn't work correctly without it)
3) Add an override for OriginThinSetupInternal.exe and set it to disabled so
that the app doesn't update during installation and a backup could be made for
testing purposes.
4) Install an older version of Origin (you can use this link
https://lutris.nyc3.cdn.digitaloceanspaces.com/games/origin/OriginSetup.exe)
5) Kill all processes in the prefix and remove override for
OriginThinSetupInternal.exe
6) Run Origin.exe with WINEESYNC=1 envar passed on.
Behavior with Esync disabled: Update window appears, then closes after a while,
reopens and finishes the update.
Behavior with Esync enabled: Update window appears, then closes but never
reopens. The update hangs and never finishes.
During the test, regular wine-staging build was used, but I've also tried it
with a custom build that ports Fsync from Proton to Wine and it has the same
issue when Fsync is in use (which it indicated in the logs).
--
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=46790
Bug ID: 46790
Summary: Witcher 3 hangs shortly after launch; may show 'press
space to skip'
Product: Wine-staging
Version: 4.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: riddervancocagne(a)hotmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63809
--> https://bugs.winehq.org/attachment.cgi?id=63809
Zip file containing api trace, partial console output and Witcher 3 crash
report.
If The Witcher 3 is launched using Wine 4.3 Staging, it will grind to a halt
almost immediately.
This is no ordinary black screen, as the game often does display the text
'Press space to skip'. Pressing space has no effect, however.
I have also tried running the game on Wine 3.03 Stable, Wine 4.0 Stable and
Wine 4.3 Devel. All three variants launch and run the game.
Attached: partial console output, api trace and Witcher 3 crash report
generated by the game itself.
--
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=47365
Bug ID: 47365
Summary: jittering caused by mouse input in vkquake
Product: Wine
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tempel.julian(a)gmail.com
Distribution: ---
Created attachment 64704
--> https://bugs.winehq.org/attachment.cgi?id=64704
wine log
In vkquake, enable vsync (and set an fps limit well above refresh rate via
"host_maxfps" command if your using a refreshrate of greater than 60Hz, as the
game caps to 72fps by default), start a new game and pan the camera via the
keyboard's arrow keys. It should be absolutely smooth.
Now, pan the camera by moving the mouse instead -> there is jitter.
After alt + Tab to the desktop and back into the game, this jitter usually is
gone. Still, it shouldn't occur in the first place, as it doesn't happen on
Windows.
I made sure this isn't a driver issue by checking with both modesetting and
xf86-video-amdgpu DDX and also on xwayland. In xwayland, the issue is less
distinct, but still noticeable.
Happens with both wine 4.9, wine-staging 4.9 and my custom 4.10 build (4.10 not
yet in Arch repository).
Get vkquake here:
https://github.com/Novum/vkQuake/releases/download/1.01.0/vkquake-1.01.0_wi…
You also need the game's free demo content, copy the "id1" folder into the main
folder. Since the official servers usually are a mess, you can get it from here
as well:
https://bugs.freedesktop.org/attachment.cgi?id=143128
--
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=46633
Bug ID: 46633
Summary: unimplemented function: kernel32.dll.startthreadpoolio
Product: Wine
Version: 4.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: mushipao(a)gmail.com
Distribution: ---
Created attachment 63542
--> https://bugs.winehq.org/attachment.cgi?id=63542
backtrace of exception
3rd party, proprietary software errors out in Wine.
0157:fixme:thread:CreateThreadpoolIo (0x64, 0x42fca0, 0x5fc2a0, (nil)): stub
wine: Call from 0x7bc51e39 to unimplemented function
KERNEL32.dll.StartThreadpoolIo, aborting
wine: Call from 0x7bc51e39 to unimplemented function
KERNEL32.dll.StartThreadpoolIo, aborting
wine: Call from 0x7bc51e39 to unimplemented function
KERNEL32.dll.StartThreadpoolIo, aborting
wine: Call from 0x7bc51e39 to unimplemented function
KERNEL32.dll.StartThreadpoolIo, aborting
wine: Call from 0x7bc51e39 to unimplemented function
KERNEL32.dll.StartThreadpoolIo, aborting
wine: Unimplemented function KERNEL32.dll.StartThreadpoolIo called at address
0x7bc51e39 (thread 0157), starting debugger...
--
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=18104
Summary: Final Draft: text to speech fails
Product: Wine
Version: 1.1.19
Platform: All
URL: http://www.finaldraft.com/downloads/demo-final-draft.php
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jens(a)porup.com
Final Draft is the screenwriter's standard word processor.
It offers a text to speech feature that does not work in wine. It doesn't break
anything if you try; the buttons just don't do anything at all.
Terminal output coming soon.
--
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.