When running guidance-power-manager it crashes with the following traceback: Traceback (most recent call last): File "/usr/bin/guidance-power-manager", line 1178, in <module> main() File "/usr/bin/guidance-power-manager", line 1153, in main mainWindow = PowermanagerApp(None) File "/usr/bin/guidance-power-manager", line 1077, in __init__ self.pmwidget.prepare() File "/usr/bin/guidance-power-manager", line 89, in prepare self.configToUi() File "/usr/bin/guidance-power-manager", line 410, in configToUi self._setCB(self.BatteryCriticalCombo, self.cb_act, self.cb_act_def_critical, self._checkOldConfig(self.config.readEntry("batteryCriticalAction", ""), False)) File "/usr/bin/guidance-power-manager", line 163, in _checkOldConfig num_val = int(value) TypeError: int() argument must be a string or a number, not 'QVariant' nano /usr/bin/guidance-power-manager [1]+ Exit 255 guidance-power-manager I'm not sure what the exact cause is, but I'm using Python-2.6.2. It is however easily fixed, by replacing the offending line, /usr/bin/guidance-power-manager:163 num_val = int(value) with num_val = value.toInt() New ebuild and patch included.
Created attachment 201917 [details, diff] guidance-power-manager-4.3.0-r1.ebuild
Created attachment 201918 [details, diff] guidance-power-manager-4.3.0-r1-fix-typeerror.patch
Just one question, did you send the patch to the upstream guys?
No, I haven't done that yet. I'd like to make sure, that it's not my own fault, since I haven't checked the good KDE folks recommendation regarding python. I could be using an unsupported version. I would however think, that it would be best if KDE works with as many versions as possible. So perhaps I should just report it regardless.
Bug reported (with patch attached) upstream (http://bugs.kde.org/show_bug.cgi?id=204938).
Now, you can use sys-power/guidance-power-manager-4.3.1 from kde-testing overlay. As kde-4.3.1 is stable now, I think it makes sense to move this ebuild to the tree.
4.3.3 in portage, closing.
