On Wed, 2005-12-14 at 16:39 -0500, John Kebbel wrote:
> How would I completely erase wine (from /root/.wine and /kebbelj/.wine)
> and reinstall it on my Fedora 4 system. Here's the Catch-22 I've gotten
> myself into.
>
rm -rf /root/.wine and the same for the kebbelj home directory.
> I figured I'd de-install wine and start over. Here's a copy and paste
> from the terminal ...
>
> bash-3.00$ sudo rpm -e wine-0.9.2-1fc4winehq.i686.rpm
> Password:
> error: package wine-0.9.2-1fc4winehq.i686.rpm is not installed
>
You have to erase the package, not the rpm.
rpm -e wine-0.9.2-1fc4winehq
> Well, then. If it's not installed, I should be able to reinstall it. No
> luck. I got this error message...
>
> bash-3.00$ su
> Password:
> [root@localhost tars]# rpm -i wine-0.9.2-1fc4winehq.i686.rpm
> package wine-0.9.2-1fc4winehq is already installed
>
> Well, if it's installed, I figure, I should be able to run it. Here's
> what I got...
>
> bash-3.00$ winefile
> wine: '/tmp/.wine-500/server-302-1b82be/socket' is not owned by you
> bash-3.00$
>
That means root started wine. It may take a reboot to fix that, but I
think a judicious use of 'ps -ef' will allow you to identify and kill
the wine server.. The wine server must be stopped then restarted as
your regular user.
> Well, if I can't run it because I don't own it, root should be able to
> run it. I got ...
>
> [root@localhost tars]# sudo winefile
> wine: creating configuration directory '/root/.wine'...
> wine: '/root/.wine' created successfully.
>
> This recreated the root version I threw away yesterday.
>
After you do all the above, then do NOT start wine as root.
Start it as your own user only and it should work. (Works for me!)
>
