A simple fix for once. I usually see this problem when I’ve installed a barebones / headless system and then wanted to add xorg to it later.
This particular time, this error cropped up when trying to run Eclipse Memory Analyzer over a X11 Forwarding session using SSH. Eclipse would throw this error and fail to start.
process 3104: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
JVMDUMP006I Processing dump event "abort", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/root/mem/mat/core.20111216.145922.3104.0001.dmp' in response to an event
JVMDUMP010I System dump written to /root/mem/mat/core.20111216.145922.3104.0001.dmp
JVMDUMP032I JVM requested Java dump using '/root/mem/mat/javacore.20111216.145922.3104.0002.txt' in response to an event
JVMDUMP010I Java dump written to /root/mem/mat/javacore.20111216.145922.3104.0002.txt
JVMDUMP032I JVM requested Snap dump using '/root/mem/mat/Snap.20111216.145922.3104.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /root/mem/mat/Snap.20111216.145922.3104.0003.trc
JVMDUMP013I Processed dump event "abort", detail "".
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
JVMDUMP006I Processing dump event "abort", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/root/mem/mat/core.20111216.145922.3104.0001.dmp' in response to an event
JVMDUMP010I System dump written to /root/mem/mat/core.20111216.145922.3104.0001.dmp
JVMDUMP032I JVM requested Java dump using '/root/mem/mat/javacore.20111216.145922.3104.0002.txt' in response to an event
JVMDUMP010I Java dump written to /root/mem/mat/javacore.20111216.145922.3104.0002.txt
JVMDUMP032I JVM requested Snap dump using '/root/mem/mat/Snap.20111216.145922.3104.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /root/mem/mat/Snap.20111216.145922.3104.0003.trc
JVMDUMP013I Processed dump event "abort", detail "".
To fix it, run
dbus-uuidgen > /var/lib/dbus/machine-id
If you don’t have dbus-uuidgen , it’s in the dbus package, which can be installed by issuing yum install dbus (of course!).
Happy weekend!
Pingback: D-Bus library appears to be incorrectly set up; failed to read machine uuid: “/etc/machine-id” is not a regular file See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace Abor
Thank you. This has been a quick solution thanks to you.
Thank you 3rd time 😉
Thank you!
Sir you are a genius thanks
holy cow. i did not expect this one to be that easy. thanks!
Great. Worked like a charm.
Thanks for sharing
Thanks , Just do it will be ok !
When I run
” dbus-uuidgen > /var/lib/dbus/machine-id”
I keep getting
” bash: /var/lib/dbus/machine-id: Permission denied”
Help pleae
Hi ,
Try, “sudo dbus-uuidgen > /var/lib/dbus/machine-id”
Cheers,
Graham.
I did try
“sudo dbus-uuidgen > /var/lib/dbus/machine-idâ€
same result
†bash: /var/lib/dbus/machine-id: Permission deniedâ€
Best Regards
sudo dbus-uuidgen –ensure
Thankks !! you save me !
Thanks for the quick solution!
@mkhalil: I had the same problem too, I ended up creating the file manually and copying the generated ID into it:
sudo touch /var/lib/dbus/machine-id
dbus-uuidgen
#copy the generated ID
sudo vim /var/lib/dbus/machine-id
#paste it in and save
This solved the problem here as well. Needed this to start headless skype + bitlbee. Thanks a lot!
Thanks for sharing this! My exact problem and solution.
I hunted for quite a while to find this solution. Thank you for such a clear and concise answer.
Thank you.
Like KJ I had to create the machine-id file myself in the /etc/ folder . I am using FreeBSD 10.2 … but thank you, Firefox works now! 🙂
you ROCK G!
Thank you, it was great help
Thanks a lot this saved me a week of debbuging
Thanks Graham this did the trick. I don’t know why the package wouldn’t generate an ID by default.
for me this happened running spyder in Windows Subsystem for Linux. The location expected was actually /etc/machine-id and the command above got permission denied even with sudo, so I just called dbus-uuidgen by itself, copied the id, then did sudo nano /etc/machine-id and pasted the id, and saved/exited. Then spyder worked (of course I already installed xming)
This fixed a bug in Firefox for me on FreeBSD! Thank you!
Fantastic. This worked for me as well thanks so much.
Running on Docker CentOS7.