Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Thunderbird 115.1.1 crashes when printing (on Fedora 38)

  • 10 отговора
  • 0 имат този проблем
  • 6 изгледи
  • Последен отговор от firefox.smelting423

more options

Hello, I'm using Thunderbird 115.1.1 (thunderbird-flatpack - 1.0) on Fedora 38 Workstation. Thunderbird crashes immediately when I want to print an e-mail. The dialog box that then appears indicates that no trace has been created.

The problem persists if I run Thunderbird in safe mode.

Any ideas on how to solve this problem? Thanks, Chris.

Hello, I'm using Thunderbird 115.1.1 (thunderbird-flatpack - 1.0) on Fedora 38 Workstation. Thunderbird crashes immediately when I want to print an e-mail. The dialog box that then appears indicates that no trace has been created. The problem persists if I run Thunderbird in safe mode. Any ideas on how to solve this problem? Thanks, Chris.

Избрано решение

Printing crash is now fixed in org.freedesktop.Platform 22.08.15. Ensure you have this version or do upgrade.

Прочетете този отговор в контекста 👍 0

Всички отговори (10)

more options

> The dialog box that then appears indicates that no trace has been created.

Screen shot or exact wording?

more options

Wayne Mery a écrit

> The dialog box that then appears indicates that no trace has been created. Screen shot or exact wording?

Thank you for your reply. Here is a screenshot I just took.

more options

This is known issue which will be fixed in next flatpak runtime update (org.freedesktop.Platform 22.08.15). It should be matter of few days, see https://bugzilla.mozilla.org/show_bug.cgi?id=1849397#c4 for details

The problem with broken crash reporter is also known and tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1843102

As a workaround for crash reporter you may execute app from console as "flatpak run --allow-devel org.mozilla.Thunderbird". After that you should be able to generate and send report when app crashes.

more options

qgsgiljyxzgtslsyrz a écrit

This is known issue which will be fixed in next flatpak runtime update (org.freedesktop.Platform 22.08.15). It should be matter of few days, see https://bugzilla.mozilla.org/show_bug.cgi?id=1849397#c4 for details The problem with broken crash reporter is also known and tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1843102 As a workaround for crash reporter you may execute app from console as "flatpak run --allow-devel org.mozilla.Thunderbird". After that you should be able to generate and send report when app crashes.

Thanks for your answer. Issue not solved with 115.2.0.

more options

firefox.smelting423 said

Issue not solved with 115.2.0.

That is correct. "It should be matter of few days" is not applicable to version 115 - the fix needs to go through a number of steps before it reaches version 115 - I would hope within a couple weeks.

more options

As I said the fix will be part of flatpak runtime - org.freedesktop.Platform 22.08.15 which unfortunately wasn't published yet.

The thunderbird updates doesn't matter for this issue - when runtime is updated then all possible thunderbird versions will be fixed at once but without runtime update none thunderbird update will ever fix it - the problem isn't in thunderbird but in flatpak runtime.

Above is about crash in print dialog. The crash reporter itself will be fixed in future thunderbird release.

Променено на от qgsgiljyxzgtslsyrz

more options

Quite right. Thanks for clarifying.

more options

Thank you for this clarification.

more options

Избрано решение

Printing crash is now fixed in org.freedesktop.Platform 22.08.15. Ensure you have this version or do upgrade.

more options

Yep ! It works now. Thanks !