Description of problem: Trying to use lorax to make a rawhide netboot.iso on an up to date Fedora 18 host. lorax creates a directory tree for yum to install rpms into. Inside the chroot there are no dbus daemons and the tree is pretty bare. at-spi appears to be using gconftool-2 which blows up because it finds a blank /etc/machine-id file. I can reproduce this inside the chroot manually by running: # export GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults # gconftool-2 --makefile-install-rule /etc/gconf/schemas/at-spi.schemas process 6064: D-Bus library appears to be incorrectly set up; failed to read machine uuid: UUID file '/etc/machine-id' should contain a hex string of length 32, not length 0, with no other text See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace Aborted (core dumped) Version-Release number of selected component: GConf2-3.2.6-1.fc19 Additional info: backtrace_rating: 4 cmdline: gconftool-2 --makefile-install-rule /etc/gconf/schemas/at-spi.schemas core_backtrace: 336dfc39ff6a19ad2875d113088ba22db5c2d52d 0x35de5 _nl_find_msg /lib64/libc.so.6 8ab35d9e553bf1b0cdd88062d0aba6b4c4f8e086 crash_function: _dbus_abort executable: /var/tmp/lorax.6SOh97/installtree/usr/bin/gconftool-2 kernel: 3.7.4-204.fc18.x86_64 os_release_in_rootdir: Fedora release 19 (Rawhide) remote_result: NOTFOUND rootdir: /var/tmp/lorax.6SOh97/installtree uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 _dbus_abort at dbus-sysdeps.c:94 #3 _dbus_warn_check_failed at dbus-internals.c:290 #4 _dbus_get_local_machine_uuid_encoded at dbus-internals.c:882 #5 _dbus_get_autolaunch_address at dbus-sysdeps-unix.c:3465 #6 _dbus_transport_new_for_autolaunch at dbus-transport.c:292 #7 _dbus_transport_open_autolaunch at dbus-transport.c:323 #9 _dbus_transport_open at dbus-transport.c:391 #10 connection_try_from_address_entry at dbus-connection.c:1801 #11 _dbus_connection_open_internal at dbus-connection.c:1870 #12 dbus_connection_open_private at dbus-connection.c:2623
Created attachment 693106 [details] File: backtrace
Created attachment 693107 [details] File: cgroup
Created attachment 693108 [details] File: environ
Created attachment 693109 [details] File: limits
Created attachment 693110 [details] File: maps
Created attachment 693111 [details] File: open_fds
Created attachment 693112 [details] File: proc_pid_status
Created attachment 693113 [details] File: var_log_messages
dbus requires a machine-id to be generated at startup. I think systemd does this with systemd-machine-id-setup
(s/startup/first startup/)
this is probably caused by this change: https://bugzilla.gnome.org/show_bug.cgi?id=671490
talked to bcl. I think the problem will go away if lorax scrubs the chroot environment, so bits from the host don't leak in (like DISPLAY and DBUS_SESSION_BUS_ADDRESS)
Fix this by unsetting DISPLAY and DBUS_SESSION_BUS_ADDRESS in lorax.
(In reply to comment #13) > Fix this by unsetting DISPLAY and DBUS_SESSION_BUS_ADDRESS in lorax. this is fixed where, I still need unset DISPLAY before compose repo with pungi