Bugzilla – Bug 127655
kdeutils3-laptop: can't start klaptop applet - drop it
Last modified: 2006-01-18 14:27:57 UTC
I installed full KDE selection and also standard installation and get klaptop battery monitoring in KDE Control Center. 1.) we have kpowersave and should never install this (not working) kcm module/ applet. 2.) you can't start battery monitoring (applet) from the kcm module. Nothing happens if you click on the button. I think we should drop klaptop from the distribution.
Well, klaptop works for me (FSC M3438G), and I even uninstalled kpowersave as I prefer KDE's klaptop.
it could be that it starts after the next login.. however I'm undecided.. kpowersave has the potential to be better than kcmlaptop, however in same cases it fails to do actually do so. I suggested several times to drop kcmlaptop.. how much is kpowersave dependant on powersave ? can it work at all if powersave daemon is not running ?
I found now way to get the applet part of klaptop running. Also not with relogin. Btw. currently KPowersave depends on powersave. Without powersave you have only a very reduced functionality. But we plan to implement some of the base functions of klaptop in KPowersave to get the basics also if powersave is missing. We also plan to move the configure dialog to a kcm-plugin, but I must first take a look at this.
*** Bug 132303 has been marked as a duplicate of this bug. ***
We discussed this again in the mobile team. We suggest this: * split off kmilo parts from the kdeutils3-laptop package * don't install kdeutils3-laptop (klaptop part) by default on laptops * install kmilo part of package by default on laptops We should change this for Code10 and SUSE 10.1
we'll move klaptop to kdeutils3-extra - after beta1. If mobile team needs this urgently, go ahead
there is currently no solution for the "install kmilo part for laptops" because we don't have patterns yet and selections don't allow this (as laptop selection can't rely on kde being installed). other than that we decided to drop klaptop from the packages (also due to licensing issues that can't be solved easily). maybe later when both conditions are fixed this can be solved correctly.