Description of problem: After upgrading to Cauldron, Thunderbird is completely broken. This means that my e-mails aren't visible anymore (everything below the toolbar is empty). There is no "new message" button in the tool bar anymore. When I create a new message (file > new > message) I can write a message as usual, but when I click "send" nothing happens. There are things that seem to be working fine. When I look at my account settings all my e-mail accounts are there properly. Version-Release number of selected component (if applicable): Thunderbird 60.3.3 (64 bits) How reproducible: Steps to Reproduce: 1. open Thunderbird 2. no e-mails are shown and the things mentioned above aren't working properly
Created attachment 10558 [details] Screenshot of Thunderbird 60.3.3
Created attachment 10559 [details] Thunderbird 52.9.1 before upgrading This is how the Thunderbird windows looks like under mageia 6 before upgrading Thunderbird to version 60.3.3.
There has been an update on mageia 6 to Thunderbird 60.3.3. This broke my Thunderbird the same way as upgrading to Cauldron. The only way to see my e-mails again was to uninstall the new version ant to go back to the version 52.2.1.
Version: Cauldron => 6
Hi Béat, Sorry to read about the problem. Which display manager and which desktop environment do you use? What is the output of lspcidrake -v | grep Card and, on a system with broken Thunderbird, of: rpm -qa | grep thunderbird
Keywords: (none) => NEEDINFOWhiteboard: (none) => MGA6TOOVersion: 6 => CauldronSummary: Broken Thunderbird after update to Cauldron (no e-mails shown) => Broken Thunderbird after update to thunderbird-60.3.3 (no e-mails shown), both in Cauldron and in Mageia 6Source RPM: (none) => thunderbirdCC: (none) => doktor5000, marja11, nicolas.salguero
I use the standard display manager (I don't know exactly how it is called) and KDE is my desktop environment. The output of "lspcidrake -v | grep Card" is: Card:Intel 810 and later: Intel Corporation|UHD Graphics 620 [DISPLAY_VGA] (vendor:8086 device:5917 subv:1043 subd:1c30) (rev: 07) The output of "rpm -qa | grep thunderbird" is /etc/host.conf : ligne 3 : commande erronée« nospoof on » /etc/host.conf : ligne 4 : commande erronée« spoofalert on » thunderbird-en_US-60.3.3-1.mga7 thunderbird-60.3.3-9.mga7 thunderbird-fr-60.3.3-1.mga7 thunderbird-de-60.3.3-1.mga7
I have no idea what can cause this, here in cauldron, with a different "Intel 810 and later" Thunderbird works fine with KDE (Plasma5). Béat, before starting Thunderbird, can you open 2 terminals/konsoles 1. become root in the first one and enter this command: journalctl -f 2>&1 | tee journal.txt 2. as normal user in the second konsole, start thunderbird like this: thunderbird 2>&1 | tee thunderbird.txt As soon as you've seen the problem persists, you can close the applications. Please attach journal.txt and thunderbird.txt
CC: (none) => kde
Created attachment 10576 [details] output of "journalctl -f 2>&1 | tee journal.txt"
Created attachment 10577 [details] result of "thunderbird 2>&1 | tee thunderbird.txt"
Thanks for the feedback. Right after you start thunderbird, i see: déc 17 12:37:59 localhost.localdomain plasmashell[5300]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML QQuickText: Binding loop detected for property "width" I have no idea what that means nor whether any plasmoid has anything to do with how Thunderbird is rendered. Assigning this report to KDE team for an answer. They'll assign this report back to bugsquad if your log doesn't show a related problem on KDE side. I doubt that line is related, though :-/ Béat, could you also try the following: Test one or more other DEs and DMs, to see whether Thunderbird works fine in them. If it doesn't: create a new user (without copying your .thunderbird to it) and test whether Thunderbird works better there
Assignee: bugsquad => kde
The bug appeared also on other desktop environments. The problem didn't appear when I deleted the old configuration files .thunderbird and started a fresh version of Thunderbird. On Mageia 6 Thunderbird has been updated to the version 60.3.3 and nobody else reported a problem. I think it doesn't make sense to invest any more time on this bug. I suggest to close this bug. I myself have set up a fresh Thunderbird from scratch and this worked without any problem. Thanks for your support!
Resolution: (none) => FIXEDStatus: NEW => RESOLVED