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

[Bug 36546] Please remove `tmpfs` special treatment in ntdll

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36546 --- Comment #8 from Bruno Jesus <00cpxxx(a)gmail.com> --- I can confirm that Futuremark SystemInfo will not install inside tmpfs drive, but it will in ramfs. AFAIK the difference between tmpfs and ramfs is that ramfs will grow if full while tmpfs will not. Is this enough for you to solve this bug? -- 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.

June 1, 2014

[Bug 36546] Please remove `tmpfs` special treatment in ntdll

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36546 --- Comment #7 from Henri Verbeet <hverbeet(a)gmail.com> --- (In reply to Artem S. Tashkinov from comment #6) > Again, some people may have their home dirs mounted as tmpfs. Are you saying > they are all screwed? I'm not really saying anything on the topic since it's not quite my area of expertise, I'm just trying to clarify the bug report. If you're just asking for my opinion, the current behaviour seems reasonable to me, but I don't have the kind of setup the bug report is about, so that's probably not worth much. -- 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.

June 1, 2014

[Bug 36630] Wizards Event Reporter fails on startup with .NET runtime reporting: 'Strong name validation failed. Exception from HRESULT: 0x8013141A'

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36630 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet, download URL| |http://webapp.wizards.com/D | |CIRUpdate/ReporterSetup.exe -- 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.

June 1, 2014

[Bug 36630] New: Wizards Event Reporter fails on startup with .NET runtime reporting: 'Strong name validation failed. Exception from HRESULT: 0x8013141A'

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36630 Bug ID: 36630 Summary: Wizards Event Reporter fails on startup with .NET runtime reporting: 'Strong name validation failed. Exception from HRESULT: 0x8013141A' Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, reported in WineHQ user forums here: http://forum.winehq.org/viewtopic.php?f=8&t=22329 Prerequisite: 'winetricks -q dotnet20sp1 jet40' --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Wizards of the Coast/Event Reporter $ wine ./Reporter.exe fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime 2.0 Error Reporting"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003e8,(nil),0x0008,0x000000f4,0x3009a1b4,0x69c610): stub err:eventlog:ReportEventW L"reporter.exe" err:eventlog:ReportEventW L"4.1.14.439" err:eventlog:ReportEventW L"537a1f52" err:eventlog:ReportEventW L"kernel32.dll" err:eventlog:ReportEventW L"5.1.2600.2180" err:eventlog:ReportEventW L"00000000" err:eventlog:ReportEventW L"0" err:eventlog:ReportEventW L"0002ac57" fixme:advapi:DeregisterEventSource (0xcafe4242) stub ... Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Reporter, Version=4.1.14.439, Culture=neutral, PublicKeyToken=f6187a2321850a68' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) File name: 'Reporter, Version=4.1.14.439, Culture=neutral, PublicKeyToken=f6187a2321850a68' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A) The Zone of the assembly that failed was: MyComputer wine: Unhandled exception 0xe0434f4d in thread 9 at address 0x7b83ac57 (thread 0009), starting debugger... --- snip --- Running 'sn.exe' (Strong Name-Tool) from .NET Framework 2.0 SDK ('winetricks -q dotnet20sdk') on the assembly also reports failure: --- snip --- $ wine "C:\Program Files\Microsoft.NET\SDK\v2.0\bin\sn.exe" -vf ./Reporter.exe Microsoft (R) .NET Framework Strong Name Utility Version 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. fixme:msvcrt:__clean_type_info_names_internal (0x60345090) stub Failed to verify assembly -- Strong name validation failed for assembly './Reporter.exe'. fixme:msvcrt:__clean_type_info_names_internal (0x7a38d5c8) stub --- snip --- Interestingly, registering the assembly for verification skipping is reported successful but verification is still done and fails in the end. --- snip --- $ wine "C:\Program Files\Microsoft.NET\SDK\v2.0\bin\sn.exe" -Vr ./Reporter.exe Microsoft (R) .NET Framework Strong Name Utility Version 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. Verification entry added for assembly 'Reporter,F6187A2321850A68' fixme:msvcrt:__clean_type_info_names_internal (0x7a38d5c8) stub --- snip --- $ sha1sum ReporterSetup.exe 36a15e8bf2c9d1a1501fe3fd0844f695750e198c ReporterSetup.exe $ du -sh ReporterSetup.exe 14M ReporterSetup.exe $ wine --version wine-1.7.19-70-gd6a59f7 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.

June 1, 2014

[Bug 36629] .NET Framework 4.0 fails to install

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36629 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet, download, Installer CC| |focht(a)gmx.net Summary|dotnet40 installation |.NET Framework 4.0 fails to |failed with many 'Exception |install |from HRESULT' | --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello dino, I can't reproduce this, the .NET Framework 4.0 install works fine (either by itself or 'winetricks' recipe). You're definitely not installing .NET 4.0 or installing in a broken WINEPREFIX as this should not happen: --- snip --- 06/01/2014 15:42:39.901 [318]: Assemblies to compile: 1 06/01/2014 15:42:39.989 [318]: Uninstalling assembly C:\windows\Microsoft.Net\Framework\v3.0\WPF\PresentationFontCache.exe because of an error during compilation: Exception from HRESULT: 0x80040155. --- snip --- Please follow the common rules for .NET Frameworks install. 1) clean 32-bit WINEPREFIX (important!) 2) winetricks recipe If it still fails, _attach_ complete terminal output. Again: use a new WINEPREFIX or the bug report is automatically invalid. 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.

June 1, 2014

[Bug 36629] dotnet40 installation failed with many 'Exception from HRESULT'

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36629 --- Comment #1 from dino <dyvazar(a)numericable.fr> --- Created attachment 48675 --> http://bugs.winehq.org/attachment.cgi?id=48675 dotnet40 install checking -- 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.

June 1, 2014

[Bug 36629] New: dotnet40 installation failed with many 'Exception from HRESULT'

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36629 Bug ID: 36629 Summary: dotnet40 installation failed with many 'Exception from HRESULT' Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dyvazar(a)numericable.fr >From a fresh wineprefix and latest winetricks 1196, i've tried again to do a dotnet40 installation. But there is a lot of errors when i check it. -- 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.

June 1, 2014

[Bug 33344] Grand Theft Auto: San Andreas v1.01 fails to offer 1366 x 768 (16:9) resolution in display setup

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=33344 --- Comment #6 from Dario Madeo <madeodario(a)gmail.com> --- Thank you Anastasius. This is my xranrd output: -- begin snip -- $ xrandr Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384 HDMI-0 disconnected primary (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 344mm x 193mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected -- end snip -- xrandr returns 1366x768. Anyway, this mode does not appear in the game. In particular, if I don't use windowed mode and the display is set to 1366x768, then the game enlists only 4:3 resolutions (640x480, 800x600 and 1024x768). If I use a windowed mode with an emulated desktop of 1366x768, the behavior is the same as before. Anyway, I confirm as you say that 1280x720 in windowed mode works (clearly, I must set the emulated desktop to 1280x720). The version of the game I'm using is 1.01 -- 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.

June 1, 2014

[Bug 36546] Please remove `tmpfs` special treatment in ntdll

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36546 --- Comment #6 from Artem S. Tashkinov <t.artem(a)mailcity.com> --- (In reply to Henri Verbeet from comment #5) > are you arguing that it shouldn't be needed? This. Again, some people may have their home dirs mounted as tmpfs. Are you saying they are all screwed? -- 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.

June 1, 2014

[Bug 34498] Garena Messager LAN button doesn't work ('garena_room.exe' helper keeps showing 'Auth in Main Server')

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=34498 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |focht(a)gmx.net Version|unspecified |1.7.1 Summary|Garena Lan button doesn't |Garena Messager LAN button |work |doesn't work | |('garena_room.exe' helper | |keeps showing 'Auth in Main | |Server') Ever confirmed|0 |1 --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello Josef, --- quote --- I think, this is duplicate of #34650 --- quote --- actually it's the other way around: you created a dupe - hence I merged it here. 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.

June 1, 2014