Bug 973618 - no restart and shutdown opition in lightdm menu
Summary: no restart and shutdown opition in lightdm menu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm
Version: 19
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F19-accepted, F19FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2013-06-12 11:10 UTC by Wolfgang Ulbrich
Modified: 2014-03-14 13:05 UTC (History)
9 users (show)

Fixed In Version: lightdm-1.6.0-10.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-22 02:32:08 UTC


Attachments (Terms of Use)
lightdm.log (3.02 KB, text/x-log)
2013-06-12 11:14 UTC, Wolfgang Ulbrich
no flags Details
x-0.log (3.88 KB, text/x-log)
2013-06-12 11:15 UTC, Wolfgang Ulbrich
no flags Details
x-0-greeter.log (2.21 KB, text/x-log)
2013-06-12 11:16 UTC, Wolfgang Ulbrich
no flags Details

Description Wolfgang Ulbrich 2013-06-12 11:10:10 UTC
Description of problem:
After a fresh installed MATE desktop from f19 netiso TC2, shutdown and restart options didn't displayed in lightdm panel menu.
In /var/log/lightdm/x-0-greeter.log i found this warning.

** (process:468): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files

Installing consolekit-x11 fix the issue, after a restart the menu items displayed well are working.

Also 'suspend on lid close' didn't work without consolekit, but i'm not shure if this lightdm related.

Version-Release number of selected component (if applicable):
lightdm-1.6.0-9.fc19.x86_64

How reproducible:



Steps to Reproduce:
1. Install MATE Desktop from netinstall iso f19 TC2 and reboot.
2. try to to restart/shutdown from lightdm panel menu.

Actual results:
no shutdown/restart option in panel menu

Expected results:
shutdown/restart option in panel menu

Additional info:

Comment 1 Wolfgang Ulbrich 2013-06-12 11:14:56 UTC
Created attachment 760098 [details]
lightdm.log

Comment 2 Wolfgang Ulbrich 2013-06-12 11:15:54 UTC
Created attachment 760099 [details]
x-0.log

Comment 3 Wolfgang Ulbrich 2013-06-12 11:16:39 UTC
Created attachment 760100 [details]
x-0-greeter.log

Comment 4 Kevin Fenzi 2013-06-20 18:34:52 UTC
I'm seeing this also on a TC6 xfce spin install.

Comment 5 Rex Dieter 2013-06-20 18:37:43 UTC
I can confirm now:

* selinux isnt it (enabled/permissive doesn't matter)
* polkit.rules seems correct

Now, testing different bindings (gtk/gobject vs qt/kde).

* gtk/gobject doesnt work

Comment 6 Rex Dieter 2013-06-20 18:41:04 UTC
A ha!

* lightdm-kde works

OK, time to re-review the systemd-login patch to lightdm-gobject bindings

Comment 7 Rex Dieter 2013-06-20 18:50:15 UTC
For example, working -qt bindings code example:

if ( d->login1Interface->isValid() ) {
  QDBusReply<QString> reply1 = d->login1Interface->call("CanReboot");
  if (reply1.isValid()) {
    return (reply1.value()=="yes");
  }
}


-gobject bindings equivalent:

/**
* CanReboot, CanPowerOff returns a string "yes", "no", or "challenge", not a boolean as ConsoleKit
**/
if (g_variant_is_of_type (result, G_VARIANT_TYPE ("(s)"))) {
    g_variant_get (result, "(b)", str_result);
    if(g_strcmp0(str_result,true_result) == 0) {
        function_result = TRUE;
    }
...


Now, I get to wrap by brain around how this g_variant stuff is supposed to work again. :-/

Comment 8 Fedora Update System 2013-06-20 20:25:25 UTC
lightdm-1.6.0-10.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lightdm-1.6.0-10.fc19

Comment 9 Rex Dieter 2013-06-20 20:41:24 UTC
nominating blocker, xfce/mate spins won't be able to shutdown/restart from login screen without this fix.

Comment 10 Kevin Fenzi 2013-06-21 19:16:22 UTC
+1 FE (since it's non blocking desktops, I don't think it can really be a blocker)

Comment 11 Fedora Update System 2013-06-21 19:17:05 UTC
Package lightdm-1.6.0-10.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lightdm-1.6.0-10.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11449/lightdm-1.6.0-10.fc19
then log in and leave karma (feedback).

Comment 12 Dan Mashal 2013-06-21 19:17:31 UTC
+1

Comment 13 Adam Williamson 2013-06-21 21:12:57 UTC
+1 here too, setting accepted freeze exception.

Comment 14 Mukundan Ragavan 2013-06-21 22:44:54 UTC
1.6.0-10 fixes the issue. restart and shutdown options are back.

Comment 15 Adam Williamson 2013-06-21 22:47:32 UTC
thanks! setting VERIFIED. can you up-karma the update if you didn't already?

Comment 16 Fedora Update System 2013-06-22 02:32:08 UTC
lightdm-1.6.0-10.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Steve Rogerson 2013-08-08 08:20:59 UTC
I still get this problem:
kernel 3.10.4-300.fc19.x86_64
$ rpm -q lightdm
lightdm-1.6.0-10.fc19.x86_64

Suspend works with gnome, not with MATE

lenovo G570 laptop.

Fn-F1: beeps and (sometimes) produces a window with "Failure reported as: Cannot suspend"

No sleep/hibernate options in the shutdown window. Same with and without ConsoleKit-x11.

selinux not enforced. Nothing in any log looks helpful.

Comment 18 Steven Franzen 2014-03-13 13:15:38 UTC
I also still have this issue on Fedora 20 with KDE and lightdm 1.8.5-2. It must still be something to do with permissions, as the buttons are present and working when I run $ lightdm -d --test-mode.

Comment 19 Rex Dieter 2014-03-13 13:34:18 UTC
Steven, please file a separate bug, yours is likely different

Comment 20 Steven Franzen 2014-03-14 13:05:06 UTC
(In reply to Rex Dieter from comment #19)
> Steven, please file a separate bug, yours is likely different

Done (1076493).


Note You need to log in before you can comment on or make changes to this bug.