dbus_glib.tcel

[jpeters]

After installing dbus_glib.tcel and attempting to run skype_dynamic I get:

Code: [Select]

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

Skype dynamic almost loads with qt-4.2.2 and a few support libs . It flashes before producing the dbus error. 

[Juanito]

You get this error message because the dbus daemon is not running, you can start it with:

Code: [Select]

$ sudo mkdir -p /var/lib/dbus
$ sudo dbus-uuidgen --ensure
$ sudo mkdir /var/run/dbus
$ sudo dbus-daemon --system
$ sudo mkdir /etc/dbus-1/session.d


[jpeters]

Code: [Select]

tc@box:/etc/dbus-1$ sudo dbus-uuidgen
4eae464456c126bba267d7124a03e3af

but...

Code: [Select]

tc@box:~$ sudo dbus-daemon --system
Failed to start message bus: Failed to read directory "/etc/dbus-1/system.d": No such file or directory


[Juanito]

Ah - OK, I use dbus with bluez which contains files in "/etc/dbus-1/system.d" so it already exists - I guess you'll need to create this directory before "sudo dbus-daemon --system"

[jpeters]

Thanks....that got it working.  Unfortunately, skype dynamic does exactly what skype static does.....accepts login  and then just disappears with

Code: [Select]

terminate called after throwing an instance of 'unsigned int'
Aborted

BTW....that list might be nice on the info file. 

[jpeters]

You get this error message because the dbus daemon is not running, you can start it with:

Code: [Select]

$ sudo mkdir -p /var/lib/dbus
$ sudo dbus-uuidgen --ensure
$ sudo mkdir /var/run/dbus
$ sudo dbus-daemon --system
$ sudo mkdir /etc/dbus-1/session.d


For the record. the last line should read   " sudo mkdir  /etc/dbus-1/system.d"    (and be placed before running the dbus-daemon).   

[Juanito]

Depending on the circumstances, you might need both "session.d" and "system.d"...

[jpeters]

Depending on the circumstances, you might need both "session.d" and "system.d"...

Thanks for the clarification....I thought it was a typo..