Unable to quit NVDA on my Windows 7 64-Bit computer with (NVDA) Version: next-11133,ed1859a.

[nvaccessAuto]

Reported by Brendon22 on 2014-10-06 11:28
Hello,

I am not sure what is going on!! When I try and quit NVDA with the following instructions: Press NVDA+Key+Q running on the laptop mode so, with caps lock and Q, NVDA just sounds the error sound and will not quit from my Windows 7 64 Bit computer. Why is this? Using (NVDA) Version: next-11133,ed1859a. Then when I try and press the NVDA Key+N to get the NVDA menu up , the menu will stay on the screen for about three seconds then will return me to my desktop. I can't stop NVDA running , why is this?

Thank you.

Brendon Donohue.
Blocking #3763

[nvaccessAuto]

Comment 1 by ateu on 2014-10-06 12:18
Yes, I can confirm this.
My system is Windows 7 64 bit.
I press NVDA+q and NVDA is not quited, so that I have to close it using task manager.

[nvaccessAuto]

Comment 2 by jteh on 2014-10-07 05:00
Do you have any add-ons installed? If so, does this occur without them?

If you get an error sound, that means an error was logged. Please provide a log file as described in LogFilesAndCrashDumps.

[nvaccessAuto]

Attachment nvda.log added by ateu on 2014-10-07 10:00
Description:

[nvaccessAuto]

Comment 3 by jteh on 2014-10-07 10:18
Thanks for the log. You didn't mention whether this occurs if you disable any add-ons. Also, I assume you only get the error sound after you try NVDA+q the second time?

I might need a log at level debug to have any chance of figuring this out. I can't reproduce it here.

[nvaccessAuto]

Attachment nvda_debug.log added by ateu on 2014-10-07 13:07
Description:

[nvaccessAuto]

Comment 4 by ateu on 2014-10-07 13:11
Hi,

Once NVDA+q is pressed and the error occurs, it's not possible to open any dialog. Also, it's not possible to close NVDA or open a dialog using the menu. My add-ons are just synthesizer, and recently I haven't installed or removed any add-on.

[nvaccessAuto]

Comment 5 by jteh (in reply to comment 4) on 2014-10-07 22:54
Replying to ateu:

My add-ons are just synthesizer

I see MouseGuide, nvSpeechPlayer, ocr, Softvoice Speech Hub and Weather Plus.

and recently I haven't installed or removed any add-on.

That doesn't matter. There could still be a bug in an add-on that only happens to trigger a problem due to a recent change. Note that i have nvSpeechPlayer and ocr installed and don't see this, so it probably isn't one of those, if it's any of them at all.

Thanks for the new log. However, it appears to be the wrong one. I see you moving through a log in a text editor, but not the actual quit log. You'll probably need to provide nvda-old.log, not nvda.log, as nvda.log is for the currently running copy.

[nvaccessAuto]

Comment 6 by jteh on 2014-10-08 01:26
Please try this try build and report whether it fixes the issue. I'd still like to know why it doesn't occur for most users, though.

[nvaccessAuto]

Comment 7 by ateu on 2014-10-09 01:22
Hi,

Using this build, the problem doesn't occurs.

[nvaccessAuto]

Comment 8 by jteh on 2014-10-10 11:05
Okay. This fix is bb218fc (incubated in e3e0e85). It should be in the "next" branch snapshot for 11 October.

Closing as fixed as per comment:7. Please reopen if the problem persists.
Changes:
State: closed

[nvaccessAuto]

Comment 9 by ateu on 2014-10-17 12:52
Hi Jamie,

From new tests, I can notice that when using add-ons, the problem occurs. However, once removed all add-ons, the problem doesn't occurs.

[nvaccessAuto]

Comment 10 by ateu on 2014-10-17 13:17
Wow! The problem was being caused by an add-on: jumpToLine.
Once I removed it, all is normal.

[nvaccessAuto]

Comment 11 by Brendon22 on 2014-10-18 21:21
Hello,

Thank you for looking into this. Very sorry that it has taken me a while to get back to you regarding this. This issue is still happening with the new version of NVDA. I get the following error:

Exiting
ERROR - scriptHandler.executeScript (07:13:37):
error executing script: <bound method GlobalCommands.script_quit of <globalCommands.GlobalCommands object at 0x057844F0>> with gesture u'NVDA+q'
Traceback (most recent call last):
File "scriptHandler.pyc", line 174, in executeScript
File "globalCommands.pyc", line 830, in script_quit
File "gui__init__.pyc", line 503, in quit
File "wx_core.pyc", line 16709, in getattr
PyDeadObjectError: The C++ part of the MainFrame object has been deleted, attribute access no longer allowed. Please look into this. There is clearly an issue.
Changes:
State: reopened

[nvaccessAuto]

Comment 12 by nvdakor (in reply to comment 11) on 2014-10-18 21:49
Replying to Brendon22:

Hello,

Thank you for looking into this. Very sorry that it has taken me a while to get back to you regarding this. This issue is still happening with the new version of NVDA. I get the following error:

Exiting

ERROR - scriptHandler.executeScript (07:13:37):

error executing script: <bound method GlobalCommands.script_quit of <globalCommands.GlobalCommands object at 0x057844F0>> with gesture u'NVDA+q'

Traceback (most recent call last):

File "scriptHandler.pyc", line 174, in executeScript

File "globalCommands.pyc", line 830, in script_quit

File "gui__init__.pyc", line 503, in quit

File "wx_core.pyc", line 16709, in getattr

PyDeadObjectError: The C++ part of the MainFrame object has been deleted, attribute access no longer allowed.

This is with latest next build, right? If so, please try with no add-ons (press Control+Alt+N to forcefully restart, then try restarting with add-ons disabled). If you are using latest next, try quitting to see if the dead object error is logged.
Thanks.

[nvaccessAuto]

Comment 13 by Brendon22 on 2014-10-18 22:29
Hello,

Yes, the version that is the latest. Note: ALT+Control N doesn't do anything when you press it. Is there a keystroke to disable Add-Ons or do I have to remove all of them?

[nvaccessAuto]

Comment 14 by jteh on 2014-10-19 03:35
Please state the exact version you're running. Thanks.

[nvaccessAuto]

Comment 15 by Brendon22 on 2014-10-19 04:51
Hello,

Next-11171,e90ea82 is the version I am using. There is an issue.

[nvaccessAuto]

Comment 16 by jteh (in reply to comment 13) on 2014-10-19 22:37
Replying to Brendon22:

Is there a keystroke to disable Add-Ons or do I have to remove all of them?

If you have the exit dialog enabled in General settings, when you press NVDA+q, one of the options allows you to Restart with add-ons disabled. This is a very recent change. Please try this and report. Thanks.

Possible duplicate of #4474.

[nvaccessAuto]

Comment 17 by Brendon22 on 2014-10-24 10:37
Hello.

Thank you for this. I check this setting. I didn't have this setting checked. But there is still issues: when I try and restart NVDA with Add-Ons disabled NVDa restarts, but then when I try and get NVdA just to exit, it will not do anything and there isn't any error sound? The dialog doesn't come up, so there is still something strange going on. This is the 23 10 snapshot.

Thank you. Please advise?
Brendon Donohue.

[nvaccessAuto]

Comment 18 by jteh on 2014-10-26 22:20
Did you save settings after enabling the exit dialog? Otherwise, pressing NVDA+q after the restart might just exit without bringing up the dialog. If that's not the case, I think we'll need to see a log at level input/output for the session with add-ons disabled.

[nvaccessAuto]

Comment 19 by Brendon22 on 2014-10-27 10:34
Hello,

Yes, this is what I did, save the settings. But NVDA will still not close without this dialog being enabled. Do you want me to provide a log then?

Thank you.

[nvaccessAuto]

Comment 20 by jteh on 2014-10-27 10:57
I'm confused. Let's go back to the start.

If you:

1. Enable the exit dialog;
2. Save settings (NVDA+control+c);
3. Press NVDA+q;
4. Choose to restart with add-ons disabled;
5. Press NVDA+q; and
6. Choose to exit.
   Does NVDA exit correctly? If not, what happens instead?

Are you using an installed or portable copy? If portable, note that NVDA dialogs may not get focus correctly and you might need to alt+tab to them. This is a known, intermittent and unavoidable issue with portable copies.

[nvaccessAuto]

Comment 21 by Brendon22 on 2014-10-27 13:49
Hello again,

I'm confused. Let's go back to the start.

Sorry, it wasn't my intent to make you confused.

If you:

1. Enable the exit dialog;
2. Save settings (NVDA+control+c);
3. Press NVDA+q;
   4.Choose to restart with add-ons disabled;
   5.Press NVDA+q; and
4. Choose to exit.

Does NVDA exit correctly? If not, what happens instead?

Yes, NVDA restarts correctly but restarts with the NVDA error sound? But if I hit on exit only, NVDA doesn't exit at all. It just continues to work like it was not told to exit at all. Very strange. Then when I try and bring up the exit dialog again, this is when I hear the error sound. Hmm.

Are you using an installed or portable copy? If portable, note that NVDA dialogs may not get focus correctly and you might need to alt+tab to them. This is a known, intermittent and unavoidable issue with portable copies.

Installed copy, addmin on the computer with UAC turned off.

Thanks.

[nvaccessAuto]

Comment 22 by Brendon22 on 2014-11-11 09:40
Hello, Again.

I have done some mor looking into this. When I tell NVDA to restart with all add-Ons disabled, I get the following error in the NVDA log with the NVDA error sound, so I don't think this is related to an Add-On. Here is the error:

ERROR - synthDriverHandler.setSynth (18:56:56):
setSynth
Traceback (most recent call last):
File "synthDriverHandler.pyc", line 86, in setSynth
File "synthDriverHandler.pyc", line 38, in _getSynthDriver
ImportError: No module named eloquence
INFO - synthDrivers.espeak.SynthDriver.init (18:56:56):
Using eSpeak version 1.48.03 04.Mar.14

Please advise?

Thank you.

[nvaccessAuto]

Comment 23 by nvdakor (in reply to comment 22) on 2014-11-11 09:43
Replying to Brendon22:

Hello, Again.

I have done some mor looking into this. When I tell NVDA to restart with all add-Ons disabled, I get the following error in the NVDA log with the NVDA error sound, so I don't think this is related to an Add-On. Here is the error:

ERROR - synthDriverHandler.setSynth (18:56:56):

setSynth

Traceback (most recent call last):

File "synthDriverHandler.pyc", line 86, in setSynth

File "synthDriverHandler.pyc", line 38, in _getSynthDriver

ImportError: No module named eloquence

INFO - synthDrivers.espeak.SynthDriver.init (18:56:56):

Using eSpeak version 1.48.03 04.Mar.14

Please advise?

Thank you.

This is normal for a snapshot (see my comment on #4057). According to Jamie, this will not occur when 2014.4 official is used. Thanks.

[nvaccessAuto]

Comment 24 by Brendon22 on 2014-11-11 09:48
Hello,

Thank you for your quick reply. OK, that is fine, but the question is, could this error cause NVDA to not restart correctly?

Thank you.

[nvaccessAuto]

Comment 25 by nvdakor (in reply to comment 24) on 2014-11-11 09:51
Replying to Brendon22:

Hello,

Thank you for your quick reply. OK, that is fine, but the question is, could this error cause NVDA to not restart correctly?

Thank you.

In a way, think of no add-ons mode as a safe mode for NVDA where you want to use no add-ons or to isolate problems with add-ons. This will let NVDA use eSpeak - that is, it'll still be NVDA but with no add-ons. To get your add-ons back, restart NVDA. Thanks.

[nvaccessAuto]

Comment 26 by jteh (in reply to comment 23) on 2014-11-11 09:56
Replying to nvdakor:

ImportError: No module named eloquence

This is normal for a snapshot (see my comment on #4057). According to Jamie, this will not occur when 2014.4 official is used.

That's not quite right. The exception will still occur, but you won't hear the error sound, since error sounds are disabled in rcs and final releases. This error just indicates that the synth you are using can't be loaded, which makes perfect sense because it's an add-on and add-ons are disabled. So, NVDA falls back to eSpeak.

[nvaccessAuto]

Comment 27 by Brendon22 on 2014-11-11 09:57
Hello,

Yes, I understand what the mode is for, what I can't understand is why I can't restart NVDA when I have Add-Ons on?

Thanks.

[nvaccessAuto]

Comment 28 by nvdakor (in reply to comment 27) on 2014-11-11 10:02
Replying to Brendon22:

Hello,

Yes, I understand what the mode is for, what I can't understand is why I can't restart NVDA when I have Add-Ons on?

Thanks.

Ah, the original issue: you can't restart NVDA when add-ons are on because one or more add-ons will not exit correctly. Based on our previous conversation, have you removed the offending add-ons which causes NVDA to not restart to see if they are the real culprits?
@jteh: should have gone over differences between pyc and pyo - oops, got it now.
Thanks.

[nvaccessAuto]

Comment 29 by Brendon22 on 2014-11-11 10:03
Hello,

I see what you are saying regarding the error and that makes sence. But I can't understand why I can't quit NVDA when Add-Ons are running?

Thanks.

[nvaccessAuto]

Comment 30 by jteh (in reply to comment 29) on 2014-11-11 10:06
Replying to Brendon22:

I see what you are saying regarding the error and that makes sence. But I can't understand why I can't quit NVDA when Add-Ons are running?

Almost certainly because one of the add-ons you are using has a bug. It might not have been triggered before now, but it's still a bug. That's why I wanted you to test with add-ons disabled. If you can exit fine with add-ons disabled, then the problem lies in an add-on you are using.

[nvaccessAuto]

Comment 31 by Brendon22 on 2014-11-11 10:14
Hello,

Thank you for your reply. Yes, NVDA will restart fine withouth Add-Ons turned on. What Add-On should I remove to try and resolve this issue?

Thanks.

[nvaccessAuto]

Comment 32 by jteh on 2014-11-11 10:15
I'm afraid it's probably going to be a painful process of trial and error.

[nvaccessAuto]

Comment 33 by Brendon22 on 2014-11-11 10:19
Hi,

OK, thanks. I will try this over the next week or so and report back regarding this.

Thanks.

[nvaccessAuto]

Comment 34 by jteh on 2014-11-11 10:33
Joseph may be able to give you some idea of which add-ons he knows about with this problem...

[nvaccessAuto]

Comment 35 by Brendon22 on 2014-11-11 11:16
Hi,

Yes, great idea, Joseph can you provide me with any starting points?

Thank you.

[nvaccessAuto]

Comment 36 by nvdakor (in reply to comment 35) on 2014-11-11 20:52
Replying to Brendon22:

Hi,

Yes, great idea, Joseph can you provide me with any starting points?

Thank you.

Sure. Can you list names and versions of add-ons you've installed in your NvDA installation? I'll locate the source code for these add-ons and report back on the offending add-ons and will report my findings to the add-ons list.
Thanks.

[nvaccessAuto]

Comment 37 by Brendon22 on 2014-11-11 21:34
Hi mate,

These are the Add-ons I have installed:

balloon history with shift... runni... 1.1 Oriol gomez
Bit Che runni... 1.4-d... Alberto Zanella lapostadialberto@gmail.com, Alb
Driver for the braillenote ... runni... 0.2 Rui Batista
Control Usage Assistant -... runni... 2.1 Joseph Lee joseph.lee22590@gmail.com
Dropbox runni... 4.0-d... Patrick ZAJDA patrick@zajda.fr, Filaos and other c
Eloquence Synthesizer (a... runni... 0.201... NVDA user
Emoticons runni... 1.0 Chris Leo llajta2012@gmail.com, Noelia Ruiz Mar
eMule runni... 1.1-d... Noelia nrm1977@gmail.com, Chris <llajta2012@h
An extended appModule ... runni... 1.1 Hrvoje Katic hrvojekatic@gmail.com, NVDA-add
this addon is to put text ... runni... Jennifer Wenson <jwens82@gmail.com
read files using NVDA wit... runni... 1.1 Oriol gomez
GoldWave runni... 1.1 Joseph Lee joseph.lee22590@gmail.com, David P
Google Speech Recogniti... runni... 1.0 Mesar Hameed mhameed@src.gnome.org, beqa
Instant Translate - Transl... runni... 2.1 Alexy Sadovoy aka Lex lex@progger.su, ruslan <ru
NoBeepsSpeechMode runni... 1.2 Alberto Buffolino a.buffolino@gmail.com
Plays sounds based on o... runni... 0.201... Tyler Spivey tspivey@pcdesk.net
OCR runni... 0.201... NV Access Limited & other contributors

These should be the latest versions of these Add-Ons.

Thanks. I hope the list above is understandable?

[nvaccessAuto]

Comment 38 by nvdakor on 2014-11-11 22:23
Hi,
Found the culprit: @oriol, can you take a look at your File Reader add-on? The terminate method in there will not let NvDA exit. If you want your add-on listed in our community add-ons site, please rewrite the terminate method to remove this major bug.
For others (including the original poster): I'll ask on the NVDA Add-ons list to blacklist File Reader add-on until the exit bug is resolved. This will mean you need to uninstall this particular add-on to resolve exit issue. Thanks.

[nvaccessAuto]

Comment 39 by Brendon22 on 2014-11-11 23:02
Hi,

Thank you very much for this, I will remove this Add-On. What is it called in the Add-Ons manager?

Thanks.

[nvaccessAuto]

Comment 40 by jteh on 2014-12-03 03:10
Closing as invalid since this was determined to be a problem in an add-on (comment:31, comment:38).
Changes:
Added labels: invalid
State: closed

[nvaccessAuto]

Comment 41 by Brendon22 on 2014-12-03 12:01
Thanks for doing this, after removing the correct NVDA Add-On, restarting NVDA works fine.:).

[nvaccessAuto]

Comment 42 by Brendon22 on 2015-08-01 02:48
Changes:
Removed labels: invalid
State: reopened

[nvaccessAuto]

Comment 43 by Brendon22 on 2015-08-01 02:49
Good afternoon,
I can confirm that this issue has been resolved.
Closing.
Changes:
State: closed