Registered Member
|
When I click on System settings => Power Management => Activity Settings I see everything greyed out and I get this message:
"Power Management configuration module could not be loaded. The activity service is not running. It is necessary to have the activity manager to configure activity-specific power management behavior." I'm using kde 5. Anyone can help? |
|
run "kcmshell5 kded" and in the lower section enable power management.
|
Registered Member
|
I ran "kcmshell5 kded" but power management was already enabled.
Last edited by jribeiro on Sun Jul 05, 2015 4:42 pm, edited 4 times in total.
|
|
Ah, sh** - maybe I should better read the entire post next time
> The activity service is not running. Only PM / activity is affected and the reason seems to be that kactivitymangerd is either not running or not responding via dbus, check
If it's there and responsive, it's either a bug in the powerdevil kcm or libkactivites |
Registered Member
|
It seems it is not running:
Info from logs:
|
|
can you "kactivitymanagerd start-daemon" when the session is up?
(Trying to create a QWidget before a QApplication is weird and a major bug, since it would systematically prevent the application from running ever - ie. it should never run on any system) |
Registered Member
|
Here it is:
|
|
Looking into the source [1], kactivitymanagerd creates a QGuiApplication which is NOT sufficient for using QWidget - there either should be no QWidget or kactivitymanagerd should use a QApplication instance.
It also loads plugins _and_ links libQt5Widgets.so.5 here, what's at least "suspicious". => Please file a bug at http://bugs.kde.org, against "frameworks-kactivities" [1] http://quickgit.kde.org/?p=kactivities. ... cation.cpp |
Registered Member
|
I created another user.
I rebooted the system. I Logged in with new user. And I was astonished... It worked. Before, I had removed ~/.kde, ~/.kde4, and ~/.cache but it was not enough. The problem was in another configuration file. Which file? I really dont know. Anyway, thanks for your help. |
Registered Member
|
The problem returned.
So I removed the directory ~/.config. It solved the problem but is only temporary because if I reboot the system the problem arises again. |
|
less ~/.config/kactivitymanagerdrc
look at the [Plugins] section (I actually have all enabled, for I don't much appreciate the system tracking my actions) - one of them will create a widget, causing the crash. Please file a bug against frameworks-kactivities, so that the maintainer gets aware of it. |
Registered Member
|
I did it. It is here: https://bugs.kde.org/show_bug.cgi?id=350036
$ cat ~/.config/kactivitymanagerdrc [activities] a002e775-e672-4cb1-8418-2110b48097e4=Predefinição [main] currentActivity=a002e775-e672-4cb1-8418-2110b48097e4 runningActivities=a002e775-e672-4cb1-8418-2110b48097e4 |
Registered Member
|
I found out If I replace compiz for kwin I am able to use power management, e.g, lock screen feature. Maybe kde5 broke friendship with compiz because in kde4 they coexisted nicely.
|
|
This has nothing to do directly with the windowmanager - KWin talks to kactivitymanagerd, thus it will be started implicitly. But that's it and it does no way explain why kactivitymanagerd tries to create a QWidget on your system (while that attempt explains the abort - QWidget isn't supported by plain QGuiApplication)
|
Registered Member
|
The question is: Why kactivimanagerd does not start with compiz but it starts with kwin? |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft