http://bugs.winehq.org/show_bug.cgi?id=58112
Bug ID: 58112
Summary: Unimplemented function
KERNEL32.dll.InitializeSynchronizationBarrier
Product: Wine
Version: 10.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: git.ceeac(a)gmail.com
Distribution: ---
I am developing a cross-platform application that uses barriers as a
synchronization primitive.
This works fine when the application is started on Windows, however when
started on Linux (Arch) + WINE (10.5), the application crashes with
wine: Unimplemented function KERNEL32.dll.InitializeSynchronizationBarrier
called at address 00006FFFFFC695E8 (thread 012c)
Presumably, all of the following functions are unimplemented in WINE:
- InitializeSynchronizationBarrier
- DeleteSynchronizationBarrier
- EnterSynchronizationBarrier
--
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=58548
Bug ID: 58548
Summary: user32/menu: Sub‑menus always open instantly –
TrackPopup/TrackMenu code ignores SPI_GETMENUSHOWDELAY
and MenuShowDelay in registry
Product: Wine
Version: 7.7
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: falcon4(a)gmail.com
Observed:
Registry setting HKEY_CURRENT_USER\Control Panel\Desktop\MenuShowDelay is set
to the intended default value (400).
SystemParametersInfoW(SPI_GETMENUSHOWDELAY) returns the configured value (e.g.
400 ms).
Yet any Win32 app (Task Manager, Notepad++, etc.) opens sub‑menus with zero
delay; mousing past them collapses/opens instantly.
Expected:
Menu pop‑ups wait <MenuShowDelay> ms before showing, matching Windows behaviour
since Win 95.
This bug leads to having to "tightrope" sub-menu selections, carefully moving
the cursor along a selection to prevent the sub-menu from collapsing.
This was reported back in 2009 by a user that was advised to file a Bugzilla
report, but none seems to have ever been made:
https://forum.winehq.org/viewtopic.php?t=4147
At a quick glance through /wine/dlls/win32u/menu.c, it seems like menu-show
delays were never implemented at all, and I can only hope this is worth fixing
to improve user experience after all these years :)
--
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=51847
Bug ID: 51847
Summary: fixme:advapi
Product: Wine
Version: 6.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: danielrosario92(a)gmail.com
Distribution: ---
Created attachment 70741
--> https://bugs.winehq.org/attachment.cgi?id=70741
problems
not installing programs
--
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=56921
Bug ID: 56921
Summary: MusicBee: Random moments of lag when scrolling,
seemingly related to rendering of rating stars.
Product: Wine-staging
Version: 9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v_winebugs(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 76742
--> https://bugs.winehq.org/attachment.cgi?id=76742
Log from terminal
Tested on Wine 9.5-staging, on Fedora 40 KDE Plasma Spin
MusicBee will have these random moments of lag when scrolling on views and
playlists that have rating stars enabled. It seems to be related to how the
stars are being rendered, since when they are hidden the lag goes away, and
this lag is not present when running MusicBee under Windows. To make it worse,
this lag persists after the app is restarted.
Attached is a log from the terminal done while using MusicBee with the lag.
--
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=58545
Bug ID: 58545
Summary: Wine preloader always crashes if I run under nix
develop shell, no programs work
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xvroad(a)gmail.com
Distribution: ---
wine64-preloader always crashes with "Segmentation fault" error at startup if
started under nix develop environment, which I created for developing
yabridge-based C++ app.
The command, nix develop, is a command of nix package manager. It automatically
download tools and libraries needed for developing my C++ app, and creates a
temporary shell with all required environment variables set for development. I
ran the command on NixOS 25.05.
If I understand correctly, nix develop command just sets environment variables.
I have no idea how that lead to a difficult to diagnose crash.
I attached the gdb debugger to debug wine64 and wine64-preloader. It seems that
it's crashing somewhere after wld_start, but I'm not sure exactly where the
issue is.
https://gitlab.winehq.org/wine/wine/-/blob/wine-10.0/loader/preloader.c?ref…
I uploaded the flake.nix for reproducing the issue to a GitHub repo.
https://github.com/vroad/wine-crash-test
I can't reproduce the issue by
* Sourcing environment variables dumped and running wine outside nix develop
shell.
* Setting really long environment variables and running wine outside nix
develop shell. wine can just handle it fine.
* Running wine inside nix develop, but with a different set of packages.
The issue is reproducible on wine built from current latest master commit
(https://gitlab.winehq.org/wine/wine/-/commit/5b5f7fa104582c08e860f84c6fb361…).
--
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=42741
Bug ID: 42741
Summary: StarCraft I: 1.18 PTR fails to initialize
ClientSdk.dll
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: li.davidm96(a)gmail.com
Distribution: ---
Created attachment 57743
--> https://bugs.winehq.org/attachment.cgi?id=57743
stderr output of Wine when running StarCraft.exe
The 1.18 public test release of the upcoming version of StarCraft I does not
launch, as ClientSdk.dll fails to initialize.
Tested with Wine 2.4 (latest from Arch repositories), in a fresh 64-bit
wineprefix. Architecture is AMD64.
The download is here:
https://us.battle.net/forums/en/starcraft/topic/20753915707
sha1sum:
2d6702a425f13659227814fbc903568d63daeb08
/home/lidavidm/Downloads/Starcraft+1.18+PTR+1202.zip
--
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=58544
Bug ID: 58544
Summary: Forums are crippingly slow
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
URL: https://forum.winehq.org/
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: ---
The forums are crippingly slow.
https://forum.winehq.org/
It is currently taking minutes to load a single page, or it is just timing out
with the Cloudflare 504.
I'm going to take a wild guess here and say.... AI crawlers.
Hopefully not though and there's something simpler going on?
--
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=57595
Bug ID: 57595
Summary: Login repeated requested to submit bugs
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dav75uk(a)yahoo.co.uk
CC: austinenglish(a)gmail.com
Distribution: ---
It doesn't seem to remember the login session (on firefox at least) when
submitting bugs and screenshots. Cookie 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=58541
Bug ID: 58541
Summary: I was installing old skype
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: apphelp
Assignee: wine-bugs(a)winehq.org
Reporter: younusalbaloushi(a)gmail.com
Distribution: ---
Created attachment 79039
--> http://bugs.winehq.org/attachment.cgi?id=79039
I was installing old skype and I see this
I was installing this and I see this
--
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=58540
Bug ID: 58540
Summary: Using copy shortcut (Ctrl+C) does not always work on
XWayland
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v_winebugs(a)outlook.com
Distribution: ---
Wine version 10.12
Arch Linux (rolling)
KDE Plasma 6.4.3 on Wayland
When using the Ctrl+C command to copy and paste from a WINE application while
running the X11 version of WINE in XWayland, it doesn't always work. It tends
to work the first time, but subsequent copies are very flaky, and don't work.
I ran into this a lot in MusicBee, as I was copying tags a lot, but I don't
think it's specific to MusicBee, as it also occurs in WINE Notepad. It doesn't
seem to be an issue with KDE's XWayland implementation, as I can copy from
native applications running via XWayland just fine.
I have tried to allow higher keystroke permissions to X11 apps via KDE's System
Settings. This does not occur when running WINE in native Wayland, but there's
another bug in which highlighted text gets erased when clicking away.
How to reproduce:
1. Load any application that has Windows' textbox input in WINE, via XWayland
(e.g. Notepad, MusicBee).
2. Write a test sentence.
3. Copy that sentence using Ctrl+C and paste it into anything else with text
input (e.g. text editor)
4. Write a different test sentence.
5. Copy that one using Ctrl+C, but only once, and attempt to paste it into the
other application.
6. Notice that the old sentence is copied, not the new one.
--
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.