Closed Bug 1711307 Opened 4 years ago Closed 4 years ago

Cannot Change Column Widths - problem with xulstore.json

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wolfiejunk, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36

Steps to reproduce:

When adjusting column widths in the folder pane, the cursor changes to a double arrow when placed on the separator between "Name" and Total in the headings row. The column width can then be adjusted.

The same procedure used to be how it worked in the message pane. Currently, no matter where the cursor is moved in the column headings, a double arrow cursor change does not happen and the column widths cannot be changed.

Actual results:

See above.

Expected results:

When the cursor is placed over the separator bars in the column headings, it should change to a double arrow cursor and enable changing (dragging) the column size.

I can not reproduce using Thunderbird 78.10.1 on Fedora 34 Workstation, Gnome 40 desktop, or Windows 10.

Component: Untriaged → Folder and Message Lists
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
See Also: → 1651940, 1684995

Nor can I reproduce it on other machines.

This machine:

Processor Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
Installed RAM 32.0 GB (31.7 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 10 Pro
Version 20H2
Installed on ‎12/‎27/‎2020
OS build 19042.985
Experience Windows Feature Experience Pack 120.2212.2020.0

Likely something wrong with your xulstore.json which stores the column widths. Remove/rename it and then try again.

Per your suggestion, I Just tried that, José.
No cigar, same issue.

It rings a bell, but I can't find where I've seen it before. Try running in safe mode, Help > Restart with Add-ons Disabled. That also resets some other settings to their default value temporarily. Next would be to try on a new profile. You can create one via Help > Troubleshooting Information, about:profiles, or by starting Thunderbird with -p. This is not a TB bug, something has gone wrong in that particular profile. You can also check the error console, Tools > Developer Tools > Error Console.

It rang a bell for me, too, José, but no cigar. I set it to safe. ... no change. Removed Tbird and d/l and install the newest version... no change.

That means that the issue is somewhere in the profile itself. That makes for a little more work since I am not totally sure where the settings are for things like the passwords and account settings, layouts, etc. The emails themselves are not an issue, but the settings are.

But one thing seems to be true. It is not, as you said, a Tbird bug.

Set the profile for the old location and walla, the issue resurfaces. Not knowing what file is responsible makes it difficult, but I can with time copy files from the default profile one at a time and see when it clears up.

Well, it's a TB bug insofar as it shouldn't behave that way without an error message or some indication as to what's going wrong.
https://www.google.com/search?q=thunderbird+cannot+resize+columns
found a few things:
https://support.mozilla.org/en-US/questions/1271281 with a link to
http://forums.mozillazine.org/viewtopic.php?f=39&t=3055940

The settings are all over the place in the profile, there is prefs.js which has the accounts; passwords are in those .db files, then there are address books in .sqlite files (referenced from prefs.js), there is calendar data (folder calendar-data). And there are other bits, like extensions, OpenPGP data (if you use OpenPGP) and much more. Depending on how much time you want to invest and what your skills are, you could take a backup copy of the profile then remove everything except what I mentioned. If the "damage" is in the prefs.js, then you have a bigger issue.

José, on the one link you gave me, http://forums.mozillazine.org/viewtopic.php?f=39&t=3055940 I found the following:


mitchara

Posts: 1
Joined: January 6th, 2020, 5:02 am
Post Posted January 6th, 2020, 5:16 am

I suffered the same issue and I just found a workaround.
If your problem is the same as mine, hopefully you can at least change the order of the columns by dragging the headings. Try a drag. After that the resizing action works fine for me. Maybe the heading line gets some "focus" when you click/drag on it.

In my case, just after starting Thunderbird the mouse cursor won't change to a double arrow as it is supposed to even when you hover it on column borders, but after "focusing" the header line it starts to work.
Hope it helps.

That absolutely worked and it also cemented into place this being a bug in TBird. Moving the columns is programmatic in that TBird records the changes somewhere. If it were file corruption that should not work to correct the issue. It is certainly a bizarre bug, but there you have it.

Many thanks for your help. I had searched as well, but never hit on that post.

See Also: → 1673796

@Reporter,
Does this still reproduce when using version 91? And if you resolved the problem, what was the solution?

Flags: needinfo?(wolfiejunk)
Summary: Cannot Change Column Widths → Cannot Change Column Widths - problem with xulstore.json

@Reporter,
Does this still reproduce when using version 91? And if you resolved the problem, what was the solution?

Whiteboard: [closeme 2021-12-22]

Wayne,
At the point where I recently replaced the computer on which the error was occurring, the issue was resolved. I am not sure what caused that to happen, but suspect that since the programs loaded on the new one were different that it was probably software other than Thunderbird causing an issue. Thanks for the follow-up.

Flags: needinfo?(wolfiejunk)

Resolved per whiteboard and Comment 12

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2021-12-22]
You need to log in before you can comment on or make changes to this bug.