Bug 861188 - lightdm does not start on boot
Summary: lightdm does not start on boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 18:28 UTC by Marcus Moeller
Modified: 2012-09-28 06:47 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-09-28 06:47:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output with systemd debug information (234.47 KB, text/plain)
2012-09-27 19:22 UTC, Marcus Moeller
no flags Details

Description Marcus Moeller 2012-09-27 18:28:31 UTC
Description of problem:

I have installed LightDM on a Fedora 18 Minimal X Installation and activated it using systemctl enable lightdm.service.

Sadly it does not start on boot.

systemctl status lightdm.service
lightdm.service - Light Display Manager
	  Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled)
	  Active: inactive (dead)
	    Docs: man:lightdm(1)
	  CGroup: name=systemd:/system/lightdm.service


When I start it manually from console using systemctl restart lightdm.service it works fine.

I have tried to find out more in the logs but only found:

/var/log/lightdm/x-0-greeter.log
(lightdm-gtk-greeter:1032): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed

(lightdm-gtk-greeter:1032): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed

(lightdm-gtk-greeter:1032): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed

** (lightdm-gtk-greeter:1032): WARNING **: Unexpected accounts property type for XHasMessages: (null)

(lightdm-gtk-greeter:1032): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed


and /var/log/messages
Sep 27 14:39:27 localhost dbus-daemon[472]: dbus[472]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=995 pid=1109 comm="/usr/sbin/lightdm-gtk-greeter ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.19" (uid=0 pid=1007 comm="/usr/sbin/console-kit-daemon --no-daemon ")
Sep 27 14:39:27 localhost dbus[472]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=995 pid=1109 comm="/usr/sbin/lightdm-gtk-greeter ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.19" (uid=0 pid=1007 comm="/usr/sbin/console-kit-daemon --no-daemon ")

Sep 27 14:41:06 localhost lightdm[1089]: ** (process:1268): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to get information about the calling process

Comment 1 Rex Dieter 2012-09-27 18:45:24 UTC
Is lightdm the only DM on this system (besides gdm perhaps)?

Otherwise,
https://fedoraproject.org/wiki/Features/DisplayManagerRework#How_To_Test

suggests you need to:
systemctl enable --force lightdm.service

Comment 2 Marcus Moeller 2012-09-27 18:57:31 UTC
lightdm is the only dm installed on that machine, so forcing does not help.

Comment 3 Marcus Moeller 2012-09-27 19:22:48 UTC
Created attachment 618259 [details]
dmesg output with systemd debug information

Comment 4 Marcus Moeller 2012-09-28 06:47:43 UTC
Missed to systemctl --force enable graphical.target

Sorry for the noise.


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