wine-bugs December 2019

wine-bugs@winehq.org

1 participants
7450 discussions

[Bug 43454] New: Finereader 12 Professional crashes at start
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=43454 Bug ID: 43454 Summary: Finereader 12 Professional crashes at start Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sanya-0996(a)yandex.by Distribution: --- Created attachment 58821 --> https://bugs.winehq.org/attachment.cgi?id=58821 backtrace Finereader 12 Professional crashes at start with wine 1.6, 2.0.2 and 2.13. Installed by: wine msiexec /i ABBYY\ FineReader\ 12\ Professional.msi DISABLEROLLBACK=1 -- 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.

2 7

[Bug 43765] New: RSpec-Explorer windows are sometimes unresponsive to keyboard and mouse input
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=43765 Bug ID: 43765 Summary: RSpec-Explorer windows are sometimes unresponsive to keyboard and mouse input Product: Wine Version: 2.17 Hardware: x86 URL: https://www.rspec-astro.com/setupdownload/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Under some conditions, the application will refuse to respond to mouse and keyboard input. The windows can be minimized, closed, focused, etc; and edit controls will blink the caret, but buttons won't be clicked and other controls similarly won't update. This affects not only the main window but also the common open-file dialog. I can pretty reliably trigger this by starting the main application, ensuring that it is not maximized, then clicking the folder icon in the upper left to trigger the open-file dialog. Said dialog will in most cases not respond to input as described above; and, when it is closed, the main window will sometimes similarly stop responding to input. I can also see this behaviour, though less consistently, with the first window that shows up (warning you that this program is a free trial); this window sometimes fails to respond to input, and usually the main window will fail to respond after it is closed. This state of unresponsiveness can in fact be undone. If the main window is unresponsive, minimizing and restoring it will cause it to again be responsive. More bizarrely, if one of the dialog windows is unresponsive, moving the main window below the dialog (or nearly below it) will cause it to be responsive; additionally, any keyboard or mouse events will be processed. Adding some traces to DIALOG_DoDialogBox() shows that there are clearly mouse events in the queue, but they seem to be ignored by PeekMessage(). I have no idea why this would happen. -- 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.

2 8

[Bug 42555] New: Units are invisible in Shogun: Total War battle map
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=42555 Bug ID: 42555 Summary: Units are invisible in Shogun: Total War battle map Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: aaronbpaden(a)gmail.com Distribution: --- Created attachment 57460 --> https://bugs.winehq.org/attachment.cgi?id=57460 wine log Units that should appear on the battle map are invisible. They are still there, you can see them moving around on the minimap and you can select them and give orders, but they aren't visible. Shogun is known to not work well with modern Windows, so I've tried with both Windows 7 and Windows 98 on a clean prefix, but I get the same issue. >From the logs, this appears to be a d3d issue. Shogun uses DirectX 8, if it 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.

2 3

[Bug 47690] New: When DirectWrite rendering is enabled in Notepad++ there are still no ligatures.
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=47690 Bug ID: 47690 Summary: When DirectWrite rendering is enabled in Notepad++ there are still no ligatures. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- [Notepad++](https://github.com/notepad-plus-plus/notepad-plus-plus) is an application based on Scintilla. Scintilla is a library for creating textareas. [DirectWrite](https://docs.microsoft.com/en-us/windows/win32/directwrite/dir… is an API for text rendering with subpixel antialiasing which can be hardware-accelerated using Direct2D. [SCI_SETTECHNOLOGY](https://www.scintilla.org/ScintillaDox.html#SCI_SETTECHN… is a enum value identifying a call to Scintilla (in fact it is done using Windows messages). When it is set to values > 0 (SC_TECHNOLOGY_DIRECTWRITE, SC_TECHNOLOGY_DIRECTWRITERETAIN, or SC_TECHNOLOGY_DIRECTWRITEDC), Scintilla uses DirectDraw accelerated via Direct2D for rendering instead of an own surrogate. A byproduct of enebling DirectWrite rendering is ligatures support on fonts having them, like Fira Code. In fact it is the main reason to enable DirectWrite in NPP. In Windows >7 everything works fine. In Wine there are no ligatures (and some other issues). -- 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.

2 10

[Bug 45774] New: Black screen (Ragnarok Online kRO)
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=45774 Bug ID: 45774 Summary: Black screen (Ragnarok Online kRO) Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vectorfish(a)gmail.com Distribution: --- Since Wine 3.13, you get black screen in Ragnarok Online from the very beginning. I went through regression test and it turned out that the issue started with commit 6ccb94392a8ef4bca701ae2a560f4ea1da677edd ("server: Clip visible region to the surface rectangle instead of the desktop."). -- 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.

2 11

[Bug 17233] New: Zanzarah game opens a black fullscreen window and then crashes
by wine-bugs＠winehq.org 08 May '20

08 May '20

http://bugs.winehq.org/show_bug.cgi?id=17233 Summary: Zanzarah game opens a black fullscreen window and then crashes Product: Wine Version: 1.1.14 Platform: PC-x86-64 URL: http://www.download.com/Zanzarah-demo/3000-7492_4- 10246951.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: gryffus(a)hkfree.org Game opens a black fullscreen window and then crashes. I am using an nvidia card. -- 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.

2 42

[Bug 40311] New: Processing of 'DeviceIoControl' calls doesn't corresponds to specification
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=40311 Bug ID: 40311 Summary: Processing of 'DeviceIoControl' calls doesn't corresponds to specification Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: ugnenko(a)mail.ru Distribution: --- As described in specification 'Buffer Descriptions for I/O Control Codes' for 'METHOD_IN_DIRECT' or 'METHOD_OUT_DIRECT' transfer types the data buffer, to which points the pointer passed as 'lpOutputBuffer' argument into 'DeviceIoControl', must be accessible from driver. In other words, when in control code is specified 'METHOD_IN_DIRECT' tranfer type, the 'lpOutputBuffer' buffer may be used as the additional buffer of data that driver may transfer to device. This feature is used in software and drivers for Hantek Oscilloscopes. The pointer 'lpOutputBuffer' and argument 'nOutBufferSize', which are passed to 'DeviceIoControl' function, must are used as corresponding values for fields 'StartVa', 'ByteOffset' and 'ByteCount' in 'irp->MdlAddress' structure. But Wine allocates new output buffer that are passed to 'IoBuildDeviceIoControlRequest' (see function 'dispatch_ioctl' in source file 'dlls/ntoskrnl.exe/ntoskrnl.c'). Thus data stored in output buffer aren't available for driver. Specification: https://msdn.microsoft.com/en-us/library/windows/hardware/ff540663(v=vs.85)… -- 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.

2 8

[Bug 40894] New: Warcraft 3: Crash on starting the game
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=40894 Bug ID: 40894 Summary: Warcraft 3: Crash on starting the game Product: Wine Version: 1.9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 54985 --> https://bugs.winehq.org/attachment.cgi?id=54985 Terminal output A few days before I was still able to start Warcraft 3 (not sure if it was with Wine 1.9.12 or already Wine 1.9.13) and now after using a clean profile Warcraft 3 crashes on starting it. In the attachments is the terminal output. -- 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.

2 18

[Bug 46377] New: The Bat!: weird behaviour of program icon on the KDE taskbar
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=46377 Bug ID: 46377 Summary: The Bat!: weird behaviour of program icon on the KDE taskbar Product: Wine Version: 4.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- Created attachment 63123 --> https://bugs.winehq.org/attachment.cgi?id=63123 Weird icon changes The program icon shown on the taskbar changes during the program is active und also when it closes. Also the label on taskbar is changing. This is Debian buster with Plasma (KDE) desktop. -- 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.

2 5

[Bug 42313] New: Process Hacker 2.39.124 crashes when attempting to inspect any process
by wine-bugs＠winehq.org 08 May '20

08 May '20

https://bugs.winehq.org/show_bug.cgi?id=42313 Bug ID: 42313 Summary: Process Hacker 2.39.124 crashes when attempting to inspect any process Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hakusdream(a)gmail.com Distribution: --- Created attachment 57053 --> https://bugs.winehq.org/attachment.cgi?id=57053 Relevant backtrace Release version of Process Hacker faults when attempting to inspect a process through its GUI. -- 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.

2 9

Jump to page:

2025

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 December 2019