http://bugs.winehq.org/show_bug.cgi?id=58515
Bug ID: 58515
Summary: Street Chaves only displays a black screen
(regression)
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: denilsonsa(a)gmail.com
Distribution: ---
Wine versions up to 9.7 were able to render the game graphics correctly. Now I
tested again on Wine version 10.11 and all I get is a black screen.
The game seems to be working, because I can blindly press "Z" to confirm, then
"5" to insert credits (and hear the sound effect), and "1" to start, an "Z" a
couple of times to select my character and advance to the actual fight… After
all of this, I can hear the in-game music and the in-game sound effects of the
fight. I just can't see any of it due to being pure black.
How to reproduce?
1. Get the game archive from https://archive.org/details/street-chaves-1.5-a
2. Unpack it anywhere, and run `wine Chaves.exe`
3. After a few moments, a black window without any decoration will show up.
Having no decorations is normal expected behavior. Having it completely black
is a bug/regression.
Tests?
The game works fine under "Proton Experimental" on the Steam Deck, but I don't
know exactly what is the Wine version.
It also works fine under "Proton 10.0-1 (beta)".
It does NOT work (black screen) under Wine 10.11 on Manjaro Linux.
It does NOT work (black screen) under wine-ge-8-26-x86_64, which is the default
Wine runner for Lutris, installed from Flatpak.
https://lutris.net/games/street-chaves/
Other Wine versions are untested.
If you are testing other versions, please be aware that older versions had a
problem with keyboard input. You could see graphics on the screen, but you
couldn't progress any further. This has been solved in bug 52738.
--
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=49905
Bug ID: 49905
Summary: VbsEdit runs wscript.exe with unsupported switches /d
and /u
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wscript
Assignee: wine-bugs(a)winehq.org
Reporter: sloper42(a)yahoo.com
Distribution: ---
Created attachment 68266
--> https://bugs.winehq.org/attachment.cgi?id=68266
patch for wscript
In VbsEdit version 9.2139 from https://www.vbsedit.com/, when choosing "Start
Debugging with wscript", wscript.exe is called with unsupported options /d
(debug) and /u (unicode).
Therefore wscripts bail out and script is not executed.
Solution is to ignore these options.
--
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=58637
Bug ID: 58637
Summary: SimCity 2000 Windows 95 edition doesn't launch
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ihatemylife0025(a)gmail.com
Distribution: ---
Created attachment 79198
--> http://bugs.winehq.org/attachment.cgi?id=79198
Logs
The Windows 95 edition of SimCity 2000 (URL:
https://archive.org/details/sc2000_win95) doesn't launch. I remember it did
work in older versions of wine (I think 8.0) but I can't point out the exact
version it stopped working.
Steps to reproduce:
Launch the game directly (not the setup, it's 16-bit and it's known to be
problematic even on Windows. The game itself is 32-bit)
WIN95/SC2K/SIMCITY.EXE
I tried https://github.com/sc2kfix/sc2kfix too which is a patch that gets the
game running on modern versions of Windows but it didn't make any difference.
My computer's technical specifications (although I don't think they matter, I
tried it with several different computers with different distros and got the
exact same error):
GPU:
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2
[Iris Xe Graphics] (rev 01)
Subsystem: Lenovo Device 3f9c
Kernel driver in use: i915
Kernel modules: i915, xe
CPU:
11th Gen Intel(R) Core(TM) i5-1135G7 (8) @ 4.20 GHz
Laptop Model:
82H8 (IdeaPad 3 15ITL6)
Kernel Version:
Linux 6.15.10-200.fc42.x86_64
Distribution:
Fedora 42 KDE Plasma Edition
--
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=7115
Alexandre Julliard <julliard(a)winehq.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #30 from Alexandre Julliard <julliard(a)winehq.org> ---
Closing bugs fixed in 10.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.
http://bugs.winehq.org/show_bug.cgi?id=58744
Bug ID: 58744
Summary: Missing Type on get_type within dlls/msi/suminfo.c
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: matgrioni(a)gmail.com
Distribution: ---
For a certain use case I wanted to run Microsoft Keyboard Layout Creator
(MSKLC) on a serverless function and therefore was trying to get it to run on
Wine.
The application takes a keyboard layout definition and then has functionality
to create a MSI which contains the DLL for the created keyboard. When running
this compilation step, the MSI creation was failing and I was able to identify
that the MSI creation process with MSKLC was calling MsiSummaryInfoSetPropertyW
with property PID_EDITTIME which is missing from /dlls/msi/suminfo.c:get_type
and should have type VT_FILETIME according to this documentation:
https://learn.microsoft.com/en-us/windows/win32/msi/summaryinfo-summaryinfo.
By adding PID_EDITTIME to the function, I was able to unblock this part.
Overall it's a trivial problem and fix, I figure in part it hasn't been run
into is that the use case of *creating* an MSI (rather than running it), is
quite small, and it seems the EDITTIME property may not be read from on
installation.
I created a bug for it, since I was having issues creating a fork and the
problem is quite trivial, and my ability to contribute to wine will probably
not extend much beyond this issue :)
--
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=54670
Bug ID: 54670
Summary: 16-bit applications fail in wow64 mode
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, Installer, wow64
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
$ wineserver -k ; rm -rf ~/.wine ; WINE=/opt/oldwownew/wine-8.0/bin/wine
winetricks -q icodecs
------------------------------------------------------
Executing load_icodecs
Executing cabextract -q -d
/home/austin/.wine/dosdevices/c:/windows/temp/codinstl/
/home/austin/.cache/winetricks/icodecs/codinstl.exe
Executing cd /home/austin/.wine/dosdevices/c:/windows/temp/codinstl/
Executing /opt/oldwownew/wine-8.0/bin/wine setup.exe /s
0284:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in
experimental wow64 mode
0284:fixme:wow:wow64_NtSetLdtEntries 0107 02d0323f 0100f338 0000 00000000
00000000: stub
0284:err:module:LdrInitializeThunk "krnl386.exe16" failed to initialize,
aborting
0284:err:module:LdrInitializeThunk Initializing dlls for
L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005
------------------------------------------------------
--
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=58742
Bug ID: 58742
Summary: winedbg: Internal crash at 00006FFFFF8CB5E5
(pe_load_msc_debug_info)
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: zowie+wine(a)vandillen.io
Distribution: ---
Platform: Linux Mint 21.3 Cinnamon
Linux Kernel: 5.15.0-156-generic
Platform 2: Linux Mint 22.2 Cinnamon
Linux Kernel 2: 6.8.0-83-generic
When I build Wine myself and run the command `$WINE winedbg explorer` with it,
it leads to a crash. This does not happen with the official builds of Wine, so
I'm guessing there's some package version difference or something along those
lines that makes this occur.
Log from a custom build of 10.15:
```
user@pc:~/wine/test$ $WINE winedbg explorer
WineDbg starting on pid 0184
0180:fixme:dbghelp:elf_search_auxv can't find symbol in module
0180:fixme:dbghelp:elf_search_auxv can't find symbol in module
winedbg: Internal crash at 00006FFFFF8CB5E5
user@pc:~/wine/test$
```
Log from the official build of 10.15:
```
user@pc:~/wine/test$ wine winedbg explorer
WineDbg starting on pid 01b4
01b0:fixme:dbghelp:elf_search_auxv can't find symbol in module
01b0:fixme:dbghelp:elf_search_auxv can't find symbol in module
0x006fffffc00c3d ntdll+0x10c3d: retq
Wine-dbg>
```
The crash occurs in pe_load_msc_debug_info from pe_module.c, in the branch with
`/* Debug info is stripped to .DBG file */`. The variable `dbg` is null, so it
crashes when trying to dereference it.
Here's a quick fix I made for it. It fixes the crash but it doesn't really
solve
the underlying issue. As a result the debugger is missing so much debug
information that it's not actually that helpful.
```
/* Read in debug directory */
dbg = RtlImageDirectoryEntryToData( mapping, FALSE,
IMAGE_DIRECTORY_ENTRY_DEBUG, &nDbg );
nDbg = dbg ? nDbg / sizeof(IMAGE_DEBUG_DIRECTORY) : 0;
/* NEW */
if (!dbg)
{
pe_unmap_full(fmap);
return ret;
}
/* END */
/* Parse debug directory */
```
It's a bit annoying but for the time being I'll probably use the official build
for debugging, or maybe I'll try to build Wine using the Docker set-up from the
Gitlab CI.
--
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=58666
Bug ID: 58666
Summary: wine 10.14 fails to build in alpine linux x86
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nathbappai(a)gmail.com
Distribution: ---
Created attachment 79251
--> http://bugs.winehq.org/attachment.cgi?id=79251
linker error output
* gcc 15.2.0
* mingw gcc 15.2.0
* build script
https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/wine/A…
* build error is in the attached linker-error-output.txt file.
--
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=58730
Bug ID: 58730
Summary: Images in iTunes have a white background (see picture)
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: usr_40476(a)icloud.com
Distribution: ---
Created attachment 79347
--> http://bugs.winehq.org/attachment.cgi?id=79347
bruh
um not quite sure how to further explain it so i guess heres a 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.