Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

How to fix folder columns getting always reset to default?

  • 2 replies
  • 1 has this problem
  • 3 views
  • Last reply by sashka76

sashka76
sashka76
more options

I go to a folder, say, Sent. Re-order header columns, add those I want, remove those I don't want. Click on different folder. As soon as I go back to the folder Sent, the columns are reset to default (both the order and what columns are displayed). I tried going through Apply To Folder menu -- still no effect. Tried to delete MSF file for folder Sent -- does not help. Every time I go to a folder, its columns are set to default display.

I go to a folder, say, Sent. Re-order header columns, add those I want, remove those I don't want. Click on different folder. As soon as I go back to the folder Sent, the columns are reset to default (both the order and what columns are displayed). I tried going through Apply To Folder menu -- still no effect. Tried to delete MSF file for folder Sent -- does not help. Every time I go to a folder, its columns are set to default display.

Modified by sashka76

Chosen solution

OK, just fixed it myself. Disabled Mnenhy and Lightning extentions -- and it works properly (not sure which one was causing it, but who cares)

Read this answer in context 👍 0

All Replies (2)

sashka76
sashka76 Question owner
more options

Just some additional info: I am running Arch Linux, Thunderbird version - 52.4.0 (64-bit)

sashka76
sashka76 Question owner
more options

Chosen Solution

OK, just fixed it myself. Disabled Mnenhy and Lightning extentions -- and it works properly (not sure which one was causing it, but who cares)