A recent patch to DDO makes the game crash whenever the in-game store is opened (this is an interface which runs though an in-game web browser). The crashing has been attributed by the developers to Awesomium no longer supporting older versions of Windows - Windows XP users are suffering from the same problem as WINE users here - and specifically to a "lack of specific system and security updates that Windows XP no longer receives."
Is there anything that I can do to address this? It kinda sounds like it's just an expired certificate. Is that something that I can update manually?
Awesomium causing some problem (Dungeons and Dragons Online)
Re: Awesomium causing some problem (Dungeons and Dragons Onl
Wine uses the certificates on the host system, so assuming you've kept those up-to-date, that shouldn't be the problem. However, there have been issues with some sites (notably EA Origin) whose certificates have been removed from most distro bundles because they are not secure. https://bugs.winehq.org/show_bug.cgi?id=35828
You didn't mention your Wine version. If it's not the latest development release, upgrade. If the problem is present in 1.9.4 or later, post terminal output.
You didn't mention your Wine version. If it's not the latest development release, upgrade. If the problem is present in 1.9.4 or later, post terminal output.
Re: Awesomium causing some problem (Dungeons and Dragons Onl
Okay, I have upgraded to 1.9.4 and nothing's changed. The terminal output is lots of lots of the same two lines, followed by:
That doesn't seem very helpful though... I think the output might be more informative if I could get it to stop displaying the two input stream lines - is there a way to do that?
There was also a line:fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_TANGENT, usage_idx=0].
fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_BINORMAL, usage_idx=0].
fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_TANGENT, usage_idx=0].
fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_BINORMAL, usage_idx=0].
fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_TANGENT, usage_idx=0].
fixme:d3d:fixed_get_input Unsupported input stream [usage=WINED3D_DECL_USAGE_BINORMAL, usage_idx=0].
fixme:advapi:UnregisterTraceGuids deadbeef: stub
fixme:advapi:UnregisterTraceGuids deadbeef: stub
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
But I think I resolved that one by installing winbind, as it suggests. No change.err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
That doesn't seem very helpful though... I think the output might be more informative if I could get it to stop displaying the two input stream lines - is there a way to do that?
Re: Awesomium causing some problem (Dungeons and Dragons Onl
There's no crash in the terminal output you posted. If it crashed, you should have gotten Wine's popup crash dialog, which has an option to save the backtrace.
This can cause crashes. https://wiki.winehq.org/FAQ#Broken_NVID ... _RandR_1.0Code: Select all
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
Re: Awesomium causing some problem (Dungeons and Dragons Onl
It's likely that there's no crash given in the terminal because it's just the game window that crashes, the game launcher process is still running after the crash and I have to kill it manually. It's still consuming a lot of cpu time at that point, and it continues to do so even if I leave it running for a good while... don't know what it's doing.
I don't think the NVIDIA RandR thing is the problem here - I run DDO in a window, not full screen, so there's no resolution change. I did try the fix though and it gave me an error saying that putting a line starting with "Option" in xorg.conf is not allowed. Don't know what's up with that, but I'm pretty confident that it's a side issue which is unrelated to this one.
Is there no way to silence the "Unsupported input stream" lines? I think the terminal output will be more useful if I can do that.
I don't think the NVIDIA RandR thing is the problem here - I run DDO in a window, not full screen, so there's no resolution change. I did try the fix though and it gave me an error saying that putting a line starting with "Option" in xorg.conf is not allowed. Don't know what's up with that, but I'm pretty confident that it's a side issue which is unrelated to this one.
Is there no way to silence the "Unsupported input stream" lines? I think the terminal output will be more useful if I can do that.