Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Upgrade TB 68.12 with enigmail to TB 78.3.1 failed (Tumbleweed)

  • 2 antwurd
  • 1 hat dit probleem
  • 22 werjeftes
  • Lêste antwurd fan roku54

more options

After the installation of new TB 78.3.1 packages in Tumbleweed the start of the new TB version has stalled without any additional info, no migration of pgp keys was performed.

However, TB perfectly starts in safe-mode with the enigmail extension disabled. Further add-ons / extensions have been deleted to isolate the problem. Obviously, the migration of enigmail data still seems to be pending. In safe-mode I have already used the OpenPGP Key Manager to reinstall my missing keys. Encryption again works successfully.

How can I get rid of the incomplete enigmail migration which seems to block the TB start in normal mode?

After the installation of new TB 78.3.1 packages in Tumbleweed the start of the new TB version has stalled without any additional info, no migration of pgp keys was performed. However, TB perfectly starts in safe-mode with the enigmail extension disabled. Further add-ons / extensions have been deleted to isolate the problem. Obviously, the migration of enigmail data still seems to be pending. In safe-mode I have already used the OpenPGP Key Manager to reinstall my missing keys. Encryption again works successfully. How can I get rid of the incomplete enigmail migration which seems to block the TB start in normal mode?

Bewurke troch Wayne Mery op

Keazen oplossing

Upgrade problem solved by TB 78.4.0.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

more options

In the meantime, I copied my complete profile to an openSUSE Leap 15.2 system with kernel 5.3.18. In this new setup TB 78.3 works fine, even in normal mode.

Therefore, the blocking situation described above has not been caused by any migration problems. It seems to be an incompatibility of the Tumbleweed system (based on kernel 5.8.12) and TB 78.3.

more options

Keazen oplossing

Upgrade problem solved by TB 78.4.0.