http://bugs.winehq.org/show_bug.cgi?id=58286
Bug ID: 58286
Summary: Cannot create a 64-bit wineprefix with old wow64
Product: Wine
Version: 10.8
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, regression, source, win64
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: cb87d40cd4a8837826ea76efc91371ab09eb9d63
Distribution: Ubuntu
Created attachment 78634
--> http://bugs.winehq.org/attachment.cgi?id=78634
config.logs
Since commit cb87d40cd4a8837826ea76efc91371ab09eb9d63 I have been unable to
create a 64-bit wineprefix when I build Wine. This is running without first
using "make install".
wine: created the configuration directory '/tmp/wine/wineprefix'
wine: WINEARCH set to win64 but '/tmp/wine/wineprefix' is a 32-bit
installation.
Whereas /tmp/wine/wineprefix does not initially exist. It is created by Wine,
but then insists it's 32-bit and immediately exits.
- New wow64 works fine
- 32-bit works fine
- -O0 and -O2 make no difference
- The prebuilt debs work fine
commit cb87d40cd4a8837826ea76efc91371ab09eb9d63
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Feb 14 15:32:19 2025 +0100
makefiles: Create wine as a symlink to tools/wine/wine.
This commit cannot be reverted, but checking out the commit before fixes the
issue.
My process as per
https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#shared-wow64
1. Build 64-bit-only
2. Build 32-bit
3. Build 64-bit-wow
This is the same process I have always used.
I know there's been a number of changes in this area so I don't know how to
work around it.
In all cases I use Debian Stable chroots (with schroot) but the same result
using Debian Testing.
If it's me doing something stupid then I apologise in advance.
--
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=58182
Bug ID: 58182
Summary: Virtual desktop corked in 10.6
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
Created attachment 78478
--> http://bugs.winehq.org/attachment.cgi?id=78478
messed up virtual dektop
Fedora 41
wine-devel-10.6-1.1.x86_64
Xfce 4.18
This is a disaster!
$ wine explorer /desktop=Notepad,1680x1050
open full screen. The dimensions are ignored.
$ wine explorer /desktop=Notepad,1680x1050 notepad.exe (or what ever program
you want)
[1] opens in the upper left of the screen
[2] the top of the decorations bar opens underneath the "panel 1" bar, so you
can not grab the windows and move it
[3] once mouse clicked inside the virtual desktop, the mouse can not be used
off the virtual desktop. (You have to click the "X" in the upper right to
exist the program to get your mouse back.)
[4] the virtual desktop opens a shadow of the panel 1 off to its left (will
provide a screen shot). Note that it does not include itself in the shadow
--
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=44453
Bug ID: 44453
Summary: 30525
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thekagles(a)gmail.com
Distribution: ---
Created attachment 60394
--> https://bugs.winehq.org/attachment.cgi?id=60394
30525
30525
--
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=47147
Bug ID: 47147
Summary: Visual Pinball X crash with wine staging but works
with normal wine dev
Product: Wine-staging
Version: 4.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adec2010(a)hotmail.co.uk
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Visual Pinball X does not run in wine staging but does in normal wine
--
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=58247
Bug ID: 58247
Summary: ABNT Keyboard Not Working Properly in Wine with
Wayland Driver
Product: Wine
Version: 10.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: xnep1(a)hotmail.com
Distribution: ---
Created attachment 78588
--> http://bugs.winehq.org/attachment.cgi?id=78588
Tracefile with winedebug=keyboard,key showing "/" not working
When running Wine applications using the Wayland driver, certain keys on the
Brazilian ABNT2 keyboard (such as the slash /, question mark ?, and other
special characters) do not function correctly. These keys either generate no
character.
In contrast, when using the X11 driver (wine X11), the same keys function as
expected, and the correct characters are produced. Upon inspection, the scan
codes received under Wayland are extended (e.g., 0x259 instead of 0x59 for the
slash key), which seems to lead to incorrect mapping or interpretation by Wine.
This issue appears to stem from incomplete or incorrect handling of extended
scan codes or keyboard layout mapping for the br-abnt2 layout in the Wayland
input.
In my tests, I forced the correct scan code for the slash key (0x59), and after
this adjustment, the key started working properly again.
I have attached a trace log file showing the key input events during the
failure. Although I am currently using a modified version of Wine to generate
this trace, the problem also occurs on the stable Wine release. (It's late and
I'm not going to redo the test just to have a clean trace file. Sorry.)
--
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=48083
Bug ID: 48083
Summary: Directory name with dot as a last character
Product: Wine
Version: 4.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: bi.ja(a)seznam.cz
Distribution: ---
Hi if you create directory name with dot as a last character, wine goes up in
directory structure.
So if you have
c/users/user/Local Settings/Application Data/ČSOB Pojišťovna, a.s.
wine goes to c/users/user/Local Settings/Application Data/
I tested it with winefile.
--
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=57097
Bug ID: 57097
Summary: Keyboard inputs for special characters on non-english
keyboards are switched in winewayland
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: sutupud(a)yahoo.com
Distribution: ---
I noticed that if I use a german keyboard layout, the key mapping seems to be
off. I'm using kwin_wayland (but also tested on sway, same result).
The regular lower keys are ok, but example, ö produces ü, # produces ä, etc.
Looking at dlls/winewayland.drv/wayland_keyboard.c, I saw that there are
different lookup tables for different languages (scan2vk_qwerty,
scan2vk_azerty. scan2vk_qwertz, ...), so my first quess was that something
might be switched there.
But that doesn't really seem the case, changing it to always use
`scan2vk_qwertz ` regardless of `lang` makes it work.
I don't really have a very good understanding of how this is supposed to work,
but does the appliaction really need to do such a translation? Isn't that
already handled by the layout being passed in? At least that would explain why
it works when doing no such lookup 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.
https://bugs.winehq.org/show_bug.cgi?id=55212
Bug ID: 55212
Summary: Need for Speed SHIFT demo crashes due to HLSL syntax
error "unexpected '<', expecting ';' or ','"
Product: vkd3d
Version: 1.8
Hardware: x86-64
URL: https://www.fileplanet.com/archive/p-69053/Need-For-Sp
eed-Shift-Demo
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Distribution: ---
Created attachment 74822
--> https://bugs.winehq.org/attachment.cgi?id=74822
VKD3D_SHADER_DEBUG=trace WINEDEBUG=+d3dcompiler
0024:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0024:err:d3dcompiler:D3DCompile2 Shader log:
0024:err:d3dcompiler:D3DCompile2 <anonymous>:1:40: E5000: syntax error,
unexpected '<', expecting ';' or ','
0024:err:d3dcompiler:D3DCompile2
This seems to be the relevant trace:
vkd3d:0024:trace:preproc_lexer_parse float4x4 worldViewProj : WORLDVIEWPROJ <
bool appEdit = false ; > ;
--
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=48380
Bug ID: 48380
Summary: Visual Basic 6 - Error
Product: Wine
Version: 5.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jopiodz00(a)gmail.com
Distribution: ---
Created attachment 66137
--> https://bugs.winehq.org/attachment.cgi?id=66137
backtrace.txt & Visual Basic 6 portable .exe
This error presents itself when you try to load a project.
--
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=55432
Bug ID: 55432
Summary: PlanetSide 2: White screen when running launcher
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
Distribution: ---
I am using Steam, so when I click "Play" in Steam, the black screen whith
DayBreak logo appears for a second or two, and then it says for few more
moments black and then turns all white.
After following the suggestion to add "--disable-gpu" in
https://www.reddit.com/r/linux_gaming/comments/va7qag/planetside_2_only_loa…
, launcher starts just fine. After that, the BattleEye error occurs, blocking
to run the game.
System:
$ inxi -Gxxx
Graphics:
Device-1: Intel DG2 [Arc A770] driver: i915 v: kernel arch: Gen-12.7 pcie:
speed: 2.5 GT/s lanes: 1 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1,
DP-2, DP-3, DP-4, HDMI-A-3 bus-ID: 03:00.0 chip-ID: 8086:56a0
class-ID: 0300
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
compositor: gnome-shell v: 44.3 driver: gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: BenQ G2420HDBL serial: RAB03454SL000
res: 1920x1080 dpi: 92 size: 477x268mm (18.78x10.55") diag: 604mm (23.8")
modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-2 model: Philips FTV serial: 16843009 res: 1920x1080
dpi: 76 size: 640x360mm (25.2x14.17") diag: 734mm (28.9") modes:
max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel Arc A770 Graphics
(DG2) direct-render: Yes
--
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.