In these days of Zoom I found that I needed to make a meeting call but the other party (a business) had a corporate account with MS and invited me to use MS Teams.
During this process I have installed and allowed a bunch of software from MS. After all this and having tried both Firefox browser, which gave me no voice or video and the MS app on Linux, which failed to work, I now get pop up signature requests every time I open my laptop and then gives me automatic update errors.
If I needed re-affirmation of why I tend to avoid MS, this was it.
Please could somebody tell me how to clean out this rubbish. As I recall I opened the first MS download using Yast. Will there be a history there which could help?
You should also execute the following to check that, all the housekeeping has been done …
“rpm --rebuilddb”
“zypper verify”
“rpm --verify --all”
“rpmconfigcheck”
You also need to check for orphaned packages.
To be absolutely certain, you need to check for anything the Redmond folks happened to have placed in systemd and /etc/ …
The final check, is for files in /usr/, /lib/, /lib64/, /bin/, /sbin/ and /var/ which aren’t owned by any installed package …
And, anything in /tmp/ and /root/ which may have been leftover from the Redmond experience …
You are welcome. One advice though.
Next time that you go “adventureous” take a pencil and paper to make notes what you did. Then it is much more easy to go in reverse mode.
Apart from the files mentioned in the RPM (that will be removed on de-insstallation), I found files in $HOME/.config/Microsoft and ~HOME/.config/teams. This is thus for the user that used it.
I do not think it will leave more traces then any other de-installed RPM.
But, using KDE, I found that once started, it added itself to the applications to be started at log-in. I unchecked that, but a start of teams (weeks later) checked it again. The item (checkbox) was gone with the de-installation of the RPM.
Hi and many thanks for the further suggestions. I think I have cleaned out all the MS stuff but running rpm --verify --all brought up quite a few issues I am not sure I can fix. Will read a bit and come back when I have tried to understand exactly what has been shown up.
From rpmconfigcheck I have;-
alastair@localhost:~> sudo rpmconfigcheck
[sudo] password for root:
Searching for unresolved configuration files
Please check the following files (see /var/adm/rpmconfigcheck):
/etc/chrony.conf.rpmnew
/etc/fonts/conf.d/30-metric-aliases.conf.rpmsave
/etc/localtime.rpmnew
alastair@localhost:~>
Why did you forget about CODE tags? I assume it takes the same, or even less, effort to use CODE tags then it takes to use a fixed font. Again, make notes, in this case on how to work on the openSUSE forums to make helping easier for those who spend their spare time.
When an update for a package is installed, sometimes the configuration file(s) belonging to the product in the package are also updated (e.g. to accommodate new configuration parameters). This will overwrite the existing configuration. The system manager (you) may have changed those file(s) and those changes would then be lost. When the installation finds out that the original files were changed it might avoid the overwriting. This then potentially may give you two situations:
The new file overwrites the old file, but the old file is saved as <the-config-file-name>.rpmold
the old file is not overwritten, but the new file is installed as <the config-file-name>.rpmnew
In both cases, you should compare them and merge your changes into the active configuration file. After that you can remove the .rpmold/.rpmnew file.
BTW, this has nothing to do with your teams question at all and is very off-topic.
Hi Henk,
I did not forget the CODE flags; after posting I went back to my post to edit it and add the output which intended to add. For reasons I have not yet fathomed the edit did not offer the CODE flag in the header.
I appreciate my questions have taken you off topic but do appreciate your advice, for which many thanks. Continuing with my OT I saw many other possible problems in my checking so I have quite a bit of cleaning up to do. Will start a new thread when I have read a few more man pages.
Thanks again,
Budge
Sorry to be a bit pedantic about this, but after first not using CODE tags end posting the post, you can not repair it into CODE tags anymore (only by removing the wrong part and inserting again the copy from the terminal between CODE tags). What is lost during the posting (being not protected by the CODE tags) is lost.
And when you edit an already posted post, you do not have all features available, but you can get them by clicking the Advanced button below.
As your first post did not describe what you did, in fact giving a good advice was not really an option. Thus I painted what I did to get teams and then the logical steps backward to undo that. In the hope that somewhere it would fit your situation a bit. To put it in short: we can not mind read what you did and when you yourself can not remember or read back your notes, even mind reading would not have helped.
OTOH I doubt that all the zypper and RPM checks advised by @dcurtisfra are really needed. I doubt very much that MS will have put real sabotage in it’s RPMs to break the system. And I do not think that most people will run all those checks after they de-installed some package (I don’t).
Cleaning up in ~/.config of the teams and most probably (when you have not other MS products the Microsoft directory might bring you some reassurance, although they contain only configurations and do nothing.
But it brought you the not unimportant fact of the existence of .rpmnew and .rpmold files and their usage,