September 2015 - Wine-Bugs - list.winehq.org

[Bug 29181] New: Combo box doesn't get a background in dialog editor
by wine-bugs＠winehq.org Jan. 11, 2019

Jan. 11, 2019

http://bugs.winehq.org/show_bug.cgi?id=29181 Bug #: 29181 Summary: Combo box doesn't get a background in dialog editor Product: Wine Version: 1.3.33 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: toni.spets(a)iki.fi Classification: Unclassified Created attachment 37647 --> http://bugs.winehq.org/attachment.cgi?id=37647 Hack for background drawing When using a resource editor like ResEdit to create dialogs, combo boxes have CBF_EDIT set and the white background is not drawn and the dialog background is seen instead. Attached a patch that workarounds the problem for this case. It is probably not the correct fix as there must be a reason why CBF_EDIT state control background is not drawn. Of course on Windows the combo box background is drawn with this program. -- 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 9

[Bug 33835] New: Touhou 13.5 black screen
by wine-bugs＠winehq.org Jan. 5, 2019

Jan. 5, 2019

http://bugs.winehq.org/show_bug.cgi?id=33835 Bug #: 33835 Summary: Touhou 13.5 black screen Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: murela_alba(a)abv.bg CC: wine-bugs(a)winehq.org Classification: Unclassified Created attachment 44861 --> http://bugs.winehq.org/attachment.cgi?id=44861 Title screen When running Hopeless Masquerade after the loading screen the only thing rendered is the main menu and game logo, with no background and when trying to go into story mode, the entire screen turns black. Music and sound effects are running properly at the same time. Game version is 1.03b, but 1.0 does the same. Tested with wine 1.6-rc2 on Ubuntu 13.04 (64-bit). -- 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 15

[Bug 38721] New: Steam problem - Wine uncompability or something similar
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

https://bugs.winehq.org/show_bug.cgi?id=38721 Bug ID: 38721 Summary: Steam problem - Wine uncompability or something similar Product: Wine Version: 1.7.44 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adriansnetlis3(a)inbox.lv Distribution: --- Created attachment 51646 --> https://bugs.winehq.org/attachment.cgi?id=51646 The .log file with errors Hi! I want to report that Steam installation has a problem here. I am posting the log as attachment, but it is PlayOnlinux. Why PlayOnLinux - I am not gone do very the same in console now as the installation was long for running Resident Evil 5. But I am 100% sure this problem is releated to Wine and will be the same also in non-POL installation. Actually, I am not 100% sure what the problem is, but the log puts out one error that POL members which I reported a problem with Resident Evil 5(here you can see my problem: https://www.playonlinux.com/en/topic-13184-Resident_Evil_5_Gold_Edition_Ste… ). It may be reason why Resident Evil 5 not run, so I have to ask it here as POL can't help with Wine errors. The POL log is in attachment. Please, don't reject this - this may be important for multiple people! -- 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 17

[Bug 34334] New: MetaTester 5 never sends or receives data
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=34334 Bug #: 34334 Summary: MetaTester 5 never sends or receives data Product: Wine Version: 1.7.0 Platform: x86-64 URL: http://files.metaquotes.net/metaquotes.software.corp/m t5/mt5tester.setup.exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45702 --> http://bugs.winehq.org/attachment.cgi?id=45702 wine-1.7.0-199-g52fb1cc console output (1st run) The MetaTrader 5 Strategy Tester Agent (MetaTester 5) never sends or receives any data. It comes as part of MetaTrader 5 but is also available separately to create your own server farm. It installs itself as a system service on Windows (SYSTEM account) and runs in the background once it has been initially set up from the main application. Wine seems to have a problem running the services but that is a different problem (bug not yet logged). Wireshark confirms that no connection attempts are sent or received. Not externally anyway. The main application window shows statistics for data transfer and under Windows XP this can be a few kB each day when quiet (when stock markets are closed), but Wine never registers a single byte. Netstat shows that the agents themselves are listening: tcp 0 0 0.0.0.0:2001 0.0.0.0:* LISTEN 216313/wineserver I can telnet to this port and it remains open for a few seconds before timing out and closing. This does not register as data on the main application (same in XP). There are listeners on port 6010 and 6011 too but I think they're control ports. I am attaching the first run log as two agent services start successfully on first run. You can start as many as you like but it makes sense to have one agent per core. Ran all day on Windows XP and Linux to compare. In testing I enabled the agents to join the community (global) network. An account is not required for this. -- 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 7

[Bug 32218] New: LTSpice: Objects not resized when the window is resized
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=32218 Bug #: 32218 Summary: LTSpice: Objects not resized when the window is resized Product: Wine Version: 1.5.17 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 00cpxxx(a)gmail.com Classification: Unclassified Steps to reproduce: 1) Download, install and run LTSpice - http://ltspice.linear.com/software/LTspiceIV.exe 2) Create a new schematic (File -> New Schematic) 3) Press L, click somewhere (this will create a component in the screen) 4) Press ESC to go back to the select tool, hold CTRL and right-click the component to open a properties window. 5) Resize the window. The internal window listview will not get resized to match the new window size. This is not a duplicate of bug 3037 and may or may not be a duplicate of bug 7007 it will take a while to check. -- 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 13

[Bug 32221] New: LTspice: component drawing issues when moving
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=32221 Bug #: 32221 Summary: LTspice: component drawing issues when moving Product: Wine Version: 1.5.13 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: testelor(a)yahoo.com Classification: Unclassified Created attachment 42497 --> http://bugs.winehq.org/attachment.cgi?id=42497 Traces left behind when moving Steps to reproduce: 1) Download and install LTspice - http://ltspice.linear.com/software/LTspiceIV.exe 2) Run LTspice using: $ wine scad3.exe -nowine 3) Create a new schematic, press 'R' (resistor), for example, and don't place it by clicking, simply move it around. The same happens for any component that is grabbed and moved. See the attached screenshot. -- 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 11

[Bug 33719] New: comctl32:propsheet custom window proc test failure
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=33719 Bug #: 33719 Summary: comctl32:propsheet custom window proc test failure Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified A number of VMs report one of these two related test failures: Elevated privileges (or pre-Vista): propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x001c was expected, but got msg 0x0047 instead or not elevated privileges: propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x0046 was expected, but got msg 0x0210 instead They have been seen on the following systems: comctl32 5.81.4968.2500 Windows 2000 Professional SP4 + IE55 (rare ~1/50) comctl32 5.82.3790.3959 Windows 2003 Enterprise Server SP2 + IE8 (rare ~1/50) comctl32 5.82.6002.18305 Windows Vista Home Premium SP2+IE9 comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit (+IE8) (32-bit tests) comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit + IE9 (32-bit tests) comctl32 5.82.7601.17514 Windows 7 SP1 (not one of mine) comctl32 5.82.9200.16384 Windows 8 -- 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 12

[Bug 26262] New: No video output in game
by wine-bugs＠winehq.org Jan. 1, 2019

Jan. 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=26262 Summary: No video output in game Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: torgeriedel(a)gmx.de When trying to play Commandos - Behind Enemy lines, there is no video output. Sound is working. -- 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 25

[Bug 33368] New: WM_DEADCHAR events not sent
by wine-bugs＠winehq.org Dec. 31, 2018

Dec. 31, 2018

http://bugs.winehq.org/show_bug.cgi?id=33368 Bug #: 33368 Summary: WM_DEADCHAR events not sent Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 44152 --> http://bugs.winehq.org/attachment.cgi?id=44152 Keyboard traces in three different scenarios (Windows, Wine, Wine+patch) XFilterEvent() returns true for events of dead keys, so they are not processed by wine. However, that prevents sending a WM_DEADCHAR event to the application, as it works on Windows. For example, in order to emit a "ê" character in a french keyboard layout, I first have to press ^ (which is a dead key) and then e. Under Windows, this leads to the following sequence of events : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e KEYUP: dead_circumflex Under wine I have only those events : KEYUP: dead_circumflex KEYDOWN: e CHAR: ê Attached patch fixes most of that, with it I get : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex UP: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e Note that it’s still slighty different from Windows (KEYUP for dead key is third message on Wine, whereas it is before the last one on Windows), but I don’t see a clean fix for this issue. As for the traces in attachment, contains three traces. The first one is from Spy++ on Windows ; the second is the relevant output of WINEDEBUG=+msg notepad for unpatched wine ; the third one for patched wine. -- 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 6

[Bug 36095] New: valgrind errors in loader when loading a dll
by wine-bugs＠winehq.org Dec. 31, 2018

Dec. 31, 2018

https://bugs.winehq.org/show_bug.cgi?id=36095 Bug ID: 36095 Summary: valgrind errors in loader when loading a dll Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: major Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Noticed this in most tests, there are at least 3 places. 1: ==11164== 26 bytes in 1 blocks are definitely lost in loss record 57 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11164== by 0x7BC54CF3: alloc_module (loader.c:919) ==11164== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11164== by 0x40192DE: __wine_dll_register (loader.c:517) ==11164== by 0x7B88A18B: __wine_spec_init (init.c:35) ==11164== by 0x4E850459: call_init.part.0 (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850593: _dl_init (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854953: dl_open_worker (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854013: _dl_open (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA25CBB: dlopen_doit (in /usr/lib/libdl-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA263CB: _dlerror_run (in /usr/lib/libdl-2.18.so) ==11164== by 0x4EA25D70: dlopen@@GLIBC_2.1 (in /usr/lib/libdl-2.18.so) ==11164== by 0x4019898: wine_dlopen (loader.c:1029) ==11164== by 0x4018C06: dlopen_dll (loader.c:295) ==11164== by 0x4019532: wine_dll_load (loader.c:581) ==11164== by 0x7BC57199: load_builtin_dll (loader.c:1732) ==11164== 2: ==11164== 32 bytes in 1 blocks are possibly lost in loss record 65 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11164== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11164== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11164== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11164== by 0x7BC58099: load_dll (loader.c:2045) ==11164== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11164== by 0x7B85A79A: load_library (module.c:933) ==11164== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11164== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11164== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11164== by 0x4019864: wine_init (loader.c:952) ==11164== by 0x7BF011AD: main (main.c:237) ==11164== 3: ==11165== 20 bytes in 1 blocks are definitely lost in loss record 14 of 58 ==11165== at 0x7BC4C735: notify_alloc (heap.c:255) ==11165== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11165== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11165== by 0x7BC54CF3: alloc_module (loader.c:919) ==11165== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11165== by 0x40193D9: wine_dll_set_callback (loader.c:548) ==11165== by 0x7BC5ABA2: __wine_process_init (loader.c:3086) ==11165== by 0x4019864: wine_init (loader.c:952) ==11165== by 0x7BF011AD: main (main.c:237) ==11165== 4: ==11194== 32 bytes in 1 blocks are possibly lost in loss record 66 of 248 ==11194== at 0x7BC4C735: notify_alloc (heap.c:255) ==11194== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11194== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11194== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11194== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11194== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11194== by 0x7BC58099: load_dll (loader.c:2045) ==11194== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11194== by 0x7B85A79A: load_library (module.c:933) ==11194== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11194== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11194== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11194== by 0x4019864: wine_init (loader.c:952) ==11194== by 0x7BF011AD: main (main.c:237) ==11194== (tested running advapi32/security.c) wine-1.7.17-92-ge2bf516 -- 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