https://bugs.winehq.org/show_bug.cgi?id=45153
Bug ID: 45153
Summary: I keep getting an error that says my
"steamerrorreporter" has a critical issue, this is
what I see when I click on the "details" spot. What do
I do? (I am on a MacBook Pro running High Sierra)
Product: Wine
Version: 0.9-pre
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: penningtonbrittney(a)live.com
Created attachment 61341
--> https://bugs.winehq.org/attachment.cgi?id=61341
(backtrace)
I keep getting an error that says my "steamerrorreporter" has a critical issue,
this is what I see when I click on the "details" spot. What do I do? (I am on a
MacBook Pro running High Sierra)
--
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=45140
Bug ID: 45140
Summary: Mac OS X 10.13.4 warns on 32 bit apps; 10.14 will
likely deprecate 32 bit support
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
Assignee: wine-bugs(a)winehq.org
Reporter: pembertona(a)gmail.com
Distribution: ---
Created attachment 61327
--> https://bugs.winehq.org/attachment.cgi?id=61327
Mac 10.13.4 32-bit prompt
Sorry to file a non-specific bug, but I'm wondering if the Wine community is
aware Mac OS X 10.13.4, the current version, now prompts users when running 32
bit apps?
It is likely 10.14, which should launch September of 2018, will deprecate 32
bit app support altogether.
Is there a plan to focus on 64 bit support for Wine on Mac? Many features seem
buggy or untested. There's also a fair amount of Wine documentation (perhaps
old?) that state 64 bit Wine on Mac isn't supported (eg:
https://www.winehq.org/wwn/364#Wine64%20on%20Mac%20OS%20X).
--
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=45112
Bug ID: 45112
Summary: Winamp - Milkdrop complains
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
Clicking the visualisation tab displays a dialog:
MILKDROP ERROR
Error compiling ps_2_0 warp shader
:127:8:error: syntax error, unexpected KW_TEXTURE
Then you click OK and get another dialog
MILKDROP ERROR
Your hardware says that it supports shader model
3.0 [PSVersion==0x300],
but it doesn't seem to do it properly -
maybe your display is just buggy.
You might want to try updating your display driver
to the latest WHQL driver from the chipset
manufacturer
(NVIDIA, ATI, etc)
Googling for
wine winamp "ps_2_0 warp shader"
Shows the issue going back to at least 2010
Tested on AMD Radeon Vega 8 - on wine 3.7-staging
--
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=45076
Bug ID: 45076
Summary: The Fitbit OS 2.0 Simulator crash in wine 3 and ubuntu
18.04 64bit
Product: Wine
Version: 3.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stillpointx(a)gmail.com
Distribution: ---
Created attachment 61223
--> https://bugs.winehq.org/attachment.cgi?id=61223
Backtrace wine crash information
The Fitbit OS 2.0 Simulator crash in wine 3 and ubuntu 18.04 64bit
I'm trying to install Fitbit OS 2.0 Simulator to work. The program can be
found here
https://simulator-updates.fitbit.com/download-win
What it's suppose to look like can be found here but it crashes.
https://dev.fitbit.com/blog/2018-03-13-announcing-fitbit-os-2.0-and-simulat…
The crash / errors I get when I run it using the command
rttr@sys11: ~/.wine/drive_c/users/rt/Local Settings/Application
Data/Programs/@fitbitsimulator$ wine Fitbit\ OS\ Simulator.exe
Checking for update
Update for version 0.5.3 is not available (latest version: 0.5.3, downgrade is
disallowed.
wine: Unhandled exception 0x80000003 in thread 59 at address 0x20dd7cb (thread
0059), starting debugger...
--
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=45061
Bug ID: 45061
Summary: crash when running Battle.net-Setup.exe
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b1779506(a)trbvn.com
Distribution: ---
Created attachment 61192
--> https://bugs.winehq.org/attachment.cgi?id=61192
crash log wine battlenet
crash log
--
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=45056
Bug ID: 45056
Summary: cannot get into help topics
Product: Wine
Version: unspecified
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kdmmpm2017(a)gmail.com
selected Help menu. asked me to install wine gecko, brought up AceMoney Help in
gray and dumped.
--
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=45043
Bug ID: 45043
Summary: Icewind Dale 1 unplayable due to lag, possible
regression
Product: Wine
Version: 3.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ckoe_(a)web.de
Distribution: ---
Hello everybody,
I would like to report a problem with Icewind Dale 1 ("Classic" patchlevele
1.42 as distributed by GoG, not Beamdog EE). The Icewind Dale 1 is using the
widescreen mod. Game was perfectly playable with older wine versions, see below
for details and see also AppDB.
OS is Debian 9 (Stretch, stable) on Intel Haswell with IGP HD4400 graphics.
Wine has been upgraded to 3.6 from the packages available at winehq using
apt-get install --install-recommends winehq-devel. Game is set to 32 bit
graphics, setting it to 16 bit and using Software BLT does mot appear to make a
difference. The IWDs opengl rendering backend is always set to off in
icewind.ini and confirmed with the configuration program.
With wine 3.6 I observe severe lag in all menus as far as tested, e.g. starting
and loading a game. Screen build up is extremely slow, screen is black for
several seconds. Menu buttons update/ show a press after about 1 to 5 seconds,
also menu button clicks sounds lag. Mouse pointer lags and flickers. Actual
loading also takes minutes, I could not get beyond the end of the load screen
waiting several minutes for the game to finish loading the save, I killed it.
Starting screen movies (Black Isle animation) play fine, though.
Upon start I see in the terminal
# wine IDMain.exe
BEGIN LOGGING SESSION
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32a8e8,0x00000000), stub!
0009:fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1.
Later I see literally thousands (extreme high frequency logging) of messages
0034:fixme:dplay:DP_IF_Receive
(0x344c0a0)->(0x387fe30,0x387fe24,0x00000000,0x57f2970,0x387fe2c,1): stub
in my terminal.
I am reporting this against wine 3.6 as a possible regression because:
With wine 1.6: It worked without any problems in debian old-stable (jessie)
with wine 1.6 from the debian package.
With wine 1.8: I got it to work after much experimentation with debian stables
wine 1.8 package using ddr=gdi instead of ddr=opengl.
Remark: There are reports of crashes while saving when using IWDs experimental
opengl renderer backend.
I was instead observing a similar crash upon saving (clicking the Safe button,
apparently freezes when trying to render the slot selection screen) when using
wines d3d, i.e. opengl is off in icewind.ini. I see
err:d3d:init_driver_info No driver version info found for device 8086:0416,
driver model 0x2. ddr=gdi appears to change the d3d backend to something
working. This appears to have been fixed in later wine versions because:
With wine 3.0: In wine stable from winehq, i.e. 3.0, it just works with
defaults ! No ddr= settings or any fiddling required. Game is playable, no lag,
no crashes. I also see the
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32a8e8,0x00000000), stub!
0009:fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1.
0043:fixme:dplay:DP_IF_Receive
(0x337ba98)->(0x37bfe30,0x37bfe24,0x00000000,0xee9990,0x37bfe2c,1): stub
as mentioned above in the terminal.
With wine 3.6: In wine 3.6 it is unplayable as descibed above.
Please let me know what other debug information I might need to gather.
Best Regards
Christof
--
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=45041
Bug ID: 45041
Summary: eldorado 0.6 / halo online: missing a more than one
back buffer
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: romulasry(a)gmail.com
Distribution: ---
Created attachment 61170
--> https://bugs.winehq.org/attachment.cgi?id=61170
wine log
fixme:d3d:swapchain_init The application requested more than one back buffer
might be the issue with this app
--
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=45034
Bug ID: 45034
Summary: Hired Team: Trial Gold(2001) crashes with
setup_exception_record stack overflow
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spleefer90(a)gmail.com
Distribution: ---
Tested under Wine-devel 32/64bit and wine-staging 64 bit, result is the same
under all.
The Wine-devel 32 bit prefix was completely fresh.
I tried running this in a different TTY and launched the game from there. This
got rid of the BPP fixme but it still crashed.
xinit /usr/bin/xterm -- :1 -ac -depth 16
WINEPREFIX=~/wine/wine32 wine Shine.exe
0009:fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from
32 to 16
0009:err:seh:setup_exception_record stack overflow 1184 bytes in thread 0009
eip 7bc45116 esp 00230e90 stack 0x230000-0x231000-0x330000
The game uses DX7.0a/OpenGL(?).
If I can provide any other info, please do tell what's needed.
--
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=45020
Bug ID: 45020
Summary: Dead by Daylight (Steam): Crash after auto-save icon
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cheepayseal(a)protonmail.com
Distribution: ---
Created attachment 61142
--> https://bugs.winehq.org/attachment.cgi?id=61142
Backtrace of the bug.
After starting the game, it auto-saves right before loading the menu, but
crashes while doing that.
--
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.