http://bugs.winehq.org/show_bug.cgi?id=58751
Bug ID: 58751 Summary: Please build Debian packages of wine with ntsync enabled Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs@winehq.org Reporter: shtetldik@gmail.com CC: dimesio@earthlink.net Distribution: ---
I noticed that Debian packages of Wine 10.16 come without ntsync support (which was just completed in 10.16).
Most likely reason is that packages are built without Linux kernel headers being present during build.
You can add linux-headers-amd64 package when building to make it work.
Thank you!
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- There was no warning from configure about ntsync.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #2 from Shmerl shtetldik@gmail.com --- It might be just not complaining and says "no" there? Check what you get for ntsync.h in the log.
http://bugs.winehq.org/show_bug.cgi?id=58751
Chiitoo chiitoo@gentoo.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chiitoo@gentoo.org
--- Comment #3 from Chiitoo chiitoo@gentoo.org --- Looking at the logs, if I'm looking at the correct ones [1], it does look like for the Debian builds the ntsync check says 'no', while in the xUbuntu log it's a 'yes'.
1. https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #4 from Rosanne DiMesio dimesio@earthlink.net --- The Debian 12 and Ubuntu logs say no, the Debian 13 and Testing logs say yes.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #5 from Chiitoo chiitoo@gentoo.org --- (In reply to Rosanne DiMesio from comment #4)
The Debian 12 and Ubuntu logs say no, the Debian 13 and Testing logs say yes.
Was just about to say, after looking more better, that some of them say yes, some don't so I guess the ones with no are still on a kernel version before 6.14 or so? Thus missing the feature.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #6 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Chiitoo from comment #5)
Was just about to say, after looking more better, that some of them say yes, some don't so I guess the ones with no are still on a kernel version before 6.14 or so? Thus missing the feature.
Probably. All our Debian/Ubuntu packages use the same control and rules files. When something like this happens, it is generally because the older distros have a "too old" something.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #7 from Shmerl shtetldik@gmail.com --- I'm using package for testing / forky, and it doesn't work somehow.
I don't see linux-headers-amd64 here:
https://build.opensuse.org/projects/Emulators:Wine:Debian/packages/wine-deve...
Just add to Build-Depends no matter what version, and it should work when kernel has it.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #8 from Shmerl shtetldik@gmail.com --- I see that ntsync.h is also found in linux-libc-dev and you have that installed, but not sure if it's the same one or not. I built stuff locally using linux-headers-amd64 and my build works with ntsync.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #9 from Shmerl shtetldik@gmail.com --- I checked, ntsync.h found in linux-libc-dev and in linux-headers-6.16.9+deb14-common is exactly the same.
So I assume your build with linux-libc-dev present according to your build depends should produce a good result, so why doesn't it work?
I was testing your forky Wine build with Cyberpunk 2077 with mangohud, and it shows that ntsync is not available which is also demonstrated by bad performance (unlike using my build).
The only extra addition I'm using in tests in vkd3d-proton to make Cyberpunk 2077 work normally.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #10 from Shmerl shtetldik@gmail.com --- Also, for the reference. On my build:
rg --binary ntsync bin/wineserver: binary file matches (found "\0" byte around offset 7)
On WineHQ build of Debian forky package (wine-devel-amd64 10.16~forky-1)
rg --binary ntsync
I.e. it doesn't find ntsync anywhere in the wineserver binary.
Debian testing (forky) currently has kernel 6.16.9 so it surely should have ntysybc.h.
See: https://tracker.debian.org/pkg/linux
http://bugs.winehq.org/show_bug.cgi?id=58751
CWB cwbussard@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cwbussard@gmail.com
--- Comment #11 from CWB cwbussard@gmail.com --- I can confirm the same problem with wine-staging 10.16 for Trixie and the Trixie backports 6.16.3 kernel.
Running rg --binary ntsync on /opt/wine-staging/bin/ comes up empty.
Likewise, lsof /dev/ntsync comes up empty while running something in wine.
The Trixie backports kernel has a ntsync module, and it's loaded and permissions are 666: sudo modprobe ntsync sudo udevadm info --name=ntsync
P: /devices/virtual/misc/ntsync M: ntsync J: c10:261 U: misc D: c 10:261 N: ntsync L: 0 E: DEVPATH=/devices/virtual/misc/ntsync E: DEVNAME=/dev/ntsync E: DEVMODE=0666 E: MAJOR=10 E: MINOR=261 E: SUBSYSTEM=misc
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #12 from Shmerl shtetldik@gmail.com --- I don't expect it to work on Trixie unless you build it yourself, since its default kernel headers or libc-dev package has no needed ntsync.h file and they'd be used during winehq build for it as was mentioned in the above comments.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #13 from CWB cwbussard@gmail.com ---
I don't expect it to work on Trixie unless you build it yourself, since its default kernel headers or libc-dev package has no needed ntsync.h file and they'd be used during winehq build for it as was mentioned in the above comments.
Oof. That's kind of a big deal, leaving Trixie in the dirt for at least a couple years to come. Would it be possible to change the WineHQ build process to use the headers from the backports kernel without breaking stuff for people still on the 6.12 kernel?
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #14 from Shmerl shtetldik@gmail.com --- Hopefully it's possible with OBS, but besides that the actual problem for Trixie, even Forky build has something wrong with it, which is why I opened this bug.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #15 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to CWB from comment #13)
Oof. That's kind of a big deal, leaving Trixie in the dirt for at least a couple years to come. Would it be possible to change the WineHQ build process to use the headers from the backports kernel without breaking stuff for people still on the 6.12 kernel?
No. We do not build using backports precisely because it would break things for people who don't use backports.
http://bugs.winehq.org/show_bug.cgi?id=58751
--- Comment #16 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Shmerl from comment #14)
even Forky build has something wrong with it, which is why I opened this bug.
It appears the OBS is installing an older version of linux-libc-dev by default:
[ 22s] [36/784] installing linux-libc-dev-6.12.38-1
It's being installed as part of the base build container provided by the OBS, over which I have no control. I'll try specifying a higher version in the dsc file for the next release.
-
WineHQ Bugzilla