Bug 1463 – Visual corruption after running 2.1.2, 2.0.0 or 2.0.3 then HEAD

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 1463 - Visual corruption after running 2.1.2, 2.0.0 or 2.0.3 then HEAD


Summary:	Visual corruption after running 2.1.2, 2.0.0 or 2.0.3 then HEAD

Status:	CLOSED WONTFIX

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.1.3
Hardware:	Per OS All

Importance:	P4 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:	upgraders

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-07-28 12:01 UTC by Gale Andrews
Modified:	2019-06-14 04:17 UTC (History)
CC List:	4 users (show)

See Also:
Steps To Reproduce:	1 Quit Audacity and delete audacity.cfg. 2 Run 2.1.2, exit, run 2.0.0 or 2.0.3, exit, run HEAD, observe display corruption in upper tooldock. 3 Reset Toolbars fixes it.
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gale Andrews 2016-07-28 12:01:22 UTC

Reproducible on my machines (1024px width monitors). 

See image at http://bugzilla.audacityteam.org/attachment.cgi?id=696.

Recording Meter Toolbar is not visible. Playback Meter Toolbar is behind the non-button areas in Transport Toolbar and covers the top row of Tools Toolbar.  Playback Meter Toolbar (what you can see of it) does not register playback.

Many users may currently be running 2.0.3 after 2.1.2 on Windows 10, given 2.0.3 was a recommended fix for 2.1.2's Internal PortAudio Error. Such users are expected to update to 2.1.3, given 2.1.3 will be announced as fully supporting Windows 10.

Comment 1 Peter Sampson 2019-06-13 12:22:02 UTC

The bug title refers to 
> ...after running 2.1.2, 2.0.0 or 2.0.3 then HEAD
Many users may currently be running 2.0.3 after 2.1.2 on Windows 10, given 2.0.3 was a recommended fix for 2.1.2's Internal PortAudio Error. Such users are expected to update to 2.1.3, given 2.1.3 will be announced as fully supporting Windows 10.
We are now way beyond 2.0.x and 2.2.x - so is this bug still valid for 2.3.x



Gales statement in Comment #1 is no longer relevant 
>Many users may currently be running 2.0.3 after 2.1.2 on Windows 10, 
>given 2.0.3 was a recommended fix for 2.1.2's Internal PortAudio Error. 
>Such users are expected to update to 2.1.3, given 2.1.3 will be announced 
>as fully supporting Windows 10.