Bug 496650

Summary:	Cannot change splash screen different than Breeze
Product:	[Applications] systemsettings	Reporter:	Piotr Mierzwinski <piotr.mierzwinski>
Component:	kcm_splashscreen	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	nate, piotr.mierzwinski
Priority:	NOR
Version First Reported In:	master
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	splash screen

Description Piotr Mierzwinski 2024-11-24 23:07:04 UTC

SUMMARY
More than one week ago I noticed that my splash screen changed to default, so "Breeze". Today I decided to check this out and to try to change. Unfortunately I wasn't able to change to different than Breeze or "None". To be funny is highlighted one which is not uses (check attached screenshot).
Click on other then Breeze or None doesn't work. Usually is highlighted first one. When I click on "preview" button also happens nothing. I can navigate through the splash screens only by keyboard (arrows).

The titles of my old screen splashes disappeared. I installed new one and is visible and seem to be able to be activated.

I made short investigation and found that in new splash screen is used .json file but in old there is .desktop. Maybe this is root cause.

Seems you changed type of file what holds metadata and abandoned old format with no information in the system. Tell me please why? I think there is many uses who use old splash screens, and one day it stopped work without any explanation. For me as user this looks like not a good approach on your part. You break backward compatible with something and don't care what happen next and even don't show any information what is wrong.
IMO. This is for sure not user friendly approach.

STEPS TO REPRODUCE
1. Try to change splash screen to installed couple weeks ago, or older. One what works in Plasma 5.
2.
3.

OBSERVED RESULT
Is not possible to change splash screen

EXPECTED RESULT
Would be nice if would be possible to change splash screen to old one and at least show information what is wrong with old.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
KDE Neon Unstable

Comment 1 Piotr Mierzwinski 2024-11-24 23:19:33 UTC

Created attachment 176094 [details]
splash screen

Comment 2 Piotr Mierzwinski 2024-11-24 23:44:13 UTC

Using metadata.json from splash screen adapted to Plasma 6 ("AccreationDisc") - here I replaced anly couple names and replacing "source:" in Splash.qml I made that my all old splash screens started work.

Comment 3 Nate Graham 2024-11-25 21:22:37 UTC

> Seems you changed type of file what holds metadata and abandoned old format with no information in the system.

What are you talking about exactly?

Did you by any chance just upgrade to Plasma 6, and these splash screens are leftover from the time when you were using Plasma 5?

Comment 4 Piotr Mierzwinski 2024-11-30 00:08:07 UTC

(In reply to Nate Graham from comment #3)
> > Seems you changed type of file what holds metadata and abandoned old format with no information in the system.
> 
> What are you talking about exactly?
I mean that with my old splashscreen (in its directory) was placed .destkop file, and in new (lately installed) there is .json
 
> Did you by any chance just upgrade to Plasma 6, and these splash screens are
> leftover from the time when you were using Plasma 5?

I updated Plasma to version 6 long time ago. I don't remember which one version I used as first, if it was 6.0.x or 6.1. Anyway since thouse time all my splash screens were working well, and one or two weeks ago (sorry don't remember) just stopped. As I described above, I discovered difference between old and new version and applied it and in result all started work.

< and these splash screens are leftover from the time when you were using Plasma 5?
Yes, they are. To be clear I just copied them from other distribution, which I used with Plasma 5

Comment 5 Nate Graham 2024-12-10 21:00:13 UTC

Then I think this is expected. It was communicated that Plasma 5 content needed to be updated to work with Plasma 6; old Plasma 3 add-ons copied over are not expected to work automatically.

Comment 6 Piotr Mierzwinski 2025-02-20 22:26:00 UTC

(In reply to Nate Graham from comment #5)
> Then I think this is expected. It was communicated that Plasma 5 content
> needed to be updated to work with Plasma 6; old Plasma 3 add-ons copied over
> are not expected to work automatically.

OK. Seems I missed this.