wine-bugs January 2022

1 participants
3414 discussions

[Bug 48565] New: When entering fullscreen at lower resolution than the desktop, scrollable virtual desktop is accessible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48565 Bug ID: 48565 Summary: When entering fullscreen at lower resolution than the desktop, scrollable virtual desktop is accessible Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmayr.dev(a)gmail.com Distribution: --- I tried playing a DirectX-based game, e.g. GTAIV, using the emulated virtual desktop at 800x600 (my desktop's native resolution is 1440x900). But ever since I changed back to playing the game fullscreen at 800x600 *without the virtual desktop*, the following happens: - The game starts at the desired lower resolution - Part of my desktop environment's panel is visible within the game's viewport, at that same lower resolution - If I move the mouse far enough, I realize that there's an active 1440x900 virtual desktop, showing me a lo-res 800x600 window - I can scroll around the edges of this virtual desktop, thus Wine losing the captured mouse cursor - When playing, this moves the centered game view past the center of the screen, losing focus; this prevents the mouse cursor's movements to be confined within the fullscreen window, which is supposed to be the an immovable viewport. I haven't found a way to revert back from having tried the virtual desktop option, as the change has been somehow been made permanent. -- 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.

14 hours, 15 minutes

[Bug 51373] New: Videos from Super Seducer won't work anymore

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51373 Bug ID: 51373 Summary: Videos from Super Seducer won't work anymore Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chaosstare(a)live.fr Distribution: --- Hi, On Wine 6.0, I could play / see the videos while playing Super Seducer 1 / 2 (didn't try the third episode), it's not longer the case with Wine 6.0.1 or later. Nicolas -- 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.

14 hours, 18 minutes

[Bug 50547] New: Freezes at Fallout2-based games

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50547 Bug ID: 50547 Summary: Freezes at Fallout2-based games Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexyecu(a)gmail.com Distribution: --- Fallout2 engine based games (like Fallout Sonora) freezes for 1 — 2 seconds every 10 or 15 minutes with Wine 6.0 rc6. Wine 5.5 works fine. Fedora 32 with last updates, nvidia, alsa, secondary X-server. -- 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.

14 hours, 19 minutes

[Bug 45244] New: MapleStory: screen freezes with certain audio files

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45244 Bug ID: 45244 Summary: MapleStory: screen freezes with certain audio files Product: Wine Version: 3.8 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alpha.s3r(a)gmail.com Created attachment 61485 --> https://bugs.winehq.org/attachment.cgi?id=61485 Trimmed bug report. Frame Sync failed repeated indefinitely (but file size was 125 MB), so I erased most of those lines. Wine screen freezes when playing certain audio files. It seems to be either non-MPEG2 files or audio files that don't conform to 24k bps or 22050 Hz (any audio under this classification seems to be fine). The specific audio file that was used to replicate the crash was: MPEG 2.5 / 8k bps / 8000 Hz. I've tested out other Wine versions, and Wine Stable 3.0 has the same error, along Wine Staging 3.6, 3.7, 3.8. However, if you use Wine 2.22 or Wine 1.4.1, the app runs fine and doesn't freeze at these sound effects. -- 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.

14 hours, 21 minutes

[Bug 47893] New: Unicode characters aren't being rendered correctly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47893 Bug ID: 47893 Summary: Unicode characters aren't being rendered correctly Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: huupoke12(a)gmail.com Distribution: --- This is probably a regression since I didn't run into this issue before. Unicode characters aren't being rendered correctly. Examples: https://appdb.winehq.org/commentview.php?iAppId=9581&iVersionId=28025&iThre… https://appdb.winehq.org/objectManager.php?sClass=application&iId=2586 -- 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 day

[Bug 50553] New: SetEnvironmentVariableW function sets last error on deleting non-existent variable

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50553 Bug ID: 50553 Summary: SetEnvironmentVariableW function sets last error on deleting non-existent variable Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: topin89(a)mail.ru Distribution: --- This code ``` //gcc test.c -o test.exe && ./test.exe #include <windows.h> #include <stdio.h> int main(int argc, char *argv[]){ BOOL result; result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", "SomeValue"); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); return 0; } ``` compiled with Mingw-w64 gcc and running from command line and MSYS console gives this in Windows 10: ``` result: 1, last error: 0 result: 1, last error: 0 result: 1, last error: 0 result: 1, last error: 0 ``` and this in Kubuntu 20.04.1 with winehq-staging 6.0: ``` <snip fixmes> result: 0, last error: 203 result: 1, last error: 0 result: 1, last error: 0 result: 0, last error: 203 ``` Error 203 is ERROR_ENVVAR_NOT_FOUND, btw. So, in Win 10 deleting already deleted environmental variable doesn't lead to error, in Wine it is. This alone prevents git.exe (and probably many more apps) to work correctly. In file git-for-windows-repo/compat/mingw.c there is this function, ``` int mingw_putenv(const char *namevalue) { int size; wchar_t *wide, *equal; BOOL result; if (!namevalue || !*namevalue) return 0; size = strlen(namevalue) * 2 + 1; wide = calloc(size, sizeof(wchar_t)); if (!wide) die("Out of memory, (tried to allocate %u wchar_t's)", size); xutftowcs(wide, namevalue, size); equal = wcschr(wide, L'='); if (!equal) result = SetEnvironmentVariableW(wide, NULL); else { *equal = L'\0'; result = SetEnvironmentVariableW(wide, equal + 1); } free(wide); if (!result) errno = err_win_to_posix(GetLastError()); return result ? 0 : -1; } ``` This line : ``` result = SetEnvironmentVariableW(wide, NULL); ``` sets error on removing non-existent `PERL5LIB` and that leads to result == 0 which in turn leads to premature exit in `err_win_to_posix(GetLastError())`. In this particular case, for some reason last error sets to 0 instead of 203. Another bug probably, I'll report it later. -- 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 day

[Bug 38923] New: Unity editor eror [32x with 32x wine]

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=38923 Bug ID: 38923 Summary: Unity editor eror [32x with 32x wine] Product: Wine Version: 20050930 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: free9988771(a)gmail.com Distribution: --- Created attachment 51853 --> https://bugs.winehq.org/attachment.cgi?id=51853 unity editor eror [07/15/15 13:06:45] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. [07/15/15 13:07:31] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) [07/15/15 13:08:01] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. [07/15/15 13:52:29] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred [07/15/15 13:59:00] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) [07/15/15 13:59:01] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. [07/15/15 13:59:19] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. [07/15/15 14:07:12] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. [07/15/15 14:08:12] - Running wine-1.7.47 Unity.exe (Working directory : /home/toghrul/.PlayOnLinux/wineprefix/Unity3new/drive_c/Program Files/Unity/Editor) fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} 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. fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wbemprox:client_security_SetBlanket 0xf71feabc, 0x158ff0, 10, 0, (null), 3, 3, (nil), 0x00000000 fixme:wbemprox:client_security_Release 0xf71feabc fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030 fixme:win:DisableProcessWindowsGhosting : stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:imm:ImmDisableTextFrameService Stub fixme:thread:GetThreadPreferredUILanguages 56, 0xe7fe508, (nil) 0xe7fe50c fixme:winsock:WSALookupServiceBeginW (0xe7fe3dc 0x00000ff0 0xe7fe418) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0xe7fe544, overlapped 0x67a1e48): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x10062, filter=0xe7fe550,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x10062, filter=0xe7fe550,flags=0x00000000) returns a fake device notification handle! fixme:ver:GetCurrentPackageId (0xd02ea08 (nil)): stub fixme:win:EnumDisplayDevicesW ((null),0,0xe7fdeb0,0x00000000), stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:wtsapi:WTSRegisterSessionNotification Stub 0x2004e 0x00000000 fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (0x15a4d8)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 0xe7fe290) fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:advapi:RegisterTraceGuidsW (0x352a270, 0x57eea98, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x57b6354, (null), (null), 0x57eeab0): stub fixme:advapi:RegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} 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. fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:advapi:RegisterTraceGuidsW (0x1013a270, 0x123fea98, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x123c6354, (null), (null), 0x123feab0): stub fixme:advapi:RegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} fixme:gdi:GdiInitializeLanguagePack stub fixme:module:load_library unsupported flag(s) used (flags: 0x00000800) fixme:ver:GetCurrentPackageId (0x292ea08 (nil)): stub fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0x2004e fixme:win:EnumDisplayDevicesW ((null),0,0x2dae078,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x2dadf58,0x00000000), stub! fixme:dxgi:dxgi_output_GetDesc iface 0x1c00f0, desc 0x2dae41c stub! fixme:wbemprox:client_security_SetBlanket 0xf71feabc, 0x1c0118, 10, 0, (null), 3, 3, (nil), 0x00000000 fixme:wbemprox:client_security_Release 0xf71feabc fixme:win:EnumDisplayDevicesW ((null),0,0x2dade58,0x00000000), stub! err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already ! fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} 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 ! 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 ! err:wgl:glxdrv_wglShareLists Could not share display lists, one of the contexts has been current already ! fixme:imm:ImmReleaseContext (0x100e2, 0x1e0a08): stub 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 ! 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 ! 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 ! 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 ! 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 ! 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 ! fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0x100ee, filter=0x2dae9a4,flags=0x00000004) 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 ! 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 ! 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 ! fixme:dbghelp:validate_addr64 Unsupported address fffffffff71d0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff71b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff7060000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff75b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff7310000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff72f0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff72b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff6470000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff30b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff2520000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffeb4e0000 err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x105a097 wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. -- 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 day

[Bug 13198] New: Microsoft Pinball Arcade black/blank window in 24bpp mode

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=13198 Summary: Microsoft Pinball Arcade black/blank window in 24bpp mode Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: vanessaezekowitz(a)gmail.com Created an attachment (id=13030) --> (http://bugs.winehq.org/attachment.cgi?id=13030) Screenshot of real 8bpp mode Microsoft Pinball Arcade (commercial/full version) doesn't work properly in WINE if you're using a regular, standard-issue 24bpp X session. Intro/menu screens work, but the 3D content (direct3d? ddraw?) just produces a black screen. Steps to reproduce: 0. Obtain a copy of the game (maybe the demo version will do?). cd into your 'drive c' directory and start the game: `wine Program\ Files/Microsoft\ Games/Pinball\ Arcade/Launcher.exe` 1. A movie displays showing a closeup of one of the game's tables. 2. Click on the movie to interrupt it. The title screen appears and looks fine. 3. Click again, table select menu appears and waits for input. 4. Click on any menu item at the bottom of the window - a dialog related to it appears as it should. 5. Double-click on one of the tables - the table selection screen gets blacked out, the window resizes, and the table's loading screen appears all in the same instant - without repainting the window - the loading screen only painted on the parts of the window that were already black. So we have a window half filled with the loading screen and half transparent, showing this browser and the controlling terminal through it. 6. The loading screen disappears and the window turns solid black. A windows pointer appears. On the console, the "Cannot change screen BPP" line appears. 7. Clicking around eventually causes the pointer to disappear, probably because I managed to trigger the insert-coin hot spot followed by the "1 player" hotspot, thus starting the actual game. Hitting Esc is supposed to bring up a graphical exit/no-exit dialog, but nothing appears. Blindly hitting "y" puts me back at the table-select screen as it should. So the actual game is accepting input, it just isn't showing me anything. 7a. If I try another table, I get the exact same result, including another "Cannot change screen BPP" line on the console. 8. Double-click the table-select menu's internal Exit button and Wine drops back to my shell after a couple of seconds. Actual Results: Described above - I get a black window instead of a game table. Expected Results: Wine should have displayed the table properly and let me play the game. Notes: In order to run this game properly, the user *must* have a true 8bpp mode with StaticColor visual defined in their xorg.conf, and the user *must* manually run a second, separate X screen (e.g. one accessible with Ctrl-Alt-F8) in that more with that visual. Desipte having a known, tested, working 8bpp mode in xorg.conf, Xorg does not have any kind of ability to switch away from the currently-running depth to some other mode (e.g. it cannot and never will be able to drop from 24bpp to 8bpp), and is not expected to ever have such a feature. Furthermore, some users' hardware does not have the ability to run in true 8bpp mode at all, so this game simply *will not work* on those systems. ply does not work on some hardware, despite having correct software settings. The attached screenshot shows what the game looks like in reap 8bpp "StaticColor" mode, using twm as a window manager (it looks the same without a window manager). Versions affected: All WINE versions from roughly 0.9.31 through the current 1.0 rc1 release. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 day

[Bug 49674] New: Feature Request: Restoring previous resolution upon an app crashing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49674 Bug ID: 49674 Summary: Feature Request: Restoring previous resolution upon an app crashing Product: Wine Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s.maddox(a)lantizia.me.uk So this has been a bit of a bug of mine with Wine for a while, but you may think it's not really a problem Wine should deal with - which may be a fair point. But I couldn't find anything clearly asking for this as a feature request... so lets see how well it fairs. # The problem Lets say you open up a Windows executable which changes your screens resolution (e.g. a game) and it either... a) freezes b) is broken enough that its UI (if any appears) can't be used to nicely ask it to quit c) crashes and quits differently to how it'd normally do so upon user request With a) and b) you likely need to kill that process, which ultimately leaves you in the same situation as c). But however it happens... you're likely to find your resolution now stuck to whatever it set. If that is an incredibly low resolution (like 320x240 or 640x480)... then with the desktop environment of today (especially with HiDPI) you're likely going to struggle finding the proper option to fix it. Worse you might resort to a terminal (or switch TTY) and mess around with the xrandr command for a stupid amount of time trying to find the names of screens and such. # Expected Behaviour Well I'm not sure what actually does this. But in actual Windows (e.g Windows 10), when this same circumstance occurs... the resolution is always restored back to what it was. This leaves me to believe that Windows itself has something for this eventuality. # Research Well I've been searching around for solutions to this one for years and the best I always come across... is someone saying you're better off with a script (usually calling xrandr) mapped to a hot key or something for this eventuality. Which is fine if the number of displays you've got connected and their resolutions are always consistent... but often for laptop users moving between docks and such - it isn't. A quick chat on the #winehq IRC channel had someone mention that Proton can now scale games to the resolution you're already using instead (when the app requests a resolution change)... and pointed out these patches... https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro… https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro… That's fine, and it's a welcome feature. But I do wonder if this is a universal fix for any request for any resolution change... regardless the age (and compatibility with which version of Windows it was meant for) of the game and the way it draws on the screen (e.g. SDL, OpenGL, DirectDraw, Vulkan, etc...). However it *may* give some hope for people wanting to run older windowed-mode games from the early Win 3.1/95 era which refuse to be re-sized/re-scaled... but that's a topic for another feature request :) # Conclusion I've not got any. Should this be the job of Wine to restore the prior resolution if the app/game fails to? Like Windows somehow does? Or is this something the OS (whatever that may be, Linux/macOS or even Windows) should be doing separately from Wine for any process? Also if this is a dupe, feel free to mark it as such... I've looked and couldn't find anything that is quite so specific - at least with the points raised here. Thoughts? -- 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 day

[Bug 33270] New: Cursor disappears during Installshield install

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=33270 Bug #: 33270 Summary: Cursor disappears during Installshield install Product: Wine Version: 1.5.26 Platform: x86-64 URL: http://www.oldversion.com/download/quicktime70238.exe OS/Version: Linux Status: NEW Keywords: download, integration Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 44009 --> http://bugs.winehq.org/attachment.cgi?id=44009 Wine 1.5.26 +cursor trace With certain applications (QuickTime 7.02.38, SlingPlayer 1.3) the mouse pointer disappears. It reappears when the installation is complete (or at random intervals). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 day, 1 hour

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2022