![]() ![]() ![]() If an application complains about a lack of administrator privileges, file a bug running Wine as root probably won't help. You should always run Wine as the normal user you use to login.įor Linux systems, all ideas that Wine needs root can be solved through Posix Capabilities Opens a new window or Posix File Capabilities Opens a new window or correcting other security settings.Īs far as Windows programs are concerned, you are running with administrator privileges. If you have run Wine with sudo you need to fix the permission errors as described in the next question, and then run winecfg to set Wine up again. Running with sudo also has these same risks but with the added bonus of breaking the permissions on your ~/.winefolder in the process. ![]() NEVER run Wine as root! Doing so gives Windows programs (and viruses) full access to your computer and every piece of media attached to it. In fact, Wine expressly states that he should not do what he did from their Wiki, link below: wine folder to root the next time he runs any Wine program he'd have to do so as root and not as his user account - a huge no-no. Maybe you need to look at something like cacti?Yeah, I decided to avoid addressing this, but you're exactly right - since he changed the owner of his. Maybe a better way of looking at this is what is another way of achieving the same result? The crash is probably from the change in permissions. You do realise it's probably not launching because you're still trying to launch the app as the local user? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |