LogosLinuxInstaller icon indicating copy to clipboard operation
LogosLinuxInstaller copied to clipboard

Slow Non-Responsive UI

Open joshuabeny1999 opened this issue 1 year ago • 9 comments

Suddendly on my side the isntalled app with alpha 3 is not working properly anymore. I can't really use it due it really laggy. If i try to enter text for example as note or in the sermon editor it takse a few seconds until input appears.

I tried to disable hardware acceleration and also reinstalled everything.

What could causing that issue?

my workaround currently is using the web version but this won't work offline and does not have all features

joshuabeny1999 avatar Mar 11 '24 18:03 joshuabeny1999

In general this application has no impact on Logos's performance. The only way that would happen is if we didn't install some DLL or if through the app you changed your Wine version.

We would need more information. If you can provide logs, that would be a good starting point.

thw26 avatar Mar 11 '24 18:03 thw26

How can i provide you with logs? Where are they?

joshuabeny1999 avatar Mar 11 '24 18:03 joshuabeny1999

You can find the logs in:

~/.local/state/Logos_on_Linux/Logos_on_Linux.log

thw26 avatar Mar 11 '24 18:03 thw26

install.log Logos_on_Linux.log

Here you go

joshuabeny1999 avatar Mar 11 '24 19:03 joshuabeny1999

These lines from the log file seem problematic (L107+):

2024-03-11 18:31:31 INFO: 00c4:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2.
2024-03-11 18:31:31 INFO: 00c4:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY1".
2024-03-11 18:31:31 INFO: 0128:err:winediag:wined3d_dll_init Disabling 3D support.

The "Disabling 3D support" is repeated more later, nearer the end. I could imagine that lack of 3D support would cause major slowdowns in the UI. Maybe there's something that was done with the display settings (either in wine or in Logos) that can be reverted? Or maybe you changed screens/monitors, and the recent one is not compatible somehow?

n8marti avatar Mar 12 '24 04:03 n8marti

HelloI disabled hardware accelerate just for testing. Reevabledmit but not solve it. What I did is set the scaling in the app to 200% else it was to readable. Butthat was also before. The only thing which differs is I set the GPU to nvidia only instead using also the intel GPU. But I don't think that could be the issue due it more powerful and it also worked before with that setting. Kind regardsJoshuaAm 12.03.2024 um 05:47 schrieb n8marti @.***>: These lines from the log file seem problematic (L107+): 2024-03-11 18:31:31 INFO: 00c4:err:system:NtUserChangeDisplaySettings Changing L"\\.\DISPLAY1" display settings returned -2. 2024-03-11 18:31:31 INFO: 00c4:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\.\DISPLAY1". 2024-03-11 18:31:31 INFO: 0128:err:winediag:wined3d_dll_init Disabling 3D support.

The "Disabling 3D support" is repeated more later, nearer the end. I could imagine that lack of 3D support would cause major slowdowns in the UI. Maybe there's something that was done with the display settings (either in wine or in Logos) that can be reverted?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

joshuabeny1999 avatar Mar 12 '24 06:03 joshuabeny1999

I believe I have the same issue. UI is unusable slow. For example selecting text or just scrolling is laggy.

Notes:

  1. GPU & CPU usage not over 30%
  2. On windows performance is a non-issue
  3. Performance improves the smaller the window size
  4. Larger books like the bible are slower than smaller books

Logs

Logos.log LogosError.log oudedetai.log wine.log

Config

"LLI_LATEST_VERSION": "4.0.0-beta.4",
"TARGETVERSION": "10",
"TARGET_RELEASE_VERSION": "38.0.0.0578",
"WINEBIN_CODE": "Recommended",
"WINECMD_ENCODING": "437",
"WINE_EXE": "data/bin/wine-devel_9.19-x86_64.AppImage",
"current_logos_version": "38.1.0.2",
"logos_release_channel": "stable"

jbytes1027 avatar Dec 30 '24 00:12 jbytes1027

I noticed I also have the following line:

0134:err:winediag:wined3d_dll_init Disabling 3D support.

I also have an NVIDIA GPU, but am rendering with Intel's integrated graphics.

jbytes1027 avatar Dec 30 '24 00:12 jbytes1027

I don't know if this thread is still used, but I have the same issue and also a Nvidia GPU. I wonder if it is an Nvidia GPU problem?

UPDATE: I have solved it somewhat when I change the resolution to 1920x1080p insteed of 3840x2160p. It's usable in a lower resolution, but not perfect.

SirCallePacman avatar Aug 08 '25 18:08 SirCallePacman