[SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

deltaecho · 2008-09-05 03:01:08

Does anybody know why VirtualBox refuses to use the native Qt widget style? I was hoping the problem lied with Qt3, but it remains in VirtualBox 2.0 - which uses Qt4. In case I'm the only one suffering from this bug, I've included a screenshot:

Edit: I might should add, I'm using KDEMod4.

Last edited by deltaecho (2008-09-06 22:01:59)

deltaecho · 2008-09-05 22:16:03

I haven't figured it out yet, I'm just updating anybody interested on my progress...

I downloaded the .deb version of VBox 2.0, created a PKGBUILD, installed it, and, Voila! I had a beautiful GUI (check out the scrollbar)

Also, I've found another bug - whenever I install VBox via PKGBUILD, whether I use the generic bin file or the .deb archive, I cannot run VirtualBox as a normal user:

$ VirtualBox
VirtualBox: SUPR3HardenedMain: effective uid is not root (euid=1000 egid=100 uid=1000 gid=100)

However, I can run it with normal privileges when I install it directly from the bin file, kinda strange.

hash · 2008-09-06 18:33:58

I've installed virtualbox_bin 2.0 from AUR and also got the same issue with GUI - ugly QT4 style. Maybe you could share your .deb PKGBUILD ?

wonder · 2008-09-06 18:41:24

@deltaecho there is no bug. is a future
just to chmod 4511 to /opt/virtualbox/VirtualBox, VBoxSDL and VBoxHeadless within that directory.

buttons · 2008-09-06 19:51:55

All right, well the problem is the Arch version lets VirtualBox use its own version of Qt4, which it's bundled with.

rm /opt/virtualbox/libVBoxQtGui.so.4
rm /opt/virtualbox/libVBoxQtCore.so.4
ln -s /usr/lib/libQtGui.so.4 /opt/virtualbox/libVBoxQtGui.so.4
ln -s /usr/lib/libQtCore.so.4 /opt/virtualbox/libVBoxQtCore.so.4

Assuming you have the latest qt installed as of the time of this writing, this will work.

However, for those of us using QGtkStyle, as someone mentioned, this is the message we get:

Qt WARNING:
This process is currently running setuid or getgid.
GTK+ does not allow this therefore Qt cannot use the GTK+ integration.
Try launching your app using 'gksudo',
'kdesude' or a similar tool.
See http://www.gtk.org/setuid.html for more information.

I haven't tried this yet...

Last edited by buttons (2008-09-06 19:59:08)

buttons · 2008-09-06 20:27:26

Uh, yeah. To use QGtkStyle with VirtualBox, you have to run it as root instead. I basically symlinked my user's .VirtualBox directory to /root, and used sudo.

Not ideal...but it does work.

hash · 2008-09-06 20:31:35

buttons wrote:

All right, well the problem is the Arch version lets VirtualBox use its own version of Qt4, which it's bundled with.
rm /opt/virtualbox/libVBoxQtGui.so.4
rm /opt/virtualbox/libVBoxQtCore.so.4
ln -s /usr/lib/libQtGui.so.4 /opt/virtualbox/libVBoxQtGui.so.4
ln -s /usr/lib/libQtCore.so.4 /opt/virtualbox/libVBoxQtCore.so.4
Assuming you have the latest qt installed as of the time of this writing, this will work.
However, for those of us using QGtkStyle, as someone mentioned, this is the message we get:
Qt WARNING:
This process is currently running setuid or getgid.
GTK+ does not allow this therefore Qt cannot use the GTK+ integration.
Try launching your app using 'gksudo',
'kdesude' or a similar tool.
See http://www.gtk.org/setuid.html for more information.
I haven't tried this yet...

That did the trick! Thanks

fede · 2008-09-06 21:30:52

Thanks a lot!

fede · 2008-09-06 21:47:23

Does running Virtualbox with gksudo mean that the guest OS has root permissions? I guess not, because I checked, modified the contents of the drive within the guest OS, and the ownership of the drive file (.vdi) didn't change. But this is a crude test, maybe someone has better info on this?

deltaecho · 2008-09-06 22:00:40

Awesome then! I'm marking this one as [SOLVED], but the discussion may continue

Last edited by deltaecho (2008-09-06 22:02:27)

buttons · 2008-09-06 22:12:34

fede wrote:

Does running Virtualbox with gksudo mean that the guest OS has root permissions? I guess not, because I checked, modified the contents of the drive within the guest OS, and the ownership of the drive file (.vdi) didn't change. But this is a crude test, maybe someone has better info on this?

Since VBox runs with setuid already set, it always runs with root permissions. If you use gksudo, then it will be run as root, which is different.

See Wikipedia for details...

When a binary executable file has been given the setuid attribute, normal users on the system can execute this file and gain the privileges of the user who owns the file (commonly root) within the created process.

As for file modification, ownership never changes if the contents of the file are modified. You can verify this by, say, running vim as root and modifying a file in your user's directory. Ownership will not change.

Last edited by buttons (2008-09-06 22:30:58)

speed145a · 2008-09-08 01:33:55

buttons wrote:

All right, well the problem is the Arch version lets VirtualBox use its own version of Qt4, which it's bundled with.
rm /opt/virtualbox/libVBoxQtGui.so.4
rm /opt/virtualbox/libVBoxQtCore.so.4
ln -s /usr/lib/libQtGui.so.4 /opt/virtualbox/libVBoxQtGui.so.4
ln -s /usr/lib/libQtCore.so.4 /opt/virtualbox/libVBoxQtCore.so.4
Assuming you have the latest qt installed as of the time of this writing, this will work.
However, for those of us using QGtkStyle, as someone mentioned, this is the message we get:
Qt WARNING:
This process is currently running setuid or getgid.
GTK+ does not allow this therefore Qt cannot use the GTK+ integration.
Try launching your app using 'gksudo',
'kdesude' or a similar tool.
See http://www.gtk.org/setuid.html for more information.
I haven't tried this yet...

Thanks for the help getting this working!

I just wanted to point out to those who encounter the same thing I did... I am using Kde 4.1.1 and I used the .run file from the VirtualBox website to upgrade from my existing 1.6.6.

I had to follow the directions above but replace the folder "virtualbox" with "VirtualBox-2.0.0" so it looks like this:

rm /opt/VirtualBox-2.0.0/libVBoxQtGui.so.4
rm /opt/VirtualBox-2.0.0/libVBoxQtCore.so.4
ln -s /usr/lib/libQtGui.so.4 /opt/VirtualBox-2.0.0/libVBoxQtCore.so.4
ln -s /usr/lib/libQtGui.so.4 /opt/VirtualBox-2.0.0/libVBoxQtGui.so.4

THEN it worked like a charm!

fede · 2008-09-13 12:03:48

Thanks for the answers, buttons.

My doubt stemmed from your post above:

Uh, yeah. To use QGtkStyle with VirtualBox, you have to run it as root instead. I basically symlinked my user's .VirtualBox directory to /root, and used sudo.
Not ideal...but it does work.

So you're running it as root, aren't you? I ask because I also use qgtkstyle, and I find the idea of giving Virtualbox more privileges than needed uncomfortable since I sometimes use Windows XP witthin it. I'd rather have a relatively ugly interface for this one program.

buttons · 2008-09-13 17:02:52

fede wrote:

Thanks for the answers, buttons.
My doubt stemmed from your post above:
Uh, yeah. To use QGtkStyle with VirtualBox, you have to run it as root instead. I basically symlinked my user's .VirtualBox directory to /root, and used sudo.
Not ideal...but it does work.
So you're running it as root, aren't you? I ask because I also use qgtkstyle, and I find the idea of giving Virtualbox more privileges than needed uncomfortable since I sometimes use Windows XP witthin it. I'd rather have a relatively ugly interface for this one program.

Well, you needn't worry because it already has root privileges. Which is different from running it as root only in the user involved.

And yes, I'm running it as root now, just for the de-ugly.

I very much doubt running WinXP (or any OS) in any hypervisor is going to put your system at risk, regardless.

Last edited by buttons (2008-09-13 17:03:55)

jdhore · 2008-09-13 17:18:02

Just for the record, VBox 2.0.2 now supports QGtkStyle without mucking with running as root and chmodding and stuff (see the bug # in the official VBox changelog)

deltaecho · 2008-09-13 17:26:01

@jdhore, thanks for the update! I didn't know Sun had released an update, I'm going to install it now

+1

fede · 2008-09-13 17:46:28

Thanks jdhore!

deltaecho · 2008-09-13 18:41:00

While we're on the subject of making Qt apps that include their own Qt libraries use our native widget style, does anybody know how to coerce Google Earth into submission? I tried replacing its Qt libs with symlinks to my native libraries, as I did with VB, but it still stubbornly draws square widgets.

Edit: Removed "Qt" from "...our native Qt widget style..." in my question above.

Last edited by deltaecho (2008-09-13 18:43:18)

buttons · 2008-09-13 21:12:46

jdhore wrote:

Just for the record, VBox 2.0.2 now supports QGtkStyle without mucking with running as root and chmodding and stuff (see the bug # in the official VBox changelog)

Not only that, but the Arch PKGBUILD in AUR automagically uses native Qt rather than VirtualBox's. So this thread is officially moot

arch0r · 2008-09-13 22:03:18

arrgh, why isn't there any gtk frontend avaible!? qt is kinda lame -.-

jdhore · 2008-09-13 22:29:32

arch0r wrote:

arrgh, why isn't there any gtk frontend avaible!? qt is kinda lame -.-

http://www.xente.mundo-r.com/narf/vboxgtk/ <-- I love giving people what they want

Arch Linux

#1 2008-09-05 03:01:08

[SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#2 2008-09-05 22:16:03

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#3 2008-09-06 18:33:58

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#4 2008-09-06 18:41:24

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#5 2008-09-06 19:51:55

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#6 2008-09-06 20:27:26

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#7 2008-09-06 20:31:35

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#8 2008-09-06 21:30:52

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#9 2008-09-06 21:47:23

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#10 2008-09-06 22:00:40

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#11 2008-09-06 22:12:34

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#12 2008-09-08 01:33:55

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#13 2008-09-13 12:03:48

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#14 2008-09-13 17:02:52

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#15 2008-09-13 17:18:02

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#16 2008-09-13 17:26:01

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#17 2008-09-13 17:46:28

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#18 2008-09-13 18:41:00

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#19 2008-09-13 21:12:46

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#20 2008-09-13 22:03:18

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

#21 2008-09-13 22:29:32

Re: [SOLVED] VirtualBox 2.0 is still ugly, even with Qt4...

Board footer