Bug 511062 - lost login wallpaper
Summary: lost login wallpaper
Status: RESOLVED DUPLICATE of bug 507842
Alias: None
Product: plasmashell
Classification: Plasma
Component: Theme - Breeze (other bugs)
Version First Reported In: 6.5.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-25 01:54 UTC by alhsk
Modified: 2025-10-25 07:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
plasmalogin config in systemsettings (898.38 KB, image/png)
2025-10-25 01:54 UTC, alhsk
Details
plasmalogin in qemu vm (141.14 KB, image/png)
2025-10-25 02:40 UTC, alhsk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description alhsk 2025-10-25 01:54:18 UTC
Created attachment 186118 [details]
plasmalogin config in systemsettings

SUMMARY
The login screen wallpaper is lost and defaults to a black background after upgrading from KDE Plasma 6.4 to 6.5.

STEPS TO REPRODUCE
Start with a system running KDE Plasma 6.4.
Set a custom wallpaper for the login screen.
Upgrade the system packages to KDE Plasma 6.5.
Reboot or log out to return to the login screen.

OBSERVED RESULT
The login screen background is black instead of the previously selected wallpaper.

EXPECTED RESULT
The login screen should display the same wallpaper that was configured before the upgrade.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.12.53-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 18 × Intel® Core™ Ultra 5 125H
Memory: 32 GiB of RAM
Graphics Processor: Intel® Arc

ADDITIONAL INFORMATION
The plasmalogin.service appears to be running correctly, as shown by the output of systemctl status plasmalogin. The service successfully starts the Wayland session, and there are no obvious errors related to wallpaper loading in the log.
systemctl status plasmalogin output:

● plasmalogin.service - Simple Desktop Display Manager
     Loaded: loaded (/usr/lib/systemd/system/plasmalogin.service; enabled; preset: disabled)
    Drop-In: /etc/systemd/system/plasmalogin.service.d
             └─override.conf
     Active: active (running) since Sat 2025-10-25 09:28:31 CST; 19min ago
 Invocation: 3709adb445df4afe9593b821387072f7
       Docs: man:plasmalogin(1)
             man:plasmalogin.conf(5)
   Main PID: 1244 (plasmalogin)
      Tasks: 2 (limit: 37731)
     Memory: 23.1M (peak: 47.5M)
        CPU: 143ms
     CGroup: /system.slice/plasmalogin.service
             └─1244 /usr/bin/plasmalogin

10月 25 09:28:44 alhsk-pc plasmalogin-helper[1995]: [PAM] returning.
10月 25 09:28:44 alhsk-pc plasmalogin[1244]: Authentication for user  "alhsk"  successful
10月 25 09:28:44 alhsk-pc plasmalogin-helper[1995]: pam_kwallet5(plasmalogin:setcred): pam_kwallet5: pam_sm_setcred
10月 25 09:28:44 alhsk-pc plasmalogin-helper[1995]: pam_unix(plasmalogin:session): session opened for user alhsk(uid=1000) by alhsk(uid=0)
10月 25 09:28:44 alhsk-pc plasmalogin-helper[1995]: pam_kwallet5(plasmalogin:session): pam_kwallet5: pam_sm_open_session
10月 25 09:28:44 alhsk-pc plasmalogin-helper[1995]: Starting Wayland user session: "/usr/share/plasmalogin/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
10月 25 09:28:44 alhsk-pc plasmalogin[1244]: Session started true
10月 25 09:28:49 alhsk-pc plasmalogin[1244]: Greeter stopping...
10月 25 09:28:49 alhsk-pc plasmalogin[1244]: Auth: plasmalogin-helper exited with 255
10月 25 09:28:49 alhsk-pc plasmalogin[1244]: Greeter stopped. PLASMALOGIN::Auth::HelperExitStatus(255)

Furthermore, running sudo journalctl -b 1 -xeu plasmalogin returns no entries
Comment 1 alhsk 2025-10-25 01:55:44 UTC
well i can't shot a screenshot in plasmalogin,sorry
Comment 2 alhsk 2025-10-25 02:40:20 UTC
Created attachment 186120 [details]
plasmalogin in qemu vm
Comment 3 alhsk 2025-10-25 02:41:18 UTC
okay not only upgrade from Plasma6.4
Comment 4 Antonio Rojas 2025-10-25 07:16:49 UTC

*** This bug has been marked as a duplicate of bug 507842 ***