Bug 447198 - Cursor theme settings applying does not work globally until reboot
Summary: Cursor theme settings applying does not work globally until reboot
Status: RESOLVED DUPLICATE of bug 420859
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_cursortheme (show other bugs)
Version: 5.23.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-18 19:04 UTC by blood990
Modified: 2022-01-11 21:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of settings menu related to bug (84.96 KB, image/jpeg)
2021-12-18 19:04 UTC, blood990
Details

Note You need to log in before you can comment on or make changes to this bug.
Description blood990 2021-12-18 19:04:15 UTC
Created attachment 144660 [details]
Screenshot of settings menu related to bug

SUMMARY
***
Changing cursor theme and applying changes causes changes to only partially work. When hovering mouse over system settings or bar with system tray etc. the new cursor is show, but when hovering mouse over desktop wallpaper or dolphin file manager then old cursor theme is used. After reboot new theme properly works everywhere.
***


STEPS TO REPRODUCE
1. Change cursor theme (for example from default dark to light), click button that applies changes immediately
2. Do not reboot - hover mouse over various elements (inside settings application, outside it etc. - try various different elements of plasma DE)
3. See cursor being inconsistent either old theme or new theme, depending on what kind of thing you hover over.
4. Reboot, see cursor inconsistency being fixed by reboot

OBSERVED RESULT
Inconsistent cursor looks - either new one or old one is seen depending on what is currently hovered

EXPECTED RESULT
New cursor theme being seen everywhere immediately after applying changes in settings

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
None
Comment 1 Nate Graham 2022-01-11 21:44:13 UTC

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