(process:9060): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:
http://www.gtk.org/setuid.html
Refusing to initialize GTK+.
wedderburn wrote:Gtk style is your issue, if you open QT4 settings and set the theme to motif it opens up fine, it just looks butt ugly haven't tried cleanlooks yet
Better not run things as root, as all the VDIs and VMs will be saved in the Root folder, not your own username. Nor will you be able to edit those files, or even read without using the Root user.
With that, are you sure that the files created are still accessible for your username? Please try to fix your normal username operation first. If it runs for Root, you need to change a few settings/permissions to be able to run it with your normal username. Is your username a member of the vboxusers group?
Then why use this theme? Pick a different one. I use Xfce as window manager, and as far as I know, it uses GTK for themes. However, if a program wants to use Qt, it's just fine with that. What does google say about this error? This isn't really something that has to do with VB. It just happens that VB uses Qt instead of GTK. Any other Qt application should give the same error.
VirtualBox is the only QT4 application running using setuid on my system so it is the only application causing problems with GtkStyle.
Of course GtkStyle is anything but necessary still I would like to keep a consistent graphic style if possible.
Last edited by flowolf on 14. Sep 2008, 18:44, edited 1 time in total.
flowolf wrote:/usr/bin/VBox is only a shell script, /usr/lib/virtualbox/VirtualBox is the actual application, and yes, it is setuid.
Not on my system. It's a symlink, linking to the VBox binary. I see very clearly the listing VirtualBox -> VBox. The color, when enabled for ls, is light blue, meaning it's symlink.
Anyway, what if you run VBox instead? You can also try to remove the setuid. It's not needed on my system, might be the same for yours.
/usr/bin/VirtualBox is a symbolic link pointing to /usr/bin/VBox and /usr/bin/VBox is a shell script that runs /usr/lib/virtualbox/VirtualBox.
Try to do cat /usr/bin/VBox...