Thanks to everyone for the replies. The solution for me at this point
is going to be reverting back to 1.04. The possible solutions offered
are either not working or not worth it, and I have no idea how to build
a package (interesting idea though - must do some reading on that...)
There are zero good known reasons for me going to 1.05. Aside from
"because I can" and essentially do actually know how to, it's just that
it failed to execute as it ought to and has worked for others.
This is a far cry from where I was with linux not that long ago - many
of the things I am doing are because I have moved far enough up the
learning curve that most of the time I can be really productive and
implement cool stuff and have loads of fun all at the same time. And
not need to google everything or ask basic questions on this list. The
other week I went from 2.3 to 2.4 with OpenOffice just "because I can"
and "because it's there" without knowing what the benefits might be, in
the end all I can say is that the toolbar buttons look a little cooler,
and that's enough for me.
I'm not brave enough for betas in linux at this point but am eagerly
awaiting Hardy Heron (must be any day!), VMWare Server 2, OpenOffice 3,
KDE4.1 etc. Might even have a go with a Gnome desktop (new ground for
me). It's all good learning and experience for me, and I do appreciate
all the feedback and support from this list (and the other lugs I lurk
on now too).
Cheers,
Roger
Nick Rout wrote:
Why don't you uninstall 1.05 then build a 1.05 package for your packaging
system (based on the build for 1.040 and then install it.
Alternatively, what is the "must have" feature in 1.05 that makes it
necessary to have 1.05 as opposed to 1.04?
On Fri, April 4, 2008 10:22 am, Roger Searle wrote:
Hi Ben, nice to hear from you! OK having (I believe) set the sticky bit:
[EMAIL PROTECTED]:~$ sudo ls -al /usr/bin | grep vmware
-r-sr-xr-t 1 root root 4570 2008-04-02 11:45 vmware
i continue to get:
[EMAIL PROTECTED]:~$ vmware
exec: 180: /usr/lib/vmware/lib/wrapper-gtk24.sh: Permission denied
In fact, this is the same error regardless of whether sticky bit is set
or not. Or perhaps I mis-understand what I am supposed to be doing. In
other words, if I have done what you suggested correctly, this hasn't
solved the issue.
Cheers,
Roger
[EMAIL PROTECTED] wrote:
Use the suid sticky bit.
On Fri, 04 Apr 2008 09:02:44 +1300, Roger Searle
<[EMAIL PROTECTED]> wrote:
Good morning. I took the bait of the minor upgrade available from
VMWare Server to go up a massive 0.01 to 1.05, downloading their tar
file and running the install script. The installation went fine and
VMs
run and behave as usual. However I am no longer able to use a KDE menu
or Autostart entry to launch the application, the only method I have
found so far is to launch manually via command line thus:
[EMAIL PROTECTED]:~$ sudo /usr/bin/vmware -l
[sudo] password for roger:
which is a pain and obviously not good practice. Without sudo I get
permission denied which seems to be contrary to my understanding of the
permissions in that I have execute rights:
[EMAIL PROTECTED]:~$ sudo ls -al /usr/bin | grep vmware
-r-xr-xr-x 1 root root 4570 2008-04-02 11:45 vmware
Yes, yes, I know, use Adept - and I'm really bad. It's only offering
1.04, sure I could remove 1.05 and go back a release but it's the
learning for me. How can I create a desktop icon command that doesn't
require the use of sudo? I know the "right click the desktop, create
new, link to application" bit, and /usr/bin/vmware as the application
command doesn't do it.
Thanks for any pointers!
Roger
