Re: [orca-list] Plan to release new pre-release of Orca 3.32 ?
- From: Didier Spaier <didier slint fr>
- To: Samuel Thibault <sthibault hypra fr>
- Cc: Alex ARNAUD <alexarnaud hypra fr>, Joanmarie Diggs <jdiggs igalia com>, orca-list <orca-list gnome org>
- Subject: Re: [orca-list] Plan to release new pre-release of Orca 3.32 ?
- Date: Tue, 15 Jan 2019 10:22:37 +0100
On 14/01/2019 21:55, Samuel Thibault wrote:
Didier Spaier, le lun. 14 janv. 2019 21:52:38 +0100, a ecrit:
didier 5256 1 5256 4 5 20:05 tty1 00:04:20 orca
didier 5256 1 5363 0 5 20:05 tty1 00:00:00 orca
didier 5256 1 5364 0 5 20:05 tty1 00:00:00 orca
didier 5256 1 5368 0 5 20:05 tty1 00:00:00 orca
didier 5256 1 5429 0 5 20:05 tty1 00:00:05 orca
didier[~]$
Could it be that the function otherOrcas() finds e.g. 5363 != 5256
No, these are just threads of the same process, pgrep only finds
whole processes.
OK, found it.
Since some time I started Orca with a wrapper script named orca:
orca.bin &
setxkbmap
orca.bin being the real orca.
I did that because then every time I used the preferences GUI
it changed the X keyboard map even not making any change
So I though that maybe this instruction:
pid = os.getpid()
gave the pid of the wrapper script and of course then p != pid
So I just got rid of the wrapper script and Bingo! now orca -r works.
Fortunately there have been changes in Orca since I introduced
this workaround, so it is not needed any more.
Best,
Didier
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]