Here's my theory. If anyone has suggestions on how to avoid this it would
be most welcome.
I use Jarod's ~/.kde/Autostart/myth-load.sh, which among other things starts
mythfrontend.
Since vnc starts a new KDE session, I think this gets run again for the vnc
session and therefore mythfrontend starts a second time.
I would think this would be common as I suspect many people use both Jarod's
script and vnc.
add the following into your myth-load.sh file:
--- MYTH="`ps ax | grep mythfrontend | grep -v grep`"
if [ ! "$MYTH" ] then # place all stuff you want to run with mythfrontend here /path/to/bin/mythfrontend fi ---
that checks for a running mythfrontend process and only executes the code inside the if/then if there isn't already a mythfrontend process running ...
-g-
I tried this method first as I thought this was a nicer way to deal with it.
It worked, but backwards.
It appears that as the vncservice starts the first mythfrontend.
Then when the desired mythfrontend should get started it can't because the script sees it as already running.
It is nice to see I'm not alone on this though.
I prefer to keep the vnc service on.
I'll look into the other solution about the windows manager. I'll have to do more reading about that and educate myself.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
