https://bugs.winehq.org/show_bug.cgi?id=53550
Bug ID: 53550
Summary: Some Catalan locales not properly handled
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: marc.ruiz+wine(a)live.com
Distribution: ---
My system has locale ca_AD.UTF-8 which is for Catalan. However Wine apparently
does not recognize it as Catalan, it only recognizes ca_ES.
How to reproduce:
LANG=ca_AD.UTF-8 winecfg -> UI is shown in English (wrong).
LANG=ca_ES.UTF-8 winecfg -> UI is shown in Catalan (right).
LANG=ca_FR.UTF-8 winecfg -> UI is shown in English (wrong).
LANG=ca_IT.UTF-8 winecfg -> UI is shown in English (wrong).
I have actually discovered this while running YY-CHR
(https://appdb.winehq.org/objectManager.php?sClass=version&iId=22701). Running
this program with WINEDEBUG=nls I have discovered that ca_ES is mapped to
locale CAT and ca_AD and the others to ZZZ.
--
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=53525
Bug ID: 53525
Summary: dinpu:hid - test_hid_multiple_tlc() sometimes fails
with testsigning turned on
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on:
hid.c:3926: Test failed: Failed to find HID device matching
L"\\\\?\\hid#vid_1209&pid_0001&col02"
hid.c:3930: Test failed: got error 2
hid.c:3040: Test failed: HidD_GetPreparsedData failed with error 6
hid.c:3043: Test failed: got "\\\x00\\\x00?\x00\\\x00" expected "HidP KDR"
https://test.winehq.org/data/patterns.html#dinput:hid
These failures happened on both fgtb-w10pro64-tsign and w1064-tsign and only
those. So they seem to be specific to Windows 10 with test signing turned on.
--
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=52997
Bug ID: 52997
Summary: Integration of D3D12 support with a PE build of vkd3d
causes a crash in Steam Overlay.
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: cmccarthy(a)codeweavers.com
Distribution: ---
Launching a D3D12 game with Steam Overlay enabled results in a null pointer
dereference right after a call to D3D11On12CreateDevice(). Changing the
returned values alters the crash location.
This is a regression caused by integration of a vkd3d PE build in commit
5d62e5603. The call to D3D11On12CreateDevice() doesn't occur when using an ELF
vkd3d build.
--
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=52873
Bug ID: 52873
Summary: oleaut32:typelib fails in Wine in Hindi
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
oleaut32:typelib fails in Wine in Hindi:
typelib.c:2514: Test failed: got: L"default?"
typelib.c:2526: Test failed: got: L"default?"
typelib.c:3314: Test failed: got: L"default?"
typelib.c:3326: Test failed: got: L"default?"
https://test.winehq.org/data/patterns.html#oleaut32:typelib
A bisect shows that the test started failing with the commit below:
commit e81327358a26b160740b3421a4c7f300b4d2f06f
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Apr 13 15:13:16 2022 +0200
kernelbase: Move codepage initialization to ntdll.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Oddly this is the same commit as for a recent set of vbscript:run failures (see
bug 52872).
--
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=52779
Bug ID: 52779
Summary: Construction Set Extender crash with an Assertion
Error in wine 7.5
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
Distribution: ---
Using wine 7.5 Consturction Set Extender (plugin for Oblivion Construction Set)
crash with the following assertion
Assertion failed: Data != ActiveComboBoxes.cend(), file
Y:\CSE\Construction-Set-Extender\UIManager.cpp, line 623
Everything works fine with wine 7.4
There is no log except the common imm fixme and a lot of
d3d:wined3d_check_device_format_conversion and d3d:state_linepattern_w that are
present even in 7.4
Bisection in progress
--
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=42797
Bug ID: 42797
Summary: ICU64 for VICE: No highlighted read/write-colors in
Memory-window.
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: enkorv(a)yahoo.com
Distribution: ---
Created attachment 57824
--> https://bugs.winehq.org/attachment.cgi?id=57824
terminal output when running ICU64.exe
VICE is a Commodore 64 (and siblings) emulator. "ICU64 for VICE" is a hacking
tool that piggybacks onto the emulator and shows memory maps in useful ways.
When starting ICU64.exe it opens a small toolbar and starts the VICE emulator
as well. When selecting Memory in the toolbar a window opens which shows the
memory map of the Commodore 64. It should also highlight the memory read and
writes as well as where the CPU is currently running, using color highlighting.
This part doesn't work so the window just has a black background. You can still
zoom in and out in the memory map (using mouse scroll-wheel) and see the values
of the memory locations changing live.
An example of how the color highlighting typically looks is here (could not
find a clip of ICU64 for VICE, so this clip shows ICU64 for Frodo, which is
another Commodore 64 emulator): https://www.youtube.com/watch?v=tjcvR5McmSg
Testing and wine-environment:
Ubuntu 16.10 - 4.8.0-46-generic
wine-2.4
ICU64 needs Microsoft .NET Framework 2.0 (see
http://icu64.blogspot.se/p/download.html )
WINEPREFIX=~/.winetest2017 WINEARCH=win32 wineboot
WINEPREFIX=~/.winetest2017 winetricks dotnet2
ICU64 - https://sites.google.com/site/mathfigure/icu64vice23-v0.1.2.zip
c89d54ea7d64834694c3590660dee69e0738a418
WinVICE 2.3 -
https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/W…
b2a7ffafbcef1ab159681002616d9cf819c1ef84
Download both, unzip into same folder and run ICU64.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.
http://bugs.winehq.org/show_bug.cgi?id=31927
Bug #: 31927
Summary: ws2_32: sock.c fails intermittently - 'Test succeeded
inside todo block: GetQueuedCompletionStatus returned
0'
Product: Wine
Version: 1.5.14
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, testcase
Severity: minor
Priority: P2
Component: winsock
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Running in a loop for about 15 minutes, I got:
sock.c:5385: Test succeeded inside todo block: GetQueuedCompletionStatus
returned 0
sock.c:5386: Test succeeded inside todo block: Last error was 64
make: *** [sock.ok] Error 2
--
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=54094
Bug ID: 54094
Summary: kernel32:process - test_services_exe() sometimes fails
due to an invalid buffer size in Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
test_services_exe() sometimes fails due to an invalid buffer size in Windows:
process.c:4962: Test failed: got 0xc0000004
See https://test.winehq.org/data/patterns.html#kernel32:process
Where 0xc0000004 == STATUS_INFO_LENGTH_MISMATCH
This causes a little bit over one failure per month.
I think the failure simply happens when a process is started between the first
call to NtQuerySystemInformation(), which returns the buffer size to hold the
*array* of SYSTEM_PROCESS_INFORMATION structures, and the time we call it again
with that size. Obviously we don't start new processes ourselves so it must be
a scheduled task or some equivalent.
We should probably loop a couple of times to defend against that.
--
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=53941
Bug ID: 53941
Summary: Chicken Tournament crashes on start
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dmusic
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 73511
--> https://bugs.winehq.org/attachment.cgi?id=73511
Log file
Other issue with directmusic not being implemented completely.
--
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=53625
Bug ID: 53625
Summary: In function ‘get_gnutls_cipher’ ... error:
‘GNUTLS_CIPHER_AES_128_CFB8’ undeclared
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: version2013(a)protonmail.com
Distribution: ---
Created attachment 73024
--> https://bugs.winehq.org/attachment.cgi?id=73024
log.txt
Compiling in distro with:
compiler version 4.8.4
# gcc --version
glibc 2.19
# ldd --version
config line:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x
--libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686"
Compile error in wine-7.15
In function ‘get_gnutls_cipher’:
error: ‘GNUTLS_CIPHER_AES_128_CFB8’ undeclared
error: ‘GNUTLS_CIPHER_AES_192_CFB8’ undeclared
error: ‘GNUTLS_CIPHER_AES_256_CFB8’ undeclared
--
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=53384
Bug ID: 53384
Summary: Hogia Hemekonomi Unexpected error on first start
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)jonass.user.lysator.liu.se
Distribution: ---
Created attachment 72771
--> https://bugs.winehq.org/attachment.cgi?id=72771
Terminal with start of wine, error dialog and application in background.
On first start Hogia Hemekonomi tries to determine if this is the first run of
the program. If it is, it tries to start another executable called
hekintro.exe. hekintro.exe opens a new windows and shows an introduction.
This bug gives and Unexpected error dialog instead of the intro window.
I have tried bisecting but can not find a conclusive commit. Only that it may
be around commit 9b9d818252fe1a47f3ca52d028dc10d52fa33597 Mar 4 14:29:21 2022.
Wine 7.1 seems to be fine, 7.4 seems to be bad.
Testing on XUbuntu 18.04.6 LTS i686.
--
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=50013
Bug ID: 50013
Summary: MyPhoneExplorer 1.8.15 crashes
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 68435
--> https://bugs.winehq.org/attachment.cgi?id=68435
Backtrace (5.18 Staging)
Hello everyone,
Download-URL is at: https://fjsoft.at/de/
There is also an AppDB entry:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=34110
Installation works fine in a clean prefix with 5.18 (Staging) and the app
requires vb6run installed to start it up.
However it throws a fatal error. Backtrace is 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=49394
Bug ID: 49394
Summary: CED1401 USB function driver fails to install
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 67461
--> https://bugs.winehq.org/attachment.cgi?id=67461
WINEDEBUG=+wineusb,+setupapi,+ntoskrnl,+plugplay,+pid,+msgbox ./wine
winsupp.exe
I'm try to test the fix for bug 35903. In order to do so, I compiled wine from
source (commit 634cb775c27b61ad6ce1fbe3e9972b0edfa31dcb), and used wine from
the build directory.
Now the installation of winsupp.exe is failing (this has been working before)
with this error:
0020:0024:err:module:__wine_process_init
L"Z:\\home\\schloegl\\src\\wineapps\\winsupp.8081a20bbc0c9b99f37b98a823ce07ab25f15e9d.exe"
not supported on this system
The log file is 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=53918
Bug ID: 53918
Summary: Building with external PE libraries fails when static
libraries are also installed
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Regression SHA1: 6a912649188a765d0c58e8b26e093fb0c31b3e3d
Distribution: ---
The basic problem is that winegcc, when passed e.g.
"-L/usr/x86_64-w64-mingw32/lib -lvkd3d", looks up that library in the search
path, finds libvkd3d.a, and tries to link to it.
The mingw-w64 linking process, at least for vkd3d (but presumably others as
well), provides both "libvkd3d.a" and "libvkd3d.dll.a". The former is a static
library, and the latter is essentially an import library for libvkd3d-1.dll.
Normal mingw-w64 gcc, when passed -lvkd3d, links to the latter, according to
the search path specified in [1] s.v. "direct linking to a dll". winegcc does
not know about .dll.a and hence finds the static library first.
This worked before 6a912649 because winegcc would try to find a library ending
in ".cross.a", fail to find *any* vkd3d libraries, and just leave the linker
argument as "-lvkd3d".
Given this, an obvious solution is to teach winegcc about the ld linker path.
However, I find myself asking—why are we trying to rewrite the command line at
all? Why can't we just let mingw-w64 gcc work by itself? winegcc is, naturally,
devoid of any comments, and as far as I can tell the code doesn't actually *do*
anything that depends on the library type or path, so I started looking in the
git history, but unfortunately was only partly able to answer the question.
Here is what I found:
* c7a210bc2f27 forces the use of library paths if -mno-cygwin is set (in
addition to some other conditions). The commit message specifies that we *can*
do this (due to our use of -nodefaultlibs), but doesn't specify why we *need*
to do this. Jacek, can you by chance explain?
* 33147c947500 forces the use of library paths (sort of) if lib_suffix is set,
which makes sense—gcc won't be able to find any libraries if we are overriding
lib_suffix.
* 870d490eecdb forces the use of library paths for all winelib DLLs, so that
"-lfoo" links to "foo/foo.dll". This makes sense, but is also now obsolete—our
makefiles pass the direct paths. Or do we want to support winelib users outside
of wine including from the build tree?
* 006ec80dd5c1 introduces the logic in the first place, forcing the use of
library paths for static libraries. This was written by Dimitrie O. Paun, with
the comment "For static libs (.a) we need to pass the actual filename to
winebuild, not a -l switch." No further explanation is given.
Alexandre, can you please shed light on this?
[1] https://sourceware.org/binutils/docs-2.39/ld/WIN32.html
--
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=53623
Bug ID: 53623
Summary: Resident Evil 7 has broken rendering in DX11 mode
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: b2087112144ca945d1df9ab9d82ef8a9f6e6d00b
Distribution: ---
Created attachment 73021
--> https://bugs.winehq.org/attachment.cgi?id=73021
example
Using 'dx11_non-rt' branch.
--
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=53406
Bug ID: 53406
Summary: Had been running 7.10 Fedora version no problem, but
today updated to 7.12 broke??
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikes(a)kuentos.guam.net
Distribution: ---
Did the dnf update and it was mostly the 7.12 version of wine from Fedora.
Upgrade went thru fine, or so I thought.
But primary program I use the wine to run is Pegasus Mail.
After running it, it came up fine, and had it download new mail.
Was 14 new messages, went to view them, but just got a spinning little circle
icon. No error message shows, top and ps -ef don't seem to show anything. Had
to kill program to close it. Tried different message, but all did the same
thing.
Restarted machine, same result.
Only option I could think of was dnf downgrade wine*
That ran fine, but installed wine-core-6.16-1.fc35, thought it would have gone
to 7.10 that had been working fine before todays upgrade to 7.12?
Since no error shows other than ivy bridge is incomplete, so can't report more
than just getting a spinning icon and no response.
Have never done a downgrade before, so not sure why it went to 6.16. Just to
see what would happen type dnf upgrade wine* and it showed that it would intall
that 7.12 version, so I responsed N.
Don't know if there is some option I could run to hopefully get more details on
what is going on. But after the downgrade the messages view fine. Have it set
to using windows 10 option, so not sure if using 8.1 or some other option might
make a different.
--
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=53300
Bug ID: 53300
Summary: Controller response delayed
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 0a930890192726e64bc6207c0d04f44e4c849b7d
Distribution: ---
Lots of '00b0:err:rawinput:add_device Failed to get collection descriptor,
status 0xc00000e8.' during gameplay.
--
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=52708
Bug ID: 52708
Summary: libs/xslt/libxslt/attributes.c:136:9: error: variadic
functions must use the base AAPCS variant
Product: Wine
Version: 6.20
Hardware: arm
OS: Linux
Status: NEW
Keywords: download, regression, source
Severity: major
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Regression SHA1: 9d9d4fcc379b2541a43b14f197facb6fa8c93ee8
Distribution: Debian
gcc -c -o libs/xslt/libxslt/attributes.o libs/xslt/libxslt/attributes.c
-Ilibs/xslt -Iinclude -Iinclude/msvcrt \
-I./libs/xml2/include -I./libs/xslt -DLIBXML_STATIC -DLIBXSLT_STATIC -D_UCRT
-pipe \
-fcf-protection=none -fno-stack-protector -fno-strict-aliasing
-Wno-packed-not-aligned -gdwarf-4 \
-fPIC -fasynchronous-unwind-tables -D_WIN32 -fno-builtin -fshort-wchar
-Wno-format -g -O2 -mthumb -mfloat-abi=hard
libs/xslt/libxslt/attributes.c: In function 'xsltNewAttrElem':
libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the
base AAPCS variant
136 | xsltGenericError(xsltGenericErrorContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
137 | "xsltNewAttrElem : malloc failed\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c: In function 'xsltNewUseAttrSet':
libs/xslt/libxslt/attributes.c:217:9: error: variadic functions must use the
base AAPCS variant
217 | xsltGenericError(xsltGenericErrorContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
218 | "xsltNewUseAttrSet : malloc failed\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c: In function 'xsltResolveAttrSet.part.0':
libs/xslt/libxslt/attributes.c:651:17: error: variadic functions must use the
base AAPCS variant
651 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
652 | "xsl:attribute-set : merging import for %s\n",
name);
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c: In function 'xsltResolveSASCallback':
libs/xslt/libxslt/attributes.c:694:6: error: variadic functions must use the
base AAPCS variant
694 | xsltGenericError(xsltGenericErrorContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
695 | "xsl:attribute-set : internal error, can't move
imported "
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
696 | " attribute set %s\n", name);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c: In function 'xsltParseStylesheetAttributeSet':
libs/xslt/libxslt/attributes.c:432:2: error: variadic functions must use the
base AAPCS variant
432 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
433 | "creating attribute set table\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:301:9: error: variadic functions must use the
base AAPCS variant
301 | xsltGenericError(xsltGenericErrorContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
302 | "xsltNewAttrSet : malloc failed\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:473:6: error: variadic functions must use the
base AAPCS variant
473 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
474 | "add attribute to list %s\n", ncname);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:518:3: error: variadic functions must use the
base AAPCS variant
518 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
519 | "xsl:attribute-set : %s adds use %s\n", ncname, curval);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:555:5: error: variadic functions must use the
base AAPCS variant
555 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
556 | "updated attribute list %s\n", ncname);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the
base AAPCS variant
399 | xsltGenericError(xsltGenericErrorContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
400 | "xsl:attribute-set : name is missing\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the
base AAPCS variant
libs/xslt/libxslt/attributes.c: In function
'xsltResolveStylesheetAttributeSet':
libs/xslt/libxslt/attributes.c:713:5: error: variadic functions must use the
base AAPCS variant
713 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
714 | "Resolving attribute sets references\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c:722:3: error: variadic functions must use the
base AAPCS variant
722 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
723 | "creating attribute set table\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libs/xslt/libxslt/attributes.c: In function 'xsltApplyAttributeSet':
libs/xslt/libxslt/attributes.c:1172:13: error: variadic functions must use the
base AAPCS variant
1172 | xsltGenericDebug(xsltGenericDebugContext,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1173 | "apply attribute set %s\n", curstr);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make: *** [Makefile:159245: libs/xslt/libxslt/attributes.o] Error 1
Specific to armv7l, without mingw:
Linux blah 5.9.12 #1 SMP PREEMPT Tue Mar 30 23:29:49 CDT 2021 armv7l GNU/Linux
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
with llvm-mingw-20211002 (self-compiled, there's no linux/armv7l binary build
afaik), however, wine builds.
--
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=49517
Bug ID: 49517
Summary: Warframe crashes during loading before menu with
wined3d, gives popup
Product: Wine
Version: 5.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Distribution: ---
Created attachment 67648
--> https://bugs.winehq.org/attachment.cgi?id=67648
d3d popup error
The game crashes during the initial loading screen and gives the attached popup
message. Happens on both amd and nvidia.
The launcher is also affected by
https://bugs.winehq.org/show_bug.cgi?id=44985
in wined3d and can be worked around with WINEDLLOVERRIDES="libglesv2=d" to get
the game to the launching/crashing point.
--
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=54101
Bug ID: 54101
Summary: unimplemented function MSVCP70.dll called in 32-bit
code (0x7bc2c2e0)
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: simon(a)dryder.de
Distribution: ---
Created attachment 73636
--> https://bugs.winehq.org/attachment.cgi?id=73636
unimplemented function MSVCP70.dll when running SC CT Versus in wine 7.22
When trying to run Splinter Cell Chaos Theory Versus mode with wine 7.22 game
crashes with attached error message.
--
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=54085
Bug ID: 54085
Summary: windows.devices.enumeration:devices -
test_DeviceAccessInformation() sometimes crashes on
Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
windows.devices.enumeration:devices - test_DeviceAccessInformation() sometimes
crashes on Windows 10:
devices.c:272: Test succeeded
devices.c:114: this is the last test seen before the exception
1474:devices: unhandled exception c0000005 at 00007FFC40CC44E7
See
https://test.winehq.org/data/patterns.html#windows.devices.enumeration:devi…
The crash always happens in this call:
hr = IDeviceAccessInformationStatics_CreateFromDeviceClass( statics,
DeviceClass_AudioCapture, &access_info );
And the crashes started as soon as this test was added in the commit below:
commit d0a60ca810ecb7ef71e67cb1a21ca6dc35c18bef
Author: Paul Gofman <pgofman(a)codeweavers.com>
Date: Tue Oct 4 13:13:05 2022 -0500
windows.devices.enumeration: Create stub DeviceAccessInformation class.
The crashes were also reported by the TestBot in MR!1027 but it got merged
anyway.
--
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=54060
Bug ID: 54060
Summary: Error: junk at end of line, first unrecognized
character is `"'
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ucrtbase
Assignee: wine-bugs(a)winehq.org
Reporter: version2013(a)protonmail.com
Distribution: ---
Created attachment 73614
--> https://bugs.winehq.org/attachment.cgi?id=73614
log.txt
Compiling in distro with:
compiler version 4.8.4
# gcc --version
glibc 2.19
# ldd --version
config line:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x
--libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686"
Compile error in wine-7.21
libucrtbase-63899ddc.s: Assembler messages:
libucrtbase-63899ddc.s:2: Error: junk at end of line, first unrecognized
character is `"'
libucrtbase-63899ddc.s:11: Error: junk at end of line, first unrecognized
character is `"'
libucrtbase-63899ddc.s:14: Error: junk at end of line, first unrecognized
character is `"'
winebuild: /usr/bin/i686-w64-mingw32-as failed with status 1
make: *** [dlls/ucrtbase/i386-windows/libucrtbase.a] Error 1
--
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=53894
Bug ID: 53894
Summary: user32:sysparams - test_WM_DISPLAYCHANGE() times out
on Windows 7+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+:
sysparams.c:2474: Test failed: WaitForSingleObject returned 0x102
sysparams.c:2475: Test failed: got WM_DISPLAYCHANGE bpp 4294967295
See: https://test.winehq.org/data/patterns.html#user32:sysparams
The failures started on 2022-09-23 which saw two commits to this test. However
the test does not fail when run standalone so the commits may not be directly
responsible.
--
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=53485
Bug ID: 53485
Summary: Cursor is missing in Visio 2003 when editing text
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)copysoft.org
Distribution: ---
In Visio 2003 running under Wine 7.14 the text cursor is not displayed when
editing text.
How to reproduce:
Open visio, create a new document, select the text tool, type on the screen,
the cursor does not appear.
Text input is fine, text is rendered fine and can be selected, copied and
pasted, all that is missing is the cursor.
I've run a bisect and found that this commit appears to be responsible for the
regression:
commit b8732c80b112af388264ac84d726aad09d93c8c6
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Tue Apr 26 16:06:04 2022 +0100
win32u: Move caret APIs from user32.
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=53028
Bug ID: 53028
Summary: gamepad buttons stopped working correctly
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: piotr5(a)netscape.net
Distribution: ---
ever since upgrading to wine-7.0 my gamepad got reduced to having only 10
functioning buttons and just 5 axes are actually doing anything. I now
downgraded to wine-6.0.2 and it has all 14 buttons and 6 axes again. (actually
now there are 2 devices of the same name detected, both have 8 axes, the second
device is spreading the last 2 axes into being horizontal, while the first
correctly assigns a 2d-movement analogue to one axis and nothing to the other.
so I disabled the 2nd one.)
to be precise, "wine control.exe" has a program for testing my gamepad, and
there wine-7.0 is showing me only 10 buttons and 8 axes, of which only 5 are
moving. in some game I had assigned one of the missing keys to an action and
moving the axis which isn't perceived by wine sometimes triggers that missing
button -- cannot see anything like that in this test program.
I'm on gentoo linux, wine-vanilla is the only package providing wine there, and
stable versions are just 6.0.2 and 7.0. installing newer versions doesn't work
for me since it needs vulkan (winegcc aborts with function vkd3d_* not defined
errors in wined3d.spec) which I have not installed. is it worth upgrading, or
has that joystick bug not been fixed yet?
--
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.