But I don't want to run it as root.
When running as user I get the error message.
Whether I use yast, yum or su and then exiting su before starting the it's the same. And now I get told that I am running as root
I guess I will have to wait for Suse 11. I do not want to change settings to please a software because I can never be sure that it won't mess with the rest (do I have to change the temp's ownership every time I am using another user?).
I am running here in circles. You can lock the thread, it's not going anywhere.
Edit: And I know that the running as admin under Windows is the worst thing to do. Before you start telling me about risk of it you have to understand that some software ARE ONLY installing under administrator and if you want to run them as user it's simply not working. It's well known and because of my clients also request Trados I have to follow the trend. There is no way out of it and it's nice to have Wine running it as admin within the prefix.
Alexandre says "let the newbies run as root
Alexandre says "let the newbies run as root
On Mon, Mar 24, 2008 at 11:00 AM, Timeout <[email protected]> wrote:
clear, does:
$ mv ~/.wine ~/.wine.bak
$ wineprefixcreate
$ wine setup.exe
$ wine your_program.exe
Fix the problem (please try this in wine 0.9.58, unpatched, unless
there is a different/bug regression you are working around)?
A lot of confusion has been introduced by root vs user flamewar. To beBut I don't want to run it as root.
When running as user I get the error message.
Whether I use yast, yum or su and then exiting su before starting the it's the same. And now I get told that I am running as root [Rolling Eyes]
I guess I will have to wait for Suse 11. I do not want to change settings to please a software because I can never be sure that it won't mess with the rest (do I have to change the temp's ownership every time I am using another user?).
I am running here in circles. You can lock the thread, it's not going anywhere.
clear, does:
$ mv ~/.wine ~/.wine.bak
$ wineprefixcreate
$ wine setup.exe
$ wine your_program.exe
Fix the problem (please try this in wine 0.9.58, unpatched, unless
there is a different/bug regression you are working around)?
Alexandre says "let the newbies run as root
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 24 March 2008 09:00:21 am Timeout wrote:
changed on that, it could cause part of your problem.
the RPM world, that will probably require a reinstall anyway). Proactively
trying to solve the problem will fix the problem.
http://catb.org/~esr/faqs/smart-questions.html
- --
Paul Johnson
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH5987UCxPKZafKh0RAh40AJ4gPbq2Qu9LY8GSHgd1KaLu0nWaugCgm9pH
PxcMoLEPQadBp/Wx+pwWH4k=
=2RN0
-----END PGP SIGNATURE-----
Hash: SHA1
On Monday 24 March 2008 09:00:21 am Timeout wrote:
What's the ownership on your ~/.wine? If the ownership or permissions gotBut I don't want to run it as root.
When running as user I get the error message.
Whether I use yast, yum or su and then exiting su before starting the it's
the same. And now I get told that I am running as root [Rolling Eyes]
changed on that, it could cause part of your problem.
Waiting for some version number to roll over will not fix your problem (and inI guess I will have to wait for Suse 11. I do not want to change settings
to please a software because I can never be sure that it won't mess with
the rest (do I have to change the temp's ownership every time I am using
another user?).
the RPM world, that will probably require a reinstall anyway). Proactively
trying to solve the problem will fix the problem.
Start over, read this, and try again.I am running here in circles. You can lock the thread, it's not going
anywhere.
http://catb.org/~esr/faqs/smart-questions.html
- --
Paul Johnson
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH5987UCxPKZafKh0RAh40AJ4gPbq2Qu9LY8GSHgd1KaLu0nWaugCgm9pH
PxcMoLEPQadBp/Wx+pwWH4k=
=2RN0
-----END PGP SIGNATURE-----
Alexandre says "let the newbies run as root
On Mon, Mar 24, 2008 at 10:04 AM, Paul Johnson <[email protected]> wrote:
Timeout has been actively trying, really hard, to solve the problem
for some time now. I think perhaps giving it a rest is in fact
the right course of action; the apps in question are full of
problems in wine right now.
- Dan
Paul,Waiting for some version number to roll over will not fix your problem (and in
the RPM world, that will probably require a reinstall anyway). Proactively
trying to solve the problem will fix the problem.
Timeout has been actively trying, really hard, to solve the problem
for some time now. I think perhaps giving it a rest is in fact
the right course of action; the apps in question are full of
problems in wine right now.
- Dan