Bug 2338935 - wine-10.0-0.7rc4.fc40.x86_64 fails to run Blizzard's StarCraft
Summary: wine-10.0-0.7rc4.fc40.x86_64 fails to run Blizzard's StarCraft
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Cronenworth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-20 01:31 UTC by Louis van Dyk
Modified: 2025-02-19 03:07 UTC (History)
3 users (show)

Fixed In Version: wine-10.1-1.fc41 wine-10.1-1.fc40
Clone Of:
Environment:
Last Closed: 2025-02-12 01:36:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Louis van Dyk 2025-01-20 01:31:32 UTC
After upgrading wine to wine-10.0-0.7rc4.fc40.x86_64, Blizzard's StarCraft.exe (the original one, with BroodWars expansion), no longer starts. The black screen appears, and the debugger screen pops up (although it fails to debug).  Running it from CLI shows this:
0104:err:winebth:bluez_dbus_loop Error getting object list from BlueZ: 'org.freedesktop.DBus.Error.NameHasNoOwner': 'Could not activate remote peer 'org.bluez': activation request failed: unknown unit'
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
wine: Unhandled page fault on read access to 00000000 at address 00000000 (thread 0024), starting debugger...


After downgrading wine to wine-9.1-1.fc40.x86_64 StarCraft.exe once again executes successfully.

Reproducible: Always

Steps to Reproduce:
1. Upgrade wine to 10.0-0.7rc4.fc40.x86_64
2. Run:  wine "/home/louis/.wine/drive_c/Program Files/Starcraft/StarCraft.exe"
3. Game fails to launch successfully
4. dnf downgrade wine
5. wine 9.1-1.fc40.x86_64 installs
6. Running the above succeeds.
Actual Results:  
As in details.

Expected Results:  
Game should launch

Comment 1 Michael Cronenworth 2025-01-20 15:28:56 UTC
Application issues, even games, should be investigated via e-mail or discussion forum first.

https://forum.winehq.org/

https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/

Comment 2 Fedora Update System 2025-02-10 05:27:43 UTC
FEDORA-2025-b360045c67 (wine-10.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b360045c67

Comment 3 Fedora Update System 2025-02-10 14:17:46 UTC
FEDORA-2025-f899cee10e (wine-10.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f899cee10e

Comment 4 Fedora Update System 2025-02-11 01:52:08 UTC
FEDORA-2025-f899cee10e has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f899cee10e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f899cee10e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2025-02-11 02:19:32 UTC
FEDORA-2025-b360045c67 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b360045c67`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b360045c67

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-02-12 01:36:48 UTC
FEDORA-2025-b360045c67 (wine-10.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2025-02-19 03:07:31 UTC
FEDORA-2025-f899cee10e (wine-10.1-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.