http://bugs.winehq.org/show_bug.cgi?id=58711
Bug ID: 58711
Summary: DNF refuses to install or update winehq-staging,
checksum sha256sum mismatch
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: charlesthethobe(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Since wine version 10.15 release I'm unable to perform a system update due to
mismatching checksums between what the repo suggests and the actual rpm
package.
https://dl.winehq.org/wine-builds/fedora/42/x86_64/winehq-staging-10.15-1.1…
This file's checksum is currently:
7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0
While it's expected to be:
b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6
I tried running `# dnf clean metadata` to no avail.
--
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=58703
Bug ID: 58703
Summary: Fedora 42: Suddenly getting checksum errors
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: johnny.jy.ooi(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Recently, while trying to do the standard "dnf upgrade", my system sees updates
for wine-staging and winehq-staging, but upon triggering the upgrade, I get
checksum errors
Total size of inbound packages is 226 MiB. Need to download 226 MiB.
After this operation, 6 MiB extra will be used (install 1 GiB, remove 1 GiB).
[1/2] winehq-staging-1:10.15-1.1.x86_64
100% | 144.6 KiB/s | 75.0 KiB | 00m01s
>>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc
>>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc
>>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc
>>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc
>>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc
[2/2] wine-staging-1:10.15-1.1.x86_64
0% | 3.3 MiB/s | 1.7 MiB | 00m01s
>>> Not finished - interrupted by error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bd
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2/2] Total
100% | 3.4 MiB/s | 1.8 MiB | 00m01s
Failed to download packages
Librepo error: Downloading successful, but checksum doesn't match. Calculated:
7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256)
Expected:
b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6(sha256)
I've tried removing the winehq.repo, reimporting the repo key
(https://dl.winehq.org/wine-builds/winehq.key), readding the repo according to
the instructions, and doing "dnf clean" and it keep failing the checksum
checks.
I know there's been some issues with the repo in the past, do we have another
similar 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.
http://bugs.winehq.org/show_bug.cgi?id=58738
Bug ID: 58738
Summary: debian packages and wow64
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: info(a)fernandolucas.info
CC: dimesio(a)earthlink.net
Distribution: ---
So far it seems that the Debian packages are built without the wow64 support?
Is this right?
If so, in view of the wine 11 release, allowing the wow64 mode in the packages
would be a great step forward.
There is the step of the hardcoded dependency into the i386 packages.
I have workaround this with a local dummy package,
printf "Package: wine-devel-i386-dummy
Version: %s
Architecture: all
Provides: wine-devel-i386 (= %s)
Conflicts: wine-devel-i386
Replaces: wine-devel-i386
Maintainer: Dummy Maintainer <noreply(a)example.com>
Description: Dummy package to satisfy wine-devel-i386 dependency
This is a placeholder package that pretends to be wine-devel-i386.
" "$VERSION" "$VERSION" > wine-devel-i386-dummy_${VERSION}/DEBIAN/control
I install this package first, and then I can install wine-devel and
winehq-devel without complaining about dependencies. It would be ideal if the
repositories also provide something such as wine-devel-i386-dummy in the
release process and document that by installing it, the win32 dependency is
avoided.
--
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=56184
Bug ID: 56184
Summary: - Elite Dangerous Data Interface)
Product: Wine
Version: 9.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
Distribution: ---
Program does not start.
https://github.com/EDCD/EDDI/issues/1976
It's a companion app for this game:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=37490
Console output without "winetricks dotnet472":
[ERROR] FATAL UNHANDLED EXCEPTION: System.EntryPointNotFoundException:
CreateInstalledObjectsInfo assembly:<unknown assembly> type:<unknown type>
member:(null)
at (wrapper managed-to-native)
MS.Internal.PtsHost.UnsafeNativeMethods.PTS.CreateInstalledObjectsInfo(MS.Internal.PtsHost.UnsafeNativeMethods.PTS/FSIMETHODS&,MS.Internal.PtsHost.UnsafeNativeMethods.PTS/FSIMETHODS&,intptr&,int&)
at MS.Internal.PtsHost.PtsCache.InitInstalledObjectsInfo
(MS.Internal.PtsHost.PtsHost ptsHost,
MS.Internal.PtsHost.UnsafeNativeMethods.PTS+FSIMETHODS& subtrackParaInfo,
MS.Internal.PtsHost.UnsafeNativeMethods.PTS+FSIMETHODS& subpageParaInfo,
System.IntPtr& installedObjects, System.Int32& installedObjectsCount) [0x0024c]
in <d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.PtsCache.CreatePTSContext (System.Int32 index,
System.Windows.Media.TextFormattingMode textFormattingMode) [0x0003c] in
<d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.PtsCache.AcquireContextCore
(MS.Internal.PtsHost.PtsContext ptsContext,
System.Windows.Media.TextFormattingMode textFormattingMode) [0x000b0] in
<d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.PtsCache.AcquireContext
(MS.Internal.PtsHost.PtsContext ptsContext,
System.Windows.Media.TextFormattingMode textFormattingMode) [0x00035] in
<d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.PtsContext..ctor (System.Boolean
isOptimalParagraphEnabled, System.Windows.Media.TextFormattingMode
textFormattingMode) [0x0003c] in <d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.StructuralCache.EnsurePtsContext () [0x0001b] in
<d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.StructuralCache.get_Section () [0x00001] in
<d31f3a57049e4054ad4371f364def5bc>:0
at MS.Internal.PtsHost.FlowDocumentPage..ctor
(MS.Internal.PtsHost.StructuralCache structuralCache) [0x00010] in
<d31f3a57049e4054ad4371f364def5bc>:0
[...]
When installing "dotnet472" there's a DirectX problem. This can be workarounded
by using "winetricks dxvk". Console output without DXVK:
0150:fixme:d3d:wined3d_check_device_format_conversion output 00FD2060,
device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM,
dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
0150:fixme:d3d:wined3d_device_apply_stateblock Last Pixel Drawing Disabled, not
handled yet.
0150:fixme:d3d:wined3d_check_device_format_conversion output 00FD20C4,
device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM,
dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
01bc:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0120:fixme:dwrite:dwritetextanalyzer_AnalyzeNumberSubstitution (0F753F80 0 100
01081FF0): stub
0150:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0150:err:d3dcompiler:D3DCompile2 Shader log:
0150:err:d3dcompiler:D3DCompile2 <anonymous>:144:1: E5000: syntax error,
unexpected KW_PASS, expecting '}'
0150:err:d3dcompiler:D3DCompile2
0150:fixme:seh:WerRegisterMemoryBlock (FF9B2E60 6144) stub
0150:fixme:seh:WerRegisterMemoryBlock (FF9B2E10 4) stub
01bc:err:d3d:wined3d_context_gl_update_window Failed to get a device context
for window 0F67ACA8.
01c0:err:d3d:wined3d_context_gl_update_window Failed to get a device context
for window 0F717F48.
--
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=39352
Bug ID: 39352
Summary: Soulbringer launcher doesn't paint buttons initially
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://www.gog.com/game/soulbringer
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Created attachment 52445
--> https://bugs.winehq.org/attachment.cgi?id=52445
screenshot (comparison)
Originally reported in https://bugs.wine-staging.com/show_bug.cgi?id=96
When I start the game launcher, the 4 buttons in it (play,video,advanced,quit)
are not drawn either in fullscreen or in virtual desktop mode.
If I grab the launcher window and move it towards the edge of the screen, the
buttons appear when that part of the window which holds the buttons moves
beyond the screen.
The launcher needs mfc42.dll.
There is no demo version available.
In the terminal:
fixme:win:EnumDisplayDevicesW ((null),0,0x33d9f8,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:win:EnumDisplayDevicesW ((null),0,0x33d9f8,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0x33ddd8,0x00000000), stub!
The patch from staging to blame:
https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-D…
The patch fixes bug #35652.
wine-1.7.51-225-g3966aff
Fedora 22
XFCE 4.12
XOrg 1.17.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.
http://bugs.winehq.org/show_bug.cgi?id=58113
Bug ID: 58113
Summary: foobar2000 [v2.24.3 x64]: Volume Control is not
applied on M1 mac
Product: Wine
Version: 10.5
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ssnffb30(a)gmail.com
I am using Default UI.
Changing the volume control bar does not change the actual volume.
I have tried all output devices.
Perhaps it is a bug in winecoreaudio?
--
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=58727
Bug ID: 58727
Summary: foobar2000 crash
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: anezaki.yasuhiro(a)gmail.com
Distribution: ---
Created attachment 79336
--> http://bugs.winehq.org/attachment.cgi?id=79336
foobar2000 crash reports
foobar2000 crash
--
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=50458
Bug ID: 50458
Summary: Tooltips block input in Foobar2000
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: debilerpc(a)web.de
Distribution: ---
**Context:**
Like with most media players, Foobar2000's playlist view is essentially a
spreadsheet where each line is a track and each column displays a tag or
metadata field.
If the length of the tag exceeds the width of the column, it gets cut off. You
can see the full tag in a tooltip by hovering over it with a mouse in that
case.
**The problem:**
As long as the tooltip is displayed, the app registers neither keyboard nor
mouse input.
I suspect this problem exists in a variety of
[apps](https://bugs.winehq.org/show_bug.cgi?id=16227), not just Foobar2000, but
here it is especially annoying.
**Expected behavior:**
When input is sent, the tooltip should disappear, and Foobar2000 should react
to the input. This is what happens under Windows 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.
http://bugs.winehq.org/show_bug.cgi?id=58506
Bug ID: 58506
Summary: Some VST plugins using OpenGL don't render in WOW64
mode (black screen)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: opengl
Assignee: wine-bugs(a)winehq.org
Reporter: a.oleinic103(a)gmail.com
Distribution: ---
When using yabridge to run Windows VST plugins in a native Linux DAW (in my
case, REAPER), Waves plugins do not render correctly, showing a black window.
The window is interactable (grabs the cursor, can change settings, etc), but
dragging it, closing and re-opening, etc. does not work. In the logs, the
plugins show a bunch of OpenGL errors. This is specifically a WOW64 regression,
since using a build of Wine 10 without WOW64 works fine.
This is what it looks like:
09:07:42 [WaveShell1-VST3 14.12_x64-09EFPegt] [Wine STDERR]
0024:err:opengl:null_glEnable unsupported
09:07:42 [WaveShell1-VST3 14.12_x64-09EFPegt] [Wine STDERR]
0024:err:opengl:null_glBlendFunc unsupported
(Sorry for pasting it here, I have read the rules, but it's not letting me
paste text as an attachment for some reason :/)
--
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=52959
Bug ID: 52959
Summary: Some games are rendered in square instead fullscreen
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: slawek(a)lach.art.pl
Distribution: ---
Some games (like Empire Earth: Gold, Commandos: Behind Enemy Lines) do not
render property. It renders only in top-left square (full game frame). Rest of
screen is black.
--
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.