https://bugs.winehq.org/show_bug.cgi?id=55639
Bug ID: 55639
Summary: OSS driver sends output to wrong device
Product: Wine
Version: 8.16
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineoss.drv
Assignee: wine-bugs(a)winehq.org
Reporter: sean-freebsd(a)farley.org
Created attachment 75175
--> https://bugs.winehq.org/attachment.cgi?id=75175
trace:oss of test sound using default device in winecfg
Sometime after Wine 8.11, the OSS driver sends to the device node one higher
than selected. Whether the "System Default" or the specific node device is
picked in winecfg, the "Test Sound" goes to one higher than chosen.
In my case, the speakers are on /dev/dsp4. In the log, that device is
considered the default devnode. However, the devnode chosen for output is
/dev/dsp5. If I chose /dev/dsp3 specifically, then the audio will be output
via the speakers.
It definitely looks like an off-by-one bug.
Workaround: select lower device by number
--
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=25872
Summary: dxdiag doesn't support /t option, needed by Guild Wars
'test system' button
Product: Wine
Version: 1.3.12
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
This is the next problem after bug 25871.
Guild wars installs nicely, but if you press 'test system', you see
...
fixme:dxdiag:ProcessCommandLine /t unimplemented
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=48264
Bug ID: 48264
Summary: WineHQ Debian repos are missing Wine 4.21
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: shtetldik(a)gmail.com
CC: dimesio(a)earthlink.net, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
WineHQ Debian repo (testing for example) is still at 4.20, even though 4.21
came out at the end of last month already:
https://dl.winehq.org/wine-builds/debian/dists/testing/main/binary-amd64/
--
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=54648
Bug ID: 54648
Summary: Call of Juarez needs "isnan" handling
Product: vkd3d
Version: 1.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0718:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0718:err:d3dcompiler:D3DCompile2 Shader log:
0718:err:d3dcompiler:D3DCompile2 <anonymous>:18:6: E5005: Function "isnan"
is not defined.
1.6-195-g2880be64
--
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=54660
Bug ID: 54660
Summary: Call of Juarez shows 'Assertion failed:
deref->offset_regset == HLSL_REGSET_NUMERIC'
Product: vkd3d
Version: 1.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC, file
../vkd3d/libs/vkd3d-shader/hlsl_codegen.c, line 3143
1.6-199-gda243570
--
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=46553
Bug ID: 46553
Summary: The Witcher: Enhanced Edition Director's Cut has
texture issue with builtin d3dx9_35
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 63424
--> https://bugs.winehq.org/attachment.cgi?id=63424
screenshot
Some objects have bright textures when player isn't near to them and look
normal when near.
Native library helps with this.
wine-4.0-230-g78a8445a2a
--
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=42026
Bug ID: 42026
Summary: Monkey Island 2: Special Edition crashes to a black
window on launch.
Product: Wine
Version: 2.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thedoogster(a)gmail.com
Distribution: ---
Created attachment 56488
--> https://bugs.winehq.org/attachment.cgi?id=56488
wine Monkey2 &> log.txt
When I use WINE to start Monkey Island 2: Special Edition (from GOG), the
screen turns black. Pressing ESC closes the game (with the full-screen, black
window), and I can see the attached output in my terminal.
I should be able to switch to another desktop and get a debug trace when the
black game window is on the screen, if you'd like me to do that.
I'm using 375.26 of NVidia's drivers. While I started having WINE issues
(including this one) after the driver upgrade, and I've recently had similar
issues with Shantae: Pirate's Curse (also from GOG), everything other than
WINE seems to be working fine.
--
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=48250
Bug ID: 48250
Summary: Mirror sync in progress for stable
Product: Wine
Version: 4.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chaskarisefthimios(a)gmail.com
Distribution: ---
https://forum.winehq.org/viewtopic.php?f=8&t=33242
--
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=32482
Bug #: 32482
Summary: Windows Sysinternals "PsInfo" tool fails to retrieve
"Physical Memory" value from
"HKLM\\Hardware\\ResourceMap\\System Resources"
registry key
Product: Wine
Version: 1.5.19
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
Windows Sysinternals "PsInfo" tool fails to query for some system properties...
Making this bug about "Physical Memory".
Output:
--- snip ---
$ wine ./PsInfo.exe
PsInfo v1.77 - Local and remote system information viewer
Copyright (C) 2001-2009 Mark Russinovich
Sysinternals - www.sysinternals.com
Querying information for nexus4...fixme:ole:CoInitializeSecurity
((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
System information for \\nexus4:
Uptime: Error reading uptime
Kernel version: Microsoft Windows XP, Uniprocessor Free
Product type: Professional
Product version: 5.1
Service pack: 3
Kernel build number: 2600
Registered organization:
Registered owner:
IE version: 6.0000
System root: C:\windows
Processors: 4
Processor speed: 2.6 GHz
Processor type: Intel(R) Pentium(R) 4 CPU
Physical memory: 0 MB
Video driver:
--- snip ---
Trace log (processor info = ok, physmem = missing):
--- snip ---
...
0024:Call advapi32.RegOpenKeyExW(80000002,0042f520
L"Hardware\\Description\\System\\CentralProcessor\\0",00000000,00020019,0032f96c)
ret=00404a33
0024:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=00404a33
0024:Call advapi32.RegQueryValueExW(00000054,0042f510
L"~MHz",00000000,0032f970,0043c0e4,0032f968) ret=00404a58
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a58
0024:Call advapi32.RegQueryValueExW(00000054,0042f4e8
L"ProcessorNameString",00000000,0032f970,0043d538,0032f968) ret=00404a81
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a81
0024:Call advapi32.RegCloseKey(00000054) ret=00404a95
0024:Ret advapi32.RegCloseKey() retval=00000000 ret=00404a95
0024:Call advapi32.RegOpenKeyW(80000002,0042f210
L"Hardware\\ResourceMap\\System Resources\\Physical Memory",0032f930)
ret=00403b17
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=00403b17
--- snip ---
Wineboot already creates a couple of hardware related registry keys:
Source:
http://source.winehq.org/git/wine.git/blob/7f9dfe273a80d31e3f8c5bd0c100c813…
Might be useful to add "Hardware\\ResourceMap\\System Resources" key here along
with actual physmem value.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=57202
Bug ID: 57202
Summary: steam client stops working on wine 8.19+ on Slackware
15.0 due to mono 8.10 update
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: steampunque8(a)gmail.com
Distribution: ---
Created attachment 77100
--> https://bugs.winehq.org/attachment.cgi?id=77100
last step of bisect for steam client launch failure
I recently tried to run steam client on upstream wines and found that the
client will not start on any wine version 8.19 or above. I bisected the
problem to the update to mono 8.1.0. The last stage of bisect is attached.
When starting the client a ton of processes get created and then "Maximum
number of clients reached" messages get spammed infinitely on the console.
OS: Linux 5.15.140 Dist: Slackware 15.0 64 CPU: 9900k GPU: RTX 4070
I found a workaround to the problem to shut off mono as follows:
export WINEDLLOVERRIDES="mscoree="
This workaround seems OK since I don't think steam client itself relies on mono
but I am not sure some of the apps it launches wont.
Any tips or ideas what might be happening here would be appreciated. No issues
with the older wine versions up to 8.18 ran steam with mono enabled fine so I
am pretty sure some update in mono 8.10 is triggering the problem. There is a
good chance this is related to Slackware 15.0 distribution and has nothing to
do with wine or mono issue but I don't know where to start looking for the
breakage.export WINEDLLOVERRIDES="mscoree="
--
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.