Author Topic: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'  (Read 4487 times)

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
I fixed this with a sym link. On ubuntu the location appears to be /var/lib/dbus/machine-id

process 11552: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/usr/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

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3645
  • Hero Points: 236
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #1 on: December 15, 2014, 10:54:07 pm »
What version of Ubuntu are you running?

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #2 on: December 15, 2014, 11:07:10 pm »
14.04 and 10.04

'/usr/var' seems odd to me. Isn't it normally '/var'?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3645
  • Hero Points: 236
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #3 on: December 15, 2014, 11:37:41 pm »
Hmm...that's what I typically run. Are you running the 64-bit version?

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #4 on: December 15, 2014, 11:41:15 pm »
the 14.04 is 64, the 10.04 is 32 bit.

Neither of them have a /usr/var directory.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3645
  • Hero Points: 236
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #5 on: December 16, 2014, 03:51:10 am »
/usr/var doesn't exist on Ubuntu 32 bit or 64 bit on my machines either. I have no problem running SlickEdit though. There's must be some other difference. Not sure what. I remember there being an ubuntu goof up related to dbus but I thought that was ubuntu 12. I vaguely remember seeing a problem with a particular update. I haven't seen it since though.

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #6 on: December 16, 2014, 03:52:21 am »
No biggy :)

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 236
  • Hero Points: 22
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #7 on: December 17, 2014, 10:59:51 pm »
This has been seen in a basic (essentially headless) linux install that was missing some packages.

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.

jvert

  • Community Member
  • Posts: 30
  • Hero Points: 2
Re: 19.01.1 launch failed - 'Failed to open "/usr/var/lib/dbus/machine-id"'
« Reply #8 on: January 15, 2015, 06:14:32 pm »
I have the same problem on x64 Ubuntu 14.04. There is no /usr/var/lib/dbus/machine-id, only /var/lib/dbus/machine-id.

I fixed it with a symlink, but it seems to be a new problem with 19.01.1.

sipho

  • Junior Community Member
  • Posts: 3
  • Hero Points: 0
Same issue here when installing 19.0.1.1 over 18.0.?.? on 64 bit Ubuntu 14.04. But only when run through an ssh client with X11-forwarding. Running it from the icon on Ubuntu's desktop worked fine. Creating a symlink /usr/var/lib/dbus/machine-id to /var/lib/dbus/machine-id "fixed" the issue. But version 18 worked fine without this.

zrax

  • New Community Member
  • Posts: 1
  • Hero Points: 2
It seems to be an issue with the included dbus library (bin/libdbus-1.so.3).  I removed this file, to force the system copy to be found, and slickedit works fine again (on both Ubuntu and RHEL6).