| Summary: | gnome-base/dconf-0.26.0-r1 : ERROR:dbus.c:237:test_sync_call_success: assertion failed (error == NULL): Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /.../machine-id: Failed to open file ?/.../machine-id?: No | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 gnome-base:dconf-0.26.0-r1:20170901-045109.log logs.tbz2 temp.tbz2 tests.tbz2 |
||
Created attachment 491470 [details]
emerge-info.txt
Created attachment 491472 [details]
emerge-history.txt
Created attachment 491474 [details]
environment
Created attachment 491476 [details]
etc.portage.tbz2
Created attachment 491478 [details]
gnome-base:dconf-0.26.0-r1:20170901-045109.log
Created attachment 491480 [details]
logs.tbz2
Created attachment 491482 [details]
temp.tbz2
Created attachment 491484 [details]
tests.tbz2
This should be provided by either systemd or dbus afaik but I see it is not pulled in the dependency tree. damn, now that I read the ebuild, dbus is indeed pulled in in RDEPEND+DEPEND, why is it missing from your system ? FTR, machine-id is generated in dbus postinst so it is enough to have dbus installed. It needs not to be running. (In reply to Gilles Dartiguelongue from comment #11) > FTR, machine-id is generated in dbus postinst so it is enough to have dbus > installed. It needs not to be running. It is likely that /etc/machine-id gets removed during the tinderbox image creation process, similar to what we do for the systemd stage3 tarballs. Anyone using such an image in a chroot environment is expected to regenerate it. (In reply to Mike Gilbert from comment #12) Hhm, I do have : tinderbox@mr-fox ~ $ ll ~/run/*/etc/mach* -rw-r--r-- 1 root root 33 Aug 30 21:33 /home/tinderbox/run/13.0_20170828-211425/etc/machine-id -rw-r--r-- 1 root root 33 Aug 30 23:13 /home/tinderbox/run/13.0-desktop_20170828-210912/etc/machine-id -rw-r--r-- 1 root root 33 Aug 29 06:43 /home/tinderbox/run/13.0-desktop-gnome_abi32+64_20170828-210916/etc/machine-id -rw-r--r-- 1 root root 33 Aug 29 04:27 /home/tinderbox/run/13.0-desktop-plasma_20170828-210922/etc/machine-id -rw-r--r-- 1 root root 33 Aug 29 06:39 /home/tinderbox/run/13.0-no-multilib_20170828-210950/etc/machine-id And I do not touch theat file at all - but I'll add a check to my box to see, which packages will remove it. (In reply to Toralf Förster from comment #13) > And I do not touch theat file at all - but I'll add a check to my box to > see, which packages will remove it. What stage tarball do you use? As I said, the systemd stage3 tarballs will not have it, and dbus pkg_postinst will not be run since dbus is already installed. (In reply to Mike Gilbert from comment #14) I do use stage3 - yes. And mostly I set ~amd64 in make.conf, so the first @system (scheduled immediately after upgrading gcc and revdep-rebuild) should upgrade dbus and run then pkg_postinst(), right ? (In reply to Toralf Förster from comment #15) Yeah, that probably should have created it. I'm not sure what happened. (In reply to Mike Gilbert from comment #16) Well, have now a check in place : if [[ "$task" = "sys-apps/dbus" && ! -f /etc/machine-id ]]; then echo "/etc/machine-id is missing" rc=1 fi Maybe my general switch from "check few packages at every image" to "check every package at few systems" played a role here - so if this issue doesn't appear again, then it was just image specific. |
/gdbus/thread/creation/error: OK /gdbus/thread/sync-call/success: ** ERROR:dbus.c:237:test_sync_call_success: assertion failed (error == NULL): Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file ?/var/lib/dbus/machine-id?: No such file or directory (g-file-error-quark, 4) FAIL GTester: last random seed: R02S8fbe507c2cd32aff47a9c628d4f3550e make[2]: *** [Makefile:927: test-nonrecursive] Terminated ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-plasma-systemd_20170831-193500 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) emerge -qpv gnome-base/dconf [ebuild N ] gnome-base/dconf-0.26.0-r1 USE="{-test}"