Description of problem: mouse cursor does not change it's shape on windows borders or by providing launch feedback Version-Release number of selected component (if applicable):5.3.2 How reproducible:every time Steps to Reproduce: 1.start Plasma 5 desktop with its default cursor theme - breeze 2.move cursor to some opened window border or launch some application eg libreoffice - cursor shape does not change 3.expected behaviour - cursor shape changes on window border or displays "busy cursor" Not sure if it is related, but in .xsession-errors: /usr/bin/startkde: line 187: kapplymousetheme: command missing /usr/bin/kapplymousetheme file is indeed missing. Also, in the systemsettings there is missing dialogue for: 1. Selecting mouse theme in: Appearance -> Workspace Theme 2. Configuring mouse in: Hardware -> Input Devices Reproducible: Steps to Reproduce:
The same here
CC: (none) => piscestong
After august 12th KF5.13 & Plasma 5.4 beta update, now the mouse cursor changes on window border to another theme - in my case it changes from breeze to wonderland (or similar). However - when I changed the mouse cursor theme in systemsettings (yes, now that option exists) from breeze to something else and then back to breeze then the cursor theme started to work as expected...
As nobody confirms that change to another cursor theme in default install and setting the cursor theme in Systemsettings -> Appearance -> Workspace Theme solves the problem, then I'd set it as resolved fixed...
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
The bug still exists in fresh network install of Mageia Cauldron with Plasma Desktop. Workaround is to set the cursor theme with systemsettings.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Does this bug still occur in the current cauldron?
Blocks: (none) => 17523
Made a Cauldron network install January 20th by minimal install with X + later urpmi --no-recommends task-plasma5-minimal I did not check it specially but I do not remember the cursor theme changing as per comment 1. So I guess we can close this bug.
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED