Bug 452753 - Issues with KDE Plasma under different video cards
Summary: Issues with KDE Plasma under different video cards
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-19 05:18 UTC by Mihai Sorin Dobrescu
Modified: 2023-09-06 10:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mihai Sorin Dobrescu 2022-04-19 05:18:18 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

I have tried successively the display with two video sources:
- NVIDIA GeForce GTX 1060 6GB
-  Intel® UHD Graphics 750 (integrated into i7-11700K)

I am aware that causes are multiple, due to the current stack, but some seem KDE/Plasma related.
I describe all I faced.

STEPS TO REPRODUCE
1.  Install Nvidia video card and integrated Intel GPU into CPU
2. Plug the same display, one display,  in one or another source

OBSERVED RESULT

1. Simply running KDE/Plasma and moving the plug from one output to another does not work. There is no display output until the system is shutdown, move the plug, start again. No plug and play.
2. Image quality - as usual, the integrated Intel GPU has a slightly dull image by comparison to Nvidia, in the pre-KDE phase the console looks having even ghosting and artifacts - could be i915 driver selected by the kernel
3. No Plasma effects under Intel - could not enable the effects at all (I use Wobbling Windows and Magic Lamp)
4. Logitech mice. I use Solaar too, but regardless that, without setting mouse speed at all, the experience differs:
- with Nvidia it's too fast, as well the pointer and the scroll, in Dolphin and Firefox. VLC is worst in this regard, seems to set the volume in almost 50% steps.
- with Intel's is like pedaling in cheese everywhere. It's slower that under Nvidia when I disable smooth scrolling and get a slower speed.
5. I have enabled session restoring and use at least 4 Dolphin instances with several tabs each. At closing time, they ask whether to close the multiple tabs opened. This is an expected behavior, although I'd prefer to not pop those messages at shutdown/logoff time. But:
- under Nvidia they wait a few seconds, then proceed to shut down/logoff, which is fine!
- under Intel they wait indefinitely, which is a problem in my eyes.

EXPECTED RESULT

I'd like to:
1. Be possible to move the display from one to another output without restarting
2. Have desktop effect under this integrated card too as it is capable
3. Save and close the session and to have the option do not display all those popup messages or wait indefinitely. I am aware of the fact that some apps must signal and block closing the session, this being actually necessary for some applications.

SOFTWARE/OS VERSIONS

Operating System: MocaccinoOS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.15.32-mocaccino (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700K @ 3.60GHz
Memory: 61.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

ADDITIONAL INFORMATION

Please excuse me for adding all these here, but if some features/bugs are identified, I rely on the team to add the atomic tasks as I can't really tell if the causes are from the same or from different KDE/Plasma parts.
Comment 1 Nate Graham 2022-04-19 16:10:03 UTC
Can you try again with the Wayland session in Plasma 5.24? I believe it does much much better with multiple GPUs compared to the X11 session in Plasma 5.23.
Comment 2 Mihai Sorin Dobrescu 2022-04-19 16:23:12 UTC
Not sure if I can, last time was a problem with non-KDE apps integration, like windows without decorations and impossible to move or resize.
Comment 3 Bug Janitor Service 2022-05-04 04:35:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Mihai Sorin Dobrescu 2022-05-04 14:44:55 UTC
Hello, Nate, I've upgraded since last time to:

Operating System: MocaccinoOS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.35-mocaccino (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700K @ 3.60GHz
Memory: 61.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Proprietary nVidia driver version: 470.103.01

The problems are the same under Wayland, with these additional ones:
- Could not start Wayland session under nVidia, only with Intel.
- Yakuake expands in the middle of the screen.
- Under Intel, could not shutdown the system until I have logged into console and issued `poweroff`.
- The mouse moved more fragmented, being jumpy
Comment 5 Mihai Sorin Dobrescu 2022-05-04 17:10:15 UTC
Bonus: switching from X11 to Wayland, kept Plasma session, but switching back to X11 has lost Plasma session, meaning all apps to be reopened and restored at Plasma startup.
Comment 6 David Edmundson 2023-09-06 10:38:14 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.