Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Why is wine removal so challenging?
Hello. I've been doing some experimenting trying to get my iPhone to communicate with my Linux Mint 20 XFCE box. At one point, I made the mistake of installing wine. I knew ahead of time that this might be a bad idea, so I created a timeshift backup prior to the wine install. When I tried to roll back, I found wine quite difficult to remove. Rolling back with timeshift removed some but not all of it, I also ran Joe's excellent 

Sudo up --clean
command, and used Stacer for some additional file cleanup. These three approaches failed to fully remove wine and its related files. Finally succeeded with a point-and-click exploration of the file system in Thunar, where I manually deleted a bunch of files and folders, based loosely on the commands in this thread.

I'm back to a nice clean system now, but I don't understand why the first three methods timeshift, clean command, and Stacer didn't do the trick.  What about wine makes it so difficult to remove, and why, particularly, did the timeshift rollback not fully do the job? I can tell I don't understand something about how the system works, but I'm not sure what I've missed. Any explanation would be greatly appreciated. Just trying to learn. Smile
Must be my sence of humor! Sorry I can't shed any light on your problem of removing wine - but have you tried to remove wine stains from a white shirt - much the same situation :>)
Especially if its "Red"
Do keep in mind WINE is an interpreter and not an emulator.  So it translates Windows calls in Linux calls.

Therefore for it to work correctly it does a lot of embedding into the Linux system.  I do find this unfortunate too. Still I have seen this with other projects.  In general until proven otherwise I consider any software I install to be "hard to remove".

This most comes down to software developers but to a degree how Linux functions.  There are some apps that really do need files in many locations due to system layout.  However many programs are just lazy and sprinkle their code all over.  This however is not unique to Linux.

Many Windows programs leave all kinds of left over settings (Registry entries among others), files, and data behind despite the famous uninstall program.

So to answer your question to get WINE to work the program must heavily embed itself.  It should always be considered a one way install.  Of course a nuke and pave will remove it.  CYA will probably do a better rollback job but... that depends on when you install WINE and if you can live with undoing all the system changes since that snapshot.

It can be frustrating because I have seen Linux programs remove the GUI!!!!  It is like: "WHAT ARE YOU DOING?!!!"  At least that is what I have said watching programs "uninstall" in Linux with the package manager.  No fun.  So without taking a snapshot and even then if you can't live with nuke and pave to fully restore a system then don't install the program or at least try it in a virtual machine or an unimportant bare metal rig.  Then see how it removes itself.
Jeremy (Mr. Server)

* Desktop: Ubuntu MATE
* Windows are for your walls, Apple is for your health, Linux is for your computer
Thanks, that does make some sense. Sorry to hear that that's also been your experience with uninstalling. It's at least nice to know that I haven't missed something simple. I guess I'll consider myself lucky that I got it all cleaned up, without doing a nuke and pave.

Forum Jump:

Users browsing this thread: 1 Guest(s)