Apps very slow after update from 7.0 to 7.1

Questions about Wine on Linux
Locked
vatska
Newbie
Newbie
Posts: 3
Joined: Tue Feb 15, 2022 2:32 pm

Apps very slow after update from 7.0 to 7.1

Post by vatska »

I recently updated from Wine 7.0 to 7.1 and now apps are really slow to the point of being unusable. It might be related to nvidia, but not sure how to fix it.

I have a laptop with an NVIDIA GeForce RTX 3080 mobile running Fedora 35. On Sat the 12th, I did a dnf update which included several wine packages. After the update, I started Quicken and noticed it took a long time to start and was very slow while running. I checked the logs in /var/log and noticed Xorg.0.log was very large and growing very fast. I started tailing it while Quicken was running and noticed continuous log messages related to connected/disconnected displays. The log messages are the same that's generated from manually running the "xrandr" command. eg:

Code: Select all

[276024.749] (--) NVIDIA(GPU-0): Sharp LQ156M1JW23 (DFP-5): connected
[276024.749] (--) NVIDIA(GPU-0): Sharp LQ156M1JW23 (DFP-5): Internal DisplayPort
[276024.749] (--) NVIDIA(GPU-0): Sharp LQ156M1JW23 (DFP-5): 2670.0 MHz maximum pixel clock
Next I tried a simple test and started notepad.exe using a new wine prefix. It behaved the same way, but after some experimenting I realized the seemingly continuous display related log messages in Xorg.0.log only happen when I move the mouse over certain areas of the notepad app. For example if I move the mouse over the border or the menu bar, then there's a bunch of display related connected (or disconnected) messages in Xorg.0.log. If I move the mouse within the "text" area of notepad or stop moving the mouse when it's over the window border or menu bar then the messages stop.

Here's the output from running notepad.exe:

Code: Select all

wine notepad.exe
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.1 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0068:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0068:fixme:xrandr:xrandr10_get_current_mode Non-primary adapters are unsupported.
0068:fixme:xrandr:xrandr10_get_current_mode Non-primary adapters are unsupported.
002c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0024:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0100:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0100:fixme:imm:ImeSetActiveContext (0x79c8e8, 1): stub
0100:fixme:imm:ImmReleaseContext (0001005E, 0079C8E8): stub
0068:fixme:imm:ImeSetActiveContext (0x264240, 0): stub
0068:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000264240): stub
The output errors/warnings, suggest the problem might be the NVIDIA driver, but I'm very hesitant to start making changes to the driver. This wasn't a problem with wine 7.0 and still isn't a problem with other graphics related apps like Steam games, including windows based Steam games using Proton.

What changed in 7.1 (from 7.0) that might cause this behavior and how can I fix it?


Some other system info that might be helpful:

Code: Select all

Linux Release: Fedora 35
Linux Kernel: 5.16.8-200.fc35.x86_64
NVIDIA Driver: 510.47.03
Locked