Bug 500437 - I noticed after the update to KDE Plasma 6.3 that after logging in, I had a black screen rather than my desktop. Further investigation by using an external monitor revealed that switching my display preferences from ICC to "Built In" allowed me to see the
Summary: I noticed after the update to KDE Plasma 6.3 that after logging in, I had a b...
Status: RESOLVED DUPLICATE of bug 499789
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-19 22:23 UTC by Marc Sitkin
Modified: 2025-02-20 15:27 UTC (History)
1 user (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 Marc Sitkin 2025-02-19 22:23:20 UTC
KDE Plasma 6.3 -custom display ICC broken

SUMMARY

I noticed after the update to KDE Plasma 6.3 that after logging in, I had a black screen rather than my desktop. Further investigation by using an external monitor revealed that switching my display preferences from ICC to "Built In" allowed me to see the DE on my internal display, and it held after a reboot. Unfortunately, the "Built In" color is not suitable for photo editing.


STEPS TO REPRODUCE
1. Boot system and login
2. Observe black screen
3. plug in external monitor to switch to "built in" color in display settings

OBSERVED RESULT
Corrected black screen after login

EXPECTED RESULT
To be able to log in and see desktop using ICC color profile (which previously worked fine)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Aurora 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Hardware is Framework 13 AMD Ryzen 7040 series 64 GB Ram w Radeon 780M Graphics
Comment 1 Martin Riethmayer 2025-02-20 15:27:58 UTC

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