Skip to content

Config profile triggers: a nonexistent key causes key error traceback when attempting to switch between profiles #8778

@josephsl

Description

@josephsl

Hi,

Perhaps a regression from Emoji announcement work: one cannot switch to profiles without encountering key error exception traceback.

Steps to reproduce:

  1. Create one or more config profiles.
  2. Open config profiles (Control+NVDA+P) and try to switch to a profile manually.
  3. Alternatively, trigger a profile via say all, switching between apps and so on.

Actual behavior:

ERROR - unhandled exception (21:28:27.158):
Traceback (most recent call last):
File "gui\configProfiles.pyc", line 259, in onClose
File "config_init_.pyc", line 753, in disableProfileTriggers
File "config_init_.pyc", line 374, in handleProfileSwitch
File "config_init
.pyc", line 943, in dict
File "config_init_.pyc", line 941, in dict
File "config_init_.pyc", line 864, in getitem
KeyError: u'x'

Expected behavior:

Profile switching works normally.

System configuration:

NVDA Installed/portable/running from source:

Installed

NVDA version:

Alpha.16103

Windows version:

Windows 10 Version 1809 Preview

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 PC?

Yes

Have you tried any other versions of NVDA?

No

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug/regressionp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions