Opened 15 years ago
Closed 15 years ago
#6435 closed defect (fixed)
Installing SUNWvboxguest on OpenSolaris b134 causes gnome-appearance-properties to fail => fixed in SVN
Reported by: | Rand S. Huntzinger | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 3.1.6 |
Keywords: | Cc: | ||
Guest type: | Solaris | Host type: | Solaris |
Description (last modified by )
After installing SUNWvboxguest version 3.1.6 on an OpenSolaris build 134 guest the gnome-appearance-properties execitable fails as follows:
indy$ gnome-appearance-properties ld.so.1: gnome-appearance-properties: fatal: libXfixes.so.3: open failed: No such file or directory ld.so.1: gnome-appearance-properties: fatal: relocation error: file /usr/bin/gnome-appearance-properties: symbol glXQueryServerString: referenced symbol not found Killed indy$
I was able to get this to run by adding two symbolic links to the system; however, I don't consider this a proper fix. The links were:
indy# cd /usr/lib indy# ln -s libXfixes.so.1 libXfixes.so.3 indy# ln -s libXext.so.0 libXext.so.6
Apparently the libraries SUNWvboxguest puts onto the system requires libXfixes.so.3 and libXext.so.6 but these libraries aren't on the system. I faked it by linking in older versions of these libraries and got the application to run; however, the libraries have updated versions for a reason and it isn't clear what the side effects of linking in an older version might be. For this reason, the links aren't a proper fix.
I don't see how the VBox.log for this session would apply so I didn't attach one.
-- Rand Huntzinger
Change History (3)
comment:1 by , 15 years ago
Description: | modified (diff) |
---|
comment:2 by , 15 years ago
Summary: | Installing SUNWvboxguest on OpenSolaris b134 causes gnome-appearance-properties to fail → Installing SUNWvboxguest on OpenSolaris b134 causes gnome-appearance-properties to fail => fixed in SVN |
---|
comment:3 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thank you for the report, fixed this internally and the fix will be available in the next release.