PuTTY bug unix-bell-overload-timing-scale

This is a mirror. Follow this link to find the primary PuTTY web site.

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: Unix PuTTY misreads/writes bell overload timing settings
class: bug: This is clearly an actual problem we want fixed.
difficulty: fun: Just needs tuits, and not many of them.
priority: high: This should be fixed in the next release.
absent-in: 0.76
present-in: b00e5fb12929da5015e7331fe9b88f245301ebf2 0.77 0.78
fixed-in: 62b69a4f16875e75ece3c06fbe474104c5b5c089 7e8be5a204330c0307e07a5a96844fc8fc65d6cb (0.79)

There was a bug affecting the storage of settings for the 'bell overload' feature in Unix versions of PuTTY and pterm. (The Windows version is not affected.)

In versions 0.77 and 0.78 of PuTTY, the storage format for the two time-related settings was off by a factor of 1000, causing settings written by older versions to be misinterpreted. The fix for this could in turn cause settings saved with 0.77/0.78 to be misinterpreted by later versions, so you may want to review any sessions or Default Settings that may have been touched by these versions.

More specifically:

If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2023-08-25 23:02:41 +0100)