Thank you, that did seem to fix dbus. The only filesystem it modified was /. Everything else was clean.
Unforch, it didn't do much for udev, usb & bluetooth.
My logs are growing by the megabyte with:
Jun 24 21:40:16 coyote klogd: usb 1-22.214.171.124.4: usbfs: interface 0 claimed by usblp while 'usb' sets config #1
Jun 24 21:40:51 coyote last message repeated 7 times
Jun 24 21:41:56 coyote last message repeated 13 times
Jun 24 21:43:01 coyote last message repeated 13 times
Jun 24 21:44:02 coyote last message repeated 12 times
Jun 24 21:44:57 coyote last message repeated 11 times
Aha!! I may have just now found that too. It seems my Epson NX-515 MFP did not come back on after the power was restored, and there was a print job pending, last nights amanda report.
That thing is worse than a laser since it takes about 4 minutes, wasting ink making sure it is well primed, before it will allow the print job to proceed. It is turning into a PIMA..
That leaves the missing bluetooth... Running blueman-manager returns:
Loading configuration plugins
GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL)
[root@coyote rules.d]# ps -ea|grep blue
4083 ? 00:00:00 blueman-applet
6331 ? 00:00:00 bluetoothd
6345 ? 00:00:00 bluedevil-helpe
15278 ? 00:00:00 bluedevil-monol
looks normal I think. Or is it? At BT stuff, I am a noob.
From an lsmod:
bluetooth 51698 9 rfcomm,sco,bnep,l2cap,btusb
rfkill 12694 3 bluetooth
But no /dev/rfcomm0 has been created. Anybody have a clue why not?
Thanks & Cheers, Gene