Bug 333735

Holger, have you seen something similar?

(Hi Fred :-)

Well, also noticed that the gpm applet had the s2m and s2d working, whereas the menu under Computer > Shutdown were greyed out.

What can I do to bring more information?

Thanks.

I noticed the same, and it seems to be random and rare. Sometime you can't switch the system off too using the new "sled" buttons from main menu, but the conventional gnome menu works OK.

You updated from a previous openSUSE (or even SUSE), right? ;-) Having these warnings in /var/log/messages does not hurt. Can you please check if packages pm-utils and suspend are installed? The menu thing sounds like a menu bug ;-)

Yes I have them, and yes, I updated from opensuse 10.2 final. I would think of a menu bug as well, after all :)

It sounds like the dbus connection is broken and libssui can't grab the suspend capabilities.

Could dbus have been restarted?

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

Looks as if #333926 is the same bug. Please answer this:

(In reply to comment #2 bug #333926 from Danny Kukawka)
> Not sure about this bug. Looks to me more like a problem with the powersaved
> config on the one hand and maybe a not running HAL daemon.
> 
> 1) is hal running ('rchal status' or 'lshal')
> 2) which HAL, KPowersave and powersave version?
> 3) is this a updated system or a clean install?

Please check also if ConsoleKit is running (rcconsolekit status).

qp5 log: rcconsolekit status
Checking for service ConsoleKit daemon                               running

qp5 log: rchal status
Checking for service HAL daemon                                      unused

[not clear to me this is the same bug?]

- hal is running

`--> rpm -aq |grep -Ei 'hal|powersave' 
hal-resmgr-0.1_SVNr141-29
powersave-0.15.17-10
hal-devel-0.5.9_git20070831-13
hal-0.5.9_git20070831-13
powersave-libs-0.15.17-10
hal-palm-0.12.2-26

- ConsoleKit was 'unused'. Then after 2 minutes, I wanted to start it, but said
it was already started... and indeed, its status had switched to 'started' :/

Okay ... the problems may differ a littlebit. I reopen #333926. 

This bug looks like a ConsoleKit problem with startup. --> Holger, could you investigate?

Maybe bug #332845 is connected.

Fred, please change

        startproc -f -p $DBUS_DAEMON_PID $DBUS_DAEMON_BIN $DBUS_DAEMON_PARAMETER

to
        $DBUS_DAEMON_BIN $DBUS_DAEMON_PARAMETER

in /etc/init.d/dbus

and reboot to check whether it helps.

Did the mods, it works... but I don't know if that's because of the change, or just luck, since it works from time to time...

Also just to note that, despite the shutdown button not being greyed out, it wouldn't actually work either. ie, I would have to init 0 from the command line.

I will report in a couple days, after a few (usually unnecessary) reboots ;)

No, just got the greyed out buttons again.

Any progress here? It's pretty bothersome to have to manually type s2ram to suspend your laptop every time, and forgetting can cook your laptop in the bag. For me, it seems every 3 out of 4 boots hits this. Since I only reboot the machine every week or so, I get stuck with this lots of times.

I'm not sure what is to be done.  If libssui cannot make a dbus call to gnome-power-manager to suspend and sleep (or even get status), the menus are going to be greyed out.

(In reply to comment #18 from Calvin Gaisford)
> I'm not sure what is to be done.  If libssui cannot make a dbus call to
> gnome-power-manager to suspend and sleep (or even get status), the menus are
> going to be greyed out.

please read comment #12, it's a DBUS problem.

Calvin, I guess you can close this bug.  With the online update for D-Bus (resulting from bug #331002) everything should be fine.

I'm closing the bug based on comment #20.

Timo, Calvin - the DBUS update did not do the trick for my X60 of c#15. This is a regression with major loss of functionality (compared to openSUSE 10.2).

Other than stated in c#18 I use KDE. 

I'll second comment #22 - the update didn't work for me as well. The suggestion in comment #12 has worked fine for me, until the update yesterday. Now all the symptoms are back, suspend to ram is greyed out and when I close the lid, it tells me that "Suspend to ram has been disabled by administrator".

I'll also second the opinion that it's a major regression, this is key functionality for laptops.

/etc/init.d/dbus:

Do you both have the same like in comment#12 in there? Something like:

        echo -n "Starting D-Bus daemon";
        $DBUS_DAEMON_BIN $DBUS_DAEMON_PARAMETER

ACK, I have those lines

Mine does as well. The last two reboots has had working STR, so perhaps my bug was just that dbus wasn't properly restarted after the upgrade. As far as I'm concerned, this bug can be closed as it seems to work fine for me after all.

Closing this out as per #20 and #29.  Frank will file a separate bug for his remaining issue.

No, I still have the problem mentioned in c#15 (apart from time travel)

Frank, i'm not sure what you mean by "when invoked by command line" for comment #15

JP, if I type s2ram in bash suspend works yet the options in the applet are greyed out. 

Frank, this sounds like an unrelated bug. Please file a different bug.

Manually upgrading to hal-0.5.10*-10.1 (due to other issues) seems to fix the issue for me.

As I was the ony person left with this issue I'll close this bug -- feel free to reopen.