Bug 1045850

Summary: lxde livecd 32 bit liveinst fails on some computers
Product: [Fedora] Fedora Reporter: jeff <jeff>
Component: LiveCDAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 20CC: hlovdal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:43:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
strace output from failing udisks none

Description jeff 2013-12-22 14:58:48 UTC
Description of problem:

1) the 'install to hard drive' icon and menu fail.
2) WHen I run liveinst from a terminal, I get an error:
root being added to access control list
Inhibit all polling failed: Did not receive a reply. Possible causes include...

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

Fedora 20

How reproducible:

On my compaq evo n600c, 100% error
On my ibm t40p, I can sometimes start liveinst, but it takes a very long time.

Steps to Reproduce:
1. click on install to hard drive icon, menu entry, or from a lxterminal start liveinst
2. failure
3.

Actual results:

failure

Expected results:

I expect liveinst to start

Additional info:

I reported this bug 1032355, but it seems not have been completely fixed.
It does work when I run from vmware player.

Comment 1 Håkon Løvdal 2014-03-23 18:45:09 UTC
I can confirm that the same bug is also present when trying to install Fedora 20 from a 32bit kde livecd to an Asus A6000 pc. All 10-20 attempts to start the liveinst program has failed.

From my searching so far this seems to be related to be d-bus related. From http://kkaempf.blogspot.com/2009/03/d-bus-service-on-demand.html?showComment=1268111398629#c7898965014984453127:


the problem was ... file ownership ... One of the files that got changed to root:root ownership was dbus-daemon-launch-helper. That has now been fixed and the installer is running in a VM as I'm typing this.

Oh yeah, the weird error message was something about "Inhibit all polling failed..."

Comment 2 Håkon Løvdal 2014-03-23 19:37:04 UTC
Created attachment 877902 [details]
strace output from failing udisks

Extract from a log from running liveinst through strace, showing that the failing point is the udisks program.

Summary:

execve("/usr/bin/udisks", ["/usr/bin/udisks", "--inhibit", "--", "anaconda", "--liveinst", "--method=livecd:///dev/mapper/live-base"], [/* 19 vars */]) = 0
...
connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 33) = 0
...
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"l\3\1\1G\0\0\0\3\0\0\0u\0\0\0\6\1s\0\6\0\0\0:1.117\0\0\4\1s\0)\0\0\0org.freedesktop.DBus.Error.NameHasNoOwner\0\0\0\0\0\0\0\5\1u\0\4\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0B\0\0\0Could not get owner of name 'org.freedesktop.UDisks': no such name\0l\3\1\1G\0\0\0\4\0\0\0u\0\0\0\6\1s\0\6\0\0\0:1.117\0\0\4\1s\0)\0\0\0org.freedesktop.DBus.Error.NameHasNoOwner\0\0\0\0\0\0\0\5\1u\0\5\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0B\0\0\0Could not get owner of name 'org.freedesktop.UDisks': no such name\0", 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 414
...
write(1, "Inhibit all polling failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.\n", 239) = 239

Comment 3 Håkon Løvdal 2014-03-23 22:15:59 UTC
Several other services had problems, for instance logind:

...
Mar 23 17:57:53 localhost systemd-logind: Watching system buttons on /dev/input/event1 (Sleep Button)
Mar 23 17:58:58 localhost systemd: systemd-logind.service operation timed out. Terminating.
Mar 23 17:58:58 localhost systemd: Failed to start Login Service.
Mar 23 17:58:58 localhost systemd: Unit systemd-logind.service entered failed state.
Mar 23 17:58:58 localhost systemd: systemd-logind.service holdoff time over, scheduling restart.
Mar 23 17:58:58 localhost systemd: Stopping Login Service...
Mar 23 17:58:58 localhost systemd: Starting Login Service...
Mar 23 17:59:21 localhost dbus-daemon: dbus[671]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Mar 23 17:59:21 localhost dbus[671]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Mar 23 17:59:23 localhost dbus-daemon: dbus[671]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mar 23 17:59:23 localhost dbus[671]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mar 23 17:59:23 localhost systemd-logind: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Mar 23 17:59:23 localhost systemd-logind: New seat seat0.
Mar 23 17:59:23 localhost systemd-logind: Watching system buttons on /dev/input/event2 (Power Button)
Mar 23 17:59:23 localhost systemd-logind: Watching system buttons on /dev/input/event5 (Video Bus)
Mar 23 17:59:23 localhost systemd-logind: Watching system buttons on /dev/input/event0 (Lid Switch)
Mar 23 17:59:23 localhost systemd-logind: Watching system buttons on /dev/input/event1 (Sleep Button)
...

So trying to log in on the Ctrl-Alt-F2 tty was not possible (completely black screen, no text).

Updating systemd with "yum update systemd" to version systemd-208-15.fc20.i686 solved at least the logind problem, and now liveinst is able to successfully start anaconda. So it seems like the core problem was something with the systemd version used on the livecd.

Comment 4 Fedora End Of Life 2015-05-29 10:06:38 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 5 Fedora End Of Life 2015-06-29 13:43:19 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.