https://bugs.winehq.org/show_bug.cgi?id=50053
Bug ID: 50053
Summary: wineconsole - X Window selection
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vladimir.kokovic(a)gmail.com
Distribution: ---
I can't believe that anyone in the unix world today should ask for a linux
application to use some X window feature.
But the situation with wineconsole is such that I find myself competent to ask
that wineconsole use X window PRIMARY selection instead of DOS nonsense
mark-copy-paste!
Vladimir Koković, DP senior(70),
Serbia, Belgrade, 24.October 2020
--
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=36873
Bug ID: 36873
Summary: Chronology (.NET 4.0 game) based on 'OpenTK': mouse
input non-functional, mouse cursor invisible
Product: Wine
Version: 1.7.21
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
the GOG.com version installs .NET Framework 4.0 client profile on its own in
clean 32-bit WINEPREFIX (without Mono).
If the mouse is moved (either in fullscreen or virtual desktop mode), the
console is spammed with:
--- snip ---
fixme:win:GetMouseMovePointsEx (16 0x33ea10 0x33e5cc 64 1) stub
fixme:win:GetMouseMovePointsEx (16 0x33ea10 0x33e5cc 64 1) stub
fixme:win:GetMouseMovePointsEx (16 0x33ea10 0x33e5cc 64 1) stub
--- snip ---
Source:
http://source.winehq.org/git/wine.git/blob/bdc9b147b948b3476815c52f7fc53f4c…
--- snip ---
1427 int WINAPI GetMouseMovePointsEx(UINT size, LPMOUSEMOVEPOINT ptin,
LPMOUSEMOVEPOINT ptout, int count, DWORD res) {
1428
1429 if((size != sizeof(MOUSEMOVEPOINT)) || (count < 0) || (count > 64)) {
1430 SetLastError(ERROR_INVALID_PARAMETER);
1431 return -1;
1432 }
1433
1434 if(!ptin || (!ptout && count)) {
1435 SetLastError(ERROR_NOACCESS);
1436 return -1;
1437 }
1438
1439 FIXME("(%d %p %p %d %d) stub\n", size, ptin, ptout, count, res);
1440
1441 SetLastError(ERROR_POINT_NOT_FOUND);
1442 return -1;
1443 }
--- snip ---
MSDN:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms646259%28v=vs.85%…
That noisy stub (although annoying) doesn't seem to be the problem here.
See here for discussion and how it's implemented in 'OpenTK':
https://github.com/opentk/opentk/issues/76https://github.com/opentk/opentk/blob/develop/Source/OpenTK/Platform/Window…
--- snip ---
void HandleMouseMove(IntPtr handle, WindowMessage message, IntPtr
wParam, IntPtr lParam)
{
unsafe
{
Point point = new Point(
(short)((uint)lParam.ToInt32() & 0x0000FFFF),
(short)(((uint)lParam.ToInt32() & 0xFFFF0000) >> 16));
// GetMouseMovePointsEx works with screen coordinates
Point screenPoint = point;
Functions.ClientToScreen(handle, ref screenPoint);
int timestamp = Functions.GetMessageTime();
// & 0xFFFF to handle multiple monitors
http://support.microsoft.com/kb/269743
MouseMovePoint movePoint = new MouseMovePoint()
{
X = screenPoint.X & 0xFFFF,
Y = screenPoint.Y & 0xFFFF,
Time = timestamp,
};
// Max points GetMouseMovePointsEx can return is 64.
const int numPoints = 64;
MouseMovePoint* movePoints = stackalloc
MouseMovePoint[numPoints];
// GetMouseMovePointsEx fills in movePoints so that the most
// recent events are at low indices in the array.
int points = Functions.GetMouseMovePointsEx(
(uint)MouseMovePoint.SizeInBytes,
&movePoint, movePoints, numPoints,
Constants.GMMP_USE_DISPLAY_POINTS);
int lastError = Marshal.GetLastWin32Error();
// No points returned or search point not found
if (points == 0 || (points == -1 && lastError ==
Constants.ERROR_POINT_NOT_FOUND))
{
// Just use the mouse move position
OnMouseMove(point.X, point.Y);
}
else if (points == -1)
{
throw new System.ComponentModel.Win32Exception(lastError);
}
else
{
...
--- snip ---
That information might be still useful for 'GetMouseMovePointsEx'
implementation though.
$ wine --version
wine-1.7.21-75-g0a4c786
Regards
--
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=49135
Bug ID: 49135
Summary: 3DMark06 cannot be installed: "The CPU of this system
does not support SSE instructions"
Product: Wine
Version: 5.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Created attachment 67138
--> https://bugs.winehq.org/attachment.cgi?id=67138
Installer
It used to be installable.
$ wine 3DMark06_v121_installer.exe
0070:err:ntoskrnl:ZwLoadDriver failed to create driver
L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb"
failed to start: 1114
0024:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0024:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0031F2AC
L"C:\\users\\birdie\\Temp\\{9ECBE0A5-94B8-4225-8A90-777902F90B40}\\Disk1\\data1.hdr"
--
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=49997
Bug ID: 49997
Summary: Capella no yakusoku: Game doesn't start (black screen)
Product: Wine
Version: 5.19
Hardware: x86-64
URL: https://www.freem.ne.jp/dl/win/7629
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kakurasan(a)gmail.com
CC: jacek(a)codeweavers.com
Regression SHA1: 54e117018cd4cc58c258da92686bfad13946bde2
Distribution: ---
When trying to start the game (Game.exe), a black window appears but the game
doesn't start.
This is a regression introduced by:
commit 54e117018cd4cc58c258da92686bfad13946bde2
Author: Jacek Caban < ... >
Date: Mon Sep 21 17:07:29 2020 +0200
kernelbase: Use conhost to handle Unix consoles.
The conhost-related terminal output is "fixme:conhost:screen_buffer_ioctl
unsupported ioctl 50402c" but I'm not sure whether it is relevant.
Steps to reproduce:
1. Download "RPG Maker VX Ace Run Time Package" from
https://www.rpgmakerweb.com/run-time-package
2. Unpack "RPGVXAce_RTP.zip" and run "Setup.exe"
3. Download the game from https://www.freem.ne.jp/dl/win/7629
4. Unpack "Capella_1.09.zip" and run "Game.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.
https://bugs.winehq.org/show_bug.cgi?id=49860
Bug ID: 49860
Summary: Dungeons & Dragons Online 64bit client fails to start
in wine-5.16 and 5.17
Product: Wine
Version: 5.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: sutupud(a)yahoo.com
Distribution: ---
Created attachment 68202
--> https://bugs.winehq.org/attachment.cgi?id=68202
error stacktrace
The 64bit client of DDO fails to start in wine 5.16 and 5.17.
The client starts and shows a black screen for a second, and then crashes with:
00e8:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x6760a76d
(see attached trace)
Bisecting shows the bad commit is a686759f1d7aee67b5786b72e81a4e4fcf3f3c02
If I revert that commit on top of the current master, the client works again.
Since they also have a 32bit legacy client which still works, I would guess
that the changes in dlls/ntdll/unix/signal_x86_64.c cause some different
behaviour than the old implementation did.
For DDO the workaround would be to just use the 32bit client, but there may be
other programs affected by this change.
--
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=49529
Bug ID: 49529
Summary: 5.12 regression: Wine segfaults if the +heap debug
channel is enabled
Product: Wine
Version: 5.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: subgraph93(a)gmail.com
Distribution: ---
Created attachment 67662
--> https://bugs.winehq.org/attachment.cgi?id=67662
Contains the 2 log files; the commands to produce them are provided in the
report
OS: Ubuntu 20.04
Found the bug in the Wine 5.12-devel package from winehq. Did not happen in
5.11-devel.
If WINEDEBUG=+heap (or warn+heap) is used, Wine crashes immediately after
trying to start any program. The segfault is the only line that is output,
apparently the program itself doesn't even get to start. After I upgraded from
5.11, the first thing I did in one of my prefixes was to start a program with
+heap debugging enabled (it crashed otherwise; though that's a separate issue).
The "updating your prefix" message didn't even get to appear.
Bisection points to this commit:
commit 8a169390c9ef4d8a43b604558c4194a052473c0c
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue Jun 30 12:01:37 2020 +0200
ntdll: Build with msvcrt.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--------
I tried poking around the issue with a clean prefix on 5.12-devel. Attached
logs for commands:
1) WINEDEBUG=+all wine winecfg.exe
2) valgrind --trace-children=yes wine xcopy.exe
(sorry for that second one, I'm new to Wine debugging, and that was the first
time I did anything like that; not sure it's even relevant)
As of the moment of submitting this bug report, new patches committed to Git
after the release of 5.12 do not fix the issue.
--
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=47906
Bug ID: 47906
Summary: Regression at commit
0116660dd80b38da8201e2156adade67fc2ae823 cause game
crash.
Product: Wine
Version: 4.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
Distribution: ---
Created attachment 65401
--> https://bugs.winehq.org/attachment.cgi?id=65401
Stdout of Alice Madness Return.
there are some regression at commit 0116660dd80b38da8201e2156adade67fc2ae823
causing Alice Madness Return crash at startup.
Game is completely normal before this commit.
The moving code commit is too huge, so I did not has any solution for this. I
just using old code for playing that game.
--
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.