-
-
Notifications
You must be signed in to change notification settings - Fork 784
--no-logging option does not work anymore #19333
Copy link
Copy link
Labels
bug/regressioncomponent/loggingneeds-technical-investigationA technical investigation is required to progress the issue.A technical investigation is required to progress the issue.p2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
bug/regressioncomponent/loggingneeds-technical-investigationA technical investigation is required to progress the issue.A technical investigation is required to progress the issue.p2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for Bug.
Steps to reproduce
Launch:
nvda --no-loggingActual behavior
Expected behavior
NVDA starts normally.
NVDA logs, crash dumps and other attachments
None, logically, since we use the
--no-loggingoption...System configuration
NVDA installed/portable/running from source
Portable and from source
NVDA version
Windows version
Windows 11 24H2 (AMD64) build 26100.7171
Name and version of other software in use when reproducing the issue
N/A
Other information about your system
N/A
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors
Tested:
Both start normally with
--no-loggingoption, so the regression happened laterIf NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested.