> -----Original Message----- > From: Michael Thayer [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 14, 2007 1:12 PM > To: [EMAIL PROTECTED]; VirtualBox end user list > Subject: Re: [vbox-users] 1.3.8 - openSUSE 10.2 - "Failed to > initialize COM ... VirtualBox COM server" error > > Hello Pablo,
Hi Michael, > Sure. If I see the problem correctly, it is that we do not support > session management correctly. I had noticed that before, but was too > lazy to do anything about it :) Ah but it worked okay in 1.3.6 - no error. Let me go install 1.3.6 now .... <off to un-install .8, re-install .6> Hog dang, I'm wrong. I see the same two processes in .6 after I stop the main GUI: ... 5588 1 0 13:28 ? 00:00:00 /opt/VirtualBox-1.3.6/VBoxSVC --daemonize ... 5591 5588 0 13:28 ? 00:00:00 /opt/VirtualBox-1.3.6/VBoxXPCOMIPCD However after doing a reboot, I don't get the same error as in .8 Strange. I also checked that /etc/init.d/vboxdrv is starting at the same levels in .8 as in .6 - although it's only doing an insmod. Michael, is there some other session-specific change which occurred in .8? Seems .8 is trying to tell KDE to save its state whereas in .6, it wasn't. Once I have enough data, I'll log the bug. Or I can log it as is now. Please let me know. Cheers, -pablo _______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
