Is there a problem with the way YAVDR and its front-end starts now? I regularly see multiple instances of dbus-daemon in the process list: -
102 1313 1 0 13:21 ? 00:00:00 dbus-daemon --system --fork --activation=upstart
root 1354 1 0 13:21 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 1796 1 0 13:22 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 1968 1 0 13:22 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 1977 1 0 13:22 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 1986 1 0 13:22 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2340 1 0 13:23 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2355 1 0 13:23 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2373 1 0 13:23 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2393 1 0 13:23 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2406 1 0 13:24 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2421 1 0 13:24 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2490 1 0 13:24 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2561 1 0 13:24 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2578 1 0 13:25 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2589 1 0 13:25 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2602 1 0 13:25 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2613 1 0 13:25 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2624 1 0 13:26 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2635 1 0 13:26 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2646 1 0 13:26 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root 2658 1 0 13:27 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
and quite often the VDR frontend doesn't start properly, either showing the YAVDR blue logo or a black screen with mouse pointer and no frontend.
This happens frequently on a normal reboot, or wake from S3.
Is there anything I can do to debug this isseu further? It seems to happen with both xine front end and softhddevice. I am using a NVIDIA G210.
Thanks,
Morfsta