-   Slackware (
-   -   DBUS Problem at -Current (

willysr 03-25-2007 09:31 PM

DBUS Problem at -Current
I noticed an error message everytime i started my system saying about DBUS. I tried to reproduce the error by running :

root@laptop:/etc/dbus-1# dbus-uuidgen
dbus-uuidgen: symbol lookup error: dbus-uuidgen: undefined symbol: dbus_internal_do_not_use_create_uuid
Does anybody has a solution on this?

NB: Using Slackware-Current

rworkman 03-26-2007 09:59 AM

Show the output of:
ls /var/log/packages/dbus*
ldd /usr/bin/dbus-uuidgen
ldd /usr/bin/dbus-daemon

My first guess, even without seeing the output of those things, is that you had previously installed dbus on your own, most likely to /usr/local, and now the libs in /usr/local/lib are being seen instead of the correct ones in /usr/lib.
Also, make sure you have all of your packages are in sync with what's currently available in the -current tree - see the CHANGES_AND_HINTS.TXT file for pointers.


willysr 03-26-2007 08:20 PM


willy@laptop:~$ ls /var/log/packages/dbus*
/var/log/packages/dbus-1.0.2-i486-1 /var/log/packages/dbus-qt3-0.70-i486-1

willy@laptop:~$ ldd /usr/bin/dbus-uuidgen => (0xffffe000)
/lib/ (0xb7f52000) => /usr/local/lib/ (0xb7f06000) => /lib/ (0xb7dc3000) => /lib/ (0xb7dbf000) => /lib/ (0xb7da8000)
/lib/ (0xb7f59000)

willy@laptop:~$ ldd /usr/bin/dbus-daemon => (0xffffe000)
/lib/ (0xb7f39000) => /usr/lib/ (0xb7efb000) => /lib/ (0xb7db8000) => /lib/ (0xb7db4000)
/lib/ (0xb7f40000)
Yes, i do have dbus installed before i upgrade to -Current, but i already uninstalled it before i upgrade to -Current. My packages are already in sync with -current and i do have look on that file before i commit the upgrades

Thanks Before

willysr 03-26-2007 08:34 PM

Problem FIXED :D
Hello Rob,

Thanks for your help and your analysis is correct. It seems that dbus installation didn't clean up the library even after i commit make uninstall, so it's still left there. After i removed it, i can start the messagebus daemon again and dbus-uuidgen can now work perfectly

Thanks :D

rworkman 03-26-2007 09:28 PM

Yes, and you see now why I asked :) => /usr/local/lib/ (0xb7f06000)
This happens to a lot of people, and that's why I *strongly* recommend that people package every piece of software that they install, even if it's only with checkinstall or slacktrack. That way, you can be much more assured of removing the stale bits later when you upgrade it.
Either way, I'm glad it's working for you now. Also, I received your email and am writing a reply now.


willysr 03-26-2007 09:45 PM

yes, i never used checkinstall nor slacktrack, but i guess i should get used to it now :D

MS3FGX 03-26-2007 10:01 PM

Yeah, you should definitely be using checkinstall rather than just doing a "make install". you can never be sure what is happening if you just let it install however it wants. This becomes a problem when it is time to install if some files are left behind.

Of course, that is assuming the source package's makefile even has a "uninstall" target in the first place, which not all of them do.

All times are GMT -5. The time now is 11:26 PM.