Opened 10 years ago

Closed 9 years ago

#1893 closed defect (duplicate)

OLPC-Write Activity – Cannot open write activity in OS802B5

Reported by: hiruni Owned by:
Priority: High Milestone: Unspecified
Component: Write Version: 0.84.x
Severity: Major Keywords: OS802B5
Cc: Distribution/OS: Other (name your distribution in the description)
Bug Status: New

Description

Description:

When user tries to open the ‘Write Activity’ by clicking on the icon, the screen displays that the activity is loading but it is not loading the activity.

Steps

  1. Power on OLPC
  2. Click on the write activity icon on home page.



Actual Result:

The screen displays the write activity is loading for a long time but not loaded the activity.



Expected Result:

When the icon of “Write activity” is clicked, the activity should be loaded in few seconds


Tested Environment


OS Build: OS802B5
Machine Type: XO 1.0
Firmware: Q2E41 and Q2E42
Security Disable: Yes
Sugar Version: 0.84
Activity Version: 60

Attachments (1)

log file.txt (4.8 KB) - added by hiruni 10 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 in reply to: ↑ description ; follow-up: Changed 10 years ago by sascha_silbe

Replying to hiruni:

When user tries to open the ‘Write Activity’ by clicking on the icon, the screen displays that the activity is loading but it is not loading the activity.

Unfortunately up to (but not including) the very latest release of Sugar (0.88), that's what happens when an activity fails to start. No matter how fast it fails, it will always shows the pulsing screen for a long time. See #1447 for details.

As for Write on OS802B5, can you attach the Write log file (~/.sugar/default/logs/org.laptop.AbiWordActivity-1.log), please?

comment:2 in reply to: ↑ 1 ; follow-up: Changed 10 years ago by hiruni

Although the Write log file (~/.sugar/default/logs/org.laptop.AbiWordActivity-1.log) is searched as you told to attach, it is not available in the XO. Followings are the steps I followed to search that file.

  1. Go to terminal
  2. Then it displays the path as “/home/olpc"
  3. Enter command ‘cd .sugar/default/logs’ and press "enter"

But in this folder "org.laptop.AbiWordActivity-1.log" is not available

Since the file is not available there I followed another way as below,

  1. Go to home page
  2. Click on the activity "Log" and searched the file "org.laptop.AbiWordActivity-1.log”.

But in there also it is not available

It is pleasure if you can tell any other way to get the log

Replying to sascha_silbe:

Replying to hiruni:

When user tries to open the ‘Write Activity’ by clicking on the icon, the screen displays that the activity is loading but it is not loading the activity.

Unfortunately up to (but not including) the very latest release of Sugar (0.88), that's what happens when an activity fails to start. No matter how fast it fails, it will always shows the pulsing screen for a long time. See #1447 for details.

As for Write on OS802B5, can you attach the Write log file (~/.sugar/default/logs/org.laptop.AbiWordActivity-1.log), please?

comment:3 in reply to: ↑ 2 ; follow-up: Changed 10 years ago by sascha_silbe

Replying to hiruni:

Although the Write log file (~/.sugar/default/logs/org.laptop.AbiWordActivity-1.log) is searched as you told to attach, it is not available in the XO.

Thanks for trying! Have you started Write right before looking for the log file? ~/.sugar/default/logs only contains the logs of the current session. For older files (up to 4 old sessions are kept) you need to check the subdirectories with a large number as names. The number represents time, so the one with the largest number is contains the logs of the most recent (but not current) session.
The following command should help you locate the file:

ls ~/.sugar/default/logs/*/org.laptop.AbiWordActivity-1.log

If even after trying to start Write again there is no such log file to be found, can you please do both of the following?

  1. Attach ~/.sugar/default/logs/shell.log
  2. Paste the output of:
ls ~/.sugar/default/logs

comment:4 in reply to: ↑ 3 ; follow-up: Changed 10 years ago by hiruni

Replying to sascha_silbe:

Replying to hiruni:

Although the Write log file (~/.sugar/default/logs/org.laptop.AbiWordActivity-1.log) is searched as you told to attach, it is not available in the XO.

Thanks for trying! Have you started Write right before looking for the log file? ~/.sugar/default/logs only contains the logs of the current session. For older files (up to 4 old sessions are kept) you need to check the subdirectories with a large number as names. The number represents time, so the one with the largest number is contains the logs of the most recent (but not current) session.
The following command should help you locate the file:

ls ~/.sugar/default/logs/*/org.laptop.AbiWordActivity-1.log

If even after trying to start Write again there is no such log file to be found, can you please do both of the following?

  1. Attach ~/.sugar/default/logs/shell.log
  2. Paste the output of:
ls ~/.sugar/default/logs

As you told we put the "ls ~/.sugar/default/logs/*/org.laptop.AbiWordActivity-1.log" command in terminal and try to find that log file.It is pleasure to say that we found it.May I know do we need to attach that file??

comment:5 in reply to: ↑ 4 ; follow-up: Changed 10 years ago by sascha_silbe

Replying to hiruni:

As you told we put the "ls ~/.sugar/default/logs/*/org.laptop.AbiWordActivity-1.log" command in terminal and try to find that log file.It is pleasure to say that we found it.May I know do we need to attach that file??

Yes, please attach it to this bug (there's an "Attach File" button right after your initial bug description).

Changed 10 years ago by hiruni

comment:6 in reply to: ↑ 5 Changed 10 years ago by hiruni

Replying to sascha_silbe:

Replying to hiruni:

As you told we put the "ls ~/.sugar/default/logs/*/org.laptop.AbiWordActivity-1.log" command in terminal and try to find that log file.It is pleasure to say that we found it.May I know do we need to attach that file??

Yes, please attach it to this bug (there's an "Attach File" button right after your initial bug description).

Here I attached the log file you asked.Please let me know if have any concerns

comment:7 Changed 10 years ago by cjl

Duplicate of #1878? Both tickets have good info, so not closing either, but they should probably be closed together when resolved.

comment:8 Changed 10 years ago by cjl

See also #1375 (from earlier jhbuild, log attached)

comment:9 Changed 9 years ago by RafaelOrtiz

  • Resolution set to duplicate
  • Status changed from new to closed

This is a dup of #1878

Note: See TracTickets for help on using tickets.