I was instructed to switch to UDEV, in order to recieve dbus messages when new device nodes are created However, upon installation of UDEV and dbus, and invocation of 'dbus-monitor --system', no messages from the system are logged. If I manually send a message via dbus-send, the message is logged. (This could also actually be a problem with UDEV, or pebkac, but I'll start here) This also could be an explanation to the problem, so I'll include it: My system is a headless server with a barebones video card, no sound, and has been built accordingly. dbus-0.22-r1 seems to have dependancies on gtk+, and virtual/x11 according to http://www.gentoo-portage.com/sys-apps/dbus/dep . Are those two really needed? with my USE flags, dbus compiled without any apparent problems.. Reproducible: Always Steps to Reproduce: 1.emerge udev, according to the details in http://www.gentoo.org/doc/en/udev-guide.xml 2.emerge dbus, according to http://forums.gentoo.org/viewtopic.php?t=185508 3.start 'dbus-monitor --system', and do any sort of hardware modification (unplug and reinsert USB device, eject and insert CD-ROM drive, etc) Actual Results: Everything was built without any problems, and also started without any problems. When any sort of hardware modification was done, either udev didn't send the messages to dbus, or udev send them, and udev didn't recieve them. Expected Results: 'dbus-monitor --system' should have shown that a message had been sent across dbus when the hardware was modified. coldfire root # uname -a Linux coldfire 2.6.9-gentoo-r4 #1 Sun Nov 14 23:26:53 CST 2004 i686 AMD Duron (tm) processor AuthenticAMD GNU/Linux coldfire root # emerge info Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-2.3.4.20040808- r1, 2.6.9-gentoo-r4 i686) ================================================================= System uname: 2.6.9-gentoo-r4 i686 AMD Duron(tm) processor Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O2 -mmmx -m3dnow -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share /config /var/bind /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-tbird -O2 -mmmx -m3dnow -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="berkdb bitmap-fonts crypt cups encode f77 foomaticdb fortran gdbm imagemagick libwww maildir mysql ncurses nls pam perl pop3 readline samba sdl ssl tcpd tiff x86 xml xml2 zlib"
Thats because dbus doesn't monitor hardware device changes directly. You are thinking of HAL, which uses dbus to send messages. The X and gtk deps are clearly marked by useflags, and obviously not required for dbus.
