I am attempting to run the game Hearthstone on my netbook via the latest version of wine from the PPA. However I am having an issue apparently with OpenGL, I get the following error message.
http://i.imgur.com/8nSuCye.png
At first I thought the issue might be due to my netbook having a very odd monitor resolution (1020x600) despite the window being larger than this, unfortunately plugging into my 24 inch monitor did not solve the problem.
The game runs fine under windows, if at little slow due to my lacklustre hardware, even running full screen at 1024x600 when the machine is not connected to my monitor.
However I try to avoid Windows as much as I can, so I would love to run it under Linux too, however I am coming up against this issue, and a google search seems to only find a single instance of another person having the same problem. People with very similar hardware to mine apparently can run the game fine under Linux....
My specs:
Item atom 1.6GHz
2GB of ram
Intel GMA 945 (latest drivers from intel)
Wine 1:1.7.15-0ubuntu1-saucy
apt-cache policy libgl1-mesa-dri libgl1-mesa-dri:i386 | grep -C1 Installed
Gives:
libgl1-mesa-dri:
Installed: 10.0.0-1ubuntu2
Candidate: 10.0.0-1ubuntu2
--
libgl1-mesa-dri:
Installed: 10.0.0-1ubuntu2
Candidate: 10.0.0-1ubuntu2
I am at a loss....any ideas?
Bizarre Hearthstone issue, possibly an OpenGL issue
Re: Bizarre Hearthstone issue, possibly an OpenGL issue
@Jeros,
Have you tried running the game in Virtual Desktop? If the game wants to mode switch into 1024x768 at some point (e.g. menus or intro videos) you may run into problems running it fullscreen (even on a secondary monitor)...
What console output do you get? (Please attach as a .tar file if it's long).
What's the output of the following terminal commands:
Thanks
Bob
Have you tried running the game in Virtual Desktop? If the game wants to mode switch into 1024x768 at some point (e.g. menus or intro videos) you may run into problems running it fullscreen (even on a secondary monitor)...
What console output do you get? (Please attach as a .tar file if it's long).
What's the output of the following terminal commands:
Code: Select all
glxinfo | grep '^[a-zA-Z]'
xrandrBob
Re: Bizarre Hearthstone issue, possibly an OpenGL issue
@Bob Wya
Thanks for the reply, yes I have attempted to run it in a virtual desktop at varying resolutions, I prefer to run all wine applications that way if I can.
My console output is the following:
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:system:SetProcessDPIAware stub!
Mono path[0] = 'C:/Program Files/Hearthstone/Hearthstone_Data/Managed'
Mono path[1] = 'C:/Program Files/Hearthstone/Hearthstone_Data/Mono'
Mono config path = 'C:/Program Files/Hearthstone/Hearthstone_Data/Mono/etc'
fixme:imm:ImmReleaseContext (0x10050, 0x1406e0): stub
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f778,0x00000000), stub!
fixme:d3d:wined3d_check_device_format_conversion wined3d 0x147ae0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32f578,0x00000000), stub!
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f478,0x00000000), stub!
fixme:dxgi:dxgi_output_GetDesc iface 0x148f80, desc 0x32fa1c stub!
fixme:wbemprox:client_security_SetBlanket 0xb7263330, 0x149020, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xb7263330
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f388,0x00000000), stub!
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0.
fixme:win:RegisterDeviceNotificationW (hwnd=0x10050, filter=0x32fc6c,flags=0x00000000) returns a fake device notification handle!
err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already !
err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already !
wine: Unhandled page fault on read access to 0x0264b870 at address 0x8c20e0 (thread 002e), starting debugger...
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x4314f0,symt:0x4dd7c8)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b204,symt:0x16ac71c)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b2b4,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b2b4,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x18ebafc,symt:(nil))
glxinfo | grep '^[a-zA-Z]' yields:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX version: 1.4
GLX extensions:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 10.0.0
OpenGL extensions:
xrandr yields:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767
LVDS1 connected (normal left inverted right x axis y axis)
1024x576 60.0 +
640x480 59.9
VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 520mm x 290mm
1920x1080 60.0*+
1600x1200 60.0
1680x1050 60.0
1400x1050 60.0
1280x1024 75.0 60.0
1440x900 59.9
1280x960 60.0
1152x864 75.0
1024x768 75.1 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 66.7 60.0
720x400 70.1
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Please note the above are with the external monitor plugged in which is pretty standard for my netbook, it is mostly used as a low powered desktop.
I have a working theory, however.
Hearthstone requires either DirectX 9 or OpenGL 2.0
My gfx chip does not support OpenGL 2.0 as far as I am aware (1.4 max) therefore the issue is that Hearthstone is not running using DirectX 9, however it IS installed, this was done via winetricks.
Hence it works under windows, as it just uses DirectX 9 without issue.
It would seem I need to find a way to force it to use DirectX 9.
Thanks for the reply, yes I have attempted to run it in a virtual desktop at varying resolutions, I prefer to run all wine applications that way if I can.
My console output is the following:
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:system:SetProcessDPIAware stub!
Mono path[0] = 'C:/Program Files/Hearthstone/Hearthstone_Data/Managed'
Mono path[1] = 'C:/Program Files/Hearthstone/Hearthstone_Data/Mono'
Mono config path = 'C:/Program Files/Hearthstone/Hearthstone_Data/Mono/etc'
fixme:imm:ImmReleaseContext (0x10050, 0x1406e0): stub
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f778,0x00000000), stub!
fixme:d3d:wined3d_check_device_format_conversion wined3d 0x147ae0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32f578,0x00000000), stub!
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f478,0x00000000), stub!
fixme:dxgi:dxgi_output_GetDesc iface 0x148f80, desc 0x32fa1c stub!
fixme:wbemprox:client_security_SetBlanket 0xb7263330, 0x149020, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xb7263330
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f388,0x00000000), stub!
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0.
fixme:win:RegisterDeviceNotificationW (hwnd=0x10050, filter=0x32fc6c,flags=0x00000000) returns a fake device notification handle!
err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already !
err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already !
wine: Unhandled page fault on read access to 0x0264b870 at address 0x8c20e0 (thread 002e), starting debugger...
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x4314f0,symt:0x4dd7c8)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b204,symt:0x16ac71c)
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b2b4,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x137b2b4,symt:(nil))
fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x33c37c,L"libc.so.6"), for debug_info(abbrev:0x18ebafc,symt:(nil))
glxinfo | grep '^[a-zA-Z]' yields:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX version: 1.4
GLX extensions:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 10.0.0
OpenGL extensions:
xrandr yields:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767
LVDS1 connected (normal left inverted right x axis y axis)
1024x576 60.0 +
640x480 59.9
VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 520mm x 290mm
1920x1080 60.0*+
1600x1200 60.0
1680x1050 60.0
1400x1050 60.0
1280x1024 75.0 60.0
1440x900 59.9
1280x960 60.0
1152x864 75.0
1024x768 75.1 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 66.7 60.0
720x400 70.1
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Please note the above are with the external monitor plugged in which is pretty standard for my netbook, it is mostly used as a low powered desktop.
I have a working theory, however.
Hearthstone requires either DirectX 9 or OpenGL 2.0
My gfx chip does not support OpenGL 2.0 as far as I am aware (1.4 max) therefore the issue is that Hearthstone is not running using DirectX 9, however it IS installed, this was done via winetricks.
Hence it works under windows, as it just uses DirectX 9 without issue.
It would seem I need to find a way to force it to use DirectX 9.
Re: Bizarre Hearthstone issue, possibly an OpenGL issue
@Jeros,Jeros wrote: glxinfo | grep '^[a-zA-Z]' yields:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX version: 1.4
GLX extensions:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 10.0.0
OpenGL extensions:
Hearthstone requires either DirectX 9 or OpenGL 2.0
My gfx chip does not support OpenGL 2.0 as far as I am aware (1.4 max) therefore the issue is that Hearthstone is not running using DirectX 9, however it IS installed, this was done via winetricks.
Hence it works under windows, as it just uses DirectX 9 without issue.
It would seem I need to find a way to force it to use DirectX 9.
Ahh your theory is right! That's what I was asking for your OpenGL support information. You must understand that you can't install the "DirectX layer" in Wine. Your underlying system is still Linux. So Wine will always intercept DirectX Draw calls and translate them to the equivalent OpenGL. This is why it is recommended to Wine's builtin DirectX translation layer - rather than install the install any additional MS DirectX libraries - as they can intefer with each others operation.
If you look at the code for how Wine is implemented - it is largely a layer of "fake .dlls". These dynamic link libraries provide most of the Win32 API - Windows applications would expect to be able to access. However, in the Wine code all these calls are redirected to the native Linux/MacOS/FreeBSD networking stack, filesystem, OpenGL layer, audio layer, etc.
So in summary it looks unlikely you'll get your application running without more modern graphics support. I don't beleve your chipset is a development priority - so it's unlikely the full OpenGL 2.0 specification will ever be implmented (if this is even possible). I do believe that Mesa has a nasty habit of "over advertising" what featureset it has - which can cause Wine applications to try to run - without a meaning error/feedback...
Bob
