Zoom is vital to my job this month and prior to an update last week I had the openSUSE version of Zoom’s RPM installed and working fine.
I updated my Tumbleweed installation to openSUSE-20240704-0 last week, after which Zoom started crashing when sharing a screen. There was a message in the logs about the library libqt5qml.so and I thought I could fix this by backing out either the update for the libQtQuick5 package in particular, or just booting from the pre-update snapshot.
To make a long story short, I ultimately installed the Zoom Flatpak and resolved to get back to this when I had a bit more time.
My question - Can people suggest the right way in openSUSE Tumbleweed to handle the situation where an update breaks something on the system?
Assuming libQtQuick5 was the updated package that was at fault here, is there a way I could have downgraded just that package? Would booting from the pre-update snapshot and then just carrying on with my week have been a reasonable way to proceed?
To be clear - I’m not so much concerned about Zoom, I’m more curious about how to use the openSUSE Tumbleweed tools to recover from updates that cause problems.
Thank you!
You must log in or register to comment.
Using the flatpak is the right answer. Seriously though flatpaks are separate from the base system so this isn’t an issue.
The bigger issue is that you are running tumbleweed on a production critical machine. If you want to run it on a personal machine that isn’t critical that’s fine but for production stick with well tested. Things will break and its best to stick with slow and stable. Think Linux Mint or Debian with Flatpak apps.
