Bug 406099

Summary: Second monitor not enabled by default
Product: [Plasma] KScreen Reporter: Nancy Hand <n_hand>
Component: commonAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, nnc.hnd, plasma-bugs
Priority: NOR    
Version: 5.22.4   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=400173
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: configure monitor screen

Description Nancy Hand 2019-03-31 23:09:14 UTC
Created attachment 119188 [details]
configure monitor screen

SUMMARY
I have 2 monitors. Until about a week ago both worked fine under KDE/Plasma. Then the secondary one suddenly went black. If I boot into Gnome, both monitors work and can be configured (primary/secondary). Under Plasma the secondary monitor is grayed out. 

STEPS TO REPRODUCE
1. Boot into Plasma with both monitors turned on
2. Mid-way through KDE-splash display, secondary monitor goes blank
3. Log out, log into Gnome, both monitors are fine

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 29/Plasma 5
(available in About System)
KDE Plasma Version:  5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Kernel 5.0.4, 64bit
Comment 1 Nate Graham 2021-08-16 21:56:52 UTC
Seems a bit like Bug 400173.

Is this still happening in Plasma 5.22, by any chance?
Comment 2 Nancy Hand 2021-08-17 01:49:58 UTC
Still happens occasionally - generally with a kernel upgrade. One kernel will be fine, the next might have problems, then clean for 4-5 kernel updates before it gives out again.
Comment 3 Nate Graham 2021-08-17 01:58:07 UTC
Huh, thanks.
Comment 4 Nate Graham 2022-11-08 22:13:58 UTC
It sounds like this is actually a kernel issue, and while GNOME may be more resilient against it (good!), ideally it would be fixed in the kernel.

The next time it happens, can you paste the output of `kscreen-doctor-o`? Thanks
Comment 5 Nancy Hand 2022-11-10 19:01:35 UTC
Such timing:

~]$ kscreen-doctor --outputs
Output: 445 DVI-I-0 enabled connected  DVI Modes: 446:1280x1024@60! 447:1280x1024@75* 448:1152x864@75 449:1024x768@75 450:1024x768@70 451:1024x768@60 452:800x600@75 453:800x600@72 454:800x600@60 455:800x600@56 456:640x480@75 457:640x480@73 458:640x480@60 Geometry: 1920,28 1280x1024 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 459 DVI-I-1 disabled disconnected  DVI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 460 HDMI-0 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 461 DP-0 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 462 DP-1 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown 
Output: 463 DVI-D-0 enabled connected primary DVI Modes: 446:1280x1024@60 448:1152x864@75 450:1024x768@70 451:1024x768@60 454:800x600@60 455:800x600@56 458:640x480@60 464:1920x1080@60*! 465:1440x900@60 466:1280x800@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary


It's been interesting - this was an issue in F34 but not in F35, then resurfaced with F36.
Comment 6 Nate Graham 2022-11-14 18:43:47 UTC
Thanks. And which port is the non-functional monitor plugged into? Which port is the working monitor plugged into?
Comment 7 nancy 2022-11-14 19:09:31 UTC
The non-functioning monitor is plugged into the first port. On boot up the system reads this as the primary monitor. Within Fedora I have this set as the secondary monitor. It's an older VGA monitor.

The working monitor is plugged into the second port. On boot the system reads this as an "extra" monitor. Within the OS this is set to the primary monitor. This is a somewhat newer DVI monitor.

I'd thought they had different connectors on the video board but in looking at it just now, they both have DVI connections on the board.
Comment 8 Nate Graham 2022-11-15 17:43:23 UTC
So they are both plugged into DVI ports on your graphics card?

And if you manually enable the disabled monitor on the Display Configuration page, it gets disabled again later?
Comment 9 Nancy Hand 2022-11-15 19:30:53 UTC
Both are plugged into DVI ports.

On boot: The monitor that normally displays the login screen is blank. Almost as if not receiving any data but, if I hit return and enter my password, login continues and both monitors display the startup screens. Then the images for the two monitors change over to their "correct in KDE" locations. When looking at the Display Configuration the VGA monitor shows enabled as the secondary monitor and the DVI monitor shows as the primary.
Comment 10 Nate Graham 2022-11-16 17:58:53 UTC
Okay, now if you reboot again, do both monitors get enabled *after login* as expected, or does one of them fail to display again?
Comment 11 Nancy Hand 2022-11-16 18:12:47 UTC
The next reboot everything works as it's supposed to. 

So: apply patches, reboot, login screen is invisible. Login blind, both screens appear in KDE. Reboot again, login screen is visible again.

Continues to work properly through several patches, then the login screen goes invisible. Usually this happens after a new kernel is applied. The most recent one was not associated with a kernel update. There were 5 or so library (I think) updates.
Comment 12 Nate Graham 2022-11-16 18:45:20 UTC
Thanks for all the info. Here's what I think is happening:

1. For some reason, the monitor in question does not get enabled by default. If you manually enable it, it works.
2. Sometimes, kernel upgrades cause the monitor's EDID, serial number, or connected port name to change, so KScreen inappropriately detects it as a new screen, which triggers the original bug of it not being enabled by default all over again.

The first issue is probably more easily fixable so let's use this bug report to track it. The second issue is much more challenging to fix in KScreen, but we're working on it for Plasma 5.27.

What Plasma version are you using now?
Comment 13 Bug Janitor Service 2022-12-01 05:13:56 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 14 Nancy Hand 2022-12-01 18:51:40 UTC
current Plasma version is 5.26.3
Comment 15 Nate Graham 2022-12-01 20:18:37 UTC
Are you using an NVIDIA GPU, by any chance?
Comment 16 Nancy Hand 2022-12-02 19:00:11 UTC
yes
nvidia-gpu-firmware v. 20221109 release 144.fc36
kmod-nvidia-6.0.8-200.fc36.x86_64 kernels
Comment 17 Nate Graham 2022-12-02 20:22:59 UTC
Aha!

*** This bug has been marked as a duplicate of bug 460341 ***