We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 22 回表示
  • 最後の返信者: 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?

この投稿は Wayne Mery により に変更されました

選ばれた解決策

Upgrade problem solved by TB 78.4.0.

この回答をすべて読む 👍 0

すべての返信 (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

選ばれた解決策

Upgrade problem solved by TB 78.4.0.