https://bugs.winehq.org/show_bug.cgi?id=57880
Bug ID: 57880
Summary: Cannot upgrade to Wine 10.2 on Ubuntu due to
amd64/i386 conflict in file location
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: contramuffin(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 78103
--> https://bugs.winehq.org/attachment.cgi?id=78103
Error message when upgrading wine-devel-amd64
Upgrading to Wine 10.2 fails. wine-devel-amd64 is throwing an error during the
upgrade which says that it's attempting to overwrite a file location used by
wine-devel-i386. Using Kubuntu 24.10. See attached file for error message
--
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=57870
Bug ID: 57870
Summary: Failed to load wine-staging and wineboot for wine-10.2
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: pinkertoninrandolph(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
wine: failed to load /opt/wine-staging/lib/wine/i386-windows/ntdll.dll error
4000000e
err:environ:run_wineboot failed to start wineboot 1
All day I searched for the previous wine-staging .deb files
With the .deb files, I can easily install the previous working version
My fault for not keeping a copy of these files before upgrading to wine-10.2
I feel angry that I could not simply download the previous version, the binary,
the .deb files. Searching for the wine-staging-10.1.deb files made me feel
crazy today.
I apologize for ranting.
--
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=56553
Bug ID: 56553
Summary: ClickOnce app fails during initial download
Product: Wine
Version: 9.3
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maemigh(a)gmail.com
Created attachment 76314
--> https://bugs.winehq.org/attachment.cgi?id=76314
Console output from wine
ClickOnce app using winetricks to install dotnet472 fails at the application
download stage. Previously worked on older wine versions (still works with
version used by Whisky).
--
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=57997
Bug ID: 57997
Summary: Upgrade to winehq-devel 10.3 from winehq-devel 9.x
causes creates a broken install on Debian Bookworm.
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 78258
--> https://bugs.winehq.org/attachment.cgi?id=78258
APT console output
With the recent deprecation of the wine64 binary, upgrading winehq 64bit
packages on Debian fails due to the attempt to overwrite the
/opt/wine-{variant}/bin/wine file.
That file is owned by the 32bit package, but the 64bit one is now attempting to
overwrite it. Causing a dpkg failure, and breaking the installation.
My 0.02 cents: One fix may be just to use wine's version number in the install
prefix and then simply select the most recent version as the default through
the alternatives system. (Which would also allow concurrent installation of
multiple versions of wine for easier regression testing, and is similar to what
Proton allows for.)
E.x. /opt/wine-10.3-devel/bin/wine
Another fix would be to have a seperate tools package that contains the wine
loader for the given host arch. (Which seems to be more inline with what the
deprecation was trying to achieve.)
--
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=42893
Bug ID: 42893
Summary: Cann't insert any HBITMAP in RichEdit control
Product: Wine
Version: 2.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: xiewei(a)deepin.com
Distribution: ---
1.Run Edit.exe with wine
2.Select any emoticon insert to the richedit,but nothing happened.
--
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=54951
Bug ID: 54951
Summary: Calling SetUserObjectInformationW with
UOI_TIMERPROC_EXCEPTION_SUPPRESSION causes Invalid
parameter
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: cocoa(a)hoto.us
Distribution: ---
Created attachment 74476
--> https://bugs.winehq.org/attachment.cgi?id=74476
reproducible executable file
Confirmed on Ubuntu 22.04, wine-8.8.
I am developer who develops company internal software, using Win32 API.
Some of our members using macOS, So I recommended CrossOver.
However that member says It's crashing, I thought It maybe x64 issue so I
provided x86 build for them. It seems to work at first, but crashed after
seconds. It reports: "[87 0x81] Invalid parameter.".
I traced stack and I found this line is the problem:
https://github.com/rodrigocfd/windigo/blob/master/ui/any_globals.go#L172
And I commented out that line, It works with some graphic issue. (No graphic
issue on Wine)
I don't know about Wine's workaround about this function as many, But It seems
to UOI_TIMERPROC_EXCEPTION_SUPPRESSION flag caused the error.
I attached a simple reproducible program that creates 500x500 window.
I also confirmed It crashes on Wine 8.8, the latest development release.
I sent this issue also to CodeWeavers, but I'm filing this bug report because
this also happens on Wine.
By Wine doesn't crash but throws invalid exception, there is no trace
attachment.
Thanks.
--
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=57923
Bug ID: 57923
Summary: MEmu Android Emulator STUCK IN 99%
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: pocomal112(a)codverts.com
Distribution: ---
MEmu Android Emulator STUCK IN 99%
Here is the link to the software's website to know what software it is
https://www.mumuplayer.com/index.html
--
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=57993
Bug ID: 57993
Summary: winedevice.exe Hangs After Exiting Games
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nekoNexus(a)protonmail.ch
Distribution: ---
Created attachment 78253
--> https://bugs.winehq.org/attachment.cgi?id=78253
Vanilla Wine version 10.3 Log
Distro: Gentoo Linux (x86_64)
DXVK Version: 2.6
Gamescope Version: 3.16.2
Desktop Environment: KDE Plasma 6.2.5 (Wayland)
CPU: Ryzen 3700X @ 4.98 GHz
RAM: 32GBs @ 3600 MHz
GPU: AMD RX 7800 XT
Mesa Version: 25.0.1
Explanation:
-------------
When launching games like Sherlock Holmes: Crimes and Punishments (GOG),
exiting the game (even just launching the game and closing via the main menu
not long after) causes winedevice.exe to just hang (and this causes a zombie
window to remain open) and I'm forced to run "pkill -9 winedevice.exe" (this
problem is consistent)
It doesn't seem to show up at the end of my log, either, for some reason.
I'll still share my log (although, this specific log exhibits a separate issue
I'm about to file) for reference, however
--
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=57991
Bug ID: 57991
Summary: ULTRAKILL (ver. 16c): Graphical issues causing very
blue gameplay
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: amongusus.sinuous664(a)slmails.com
Distribution: ArchLinux
Created attachment 78248
--> https://bugs.winehq.org/attachment.cgi?id=78248
Terminal output text file
I am trying to play Ultrakill on my t430 thinkpad on Arch Linux. While it is
technically playable, the main problem is that major graphical glitches occur,
which can be seen in the attached screenshots. In the screenshots there is an
excess of blue where there shouldn't be, making it difficult to play the game
normally. The issue occurs when I launch ULTRAKILL via wine, go past the intro
screen, and load up any level with 3D graphics.
Link to the game's storepage (where I got the game):
https://store.steampowered.com/app/1229490/ULTRAKILL/
CPU: Intel i7-3632QM
GPU: Intel HD Graphics 4000
Video driver version: Mesa 25.0.1-arch1.2
Kernel version: 6.13.7-arch1-1
--
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=57978
Bug ID: 57978
Summary: Running winetest crashes VMWare Fusion
Product: Wine-Testbot
Version: unspecified
Hardware: aarch64
OS: Windows
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.lippmann.development(a)gmail.com
I'm running winetest, and Fusion says it has encountered an error and must shut
down.
I know, not supported, and probably a Fusion bug. But I figured I'd document
it here.
--
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.