Can't stop sugar

[FGrose]

Observed in SoaS 26 alpha dnf upgraded to 09-Jun-2017.

Observed after a testing session where an Activity was downgraded and then later upgraded (among other things).

On trying to shutdown an alert message appeared:

An activity is not responding.
You may lose unsaved work if you continue. (nn) Continue (x) Cancel

Pressing the Continue button closed the alert but had no other effect.
This was attempted several times. Also tried Cancel. Also tried restart.

After capturing a log and preparing a bug report and testing again I got into a state with no Activity icons in the Frame and no access to the Journal. A subsequent logout-login allowed me to capture another log and recreate a bug ticket.

Following this I was able to shutdown successfully.

[FGrose]

log capture

[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.

[FGrose]

systemd system journal

[FGrose]

Fedora Live boots default with /var/log/journal present. I think I've attached the system journal for the right boot.

[quozl]

Thanks. I'll take a punt and say Not Sugar.

Something happens to deauthenticate the liveuser; evidence is how sugar-backlight-setup works fine first time, then is refused as "Not authorized" at 10:28:00. It may relate to the pulseaudio core dump in some way, but not sure.

I'll repeat my questions; Do you remember using sshd or text console? Can you reproduce?

[FGrose]

Thanks, I agree, not likely Sugar.

I do think I logged in as liveuser in a text console to sugar-install-bundle Terminal-45.1.xo in that boot session.

I haven't reproduced the problem yet, so will close as Not Sugar, and only reopen if I'm able to reproduce the problem.

[quozl]

Thanks. Yes, if you log in on text console and don't log out, the system policy is to require confirmation from the graphical head user before shutting down. Sugar doesn't implement that part of the agreement. From memory it arrived around Fedora 20.