https://bugs.winehq.org/show_bug.cgi?id=48549
Bug ID: 48549
Summary: Arma Cold War Assault: Cursor stuck at low fps since
Wine 5.0-rc6
Product: Wine
Version: 5.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: superemppu+winehq(a)live.fi
Distribution: Ubuntu
Game: Arma Cold War Assault
Wine versions: staging 5.0-rc6 and later
OS: Ubuntu Linux 18.04
Symptoms:
In the game the cursor will get stuck at one point on the screen if I move the
mouse quick enough on low enough fps. It is very noticeable below 10 fps. This
is a regression from Wine 5.0-rc5 and earlier, where the cursor moved normally.
How to reproduce:
1. Get Arma Cold War Assault.
2. Limit the fps to 10 in some way or use a slow computer.
- I could reproduce this issue on a powerful computer using this fps
limiter: https://github.com/ThirteenAG/d3d8-wrapper/releases Set FPSLimit = 10
in d3d8.ini and start the game with WINEDLLOVERRIDES="d3d8=n,b".
3. Start the game.
4. Move your mouse fast in the main menu.
5. You should see the cursor stuck at one point.
--
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=42038
Bug ID: 42038
Summary: Cannot scroll documents being compared in winmerge
(Followup to bug 20695)
Product: Wine
Version: 2.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Bug #20695 got closed with wine-1.9.7.
It really fixes the problem when opening two existing files.
(e.g. by menu File - Open)
But if one opens just a new empty file comparison and pastes
the two file contents there the scrollbars do not work.
(e.g. by menu File - New)
(Even without pasting the scrollbars should be moveable a little bit.)
This started like the original bug between 1.1.16-pol and 1.1.17-pol
Version 1.9.7-pol shows also the problem as does 2.0-rc2-winehq.
Can this someone confirm?
--
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=48484
Bug ID: 48484
Summary: winecfg doesn't allow disabling Desktop Integration
for Downloads
Product: Wine
Version: 5.0-rc6
Hardware: x86
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
On winecfg you can disable the symlink inside a WINEPREFIX, but there is no
option to disable the mapping for "Downloads".
--
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=48646
Bug ID: 48646
Summary: 安装qq音乐后启动时报错
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: even0306(a)foxmail.com
Distribution: ---
Created attachment 66504
--> https://bugs.winehq.org/attachment.cgi?id=66504
这是wine自动获取的文件
qq音乐安装完后,启动的时候报错,忽略报错后软件还在运行,但首页加载不出任何歌曲
--
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=48018
Bug ID: 48018
Summary: QuickTime 7.0.x installer fails
Product: Wine
Version: 4.18
Hardware: x86-64
URL: http://www.oldversion.com/download/quicktime704.exe
OS: Linux
Status: NEW
Keywords: download, Installer, regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 65552
--> https://bugs.winehq.org/attachment.cgi?id=65552
Wine 4.18 console log
During installation, the installers for QuickTime 7.0.3 and 7.0.4 hit an
unhandled exception under Wine and Staging 4.18.
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x00110572).
This is a regression as they used to work fine.
I need to make some space on disk before I can set up an environment to run a
bisect, so will update.
$ sha1sum quicktime70*
00cada67cca554d53993ed51aa3cc14caf45c1cd quicktime703.exe
fadbddbccaad9b0e79a66231399a2ce6cfc5409d quicktime704.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=48371
Bug ID: 48371
Summary: Home Designer Suite 21.3.1.1x64 reports "Error
#272000009 A serious error occurred (SEH)."
Product: Wine
Version: 5.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 74.schutt(a)gmail.com
Distribution: ---
Created attachment 66120
--> https://bugs.winehq.org/attachment.cgi?id=66120
Home Designer message log when run on Wine
I am attempting to run Home Designer Suite version 21.3.1.1x64 on Wine.
Immediately after starting it and supplying a valid product key, I get a
popup reporting:
c:\p4sync\dev\releases\21\chief\cacommon\error\artexception.cpp(146): Error
#272000009
"A serious error occurred (SEH). Please contact Chief Architect Technical
Support with steps to reproduce.
"
Note that the program continues to run, and I can shut it down normally.
This page:
https://www.chiefarchitect.com/support/article/KB-00802/troubleshooting-exc…
says I should ensure my system meets minimum requirements and is fully up to
date. E.g. they want a graphics card with 1 GB memory and support for OpenGL
>= 3.3, which I have.
Home Designer writes a report of its execution, and there I found that it
reports the characteristics that it probed for the system it is running on.
Here I found that it probed "OpenGL VRam: 0" and "OpenGL GPU Count: 0". I've
attached this log as 'wine-Message Log.txt'.
When I run that same Home Designer binary on an up-to-date Windows 10 system,
it starts up without reporting a serious error, and its execution log shows
non-zero values for "OpenGL VRam" and "OpenGL GPU Count". I've attached this
log as 'real-Windows10-Message Log.txt'.
The terminal output from Wine is attached as 'run.log'.
--
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=48648
Bug ID: 48648
Summary: Gothic II Night of the Raven:unhandled exception in
Wine 5.2
Product: Wine
Version: 5.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chebanenkoigor93(a)gmail.com
Distribution: ---
Created attachment 66507
--> https://bugs.winehq.org/attachment.cgi?id=66507
Backtrace.
Unhandled exception in Wine 5.2 in Gothic II Night of the Raven,game gives you
it, when you start new 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.
https://bugs.winehq.org/show_bug.cgi?id=48480
Bug ID: 48480
Summary: dlls/krnl386.exe16 - thunk.c argument logic incorrect
for CallProcEx32W16
Product: Wine
Version: 5.0-rc6
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dirk.niggemann(a)gmail.com
CallProcEx32W16 takes a 'nrofargs' argument which may have the hight bit set by
the caller (CPEX_DEST_CDECL). Internally the function processes nrofargs in a
for loop but does not clear the high bit before looping.
This line (2475):
for (i=0;i<nrofargs;i++)
This needs to be changed to support correct argument counting to:
for (i=0;i<(nrofargs & ~CPEX_DEST_CDECL);i++)
Otherwise this routine crashes when called with CPEX_DEST_CDECL set.
--
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=48561
Bug ID: 48561
Summary: Cadence Allegro Professional 16.6 crashes at startup
Product: Wine
Version: 5.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
When attempting to launch Cadence Allegro Professional* on Wine 5.0 staging,
the application loads and checks out the network license, but immediately
generates an internal fault and pops up a dialog to that effect. Dismissing
the dialog box exits the application (thankfully it returns the network license
cleanly at that point, otherwise debugging would be quite miserable).
This behavior was observed on all tested Wine versions starting with 3.0. 4.1
and 4.12 were also tested with the same results, as was both the OpenGL and
non-OpenGL version of the Allegro software.
* We hold a current network license for this package, and are looking to
migrate away from effectively airgapped (isolated license-only network) XP
systems for this software. My understanding is that the licensed version,
versus the trial / standalone read-only version, has received no testing up
until this point on Wine.
--
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=48386
Bug ID: 48386
Summary: Some CPU features are not reported for Intel CPU
(Detroit: Become Human is affected)
Product: Wine
Version: 5.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: gofmanp(a)gmail.com
Distribution: ---
Created attachment 66146
--> https://bugs.winehq.org/attachment.cgi?id=66146
ntdll: Detect more processor features on Intel CPU.
Split off from bug #48291.
The application reads CPU features from shared user data area and requires or
benefits from certain CPU features. Some features from CPUID level 0x80000001
are currently recognized for AMD only while they are available on Intel as
well.
--
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.