Bug 1071548 - Autologin fails on created Fedora 20 LiveCD xfce
Summary: Autologin fails on created Fedora 20 LiveCD xfce
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm
Version: 20
Hardware: x86_64
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL: http://forums.fedoraforum.org/showthr...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-01 15:55 UTC by yunzheng.hu
Modified: 2015-06-30 00:55 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:55:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
typescript of live-CD creation (908.94 KB, text/plain)
2014-06-28 06:21 UTC, Peter H. Jones
no flags Details
kickstart file (12.55 KB, text/plain)
2014-06-28 12:17 UTC, Peter H. Jones
no flags Details
kickstart file (13.03 KB, text/plain)
2014-06-29 23:27 UTC, Peter H. Jones
no flags Details
typescript of livecd creation (1.17 MB, text/plain)
2014-06-29 23:28 UTC, Peter H. Jones
no flags Details
qemu console output (228.41 KB, text/plain)
2014-06-29 23:39 UTC, Peter H. Jones
no flags Details
kickstart file (14.74 KB, text/plain)
2014-07-02 01:39 UTC, Peter H. Jones
no flags Details
typescript of livecd creation (1.35 MB, text/plain)
2014-07-02 01:40 UTC, Peter H. Jones
no flags Details
tyescript of qemu console log (128.26 KB, text/plain)
2014-07-02 01:44 UTC, Peter H. Jones
no flags Details
typescript of booting Fedora-Live-Xfce-x86_64-rawhide-20140712.iso under qemu (360.29 KB, text/plain)
2014-07-12 22:45 UTC, Peter H. Jones
no flags Details

Description yunzheng.hu 2014-03-01 15:55:30 UTC
Description of problem:

When creating a new livecd using livecd-creator and spin-kickstarts package from a Fedora 20 install, the livecd boots but fails to autologin the "liveuser".

When trying to login as root or liveuser without password it just jumps back to the login screen, no desktop is shown.

Console login doesn't seem to work either for both users.

Version-Release number of selected component (if applicable):

Fedora-20

How reproducible:

Always

Steps to Reproduce:
1. Install Fedora 20
2. Install livecd-tools, spin-kickstarts
3. setenforce 0
4. livecd-creator --verbose --config=/usr/share/spin-kickstarts/fedora-livecd-xfce.ks --releasever=20 --fslabel=My-Fedora
Actual results:


Expected results:

Iso with autologin to desktop working.

Additional info:

Comment 1 Kevin Fenzi 2014-03-03 18:03:49 UTC
Can you attach: 

sudo journalctl -u lightdm -b

and

~youruser/.xsession-errors 

Also, the output from livecd-creator when making it might be of help. 

Thanks.

Comment 2 Peter H. Jones 2014-06-28 06:18:26 UTC
sudo journalctl -u lightdm -b gives:
"-- Logs begin at ven 2014-06-27 21:58:56 EDT, end at sam 2014-06-28 02:11:09 EDT. --
jun 27 22:02:14 localhost systemd[1]: Starting Light Display Manager...
jun 27 22:02:14 localhost systemd[1]: About to execute: /usr/sbin/lightdm
jun 27 22:02:14 localhost systemd[1]: Forked /usr/sbin/lightdm as 847
jun 27 22:02:14 localhost systemd[1]: lightdm.service changed dead -> start
jun 27 22:02:14 localhost systemd[847]: Executing: /usr/sbin/lightdm
jun 27 22:02:17 localhost systemd[1]: lightdm.service's D-Bus name org.freedesktop.DisplayManager now registered by :1.4
jun 27 22:02:17 localhost systemd[1]: lightdm.service changed start -> running
jun 27 22:02:17 localhost systemd[1]: Job lightdm.service/start finished, result=done
jun 27 22:02:17 localhost systemd[1]: Started Light Display Manager.
"

.xsession-errors contains:
"touch: impossible de faire un touch « /home/liveuser/.cache/imsettings/log »: Aucun fichier ou dossier de ce type
xfce4-session-Message: ssh-agent is already running; starting gpg-agent without ssh support
gpg-agent[1394]: répertoire « /home/liveuser/.gnupg » créé
gpg-agent[1394]: répertoire « /home/liveuser/.gnupg/private-keys-v1.d » créé
gpg-agent[1403]: gpg-agent (GnuPG) 2.0.24 started

(xfsettingsd:1443): GLib-CRITICAL **: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:1443): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.

(xfwm4:1408): GLib-CRITICAL **: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfwm4:1408): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(xfdesktop:1419): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed
"

Comment 3 Peter H. Jones 2014-06-28 06:21:50 UTC
Created attachment 912996 [details]
typescript of live-CD creation

Comment 4 Peter H. Jones 2014-06-28 06:36:35 UTC
Booting the DVD and adding "enforcing=1" to the boot line made logging impossible. Whether in line mode or full-screen mode, if I try to log in to an existing account, messages flash by too fast to read, and I'm back at the login prompt.

With the permissive setup, I can "setenforce 1" soon after boot.

Comment 5 Peter H. Jones 2014-06-28 12:17:32 UTC
Created attachment 913005 [details]
kickstart file

Comment 6 Peter H. Jones 2014-06-29 23:27:15 UTC
Created attachment 913232 [details]
kickstart file

Tried a complete run today. The image boots in qemu with enforcing on, but I get error messages (see below).

Comment 7 Peter H. Jones 2014-06-29 23:28:25 UTC
Created attachment 913233 [details]
typescript of livecd creation

Comment 8 Peter H. Jones 2014-06-29 23:39:04 UTC
Created attachment 913234 [details]
qemu console output

Booted and ran successfully, but with error messages. Also, the output on the qemu screen scrolled on the left side only, as if the scrolling only applied to the length of the incoming line, and not the whole width of the screen.

Also note that

grep -n logind typescript-running-livecd-xfce-jam-201406291814 gives
"1167:[  335.041714] systemd[1]: Installed new job systemd-logind.service/start as 224
1617:[  490.506676] systemd[1]: Got notification message for unit systemd-logind.service
1618:[  490.516683] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1619:[  490.527593] systemd[1]: systemd-logind.service: got WATCHDOG=1
1620:[  490.538039] systemd[1]: Got notification message for unit systemd-logind.service
1621:[  490.548683] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1622:[  490.558677] systemd[1]: systemd-logind.service: got WATCHDOG=1
1653:[  511.692418] systemd[1]: Got notification message for unit systemd-logind.service
1654:[  511.881560] systemd[1]: systemd-logind.service: Got notification message from PID 688 (READY=1...)
1656:[  512.129821] systemd[1]: systemd-logind.service: got STATUS=Processing requests...
1657:[  512.305933] systemd[1]: Got notification message for unit systemd-logind.service
1658:[  512.526725] systemd[1]: systemd-logind.service: Got notification message from PID 688 (READY=1...)
1659:[  512.731722] systemd[1]: systemd-logind.service: got STATUS=Processing requests...
1660:[  512.950770] systemd[1]: systemd-logind.service: got WATCHDOG=1
1661:[  513.173868] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/systemd_2dlogind_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=19 reply_cookie=0 error=n/a
1667:[  516.351619] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/systemd_2dlogind_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=29 reply_cookie=0 error=n/a
1668:[  516.365741] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/systemd_2dlogind_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=30 reply_cookie=0 error=n/a
1686:[  530.933734] systemd[1]: systemd-logind.service: got WATCHDOG=1
1687:[  531.212453] systemd[1]: Got notification message for unit systemd-logind.service
1688:[  531.463803] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1705:[  542.969689] systemd[1]: Got notification message for unit systemd-logind.service
1706:[  543.140041] systemd[1]: systemd-logind.service: got WATCHDOG=1
1712:[  563.068727] systemd[1]: systemd-logind.service: got WATCHDOG=1
1713:[  563.224826] systemd[1]: systemd-logind.service: got WATCHDOG=1
1768:[  579.865382] systemd[1]: Got notification message for unit systemd-logind.service
1769:[  579.898529] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1770:[  579.931651] systemd[1]: systemd-logind.service: got WATCHDOG=1
1771:[  579.969462] systemd[1]: Got notification message for unit systemd-logind.service
1772:[  580.005362] systemd[1]: systemd-logind.service: got WATCHDOG=1
1814:[  599.172753] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1815:[  599.338749] systemd[1]: systemd-logind.service: got WATCHDOG=1
1829:[  631.844706] systemd[1]: systemd-logind.service: got WATCHDOG=1
1870:[  671.709675] systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:systemd_unit_file_t:s0 tclass=service perm=status path=/run/systemd/system/session-1.scope cmdline=/usr/lib/systemd/systemd-logind: 0
1881:[  671.994781] systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:systemd_unit_file_t:s0 tclass=service perm=status path=/run/systemd/system/session-1.scope cmdline=/usr/lib/systemd/systemd-logind: 0
1892:[  672.269714] systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:systemd_unit_file_t:s0 tclass=service perm=status path=/run/systemd/system/session-1.scope cmdline=/usr/lib/systemd/systemd-logind: 0
1911:[  677.809017] systemd[1]: Got notification message for unit systemd-logind.service
1912:[  677.820722] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1913:[  677.831753] systemd[1]: systemd-logind.service: got WATCHDOG=1
1914:[  677.848690] systemd[1]: Got notification message for unit systemd-logind.service
1915:[  677.860618] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1916:[  677.871825] systemd[1]: systemd-logind.service: got WATCHDOG=1
1927:[  787.901866] systemd[1]: systemd-logind.service: got WATCHDOG=1
1951:[  912.838752] systemd[1]: Got notification message for unit systemd-logind.service
1952:[  912.849892] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1953:[  912.861705] systemd[1]: systemd-logind.service: got WATCHDOG=1
1954:[  912.872892] systemd[1]: Got notification message for unit systemd-logind.service
1955:[  912.884740] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1956:[  912.896709] systemd[1]: systemd-logind.service: got WATCHDOG=1
1963:[  936.018725] systemd[1]: Got notification message for unit systemd-logind.service
1964:[  936.029859] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1965:[  936.041681] systemd[1]: systemd-logind.service: got WATCHDOG=1
1966:[  936.058681] systemd[1]: systemd-logind.service: Got notification message from PID 688 (WATCHDOG=1...)
1967:[  936.070827] systemd[1]: systemd-logind.service: got WATCHDOG=1
1976:[ 1197.841860] systemd[1]: Installed new job systemd-logind.service/stop as 840
2132:[ 1213.461772] systemd[1]: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
2158:[ 1218.377622] systemd[1]: systemd-logind.service: cgroup is empty
2185:[ 1224.895692] systemd[1]: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected"

and grep -n [fF]ailed typescript-running-livecd-xfce-jam-201406291814
151:[    0.000000] tsc: Fast TSC calibration failed
185:[    0.861087] Failed to access perfctr msr (MSR c0010004 is 0)
210:[    1.815337] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
454:[   21.006584] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
455:[   21.092898] systemd[1]: Failed to load configuration for syslog.target: No such file or directory
456:[   21.095610] systemd[1]: Failed to load configuration for lvm2-activation-early.service: No such file or directory
457:[   21.097860] systemd[1]: Failed to load configuration for iscsid.service: No such file or directory
458:[   21.099920] systemd[1]: Failed to load configuration for iscsi.service: No such file or directory
459:[   21.104346] systemd[1]: Failed to load configuration for systemd-readahead-replay.service: No such file or directory
460:[   21.108905] systemd[1]: Failed to load configuration for systemd-readahead-collect.service: No such file or directory
465:[   21.173940] systemd[1]: Failed to load configuration for sysroot.mount: No such file or directory
548:[   22.426341] systemd[1]: ConditionKernelCommandLine=|noresume failed for dracut-cmdline.service.
549:[   22.430350] systemd[1]: ConditionKernelCommandLine=|resume failed for dracut-cmdline.service.
550:[   22.434920] systemd[1]: ConditionKernelCommandLine=|rd.break=cmdline failed for dracut-cmdline.service.
558:[   22.561938] systemd[1]: ConditionKernelCommandLine=|rd.modules-load failed for systemd-modules-load.service.
559:[   22.573595] systemd[1]: ConditionKernelCommandLine=|modules-load failed for systemd-modules-load.service.
560:[   22.586672] systemd[1]: ConditionDirectoryNotEmpty=|/run/modules-load.d failed for systemd-modules-load.service.
561:[   22.594843] systemd[1]: ConditionDirectoryNotEmpty=|/etc/modules-load.d failed for systemd-modules-load.service.
562:[   22.605875] systemd[1]: ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d failed for systemd-modules-load.service.
563:[   22.622036] systemd[1]: ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d failed for systemd-modules-load.service.
564:[   22.627795] systemd[1]: ConditionDirectoryNotEmpty=|/lib/modules-load.d failed for systemd-modules-load.service.
566:[   22.655835] systemd[1]: Starting of systemd-modules-load.service requested but condition failed. Ignoring.
575:[   22.870711] systemd[1]: ConditionDirectoryNotEmpty=|/run/sysctl.d failed for systemd-sysctl.service.
576:[   22.873727] systemd[1]: ConditionDirectoryNotEmpty=|/etc/sysctl.d failed for systemd-sysctl.service.
577:[   22.887735] systemd[1]: ConditionDirectoryNotEmpty=|/usr/local/lib/sysctl.d failed for systemd-sysctl.service.
594:[   24.412840] systemd[1]: ConditionPathExists=/etc/multipath.conf failed for multipathd.service.
595:[   24.437385] systemd[1]: Starting of multipathd.service requested but condition failed. Ignoring.
632:[   27.139613] systemd[1]: Failed to send unit change signal for systemd-journald.service: Connection reset by peer
658:[   56.699967] systemd[1]: ConditionPathExistsGlob=|/lib/dracut/hooks/initqueue/online/*.sh failed for dracut-initqueue.service.
660:[   56.751967] systemd[1]: ConditionPathExistsGlob=|/lib/dracut/hooks/initqueue/*.sh failed for dracut-initqueue.service.
691:[   74.809746] systemd[1]: ConditionPathExists=!/run/plymouth/pid failed for systemd-ask-password-console.path.
860:[  290.253626] systemd[1]: systemd-udevd-kernel.socket got notified about service death (failed permanently: no)
900:[  297.199800] systemd[1]: Failed to send unit remove signal for sys-subsystem-net-devices-ens3.device: Transport endpoint is not connected
901:[  297.324639] systemd[1]: Failed to send unit remove signal for sys-devices-platform-serial8250-tty-ttyS2.device: Transport endpoint is not connected
902:[  297.461855] systemd[1]: Failed to send unit remove signal for dev-ttyS0.device: Transport endpoint is not connected
903:[  297.520591] systemd[1]: Failed to send unit remove signal for sys-devices-virtual-block-loop1.device: Transport endpoint is not connected
904:[  297.626733] systemd[1]: Failed to send unit remove signal for dev-loop3.device: Transport endpoint is not connected
905:[  297.685732] systemd[1]: Failed to send unit remove signal for sys-module-configfs.device: Transport endpoint is not connected
906:[  297.761674] systemd[1]: Failed to send unit remove signal for systemd-journald.socket: Transport endpoint is not connected
907:[  297.826908] systemd[1]: Failed to send unit remove signal for -.slice: Transport endpoint is not connected
908:[  297.902907] systemd[1]: Failed to send unit remove signal for systemd-journald-dev-log.socket: Transport endpoint is not connected
909:[  298.044156] systemd[1]: Failed to send unit remove signal for systemd-udevd-control.socket: Transport endpoint is not connected
910:[  298.253661] systemd[1]: Failed to send unit remove signal for kmod-static-nodes.service: Transport endpoint is not connected
911:[  298.327699] systemd[1]: Failed to send unit remove signal for systemd-tmpfiles-setup-dev.service: Transport endpoint is not connected
912:[  298.461793] systemd[1]: Failed to send unit remove signal for systemd-vconsole-setup.service: Transport endpoint is not connected
913:[  298.634737] systemd[1]: Failed to send unit remove signal for timers.target: Transport endpoint is not connected
914:[  298.721877] systemd[1]: Failed to send unit remove signal for syslog.target: Transport endpoint is not connected
915:[  298.814491] systemd[1]: Failed to send unit remove signal for dev-mapper-live\x2drw.device: Transport endpoint is not connected
916:[  298.970651] systemd[1]: Failed to send unit remove signal for dev-dm\x2d2.device: Transport endpoint is not connected
917:[  299.060634] systemd[1]: Failed to send unit remove signal for dev-mapper-live\x2dosimg\x2dmin.device: Transport endpoint is not connected
918:[  299.240806] systemd[1]: Failed to send unit remove signal for sysroot.mount: Transport endpoint is not connected
919:[  299.337659] systemd[1]: Failed to send unit remove signal for initrd-udevadm-cleanup-db.service: Transport endpoint is not connected
1022:[  328.199494] systemd[1]: Failed to load configuration for syslog.target: No such file or directory
1023:[  328.743628] systemd[1]: Failed to load configuration for ntpd.service: No such file or directory
1024:[  328.768761] systemd[1]: Failed to load configuration for sntp.service: No such file or directory
1025:[  328.794593] systemd[1]: Failed to load configuration for ntpdate.service: No such file or directory
1026:[  329.354739] systemd[1]: Failed to load configuration for ip6tables.service: No such file or directory
1027:[  329.379942] systemd[1]: Failed to load configuration for iptables.service: No such file or directory
1028:[  330.142747] systemd[1]: Failed to load configuration for libvirtd.service: No such file or directory
1029:[  330.691157] systemd[1]: Failed to load configuration for lvm2-activation.service: No such file or directory
1030:[  330.839689] systemd[1]: Failed to load configuration for lvm2-activation-early.service: No such file or directory
1031:[  331.233723] systemd[1]: Failed to load configuration for systemd-random-seed-load.service: No such file or directory
1033:[  331.517786] systemd[1]: Failed to load configuration for sysroot.mount: No such file or directory
1034:[  331.544709] systemd[1]: Failed to load configuration for sysroot-var-lib-nfs-rpc_pipefs.mount: No such file or directory
1035:[  331.618206] systemd[1]: Failed to connect to system bus, retrying later...
1036:[  331.674437] systemd[1]: Failed to connect to API bus, retrying later...
1185:[  335.635928] systemd[1]: systemd-journald.socket got notified about service death (failed permanently: no)
1187:[  335.658603] systemd[1]: systemd-journald-dev-log.socket got notified about service death (failed permanently: no)
1195:[  335.836509] systemd[1]: Failed to destroy cgroup /system.slice/initrd-switch-root.service: No such file or directory
1269:[  336.844306] systemd[1]: ConditionVirtualization=no failed for systemd-readahead-collect.service.
1270:[  336.855480] systemd[1]: Starting of systemd-readahead-collect.service requested but condition failed. Ignoring.
1273:[  336.885023] systemd[1]: ConditionVirtualization=no failed for systemd-readahead-replay.service.
1274:[  336.885370] systemd[1]: Starting of systemd-readahead-replay.service requested but condition failed. Ignoring.
1298:[  339.358354] systemd[1]: ConditionDirectoryNotEmpty=|/etc/sysconfig/modules/ failed for fedora-loadmodules.service.
1299:[  339.375722] systemd[1]: ConditionPathExists=|/etc/rc.modules failed for fedora-loadmodules.service.
1301:[  339.420501] systemd[1]: Starting of fedora-loadmodules.service requested but condition failed. Ignoring.
1334:[  340.180856] systemd[1]: systemd-journald.socket got notified about service death (failed permanently: no)
1349:[  341.036886] systemd[1]: ConditionKernelCommandLine=|rd.modules-load failed for systemd-modules-load.service.
1350:[  341.077738] systemd[1]: ConditionKernelCommandLine=|modules-load failed for systemd-modules-load.service.
1351:[  341.108473] systemd[1]: ConditionDirectoryNotEmpty=|/run/modules-load.d failed for systemd-modules-load.service.
1352:[  341.139721] systemd[1]: ConditionDirectoryNotEmpty=|/etc/modules-load.d failed for systemd-modules-load.service.
1353:[  341.169619] systemd[1]: ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d failed for systemd-modules-load.service.
1354:[  341.200649] systemd[1]: ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d failed for systemd-modules-load.service.
1355:[  341.234718] systemd[1]: ConditionDirectoryNotEmpty=|/lib/modules-load.d failed for systemd-modules-load.service.
1357:[  341.293650] systemd[1]: Starting of systemd-modules-load.service requested but condition failed. Ignoring.
1374:[  342.505736] systemd[1]: ConditionDirectoryNotEmpty=|/run/sysctl.d failed for systemd-sysctl.service.
1376:[  342.645822] systemd[1]: ConditionDirectoryNotEmpty=|/usr/local/lib/sysctl.d failed for systemd-sysctl.service.
1385:[  343.467684] systemd[1]: ConditionPathExists=!/run/plymouth/pid failed for systemd-ask-password-console.path.
1386:[  343.495765] systemd[1]: Starting of systemd-ask-password-console.path requested but condition failed. Ignoring.
1388:[  343.567354] systemd[1]: ConditionPathExists=/sys/fs/fuse/connections failed for sys-fs-fuse-connections.mount.
1389:[  343.596801] systemd[1]: Starting of sys-fs-fuse-connections.mount requested but condition failed. Ignoring.
1391:[  343.665651] systemd[1]: ConditionDirectoryNotEmpty=|/run/binfmt.d failed for systemd-binfmt.service.
1392:[  343.697752] systemd[1]: ConditionDirectoryNotEmpty=|/etc/binfmt.d failed for systemd-binfmt.service.
1393:[  343.729693] systemd[1]: ConditionDirectoryNotEmpty=|/usr/local/lib/binfmt.d failed for systemd-binfmt.service.
1394:[  343.760628] systemd[1]: ConditionDirectoryNotEmpty=|/usr/lib/binfmt.d failed for systemd-binfmt.service.
1395:[  343.793882] systemd[1]: ConditionDirectoryNotEmpty=|/lib/binfmt.d failed for systemd-binfmt.service.
1397:[  343.854937] systemd[1]: Starting of systemd-binfmt.service requested but condition failed. Ignoring.
1403:[  344.080593] systemd[1]: ConditionPathExists=/etc/multipath.conf failed for multipathd.service.
1404:[  344.123800] systemd[1]: Starting of multipathd.service requested but condition failed. Ignoring.
1441:[  346.694027] systemd[1]: Failed to destroy cgroup /system.slice/sysroot-var-lib-nfs-rpc_pipefs.mount: No such file or directory
1532:[FAILED] Failed to start Create Volatile Files and Directories.
1566:[  446.414644] systemd[1]: ConditionKernelCommandLine=!rd.live.image failed for dnf-makecache.timer.
1567:[  446.424633] systemd[1]: Starting of dnf-makecache.timer requested but condition failed. Ignoring.
1702:[  541.289314] systemd[1]: firewalld.service changed final-sigterm -> failed
1718:[  564.872635] systemd[1]: Failed to send unit remove signal for firstboot-text.service: Transport endpoint is not connected
1730:[  567.192701] systemd[1]: Failed to process message [type=method_call sender=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StopUnit signature=ss]: Unit firstboot-graphical.service not loaded.
1734:[  568.384747] systemd[1]: Failed to load configuration for firstboot-graphical.service: No such file or directory
1738:[  569.679757] systemd[1]: Failed to send unit remove signal for firstboot-graphical.service: Transport endpoint is not connected
1745:[  573.292720] systemd[1]: ConditionDirectoryNotEmpty=|/var/lib/iscsi/nodes failed for iscsi.service.
1779:[  580.706799] systemd[1]: Failed to load configuration for mdmonitor-takeover.service: No such file or directory
1781:[  580.824835] systemd[1]: Failed to process message [type=method_call sender=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StopUnit signature=ss]: Unit mdmonitor-takeover.service not loaded.
1817:[  607.755809] systemd[1]: Starting of initial-setup-graphical.service requested but condition failed. Ignoring.
1819:[  612.757604] systemd[1]: ConditionPathExists=/var/log/Xorg.0.log failed for abrt-xorg.service.
1858:[  668.939802] systemd[1]: Failed to load configuration for session-1.scope: No such file or directory
2106:[ 1205.155827] systemd[1]: cups.socket got notified about service death (failed permanently: no)
2118:[ 1209.714676] systemd[1]: avahi-daemon.socket got notified about service death (failed permanently: no)
2128:[ 1212.557418] systemd[1]: dbus.socket got notified about service death (failed permanently: no)
2129:[ 1212.758796] systemd[1]: ConditionPathExists=!/etc/alsa/state-daemon.conf failed for alsa-store.service.
2130:[ 1212.992987] systemd[1]: Failed to send job remove signal for 826: Connection reset by peer
2131:[ 1213.272791] systemd[1]: Failed to send unit remove signal for session-1.scope: Transport endpoint is not connected
2132:[ 1213.461772] systemd[1]: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
2133:[ 1213.606689] systemd[1]: Failed to send unit change signal for getty.target: Transport endpoint is not connected
2134:[ 1213.732803] systemd[1]: Failed to send unit change signal for rsyslog.service: Transport endpoint is not connected
2135:[ 1213.832743] systemd[1]: Failed to send unit change signal for NetworkManager.service: Transport endpoint is not connected
2136:[ 1213.944805] systemd[1]: Failed to send unit change signal for accounts-daemon.service: Transport endpoint is not connected
2137:[ 1214.039692] systemd[1]: Failed to send unit change signal for lightdm.service: Transport endpoint is not connected
2138:[ 1214.149899] systemd[1]: Failed to send unit change signal for graphical.target: Transport endpoint is not connected
2139:[ 1214.268813] systemd[1]: Failed to send unit change signal for cups.socket: Transport endpoint is not connected
2140:[ 1214.431672] systemd[1]: Failed to send unit change signal for cups.service: Transport endpoint is not connected
2141:[ 1214.619705] systemd[1]: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
2142:[ 1214.731735] systemd[1]: Failed to send unit change signal for upower.service: Transport endpoint is not connected
2143:[ 1214.838659] systemd[1]: Failed to send unit change signal for network.target: Transport endpoint is not connected
2144:[ 1214.948628] systemd[1]: Failed to send unit change signal for alsa-state.service: Transport endpoint is not connected
2145:[ 1215.085753] systemd[1]: Failed to send job change signal for 840: Transport endpoint is not connected
2146:[ 1215.212979] systemd[1]: Failed to send job change signal for 855: Transport endpoint is not connected
2147:[ 1215.322718] systemd[1]: Failed to send job change signal for 858: Transport endpoint is not connected
2148:[ 1215.434862] systemd[1]: Failed to send job change signal for 863: Transport endpoint is not connected
2149:[ 1215.555885] systemd[1]: Failed to send job change signal for 877: Transport endpoint is not connected
2150:[ 1215.668612] systemd[1]: Failed to send job change signal for 861: Transport endpoint is not connected
2151:[ 1215.780534] systemd[1]: Failed to send job change signal for 885: Transport endpoint is not connected
2153:[ 1216.487137] systemd[1]: Failed to send job remove signal for 877: Transport endpoint is not connected
2156:[ 1217.764705] systemd[1]: Failed to send job remove signal for 858: Transport endpoint is not connected
2157:[ 1218.030729] systemd[1]: Failed to send job remove signal for 857: Transport endpoint is not connected
2159:[ 1218.704701] systemd[1]: Failed to send job remove signal for 838: Transport endpoint is not connected
2160:[ 1218.971950] systemd[1]: Failed to send job remove signal for 883: Transport endpoint is not connected
2164:[ 1220.002684] systemd[1]: Failed to send job remove signal for 848: Transport endpoint is not connected
2165:[ 1220.273615] systemd[1]: Failed to send job remove signal for 878: Transport endpoint is not connected
2166:[ 1220.598670] systemd[1]: Failed to send job remove signal for 876: Transport endpoint is not connected
2168:[ 1220.958741] systemd[1]: Failed to send job remove signal for 884: Transport endpoint is not connected
2171:[ 1221.796701] systemd[1]: Failed to send job remove signal for 885: Transport endpoint is not connected
2174:[ 1222.602011] systemd[1]: Failed to send job remove signal for 886: Transport endpoint is not connected
2179:[ 1224.328711] systemd[1]: Failed to send job remove signal for 863: Transport endpoint is not connected
2181:[ 1224.632891] systemd[1]: Failed to send unit remove signal for polkit.service: Transport endpoint is not connected
2182:[ 1224.712763] systemd[1]: Failed to send unit remove signal for udisks2.service: Transport endpoint is not connected
2183:[ 1224.772714] systemd[1]: Failed to send unit change signal for accounts-daemon.service: Transport endpoint is not connected
2184:[ 1224.832675] systemd[1]: Failed to send unit change signal for NetworkManager.service: Transport endpoint is not connected
2185:[ 1224.895692] systemd[1]: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
2186:[ 1224.954664] systemd[1]: Failed to send unit change signal for smartd.service: Transport endpoint is not connected
2223:[ 1240.778821] systemd[1]: Failed to send job remove signal for 854: Connection reset by peer
2224:[ 1240.938855] systemd[1]: Failed to send unit change signal for chronyd.service: Transport endpoint is not connected
2293:[  OK  ] Failed unmounting /run/initramfs/live.
2313:[ 1264.731722] systemd[1]: Failed to send unit remove signal for tmp.mount: Transport endpoint is not connected
2314:[ 1264.833619] systemd[1]: Failed to send unit remove signal for fedora-import-state.service: Transport endpoint is not connected
2315:[ 1265.033627] systemd[1]: Failed to send unit remove signal for slices.target: Transport endpoint is not connected
2316:[ 1265.110712] systemd[1]: Failed to send unit remove signal for systemd-journald-dev-log.socket: Transport endpoint is not connected
2317:[ 1265.235754] systemd[1]: Failed to send unit remove signal for dmraid-activation.service: Transport endpoint is not connected
2318:[ 1265.310678] systemd[1]: Failed to send unit remove signal for lvm2-monitor.service: Transport endpoint is not connected
2319:[ 1265.383777] systemd[1]: Failed to send unit remove signal for sys-fs-fuse-connections.mount: Transport endpoint is not connected
2320:[ 1265.519852] systemd[1]: Failed to send unit remove signal for dev-mqueue.mount: Transport endpoint is not connected
2321:[ 1265.595667] systemd[1]: Failed to send unit remove signal for systemd-random-seed.service: Transport endpoint is not connected
2322:[ 1265.773649] systemd[1]: Failed to send unit remove signal for cryptsetup.target: Transport endpoint is not connected
2323:[ 1265.853726] systemd[1]: Failed to send unit remove signal for basic.target: Transport endpoint is not connected
2324:[ 1265.938866] systemd[1]: Failed to send unit remove signal for firewalld.service: Transport endpoint is not connected
2325:[ 1266.023606] systemd[1]: Failed to send unit remove signal for fedora-loadmodules.service: Transport endpoint is not connected
2326:[ 1266.107451] systemd[1]: Failed to send unit remove signal for systemd-readahead-done.timer: Transport endpoint is not connected
2327:[ 1266.252832] systemd[1]: Failed to send unit remove signal for rtkit-daemon.service: Transport endpoint is not connected
2328:[ 1266.333647] systemd[1]: Failed to send unit remove signal for livesys.service: Transport endpoint is not connected
2329:[ 1266.422848] systemd[1]: Failed to send unit remove signal for initial-setup-text.service: Transport endpoint is not connected
2330:[ 1266.514764] systemd[1]: Failed to send unit remove signal for abrtd.service: Transport endpoint is not connected
2331:[ 1266.602744] systemd[1]: Failed to send unit remove signal for avahi-daemon.service: Transport endpoint is not connected
2332:[ 1266.692029] systemd[1]: Failed to send unit remove signal for ModemManager.service: Transport endpoint is not connected
2333:[ 1266.779659] systemd[1]: Failed to send unit remove signal for abrt-oops.service: Transport endpoint is not connected
2334:[ 1266.865814] systemd[1]: Failed to send unit remove signal for getty.target: Transport endpoint is not connected
2335:[ 1266.957755] systemd[1]: Failed to send unit remove signal for systemd-ask-password-wall.path: Transport endpoint is not connected
2336:[ 1267.115734] systemd[1]: Failed to send unit remove signal for rc-local.service: Transport endpoint is not connected
2337:[ 1267.200678] systemd[1]: Failed to send unit remove signal for serial-getty: Transport endpoint is not connected
2338:[ 1267.289541] systemd[1]: Failed to send unit remove signal for syslog.target: Transport endpoint is not connected
2339:[ 1267.378948] systemd[1]: Failed to send unit remove signal for ntpdate.service: Transport endpoint is not connected
2340:[ 1267.470678] systemd[1]: Failed to send unit remove signal for time-sync.target: Transport endpoint is not connected
2341:[ 1267.564703] systemd[1]: Failed to send unit remove signal for iptables.service: Transport endpoint is not connected
2342:[ 1267.654822] systemd[1]: Failed to send unit remove signal for serial-getty: Transport endpoint is not connected
2343:[ 1267.741728] systemd[1]: Failed to send unit remove signal for serial-getty: Transport endpoint is not connected
2344:[ 1267.899702] systemd[1]: Failed to send unit remove signal for ebtables.service: Transport endpoint is not connected
2345:[ 1267.984942] systemd[1]: Failed to send unit remove signal for systemd-tmpfiles-clean.service: Transport endpoint is not connected
2346:[ 1268.147650] systemd[1]: Failed to send unit remove signal for systemd-ask-password-console.service: Transport endpoint is not connected
2347:[ 1268.308641] systemd[1]: Failed to send unit remove signal for lvm2-activation-early.service: Transport endpoint is not connected
2348:[ 1268.462820] systemd[1]: Failed to send unit remove signal for iscsid.socket: Transport endpoint is not connected
2349:[ 1268.573737] systemd[1]: Failed to send unit remove signal for rpcbind.service: Transport endpoint is not connected
2350:[ 1268.661645] systemd[1]: Failed to send unit remove signal for systemd-random-seed-load.service: Transport endpoint is not connected
2351:[ 1268.808650] systemd[1]: Failed to send unit remove signal for dev-ttyS1.device: Transport endpoint is not connected
2352:[ 1268.887596] systemd[1]: Failed to send unit remove signal for dev-ttyS3.device: Transport endpoint is not connected
2353:[ 1268.966712] systemd[1]: Failed to send unit remove signal for sys-devices-virtual-block-loop0.device: Transport endpoint is not connected
2354:[ 1269.123668] systemd[1]: Failed to send unit remove signal for dev-loop3.device: Transport endpoint is not connected
2355:[ 1269.208740] systemd[1]: Failed to send unit remove signal for sys-subsystem-net-devices-ens3.device: Transport endpoint is not connected
2356:[ 1269.372586] systemd[1]: Failed to send unit remove signal for sys-devices-virtual-block-dm\x2d1.device: Transport endpoint is not connected
2357:[ 1269.536617] systemd[1]: Failed to send unit remove signal for dev-mapper-live\x2drw.device: Transport endpoint is not connected
2358:[ 1269.687671] systemd[1]: Failed to send unit remove signal for poweroff.target: Transport endpoint is not connected
2359:[ 1269.772703] systemd[1]: Failed to send unit remove signal for plymouth-poweroff.service: Transport endpoint is not connected"

Comment 9 Peter H. Jones 2014-07-02 01:39:56 UTC
Created attachment 913944 [details]
kickstart file

I have a live build that I can't log into in mode 3 when running under qemu. In mode 5, lightdm seemed to be in a loop: the screen would flash up lots of text, then go black. I believe the guest is in permissive mode.

Comment 10 Peter H. Jones 2014-07-02 01:40:55 UTC
Created attachment 913945 [details]
typescript of livecd creation

Comment 11 Peter H. Jones 2014-07-02 01:44:34 UTC
Created attachment 913959 [details]
tyescript of qemu console log

When I booted the ISO image with qemu, I erased the enforcing=1 parameter, leaving the guest in permissive mode. When the login prompt appeared, I tried logging in as "liveuser" and "root", with no password. Both logins failed. Only one seems present in the console log.

Comment 12 Kevin Fenzi 2014-07-02 20:52:39 UTC
So, the orig report here was a f20 xfce spin image, the later report is a custom rawhide kickstart?

I think this in both cases could be a lightdm issue however. 

Moving over there for comment...

Comment 13 Peter H. Jones 2014-07-03 03:44:49 UTC
This is an intermittent problem. If I get it on my custom build, I believe it's worth trying to reproduce it on the distributed Xfce build, as the build and its supporting documentation are available on koji.

Comment 14 Peter H. Jones 2014-07-12 22:45:09 UTC
Created attachment 917559 [details]
typescript of booting Fedora-Live-Xfce-x86_64-rawhide-20140712.iso under qemu

This run makes me think the problem might be in selinux. I booted Fedora-Live-Xfce-x86_64-rawhide-20140712.iso, used the tab key to edit the command line as follows:
"BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Xfce-x86_64-rawhide- rootfstype=auto ro rd.live.image debug rd.luks=0 rd.md=0 rd.dm=0 console=ttyS0 enforcing=0 3"

The login prompt appeared, and I was able to log in as root, and poweroff.

grep -n avc: <typescript-file> gives:
"1849:[  305.824452] audit: type=1400 audit(1405203940.085:3): avc:  denied  { read } for  pid=643 comm="auditd" name="group" dev="dm-0" ino=16 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=1
1850:[  305.827013] audit: type=1400 audit(1405203940.089:4): avc:  denied  { open } for  pid=643 comm="auditd" path="/etc/group" dev="dm-0" ino=16 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=1
1851:[  305.843863] audit: type=1400 audit(1405203940.106:5): avc:  denied  { getattr } for  pid=643 comm="auditd" path="/etc/group" dev="dm-0" ino=16 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=1
"

Comment 15 Kevin Fenzi 2014-07-13 21:20:16 UTC
Possibly a dupe there of https://bugzilla.redhat.com/show_bug.cgi?id=1116450 ?

Comment 16 Fedora End Of Life 2015-05-29 11:06:45 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2015-06-30 00:55:20 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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