C7, Removing Zoom Problem

Home » CentOS » C7, Removing Zoom Problem
CentOS 11 Comments

Guys, I’m trying to update my zoom client and yum (or yumex) won’t let me do an update, so I try to remove the installed one, on the theory that if it isn’t there I should be able to install a newer one, by doing “sudo yum remove zoom_x86_64” (where my PWD is the directory where the zoom RPM files live) and it tells me “no packages marked for removal.

Reading thru the man page for rpm I can’t figure out any other way to do it. Suggestions, any one?

Thanks in advance!

Fred

11 thoughts on - C7, Removing Zoom Problem

  • Hi

    This should tell you the real name of the package

    rpm -qa zoom\*

    Then rpm -e zoom… should remove it.

    That said, I’ve never used zoom so I don’t really know if they do something special.

    Regards, Simon

  • Looking at https://support.zoom.us/hc/en-us/articles/204206269-Installing-or-updating-Zoom-on-Linux#h_c3eadf5f-1311-4d38-972e-dd8868353ccb

    You should use:   sudo yum remove zoom

    Commercial companies are notorious for renaming their RPM’s to different filenames than what the package variables set.  The filename has no bearing on the package name when installed.  In this case, the download is called “zoom_x86_64.rpm” but it’s real rpm filename with the typical name-version-release.arch may be queried from the download file itself:

    rpm -q –qf=’%{name}-%{version}-%{release}.%{arch}\n’ -p ./zoom_x86_64.rpm zoom-5.13.5.431-1.x86_64

    As you can see, the real package name is “zoom”.

    “sudo rpm -ev zoom” would also be a fine option.

  • That’s because CentOS/RHEL 7 is no longer supported. Zoom download page shows 5.13.4.711 as the latest for 7. (5.13.7.683 is the latest for 8+.)

    You can download and install 5.13.7.683 but it won’t start:

    zoom: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20′ not found
    (required by zoom)
    zoom: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21′ not found
    (required by zoom)

  • well, as one of the earlier posters showed how, I did remove the existing one then installed the new one (the one that Zoom offers for CentOS-7, not the one for CentOS-8, which has the problem you describe) and voila, works like a charm!

    Fred

  • Yes but that’s the old version – 5.13.4.711 not the latest 5.13.7.683.
    “Check for Updates” will tell you there’s a new version but you’ll be stuck with that old version until you upgrade from CentOS 7 to something newer.

  • ah, that’s OK for now, as long as it works.

    I’m trying to build up the courage to do a full system upgrade to Rocky.latest. I hate doing upgrades, it’s such a pain in the rear to get everything working again, and get all my tweaks back into place. I despise Gnome 3+, and prefer Mate. Someone (EPEL ??) built Mate for C7, but the existing binaries for C8 don’t work very well, there are none that I know of for C9, and AFAIK Rocky is the only CentOS clone that supports Mate. there IS Ubuntu Mate, but I am more comfy with RH-derived systems.

  • I’ve made to move to Rocky 8 after it was released and there is support for MATE and if you prefer lightdm as a window manager.  It has some minor quirks, but all in all it works just fine. I’ve not tried it yet but there is also a Rocky 9 MATE live image available https://docs.rockylinux.org/en/guides/desktop/mate_installation/

    Pete

    —
    Unencumbered by the thought process.
    — Click and Clack the Tappet brothers

  • Getting all your configuration into ansible, puppet or the like is a bit of work but a real benefit when it’s time to upgrade.

    I’m using Mate on Rocky 9 at work and on CentOS 8 stream on my laptop. Works fine for what I need.

  • It’s possible but can be a lot of work if you’re not familiar with the software.

    A simpler option is to save all your configured files in a version control system (git, subverion, mercury for example). That keeps a history of all the customizations you made and also makes it easy to revert a change that causes problems. There are open source tools to help (etckeeper is one but there are others).

  • Yes, that would be 1/2 of the challenge. The other 1/2 is the installation of all the software, some of which is done through yum (or dnf) of course. The more challenging part is the installation of various bits and pieces the main apps have been extended by etc.

    I agree, not easy to automate.