April 2018 - Wine-bugs - list.winehq.org

[Bug 45013] New: Wine 3.6 Androidx86 8.12 missing in Wine wizzard for change Wine desktop resolution , its tiny..
by wine-bugs＠winehq.org 18 Apr '18

18 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=45013 Bug ID: 45013 Summary: Wine 3.6 Androidx86 8.12 missing in Wine wizzard for change Wine desktop resolution, its tiny.. Product: Wine Version: 3.6 Hardware: x86 OS: Android Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ruthan(a)email.cz Wine on Androidx86 is using some, very small resolution - 800x600, i thing, some windows parts are out of the screen - because are too big and there is not option to change it to something bigger or native screen resolution. -- 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.

1 1

[Bug 3260] StarForce 3.x: games crash or fail to start due to missing kernel driver infrastructure [metabug]
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=3260 --- Comment #68 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- I think it would be a good idea to close this bug now. Multiple specific Starforce bugs have been created recently and IMO it would be a good idea to follow that trend. -- 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.

1 0

[Bug 45003] New: Wine 3.6 on Android x86, maximize button or ALT+TAB etc, not working is not possible to enlarge game without
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=45003 Bug ID: 45003 Summary: Wine 3.6 on Android x86, maximize button or ALT+TAB etc, not working is not possible to enlarge game without Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ruthan(a)email.cz Distribution: --- Tested on multiple machines, only few games now working on Wine on Android and even them are almost uplayble because Wine internal esolution limitation - usualy 800x600 or 1024x768 what sucks on 1080p screen.. There are running in windom mode and maximize button or alt+tab option are not working. Tested on Quake - Steam, Hexen 2 demo - software, Unreal Tournament 99 demo - its running in safe mode with software renderer. -- 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.

1 5

[Bug 44987] New: Civilization V crashes on startup
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=44987 Bug ID: 44987 Summary: Civilization V crashes on startup 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: christophercormier(a)protonmail.com Distribution: --- Created attachment 61121 --> https://bugs.winehq.org/attachment.cgi?id=61121 Backtrace from running the game in DirectX 9 mode When launching Civilization V in DirectX 9 mode on a clean 32-bit Wine prefix, it immediately crashes with a program error of "The program CivilizationV.exe has encountered a serious problem and needs to close." The launcher does work, as it allows me to choose between DirectX 9 and DirectX 11. Neither DX9 or DX11 launch and both cause the same error. This is a regression since, if I roll back the Wine version to 2.19, it works without any issues in DX9 mode. It also previously would open a window for DX11 before crashing, but now it does not even get that far. I'm testing this on Kubuntu 17.10, with a GTX 960 graphics card using the binary NVIDIA driver. This issue persists in both regular Wine 3.6 and Wine 3.6-staging, and with the multi-threaded command stream both enabled and disabled. The backtrace for both the DX9 and DX11 versions have been attached -- 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.

1 4

[Bug 44992] New: Setting dpi in winecfg has no effect on application
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=44992 Bug ID: 44992 Summary: Setting dpi in winecfg has no effect on application 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: gordon1drake(a)yahoo.com Distribution: --- I am using a "low" resolution monitor set at 1280x1024 and I have been setting the dpi in winecfg to 128 otherwise the fonts are too small. With version 3.6, however, the application still looks like it is set at 96 and changing the value in winecfg has no effect. The application is called Scrivener and it does have the ability to set the font and size of the menu and other panes. It also has the ability to zoom on the editor pane. Unfortunately, it now has to be set much higher than usual. It should be noted that winecfg, task manager, etc do change. There was an instance when the font did not change in these but I can't reproduce. It may have happened when trying to upgrade an existing wineprefix. -- 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.

1 3

[Bug 44996] New: Enhancement requests related to Winetricks and Wine
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=44996 Bug ID: 44996 Summary: Enhancement requests related to Winetricks and Wine Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ricky.tigg(a)gmail.com Distribution: --- Created attachment 61128 --> https://bugs.winehq.org/attachment.cgi?id=61128 Snaphots related to designs and fonts sizes 1. As noticeable GUI messages associated to the launch of Winetricks are not displayed properly as expected in any user-friendly designs (winetricks_error.png, winetricks_One-time question about helping Winetricks development.png, winetricks_Information.png). 2. With no exception in all windows associated to Wine, fonts' sizes are not applied according to the size currently in use on Linux system, especially the one which applies to interfaces (here set to Cantarell Regular 11). Window title is Cantarell Bold 11. Wine persists to apply its own size set to interfaces (probably size 7–8) regardless system set font sizes (Wine configuration.png). For comparison system fonts apply normally to windows related Wineprefix itself (Winetricks - current prefix is "-home-yk-.wine"_006.png). For convenience I opened the Wine windows from Winetricks | Select the default Wineprefix. Tested on Fedora desktop using components: winetricks.noarch 20180217-1.fc28 @updates-testing wine.x86_64 3.5-1.fc28 @updates-testing -- 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.

1 1

[Bugzilla] Account Lock-Out: shadow@umbrox.de ( p54936861.dip0.t-ipconnect.de (84.147.104.97))
by wine-bugs＠winehq.org 17 Apr '18

17 Apr '18

The address p54936861.dip0.t-ipconnect.de (84.147.104.97) failed too many login attempts (5) for the account shadow(a)umbrox.de. The login attempts occurred at these times: 2018-04-16 20:52:11 CDT 2018-04-16 20:52:27 CDT 2018-04-16 20:52:34 CDT 2018-04-16 20:52:53 CDT 2018-04-16 20:53:07 CDT This IP will be able to log in again using this account at 2018-04-16 21:22 CDT.

1 0

[Bug 4405] combo box text not selected when getting the focus
by wine-bugs＠winehq.org 16 Apr '18

16 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=4405 --- Comment #17 from rebe(a)gmx.net --- Still with wine 3.6 > These 2 patches were not merged > as Dmitry Timoshkov pointed some issues with it back in January. https://www.winehq.org/pipermail/wine-devel/2016-January/111425.html https://www.winehq.org/pipermail/wine-devel/2016-January/111427.html https://www.winehq.org/pipermail/wine-devel/2016-January/111430.html The suggestion is to implement something else missing first and mostly related to testing. -- 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.

1 0

[Bug 37356] New: Multiple software protection/DRM schemes need ntoskrnl 'IoGetDeviceObjectPointer' implementation (Tages v5.x, ProtectDISC 6.x)
by wine-bugs＠winehq.org 16 Apr '18

16 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=37356 Bug ID: 37356 Summary: Multiple software protection/DRM schemes need ntoskrnl 'IoGetDeviceObjectPointer' implementation (Tages v5.x, ProtectDISC 6.x) Product: Wine Version: 1.7.27 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, split off from bug 9484 and also mentioned here: https://github.com/compholio/wine-compholio/issues/80 Can be reproduced with Tagès drivers version 5.x alone (two stacked/layered drivers). Also needed for other DRM schemes, such as ProtectDISC 6.x --- snip --- ... 0016:Call KERNEL32.CreateProcessW(00000000,00119fa8 L"C:\\windows\\system32\\winedevice.exe lirsgt",00000000,00000000,00000000,00000400,00540000,00000000,0084e4c8,0084e50c) ret=7edb5d3f ... 0038:Call KERNEL32.__wine_kernel_init() ret=7bc5a00d 0016:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7edb5d3f ... 003c:Starting thread proc 0x7ed9b77b (arg=0x119670) ... 003c:Call advapi32.RegisterServiceCtrlHandlerExW(001152aa L"lirsgt",7edfc61f,00000000) ret=7edfc86c 003c:Ret advapi32.RegisterServiceCtrlHandlerExW() retval=0011a968 ret=7edfc86c ... 0009:Call KERNEL32.CreateFileW(0033c4d0 L"\\\\.\\lirsgt",c0000000,00000000,00000000,00000003,40000000,00000000) ret=0040108f ... 0009:Ret KERNEL32.CreateFileW() retval=00000064 ret=0040108f ... 0009:Call KERNEL32.DeviceIoControl(00000064,0022e013,0033c6fc,00000000,0033c6fc,00000000,0033c6f8,00000000) ret=00401ac3 ... 003c:Call driver dispatch 0x542140 (device=0x11aeb0,irp=0x53e780) 003c:Call ntoskrnl.exe.IoAllocateMdl(0011b4c0,00000005,00000000,00000000,00000000) ret=005416bd 003c:Call ntdll.RtlAllocateHeap(00110000,00000008,00000020) ret=7ed2eb34 003c:Ret ntdll.RtlAllocateHeap() retval=0011b0e0 ret=7ed2eb34 003c:fixme:ntoskrnl:IoGetCurrentProcess () stub 003c:Ret ntoskrnl.exe.IoAllocateMdl() retval=0011b0e0 ret=005416bd 003c:Call ntoskrnl.exe.MmProbeAndLockPages(0011b0e0,00000001,00000001) ret=005416d9 003c:fixme:ntoskrnl:MmProbeAndLockPages (0x11b0e0, 1, 1): stub 003c:Ret ntoskrnl.exe.MmProbeAndLockPages() retval=0000003f ret=005416d9 003c:Call ntoskrnl.exe.MmMapLockedPagesSpecifyCache(0011b0e0,00000000,00000001,00000000,00000000,00000020) ret=005429c4 003c:fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x11b0e0, 0, 1, (nil), 0, 32): stub 003c:Ret ntoskrnl.exe.MmMapLockedPagesSpecifyCache() retval=00000000 ret=005429c4 003c:Call ntdll.RtlInitUnicodeString(0053e640,0053e648 L"\\Device\\atksgt") ret=00540387 003c:Ret ntdll.RtlInitUnicodeString() retval=0053e640 ret=00540387 003c:Call ntoskrnl.exe.IoGetDeviceObjectPointer(0053e640,00020000,0053e63c,0053e638) ret=005403a1 003c:fixme:ntoskrnl:IoGetDeviceObjectPointer stub: L"\\Device\\atksgt" 20000 0x53e63c 0x53e638 003c:Ret ntoskrnl.exe.IoGetDeviceObjectPointer() retval=c0000002 ret=005403a1 003c:trace:seh:raise_exception code=c0000005 flags=0 addr=0x5403c1 ip=005403c1 tid=003c 003c:trace:seh:raise_exception info[0]=00000001 003c:trace:seh:raise_exception info[1]=00000000 003c:trace:seh:raise_exception eax=00000000 ebx=7ed47000 ecx=0053e640 edx=0053ef8c esi=0011af68 edi=0053e944 003c:trace:seh:raise_exception ebp=00000000 esp=0053e638 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010282 003c:trace:seh:call_vectored_handlers calling handler at 0x7ed2d73c code=c0000005 flags=0 003c:trace:seh:call_vectored_handlers handler at 0x7ed2d73c returned 0 003c:trace:seh:call_stack_handlers calling handler at 0x7bc9de37 code=c0000005 flags=0 003c:Call KERNEL32.UnhandledExceptionFilter(0053e104) ret=7bc9de71 wine: Unhandled page fault on write access to 0x00000000 at address 0x5403c1 (thread 003c), starting debugger... ... --- snip --- $ sha1sum TagesSetup.exe b360bfc82b0c807c1caa7e423dfa4bc6515830a9 TagesSetup.exe $ du -sh TagesSetup.exe 204K TagesSetup.exe $ wine --version wine-1.7.27-113-g5afbb6b 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.

1 9

[Bug 41265] New: Far Cry 1: game crashes when using mouse wheel
by wine-bugs＠winehq.org 15 Apr '18

15 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=41265 Bug ID: 41265 Summary: Far Cry 1: game crashes when using mouse wheel Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: DanBrake0819(a)freenet.de Distribution: --- Created attachment 55565 --> https://bugs.winehq.org/attachment.cgi?id=55565 logfile Far Cry 1.4 (and unofficial 1.5 patch) crashes when using the mouse wheel. It happens in the latest Wine version (1.9.18). I also tested the latest stable version (1.8.4) and an older stable version (1.6.2)... the same thing: crash when using the mouse wheel. -- 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.

1 14