Bug 448336

Summary:	Monitor Not Showing Login Screen & Fonts Don't Display Properly if Monitor is Turned on after PC
Product:	[Plasma] plasmashell	Reporter:	cachandler
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate, plasma-bugs
Priority:	NOR
Version:	5.23.5
Target Milestone:	1.0
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description cachandler 2022-01-12 19:14:32 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

If the monitor is powered on after the PC is already turned on, the monitor doesn't receive a signal until the user is logged in (until this time, it shows a black screen). When the user does log in, the system font displays too small (possibly because it uses some kind of default value, rather than the value that should be used for my monitor's resolution).
This issue is resolved by turning on the monitor before powering on the PC, or restarting the PC once this issue has been noticed.

***

STEPS TO REPRODUCE

1. Turn on PC.
2. Turn on monitor once the PC has already reached the login screen. (Monitor won't display an image)
3. Login. (Fonts are too small.)

OBSERVED RESULT

The monitor receives no signal until the user is logged in. Once logged in, the monitor displays the screen, but the font is too small.

EXPECTED RESULT

The monitor would show the login screen. Once logged in, the fonts would be the appropriate size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Graphics Platform: X11
Monitor Resolution: 2560x1440

--------------------------------------------------

Here are a couple screenshots of the font rendering issue (unfortunately, I cannot take a screenshot of the monitor refusing to turn on until the user logs in): https://imgur.com/a/1wPvs9x

Comment 1 Nate Graham 2022-01-13 21:18:10 UTC

1. What GPU hardware are you using?
2. Does it happen in the Wayland session
3. Can you try the Plasma 5.24 beta and see if it's fixed there? A bunch of monitor-related fixes went in recently.

Comment 2 cachandler 2022-01-13 21:59:55 UTC

(In reply to Nate Graham from comment #1)
> 1. What GPU hardware are you using?
> 2. Does it happen in the Wayland session
> 3. Can you try the Plasma 5.24 beta and see if it's fixed there? A bunch of
> monitor-related fixes went in recently.

1. I am using an Nvidia 2070 Super.
2. I haven't tried Wayland yet, but I heard that it isn't stable enough for general use with Nvidia cards in KDE. Is that no longer the case? In any case, I'll see if the issue persists on Wayland later today.
3. I'd try the 5.24 beta if I could, but I don't think Manjaro will let me. Even on the unstable branch, it only has 5.23.5-1 as the newest version.

Comment 3 cachandler 2022-01-13 23:06:55 UTC

In regards to Wayland, the monitor still doesn't receive a signal while on the login screen. However, the font size issue (too small when I turn on my monitor after the pc has reached the login screen) seems to be present across the board, as the Wayland text is always too small with the given font size.

Comment 4 Bug Janitor Service 2022-01-28 04:37:41 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 5 cachandler 2022-02-28 06:04:58 UTC

This issue seems to have been resolved with KDE 5.24.