ID 432014 - Actions which are instances of mari.ScriptAction don't emit signals correctly.

Problem summary
Actions which are instances of mari.ScriptAction don't emit signals correctly.

Customer reported version
mari.4.6v3

Customer reported platform
windows10

Steps to reproduce

1) From Mari, open any project, then the Python Console.

2) Copy/Paste the following command: 

from PySide2.QtWidgets import QAction

def testResponse(name):
    print 'Action called: ' + str(name)

aboutAction = mari.actions.find('/Mari/Actions/About')
aboutAction.triggered.connect(lambda: testResponse('aboutAction'))

bakeAction = mari.actions.find('/Mari/Canvas/Bake')
bakeAction.triggered.connect(lambda: testResponse('bakeAction'))

fullScreenAction = mari.actions.find('/Mari/Scripts/Full Screen')
fullScreenAction.triggered.connect(lambda: testResponse('fullScreenAction'))

materialIngestAction = mari.actions.find('/Mari/Scripts/Material Ingest Tool')
materialIngestAction.triggered.connect(lambda: testResponse('materialIngestAction'))

3) Click Evaluate to run the script.

4) Open the Help > About menu and click off of it to close, observing the Python output.

5) Paint anywhere on the model, then press B on the keyboard to bake, and observe the Python output.

6) Press the Fullscreen shortcut Ctrl+Shift+F and observe output in the Python Console.

7) Select Tools > Material Ingest and bring in any material, then observe output in the Python Console.

Expected behavior
The Python Console should display output for the registered Script actions.

Actual behavior
The mari.ScriptActions are not called when input in the software.

Workaround
There is no available workaround at this time.

Reproduced by Support in

Mari 4.6v3 - Windows 10

Mari 4.6v1 - Windows 10

Mari 4.5v1 - Windows 10

Unable to reproduce bug in:

Mari 4.2v2 - Windows 10

Earliest version tested
Mari 4.2v2 - This feature did not exist before this version