Bug 30827 - ssdm default splash screen can not revert to default
Summary: ssdm default splash screen can not revert to default
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-07 19:48 CEST by david Cossé
Modified: 2022-09-08 22:30 CEST (History)
3 users (show)

See Also:
Source RPM: mageia-breeze-sddm-theme
CVE:
Status comment:


Attachments

Description david Cossé 2022-09-07 19:48:56 CEST
Description of problem:
Selecting an other plasma SSDM splash screen and back again to default Breeze from Magia does not work.

Version-Release number of selected component (if applicable):
mageia-breeze-sddm-theme-1-3bdk_mga8.noarch

How reproducible:

open plasma settings
change SSDM splach sreen from Breeze from Mageia to an other one
apply change
log out/in
selected SSDM splash sreen is the one selected
open plasma settings
change SSDM splash screen to Breeze from Mageia
log out/in
it is the Breeze splach screen that is displayed
david Cossé 2022-09-07 19:49:05 CEST

CC: (none) => saveurlinux

Barry Jackson 2022-09-07 19:54:14 CEST

Summary: ssdm default splash screen can npt revert to default => ssdm default splash screen can not revert to default
CC: (none) => zen25000

Comment 1 Marja Van Waes 2022-09-08 22:30:15 CEST
(In reply to david Cossé from comment #0)
> Description of problem:
> Selecting an other plasma SSDM splash screen and back again to default
> Breeze from Magia does not work.
> 
> Version-Release number of selected component (if applicable):
> mageia-breeze-sddm-theme-1-3bdk_mga8.noarch
> 

That's not a package that is distributed by Mageia, is it from Blogdrake? If so, it is better to contact the packager there.

Anyway, we cannot patch packages that weren't created in our Build System.

CC: (none) => marja11
Resolution: (none) => INVALID
Status: NEW => RESOLVED


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