Bug 202090

Created attachment 97236 [details]
screen grab of the failure and some simple diagnositcs showing it to be wrong

Timo will know the right dup

Sure that this happens on 10.1, btw?

Oh yes.  It's a clean install with all updates applied.

Can you please check if HAL is running (rchal status)?

Helmut, maybe this is a duplicate of your newest experiences...

Probably a duplicate of #198237?

Robert, can you also check whether the powersave daemon is running (rcpowersaved status)?

> (rchal status)
It's running.

> (rcpowersaved status)
It's running.

powersaved was certainly reported as not running on my previous install, and there seemed to be some confusion about it at the time, because I could find it with ps

I've been away from home for a few weeks, and the system seems to have updated itself again, but the dbus dialogue did not pop up when I first logged in, but did the first time after a reboot. (I had to shut down when I got home to re-arrange the power for cosmetic reasons).  I have since confirmed that the error is only seen during autologin after boot.  If I disable autologin and hence things take a bit longer, I don't see the dialogue, or if I log out and in again.

We are experiencing this problem with SLED10 as well, but only in thin ThinLinc user sessions. 

*** Bug 206352 has been marked as a duplicate of this bug. ***

(In reply to comment #9)
> We are experiencing this problem with SLED10 as well, but only in thin 
> ThinLinc user sessions. 

This has nothing to do with this bug. The reason for this: If I understand ThinLinc correct, they work with remote sessions and remote users are not allowed atm to use this interfaces on DBUS/HAL/powersave. This issue is already known.

Robert, I think that the error message comes only up after a few seconds, right? If so, can you please try the following in a shell _before_ the message is shown:

powersave -c
lshal

I don't need the complete output of the lshal command, I need just to know if there is no error.

Danny, if this doesn't give us more helpful information, I think we have to package a special kpowersave rpm with a lot of debugging output written to a file. This bug is quit annoying for a while now and I'm rather clueless otherwise.

Holger: I have been out of the country for a month, and left the machine whirring away being a server.  I had turned on online updates when I re-installed.

Now I am back in the country, the dialogue reported no longer appears.  I have tried logging on explicitly from a running machine, and using autologin from a boot.

In answer to 'after a few seconds', no it came up at the same time that ktip appeared and the prompts appeared inside the shell tool saved in the session.  So I would not have been able to do your test, even if the problem had not vanished like smoke in the wind.

So it has either been mended, healled up, or some race condition in the startup has changed for some reason.

In Bug #206352 I reported a more general problem with dbus/KDE (in 10.2). Consecutive updates have reduced the problem for me, too, so that currently only kpowersave is still having problems with dbus.

It seems that comment #10 is (now) correct and #206352 is a duplicate of this bug?

Concerning comment #12: The requester from kpowersave concerning the allegedly not running dbus comes up with a short delay (several seconds after starting KDE). However, there is not enough time for starting a konsole and typing in that commands you proposed :(.

According to comment 13, the initial bug stated in comment 1 is fixed.

Additionally it is not present in openSUSE 10.2 anymore, closing.