https://bugs.winehq.org/show_bug.cgi?id=45088
Bug ID: 45088
Summary: unimplemented function
msvcp140.dll.?GetCurrentThreadId@platform@details@Conc
urrency@@YAJXZ
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: bghome(a)gmail.com
Distribution: ---
Created attachment 61251
--> https://bugs.winehq.org/attachment.cgi?id=61251
Wine crash log
Application crashed on exit (application Traktor 2.11.1, see
https://appdb.winehq.org/objectManager.php?sClass=version&iId=36122).
--
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=43935
Bug ID: 43935
Summary: Wolfenstein 2: The new Colossus does not start,
requires VK_KHR_get_physical_device_properties2
Product: Wine-staging
Version: 2.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: philip.rebohle(a)tu-dortmund.de
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59575
--> https://bugs.winehq.org/attachment.cgi?id=59575
vkGetPhysicalDeviceProperties2KHR hack
The game crashes on startup, with wine complaining that
vkGetPhysicalDeviceProperties2KHR (from the
VK_KHR_get_physical_device_properties2 extension) is not implemented.
I'm using wine-staging 2.19 and the RADV driver, which supports the extension.
The attached patch provides a dummy implementation of this function that falls
back to calling vkGetPhysicalDeviceProperties, which allows the game to start.
I apologize that I have no idea how to properly implement Vulkan functions in
wine, it's just a very dirty hack.
Note that even with the patch the game doesn't even render the menu on my
system, but that might be due to driver issues.
--
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=44883
Bug ID: 44883
Summary: Commit b747d6f6ccdf1699a9242a570d681fa246de592e causes
warframe to crash. resolved via overrides
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xaudio2
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Distribution: ---
As mentioned in summary, after doing a bisect, I found commit
b747d6f6ccdf1699a9242a570d681fa246de592e makes wine prefer builtin over native
for xaudio2. This causes warframe to crash. I was able to get around it by
setting all xaudio2_* overrides to native,builtin in winecfg, but I don't think
this is ideal for other games that may have this problem.
--
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=38322
Bug ID: 38322
Summary: Call of Duty 4 Modern Warfare 3: Wine crashes when
Steam is starting the game
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: timsta2000(a)googlemail.com
Distribution: ---
Created attachment 51163
--> https://bugs.winehq.org/attachment.cgi?id=51163
backtrace.txt, the wine "error box" has given me
I've installed PlayOnLinux and downloaded the game over Steam and if I try to
start it, Wine crashes when Steam is starting MW3. I've changed the Windows
version from Windows XP to Windows 8 and now Steam is showing me a small empty
black box before starting the game and then it crashes.
I have a Dualboot-System with Ubuntu 14.10 and Windows 8.
--
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=11908
Summary: CPUZ shows no informations
Product: Wine
Version: 0.9.47.
Platform: PC-x86-64
URL: http://www.cpuid.com/cpuz.php
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: greg87(a)online.de
Created an attachment (id=11207)
--> (http://bugs.winehq.org/attachment.cgi?id=11207)
console log
Tested with cpuz 1.44.1
The only thing it displays is Unknown processor and the size of my ram.
--
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=12604
Summary: SimGolf v1.03 exits when starting a new game
Product: Wine
Version: 0.9.59.
Platform: PC
URL: http://www.simgolf.ea.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tom78999(a)gmail.com
Created an attachment (id=12218)
--> (http://bugs.winehq.org/attachment.cgi?id=12218)
wine output
When using the game menu to try and start a new game I receive two error
message dialog boxes; the first stating "Can't Set The PixelFormat" and the
second "Can't Create A GL Rendering Context". After OK'ing these two messages
the game exits. The critical message in the output seems to be the following:
err:wgl:X11DRV_wglCreateContext Cannot get FB Config for iPixelFormat 0, expect
problems!
I'm attaching the normal output from wine and the output with
WINEDEBUG="+x11drv".
--
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=40291
Bug ID: 40291
Summary: Borderlands crashes when forced DirectX 9 using -DX9
Product: Wine
Version: 1.9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Created attachment 53931
--> https://bugs.winehq.org/attachment.cgi?id=53931
backtrace from commandline, lsusb, lspci
Borderlands runs decent on my Fedora/MacBook Pro/Intel 3000 without any
arguments (~20fps). However, I read online that one could achieve significantly
faster frame-rates by forcing Borderlands to only use DirectX 9 with "-DX9"
"wine Borderlands.exe -DX9"
This, however causes the game to crash
I thought this might be interesting, valuable information, or perhaps even
fixable.
--
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=44784
Bug ID: 44784
Summary: Lingvo x6 portable does not start
Product: Wine
Version: 3.4
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maksim.andronenkov(a)rovaniemi.uz
Created attachment 60812
--> https://bugs.winehq.org/attachment.cgi?id=60812
logs
Recently installed wine 3.4 on MacOS High Sierra and tried to run Lingvo X6
portable www.lingvo.ru but did not happen. Logs are attached.
--
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=41564
Bug ID: 41564
Summary: Google Nik Collection: Top menu bar gone and cursor
gone
Product: Wine-staging
Version: 1.9.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dan.Tableau(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Hello, I just want to report that using wine 1.9.21 (staging) with the Google
Nik Collection creates the following issues:
Top menu bar gone, cursor gone (while inside the window).
After switching to winehq-devel, as suggest in the IRC (Thanks, slackner), the
problem was gone. Both times the version used was: 1.9.21
Let me know if more info is needed. Thank for doing all this and keeping it up
and running!
--
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.