gnome-terminal says: Failed to open file “/var/local/lib/dbus/machine-id”: No such file or directory

[siguri]

Dear Sir,
trying to start gnome-terminal after update, I get

# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Cannot spawn a message bus without a machine-id: Unable to load /var/local/lib/dbus/machine-id or /etc/machine-id: Failed to open file “/var/local/lib/dbus/machine-id”: No such file or directory

may I get a hint, please where to look for a clue?

 

[gpw928]

Have you got dbus_enable="YES" in /etc/rc.conf?

 

[elgrande]

Or easier:
service enable dbus
and then
service start dbus.

 

[Alex Seitsinger]

I believe this is due to a linuxism being lost in translation. Fortunately, you can use the following code to silence this error. Here's a link to a explanation: https://www.freedesktop.org/software/systemd/man/machine-id.html

/usr/bin/touch /etc/machine-id
/usr/local/bin/dbus-uuidgen >> /etc/machine-id
/usr/sbin/service dbus restart

 

[kent_dorfman766]

the fact that a terminal window has anything to do with dbus in the first place?...sigh

 

[siguri]

...sigh

The others gave me the hint and I found peace of mind w/ my gnome-terminal again.

 

[kent_dorfman766]

The others gave me the hint and I found peace of mind w/ my gnome-terminal again.

my infered answer was that a "normal" terminal (xterm, lxterm, etc) wouldn't care about dbus because they behave the way a terminal is suppose to and are not linked with a bunch of useless bloatware libraries.

But, if it works now then I suppose you are good until you run into the next gnome inspired problem.

 

[elgrande]

my infered answer was that a "normal" terminal (xterm, lxterm, etc) wouldn't care about dbus because they behave the way a terminal is suppose to and are not linked with a bunch of useless bloatware libraries.

But, if it works now then I suppose you are good until you run into the next gnome inspired problem.

But then drm cannot exclude terminals via dbus