Bug 2008353

Summary: SDDM "Breeze Fedora" theme has outdated code (the text shadow opacity in the lockscreen hasn't been updated)
Product: [Fedora] Fedora Reporter: efqs1beo
Component: sddmAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: h2d2fyzt, jgrulich, jreznik, kde-sig, me, m, ngompa13, pierluigi.fiorini, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-08 00:44:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Breeze theme
none
Breeze Fedora theme none

Description efqs1beo 2021-09-28 03:27:18 UTC 
Created attachment 1826848 [details]
Breeze theme

Created attachment 1826848 [details]
Breeze theme

Description of problem:


Version-Release number of selected component (if applicable):
34

How reproducible:


Steps to Reproduce:
1. Make sure you're using the SDDM "Breeze Fedora" theme in System Settings > Startup and Shutdown > Login Screen.
2. Lock the screen and let the computer idle until there is just the date and hour.
3. Now repeat step 1 and 2 with the "Breeze" theme.

Actual results:
Breeze Fedora text shadow opacity is different than Breeze's. The text shadow of the SDDM Breeze theme has been updated (https://bugs.kde.org/show_bug.cgi?id=436247), but it seems that this code hasn't been merged into the Breeze Fedora theme.

Expected results:


Additional info:
Operating System: Fedora 34
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.19-200.fc34.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel Core Processor (Skylake, IBRS)
Memory: 3.8 GiB of RAM
Graphics Processor: llvmpipe
Comment 1 efqs1beo 2021-09-28 03:27:46 UTC 
Created attachment 1826849 [details]
Breeze Fedora theme
Comment 2 h2d2fyzt 2021-11-25 10:00:36 UTC 
The issue still happens in v35 with both Breeze and Breeze Fedora themes.
Comment 3 h2d2fyzt 2021-11-25 10:02:15 UTC 
Correction: the issue still happens in v35 with *both* Breeze and Breeze Fedora themes.

Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.14.18-300.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 4 Ben Cotton 2022-05-12 16:26:59 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 5 Ben Cotton 2022-06-08 00:44:19 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.