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.
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.
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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=38495
Bug ID: 38495
Summary: Origin crashes when launching a game
Product: Wine
Version: 1.7.41
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 51342
--> https://bugs.winehq.org/attachment.cgi?id=51342
Origin backtrace - Slackware 14.1 - wine 1.7.41
Hello everyone,
I compiled "wine 1.7.41" from source and bought the "Humble Bundle Origin 2"
today. Registering games works fine but when I tried to launch the "Syndicate"
game I ran into a crash. Backtrace is attached.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39649
Bug ID: 39649
Summary: Anno 1701 doesn't show images in ANNOpedia when
anti-aliasing enabled
Product: Wine
Version: 1.8-rc1
Hardware: x86
URL: http://www.gamershell.com/download_16068.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
Created attachment 52851
--> https://bugs.winehq.org/attachment.cgi?id=52851
screenshot
Pictures are missing from the ANNOpedia (in-built guide) when anti-aliasing is
enabled in Anno 1701.There's only an empty rectangle where images should
appear. These lines are spamming the console when I open the Annopedia:
err:d3d:wined3d_debug_callback 0x18fadaf8: "GL_INVALID_OPERATION error
generated. Source and destination dimensions must be identical with the current
filtering modes.".
err:d3d_surface:surface_blt_fbo >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502)
from glBlitFramebuffer() @ surface.c / 985
Those messages look similar to the ones in bug #37175.
To reproduce the problem in the demo:
1. Install and start Anno 1701 demo (game startup may take a while).
2. In the main menu go to <Options> -> <Graphics> and set up anti-aliasing, go
back to the main menu.
3. Start <Singleplayer> -> <Continuous play> and launch the game.
4. When the game is loaded press <Esc> and select <ANNOpedia> from the menu:
you should see that images are missing from ANNOpedia.
Tested with Nvidia binary drivers 340.96 and with Nouveau/Mesa git.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42326
Bug ID: 42326
Summary: Darsksiders Warmastered Edition crashes on startup
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 57074
--> https://bugs.winehq.org/attachment.cgi?id=57074
Terminal output from Wine 2.0-160-g152b240153
When attempting to run Darksiders Warmastered Edition, the game opens up to a
black screen, pops up a crash dialog that asks me if I want to create a crash
dump, and then exits to desktop with Wine 2.0 or Wine 2.0 Staging.
Please note that Darksiders Warmastered Edition is a DirectX11 game and,
therefore, there is no way to switch it to a DX9 mode.
Terminal output attached.
--
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.