Search Support

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.

Learn More

Thunderbird freezes almost immediately on startup on Fedora 32

  • 3 replies
  • 2 have this problem
  • 1 view
  • Last reply by Matt

more options

Hey all.

On my work desktop, I've got Thunderbird 68.11.0 (with add-ons: Thunderbird Conversations, Enigmail, and Cardbook) installed on Fedora 32. I don't know why, but when I launch it like normal, it is basically immediately non-responsive - I cannot click on ANYTHING in the user interface and get any kind of response. If I sneak a click in RIGHT as the interface loads, it responds, but after that there is nothing I can do.

I can't click on an email in the list, I can't click on a folder on the sidebar, I can't right-click to see my menus, I can't click on "Quick Filter" to hide the toolbar. The only parts of the interface that are responsive are the minimize/maximize/close buttons on the title bar - everything else is locked dead.

I allowed it to compact folders earlier, and I'm wondering if that has something to do with it - I'm now getting a "my@email.com: Looking for folders..." down in the status bar. I know that our email folders live on an SMB share (my "Local Folders" live at /home/tromlet/Mail), but Thunderbird is connected via IMAP and SMTP to our email server. There appears to be next to no CPU utilization coming from Thunderbird, which almost makes me think it's waiting on a reply from the server?

When I try running Thunderbird in safe mode (`thunderbird -safe-mode` in terminal) it seems to work, but as soon as I start it back up in normal mode I'm totally frozen again. I'm not sure what to do here, or if you guys have any suggestions.

Hey all. On my work desktop, I've got Thunderbird 68.11.0 (with add-ons: Thunderbird Conversations, Enigmail, and Cardbook) installed on Fedora 32. I don't know why, but when I launch it like normal, it is basically immediately non-responsive - I cannot click on ANYTHING in the user interface and get any kind of response. If I sneak a click in RIGHT as the interface loads, it responds, but after that there is nothing I can do. I can't click on an email in the list, I can't click on a folder on the sidebar, I can't right-click to see my menus, I can't click on "Quick Filter" to hide the toolbar. The only parts of the interface that are responsive are the minimize/maximize/close buttons on the title bar - everything else is locked dead. I allowed it to compact folders earlier, and I'm wondering if that has something to do with it - I'm now getting a "my@email.com: Looking for folders..." down in the status bar. I know that our email folders live on an SMB share (my "Local Folders" live at /home/tromlet/Mail), but Thunderbird is connected via IMAP and SMTP to our email server. There appears to be next to no CPU utilization coming from Thunderbird, which almost makes me think it's waiting on a reply from the server? When I try running Thunderbird in safe mode (`thunderbird -safe-mode` in terminal) it seems to work, but as soon as I start it back up in normal mode I'm totally frozen again. I'm not sure what to do here, or if you guys have any suggestions.

All Replies (3)

more options

As it works in Safe Mode, I would disable one addon at a time and do a restart each time. Test to see if all is ok. It might show an addon which is screwing things up or one addon is conflicting with another. Perhaps an addon needs updating.

Safe Mode also disables hardware acceleration. So if you have this enabled try switching it off. Edit > Preferences > Advanced > 'General' tab at the bottom...uncheck: 'Use hardware acceleration when available'

more options

Thanks for the response, Toad-Hall! Couple of things though:

  1. I have tried with safe mode, but I tried it today without turning add-ons off when it started up. Works just fine.
  1. I have not tried disabling hardware acceleration, but it was enabled before this problem.
more options

tromlet said

Thanks for the response, Toad-Hall! Couple of things though:
  1. I have not tried disabling hardware acceleration, but it was enabled before this problem.

As the setting is driver dependent, what has worked and what will work is never clear. Especially in Linux distros that are paranoid about open source everything like Debian. Not that I have any idea what distro you are using.