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 [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.
On Mon, Mar 24, 2008 at 11:00 AM, Timeout <wineforum-user at winehq.org> wrote:> 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 [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. >A lot of confusion has been introduced by root vs user flamewar. To be 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)?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 24 March 2008 09:00:21 am Timeout wrote:> 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 [Rolling Eyes]What's the ownership on your ~/.wine? If the ownership or permissions got changed on that, it could cause part of your problem.> 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?).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.> I am running here in circles. You can lock the thread, it's not going > anywhere.Start over, read this, and try again. http://catb.org/~esr/faqs/smart-questions.html - -- Paul Johnson baloo at ursine.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH5987UCxPKZafKh0RAh40AJ4gPbq2Qu9LY8GSHgd1KaLu0nWaugCgm9pH PxcMoLEPQadBp/Wx+pwWH4k=2RN0 -----END PGP SIGNATURE-----
On Mon, Mar 24, 2008 at 10:04 AM, Paul Johnson <baloo at ursine.ca> wrote:> 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.Paul, 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