I'm running the latest F18 nightly snapshot that I can find (17 Sept) fully updated via yum, on a Dreamplug.

When the system boots, it reports the following: 
Oct 21 16:53:12 asenath dbus-daemon[287]: dbus[287]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Oct 21 16:53:12 asenath dbus[287]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Oct 21 16:53:12 asenath systemd[1]: Starting Authorization Manager...
Oct 21 16:53:12 asenath systemd[1]: polkit.service: main process exited, code=killed, status=4
Oct 21 16:53:12 asenath systemd[1]: Failed to start Authorization Manager.
Oct 21 16:53:12 asenath systemd[1]: Unit polkit.service entered failed state.
Oct 21 16:53:37 asenath dbus-daemon[287]: dbus[287]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Oct 21 16:53:37 asenath dbus[287]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
When I manually run /usr/lib/polkit-1/polkitd it immediately reports "Illegal instruction".

Running polkitd under gdb, it reports: 
Program received signal SIGILL, Illegal instruction.
0xb699c450 in _GLOBAL__sub_I_jsarray.cpp () from /lib/libmozjs185.so.1.0

Looking at the build log of js on Koji for armv5tel, all the c++ and gcc command lines have the option -march=armv7-a after the option -march=armv5te, so presumably the js package for armv5tel is actually being built for armv7.

The problem appears to be in the configure.in script where for any arm architecture, it sets MOZ_ARM_ARCH to armv7-a: 
dnl Setup default CPU arch for arm target
AC_MSG_WARN([target cpu is ($target_cpu)])
case "$target_cpu" in
  arm*)
    MOZ_ARM_ARCH=armv7
  ;;
esac
Attached is a patch that sets MOZ_ARM_ARCH to armv5te if $target_cpu is armv5tel.

I have build the modified js package and Authorisation Manager now successfully starts.

Should I report this anywhere else, or is this email sufficient for this problem to be resolved.

Quentin Armitage