https://bugs.winehq.org/show_bug.cgi?id=57482
Bug ID: 57482
Summary: Total Annihilation (GOG, demo) – The game menu opens
in full screen, but the rendered part doesn’t fit the
display.
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: karol23145(a)gmail.com
Distribution: ---
Created attachment 77494
--> https://bugs.winehq.org/attachment.cgi?id=77494
wine_screenshot
WARNING: The GOG version of the game is broken starting from Wine version 9.17.
(Different bug.)
GAME DEMO CAN BE DOWNLOADED FROM:
https://archive.org/details/TotalAnnihilation_201405
I tested the Total Annihilation demo on the following Wine versions: 9.22,
9.22-staging, 9.0, 8.0, and 7.0.
Additionally, I tested the GOG version of Total Annihilation with the Commander
Pack on these Wine versions: 9.16 (last working version), 9.0, 8.0, and 7.0.
The bug is present in all tested versions, so it is likely not a regression.
Attaching wine and windows screen-shots.
After starting gameplay, everything works correctly, only menu is bugged.
--
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=57402
Bug ID: 57402
Summary: Xubuntu 24.04 with Wine Version 9.0~repack
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: newgvfone(a)gmail.com
Distribution: ---
Created attachment 77388
--> https://bugs.winehq.org/attachment.cgi?id=77388
TCP/IP communication to device crashes app & Wine?
This application worked fine with Ubuntu XFCE 22.04 but after upgrading to
24.04 it no longer works.
I tried uninstalling and reinstalling Wine (Version 9.0~repack) from the Ubuntu
software center but that did not help.
I will try a .deb file install of version 9.2 if I can to see if that helps.
This is probably Canonical's fault and not a Wine bug but I'm not savvy enough
to know.
Crash log is 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=57383
Bug ID: 57383
Summary: wine 9.0 stable
Product: Wine
Version: 9.0
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dsimonyan100(a)gmail.com
I can't run my games whenever I try to run my games the wine debugger pops up
please help me
--
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=56733
Bug ID: 56733
Summary: error
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mcsedude(a)msn.com
Distribution: ---
Created attachment 76512
--> https://bugs.winehq.org/attachment.cgi?id=76512
error
will not work attached 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.
https://bugs.winehq.org/show_bug.cgi?id=56684
Bug ID: 56684
Summary: native wayland restart to xorg causes freezes
Product: Wine
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zlice(a)crtdrift.us
Distribution: ---
from memory (maybe missed something, did something extra)
- start wayland
- run a game with native wine (star wars kotor)
- regedit and change back to `x11,wine`
- exit wayland (wine server is still running)
- start xorg
- run a game... bad times ensue. freezes, have to kill everything in tty, kill
wine
probably low priority as ppl shouldn't do this once their environment is set up
and working. idk the behavior of wine and restarting itself.
--
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=56941
Bug ID: 56941
Summary: EA app fails to launch game if total size of
environment variables exceeds ~32000 characters
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)gmail.com
Distribution: ---
### Steps to reproduce
Preparation:
- Have the EA app installed:
https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases…
- I installed it through Bottles, which installs the following Winetricks
dependencies:
https://github.com/bottlesdevs/programs/blob/main/Games/eaclient.yml
Reproducing:
- Set a very long environment variable, before launching the EA app
- From the EA app, launch any game
- Alternatively, execute the game directly, it will automatically launch the
EA app to launch the game
- If you don't have any game, "The Sims 4" is free
- The game won't launch, an error popup from the EA app will appear (see notes)
### Notes
It doesn't matter whether these ~32000 characters are from a single environment
variable, or from the combination of many of them.
I didn't test on Windows. It may be impossible to test there, since the
environment block there has a limit of 32760 characters (which may probably be
the reason for this issue in the first place).
I say "~32000", because the issue starts occurring a little before 32760
characters. However, my counting method was imprecise (I simply typed `set` in
`wine cmd`, then counted the characters), and there's also the fact that the EA
app also sets its own environment variables.
The issue also occurs with games bought from Steam (thus launched with Proton)
that also have to go through the EA app (thanks EA).
This issue existed before, and the weird thing is that the error popup from the
EA app is different from some time ago (I imagine due to the app being
updated).
Before it was: "Failed to launch game. An error on our end caused the launch to
fail. Try again a little later."
Now it's: "The game hasn't released yet" (which is obviously untrue).
Is it a stack overflow issue?
Logs obtained with `WINEDEBUG=EADesktop.exe:+relay` are too big to attach, even
compressed. Let me know what `WINEDEBUG` parameters I should use instead.
I can see that the app calls `GetEnvironmentStringsW`, shortly followed by a
`WideCharToMultiByte` for each variable (key and value separately). This is
done three times.
--
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=52500
Bug ID: 52500
Summary: error with winediag (nodrv_CreateWindow)
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: josue.bock(a)univ-smb.fr
Distribution: ---
Created attachment 71795
--> https://bugs.winehq.org/attachment.cgi?id=71795
output in command line showing errors
Hello,
When upgading from 6.22 to 6.23, wine does not open anymore with a software.
It seems to be related to another bug report
(https://bugs.winehq.org/show_bug.cgi?id=51210) but AFAIC see, this was not the
same wine version involved.
My laptop also has two GPU, one Intel and one Nvidia.
The Intel one is expected to be unactivated.
I asked for help on the forum before sending this bug report, the discussion is
here: https://forum.winehq.org/viewtopic.php?f=2&t=36155&p=135932#top
--
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=27584
Summary: MFC fillrect draws differently under wine
Product: Wine
Version: 1.3.21
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bailey937(a)yahoo.com
Created an attachment (id=35259)
--> (http://bugs.winehq.org/attachment.cgi?id=35259)
sample program for reproducing FillRect bug
I have a program that uses CPaintDC.FillRect() to draw histogram samples.
It draws one-pixel wide vertical rectangles.
Under wine, the bottom-most pixel is not drawn.
I'm attaching a sample program. Under Windows7 (have 64bit pro), the red line
is touching the black baseline and the black line on the right is touching the
baseline also.
When I run the program under wine, both the red vertical line on the left and
the black vertical line on the right are floating one pixel above the baseline.
I tried both 32bit Ubuntu 11.04 (wine 1.2.2) on a netbook and also Fedora 15
64bit (wine 1.3.21) under Virtualbox on my Windows machine. Both have the same
problem.
The relevant code for the test case is in
CChildView::OnPaint() in ChildView.cpp
--
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=48483
Bug ID: 48483
Summary: Mouse cursor always visible in Gothic 2 with D3D11
renderer
Product: Wine-staging
Version: 5.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: supercoolemail(a)seznam.cz
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Gothic 2 (Russian with 2.6 no-cd patch) with D3D11 renderer shows X11/KDE mouse
all the time. Cursor should not be visible in Gothic 2 at all. It does not have
any functional impact but it's disturbing.
How to reproduce:
- Get Gothic 2.
- Test G2 works (menu at least).
- Extract GD3D11 (e.g. from
https://github.com/Kirides/GD3D11/releases/download/v17.7-dev8/Gothic2-GD3D…
but even old versions from Liker suffer from same issue). DLLs from archive
belong to `<game dir>/System` directory.
- Start the game with `ddraw=n,b`.
- See that mouse cursor appears when menu finishes loading. Alternatively,
mouse movements make cursor appear even before menu finishes loading.
There is some analysis here https://github.com/Tk-Glitch/PKGBUILDS/issues/428 .
I can confirm that same issue happens with clean wine-staging 5.0rc4 from Arch
repositories (also with wine-tkg built from master). While clean G2 works
properly in vanilla wine, GD3D11 needs staging otherwise it crashes at startup.
Tested on
`Linux coolhost 5.4.12-arch1-1 #1 SMP PREEMPT Tue, 14 Jan 2020 21:44:31 +0000
x86_64 GNU/Linux`
Ryzen 7 1700
RX 580 8G
16 G RAM
mesa 19.3.2
--
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.