https://bugs.winehq.org/show_bug.cgi?id=45067
Bug ID: 45067
Summary: Claybook fails to create shader due to invalid cast
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Created attachment 61205
--> https://bugs.winehq.org/attachment.cgi?id=61205
Log file.
Sharers aren't being created correctly due to a failing convert
013d:fixme:d3d_shader:shader_glsl_sprintf_cast Unhandled cast from 0 to 0x6.
which leads to
....
013d:fixme:d3d_shader:shader_glsl_dump_program_source imageStore(cs_image0,
floatBitsToInt(R0).xy, <unhandled data type 0x6>.xyzw);
--
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=40694
Bug ID: 40694
Summary: Invalid behavior of "C: && echo haha" or "C: & echo
haha"
Product: Wine
Version: 1.9.10
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: fracting(a)gmail.com
Distribution: ---
On Windows, all of "C: && echo haha", "C: || echo haha", "C: & echo haha" works
fine.
On Wine, this kinds of command line generates an error of "Can't recognize 'C:
' as an internal or external command, or batch script."
Found by neovim developer: https://tea-ci.org/equalsraf/neovim/39
--
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=45387
Bug ID: 45387
Summary: arm64_map_dwarf_register: Don't know how to map
register (64-66)
Product: Wine
Version: 3.11
Hardware: aarch64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: nerv(a)dawncrow.de
Distribution: ---
Noticed while running valgrind on arm64
0088:fixme:dbghelp:arm64_map_dwarf_register Don't know how to map register 64
0088:fixme:dbghelp:arm64_map_dwarf_register Don't know how to map register 65
0088:fixme:dbghelp:arm64_map_dwarf_register Don't know how to map register 66
https://github.com/Microsoft/microsoft-pdb/blob/master/include/cvconst.h
CV_ARM64_X14 = 64,
CV_ARM64_X15 = 65,
CV_ARM64_IP0 = 66,
--
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=45081
Bug ID: 45081
Summary: Expanded FakeDLL support changed behaviour of stubs
for A/W symbols
Product: Wine-staging
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Paul.Hampson(a)Pobox.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 61234
--> https://bugs.winehq.org/attachment.cgi?id=61234
Report the results of GetProcAddress for three variations of the intersting
symbol
While looking into issues with running current Cygwin on current Wine, an error
was raised under Wine Staging 3.6:
fatal error - couldn't dynamically determine load address for
'DsEnumerateDomainTrustsW' (handle 0x7F1E632A0000), Win32 error 127
This doesn't happen either natively or with Wine 2.4 (Staging)
Looking into it, it appears the current netapi32.spec has:
@ stub DsEnumerateDomainTrusts
Given the near-trivial code attached, the behaviour difference is clear.
Windows (Windows 10 1709):
DsEnumerateDomainTrusts not found
DsEnumerateDomainTrustsA found
DsEnumerateDomainTrustsW found
Wine 2.4 (Staging) and 3.6 (Staging):
DsEnumerateDomainTrusts found
DsEnumerateDomainTrustsA not found
DsEnumerateDomainTrustsW not found
The weird thing is that Wine 2.4 worked in Cygwin, when clearly nothing has
apparently changed for this particular DLL export code-wise since 2005.
I believe this is to do with the patches in Wine Staging
(https://github.com/wine-staging/wine-staging/tree/master/patches/winebuild-…)
which have surfaced a class of previously-hidden issues in Wine.
I haven't worked out where yet, but I suspect that the Fake_DLLs are breaking
some kind of Wine magic which lets the unadorned symbols for stubs also respond
to a lookup for the adorned symbols.
Otherwise, I expect we'd see a lot more pairs like this:
@ stub DsEnumerateDomainTrustsA
@ stub DsEnumerateDomainTrustsW
I'm surprised such a change hasn't seen more issues but I was unable to find
any references to it on this Bugzilla or by searching Google.
ReactOS have a trivial patch which turns them from spec-stubs to code-stubs,
and hence corrects the exports etc: https://jira.reactos.org/browse/CORE-11056
and that would make sense for Wine.
All Wine installations here are on Ubuntu 14.04 from winehq packages, in Docker
images built from https://github.com/TBBle/wine_msys64
--
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=18164
Summary: dlls/iphlpapi/ifenum.c: compiler warnings
Product: Wine
Version: 1.1.19
Platform: PC
OS/Version: NetBSD
Status: NEW
Keywords: source
Severity: minor
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT
-fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement
-Wwrite-strings -Wpointer-arith -I/usr/pkg/include -I/usr/include
-I/usr/X11R7/include/freetype2 -I/usr/X11R7/include -O2 -I/usr/pkg/include
-I/usr/include -I/usr/X11R7/include/freetype2 -I/usr/X11R7/include -o
./ifenum.o ./ifenum.c
./ifenum.c: In function 'enumIPAddresses':
./ifenum.c:693: warning: pointer of type 'void *' used in arithmetic
./ifenum.c:693: warning: comparison of distinct pointer types lacks a cast
./ifenum.c: In function 'getIPAddrTable':
./ifenum.c:754: warning: pointer of type 'void *' used in arithmetic
./ifenum.c:754: warning: comparison of distinct pointer types lacks a cast
No patch for this one yet. Won't complain if someone beats me to it ;-).
--
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=42599
Bug ID: 42599
Summary: Max Payne 3 (Steam) crashes in DX9 mode
Product: Wine
Version: 2.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 57541
--> https://bugs.winehq.org/attachment.cgi?id=57541
log
Game just crashes at launch if render set to DX9.
--
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=27497
Summary: Regedit mangles registry keys containing embedded
NULLs
Product: Wine
Version: 1.3.22
Platform: x86
URL: http://www.gog.com/en/gamecard/sacrifice
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=35155)
--> (http://bugs.winehq.org/attachment.cgi?id=35155)
raw file
Noticed this while messing around with Sacrifice
(http://www.gog.com/en/gamecard/sacrifice).
The game stores a few keys with embedded NULLs, apparently all the ones that
store string values (dword/hex values aren't affected).
Looking at the raw registry (system.reg) shows the values fine:
"Graphic detail"=dword:00000000
"IP address"="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
"Key repeat delay"=dword:0000000a
"Key repeat start"=dword:00000032
but if I export the key with wine's regedit, it mangles them:
"Graphic detail"=dword:00000000
"IP address"=""Key repeat delay"=dword:0000000a
"Key repeat start"=dword:00000032
notice how a quote goes missing along with the newline. The game really likes
those newlines. If I remove them and rerun the game, then adjust its settings,
it adds them back.
I'll attach a text file with the raw registry, along with what I get when
exporting.
--
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=44895
Bug ID: 44895
Summary: League Of Legends: Unable to log in if behind OpenWRT
based router
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail+wine(a)m-reimer.de
Distribution: ---
I don't know how much this really depends on OpenWRT, but that's the way how I
can 100% reproduce this bug.
I run LoL with latest wine-staging. I installed using this script:
https://github.com/GloriousEggroll/leagueoflegends-linux
So far I always used AVM routers. Fritz!Box 5050 first and as my ISP now uses
Annex-J, I had to switch to a Fritz!Box 7270.
With these routers, I never had any problem with logging in from the League
client.
Now I wanted to try using a 100% open source router based on OpenWRT. As soon
as I do so, connection to the LoL login servers fails.
My brother was able to reproduce this problem on his PC and he also has Windows
installed. If he boots into Windows, login works. On Linux with Wine, login
doesn't work.
So this is a Wine problem "somehow" as it works on Windows, but it may also
have something to do with the router or network infrastructure as it works on
Wine if a proprietary router is used.
I can provide more info if required.
--
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=40742
Bug ID: 40742
Summary: cmd.exe: buffer overflow while parsing qualifiers
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: jbb.rose(a)yahoo.com
Distribution: ---
Created attachment 54646
--> https://bugs.winehq.org/attachment.cgi?id=54646
Batch file which triggers the problem
WCMD_parse() copies command qualifiers into the quals[] array. The
array is MAX_PATH (260) characters long, but the input command can be
up to MAXSTRING (8192) characters long. This can lead to buffer
overflows and crashes if a command has many qualifiers.
The attached try.bat file, taken from an actual command generated by
a cross-build system, reliably crashes wine 1.9.11 as built on SLES11SP2.
Increasing the size of quals[] to MAXSTRING characters fixes the 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=42304
Bug ID: 42304
Summary: Caladrius Blaze shows black screen on title menu
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 57028
--> https://bugs.winehq.org/attachment.cgi?id=57028
Wine 2.0 terminal output
When attempting to play the game Caladrius Blaze, I am greeted with a
completely black screen.
I've attempted to play the game while using Windows XP & 7 modes.
Any advice on what logs I would need to provide will be greatly appreciated as
I can't see anything related to DirectX in the game's terminal output at all...
--
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.