Bug 1404227 - Wrong Fedora 24 KDE splash screen after upgrade
Summary: Wrong Fedora 24 KDE splash screen after upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: f24-kde-theme
Version: 24
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 12:29 UTC by Henri
Modified: 2016-12-14 22:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 13:56:06 UTC
Type: Bug


Attachments (Terms of Use)
splash preview of org.fedoraproject.fedora.twenty.four (46.23 KB, image/png)
2016-12-14 08:34 UTC, Henri
no flags Details

Description Henri 2016-12-13 12:29:04 UTC
Description of problem: wrong splash directory after upgrade of f24-kde-theme-core package


Version-Release number of selected component (if applicable):
f24-kde-theme-core-5.8.4-1.f24.noarch

How reproducible:
Wrong Fedora 24 KDE splash screen AFTER DNF UPGRADE (december 7)

Steps to Reproduce:
1. n.a.
2. n.a.
3. n.a.

Actual results:
Wrong Fedora 24 KDE splash screen after upgrade

Expected results:
KDE splash screen belonging to org.fedoraproject.fedora.twenty.four

Additional info:
Using VANILLA F24 KDE spin (i.e. no changes!) After upgrade (december 7), 
pkg f24-kde-theme-core-5.7.5-2.fc24.x86_64 had been replaced by pkg f24-kde-theme-core-5.8.4-1.fc24.noarch.
The latter pkg has a wrong splash directory at /usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents.

As promised by the previews directory, the KDE splash screen of Fedora 24 has a PROGRESS BAR. The progress bar had been replaced by a BUSY INDICATOR after the upgrade (plus a black colored background). To repair this _mistake_, I replaced the splash directory by the one I got from an earlier version of the package, viz. f24-kde-theme-core-5.6.4-1.fc24.x86_64.rpm

Although not a show-stopper, I filed this mistake as a bug, because I have not seen a correction of this mistake in the last few days.
--

Comment 1 Rex Dieter 2016-12-13 13:56:06 UTC
It's not a mistake, kde/plasma upstream changed the breeze splash theme (and the updates you see here reflect that)

Comment 2 Henri 2016-12-13 17:10:48 UTC
(In reply to Rex Dieter from comment #1)
> It's not a mistake, kde/plasma upstream changed the breeze splash theme (and
> the updates you see here reflect that)

Not a mistake? I disagree. Okay, Rex, you are better informed than I am in this matter. However the preview for Fedora Twenty Four STILL shows the progress bar, not the busy indicator (system settings > workspace theme, tab splash screen).
--

Comment 3 Rex Dieter 2016-12-14 04:19:12 UTC
OK, what's wrong now is the preview (which wasn't updated to match)

Comment 4 Henri 2016-12-14 08:34:15 UTC
Created attachment 1231495 [details]
splash preview of org.fedoraproject.fedora.twenty.four

Path to the splash preview file:
/usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/previews/splash.png

Comment 5 Henri 2016-12-14 09:02:31 UTC
(In reply to Rex Dieter from comment #3)
> OK, what's wrong now is the preview (which wasn't updated to match)

To answer your question, I have attempted to attach the splash preview that is shown on my system ... The splash *preview* on my system still shows the splash screen that has a progress bar ... (however when testing it, the splash screen of "breeze" is displayed).

As far as I can tell, the Fedora KDE SIG deliberately? choose a splash screen that is different from the one that "breeze" has ... That is why I assert that the splash preview of *.four is correct and the splash screen (i.e. directory) of *.four is WRONG.

I know that you say different and we can leave the matter as is (especially when I am the only one that is complaining about this).

What matters is that the issue has been documented now for future reference.
--

Comment 6 Henri 2016-12-14 12:12:44 UTC
(In reply to Henri from comment #5)
> (In reply to Rex Dieter from comment #3)
> > OK, what's wrong now is the preview (which wasn't updated to match)
> 
> To answer your question, I have attempted to attach the splash preview that
[snip]

> I know that you say different and we can leave the matter as is (especially
> when I am the only one that is complaining about this).

s/when/if/
--

Comment 7 Rex Dieter 2016-12-14 13:39:16 UTC
Fedora Twenty Four is exactly Breeze, except for a different background/wallpaper.

The preview *picture* has not be updated to match 5.8 style (and may never be).  If you're saying the animated (preview) version looks different, that is odd certainly, but I cannot reproduce that.

Comment 8 Henri 2016-12-14 22:19:36 UTC
(In reply to Rex Dieter from comment #7)
> Fedora Twenty Four is exactly Breeze, except for a different
> background/wallpaper.
> 
> The preview *picture* has not be updated to match 5.8 style (and may never
> be).  If you're saying the animated (preview) version looks different, that
> is odd certainly, but I cannot reproduce that.

Allright, Rex. My apologies. Apparently I am NOT using the correct terminology.

laf=/usr/share/plasma/look-and-fool

The files below $laf/org.fedoraproject.fedora.twenty.four are from

 - rpmpkg f24-kde-theme-core and
 - rpmpkg f24-kde-theme

The files below $laf/org.kde.breeze.desktop are from

 - rpmpkg plasma-workspace

Not the same files. That is all I am saying ...

With regard to the preview *picture* and the ANIMATED splash screen, there is NO disagreement between us:

 - the preview *picture* of *.hour shows the progress bar (and will NOT be
   updated according to you)
 - the ANIMATED splash screen of *.four shows the busy indicator in front of
   a black colored background (apparently "cloned" from breeze)

Bottom-line: I filed a bug, because the preview *picture* of *.four did NOT 
match the ANIMATED splash screen of *four.

However you were already aware of this discrepancy.

Case closed.
--


Note You need to log in before you can comment on or make changes to this bug.