Bug 7858

wip

Status: NEW => ASSIGNED

After some work on this issue I think you should file it against lightdm and not against the task-razorqt meta package.

task-razorqt requires (depends) on lightdm, not the opposite.

As you already said (and I verified it during my analysis), lightdm doesn't work properly if no consolekit package is installed.
 
Consider please that none of the other task-* packages neither the *-session packages of the various desktop environments depend on consolekit, that's I would avoid to violate this standard. 

I suppose it would be better to ask the lightdm maintainers to add the consolekit requirement. This way the issue you are experiencing with the razorqt environment will be automatically resolved.

Status: ASSIGNED => NEW

Resetting assignee to default.
Changing rpm package to lightdm-1.4.0-5.mga3.

Assignee: matteo.pasotti => bugsquad
Source RPM: task-razorqt-1-6.mga3 => lightdm-1.4.0-5.mga3

Just read this[1] thread from dev ml, consolekit is deprecated so it's not a good solution. 
That confirms however that the issue is more dm-related than wm-related.

Regards

[1]http://www.mail-archive.com/mageia-dev@mageia.org/msg19124.html

If I install razorqt without lightdm there are not "RESTART" and "SHUTDOWN"
in the menu of razorqt.
So razorqt need consolekit too.

Out of curiosity I removed all *consolkit* packages. (rpm -e --nodeps) 

kdm works OK and kde menus seem unaffected.

razorqt has no shutdown or reboot options in the menu (as reported).

icewm is missing all sub-menus from the "logout" menu option (it just logs out instantly when it should offer further options)

maybe /OT
Possibly related/of interest - I noticed that when task-raqorqt was installed with consolekit present, the graphical login screen changed to one I have never seen before (it was also slightly broken visually). On removing task-razorqt and all orphans the login reverted to kdm. Installing without consolekit present did not change the login screen - it stayed with kdm.

@Jacques

No, razorqt doesn't need consolekit and the behaviour you are describing is (as for now) correct: it is supposed to be as it is. 

Look at the behaviour of other environments like lxde, please.

Moreover, you should read carefully the note 1 in comment 4 where it's clear that CK is deprecated.

It seems instead that systemd support (ck replacement) for razorqt was actually added/fixed upstream just 2 days ago [1] :-/ 

I'm going to check razorqt for systemd support.

[1] https://github.com/Razor-qt/razor-qt/issues/458

@Barry:

kde works because it was already patched (always see note 1 in comment 4).

razorqt should install a razor-lightdm-greeter but it seems that something is not working properly.

Thank you both for the inputs. Work in progress, again.

Status: NEW => ASSIGNED
Assignee: bugsquad => matteo.pasotti
Source RPM: lightdm-1.4.0-5.mga3 => razorqt-0.5.0-2.mga3

(In reply to comment #7)
> 
> razorqt should install a razor-lightdm-greeter but it seems that something is
> not working properly.
> 

Just a missing BR. I've enabled it (lightdm-razorqt-greeter subpkg) now in latest razorqt. The packaging (read: naming) follows how it's done in the other lightdm greeters I've packaged.

BTW, IMHO it would be good to split out the lightdm greeter from the razorqt src.rpm at some point. Too bad upstream doesn't ship separate sources.

CC: (none) => jani.valimaa

I added systemd support patching our packaged version (0.5.0) with code coming from git master.
It should fix this issue but I need some help doing tests. The new release 0.5.0-5.mga3 is available from the repositories.

@Jani: thank you, I'll try to ask upstream to ship the greeter sources separately then we will see (I agree with you, it would be better to split it up).

Status: ASSIGNED => NEW

The patch works as expected.

output of razor-power --check reboot
-----------------------------------
dbusCall: QDBusInterface is invalid "org.freedesktop.ConsoleKit" "/org/freedesktop/ConsoleKit/Manager" "org.freedesktop.ConsoleKit.Manager" "CanRestart" 
systemd: "CanReboot" = "yes"
-----------------------------------

Marking this bug report as resolved fixed.

Regards

Status: NEW => RESOLVED
Resolution: (none) => FIXED

(In reply to comment #10)
> The patch works as expected.
> 
> output of razor-power --check reboot
> -----------------------------------
> dbusCall: QDBusInterface is invalid "org.freedesktop.ConsoleKit"
> "/org/freedesktop/ConsoleKit/Manager" "org.freedesktop.ConsoleKit.Manager"
> "CanRestart" 
> systemd: "CanReboot" = "yes"
> -----------------------------------
> 
> Marking this bug report as resolved fixed.
> 
> Regards

After recent updates related to this and having installed task-razorqt, the DM manager in mcc is broken.

Even after uninstalling razorqt I am left with the greeter with the pizza cutter and the tool in mcc cannot change it back to KDM.

Something is broken in the DM configuration:-

[root@jackodesktop baz]# systemctl status prefdm.service
prefdm.service - Display Manager
          Loaded: loaded (/usr/lib/systemd/system/prefdm.service; static)
          Active: active (running) since Wed, 2012-10-24 13:42:03 BST; 6min ago
        Main PID: 4060 (kdm)
          CGroup: name=systemd:/system/prefdm.service
                  â 4060 /usr/bin/kdm -nodaemon

Oct 24 13:42:03 jackodesktop systemd[1]: Starting Display Manager...
Oct 24 13:42:03 jackodesktop systemd[1]: Started Display Manager.
Oct 24 13:42:03 jackodesktop kdm_config[4071]: Multiple occurrences of key 'AllowShutdown' in section [X-:*-Core] of /...kdmrc
Oct 24 13:42:03 jackodesktop kdm_config[4071]: Invalid boolean value '' at /usr/share/config/kdm/kdmrc:495
Oct 24 13:42:03 jackodesktop kdm[4060]: X server died during startup
Oct 24 13:42:03 jackodesktop kdm[4060]: X server for display :0 cannot be started, session disabled

I can only assume this is resulting from testing razorqt but I am not 100% sure.

What does 'systemctl status lightdm.service' say?

(In reply to comment #12)
> What does 'systemctl status lightdm.service' say?

[root@jackodesktop baz]# systemctl status lightdm.service
lightdm.service - Light Display Manager
          Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled)
          Active: active (running) since Wed, 2012-10-24 13:40:20 BST; 5h 24min ago
            Docs: man:lightdm(1)
        Main PID: 2056 (lightdm)
          CGroup: name=systemd:/system/lightdm.service
                  â 2056 /usr/sbin/lightdm
                  â 4100 /etc/X11/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
                  â 4111 lightdm --session-child 12 31

Oct 24 13:40:20 jackodesktop systemd[1]: Started Light Display Manager.
Oct 24 13:40:20 jackodesktop lightdm[2615]: pam_unix(lightdm-greeter:session): session opened for user lig...d=0)
Oct 24 13:40:33 jackodesktop lightdm[2958]: pam_unix(lightdm:session): session opened for user baz by (uid=0)
Oct 24 13:40:33 jackodesktop lightdm[2056]: ** (process:2958): WARNING **: Failed to open CK session: GDBu...iles
Oct 24 13:40:44 jackodesktop lightdm[3312]: pam_unix(lightdm-greeter:session): session opened for user lig...d=0)
Oct 24 13:41:00 jackodesktop lightdm[3319]: pam_unix(lightdm:session): session opened for user baz by (uid=0)
Oct 24 13:41:00 jackodesktop lightdm[2056]: ** (process:3319): WARNING **: Failed to open CK session: GDBu...iles
Oct 24 13:42:16 jackodesktop lightdm[4105]: pam_unix(lightdm-greeter:session): session opened for user lig...d=0)
Oct 24 13:42:33 jackodesktop lightdm[4111]: pam_unix(lightdm:session): session opened for user baz by (uid=0)
Oct 24 13:42:33 jackodesktop lightdm[2056]: ** (process:4111): WARNING **: Failed to open CK session: GDBu...iles
[root@jackodesktop baz]#

Ah, yes, I guess you installed lightdm when it had post/preun scripts enabled for systemd service.

Disable lightdm service with 'systemctl disable lightdm.service' and reboot or stop the service and restart prefdm.service. Note that if you stop the service, it will close the graphical session.

Well deduced :)

All working correctly now.