http://bugs.winehq.org/show_bug.cgi?id=58269
Bug ID: 58269
Summary: Build regression in wine 10.7 using clang on aarch64
(error in backend: Invalid register name "x18")
Product: Wine
Version: 10.7
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: lav(a)etersoft.ru
Distribution: ---
When compiling wine for aarch64, a build regression appeared in Wine 10.7 when
using clang (any version).
Error is that register x18 is used, and clang reports it as an hard error.
[00:04:11] fatal error: error in backend: Invalid register name "x18".
[00:04:11] PLEASE submit a bug report to
https://github.com/llvm/llvm-project/issues/ and include the crash backtrace,
preprocessed source, and associated run script.
[00:04:11] Stack dump:
[00:04:11] 0. Program arguments: clang-19 -c -o dlls/msvcr100/crt_main.o
dlls/msvcrt/crt_main.c -Idlls/msvcr100 -Idlls/msvcrt -Iinclude -Iinclude/msvcrt
-D_MSVCR_VER=100 -D__WINESRC__ -D_CRTIMP= -Wall -pipe -fcf-protection=none
-fvisibility=hidden -fno-stack-protector -fno-strict-aliasing
-Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self
-Wpointer-arith -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter
-Wvla -Wwrite-strings -gdwarf-4 -fPIC -fasynchronous-unwind-tables -D_WIN32
-fno-builtin -fshort-wchar -Wno-format -pipe -Wall -g -O2
[00:04:11] 1. <eof> parser at end of file
[00:04:11] 2. Code generation
[00:04:11] 3. Running pass 'Function Pass Manager' on module
'dlls/msvcrt/crt_main.c'.
[00:04:11] 4. Running pass 'AArch64 Instruction Selection' on function
'@mainCRTStartup'
[00:04:11] #0 0x0000ffff9b5805e8
llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
(/usr/lib/llvm-19.1/bin/../lib64/libLLVM.so.19.1+0x39705e8)
Simular bug discussed here https://bugs.winehq.org/show_bug.cgi?id=55051
--
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=12123
Summary: Wall Street Advisor 1.27 redraw problems
Product: Wine
Version: CVS/GIT
Platform: Other
URL: http://www.lathuy.com/
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Now that bug 7430 is fixed, on to runtime problems.
To install this app, first to
sh winetricks vcrun6 wsh56
Start the app. You'll see a tree control on the left
whose root node flashes constantly. Also, the main
pane doesn't redraw properly when you drag some
unrelated window in front of it.
(Also, the app outputs
err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not
registered
on startup. I think that's associated with ado15, but
doing winetricks art2kmin doesn't seem to help that...? ADO has
always been a mystery to me. But that's a different bug.)
--
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=57178
Bug ID: 57178
Summary: toolbar control doesn't forward WM_NOTIFY to it's
original parent
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: alanas.00(a)mail.ru
Distribution: Debian
Created attachment 77077
--> https://bugs.winehq.org/attachment.cgi?id=77077
foo2.c — test program, compile `x86_64-w64-mingw32-gcc-13 -std=c11 -Wall
-Wextra -Wpedantic -Wno-unused-parameter -O3 -o foo2.exe foo2.c -lcomctl32`
in windows xp professional x64 edition service pack 2 and windows 7 ultimate
service pack 1 and maybe other windowses that I didn't test but not wine
NMDDR nmhdr={
.hwndFrom=NULL,
.idFrom=0xfedcba9876543210,
.code=0xabc
};
SendMessageA(
toolbar,
WM_NOTIFY,
0x4444444444444444,
(LPARAM)nmhdr
);
does something similar to
NMDDR nmhdr={
.hwndFrom=NULL,
.idFrom=0xfedcba9876543210,
.code=0xabc
};
SendMessageA(
toolbar_original_parent,
WM_NOTIFY,
0xfedcba9876543210,
(LPARAM)nmhdr
);
except if nmhdr.code is one of 0xfffffc4a, 0xfffffc4b, 0xfffffc4c, 0xfffffc4d,
0xfffffc4e, 0xfffffc4f, 0xfffffc50, 0xfffffc51, 0xfffffc52, 0xfffffc53,
0xfffffc54, 0xfffffc55, 0xfffffc56, 0xfffffc57, 0xfffffc58, 0xfffffc59,
0xfffffc5a, 0xfffffc5b, 0xfffffc5c, 0xfffffc5d, 0xfffffc5e, 0xfffffc5f,
0xfffffc60, 0xfffffc61, 0xfffffc62, 0xfffffc63, 0xfffffc64, 0xfffffc65,
0xfffffc66, 0xfffffc67, 0xfffffc68, 0xfffffc69, 0xfffffc6a, 0xfffffc6b,
0xfffffc6c, 0xfffffc6d, 0xfffffc6e, 0xfffffc6f, 0xfffffc70, 0xfffffc71,
0xfffffc72, 0xfffffc73, 0xfffffc74, 0xfffffc75, 0xfffffc76, 0xfffffc77,
0xfffffc78, 0xfffffc79, 0xfffffc7a, 0xfffffc7b, 0xfffffc7c, 0xfffffcd7,
0xfffffcda, 0xfffffdee
nmhdr.hwndFrom is not accessed and can be inside PAGE_NOACCESS page except if
nmhdr.code is one of 0xfffffcd7, 0xfffffcda (didn't test what happens if
nmhdr.hwndFrom is readable)
nmhdr.code gets overwritten if nhmdr.code is one of 0xfffffcd9, 0xfffffd17,
0xfffffd18, 0xfffffd19, 0xfffffd1a, 0xfffffd30, 0xfffffd31, 0xfffffe34,
0xfffffe35, 0xfffffe36, 0xfffffe37, 0xfffffe38, 0xfffffe39, 0xfffffe3a,
0xfffffe3b, 0xfffffe3c, 0xfffffe3d, 0xfffffe3e, 0xfffffe62, 0xfffffeb7,
0xfffffeb8, 0xfffffeb9, 0xfffffeba, 0xfffffebb, 0xfffffebd, 0xfffffebe,
0xfffffebf, 0xfffffec0, 0xffffff4d, 0xffffff4e, 0xffffff4f, 0xffffff50,
0xffffff51, 0xffffff5d, 0xffffff5f, 0xffffff62 (see foo2.txt)
(toolbar_original_parent gets the message after overwriting nmhdr.code)
note: 0xfedcba9876543210, 0xabc, 0x4444444444444444 are arbitrary garbage
numbers
note: foo2.c code is not very good because I didn't care about non-x64
windowses and first time using windows-specific api
note: toolbar_original_parent is called h1 in foo2.c
I think this bug is reason why pressing enter in 7-zip file manager path input
doesn't work in wine and reactos (
https://old.reddit.com/r/winehq/comments/16ah3ze )
--
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=58262
Bug ID: 58262
Summary: Battle.net Launcher login dbghelp problem
Product: Wine
Version: 10.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: fymfifa(a)gmail.com
Distribution: ---
Created attachment 78601
--> http://bugs.winehq.org/attachment.cgi?id=78601
bug when using battle.net launcher (on login)
When battle.net launcher is started a problem occures that prevents the app
from loging in...
--
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=32342
Bug #: 32342
Summary: PlanetSide2 Error message and bugreport.txt and
debug.log in Steam.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: linards.liepins(a)gmail.com
Classification: Unclassified
Created attachment 42683
--> http://bugs.winehq.org/attachment.cgi?id=42683
PlanetSide2 bugreport.txt
Cannot run PlanetSide 2 on x64 Fedora 17. Popuing up three similar error log
message with attached bugreport. Also attached debug.log is generated in Steam
install dir.
--
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=40584
Bug ID: 40584
Summary: DLTCEP: wrong window layout, buttons cannot be pressed
Product: Wine
Version: 1.9.9
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: p1(a)devopsx.com
Created attachment 54426
--> https://bugs.winehq.org/attachment.cgi?id=54426
how it looks in wine
In a modal window, buttons at the bottom can't be pressed with mouse
(presumably due to tabbed control are reaching too far down). But if focused
with tab, pressing with enter or space works fine.
This is a recurrence of https://bugs.winehq.org/show_bug.cgi?id=8522. I'm not
sure if it's ever been fixed.
--
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=58267
Bug ID: 58267
Summary: BigPEmu (game emulator): regression in Wine 10.8,
won't launch, error: "Failed to create an OpenGL
context" (macOS)
Product: Wine
Version: 10.8
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cemer99797(a)isorax.com
Created attachment 78613
--> http://bugs.winehq.org/attachment.cgi?id=78613
macOS Terminal log, wine-devel 10.8
On macOS, there is a regression in Wine-devel 10.8 that causes the BigPEmu
Atari Jaguar emulator not to launch, with the following error message on
startup:
> One or more vital systems failed to initialize. Enable logging and check the log for details.
These are the lines from the BigPEmu log
> Error: Failed to create an OpenGL context. This indicates a driver problem.
> Error: Video init failure: BigPEmu_Video_OpenGL
(to enabled logging, launch with `wine ~/BigPEmu/BigPEmu.exe * -logging`, then
check the log in ~/BigPEmu/debug_log.txt)
This program launched fine in Wine-devel 10.7 and lower
tested with Wine-devel 10.8 binary release from Gcenx
(https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.8) on macOS 11.7.10
tested with BigPEmu 1.18 for Windows x64
download: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.zip
sha256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2
--
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=57988
Bug ID: 57988
Summary: BigPEmu 1.18: D3D12 rendering issues
Product: Wine
Version: 10.3
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cemer99797(a)isorax.com
Created attachment 78238
--> https://bugs.winehq.org/attachment.cgi?id=78238
intro with D3D12
In BigPEmu (an Atari Jaguar emulator), .png images are not loaded/rendered
correctly when using the D3D12 renderer
Steps to reproduce:
1. launch BigPEmu 1.18 as follows and note how the intro animation looks using
the default OpenGL renderer:
wine ~/BigPEmu_v118/BigPEmu.exe
2. use backspace/enter to navigate backward/forward in BigPEmu, go to main menu
> Input > Input Device 1 > Set Bindings, and note how the controller image
looks in the top right
3. change to D3D12 renderer: go back to the main menu > Video > Video Plugin >
BigPEmu_Video_D3D12
4. exit and relaunch BigPEmu, note how the intro looks, and once inside the app
note how the background looks. Go back to the Set Bindings menu and note how
the controller image looks. Check the attached screenshots
tested with BigPEmu 1.18 for Windows x64
download link: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.ziparchive.org link: https://archive.org/download/bigpemu-v1.00/BigPEmu_v118.zip
SHA-256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2
tested on macOS 11.7.10
Intel CPU (Haswell), integrated Intel GPU (HD Graphics 5000)
Wine Devel 10.3 from homebrew
--
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=57975
Bug ID: 57975
Summary: screen shaders don't work in BigPEmu.exe
Product: Wine
Version: 10.0
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cemer99797(a)isorax.com
BigPEmu is an Atari Jaguar emulator, it runs Atari Jaguar games fine under Wine
Stable 10.0 on macOS 11. The problem is there is a "screen effects" feature
(which are like screen shaders in RetroArch, used to emulate old CRTs, etc)
which doesn't work. By default, BigPEmu uses OpenGL (BigPEmu main menu > Video
> Video Plugin > BigPEmu_Video_OpenGL) but can also be changed to use D3D12
which will cause it crash at startup on macOS 11.
Steps to reproduce:
1. launch BigPEmu 1.18 with the following options (also opens a console):
wine ~/BigPEmu_v118/BigPEmu.exe * -conout
2. use backspace/enter to navigate backward/forward in BigPEmu, go back to the
main menu, then Video > Screen Effect > choose any screen effect
3. an error message pops up: "Failed to set the selected screen effect. It may
be incompatible with your hardware or video plugin. You can enable logging and
check the log for more details."
4. check the console which shows this error: "[1;31mError: Graphics hardware
isn't equipped to run screen effects. If this error occurs with
SM5.0-compatible hardware, try updating your graphics drivers."
tested with BigPEmu 1.18 for Windows x64
download link: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.zip
SHA-256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2
tested on macOS 11.7.10
Intel CPU (Haswell), integrated Intel GPU (HD Graphics 5000)
Wine Stable 10.0 with GStreamer 1.24.12 from homebrew
--
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=58260
Bug ID: 58260
Summary: winehq repo giving checksum doesn't match??
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikes(a)kuentos.guam.net
CC: austinenglish(a)gmail.com
Distribution: ---
WineHQ packages
100% | 816.8 KiB/s | 237.7 KiB | 00m00s
>>> Downloading successful, but checksum doesn't match. Calculated: 7a01302c17a9ce348c3b055863df8a417ac2fcb41de105236c57b72648907
--
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.