adapt-it / adaptit

Related language translation editor
Other
10 stars 5 forks source link

Balsa-XO/Adapt It: Temporary freezing #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Had only AI open, and adapted 2JN (English  -> German) and several
times, the XO was freezing temporarily: The cursor stopped blinking and AI
did not accept typing any more.
2. This happened in all kind of situations: 
- in typing in the middle of word
- after clicking Enter in the translation box and
- ....
3. It seemed to me that there was some kind of 'mental overflow' in the XO.
I waited some time (up to 3 minutes) and this did not changed.

What helped, was to click into the screen. Then the screen did a little
jump (flickered for a short moment) and then you could continue normally.

What is the expected output? What do you see instead?
To work normally

What version of the product are you using? On what operating system?
AI 4.1.2 with Balsa-XO

Please provide any additional information below.

Original issue reported on code.google.com by wolfgang...@gmx.de on 15 Apr 2009 at 9:41

GoogleCodeExporter commented 9 years ago
I have only recently installed Balsa and am still in the process of testing 
Adapt It
on the XO under Balsa. I've noticed that sometimes after there is no activity 
for a
while the screen seems to go into a lower power mode of some sort, and, as you
suggested, by clicking elsewhere (or even moving the pointer with the trackpad) 
there
would be a momentary flicker and the normal screen mode would return. Does this
happen in your situation even while you are actively typing in the phrasebox, 
or does
it happen only after you have not done any active typing for a while? In the 
Balsa
instructions Kim suggested typing the option "touch 
/mnt/etc/xo-suspend/aggressive".
If you typed this command during installation, perhaps this "aggressive" power 
saving
mode is the source of your current problem. I suggest you open the Terminal and 
type: 
   sudo rm /etc/xo-suspend/aggressive
then reboot the XO, and see if the problem persists. Let me know the result. 
Thanks
for your report.

Original comment by adaptitbill@gmail.com on 16 Apr 2009 at 5:13

GoogleCodeExporter commented 9 years ago
I did: 
- sudo rm /etc/xo-suspend/aggressive(had to log in as olpc to allow to use sudo)
- logging in as user (balsa):
- opened AI
- opened the Input Text dialog box, and the first freezing happened.(USB mouse 
and
keyboard not responding). 
- Using the XO mousepad, let the screen flicker and it worked again).
- Typing this text (on a different computer): same thing happens

Now here is a good situation, which showing the problem.
- open the Knowledgebase,
- scroll down the ScourePhrase window (with DownArrow)
- keep DownArrow pressed, till the XO 'freezes'
- now neither the external mouse or external keyboard works.
- only clicking with the XO mousepad into the Source Phrase windows 'unfreezes' 
the XO.

This also happens in AI/Help
So I suppose, that this problem is not so much Adapt It related than XO related.
-

Original comment by wolfgang...@gmx.de on 17 Apr 2009 at 7:58

GoogleCodeExporter commented 9 years ago
Yes, it appears that the problem is probably related to the XO itself. Although 
I
sometimes see a flicker as I described previously on my XO machines, this never
causes the computer to freeze up under Balsa. I wonder if there may be some
incompatibility with the keyboard or mouse that you are using with the XO.

Original comment by adaptitbill@gmail.com on 18 Apr 2009 at 3:32

GoogleCodeExporter commented 9 years ago
Thanks for this advice.
I removed the keyboard and the mouse, and the XO started to work normally.
Then I had the XO booted first and then the keyboard and mouse added, and it 
still
worked normally.
Then I booted with the keyboard and mouse attached, and still no problems.

Last Friday, the problem was so bad, that I nearly could do only 2 or three 
steps,
and then it did not move any more.

So, if the thing happens again, I will try to find out more of the 'context' of 
this
problem and how to avoid it.

Original comment by wolfgang...@gmx.de on 20 Apr 2009 at 8:16