[SRU] Change to plasma causes login splash screen defaults to propogate differently

Bug #2007614 reported by Erich Eickmeyer
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntustudio-default-settings (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
High
Erich Eickmeyer
Lunar
Invalid
Undecided
Unassigned

Bug Description

[ Impact ]

It is questionable whether or not this is a regression because this is caused by point updates to plasma, but default settings are now being set in ~/.config/kdedefaults based on the default theme which may or may not include the login splash.

The splash is included in the look-and-feel (global) theme "Ubuntu Studio" (org.ubuntustudio.desktop) but the default look-and-feel theme is "Ubuntu Studio Dark" (org.ubuntustudio-dark.desktop). Beginning in one of the point releases of plasma 5.24, the ~/.config/kdedefaults started setting ~/.config/kdedefaults/ksplashrc to point to the default look-and-feel theme's splash as opposed to the already prescribed splash as set in ksplashrc in the $XDG_CONF_DIRS path. Since org.ubuntustudio-dark.desktop does not have a splash, this returns an empty value after install and the login splash reverts to the default plasma login splash as opposed to the Ubuntu Studio branded splash.

The reason this is questionable as to if this is a regression in Plasma is that it may be by design; that a splash screen is now expected in the default theme. However, this doesn't appear to be the case in later versions, e.g. Plasma 5.26 and Plasma 5.27, although the method for setting defaults has changed in these later versions to include ways to set for Wayland.

[ Test Case ]

* Download and run the Ubuntu Studio 22.04 Jammy Daily .iso image
  - Splash will be the default Plasma splash and NOT the Ubuntu Studio splash. This is not desired.

[ What Could Go Wrong ]

* There will be *two* entries for the same splash theme, one for Ubuntu Studio and one for Ubuntu Studio Dark. Without removing the one that says "Ubuntu Studio" or redoing the entire defaults to make the dark theme "Ubuntu Studio" and the lighter one "Ubuntu Studio Light" considering there's already an "Ubuntu Studio Light", this will not be possible to avoid.

[ Other Information ]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntustudio-default-settings 22.04.26.2 [modified: usr/share/plasma/look-and-feel/org.ubuntustudio-dark.desktop/contents/defaults usr/share/ubuntustudio/kf5-settings/kdeglobals usr/share/ubuntustudio/kf5-settings/ksplashrc]
ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17
Uname: Linux 5.19.0-1017-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu Feb 16 13:09:10 2023
InstallationDate: Installed on 2023-02-16 (0 days ago)
InstallationMedia: Ubuntu-Studio 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230216.2)
PackageArchitecture: all
SourcePackage: ubuntustudio-default-settings
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
Changed in ubuntustudio-default-settings (Ubuntu):
status: New → In Progress
Changed in ubuntustudio-default-settings (Ubuntu Lunar):
status: In Progress → Invalid
Changed in ubuntustudio-default-settings (Ubuntu Jammy):
importance: Undecided → High
assignee: nobody → Erich Eickmeyer (eeickmeyer)
Changed in ubuntustudio-default-settings (Ubuntu Lunar):
importance: High → Undecided
assignee: Erich Eickmeyer (eeickmeyer) → nobody
Changed in ubuntustudio-default-settings (Ubuntu Jammy):
status: New → In Progress
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2007614

tags: added: iso-testing
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

I was unable to reproduce this on my test of the daily ISO image. I'll do another test just to be sure, though.

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

To be clear, is the "splash" you're talking about the wallpaper on the greeter and lock screen? Or do you mean the thing that has the spinning gear that shows when you first log in?

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

Disregard the above, I am able to reproduce this after all. Though strangely, I'm seeing the wrong splash screen on ISO itself.

Changed in ubuntustudio-default-settings (Ubuntu Jammy):
milestone: none → ubuntu-22.04.2
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Erich, or anyone else affected,

Accepted ubuntustudio-default-settings into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntustudio-default-settings/22.04.26.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in ubuntustudio-default-settings (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Upon testing, I was able to verify Aaron's findings that this is a problem on the ISO image itself as well. As such, I changed the test case above. However, I was able to verify that ubuntustudio-default-settings 22.04.26.3 does, indeed, fix the issue.

* Run candidate .iso image in a VM
  - Notice incorrect login splash.
* Enable proposed repository.
* Install ubuntustudio-default-settings 22.04.26.3
* Logout
* Login
  - Notice correct login splash (attached screenshot)

This *will* require a respin of the Ubuntu Studio 22.04.2 candidate .iso image.

description: updated
tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntustudio-default-settings - 22.04.26.3

---------------
ubuntustudio-default-settings (22.04.26.3) jammy; urgency=medium

  * Work around change to plasma default splash theme propogation (LP: #2007614)

 -- Erich Eickmeyer <email address hidden> Thu, 16 Feb 2023 14:32:59 -0800

Changed in ubuntustudio-default-settings (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for ubuntustudio-default-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.