Page MenuHome

Blender displays an error everytime I press Num Lock
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-13 16:27, hash: rB9b6d31fa6991
This happens on any version of blender after 2.80, but doesn't happen on 2.79 or below.

Short description of error
So, I know this is not any dealbreaker and such, but everytime I press the Num Lock button, Blender displays an error regarding context and such (image below).
I've been teaching Blender for some people and they usually freak out when they press Num Lock by accident and it displays that error, even though it doesn't change anything important for us AFAIK.

Interestingly, when - and only when - the mouse is over the properties panel, it show a menu to shitch between the properties tab disposed.

I'll put the error that appears on the log here, cause it can be useful:

Traceback (most recent call last):
  File "C:\ [insert path here] \blender-2.82-9b6d31fa6991-windows64\2.82\scripts\startup\bl_operators\wm.py", line 525, in execute
    value = context_path_validate(context, data_path)
  File "C:\ [insert path here] \blender-2.82-9b6d31fa6991-windows64\2.82\scripts\startup\bl_operators\wm.py", line 84, in context_path_validate
    value = eval("context.%s" % data_path) if data_path else Ellipsis
  File "<string>", line 1, in <module>
AttributeError: 'SpaceView3D' object has no attribute 'context'

location: <unknown location>:-1

Please note that 'SpaceView3D' refers to the 3D viewport because it's where my cursor was at that moment. If the cursor is on e.g. the Outliner, it will display the same error, but with 'SpaceOutliner' on that line instead.

Exact steps for others to reproduce the error

  • Open the startup Blender file;
  • Put the mouse pointer over any Blender panel, besides the Properties panel;
  • Press Num Lock
  • Displays the error

Have a nice thay <3

Event Timeline

Germano Cavalcante (mano-wii) lowered the priority of this task from 90 to 30.Nov 20 2019, 3:42 PM

I can't reproduce the problem.
Could you further detail the steps to reproduce it?
The same happens after loading the factory settings? (File -> Defaults -> Load Factory Settings)

So, I loaded the factory settings and the error disappeared. Thank you for that!

But before that, I've saved my keymap settings to see if there's something to do with that, and indeed it was. The only problem is that the "num lock" button don't appear on the keymap search bar, so I have no idea what shortcut (or anything like that) was assigned to it.

Still wondering why that was happening on other computers here though...

Germano Cavalcante (mano-wii) changed the task status from Unknown Status to Unknown Status.Nov 20 2019, 6:45 PM

Good that was resolved.
Maybe some versioning did not correctly update the previous version installed (this can happen with experimental builds).
Or maybe some addon caused it.
That error message should not appear anyway, but as we don't have much information to reproduce the error, I will archive the report.