After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618285 - Orca -q and --replace should quit gracefully using kill.
Orca -q and --replace should quit gracefully using kill.
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.31.x
Other All
: Normal normal
: 2.32.0
Assigned To: Mesar Hameed
Orca Maintainers
Depends on:
Blocks: 591034
 
 
Reported: 2010-05-10 17:24 UTC by Mesar Hameed
Modified: 2010-09-20 10:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Rev 1. (2.76 KB, patch)
2010-05-17 08:24 UTC, Mesar Hameed
none Details | Review

Description Mesar Hameed 2010-05-10 17:24:08 UTC
At the moment we do 'kill -9' in orca.in (becomes orca.sh)
This doesnt actually give us time to do graceful shutdown, we should be using 'kill' and if the user provides --force then we really know something has hung, and then we should use 'kill -9'
for evidence see bug 591034#c14, comment 14, 15 and 16.
Comment 1 Mesar Hameed 2010-05-17 08:24:26 UTC
Created attachment 161207 [details] [review]
Rev 1.

Joanie, could you please check that this works ok on osol?

The reason for lowering the debug level in gnomespeech.py: __speak, is that with gnome speech, we never say goodbye anyway, and having a traceback on command line is ugly.
i am refering to Goodbye in orca.py:shutdown()
Comment 2 Joanmarie Diggs (IRC: joanie) 2010-05-17 10:09:24 UTC
(In reply to comment #1)
> Created an attachment (id=161207) [details] [review]
> Rev 1.
> 
> Joanie, could you please check that this works ok on osol?

Seems to be. I've tried both regular quits and forced quits. I'm not noticing anything different, so I'm assuming it's fine. <smile>
Comment 3 Mesar Hameed 2010-05-17 10:46:01 UTC
Thanks! Same patch is commited to master.
Comment 4 Joanmarie Diggs (IRC: joanie) 2010-05-17 12:32:42 UTC
Jon, any idea if something I'm seeing in the regression tests has anything to do with this fix? In particular, I now see for each test. Doesn't seem to impact the test results....

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer

** (orca:22180): WARNING **: Failed to send buffer
Comment 5 Mesar Hameed 2010-05-17 12:49:21 UTC
Hi Joanie,

Yes, they are from this one.
Its because before we use to terminate orca, and now we are asking it nicely to quit.
Its the gnome-speech that is causing this, and thats why i lowered it from severe to warning, but if you want the tests to run without having to modify the outputs, set the debug level in gnomespeech.py __speak() to none?
Comment 6 Joanmarie Diggs (IRC: joanie) 2010-05-17 14:14:25 UTC
I just commented both of those lines out and I'm still seeing the warnings. Other ideas?