[gutsy] openoffice writer crashes when selecting a graphic in a document imported from Word.

[Veloce]

Binary package hint: openoffice.org

In a document created in Word with a picture in a frame within the header, when attempting to select the graphic open office writer ceases to respond and has to be force quit.

It does not appear to be using the CPU (or any other resource that I can see.)

I have created another file with the same characteristics and reproduced the problem.

I can supply this file - not sure how to attach it to this bug report.

[Koen (koen-beek)]

Hi,

  I tried on my gutsy system but had no problems

  can you try to start open office writer from a terminal console and see whether any message is output ?
  you can start it by using the following command : ooffice -writer open_office_error.doc

  if any error messages are output please attach them to the bug

   thanks,

     Koen

[Veloce (kerry-mayes)]

Attached is all the output to the terminal. For some reason it just stops half way through a line.

Interestingly (?) about half the time starting open office from a terminal had open office crash in a way that was handled (i.e. it said "unexpected error" and closed.) rather than the usual freeze.

[Koen (koen-beek)]

Hi,

  this bug looks like bug https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/131526

  can you try what they suggest to see whether it's the same (change your theme to Human and maybe also set visual effects to no (System->Preferences->Appearance))

    thanks,

       Koen

[Koen (koen-beek)]

Hi,

  I've been able to reproduce the problem by selecting the Cruz theme in stead of the Human theme

  So it is the same open office bug as 131526 and it should be corrected in OO-2.3.1 will fix the bug; see http://www.openoffice.org/issues/show_bug.cgi?id=82608

  In the meantime I suggest you use AbiWord or the Human theme (or any other theme that does not have this problem)

  Koen

[Veloce (kerry-mayes)]

Excellent. Using the Human theme solves the problem.

I had seen that bug but hadn't connected it with this behaviour because the symptoms are so different.

Thanks!