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!

  • Björn Tantau@swg-empire.de
    2·
    4 months ago

    I think the correct way would be to boot from a previous snapshot and roll back to that. No idea what could go wrong when you’re staying in a snapshot. I’d mostly be afraid that I’d forget that I’m on a snapshot and find myself with the error again on next boot.

    • intelisense@lemm.ee
      1·
      4 months ago

      Snapshots are read only. Best plan is to rollback to a snapshot you think works, test it and if all is good use sudo snapper rollback to make the current snapshot the default. I usually reboot at that point too, not sure if it’s necessary though.