[Bugs] #4989 Sugar UNSP: Can't stop sugar

[Sugar Labs Bugs]

#4989: Can't stop sugar
----------------------------------------+-------------------------------
  Reporter:  FGrose                     |            Owner:
      Type:  defect                     |           Status:  new
  Priority:  Unspecified by Maintainer  |        Milestone:  Unspecified
 Component:  Sugar                      |          Version:  Unspecified
  Severity:  Unspecified                |       Resolution:
  Keywords:                             |  Distribution/OS:  Fedora
Bug Status:  Unconfirmed                |
----------------------------------------+-------------------------------

Comment (by quozl):

 The alert message functioned correctly, and is caused by an activity still
 open, but the shutdown did not proceed.  In your logs, for the session
 immediately prior, in `sugar-logs-1497020928/shell.log`, are many
 instances of;

 {{{
 1497020895.169257 ERROR root: Can not stop sugar
 Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/jarabe/model/session.py", line
 107, in shutdown_completed
     pm.PowerOff(False)
   File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in
 __call__
     return self._proxy_method(*args, **keywords)
   File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in
 __call__
     **keywords)
   File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651,
 in call_blocking
     message, timeout)
 DBusException:
 org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive
 authentication required.
 }}}

 Sugar asked for the system to shutdown, but the system refused.  As a
 desktop environment on Fedora, Sugar can do no more than ask.  Sugar does
 not display the details of the refusal; and I'm not sure it needs to,
 because it should be rare.

 Cause is most likely that systemd saw you were using multiple seats; e.g.
 more than one session open, or via sshd or text console.  Do you remember
 any confirming detail?  Can you reproduce?

 I've looked for confirming detail.  On SoaS, the Log activity cannot
 access `/var/log` and does not access `journalctl`.  If your system is
 installed rather than live, there may be confirming detail in system logs
 or journal.

--
Ticket URL: <https://bugs.sugarlabs.org/ticket/4989#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system