Right clicking on any folder then left clicking on Search messages... brings up usual Search messages dialogue window but folder name drop-down list shows only No available folders rather than allowing choice from all folder names in all accounts. I *think* this effect started after most recent update to 52.1.1 Other symptoms are that 1. after close and restart of TB, the folder pane always shows all folders expanded where previously it remembered my usual view mode of Favorite, Compact View. I am able to restore my usual folder view after the restart. 2. Move to and Copy to folder name lists do not appear in the left click context menu but drag-n-drop messages into folders shown in left pane works. 3. TB installations on x86 Linux (48 branch) and x86 Windows 7 (52.1.1) work fine with same accounts/folders on the same IMAP server. I have deleted and rebuilt the global-messages-db.sqlite file without any improvement.
Does this happen with add-ons disabled, see Help menu?
(In reply to Jorg K (GMT+2) from comment #1) > Does this happen with add-ons disabled, see Help menu? Sorry, I should have mentioned that I had already tried that - safe mode with add-ons disabled does not change the behaviour.
It works for me, so there must something going on your machine, or there is a packaging issue on Linux. I don't quite understand the report: Windows 7 (52.1.1) works fine and Linux 52.1.1 doesn't work, right?
Summary: Search for messages in drop down list shows 'No available folders' → "Search for messages in:" drop down list shows 'No available folders'
(In reply to Jorg K (GMT+2) from comment #3) > It works for me, so there must something going on your machine, or there is > a packaging issue on Linux. I don't quite understand the report: Windows 7 > (52.1.1) works fine and Linux 52.1.1 doesn't work, right? Yes. But the Linux version 0n Mint 18 (Sarah, 64 bit) installed from the standard repos reports itself as 52.1.1 (64 bit) which I am assuming is a 64 bit app. On Windows 7 (64 bit), TB reports itself as 52.1.1 (32 bit) - a 32 bit build presumably - from which I suspect the problem is with the 64 bit build or its packaging.
Hi.. I'm relate to bug 1371947 I reported. As I understand this bug here is similar to my bug report. But in my case I use windows 7. Is the issue solved? //Charlie
> Is the issue solved? surely not - this bug report is still open :)
I've now had time to investigate further and have succeeded in avoiding the problem without actually identifying the root cause. I uninstalled then reinstalled TB on the problem system but the problem remained. I recently installed Linux Mint MATE 18 (64 bit) on another laptop then created my profile afresh/from scratch. This system - currently 52.2.1 - did not exhibit the problem so next step was to copy that working profile to the problem machine. Having switched to use the newer profile, the problem has gone. So, I suspect the problem was in my TB profile, and had been introduced at some point during a TB upgrade. However, still no closer to identifying the cause other than it looks to be profile 'corruption'.
You need to log in before you can comment on or make changes to this bug.