pprkut at liwjatan.at
Fri Sep 26 10:48:28 UTC 2008
Audrius Kažukauskas wrote:
> I am using KDE 4.1.1 from -current and VirtualBox 2.0.2 which I've built
> using a SlackBuild from SBo, and there's no menu entry for it in KMenu
> (or whatever it's called right now), neither I can run it by typing
> `VirtualBox' in command line. The only way to run it is to type a full
> path to /usr/lib/virtualbox/VirtualBox (BTW, it's a bit strange place
> for the executable file). If I remember correctly, there was no such
> problem with KDE3 and VirtualBox 1.6.x. I understand that SBo scripts
> are meant to use in -stable, but still this seems wrong. Is it just me
> or is it a problem of VirtualBox itself? Oh, and I've built VBox with
> VBOXUSERS=no QT4=yes QT3=no flags.
This seems strange. I can't tell about the menu-thing, as I don't have the
time to build virtualbox on current at the moment, but you should be able to
start virtualbox via command-line by typing "VirtualBox".
Things you can check:
-) Is there a /etc/vbox/vbox.conf.new? If yes, replace it with the old one.
-) Is there a /usr/bin/VirtualBox and/or /usr/bin/VBox?
Having the binaries in /usr/lib/virtualbox is indeed not perfect, but
currently it is along the lines of other distributions. I will eventually try
to move them directly into /usr/bin, but this will not be easy and I don't
know if it is possible at all.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the SlackBuilds-users