https://bugs.winehq.org/show_bug.cgi?id=50700
Bug ID: 50700
Summary: possible regression? unimplemented function
dx7vb.dll.DllRegisterServer in application that ships
with own dx7vb.dll
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lunarlambda(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I have an old application that came with dx7vb.dll. To get it to run in wine, I
had to `regsvr32 dx7vb.dll`. After that, everything worked fine.
After moving to wine-staging, neither the application or regsvr work anymore,
crashing with an unimplemented call to dx7vb.dll.DllRegisterServer.
Adding a native library override for dx7vb.dll didn't seem to work.
I can't provide much info on the application, it's basically vaporware - but it
did work on stable nevertheless.
--
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=50997
Bug ID: 50997
Summary: Wine version not displaying with staging-6.6
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cybermax(a)dexter.no
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
When launching stuff like eg. winecfg, the patch:
Staging/0001-kernel32-Add-winediag-message-to-show-warning-that-t.patch
supposed to display a FIXME line showing the wine-staging version eg.
"wine-staging 6.6 is a testing version containing experimental patches."
This version (from wine_get_version function) no longer display the version.
Probably due to upstream commit:
https://source.winehq.org/git/wine.git/commitdiff/985bd97c2bb0a161f9cae370a…
--
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=50969
Bug ID: 50969
Summary: Regression - Warframe unable to control camera with
wine-staging 6.6
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Warframe worked normally in wine-staging 6.5 for me.
Archlinux updated to wine-staging 6.6 and consequently I've lost the ability to
control the characters with the mouse in the game. Downgrading the package to
6.5 resolves it, which leads me to believe this is a regression introduced with
6.6.
With 6.6 mouse can still be used in the game menus, but as soon as the 3D world
controls become active it doesn't respond to inputs. Keyboard input works
normally, however the game is unplayable without the mouse.
--
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=48037
Bug ID: 48037
Summary: In World of Tanks in battle, mouse stuck in the middle
Product: Wine
Version: 4.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: HASH.DuOrden(a)gmail.com
Distribution: ---
Starting with wine 4.17, in battle mouse is stuck to the center of the screen,
it's just wiggles in middle and do not move the targeting reticle.
This feels very similar to what happens when "MouseWarpOverride"="force" with
only difference that with "MouseWarpOverride"="force" mouse acts like this all
the time but here mouse are stuck to center only when game requests the lock,
I'm not sure that I get the technical part correctly.
PS:This feels like a continuation of a bug #47771.
--
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=50586
Bug ID: 50586
Summary: [regression] NtQueryInformationFile returning
STATUS_INVALID_INFO_CLASS (0xc0000003) on symlinks
opened with option FILE_OPEN_REPARSE_POINT
(0x00200000)
Product: Wine-staging
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mr.dovi(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 69263
--> https://bugs.winehq.org/attachment.cgi?id=69263
wine_file.c testcase
Possible related issue: https://bugs.winehq.org/show_bug.cgi?id=50036
I'm investigating the cause of a application startup crash happening on
wine-staging 6.0 but not on wine-staging-5.21, wine-5.13 and wine-6.0
While I think I have found a workaround to have it running on staging-6.0, I
realized it may be worth a share since it took me a few hours of searching the
relay logs.
I have attached a test case but basically, calling NtQueryInformationFile on a
symlink opened with the file handle option FILE_OPEN_REPARSE_POINT seem to
cause NtQueryInformationFile to return STATUS_INVALID_INFO_CLASS, even if the
class is correctly set to FileAllInformation
# wine 5.13
# pNtCreateFile -> 0
# NtQueryInformationFile -> 0
# wine 5.13
# pNtCreateFile -> 0
# NtQueryInformationFile -> 0
# wine-staging 5.21
# pNtCreateFile -> 0
# NtQueryInformationFile -> 0
# wine-staging 5.21
# pNtCreateFile -> 0
# NtQueryInformationFile -> 0
# wine-staging 6.0
# pNtCreateFile -> 0
# NtQueryInformationFile -> c0000003
# wine-staging 6.0
# pNtCreateFile -> 0
# NtQueryInformationFile -> 0
My system is Arch Linux
--
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=50761
Bug ID: 50761
Summary: ntdll-Junction_Points update broke macOS compilation
Product: Wine-staging
Version: 6.3
Hardware: x86-64
OS: Mac OS X
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Regression SHA1: 750044c08c49c7a117fcc911506a198969379144
Created attachment 69550
--> https://bugs.winehq.org/attachment.cgi?id=69550
output
This is on a fully updated macOS 10.14 system, using mingw and the macOS 10.13
SDK to compile wine.
--
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=50766
Bug ID: 50766
Summary: In Wine Staging 6.3, symbolic links are no longer
active and become regular files.
Product: Wine-staging
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 93.duke.xperia(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 69557
--> https://bugs.winehq.org/attachment.cgi?id=69557
screenshot
In Wine Staging 6.3, symbolic links are no longer active and become regular
files.
When downgrading to version 6.2, symbolic links are active again.
--
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=50727
Bug ID: 50727
Summary: Foobar2000 fails to install in current Staging
Product: Wine
Version: 6.2
Hardware: x86-64
URL: https://www.foobar2000.org/getfile/foobar2000_v1.6.4.e
xe
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 69481
--> https://bugs.winehq.org/attachment.cgi?id=69481
screenshot from installer
See attached screenshot.
Either:
1. try as current user: result is the installer just exits silently
2. try username/password: result is the installer says you need admin rights.
@Zebediah: I'm guessing this has to do with
https://github.com/wine-staging/wine-staging/commit/811467bf6a4c43de2485b37…
?
--
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=50551
Bug ID: 50551
Summary: Serious Sam Classic (TFE/TSE) has no sound when EAX is
enabled
Product: Wine-staging
Version: 6.0
Hardware: x86-64
URL: https://www.fileplanet.com/archive/p-35640/Serious-Sam
-The-Second-Encounter-Demo
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
The game runs without audio when EAX option is enabled in Staging and EAX is
selected as the sound system in the game' audio options.
'EAX error: Cannot set environment' appears in the game's console.
wine-6.0-201-g2d4dd4252b0 (Staging)
SeriousSamSEDemo.exe
md5sum: 9b22eb6765979a02ecbf641f53d0f162
--
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=47932
Bug ID: 47932
Summary: Mouse-clicks no longer recognized `World of Warships`
Product: Wine-staging
Version: 4.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukas.lueg(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
`World of Warships 0.8.8` used to work more or less flawlessly in wine-4.16;
since the update to 4.17 left/right mouse clicks are no longer recognized at
all in the main menu (including login), rendering the application unusable.
The problem appeared since `wine-4.17-2" on x86_64, using Fedora 30.
Downgrading to 4.16 fixed the problem.
--
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.