[Bugs] #4662 Write URGE: No changes are saved in Write 94 on Fedora 20 TC2

[Sugar Labs Bugs]

#4662: No changes are saved in Write 94 on Fedora 20 TC2
--------------------------+-------------------------------
  Reporter:  inkyfingers  |            Owner:  godiard
      Type:  defect       |           Status:  assigned
  Priority:  Urgent       |        Milestone:  Unspecified
 Component:  Write        |          Version:  0.98.x
  Severity:  Critical     |       Resolution:
  Keywords:               |  Distribution/OS:  Fedora
Bug Status:  New          |
--------------------------+-------------------------------
\
\
\
\
\
\

Comment (by inkyfingers):

 == Updated summary ==

 Write (updated by git clone) is usable in .rtf mode with care on yum-
 updated SoaS.
 Using Write in the default .odt mode is less successful.
 Performance has improved since original bug report, but variable
 performance is seen.

 == Current testing environment ==

 FedoraLiveSoaS-i686-20.1 hard drive install with liveinst. (Now, no xfce,
 no sugar-runner.)

 Write git cloned as of 3 June 2014 (ie > v.94),
 Fedora 20 environment yum updated, 14 June 2014,
 including sugar.repo updated with
 http://copr.fedoraproject.org/coprs/dnarvaez/sugar/repo/fedora-20-i386,
 (Tests of Write have been with Write the only Activity running.)

 == Testing ==

 See a sequence of six tests attached:
 `16-06-2014_AbiWordActivity_x6-tests`, and the six log files.

 == Generalized Performance Report ==

 Write usually starts,  - ok.

 Activity tab, rename_file field can be edited - ok.

 Tab will generally move cursor from Activity tab, rename_file field into
 the document - ok.

 Text can be entered on document - ok.

 Write does not consistently meet the expectation that on pressing the Stop
 button, Write will close, and work in progress can be resumed from
 Journal. Fail.

 Pressing the Stop button causes the cursor to "run timer" for a second or
 two, then close, visually appropriately.

 Write closes, but Resume mostly (not always) opens a blank page, mostly in
 the created filename.

 A document can be exported as .rtf (or .html or .txt), but expect the
 original file to fail to resume.

 Open the exported .rtf file and edit it - ok.

 Now, Stop, Journal entry, and resume work satisfactorily, work can now
 proceed reliably with this file - ok.

 It seems, Write can work successfully with .txt, .rtf, .html files,  but
 .odt files are harder to succeed.

 The ability to generate an .odt is not a total fail. Sometimes .odt
 documents are saved and resumed. Re-opened .odt documents might then be
 lost on a subsequent close. Both behaviors are seen in the test sequence
 attached `16-06-2014_AbiWordActivity_x6tests`.

 == Fails ==

 Exporting any document as .pdf causes Write to collapse.

 Use Speak to read aloud text in a Write document causes Write to collapse.

 == Intermittent ==

 It has continued to be intermittent whether an empty (that is, lost)
 "Write Activity" is seen in the Journal.

 The "resistance" to putting the cursor in the Activity tab, rename_file
 field is less noticeable than at time of original bug report.

 == Sound ==

 Characteristic sound is generated by the backspace key reaching
 start_of_line.
 Sound, in general, is working in SoaS.

 == Collaboration ==

 Write sometimes opens with the sharing icon greyed out, but not every
 time.
 A similar thing is now seen in Chat. I relate this to intermittent
 collaboration availability, but it is not fully consistent with whether
 other_user avatars are visible in F1 View.
 Activities open for sharing commonly do not throw an icon into the F1 View
 on my SoaS.
 I do not have hardware to test collaboration in a local mesh.
 I have the impression that, on days when the sharing icon is greyed out,
 Write may perform better.
 I avoid opening the Sugar 0.100.0 session to collaboration, as I think
 this would increase the over-sensitivity of Write.

 == Speculation ==

 This inexact behavior may be consistent with bugs ... unresolved
 collaboration issues, ... or unresolved sound issues hogging resources.
\
\
\

--
Ticket URL: <http://bugs.sugarlabs.org/ticket/4662#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system