wine-bugs November 2017

1 participants
7653 discussions

[Bug 43576] New: unit test: Menu Highlight does not return to original color after style applied

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43576 Bug ID: 43576 Summary: unit test: Menu Highlight does not return to original color after style applied Product: Wine Version: 2.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Brad.Wine1(a)amaitis.com Distribution: --- Created attachment 58987 --> https://bugs.winehq.org/attachment.cgi?id=58987 Image of Visual bug winehq-devel wine --version wine-2.13 and wine-2.14 Menu highlighting works without the style loaded. After Style is loaded Menu Highlight does not return to original color. delphi source code is available download unit test http://www.ateksol.com/dev/unittest/MenuStyle.exe sha1sum b08eb7ad7fb0ea9164071b53dcacd117390d0913 MenuStyle.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.

6 years, 6 months

[Bug 5858] oleaut32 -WinAmbulancia (@MDB,VB) -database repare fails

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=5858 oll <oll.full001(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oll.full001(a)gmail.com -- 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.

6 years, 6 months

[Bug 43853] New: Keepass2 fails to launch

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43853 Bug ID: 43853 Summary: Keepass2 fails to launch Product: Wine Version: 2.0.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madmedix(a)gmail.com Distribution: --- Created attachment 59411 --> https://bugs.winehq.org/attachment.cgi?id=59411 system generated log file Portable Apps version, resides on seperate HDD that is also used by Win10/64. Stock Ubuntu 17.10/64 install. Previously worked without problems until this update (from Synaptic): Commit Log for Tue Sep 12 22:09:27 2017 Upgraded the following packages: bluez (5.43-0ubuntu1) to 5.43-0ubuntu1.1 bluez-obexd (5.43-0ubuntu1) to 5.43-0ubuntu1.1 file (1:5.29-3) to 1:5.29-3ubuntu0.1 flashplugin-installer (26.0.0.151ubuntu0.17.04.1) to 27.0.0.130ubuntu0.17.04.1 gnome-software-common (3.22.7-0ubuntu3.17.04.5) to 3.22.7-0ubuntu3.17.04.7 libbluetooth3 (5.43-0ubuntu1) to 5.43-0ubuntu1.1 libgd3 (2.2.4-2ubuntu0.2) to 2.2.4-2ubuntu0.3 libgd3:i386 (2.2.4-2ubuntu0.2) to 2.2.4-2ubuntu0.3 libgnutls30 (3.5.6-4ubuntu4.1) to 3.5.6-4ubuntu4.2 libgnutls30:i386 (3.5.6-4ubuntu4.1) to 3.5.6-4ubuntu4.2 liblouis-data (3.0.0-3) to 3.0.0-3ubuntu0.2 liblouis12 (3.0.0-3) to 3.0.0-3ubuntu0.2 libmagic-mgc (1:5.29-3) to 1:5.29-3ubuntu0.1 libmagic1 (1:5.29-3) to 1:5.29-3ubuntu0.1 python3-louis (3.0.0-3) to 3.0.0-3ubuntu0.2 -- 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.

6 years, 6 months

[Bug 42569] New: user32/tests/clipboard intermittent failure (" expected freed memory")

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42569 Bug ID: 42569 Summary: user32/tests/clipboard intermittent failure ("expected freed memory") Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- The following error is sometimes given: clipboard.c:1742: Test failed: expected freed mem 0x155300 This seems to affect the acer64 and f25 test machines but not the hd6800. -- 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.

6 years, 6 months

[Bug 42568] New: user32/tests/ msg.ok intermittent failure in SendMessage from other thread

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42568 Bug ID: 42568 Summary: user32/tests/msg.ok intermittent failure in SendMessage from other thread Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- The following lines are sometimes printed when running the tests for msg.c: msg.c:15837: Test failed: SendMessage from other thread 4: 0: the msg 0x0401 was expected, but got msg 0x0403 instead msg.c:15837: Test failed: SendMessage from other thread 4: 1: the msg sequence is not complete: expected 0000 - actual 0401 msg.c:15845: Test succeeded inside todo block: wrong status 00000000 msg.c:15849: Test succeeded inside todo block: SendMessage from other thread 5: marked "todo_wine" but succeeds This affects both of the test machines. -- 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.

6 years, 6 months

[Bug 43750] New: USB "ttyACM0" serial port not being created

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43750 Bug ID: 43750 Summary: USB "ttyACM0" serial port not being created Product: Wine Version: 2.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phoenix-precision(a)gmx.co.uk Distribution: --- I have followed the new instructions at https://wiki.winehq.org/Wine_User%27s_Guide#Serial_and_Parallel_Ports, to use a Neo 7 GPS module. I had to create the registry key HKLM\Software\Wine\Ports as it did not already exist. I added a string value "COM1" with the data /dev/ttyACM0, ran wineserver -k and started my application (u-center from https://www.u-blox.com/sites/default/files/ublox-GNSS_u-center_windows_v8.2… ) ls -l .wine/dosdevices shows the same four standard com ports as normal, no change. Next I deleted com1 and manually created the link to /dev/ttyACM0. When I restarted wine the link had been replaced by the standard one again. I also attempted to create COM5 via the registry key HKLM\HARDWARE\DEVICEMAP\SERIALCOMM, but Wine is having none of it and deletes it when re-started. By starting the application and then manually creating the COM port link I am able to use my device, so there is nothing wrong there. It is purely the mapping of COM ports which is the problem. -- 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.

6 years, 6 months

[Bug 37669] New: Resetting a write watch can cause memory access violation in kernel

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37669 Bug ID: 37669 Summary: Resetting a write watch can cause memory access violation in kernel Product: Wine Version: 1.7.32 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru Distribution: --- What happens: heavy multi-threaded network application in one thread reads/writes from/to a socket while in another thread .net GC calls GetWriteWatch with flag WRITE_WATCH_FLAG_RESET on a buffer which was just verified for write access and passed by ws2_32.recv to recvmsg kernel call. While recvmsg waits for incoming data GetWriteWatch resets write watches by clearing VPROT_WRITE access on a buffer passed to recvmsg. That cases recvmsg to return EFAULT which in turn leads to a .net application raising an exception and dying. This is basically a .net garbage collector causing races in network code which reads/writes to a buffer because reading or writing via a network is much slower than say reading/writing a disk file, but essentially this is a general problem with resetting a write watch while another thread is being dealing with the affected memory range. -- 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.

6 years, 6 months

[Bug 43405] New: NieR:Automata - Most bullets are invisible

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43405 Bug ID: 43405 Summary: NieR:Automata - Most bullets are invisible Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 58747 --> https://bugs.winehq.org/attachment.cgi?id=58747 How the minigame looks on linux NieR:Automata is an 64Bit DX11 game on Steam. It has some rendering issues, most standard bullets are completely invisible, both in the actual game and the minigame. Screenshots attached. I made an apitrace, but unfortunately this comes at a whooping 1.4GB (543MB compressed). If you still want it, I uploaded it here: http://www.mediafire.com/file/me8dsk3asiuqoiw/automata.7z I don't know if it's possible to trim apitraces at the start, but if so, please tell me and I'll shrink it down. It's just that I can't skip those parts of the game. Screenshots from frame 3050(windows) and 3052(linux), but I removed the transparency. Using wine-2.12-staging on Arch Linux for my tests. -- 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.

6 years, 6 months

[Bug 42863] New: winexy: Creates invalid glsl

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42863 Bug ID: 42863 Summary: winexy: Creates invalid glsl Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 57963 --> https://bugs.winehq.org/attachment.cgi?id=57963 Cutdown log of the error When running winexy, via stream, the game doesn't display anything. -- 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.

6 years, 6 months

[Bug 43952] New: kernel32/tests/console.ok fails

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43952 Bug ID: 43952 Summary: kernel32/tests/console.ok fails Product: Wine Version: 2.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: alexhenrie24(a)gmail.com, fgouget(a)codeweavers.com Distribution: --- Consistently fails in test_ReadConsole() on Francois Gouget's test machines and the CW1/CW2 machines, but nowhere else: console.c:2585: Test failed: expected INVALID_FILE_SIZE, got 0 console.c:2586: Test failed: expected ERROR_INVALID_HANDLE, got -559038737 CCing Francois Gouget and Alex Henrie. I think the current theory was that this had to do with netcat? -- 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.

6 years, 6 months

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 November 2017