https://bugs.winehq.org/show_bug.cgi?id=55845
Bug ID: 55845
Summary: Blair Witch (2019) from GOG won't launch due to a X
error
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
The error is:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 156 (NV-GLX)
Minor opcode of failed request: 43 ()
Serial number of failed request: 377
Current serial number in output stream: 378
GPU: NVidia RTX 3070
Driver: 535.54.03
Wine: wine-8.19
OS: Ubuntu 22.10
MR applied: https://gitlab.winehq.org/wine/wine/-/merge_requests/4223
--
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=28842
Bug #: 28842
Summary: Dungeon Defenders configurator renders slowly
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rmlipman(a)gmail.com
Classification: Unclassified
Demo available on Steam
Must be installed in 1.3.26 (requires installing .net 3.5 even if already
installed, regression in bug 28401)
To reproduce:
Launch the game from Steam
Select configure
Configurator app will be slow
--
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=54598
Bug ID: 54598
Summary: New Shorter Oxford English Dictionary doesn't show
(child) window
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
Created attachment 74128
--> https://bugs.winehq.org/attachment.cgi?id=74128
nsoed.png blank/gray screen
Forum: https://forum.winehq.org/viewtopic.php?p=139548#p139548
URL: https://archive.org/details/pcbasics-31
While I'm not entirely sure if this is the same problem Canard has, New Shorter
Oxford English Dictionary (NSOED) no longer works properly after Wine version
7.5
When NSOED is started, a blank/gray screen is displayed (nsoed.png)
A window becomes visible when the user clicks Window -> Cascade
I can imagine that this look like the database is not loading.
d765edc411a6844f6322dd9da280aa0436391828 is the first bad commit
commit d765edc411a6844f6322dd9da280aa0436391828
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Fri Mar 18 14:27:55 2022 +0100
win32u: Move NtUserCreateWindowEx implementation from user32.
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=55833
Bug ID: 55833
Summary: HeidiSQL 12.5.0.6677 crashes on start since Wine 8.17
on ArchLinux
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: clemens.ml(a)gmx.net
Distribution: ---
Created attachment 75330
--> https://bugs.winehq.org/attachment.cgi?id=75330
HeidiSQL Bug report output.
Arch Linux (latest)
Starting heidisql 12.5.0.6677 vompiled with Delphi 11 on different wine
versions:
wine 8.16 works fine.
wine 8.17 crashes:
exception message : Access violation at address 00000002FB43949D in module
'comctl32.dll'. Write of address FFFFFFFFFE1FF500.
wine 8.18 crashes:
exception message : Access violation at address 00006FFFFE13956D in module
'comctl32.dll'. Write of address FFFFFFFFFE1FF500.
Reproducable: always
I might be able to debug using gdb when I receive detailed instructions.
--
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=55761
Bug ID: 55761
Summary: PLSQL Developer: Access Violation when trying to log
in
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robertdejager(a)tutanota.com
Distribution: ---
Created attachment 75249
--> https://bugs.winehq.org/attachment.cgi?id=75249
Screenshot of the error
Since wine version 8.17, PL/SQL Developer throws an Access Violation exception
when trying to log into a database.
I have attached a screenshot with the exact error.
Steps to reproduce:
* Install wine 8.17
* Download Oracle Instant Client (64 bit) and unzip into your prefix in
c:\ORACLE\instantclient_21_9
* Import the registry entries from the attached .reg file
* Edit c:\ORACLE\instantclient_21_9\tnsnames.ora and add a connect string for a
database (apologies, I cannot provide a database or a connect string for it)
* Install PL/SQL Developer 14 (64 bit) (15 gives me crippling visual glitches,
so I could not test)
* Run PL/SQL Developer and try to log into a database
Workaround:
* Downgrade to wine <= 8.16
--
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=55747
Bug ID: 55747
Summary: The 64-bit dbghelp:dbghelp fails in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The 64-bit dbghelp:dbghelp fails in Wine:
New Windows-on-Windows case:
dbghelp.c:827: Test failed: Wrong bitness aggregation count 0 5
dbghelp.c:829: Test failed: Wrong kind aggregation count 0 1
dbghelp.c:831: Test failed: Wrong directory aggregation count 5 0
dbghelp.c:889: Test failed: Wrong kind aggregation count 1 2
dbghelp.c:1213: Test failed: [64/32 enum:+32bit wow64]: Unexpected
enum.count_exe 1
dbghelp.c:1337: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum
count32_bit (23/23)
dbghelp.c:1343: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum
wowdir (22/22)
dbghelp.c:1345: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum exe
(1/1)
dbghelp.c:1213: Test failed: [64/32 enum:default wow64]: Unexpected
enum.count_exe 0
dbghelp.c:1217: Test failed: [64/32 enum:default wow64]: Unexpected
enum.count_32bit 0
dbghelp.c:1223: Test failed: [64/32 enum:default wow64]: Unexpected
enum.count_wowdir 0
dbghelp.c:1226: Test failed: [64/32 enum:default wow64]: Unexpected
sym.count_exe 0
dbghelp.c:1230: Test failed: [64/32 enum:default wow64]: Unexpected
sym.count_32bit 0
dbghelp.c:1236: Test failed: [64/32 enum:default wow64]: Unexpected
sym.count_wowdir 0
Old Windows-on-Windows case:
dbghelp.c:818: Test failed: Wrong bitness aggregation count 0 1
dbghelp.c:820: Test failed: Wrong kind aggregation count 0 1
dbghelp.c:822: Test failed: Wrong directory aggregation count 1 0
dbghelp.c:671: Test failed: C:\windows\syswow64\ntdll.dll shouldn't already be
loaded
dbghelp.c:878: Test failed: Wrong bitness aggregation count 22 2
dbghelp.c:880: Test failed: Wrong kind aggregation count 1 2
dbghelp.c:882: Test failed: Wrong directory aggregation count 1 22
dbghelp.c:1278: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected
enum.count_exe 1
dbghelp.c:1284: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected
enum.count_systemdir 1
dbghelp.c:1289: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected
enum.count_ntdll 2
dbghelp.c:1296: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected
sym.count_64bit 1
dbghelp.c:1297: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected
sym.count_systemdir 1
dbghelp.c:1337: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different
sym/enum count32_bit (22/24)
dbghelp.c:1339: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different
sym/enum count64_bit (1/0)
dbghelp.c:1345: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different
sym/enum exe (1/1)
dbghelp.c:1347: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different
sym/enum exe (1/2)
dbghelp.c:1278: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
enum.count_exe 0
dbghelp.c:1284: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
enum.count_systemdir 1
dbghelp.c:1289: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
enum.count_ntdll 1
dbghelp.c:1291: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
sym.count_exe 0
dbghelp.c:1296: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
sym.count_64bit 1
dbghelp.c:1297: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
sym.count_systemdir 1
dbghelp.c:1302: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected
sym.count_ntdll 1
dbghelp.c:1337: Test failed: [64/32 enum:default wine_old_wow64]: Different
sym/enum count32_bit (0/1)
dbghelp.c:1339: Test failed: [64/32 enum:default wine_old_wow64]: Different
sym/enum count64_bit (1/0)
See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp
A bisect shows that this started with the commit below:
commit de81e2ea41b27a14f88177639c5b5d35a210b5bd
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Oct 6 15:08:02 2023 +0200
ntdll: Only create the main module on the 32-bit side for wow64.
This means this most likely has the same fix as bug 55744.
--
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=55960
Bug ID: 55960
Summary: user32: 512 is not enough for LB_ADDSTRING
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
So, as noted in bug 54034, while dealing with some out-of-memory crashes, I ran
into an odd one, one that could be triggered even shortly after reload and
acting more like a buffer overflow bug.
Namely, if a certain string that was about to be displayed on the screen was
above 530 chars (but it had newline embedded), the game crashed, but didn't if
the string was manually truncated.
It left me grasping at straws, as my (quite lacking) gdb skills didn't lets me
see where the crash occurred.
So, I was left waiting for some burst of inspiration.
It came today.
For some reason, this felt like I had been hitting some internal limit. I
suspected wine code.
After trying a few debug channel combinations, I eventually tested 'msg'.
The strings were printed using ID3DXFontImpl_DrawTextA.
In the log, I've noted LB_ADDSTRING and - after looking at that code - took a
stab in the dark.
I've set the buffer size for that message in both WINPROC_CallProcAtoW and
WINPROC_CallProcWtoA to 1536 (yes, likely excessively large). Making this
change has fixed the crash.
I'm marking it wine 8.21, but I expect this has been around as long as wine has
been using too small buffer.
--
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=55511
Bug ID: 55511
Summary: Wine repeatedly prints err:system:update_display_cache
Failed to read display config.
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: m101010a(a)gmail.com
Distribution: ---
In sysparams.c the read_display_adapter_settings function uses the global
variable config_key, but does not actually initialize it. This causes the
function to fail, and that failure eventually trickles down to
update_display_cache. I haven't seen any functionality break because of it, but
the messages are annoying and could be trivially fixed by initializing
config_key before it is used.
--
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=55014
Bug ID: 55014
Summary: kernel32:comm crashes in WoW64 mode on Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:comm crashes in WoW64 mode on Linux:
comm.c:708: Found Com port COM1. Connected devices may disturb results
Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit
code (0x007f47b448083c).
[...]
=>0 0x007f47b448083c wait_for_event+0x1c(arg=<internal error>)
[/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945]
in ntdll.so (0000000000000000)
0x007f47b448083c wait_for_event+0x1c
[/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945]
in ntdll.so: mov (%rdi), %rdi
945 if (!server_get_unix_fd( commio->hDevice, FILE_READ_DATA |
FILE_WRITE_DATA, &fd, &needs_close, NULL, NULL ))
See https://test.winehq.org/data/patterns.html#kernel32:comm
The failure seems to only happen on the TestBot VMs, maybe because of QEmu,
particularly because it does not set the baud rate correctly.
A bisect shows that this failure started with the commit below:
commit b337c5b1a1757b2abbc90a7c6955d64242861ab9
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Jun 2 09:35:29 2023 +0200
ntdll: Use the default ABI for all functions on the Unix side.
--
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=45305
Bug ID: 45305
Summary: [AZERTY Keyboard]Certains special keys are not
correctly recognized.
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Hello,
I have a problem when i want to use special character with my French Keyboard.
If i use "é", "è", "ç" and "à" keys in winecfg, regedit or notepad, these
symbols are correctly write.
But in game/all games, if i use these keys, the game does not recognize it.
Example for Vampyr, "é" symbol is used by default for an action. If i want to
use "é" for an other action, when i press the key on my keybaord, there is no
effect, the key is not recognized.
I have this problem even if i export LC_ALL=fr_FR before to launch Steam.
If someone had this issue in the past and fix this problem, i'll say him thanks
you.
--
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=54616
Bug ID: 54616
Summary: Wine 8.0+, Memory Access Violation in Libaes.dll,
Texecom Wintex
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zestier-bib.0a(a)icloud.com
Distribution: ---
Created attachment 74142
--> https://bugs.winehq.org/attachment.cgi?id=74142
Error from console when Program is run.
When attempting to run running Texecom Wintex in Wine 8.0 or above, there is a
Memory Access Violation/Buffer Overrun error c0000005 in libaes.dll.
Downgrading to Wine 7.0.1 with no other changes allows the program to run
normally.
The environment has C++ Redistributable 2010 installed as required.
There is no GUI errors shown when the issue is present. The attached .txt file
contains the error that is printed when the program is run via the console.
libaes.dll seems to be specific to this program.
The program can be downloaded from here:
https://texecom-live.s3.eu-west-2.amazonaws.com/wp-content/uploads/2022/08/…
(no account required)
or https://www.texe.com/help-and-support/product-support/ (free account
required)
No accounts or hardware is needed to run the software.
See also: My forum post:
https://forum.winehq.org/viewtopic.php?p=139794#p139794
If I can provide any more information, please let me know.
--
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=40236
Bug ID: 40236
Summary: winetricks ie6: buttons are missing
Product: Wine
Version: 1.9.4
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Regression SHA1: 6e638d824b80e8a02cb830cd6bc25a7ef8507849
Distribution: Fedora
Created attachment 53780
--> https://bugs.winehq.org/attachment.cgi?id=53780
screenshot
Regression, introduced by:
commit 6e638d824b80e8a02cb830cd6bc25a7ef8507849
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
Date: Mon Mar 23 10:20:59 2015 +0800
shell32: Update version information to match XP values.
To reproduce:
$ rm -rf ~/.wine
$ winetricks -q ie6
$ cd ~/.wine/drive_c/Program\ Files/Internet\ Explorer/
$ wine "C:\\program files\\internet explorer\\iexplore.exe"
see screenshot.
--
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=53114
Bug ID: 53114
Summary: Crash of applications and games when out of focus
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ryu.ketsueki(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I don't know why this happens but every wine application I could test, they
need to stay on focus in the current virtual desktop (from the Desktop
Environment, not Wine's virtual desktop) or else they will simply close on
their own. I can't track to a specific cause because even with a completely new
prefix with no "helpers", Lutris and even Valve's own Proton, this happens. So
far I got the exact same result with The Sims 4, StarCraft 2 and Sonic After
the Sequel. All those games will close if I change to another virtual desktop,
let's say, desktop 2, if the apps themselves are on desktop 1. It also happened
with the releases but it persists with Staging as well. I don't know how to
backtrace this, as launching them through CLI didn't return anything useful and
I'm not sure if wine itself is what is crashing or the applications. I didn't
get the classic crash window either. They simply close.
--
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=40712
Bug ID: 40712
Summary: blueMSX hangs at start
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jeremielapuree(a)yahoo.fr
Distribution: ---
Lauching the msx emulator blueMSX makes it hang: here is the short console
output
wine blueMSX.exe
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make
sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the
winbind package of your distribution.
fixme:dwmapi:DwmIsCompositionEnabled 0x6d88c758
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69e94b5e, context
0x8bd300, init_notify 0, handle 0x127e1b0): stub
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make
sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the
winbind package of your distribution.
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0a6836, context
0x93dd98, init_notify 0, handle 0x124e7a4): stub
wine: configuration in '/home/david/.wine' has been updated.
fixme:win:EnumDisplayDevicesW ((null),0,0x33ec64,0x00000000), stub!
fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for
adapter 0.
err:aspi:SCSI_OpenDevice Failed to open device /dev/sg0: Permission non
accordée
fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for
adapter 1.
fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for
adapter 2.
err:aspi:SCSI_OpenDevice Failed to open device /dev/sg2: Permission non
accordée
fixme:win:EnumDisplayDevicesW ((null),0,0x33ea54,0x00000000), stub!
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:d3d:wined3d_surface_blt Can't handle WINED3D_BLT_DO_NOT_WAIT flag.
--
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=49177
Bug ID: 49177
Summary: Naruto Online
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kacper.cholody(a)onet.pl
Distribution: ---
Created attachment 67194
--> https://bugs.winehq.org/attachment.cgi?id=67194
dont know
When i run an application its showing a bug. I cant run game
--
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=45268
Bug ID: 45268
Summary: Logicly 1.9 (Adobe AIR app) windows do not resize
correctly when screen resolution is set to non-default
value
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
Created attachment 61511
--> https://bugs.winehq.org/attachment.cgi?id=61511
Start log for logicly 1.8
Logicly 1.9 (Adobe AIR application) installs and works perfect when the screen
resolution is left at the default (96 dpi). When changing the screen resolution
to a higher value (which is necessary for newer displays) Logicly shows its
windows minimized. This prevents installing because (i.e.) the License accept
dialog can not be confirmed.
To reproduce
- Download logicly 1.9 (see download link)
- change the screen resolution with winecfg to (i.e.) 168 dpi
- Install Logicly by calling the installer, start it after installation
The shown windows are minimized and not resizable.
When installing with the default screen resolution and running Logicly later,
its windows are minimized and can be resized. so the app is usable in
principle.
It may be of interest, that the previous release (Logicly 1.8) does not have
this problem (download from http://logic.ly/updates/Logicly-1.8.0.exe).
The log files from the start of both releases 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=54243
Bug ID: 54243
Summary: Warcraft 2 BNE: Fails CD check in wine versions >6.0.X
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: mmogilvi2+wine(a)gmail.com
Distribution: ---
SYMPTOM: Starting with wine versions mid-6.X and including all 7.X through at
least 7.22, the game "Warcraft 2: Battle.net Edition" always fails a CD check
and pops up an error dialog:
"Warcraft II Battle.net Edition is unable to read a required file. Your
Warcraft II Battle.net Edition CD may not be in the CDROM drive. Please ensure
that the disk in in the CDROM drive and press OK. To leave the program, press
Exit."
----
BACKGROUND:
Wine had long been able to run "Warcraft 2: Battle.net Edition", up through
wine version 6.0.2 and some early 6.X versions.
As described in the howto of the application DB
https://appdb.winehq.org/objectManager.php?sClass=version&iId=592 (and other
places), in my setup I have long used an .iso of my original CD, with symlinks
for "d::" (linked to the iso) and "d:" (linked to the directory where the .iso
is loop-mounted). (I actually use some wrapper scripts to temporarily mount it
only when needed, etc...)
I unsuccessfully asked about this in the wine forum last July
https://forum.winehq.org/viewtopic.php?f=8&t=36787&sid=e1b75b6a5ffa1534a042…
and am finally digging deeper into it on my own. There are also some
tangential mentions in my recent Gentoo Linux forum post:
https://forums.gentoo.org/viewtopic-p-8766703.html
----
ANALYSIS:
I have managed to git bisect this bug to commit
50903a15046354e405564aff6430ee505c01100a "kernelbase: Reimplement
GetVolumeInformation on top of GetVolumeInformationByHandle" (although I needed
to cherry-pick an unrelated "sincos()" build fix at each step...).
Digging deeper, the following sequence of events leads to the bug:
1. The game calls GetVolumeInformationW() with root=L"D:\\".
- The game only wants file system flags and FS type name.
- Wine proceeds to:
2. NtOpenFile() the root (I haven't traced into this much)...
3. GetVolumeInformationByHandleW()
4. NtQueryVolumeInformationFile() with
info_class=FileFsAttributeInformation
5. get_mountmgr_fs_info(), which determines
unix_name="/archive/wineData/warcraftII-BNE-2001.iso"
and letter=25 (Z:).
- BUG: letter=25 definitely indicates a bug. The game is asking
about D:, not Z:.
- MAYBE BUG: Not sure whether mapping "D:\\"'s handle to the .iso
rather than the loop mount point directory is a bug or not.
- FYI: I'll note that NtQueryVolumeInformationFile()'s documentation
says that if the handle "represents a direct device open, only
FileFsDeviceInformation can be specified..." in the remarks (i.e.,
not the info_class being asked for here). There doesn't seem
to be any attempt to enforce this in wine. See
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-nti…
6. Since wine now thinks the game is asking about "Z:", it returns file
system type "NTFS" and associated flags, rather than the correct
"CDFS" (and flags).
7. Presumably the game sees the "NTFS" and/or flags, decides this
isn't a CD at all, and after some more searching, ultimately
pops up the error dialog.
----
POTENTIAL FIXES:
I'm not sure the best way to fix this. Some possibilities include:
A. Somehow ensure the handle that GetVolumeInformation() opens gets
mapped to the mounted directory, instead of the .iso file?
- This would seem to make sense, but I'm not sure.
B. Add more logic to find_dos_device() to notice if path is a file
(or device) that is pointed at by one of the double-colon symlinks?
- It might need similar caching as get_drives_info(), etc?
This would be just a little involved, but might be the best
"smallish scale" fix.
C. Just revert commit 50903a15046354e405564aff6430ee505c01100a?
But that might leave GetVolumeInformationByHandle() broken,
and it does seem cleaner to only do all the device/FS
superblock parsing and determination in one place...
D. Do a more thorough audit / cleanup of how different ways of
representing and mapping between unix names, NT names, devices,
mount points, symlinks, fallback logic, etc all interact with
each other? My initial vague impression is that a lot of this
logic is a bit haphazard and only "mostly" works, rather than
being robustly designed to always work.
- Very involved and time consuming, and well beyond anything
I currently have any interest in attempting myself.
----
WORKAROUND:
A quick end-user workaround that seems to work is to change the "d::" symlink
to point to the correct /dev/loop0 or loop1, or 2...., that just happens to
match whatever free loop device that "mount" dynamically picks to use.
- I think this only works because these days /dev is usually
mounted as a separate file system, and in wine there is
find_dos_device() logic to stops looking if the st_dev changes
and then later stuff falls back on doing something else...
- Even disregarding that, it seems a bit ugly and fragile to
assume a particular loop device, especially if you have other
things you sometimes loop mount... (Although maybe my wrapper
script could dynamically update the symlink based on parsing
/proc/mounts after things are mounted...)
--
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=23921
Summary: LBA2 doesnt refresh its screen
Product: Wine
Version: 1.3.0
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vleon1(a)gmail.com
Little big adventure 2 rarely refresh its screen, rendering the game
unplayable. the bug didnt exist in the 1.2 branch.
You can hear the games music from the next screen (for example from the ingame)
while having a picture of the games menu.
--
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=55703
Bug ID: 55703
Summary: Introduced in 8.17
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugs(a)cometchaser.de
Distribution: ---
Drag and drop of files within an commercial applications doesn't work anymore
in Wine 8.17.
It worked until Wine 8.16.
It works in Debian 11 with Wine 8.8 or Debian 12 with Wine 8.16 but not anymore
in Debian 11 with Wine 8.17
See the error:
Error new in Wine 8.17
Download a video file at:
https://www.cometchaser.de/wine/Wine-8.17-Error.mkv
Download a video file at:
https://www.cometchaser.de/wine/Wine-8.16-Works.mkv
--
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=55561
Bug ID: 55561
Summary: kernel32:virtual - The 32-bit test_write_watch() fails
in the new WoW mode
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:virtual - The 32-bit test_write_watch() fails in the new WoW mode:
virtual.c:2099: Test failed: VirtualAlloc succeeded
See https://test.winehq.org/data/patterns.html#kernel32:virtual
A bisect shows that this started with the commit below:
commit f6dbcccab9e33f05b4df9ba3824a849b172b97c3
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Aug 28 13:47:14 2023 +0200
wow64: Send cross-process notifications.
--
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=45123
Bug ID: 45123
Summary: gdiplus/graphicspath test crashes under clang-5.0.1
but not gcc-7.3.0
Product: Wine
Version: 3.7
Hardware: x86
URL: https://test.winehq.org/data/8dca6c35e11a104385242ed83
46ee05707b78ef7/linux_ae-gentoo-dbg-clang/gdiplus:grap
hicspath.html
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: madewokherd(a)gmail.com
Distribution: Gentoo
Backtrace:
=>0 0x7eca42d9 widen_joint+0x139(p1=<is not available>, p2=<is not available>,
p3=<is not available>, pen=<is not available>, last_point=<has been optimized
away by compiler>)
[/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:1849]
in gdiplus (0x0033fc38)
1 0x7eca2ac1 GdipWidenPath+0x3a0(path=<is not available>, pen=<is not
available>, matrix=<is not available>, flatness=<is not available>)
[/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:2029]
in gdiplus (0x0033fca8)
2 0x7ed36262 func_graphicspath+0x3331() in gdiplus_test (0x0033fe08)
3 0x7ed74968 main+0x457() in gdiplus_test (0x0033fea8)
4 0x7ed74caa in gdiplus_test (+0x8fca9) (0x0033fee0)
5 0x7b45df9c call_process_entry+0xb() in kernel32 (0x0033fef8)
6 0x7b45e0f3 start_process+0x122(entry=0x7ed74f7a, peb=<is not available>)
[/var/lib/jenkins/home/workspace/wine-clang/dlls/kernel32/process.c:1099] in
kernel32 (0x0033ffdc)
7 0x7b45dfaa start_process_wrapper+0x9() in kernel32 (0x0033ffec)
0x7eca42d9 widen_joint+0x139
[/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:1849]
in gdiplus: divps %xmm5,%xmm0
1849 float dx0 = distance * (p2->X - p1->X) / length_0;
--
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=27916
Summary: Ferro CCTV: Fails to start
Product: Wine
Version: 1.3.25
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=35713)
--> (http://bugs.winehq.org/attachment.cgi?id=35713)
Error message
Steps to reproduce:
1) remove ~/.wine
2) winetricks wmp9
3) install Ferro CCTV
4) wine FerroCCTV.exe
Behaviour:
Error message (see attachment).
Expected behaviour:
No error message.
--
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=55908
Bug ID: 55908
Summary: Regression beginning with 8.17: PNGGauntlet gives an
error message and hangs if output folder doesn't exist
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: NM64+bugs.winehq.org(a)PM.me
Distribution: ---
Created attachment 75452
--> https://bugs.winehq.org/attachment.cgi?id=75452
wine-devel 8.16
Beginning with wine-devel 8.17, PNGGauntlet no longer properly handles if the
output folder doesn't already exists.
In wine-devel 8.16 it would ask that the location doesn't exist and if it
should be created, and it'd "just work" without issue.
In wine-devel 8.17 and newer (including the newest 8.20), you get some sort of
error message instead and the program can end up hanging.
Attached are two demonstration videos, one using wine-devel 8.16 and the other
8.17, showing the entire process from scratch on a live ISO session of Linux
Mint 21.2 Cinnamon.
I've also attached the terminal output as well as the information that the
error message returns.
(oh and, is it just me, or is the "Compiling Wine" steps of
https://wiki.winehq.org/Regression_Testing completely out of date, at least
when testing in live ISO sessions of modern Debian-based distros like not only
the aforementioned Linux Mint 21.2 Cinnamon but also LMDE 6 and Xubuntu 23.10)
--
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.