October 2018 - Wine-Bugs - list.winehq.org

[Bug 45199] Many applications and games fail to start/ crash after compiling wine with gcc 8.1.0 and -O2 (GOT/ PIC register load code now emitted at function entry, missing hotpatch signatures)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45199 --- Comment #49 from Alex Henrie <alexhenrie24(a)gmail.com> --- Please upload console output and backtraces as attachments, don't copy and paste them. Also, what you posted is only the console output, you didn't include the backtrace. On Arch Linux, the packaged version of Wine does not include debug symbols, and there is no supplementary package to install them. To get debug symbols, you will have to build a copy of Wine from source. See https://wiki.winehq.org/Building_Wine for instructions on how to do that. It's really not that hard, and you'll have to learn how to build Wine in order to test possible solutions anyway. -- 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.

Oct. 1, 2018

[Bug 45148] [Overwatch] Left Ctrl does not work

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45148 --- Comment #12 from Ryan Rohrer <ryan.rohrer(a)gmail.com> --- Interesting I have a Corsair K65. Maybe it’s a Corsair specific 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.

Oct. 1, 2018

[Bug 45148] [Overwatch] Left Ctrl does not work

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45148 --- Comment #11 from odzinic(a)gmail.com --- I came across some other users reporting this on other websites. Both of them were using a Corsair keyboard so I'm wondering if it might have something to do with that. I'm using a Corsair K90. A user also mentioned that when they used a program to virtually switch the left and right control keys Overwatch still recorded LCONTROL as RCONTROL but they were able to use the swapped control key on the left. Not sure if this helps. -- 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.

Oct. 1, 2018

[Bug 26865] Cannot drag-drop extract files (WinRAR, 7-Zip, etc.)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=26865 donanykey(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |donanykey(a)gmail.com --- Comment #13 from donanykey(a)gmail.com --- Confirmed on MacOS @ Wine-devel 3.17 You can't drag-n-drop files out from app's file explorer (WinRar in this case) to Desktop 0009:trace:clipboard:macdrv_UpdateClipboard 0030:trace:clipboard:update_clipboard is_clipboard_owner 1 last_clipboard_update 233371240 now 233372843 000d:trace:clipboard:GetClipboardOwner returning 0x10028 0034:fixme:shell:SHAutoComplete stub 0034:fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0) 0034:err:listview:LISTVIEW_WindowProc unknown msg 108c wp=00000000 lp=00000000 0035:fixme:ver:GetCurrentPackageId (0x140fdf0 0x0): stub 0034:trace:clipboard:macdrv_UpdateClipboard 0030:trace:clipboard:update_clipboard is_clipboard_owner 1 last_clipboard_update 233371240 now 233390272 0034:warn:clipboard:macdrv_UpdateClipboard failed to read from pipe: 233 0034:trace:clipboard:macdrv_UpdateClipboard 0030:trace:clipboard:update_clipboard is_clipboard_owner 1 last_clipboard_update 233371240 now 233408655 0034:fixme:shell:IPersistFile_fnSaveCompleted (0x7d9110)->(L"C:\\users\\_cut_\\Recent\\dotnet-sdk-2.1.202-win-x86.zip (2).lnk"): stub 0034:err:listview:LISTVIEW_WindowProc unknown msg 108c wp=00000000 lp=00000000 0037:trace:clipboard:GetClipboardOwner returning 0x10028 0034:trace:clipboard:macdrv_UpdateClipboard 0030:trace:clipboard:update_clipboard is_clipboard_owner 1 last_clipboard_update 233371240 now 233415292 0034:warn:clipboard:macdrv_UpdateClipboard failed to read from pipe: 233 0034:trace:clipboard:GetClipboardOwner returning 0x10028 -- 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.

Oct. 1, 2018

[Bug 26803] file open dialog: slow when selecting many files

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=26803 donanykey(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |donanykey(a)gmail.com --- Comment #18 from donanykey(a)gmail.com --- Confirmed wine-devel 3.17 Even though its not that dramatic as in the initial message, still, 823 files are being selected in ~7 seconds, while on Windows 10 -- 4366 files in ~2 seconds C:\windows\system32 was used for both selections -- 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.

Oct. 1, 2018

[Bug 14601] WinRAR easter egg animation very slow

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=14601 --- Comment #15 from donanykey(a)gmail.com --- Created attachment 62446 --> https://bugs.winehq.org/attachment.cgi?id=62446 Ubuntu 18.04.1 (About) -- 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.

Oct. 1, 2018

[Bug 14601] WinRAR easter egg animation very slow

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=14601 --- Comment #14 from donanykey(a)gmail.com --- Created attachment 62445 --> https://bugs.winehq.org/attachment.cgi?id=62445 MacOS (About) Any seen cpu usage was caused by other processes -- 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.

Oct. 1, 2018

[Bug 14601] WinRAR easter egg animation very slow

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=14601 --- Comment #13 from donanykey(a)gmail.com --- Created attachment 62444 --> https://bugs.winehq.org/attachment.cgi?id=62444 Windows 10 (About) -- 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.

Oct. 1, 2018

[Bug 14601] WinRAR easter egg animation very slow

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=14601 --- Comment #12 from donanykey(a)gmail.com --- Hi Guys, Although the high cpu usage has been seen on Windows as well, with recent version of WinRar @ Wine 3.17 its all OK everywhere (see screenshots attached) And I don't see any pixel artifacts (at least my eye doesn't catch any) even though there is spam of 0034:fixme:wincodecs:BitmapScaler_Initialize unsupported mode 3 I believe this bug could be resolved. -- 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.

Oct. 1, 2018

[Bug 45815] FamiTracker etc. use much more CPU in Wine than Windows

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45815 --- Comment #5 from jimbo1qaz <jimbo1qaz(a)gmail.com> --- would be nice if I could use `gdb --args wine exe` and have it pick up symbols... apt install wine-devel-dbg:i386 (note, amd64 didn't supply 32-bit symbols, and conflicts with i386 due to widl) gdb --args wine j0CC-Famitracker-j0.6.1.exe >Reading symbols from wine...Reading symbols from /usr/lib/debug//opt/wine-devel/bin/wine...done. (gdb) b GetWindow Function "GetWindow" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (GetWindow) pending. (gdb) b GetTopWindow Function "GetTopWindow" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 2 (GetTopWindow) pending. (gdb) b CallWindowProcA Function "CallWindowProcA" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 3 (CallWindowProcA) pending. (gdb) r Starting program: /usr/bin/wine j0CC-Famitracker-j0.6.1.exe you have to continue past SIGUSR1 twice (0xf7ffcc89), but none of the breakpoints trigger. -- 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.

Oct. 1, 2018