Description of problem: Every time I install Mageia, it ships with annoying or non-working settings of the touchpad. To fix them, I have to install kcm_touchpad (synaptiks doesn't work) It would be appropriate to cater to a significant portion of your users and give them the tools to edit touchpad settings as default after installing task_kde. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedCC: (none) => balcaen.john, lmenutSource RPM: (none) => task-kde
Looks like kcm_touchpad is installed by default on KDE4 installations made using the classical installer, as it's listed in meta-task's rpmsrate-raw. The logic is interesting because it will only get installed if the hardware comprises a touchpad, but then users installed KDE4 via task-kde4 won't get it. It should be probably replaced by kcm-touchpad btw, which is newer and also part of plasma5 upstream now.
CC: (none) => mageiaSummary: Make kcm_touchpad part of task_kde => Make kcm_touchpad part of task-kde4
Hardware: x86_64 => AllVersion: 4 => Cauldron
Source RPM: task-kde => task-kde4
(In reply to Rémi Verschelde from comment #1) > Looks like kcm_touchpad is installed by default on KDE4 installations made > using the classical installer, as it's listed in meta-task's rpmsrate-raw. > The logic is interesting because it will only get installed if the hardware > comprises a touchpad, but then users installed KDE4 via task-kde4 won't get > it. That's why I'm a bit reluctant to add kcm_touchpad (or kcm-touchpad) in task-kde4; this would install it by default on lot of systems that don't need it. > > It should be probably replaced by kcm-touchpad btw, which is newer and also > part of plasma5 upstream now. kcm-touchpad is newer, powerfull but also far more complex than kcm_touchpad, and all the options of the GUI are often criticized [1] , that's why I never replaced and obsoleted kcm_touchpad by kcm-touchpad. [1] eg. https://kshadeslayer.wordpress.com/2014/02/11/new-touchpad-management-app-in-kubuntu-14-04
(In reply to Luc Menut from comment #2) > (In reply to Rémi Verschelde from comment #1) > > > > It should be probably replaced by kcm-touchpad btw, which is newer and also > > part of plasma5 upstream now. > > kcm-touchpad is newer, powerfull but also far more complex than > kcm_touchpad, and all the options of the GUI are often criticized [1] , > that's why I never replaced and obsoleted kcm_touchpad by kcm-touchpad. > > [1] eg. > https://kshadeslayer.wordpress.com/2014/02/11/new-touchpad-management-app-in- > kubuntu-14-04 I was discussing this with neoclust a while ago, and he agreed that kcm-touchpad would make sense as a new default, so I might have overruled you here and did the change already: - kcm-touchpad: http://svnweb.mageia.org/packages?view=revision&revision=821633 (I've also obsoleted synaptiks in a later commit, as it seems to be broken) - meta-task: http://svnweb.mageia.org/packages?view=revision&revision=821635 If you think that it would be better to keep kcm_touchpad as default for now, I can withdraw my freeze push request and revert the commits.
I don't have a strong opinion. kcm_touchpad and kcm-touchpad are 2 systemsettings's modules to configure touchpad. Some distros have choosen to obsolete kcm_touchpad, others to have both of them.
(In reply to Luc Menut from comment #4) > I don't have a strong opinion. kcm_touchpad and kcm-touchpad are 2 > systemsettings's modules to configure touchpad. Some distros have choosen to > obsolete kcm_touchpad, others to have both of them. OK, for the time being I've reverted my commit obsoleting kcm_touchpad. So for Mageia 5 we'll have kcm-touchpad as the default option, but people will still be able to install kcm_touchpad instead if they prefer it.
Closing as wontfix as per the above discussion (and it's not relevant for Cauldron which has no task-kde4).
Status: NEW => RESOLVEDVersion: Cauldron => 5Resolution: (none) => WONTFIX