On 14/07/2021 22:13, Phil Perry wrote:
On 14/07/2021 07:28, Toralf Lund wrote:
On 13/07/2021 14:23, Phil Perry wrote:
On 13/07/2021 13:02, Toralf Lund wrote:
Does anyone else run Microsoft Teams on CentOS 7?
I've used it for a while now, and it's generally worked reasonably
well. However, after upgrading to the latest version from the
Microsoft repos, it doesn't start up properly. Processes start and
remain active until I give up and kill them, but I can't see a
window or a tray icon or anything.
Has anyone else seen this? Is there anything I can do to make the
GUI appear?
This is not a big deal as everything just works fine if I revert to
the previous release, but it would be interesting to know if this
is a general problem with the software, or I have some weird issue
with my system.
The release that doesn't work is 1.4.00.13653. The one that does is
1.4.00.7556.
- Toralf
My wife has been using it on el7, but for the last month or two yum
has been complaining about broken dependencies when trying to update
it, so I'd disabled the Teams repo from yum updating.
OK. Do you know what dependencies that might be? Just out of interest...
I've never had any issues like that. Like I said, the latest (?)
version installs just fine on my system, it's just that it doesn't do
anything useful.
I can check what version I'm running later for you, if that would be
helpful.
Well, it would be kind of interesting...
- T
My currently installed/working version is:
# rpm -qa | grep teams
teams-1.4.00.7556-1.x86_64
OK. Thanks.
That's the one that works here, obviously.
and when I attempt a yum update, I get:
Resolving Dependencies
--> Running transaction check
---> Package teams.x86_64 0:1.4.00.7556-1 will be updated
---> Package teams.x86_64 0:1.4.00.13653-1 will be an update
--> Processing Dependency: libstdc++.so.6(CXXABI_1.3.8)(64bit) for
package: teams-1.4.00.13653-1.x86_64
--> Processing Dependency: libstdc++.so.6(CXXABI_1.3.9)(64bit) for
package: teams-1.4.00.13653-1.x86_64
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.20)(64bit) for
package: teams-1.4.00.13653-1.x86_64
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.21)(64bit) for
package: teams-1.4.00.13653-1.x86_64
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.22)(64bit) for
package: teams-1.4.00.13653-1.x86_64
--> Finished Dependency Resolution
Error: Package: teams-1.4.00.13653-1.x86_64 (teams)
Requires: libstdc++.so.6(GLIBCXX_3.4.20)(64bit)
Which I don't see.
But I found out what's going on;
[toralf@localhost ~]$ rpm -q --whatprovides
'libstdc++.so.6(GLIBCXX_3.4.22)(64bit)'
chrome-deps-stable-3.13-1.x86_64
[toralf@localhost ~]$ rpm -ql chrome-deps-stable
/opt/google/chrome/lib/libgnome-keyring.so.0
/opt/google/chrome/lib/libstdc++.so.6
/opt/google/chrome/lib/link-to-libgnome-keyring.so.0
/opt/google/chrome/modify_wrapper
The problem is, even though this package "provides" the lib, it's not
available for general use, in that /opt/google/chrome/lib isn't added to
the library path.
I believe this package was supposed to help you get around some kind of
dependency issue with chrome packages from Google a long time ago.
Offered as a quick-fix by someone associated with the Fedora project,
but probably not included in any of the "usual" repos. I'd quite
forgotten that I had this.
Didn't think to check this sooner; I guess I assumed that everything
would be OK with the dependencies, since the processes did not fail with
the runtime linker error you might expect. But I suppose the components
are loaded in a somewhat more roundabout way, i.e. the teams executable
is not actually linked to the new libstdc++ or anything that uses it.
- Toralf
Error: Package: teams-1.4.00.13653-1.x86_64 (teams)
Requires: libstdc++.so.6(CXXABI_1.3.9)(64bit)
Error: Package: teams-1.4.00.13653-1.x86_64 (teams)
Requires: libstdc++.so.6(GLIBCXX_3.4.21)(64bit)
Error: Package: teams-1.4.00.13653-1.x86_64 (teams)
Requires: libstdc++.so.6(CXXABI_1.3.8)(64bit)
Error: Package: teams-1.4.00.13653-1.x86_64 (teams)
Requires: libstdc++.so.6(GLIBCXX_3.4.22)(64bit)
So Teams now needs a newer version of libstdc++ than that in RHEL7. As
others have mentioned, Microsoft clearly do not understand how to
package software using RPM and you are probably better off with a
snap/flatpak solution.
--Phil
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.centos.org%2Fmailman%2Flistinfo%2Fcentos&data=04%7C01%7Ctoralf.lund%40pgs.com%7C5fe5b49725f14958ad5c08d94703de19%7C51d05d6147e9480b93b298dc84f1ed06%7C0%7C0%7C637618904213717799%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mpQ6mN%2FZ4cThc7ikBOG5J62plzh2kWVwPDPpOZm5i24%3D&reserved=0
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
