nostalgy-xpi
nostalgy-xpi copied to clipboard
opto
Solved (maybe?) with TB v91.9.0, Nostalgy++ v3.4.2...?? : Significant problems: Nostalgy++ versions beyond v3.2.0 on TB v91.8.x, macOS 10.15.7: customized keys do not work (at least)
My experience per the "forced upgrade" (described in the issue #159) is that there are numerous things broken with Nostalgy++ v3.2.16 on Thunderbird v91.6.1. There were so many things not working I decided not to log the issue. I'm mostly a "custom keys" user, and at some point many (most?) of the custom keys were not working... but again, I was in no way being comprehensive in tracking what worked and what didn't. There were other keys not w
I have since reverted back to Nostalgy++ v3.2.0 on Thunderbird v91.6.0.
for move > 100 messages and mouse up bounce for mouse gesturees, please try: https://github.com/opto/nostalgy-xpi/releases/tag/v3.2.18
Understood, and thanks Klaus for the followup. However, it's important to note: I could not perform most any, basic custom-key command (eg: single message move, copy) with my above config.
for move > 100 messages and mouse up bounce for mouse gesturees, please try: https://github.com/opto/nostalgy-xpi/releases/tag/v3.2.18
not here. which OS? which other addons? restrict to mailTab does not help?
Any other addon registering keys? All that code has not changed.
macOS 10.15.7.
Many thanks Klaus for looking into this. However, these symptoms were so bad, I figured there was something else wrong (beyond Nostalgy++). Let's pause investigating this issue for now, and if I find myself in a similar place again (in the near term), we can revisit this issue.
I simply documented the issue here in case it was good for you Klaus to know about it.
I have since reverted back to Nostalgy++ v3.2.0 on Thunderbird v91.6.0 and everything is fine again. (Remember: v3.2.16 was "forced" on me because of #159).
Should I try upgrading to v3.2.8?
let us see whether the people with the mouse gesture problem are ok now
and yes, on MacOS we had several problems up to now.
Actually, TB has. Addons can register the browser action button, which can have a menu. So it should have a down arrow such as other menu-buttons. I am told by TB people that we all don't have this arrow because it cannot be displayed o Mac. (by the experts in TB team)
Klaus, are you referring to specific version of TB and Nostalgy++ in these comments that immediately follow below, and if so, which ones?
let us see whether the people with the mouse gesture problem are ok now
and yes, on MacOS we had several problems up to now.
Actually, TB has.
I have no idea why we are discussing "browser action button," "down arrows," and "menu buttons" on this issue (per the comments below), I'm completely lost when I read the comment below (maybe these things apply to errors/problems with more-recent Nostalgy++ versions, problems I've not yet experience? I'm not sure). I do not see how any of those things apply. But that's okay, I doubt I need to understand. I'm simply reporting in this issue that the Nostalgy++ v3.2.16 + TB 91.6.1 + macOS 10.15.7 combination failed so badly on this system that it's not even worth trying to debug it right now. Maybe I'll try other version-combinations later.
Addons can register the browser action button, which can have a menu. So it should have a down arrow such as other menu-buttons. I am told by TB people that we all don't have this arrow because it cannot be displayed o Mac. (by the experts in TB team)
Thanks Klaus for all your efforts on this project, it's awesome!
Update:
I just upgraded to Nostalgy++ v3.2.17 (while remaining on TB v91.6.0, macOS v10.15.7) from v3.2.0. And the same "major breakage" symptoms described above immediately started happening (even without restarting TB).
Seems to me like there's major v3.2.0+ issues with key bindings on v91.6.x on macOS. This seems quite repeatable.
I'm reverting to v3.2.0 for now. I might try v3.2.8 or some other "more recent" Nostalgy++ version later.
3.2.17 s identical to 3.2.16, I just was asked to remove an obsolete file.
If, then you need to install 3.2.18 after download from file, using the link given in the other post
Update
Summary: no issues (yet) with v3.2.8.
Details
I reverted back to v3.2.0 and then upgraded to v3.2.8, which seems to work fine (or at least, no immediate issues found like with v3.2.17).
I'll next try v3.2.18 next and report back.
Update: v3.2.18 breaks just as badly as v3.2.16 and v3.2.17 (all on TB v91.6.0). v3.2.8 works just fine.
macOS details:
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H1713
$
Update: v3.2.8 started giving me problems (after using TB for several mins, unlike v3.2.16 and above, which fails immediately), again with some/many of the custom keys not working. So I reverted back to v3.2.0, which seems to be the only recent, "known working" (so far) version of Nostalgy++ for my environment.
Also: I'm running TB v91.6.1 now (upgrade over v91.6.0).
Hi Klaus (@opto) - can you share your position on this topic? I understand if you're disregarding this issue because you're unable to duplicate any problems.
I want to stress: the most-recent versions of Nostalgy++ (particularly v3.2.16 and above) immediately breaks most every customized key in my Nostalgy++ configuration. It's really bad.
v3.2.0 seems to work with no problems over a long period of time. v3.2.8 "eventually" breaks.
I don't remember any changes with respect to the keys in all those versions. I will have a look at the code.
Is there a difference in behaviour, if you install and use a version, versus install, restart TB, use then?
Do you install ober or deinstall the old first?
I don't remember any changes with respect to the keys in all those versions. I will have a look at the code.
My guess: the behavior is so broken that something unrelated to keys may be causing a more-general problem. For example: a possible memory-buffer overwrite. However, this is all pure speculation, I have no specific data to support this.
Is there a difference in behaviour, if you install and use a version, versus install, restart TB, use then?
My tests included at least one restart of Thunderbird and then retesting. All scenarios were similarly broken.
Do you install ober or deinstall the old first?
Assuming these is the same question:
"Do I first de-install Nostalgy++ (original version) and then reinstall Nostalgy++ (new version)?"
No, I simply install the new version without de-installing the original version.
Klaus (@opto)- do my writings above answer all your questions and provide you all the context you are seeking?
Tested with Nostalgy++ v3.3.17 and experience same problems:
- All customized keys appear to be disabled immediately or within a few seconds of a TB restart.
- TB was restarted at least 5 times after Nostalgy++ v3.3.17 install.
- I reverted back to v3.2.0 and all works once again.
Thunderbird v91.6.1. macOS v10.15.7.
Update: I tested the above with Thunderbird v91.7.0. In very limited (read: not comprehensive) testing I experienced the same problems, so I reverted back to Nostalgy++ v3.2.0 (once again).
Update: I upgraded Thunderbird to v91.8.1. Nostlagy++ v3.2.0 still works (thus far). The more-recent Nostalgy++ versions I tried all break (I tried v3.2.17, v3.3.19, maybe one other) all break in the same way as mentioned before. My tests today suggest the customized-keys (in Nostalgy++) sometimes become "deactivated" not as quickly as tests I performed above.
Update: I updated Thunderbird to v91.9.0 and Nostalgy++ v3.4.2 (with the still-unwanted "forced upgrade" described in the issue #159 -- but not a big problem).... and I am unable to get anything to break or misbehave after several minutes of usage and Thunderbird restarts.
-
This is great news in the sense that the latest version(s) of things all seem to work (woo hoo!)!
-
It's (kind of) bad news in that we still have no root cause for previously-unworking behavior. (Alas, we can not always get everything we want. 🤓)
If I experience any further problems I will post here. Let's give it a couple weeks before closing this issue, if that works?