[upstream] OOo crashes while spellchecking protected cells

Thanks for your bug report. In order to help gathering necessary information to reproduce and fix that bug, can you provide these informations? :

1. Are you able to reproduce this bug?
2. If you can reproduce this bug, can you attach a document that cause the problems in the same circumstances that you described previously?
3. Can you say which version of openoffice you are using? You can know this by typing this in a terminal : apt-cache policy openoffice.org
4. Can you say which version of ubuntu you are using? Feitsy/Gutsy/Hardy?

Thanks for your contribution

Thank you for your email.

In answer to your queries :-

   The spread sheet I compiled was a name and address sheet. I have
managed to replicate the situation by merely typing the first two
columns of text ( I hope you don't mind me not including the other
details which were addresses, phone numbers etc.) I then selected the
whole sheet (by clicking on the the top left hand corner) and selected
'protect sheet' I then selected 'spell check' and the error message came
up saying something to the effect that the sheet was protected. At that
point the programme crashed and I needed to reboot the PC. When the PC
was running again the programme recovered the spreadsheet for me.
What I then did was to create another spread sheet, Identical to the
one I've just mentioned, and took it to the point where I had
protected it but did not use the spell checker.
This sheet is attached under the name 'Crash'

 Details of the version of Open Office are attached under the name 'version'
The version of Abuntu is 'gutsy'

I hope this will be of use to you

Regards,

Geoff Bennett

Saïvann Carignan wrote:
> Thanks for your bug report. In order to help gathering necessary
> information to reproduce and fix that bug, can you provide these
> informations? :
>
> 1. Are you able to reproduce this bug?
> 2. If you can reproduce this bug, can you attach a document that cause the problems in the same circumstances that you described previously?
> 3. Can you say which version of openoffice you are using? You can know this by typing this in a terminal : apt-cache policy openoffice.org
> 4. Can you say which version of ubuntu you are using? Feitsy/Gutsy/Hardy?
>
> Thanks for your contribution
>
> ** Changed in: openoffice.org (Ubuntu)
> Assignee: (unassigned) => Saïvann Carignan (saivann)
> Status: New => Incomplete
>
>

Thanks for your quick and detailed answer!

Apparently, your attachments were not added to the bug report. Can you go to that link : https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/186674 and add your attachment? If you prefer, You can also send these attachments to my public adress : <email address hidden> and I will take care to add them to the bug report for you. Of course, it is important that you protect your personal informations and you may want to modify the document in order to remove anything that can be sensitive and keep in mind that the bug report is public. Thanks a lot for your contribution.

I opened the Crash.ods file, selected the whole content of the file with the top-left button and I did run spellchecker, I got the same error message against the fact that the spellchecker can't check protected sheet but I was not able to reproduce the crash or any other serious problem. Are you able to reproduce the computer crash with the Crash.ods spreadsheet that you attached to the bug report?

Thank you for your email.

Yes, my copy of the file will crash. If I don't select at least the
cells containing text then it will not crash.
I have also just created another spreadsheet with a column of random
words and after protecting it and selecting the cells containing text,
this will also crash when I use the spell checker. (Whether or not I use
the data-sort facility doesn't make any difference.)
Does this mean that this is just a problem with my own operating system
? If this is the case I can only apologise for putting you to all this
trouble.

Regards,

Geoff Bennett

Saïvann Carignan wrote:
> I opened the Crash.ods file, selected the whole content of the file with
> the top-left button and I did run spellchecker, I got the same error
> message against the fact that the spellchecker can't check protected
> sheet but I was not able to reproduce the crash or any other serious
> problem. Are you able to reproduce the computer crash with the Crash.ods
> spreadsheet that you attached to the bug report?
>
>

Thanks for your answer. Any crash as a reason behind it and in your case, if you can reproduce the bug each time, it's clear that something can be fixed in order to resolve that issue. However, it is quite bad because the cause of your bug is hard to find since I don't see duplicate bug reports and since I can't reproduce it with the computers I have here.

Maybe that you forgot to speak about one step to reproduce the bug? Or maybe that your computer is not crashed but just slow and buggy? Any additional informations can be important and lead us to complete this bug report. You can have detailed informations concerning the active processes on your computer by typing this on a terminal without the quotes : "ps aux". If you are still able to use your system after openoffice crashed, you can use this command to look if a process use a abnormal percentage of the CPU. You can also use techniques described here : https://wiki.ubuntu.com/DebuggingProgramCrash to create debug files for openoffice which will help developers to find the cause of the bug.

I've been able to crash openoffice by clicking on the "close" button of the spellchecker. This is indeed a genuine bug which I will forward to openoffice developers but I still wonder how the computer crash can happen and why.

Thanks for your contribution so far.

Thank you for your email.

I Can still use the system after 'open office' has crashed and I have
run 'ps aux'.
I have attached a printout of the terminal although there does not
 appear to be any excessive percentage cpu activity. (Having said that I
am very
new to Ubuntu.)

I have copied the debugging information from the website and will get
back to
you as soon as I have installed the debug packages.

Regards,

Geoff Bennett

Saïvann Carignan wrote:
> Thanks for your answer. Any crash as a reason behind it and in your
> case, if you can reproduce the bug each time, it's clear that something
> can be fixed in order to resolve that issue. However, it is quite bad
> because the cause of your bug is hard to find since I don't see
> duplicate bug reports and since I can't reproduce it with the computers
> I have here.
>
> Maybe that you forgot to speak about one step to reproduce the bug? Or
> maybe that your computer is not crashed but just slow and buggy? Any
> additional informations can be important and lead us to complete this
> bug report. You can have detailed informations concerning the active
> processes on your computer by typing this on a terminal without the
> quotes : "ps aux". If you are still able to use your system after
> openoffice crashed, you can use this command to look if a process use a
> abnormal percentage of the CPU. You can also use techniques described
> here : https://wiki.ubuntu.com/DebuggingProgramCrash to create debug
> files for openoffice which will help developers to find the cause of the
> bug.
>
> I've been able to crash openoffice by clicking on the "close" button of
> the spellchecker. This is indeed a genuine bug which I will forward to
> openoffice developers but I still wonder how the computer crash can
> happen and why.
>
> Thanks for your contribution so far.
>
>

Further to my previous email, I have added the additional lines to
/etc/apt/sources.list:
and run the update but when it comes to actually using these programmes
such as 'Backtrace',
'Strace' or 'Valgrind', I'm afraid I am lost.
 Any help would be appreciated

Regards,

Geoff Bennett

Saïvann Carignan wrote:
> Thanks for your answer. Any crash as a reason behind it and in your
> case, if you can reproduce the bug each time, it's clear that something
> can be fixed in order to resolve that issue. However, it is quite bad
> because the cause of your bug is hard to find since I don't see
> duplicate bug reports and since I can't reproduce it with the computers
> I have here.
>
> Maybe that you forgot to speak about one step to reproduce the bug? Or
> maybe that your computer is not crashed but just slow and buggy? Any
> additional informations can be important and lead us to complete this
> bug report. You can have detailed informations concerning the active
> processes on your computer by typing this on a terminal without the
> quotes : "ps aux". If you are still able to use your system after
> openoffice crashed, you can use this command to look if a process use a
> abnormal percentage of the CPU. You can also use techniques described
> here : https://wiki.ubuntu.com/DebuggingProgramCrash to create debug
> files for openoffice which will help developers to find the cause of the
> bug.
>
> I've been able to crash openoffice by clicking on the "close" button of
> the spellchecker. This is indeed a genuine bug which I will forward to
> openoffice developers but I still wonder how the computer crash can
> happen and why.
>
> Thanks for your contribution so far.
>
>

Thanks for your efforts on this but since I can now reproduce the bug ( by clicking on the "close" button ) and that I see that in the same circumstances you described, a huge number of openoffice windows are opening, this can easily lead openoffice to crash some GNOME processes so it seems pretty clear that we've got sufficient informations. I will take care to create the backtrace and to forward it upstream so openoffice developers look at it and fixes that bug.

The time you took to give all needed informations and details for this bug is really appreciated. Thanks for your contribution.

I will change the description of the bug to be more descriptive.

Confirmed to still exist on upstream's openoffice.org 2.4.0~rc2.

And still exist on 3.0.1

Geoff Bennett, this issue is unreproducible in LibreOffice Calc via the Terminal:

wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/186674/+attachment/198005/+files/Crash.ods && localc -nologo Crash.ods

Ctrl+A -> Tools and notice spelling is grayed out. Does that work for you?

lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1:3.3.2-1ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

Thank you for your e-mail.

I have tried creating the sample spread sheet in Libre Office Calc and
cannot make it reproduce the problem. When protection is applied to the
sheet, tools-Spellcheck and Format-Cells is greyed out, without sheet
protection spellcheck works fine.

Regards,

Geoff Bennett

On 18/05/11 03:51, Christopher M. Penalver wrote:
> Geoff Bennett, this issue is unreproducible in LibreOffice Calc via the
> Terminal:
>
> wget
> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/186674/+attachment/198005/+files/Crash.ods
> && localc -nologo Crash.ods
>
> Ctrl+A -> Tools and notice spelling is grayed out. Does that work for
> you?
>
> lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> apt-cache policy libreoffice-writer
> libreoffice-writer:
> Installed: 1:3.3.2-1ubuntu5
> Candidate: 1:3.3.2-1ubuntu5
> Version table:
> *** 1:3.3.2-1ubuntu5 0
> 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages
> 100 /var/lib/dpkg/status
> 1:3.3.2-1ubuntu4 0
> 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
>
> ** Also affects: libreoffice (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Incomplete
>

Geoff Bennett, regarding OpenOffice, your crash report is missing. If you continue to have this problem, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.