Bug 470818

Summary:	[NVIDIA] 2nd monitor not detected upon login
Product:	[Plasma] kwin	Reporter:	mashkal2000 <mashkal2000>
Component:	multi-screen	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	nate
Priority:	NOR	Keywords:	multiscreen
Version:	5.27.5
Target Milestone:	---
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=460341
Latest Commit:		Version Fixed In:	6.0
Sentry Crash Report:

Description mashkal2000@gmail.com 2023-06-09 03:58:29 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
***


STEPS TO REPRODUCE
1. Log in

OBSERVED RESULT
Monitor is blank

EXPECTED RESULT
Monitor is not blank

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-43-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i5-13600K
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Manufacturer: ASRock
Product Name: Z690M-ITX/ax

ADDITIONAL INFORMATION
Workaround:
```
$ kscreen-doctor output.DP-2.enable
Enabling output 2
kscreen.doctor: setop exec returned KScreen::Config( 
KScreen::Output(1, "HDMI-A-3", connected enabled priority 1, pos: QPoint(0,0), res: QSize(1920, 1080), modeId: "0", scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) 
KScreen::Output(2, "DP-2", connected enabled priority 2, pos: QPoint(0,0), res: QSize(2560, 1440), modeId: "0", scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) )
$ Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
```

Comment 1 Nate Graham 2023-06-09 19:21:38 UTC

> kscreen-doctor output.DP-2.enable
By running this command, I gather that the output was *disabled* in KScreen until you ran the command, and then afterwards, it became enabled again and displayed a picture? Do I have that right?

Comment 2 mashkal2000@gmail.com 2023-06-10 05:43:31 UTC

(In reply to Nate Graham from comment #1)
> > kscreen-doctor output.DP-2.enable
> By running this command, I gather that the output was *disabled* in KScreen
> until you ran the command, and then afterwards, it became enabled again and
> displayed a picture? Do I have that right?

Yes, that's correct.

Comment 3 Nate Graham 2023-06-13 21:00:06 UTC

Thanks, it looks like Bug 460341, which was fixed in our code and verified by other NVIDIA users. So either you're hitting an edge case, or it's a different issue, or maybe the fix also relies on a specific version of the NVIDIA driver. What driver version are you using?

Comment 4 mashkal2000@gmail.com 2023-06-15 01:24:36 UTC

Here's the driver version: NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0

Comment 5 Nate Graham 2023-06-17 16:11:10 UTC

Thanks!

Comment 6 mashkal2000@gmail.com 2024-03-04 05:21:43 UTC

Seems to be fixed by plasma 6 on driver version 535. Was still broken on plasma 5 on 535.

Comment 7 Nate Graham 2024-03-04 05:33:02 UTC

Great, thanks a lot for following up!