April 2014 - Wine-Bugs - list.winehq.org

[Bug 35748] Blazing Angels 2: cannot initialize 3D engine

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35748 --- Comment #3 from Bruno Jesus <00cpxxx(a)gmail.com> --- Maybe the game resorts to the debug dll when something wrong happens. There are issues in W2K too: http://win2kgaming.prophpbb.com/topic684.html#p2368 -- 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.

April 30, 2014

[Bug 18614] Problem with starting of wine or winecfg

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=18614 --- Comment #47 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Frédéric Delanoy from comment #46) > (In reply to Steve Dawson from comment #45) > > (In reply to Frédéric Delanoy from comment #44) > > > Is this still an issue in latest wine (1.7.17 or later)? > > > > I haven't seen this issue since my post on 07/2012, I don't believe it was a > > wine problem, more likely an issue with gcc compiling 32 bit code on x86_64. > > > > I am currently running 1.7.17. > > > > Regards > > > > Steve. > > Assumed fixed. I'd say worksforme since he is not the original reporter and also he said the problem was probably not 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.

April 30, 2014

[Bug 18614] Problem with starting of wine or winecfg

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=18614 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #46 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- (In reply to Steve Dawson from comment #45) > (In reply to Frédéric Delanoy from comment #44) > > Is this still an issue in latest wine (1.7.17 or later)? > > I haven't seen this issue since my post on 07/2012, I don't believe it was a > wine problem, more likely an issue with gcc compiling 32 bit code on x86_64. > > I am currently running 1.7.17. > > Regards > > Steve. Assumed fixed. -- 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.

April 30, 2014

[Bug 35748] Blazing Angels 2: cannot initialize 3D engine

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35748 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, --- snip --- fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.DebugCRT" (8.0.50608.0) err:module:import_dll Library MSVCR80D.dll (which is needed by L"C:\\Program Files\\Ubisoft\\Blazing Angels 2 Secret Missions of WWII\\Bin\\restore.exe") not found --- snip --- If the game executables really bind to the debug version of the VC++ runtime this would be a serious accident on the developer or publisher side. There is a rule: you don't ship apps/games linked to the debug version of the VC++ runtime. These dlls are non-redistributable, they are part of Visual Studio installation. You don't expect people wanting to play a game installing Visual Studio. Not a Wine bug. Complain to whoever developed/published that product. Regards -- 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.

April 30, 2014

[Bug 36176] winecfg hangs when trying to add override for dbghelp

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36176 --- Comment #2 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- Oddly enough I only get it when I type the exact "dbghelp" word in it. Now I retried a couple of times and it doesn't occur anymore (I got the warning popup). Maybe the warning popup wasn't visible but somehow active? Anyway I'll leave this bug open for the time being so I can see if some people can reproduce. I'll also retest regularly and check if it happens again (and close this bug if not). -- 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.

April 30, 2014

[Bug 35748] Blazing Angels 2: cannot initialize 3D engine

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35748 Jarkko K <jarkko_korpi(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi(a)hotmail.com --- Comment #1 from Jarkko K <jarkko_korpi(a)hotmail.com> --- "err:module:import_dll Library MSVCR80D.dll (which is needed by L"C:\\Program Files\\Ubisoft\\Blazing Angels 2 Secret Missions of WWII\\Bin\\restore.exe") not found" Have you tried adding msvcr80.dll ? -- 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.

April 30, 2014

[Bug 36159] Google-Earth: no search results and no itinerary displayed

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36159 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Are you sure the cause of both is the same? If not then these are separate issues and need separate bug reports. You could try "winetricks msxml3" as a workaround. -- 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.

April 30, 2014

[Bug 34239] MicroStation V8i SELECTseries 2: rendering problems (Direct3D 9)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=34239 --- Comment #13 from Pekka Helenius <fincer89(a)hotmail.com> --- D3D_surface debugging ------------------------ d3d_surface part debugging output, performed with Intel HD 4600 Graphics + Nouveau drivers + default Linux Mint 16 OS. Wine 1.7.17, 32-bit prefix. Because log file is more than 1000kb, I uploaded it to Zippyshare. Link: http://www34.zippyshare.com/d/3054676/51284/microstationv8i_d3d_surface_win… -- 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.

April 30, 2014

[Bug 18614] Problem with starting of wine or winecfg

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=18614 --- Comment #45 from Steve Dawson <sdawson(a)pa.metrocast.net> --- (In reply to Frédéric Delanoy from comment #44) > Is this still an issue in latest wine (1.7.17 or later)? I haven't seen this issue since my post on 07/2012, I don't believe it was a wine problem, more likely an issue with gcc compiling 32 bit code on x86_64. I am currently running 1.7.17. Regards Steve. -- 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.

April 30, 2014

[Bug 34239] MicroStation V8i SELECTseries 2: rendering problems (Direct3D 9)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=34239 --- Comment #12 from Pekka Helenius <fincer89(a)hotmail.com> --- Created attachment 48317 --> http://bugs.winehq.org/attachment.cgi?id=48317 Microstation V8i rendering problems - WINEDEBUG=+d3dhader,-win,-nls (Wine 1.7.17 with Intel HD 4600 graphics) Some additional notes: I dug this problem a little bit more. The earlier test I submitted while ago was made using fglrx drivers with AMD Radeon 7970 graphics card (Ubuntu 13.10, 32-bit prefix). I decided to test the bug also with my laptop, equipped with Intel HD 4600 graphics card. This card could manage the d3d_shader line 6162 call allright (Nouveau + default Linux Mint 16 settings). d3d_shader part wasn't problematic after all. However, with this Intel card, d3d_surface throwed fixme messages all the way to the terminal output so I decided to debug it. The issue is equal to the end user but there seems to be differences depending on your graphics card and drivers you use, however. D3D_shader part with Intel HD 4600 as an attachment. -- 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.

April 30, 2014