Power butten has no effect anymore

so the offending line in powerbtn.sh seems to be this:

 /usr/bin/dcop --all-sessions --all-users ksmserver ksmserver logout 1 2 0

- typing this to a shell gives error messages as seen above ("Couldn't attach to DCOP server!")
- as seen below, dcop thinks it has 2 processes and might try to talk to the other, but there is no such process
- this screwed up state seems to survive reboots, so it might be worth it to find the cause!

any hints?
;-) äxl

++++++++++++

xl@merlin:~$ sudo dcop --list-sessions --all-users
Active sessions for user /root :
  .DCOPserver_merlin__0

Active sessions for user /home/xl :
  .DCOPserver_merlin__0

xl@merlin:~$ pidof dcopserver
5248

this line (the offending one without "--all-users" works as it should:
 dcop --all-sessions ksmserver ksmserver logout 1 2 0

this line solved the problem:
sudo rm /root/.DCOPserver_merlin__0 /root/.DCOPserver_merlin_:0

maybe it should be filed upstream as a bug, that this situation can happen (no dcop server but socket is left), and that it survives reboots.

;-) xl

I ran into the same bug, and I just want to add for clarity:

Not only do you have to delete the files
/root/.DCOPserver_host__0 and /root/.DCOPserver_host_:0
but also, respectively,
/home/user/.DCOPserver_host__0 and /home/user/.DCOPserver_host_:0
of all relevant users (i.e. users who are not logged in).

Thanks for reporting this bug. What version of Ubuntu were you using? Is this still an error in Jaunty? Does the power button work at all, i.e. is it hibernation/suspend problem you're having?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!