Wine update destroyed my VirtualBox installation!

English Applications
1

I used to have Wine 1.7.2, and I updates to 1.7.10 via Software Manager (browsed Wine’s repo and applied switch). I noticed indeed that many new packages were to be installed. During Software Manager’s installation process (the package download and installation constant logs), I noticed one of the rpm packages threw an additional output, saying something regarding VirtualBox root and I don’t know.

But the thing is, I tried to open VirtualBox and nothing happened. Then tried opening from console and got “Could not find VirtualBox installation. Please reinstall.” I don’t know how the heck I can check recent Software Manager installation logs, or where they’re stored, but I guess that’d help…

Can you help me? I really need VirtualBox for work!!!
I installed VirtualBox by downloading and installing the rpm from Oracle’s site.

2

Try remove the Virtual Box installation from Oracle and use the distro version available from the default -oss repo.

I don’t know how the heck I can check recent Software Manager installation logs, or where they’re stored, but I guess that’d help…

Try this command (there is also a zypper equivalent):

rpm -qa -last | less
3

I think I found the file I wanted, /var/log/zypp/history.
And this is the part I was trying to mention:

# 2014-01-09 18:35:43 samba-krb-printing-3.6.12-59.13.1.x86_64.rpm installed ok
# Additional rpm output:
# setting /usr/lib/virtualbox/VirtualBox to root:vboxusers 4750. (wrong owner/group root:root permissions 4511)
# setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong owner/group root:root permissions 4511)
# setting /usr/lib/virtualbox/VBoxSDL to root:vboxusers 4750. (wrong owner/group root:root permissions 4511)
# setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong owner/group root:root permissions 4511)
# setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong owner/group root:root permissions 4511)
# network smb "Unknown" "Windows Printer via SAMBA"
# 
2014-01-09 18:35:43|install|samba-krb-printing|3.6.12-59.13.1|x86_64||repo-update|70aeb272d6305a20c5ef8b07a9f225ba3f411b253540af3886587121c6d68b0b|

This must be the part that f****d my VirtualBox installation.
But why is this happening? Why does Samba have to do with Wine or VirtualBox!? I was just updating freaking Wine!
And even if it got fixed, then it means Wine will always break any existing VirtualBox installation!!

4

On 2014-01-10 02:36, F style wrote:

> This must be the part that f****d my VirtualBox installation.
> But why is this happening? Why does Samba have to do with Wine or
> VirtualBox!? I was just updating freaking Wine!
> And even if it got fixed, then it means Wine will always break any
> existing VirtualBox installation!!

I’d guess it is not Wine, but a postinstall script that calls this:


chkstat --system --set

This was previously run by the old script SuSEconfig, which was run
after every install. What it does is apply the permissions defined in
the “/etc/permissions” files - so if they are wrong for you, you have to
edit “permissions.local”.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

5

Do you use the suse packaged version of VirtualBox, -oss repo?
I both run VirtualBox and Wine on the same system also, on openSUSE 13.1, I have not encountered any such issue so far.

6

No intention to offend nor the like, but why do you ask what you already know?

7

No problem mate.
I may have missed it but the only reference I could see in regard the origin of VirtualBox, if that was what you meant, is to an RPM downloaded from the VirtualBox site. And as the suse packaged version of VB is split into several packages, I made the presumption that another build could be structured differently thus, potentially at least, causing trouble.

What is the present status of your VB/WINE system?