[ooo-build] [i386] OpenOffice crashes when saving .doc file with "notes" in it, Karmic.

Bug #457220 reported by billjoie
228
This bug affects 43 people
Affects Status Importance Assigned to Milestone
OpenOffice
Fix Released
Critical
Baltix
Invalid
Undecided
Unassigned
openoffice.org (Ubuntu)
Fix Released
High
Chris Cheney
Nominated for Karmic by Arise

Bug Description

Binary package hint: openoffice.org

Everything was working in Ubuntu 9.04, but since fresh install of Ubuntu 9.10 beta, OpenOffice crashes if saving a MS doc files that contain "notes". Saving doc files without notes works just fine. Saving an odt file with or without notes works fine. Only writer crashes, open calc spreadsheets remain open. Have been updating meticulously.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 9607560fff7b67db547922fbab66dc1c
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
Date: Wed Oct 21 15:51:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
Package: openoffice.org-core 1:3.1.1-4ubuntu2
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: openoffice.org
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
billjoie (joie-bill) wrote :
summary: - OpenOffice crashes when saving .doc file with "notes" in it
+ OpenOffice crashes when saving .doc file with "notes" in it, Karmic
+ beta.
Revision history for this message
Chris Cheney (ccheney) wrote : Re: OpenOffice crashes when saving .doc file with "notes" in it, Karmic beta.

Does this still happen if you remove the openoffice.org-kde package?

Changed in openoffice.org (Ubuntu):
status: New → Incomplete
Revision history for this message
billjoie (joie-bill) wrote :

I do not have openoffice.org-kde installed. Here is a list of what appears when I have installed with "openoffice.org*" according to apt-get. Let me know if I can provide any additional info.

openoffice.org-base-core
openoffice.org-draw
openoffice.org-help-en-us
openoffice.org-math
openoffice.org-writer
openoffice.org-calc
openoffice.org-emailmerge
openoffice.org-hyphenation
openoffice.org-style-human
openoffice.org-common
openoffice.org-gnome
openoffice.org-hyphenation-en-us
openoffice.org-thesaurus-en-au
openoffice.org-core
openoffice.org-gtk
openoffice.org-impress
openoffice.org-thesaurus-en-us

Chris Cheney (ccheney)
Changed in openoffice.org (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
billjoie (joie-bill) wrote :

Purged all packages and re-installed all openoffice.org* packages. Removed .openoffice.org folder to rule out any local modification. After reinstall, removed openoffice.org-gnome and openoffice.org-gtk...and it still does it!

Revision history for this message
billjoie (joie-bill) wrote :

Bounce. Am I the only one affected by this bug? Is there any information I can provide to further help the diagnostic? Two days before the official release of Karmic Koala, all my updates done, and I still cannot save notes in *.doc files.

Revision history for this message
Chris Cheney (ccheney) wrote :

After updating my system to Karmic and running OOo 1:3.1.1-5ubuntu1 I can not reproduce this issue. I am able to save to Microsoft Word 97/2000/XP format just fine with notes attached.

Changed in openoffice.org (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Geriborg (dion-dennis) wrote :

I'm having the same problem as billjoie, except that this emerged ONLY with the final release. I did not have this problem, earlier on. I've uninstalled, reinstalled, purged, etc., it is as Billjoie says. In fact, I've had to move over to Windows XP to use OpenOffice 3.1.1. on that platform, for the commenting on essays that I routinely do.

Revision history for this message
billjoie (joie-bill) wrote :

Hi Geriborg, In the end, what I had to do was:
1) purge Openoffice and any program having anything to do with openoffice, delete local directory configurations ,etc.
2) Make sure you reinstall java properly
3) Download the installation zip file from the openoffice.org website, and decompress it with file-roller
4) From the DEB directory, install all deb files with "sudo dpkg -i *deb" (I know this is not the most prudent move in the world)
5) Move to the subdirectory to install the "desktop integration", still with "sudo dpkg -i *deb"
...now it works very smoothly. No need to go back to Windows...misery! I really hope someone can understand what is happening, though. If any system configuration info is required to solve this issue, please let me know.

Revision history for this message
Yahya (yahya-hamidaddin) wrote :

I have the same problem in Karmic official version (upgraded from Jaunty). To reprocude:
1- Create a new document in openoffice.
2- Insert a new note (Ctrl+Alt+N)
3- Write "abc"
4- Press save as MS Word 97/2000/XP

It consistently caches for me.

I don't recall having this problem in Jaunty.

Revision history for this message
altima (timashkov) wrote :

the same with me on Gnome.

Revision history for this message
altima (timashkov) wrote :

when I try to save a document with at least on "Note", it crashes, the file being not saved.

Revision history for this message
indrek (indrek-seppo) wrote :

Same here with final karmic (kubuntu, updated from jaunty).

It is a real PITA for me at the moment (have to go through a lot of students papers and add comments to them).

If this is not some rare issue then it is a major showstopper for a lot of people.

Is there any additional information I can give?

Revision history for this message
arne (arne-shadowweb) wrote :

Same here with final karmic (kubuntu, updated from jaunty).

I used the same document as .doc and .odt on jaunty with no problems.

When I remove the comments from the document I can save to .doc format. But when I close the .doc file then OOo still crashes, but with now harm to any file.

Revision history for this message
Arise (northwood) wrote :

In Karmic, with all the updates installed, Openoffice still crashes on saving documents (with notes in) to *.doc (tested on 3 machines, one of which has a clean install of Karmic).

Revision history for this message
Larry Tate (cathect) wrote :

I can confirm this behavior too. After crash, all notes are lost upon file recovery. Like Indrek, I am trying to comment on student essays and this as become a HUGE problem for me as I teach distance education...

I think this is a pretty critical bug.

Revision history for this message
Larry Tate (cathect) wrote :

I should add that I am not running the Beta...but the release of 9.10.

Revision history for this message
Arise (northwood) wrote :

It's a huge trouble really. Confirmed on 9.10 release. Is there any workaround at least?

billjoie (joie-bill)
Changed in openoffice.org (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
billjoie (joie-bill) wrote :

Hi Arise,
Yes there is a work around, that is what my post of the 1st of November was about. First you totally remove openoffice from your computer, then you install java (if not already there). Then you download the program (deb files) from the openoffice.org website, and install them with dpkg. It worked for me, openoffice works flawlessly. If these instructions (combined with previous post) are not clear enough, don't hesitate to ask.

Revision history for this message
Arise (northwood) wrote :

Hi billjoie,
Thanx for trying to help! Actually, the idea of removing Ubuntu's built-in "Go-oo" (Novell's) and installing something else came first of all. Well, installing SUN's binaries might help, but for one little thing: SUN's builds suck, they have performance and usability issues (oh I remember that ugly "scale" pop-up dialog in OpenOffice.org 2.x). I ended up installing Infraresourse OpenOffice 3.1.1 build from third-party repo (Infraresourse is a russian company that distributes its own OpenOffice build, stuffed with some Russia-specific improvements; *.deb binaries are found here http://bouncer.i-rs.ru/?product=OpenOffice.org&lang=ru&version=3.1.1&os=linuxinteldeb ). Well, Openoffice quit crushing every now and than, but it's a "crutch" anyway and it's a big hustle if you have more than one ubuntu-powered computer. So I wondered if there's any possibillity to get naitive Ubuntu's "Go-oo" working, as it outperforms all the competitors (it's noticeable on my hardware at least).

Sorry for my clumsy English

Revision history for this message
Larry Tate (cathect) wrote :

BilliJoe,

I removed ALL Open Office packages w/ Synaptic and installed the Sun .debs. The install went fine but it still crashes when using a .doc file.

Revision history for this message
Arise (northwood) wrote :

There are some additional packages not containing "OpenOffice.org" in their names but still related to OpenOffice, one of them causes all the mess. Though I can't figure out which one is that "bad guy".

billjoie (joie-bill)
summary: - OpenOffice crashes when saving .doc file with "notes" in it, Karmic
- beta.
+ OpenOffice crashes when saving .doc file with "notes" in it, Karmic.
Revision history for this message
Ian Anderson (iancarol) wrote : Re: OpenOffice crashes when saving .doc file with "notes" in it, Karmic.

For information

I have a brand new installation of Karmic 9.10 with OOo built and all up to date. Never been touched before.
I wanted to move from Word. I can open and edit word documents , but the OOo spell checker is not functioning, and any attempts to use the options menu in OOo produce crashes at diffferent points with a frozen Ubuntu and mouse movement only. The effect is an unusable OOo at the moment.

Will remove and try re install though Ubuntu Software Centre before attempting the above recommendations

Revision history for this message
Ian Anderson (iancarol) wrote :

Further to my last post I can confirm that I have carried out the above thread instructions removed all packages via Synaptic uninstaller and also via the terminal by sudo apt-get remove purge open office.org followed up by sudo apt-get autoremove (as prompted) which removed some other stuff. (Software Centre Uninstall ineffective)

Then obtained the Linux deb version from Open Office Org web site using the Get More Platforms line and selecting in my case 32 bit version Ubuntu & Deb English US
this file is OOo_3.1.1_LinuxIntel_install_en-US_deb.tar.gz Placed in the home folder
then via the terminal extracted with this command tar -vxzf OOo_3.1.1_LinuxIntel_install_en-US_deb.tar.gz
this creates a new folder in the home folder called 000310_m19_native_packed-1_en-US.9420 (hidden folder)
then cd debs to change to the sub folder inside it
then sudo dpkg -i *.deb which completes the installation
any attempt to fiddle with menus after this is declined (mentioned in tutorials elsewhere for earlier version of OOo)
I can now open Writer with resultant more time between crashes, but still no working Spelling checker.
This post is not totally related to the above thread except that I think there must be a large bug preventing Karmic and Open Office working together. Reluctantly I'm returning to Microsoft Word until it is sorted out.
I'm a Linux beginner but also a working person who needs a working word processor.

Revision history for this message
Chris Cheney (ccheney) wrote :

Has anyone who experienced this bug been running on something other than i386? The system I am testing on that can't reproduce this bug is amd64 so that might be why. I will try to get a i386 disc to test with to see if that is the issue.

Revision history for this message
billjoie (joie-bill) wrote :

Hi Chris,
I use i386.

Revision history for this message
Roberto A. Foglietta (robang74) wrote :

Hi, I have reported the same bug to openoffice bug-tracker but after carefully checks they closed it because does not apply to the build downloadable from their site. It happens in other UNIX OS but not in all UNIX OS. Bug report could be read by the following link, please take a look:

http://www.openoffice.org/issues/show_bug.cgi?id=106951

Revision history for this message
aizquier (aizquier) wrote :

I could reproduce this bug using a fresh installation of ubuntu 9.10 on a virtual machine (vBox). Windows version of OpenOffice 3.1.1 do not seem to present the bug.

Revision history for this message
gloonie (gloonie) wrote :

I confirm that I have the same problem crashing with notes inserted in a document. I am running kubuntu 9.10 with the latest updates. I have OpenOffice 3.1.1 OOO310m19 (Build 9420).

Everything works fine if I remove the "notes" and then save.

This is a very critical problem, since I constantly work with documents passed on to windows users..

Revision history for this message
aizquier (aizquier) wrote :

I confirm that uninstalling the Ubuntu version of OpenOffice 3.1.1 and installing the native version from Openoffice.org the problem is gone. However, for those who prefer to wait until this bug is fixed in the Ubuntu repositories, and do not want to install non-ubuntu packages, BUT are in a *hurry* that requires a rapid but temporary solution, I found that the portable version of OpenOffice (for windows) seems to works well using wine, this version can be easily disposed afterwards. It can be found at:

http://portableapps.com/apps/office/openoffice_portable

Revision history for this message
gloonie (gloonie) wrote :

A bit more information: I found that when I opened a MS Word document with Comments already in the document, Ooo worked with no problems or crashes.

 It seems to crash for me only when I try to save an odt document with notes to a file in MS Word format.

Revision history for this message
dtower (dustintower) wrote :

I have the same problem, and I completely removed everything related to Open Office in Synaptic. I then did a fresh install from Open Office.org. After I navigate to the folder that was extracted, and use "sudo dpkg -i *deb" to try to install it, I got:

dpkg: error processing *deb (--install):
 cannot access archive: No such file or directory
Errors were encountered while processing:
 *deb

I'm also in a critical problem and have a large load of student papers that need comments.
Can anyone help with this?

Thanks!

Revision history for this message
dtower (dustintower) wrote :

Sorry, I just realized I had to navigate one folder deeper. I now have the version from Open Office installed, but it crashes on startup each and every time now. This is a serious problem for me.

Revision history for this message
billjoie (joie-bill) wrote :

Sorry you are having a bad Ubuntu experience there. When exactly does OpenOffice crash (introduction screen, after, etc.)? Did you install the desktop integration that is in the subdirectory? Do you have java installed? Did you get any error message during installation?

Revision history for this message
dtower (dustintower) wrote :

Open Office crashes on the introduction screen when I attempt to open "writer". I have been able to open other types of documents "draw" or "impress" and then open a text document from "File --> New --> Text Document". I was then able to open a file and save it in .doc format without crashing! I was then able to make changes and add notes to a file without saving it. This is great news so far, and thanks for the suggestions above.

I did a search in Synaptic, and it looks as if I do have sun-java6-jre, sun-java5-jre, and "default-jre-headless" all installed. Would deleting one of these solve my problem (which is still a problem, but not as severe as before).

I didn't get any error message on installation that I'm aware of.

Thanks!

Revision history for this message
dtower (dustintower) wrote :

correction to the last post: the second-to-last sentence of the first paragraph should say, "I was then able to...and add notes without *it crashing when* saving it." (a significant difference)

Revision history for this message
dtower (dustintower) wrote :

Sorry, thanks so much for your help. My problem is solved now. I hadn't installed the desktop integration in the sub-directory. Not it all opens beautifully. Thanks again.

Revision history for this message
dtower (dustintower) wrote :

Ugh. My problem is NOT solved. Now it is crashing again after a reboot. Can this be a java version problem? What do I need to do? Thanks

Revision history for this message
Doug Holton (edtechdev) wrote :

I just ran across this bug at the worst time - trying to grade draft papers (by inserting notes), I have to revert to Jaunty so that I can get through this

To reproduce: open .doc file, insert note (control-alt-note), type note, save....crash.

Some documents can't even be recovered with the note(s).

Revision history for this message
Doug Holton (edtechdev) wrote :

I uninstalled ooo and tried the openoffice 3.1 from openoffice.org site and it crashed on launch when trying to open a .doc file.

I uninstalled that, deleted the .openoffice folder and re-installed the ubuntu ooo package, and now openoffice has a windows 98 look & feel.

But, it doesn't crash when loading or saving a .doc file, with or without notes.

Changed in openoffice:
status: Unknown → Invalid
Revision history for this message
Doug Holton (edtechdev) wrote :

The crashing on save started occuring again. It crashes on .doc files for which I've inserted a note.

Changed in openoffice:
importance: Unknown → Undecided
status: Invalid → New
Changed in openoffice.org (Ubuntu):
assignee: nobody → Chris Cheney (ccheney)
importance: Undecided → High
Chris Cheney (ccheney)
summary: - OpenOffice crashes when saving .doc file with "notes" in it, Karmic.
+ [i386] OpenOffice crashes when saving .doc file with "notes" in it,
+ Karmic.
Chris Cheney (ccheney)
summary: - [i386] OpenOffice crashes when saving .doc file with "notes" in it,
- Karmic.
+ [ooo-build] [i386] OpenOffice crashes when saving .doc file with "notes"
+ in it, Karmic.
Changed in openoffice.org (Ubuntu):
status: Confirmed → Triaged
Chris Cheney (ccheney)
Changed in openoffice:
importance: Undecided → Unknown
status: New → Unknown
Changed in openoffice:
status: Unknown → Confirmed
Changed in openoffice:
status: Confirmed → Incomplete
Changed in openoffice:
status: Incomplete → Confirmed
Changed in openoffice:
status: Confirmed → Incomplete
30 comments hidden view all 110 comments
Revision history for this message
ushlonsky (ushlonsky) wrote :

This bug is particularly bothersome. I grade and comment student papers by using OO's notes functions and now is grading time!!
What I do to get aound the problem, is save everything in odt.hen use zamzar.com to covert to .doc and then maio the file to the students.

Revision history for this message
Doug Holton (edtechdev) wrote :

Novell isn't even acknowledging the bug exists, and this bug report is tied to them now.

I'm back in Jaunty now, it's the only permanent solution.

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

@Doug
> Novell isn't even acknowledging the bug exists, and this bug report is tied to them now.
If you read the upstream bug report, you'll see that the openSUSE developers are working to fix this, they just need some more info on the source of the problem, that's why it is marked incomplete upstream. If you want to help fix this, help out with the upstream bug.

Revision history for this message
kennedy (ralphkennedy) wrote : Re: [Bug 457220] Re: [ooo-build] [i386] OpenOffice crashes when saving .doc file with "notes" in it, Karmic.

I've installed 64-bit Ubuntu 9.10 and can confirm Chris Cheney's earlier
observation that the bug appears not to be reproducible there. For
whatever that's worth....

Gabe Gorelick wrote:
> @Doug
>
>> Novell isn't even acknowledging the bug exists, and this bug report is tied to them now.
>>
> If you read the upstream bug report, you'll see that the openSUSE developers are working to fix this, they just need some more info on the source of the problem, that's why it is marked incomplete upstream. If you want to help fix this, help out with the upstream bug.
>
>

Revision history for this message
Emerson (martinseac) wrote :

Oh, God... Ubuntu developers doesn't have to communicate with ms word users? More that 50 days and nothing happens?
And I cant use Sun's .deb because I have to install bibus, that uses python uno and I cant make it communicates with openoffice. Please, pay attention to this bug!

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

Right now, the upstream bug is waiting on someone to make sure this bug still exists in the current code. If people want to help get this bug solved, grab the latest upstream build and report back upstream whether this bug still exists.

Revision history for this message
Emerson (martinseac) wrote :

Sorry about my ignorance, but how can I get upstream build? Any kind of repo to put on sources.list? Or there is .deb packages to download? I can test this because I have some files to be converted to .doc

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

Kohei, could you be a bit more specific (for those of us who are not Chris ;-) ) about what you mean with the latest build...?
I cloned the git repository and switched to the 3.1.1 branch following this description: http://www.freedesktop.org/wiki/Software/ooo-build/GettingIt
It seems that this gives exactly the same build number as the one packaged by ubuntu (ooo310m19, build: 9420).
After configure (--with-distro=UbuntuKarmic --disable-kde --disable-kde4 ), download and make I'm ending up with an Openoffice that shows the initially reported bug, i.e. crashes.

As a sidenote: I tried the OpenSuse 11.2 Gnome Live CD, which seems to have ooo310m21, build 9319 -- and I *don't* see the crash. I'm not sure about the numbering scheme (why m21 instead of m19 but lower build No.?), but this seems to be an *older* version, right?

If you need anything else, I'd be happy to do some more bug triaging.

Revision history for this message
In , Tlillqvist (tlillqvist) wrote :

The "build number" has a misleading name and is more or less redundant and meaningless to end-users. It has a one-to-one equivalence with "milestone tags" like ooo310m19. (Each released upstream source version, like 3.1.1, is equivalent to a "milestone tag" and thus also "build number". Yes, three ways to say the same thing!)

The build number is the same regardless of what set of patches has been applied. On OOo builds in Linux distros you should tell what version numbers the package management uses.

I would suggest we in ooo-build would remove the "build number" from the Help:About dialog...?

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

Thanks for clearing this up a bit (although, both Ubuntu and OpenSuse say they ship 3.1.1., but Ubuntu calls it ooo310m19 and OpenSuse ooo310m21) - is the OpenSuse version than newer than the Ubuntu version? But then why does the git version give me ooo310m19 like Ubuntu?
Anyway, for the record: the versioning info in ubuntu is 3.1.1-5ubuntu1.

Revision history for this message
In , Tlillqvist (tlillqvist) wrote :

> Ubuntu calls it ooo310m19 and OpenSuse ooo310m21

Yeah, that is some minor bug in the openSUSE build of OOo; even the 3.2 pre-builds talk about "OOO320m21 (Build:9319)" in the Help:About dialog.

Revision history for this message
In , Kyoshida (kyoshida) wrote :

BTW,(In reply to comment #8)
> Kohei, could you be a bit more specific (for those of us who are not Chris ;-)
> ) about what you mean with the latest build...?
> I cloned the git repository and switched to the 3.1.1 branch following this
> description: http://www.freedesktop.org/wiki/Software/ooo-build/GettingIt
> It seems that this gives exactly the same build number as the one packaged by
> ubuntu (ooo310m19, build: 9420).

Yup, that's what I mean by the 'latest build'. When someone says latest build, that normally means the latest development build, fresh from the git repository.

> After configure (--with-distro=UbuntuKarmic --disable-kde --disable-kde4 ),
> download and make I'm ending up with an Openoffice that shows the initially
> reported bug, i.e. crashes.

So, this eliminates the possibility that the problem was resolved in the latest build. This also hints strongly that the problem lies in somewhere in the distro-config difference.

Marcel, could you try rebuilding it with the '--without-stlport' build option? I've observed from my past experience that, many crash problems that occur on Ubuntu (or Debian) but do not occur on openSUSE were attributed to what appears to be a bug in the stlport itself. We do build ours without stlport for the openSUSE distro, so if you could try that, and see if that makes any difference, we will know where the problem likely is.

> As a sidenote: I tried the OpenSuse 11.2 Gnome Live CD, which seems to have
> ooo310m21, build 9319 -- and I *don't* see the crash. I'm not sure about the
> numbering scheme (why m21 instead of m19 but lower build No.?), but this seems
> to be an *older* version, right?

I'm not 100% sure, but I *think* m21 was used for 3.1, and m19 for 3.1.1. Now, I have no clue why we went backward in the milestone number when going from 3.1 to 3.1.1, but our 3.1.1 build AFAIK is based on ooo310-m19.

> If you need anything else, I'd be happy to do some more bug triaging.

Please try a new build with --without-stlport option to see if that makes any difference if it's not too much trouble. Also, the backtrace in launchpad suggests that the crash occurs in

WW8_SdrAttrIter::OutParaAttr ()

but it would help us if you could somehow find out exactly on which line the crash occurs. Thanks!

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

> Yup, that's what I mean by the 'latest build'. When someone says latest build,
> that normally means the latest development build, fresh from the git
> repository.
thanks, that's what I thought. I was just confused by the "build number" in the about dialog and thought that the ubuntu one might already be the latest build...

> Marcel, could you try rebuilding it with the '--without-stlport' build option?
When using ./configure --without-stlport I get
  configure: WARNING: unrecognized options: --without-stlport
and ./configure --help also does not show such an option - does it work anyway?

> I'm not 100% sure, but I *think* m21 was used for 3.1, and m19 for 3.1.1. Now,
> I have no clue why we went backward in the milestone number when going from 3.1
> to 3.1.1, but our 3.1.1 build AFAIK is based on ooo310-m19.
ok, thank you (and Tor) for the explanation - I guess I'll ignore those numbers from now on ;-)

Revision history for this message
In , Kyoshida (kyoshida) wrote :

(In reply to comment #13)

> When using ./configure --without-stlport I get
> configure: WARNING: unrecognized options: --without-stlport
> and ./configure --help also does not show such an option - does it work anyway?

Yes. It's a configure option for the upstream part of the build. If you look into build/ooo320-m19/ there is another configure script there. That one should understand --without-stlport option.

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

Unfortunately, with --without-stlport (after make clean) I get a strange build error:

dmake: Error: -- `data/home/mst/programming/ooo-build/build/ooo310-m19/i18npool/source/collator/data' not found, and can't be made

ERROR: Error 65280 occurred while making /home/mst/programming/ooo-build/build/ooo310-m19/i18npool/source/collator
make: *** [stamp/build] Error 1

Note the strange path "data/home/mst/..." instead of "/home/mst/..."
Any suggestions?

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

Forget about comment#15, that was a totally unrelated issue (possibly connected to using zsh instead of bash) - but I built it now with --without-stlport and it still crashes... It might however still have something to do with the stlport version. On my system I have both libstlport4.6ldbl and libstlport5.2 installed, but only the -dev package for 5.2 -- so I guess that one is used.

Regarding the question of the line where the crash occurs: According to gdb it is
build/ooo310-m19/sw/source/filter/ww8/wrtw8esh.cxx:1137

so that means the following if statement:
               if( nSlotId && nWhich != nSlotId &&
                    0 != ( nWhich = pDstPool->GetWhich( nSlotId ) ) &&
                    nWhich != nSlotId &&
                    0 != ( pOut = aWW8AttrFnTab[ nWhich - RES_CHRATR_BEGIN ] )
                    && ( bCharAttr ? ( nWhich >= RES_CHRATR_BEGIN
                                      && nWhich < RES_TXTATR_END)
                                   : (nWhich >= RES_PARATR_BEGIN
                                      && nWhich < RES_FRMATR_END) ) )

Hope that helps...

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

it seems to be the array access for aWW8AttrFnTab, "print nWhich" in gdb gives me 3998 which does not seem to be a correct value (from my very limited knowledge of this code...)

Revision history for this message
In , Kyoshida (kyoshida) wrote :

I just compared the same function with 3.2, and someone has removed the

0 != ( pOut = aWW8AttrFnTab[ nWhich - RES_CHRATR_BEGIN ] )

part from the above if condition statement. Not sure if that's related to the crash, but just FYI.

Revision history for this message
In , Tlillqvist (tlillqvist) wrote :

The expression in the if statement in comment #16 indeed looks a bit odd. It contains

  aWW8AttrFnTab[ nWhich - RES_CHRATR_BEGIN ]

so hopefully nWhich should be >= RES_CHRATR_BEGIN otherwise that will index aWW8AttrFnTab way out of its bounds.

then a bit later in the expression it contains

  nWhich >= RES_CHRATR_BEGIN

(twice) i.e. a subexpression that one hopes should always be true (or indeed cause a crash in the array indexing earlier).

Revision history for this message
Jeremy Davis (jedmeister) wrote :

I think I am also experiencing this issue (or one with a very similar symptom). The cause seems to be different so I'm not 100% sure. For me I have been working on a .doc (that was created with Ooo3.1.1 on WinXP) and have just added a Ooo Draw drawing and on saving it crashed. It saves fine in .odt or .docx

I am using Karmic i386 with standard (latest) Ooo3.1.1 (OOO310m19-Build:9420)
[openoffice.org-core 1:3.1.1-5ubuntu1]

I too am interested in testing the upstream build but have no idea where to get it from either. Anyone help us out here?

Revision history for this message
Jeremy Davis (jedmeister) wrote :

Is this bug the same as Bug #454545 (which has been marked as "fix released" - in v3.2)?

Also even though it seems to save ok in .docx the picture is gone.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

@JedMeister: To find out, whether you're problem is the same as the one reported here, you should 1) install the -dbgsym packages for openoffice (see here: https://wiki.ubuntu.com/DebuggingProgramCrash) and 2) start openoffice under the gdb debugger like this:
  gdb /usr/lib/openoffice/program/soffice.bin
Then, in the gdb console enter
  run -writer
and reproduce the crash. If in gdb you get an output like:
  Program received signal SIGSEGV, Segmentation fault.
  0x03de0747 in WW8_SdrAttrIter::OutParaAttr () from /usr/lib/openoffice/basis3.1/program/libmswordli.so
then it is very likely the same problem. If you get the error in a different function, consider filing a new bug (ideally with a sample document triggering the bug) and possibly include a full backtrace (instructions here: https://wiki.ubuntu.com/Backtrace )

Bug #454545 is a different bug and not (at least not directly) related.

Note: The bug filed here is one that does not seem to be present when using the original openoffice.org package (from http://download.openoffice.org/index.html but be aware that these packages have other issues :-/ ), but only with the ooo-build version that is used by many linux distributions (see comment #59). The "novell-bugs #559714 " is about ooo-build. To test their newest version (like I did, see that bug) you would have to build it from sources, which takes *very* long, uses ~10GB of disk space and is not really recommendable if you're not experienced building from source.

The good news is that apparently, the crash reported here will be gone with v3.2 as well. The code that seems to trigger the crash is no longer present, because the word export filter has been reworked.

Revision history for this message
In , Kendy (kendy) wrote :

Kohei: The ugly aWW8AttrFnTab is totally gone in 3.2 - it used to be an array of callbacks, I changed them into virtual methods. The check for 0 != ( pOut = aWW8AttrFnTab[ nWhich - RES_CHRATR_BEGIN ] ) was to see if the function is a valid callback, or not.

Marcel: Please, can you test the problem also with 3.2?

Revision history for this message
In , Marcel Stimberg (marcelstimberg) wrote :

[Had some trouble building 3.2: First, the bin/unpack script failed in line 298, after replacing
        ) 200>$SRCDIR/clone/$pkg-lock
with
        ) 2>$SRCDIR/clone/$pkg-lock
it worked, however.
In the end, make install failed, due to this problem (mail thread has also the solution): http://lists.freedesktop.org/archives/ooo-build/2009-December/000438.html]

I finally managed to build 3.2, and indeed, the problem seems to be gone, i.e. I can create a doc with a note and save it in the doc format without crash :-)

[BTW, removing NEEDINFO]

Revision history for this message
In , Pmladek (pmladek) wrote :

Okay, we do not want to backport the fix for OOo-3.1.1. OOo-3.2-final should be hopefully released within two weeks or so. => FIXED

Thanks you all for help and patience.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

FYI: Upstream (ooo-build) mark the bug as “fixed” because it no longer exists in 3.2 -- unfortunately there will be no backport to 3.1, so we have to wait until 3.2 is released in its final state (~2 weeks) and packaged for Ubuntu.

Revision history for this message
Jeremy Davis (jedmeister) wrote :

Hey Marcel, Thanks for your detailed and noob friendly help with my bug. Hopefully this 3.2 fix will fix my bug too (sounds likely). I have been really busy lately and so haven't completed all the steps you spelled out for me, but I wanted to let you know I really appreciated the effort you put into your response.

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

So does all of 3.2 have to be backported to really fix this on Karmic?

Revision history for this message
madbiologist (me-again) wrote :

Release Candidate 2 for OpenOffice.org 3.2 has been released - see http://www.openoffice.org/news/#32rc2

Unfortunately this version is not being tracked in Ubuntu 10.04 Lucid Lynx - see https://launchpad.net/ubuntu/+source/openoffice.org

Anyone who is affected by this bug and wants to see the fix in Lucid will need to tell the package maintainer (in this case the Ubuntu Development Team, a link to their page is at the ubuntu source link above) quickly, as the feature freeze is on February 18th 2010. The partner upload deadline is on January 28th 2010, but this shouldn't matter at there is already an OpenOffice.org package of some kind in Lucid. See the Lucid Release Schedule at https://wiki.ubuntu.com/LucidReleaseSchedule for more info.

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

According to this blueprint, https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-openoffice, Lucid is already targeting OOo 3.2.1.

Revision history for this message
madbiologist (me-again) wrote :

Thanks Gabe, that's good to know. Sounds like they will be adding it after the feature freeze, and possibly after the beta 1 freeze.

I'm wondering if there is a 3.2rc2 PPA for Lucid available anywhere?

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

@madbiologist:
> I'm wondering if there is a 3.2rc2 PPA for Lucid available anywhere?
I think first, ooo-build (see comment #59) has to be released for 3.2 (AFAIK, it follows a release by openoffice.org by about 2 weeks or so). Then it will probably appear in this PPA: https://launchpad.net/~openoffice-pkgs/+archive/ppa

Revision history for this message
gdneil (nsy999) wrote :

Hello,
Not sure if this helps... But had similar problems with Open Office crashing often with a fresh install of 9.10, but not when running 9.10 Live off a USB stick. Noted that the difference was that I had encrypted my home directory with the option available on install of 9.10. Installed again with home directory encryption off, and Open Office has not crashed since! Was having crashes with other programs also (jPilot, others) but running solidly now that I have removed encryption. Not a permanent fix obviously, but hope this helps lead in the right direction. I had tried the Sun version of oo, etc. and still got occasional crashes... but all is fine now!
-Neil

Revision history for this message
madbiologist (me-again) wrote :

OpenOffice.org 3.2 Release Candidate 5 has been released - see http://www.openoffice.org/news/index.html#32rc5

Revision history for this message
Eugenia (eudigio) wrote :

i've got the same problem....at first it was ok, and i could save as .doc ...but since 2 weeks i cannot.....

Revision history for this message
Jade Lacosse (sprucegum) wrote :

My girlfriend was working on an 80 page report for work today. The report contained many notes and it was necessary to save the document as .doc since her co-workers are old dogs who only know m$. Oo crashed when she tried to save the file. I managed to solve the problem by uninstalling the Ubuntu Oo 3.1 package and installing 3.2 from Openoffice.org. This solved the problem and she was then able to save the report as a .doc.

Revision history for this message
madbiologist (me-again) wrote :

The final version of OpenOffice.org 3.2 was released on 11th February 2010 - see http://www.openoffice.org/news/

Now we just have to wait for the corresponding ooo-build to be released for 3.2.

Revision history for this message
Tomasz Czapiewski (xeros) wrote :

Is there any repository or ppa with OpenOffice.org 3.2 already backported from Lucid to Karmic?
It looks like OOo 3.2 is really needed to fix this bug.

Revision history for this message
Tim Keitt (tkeitt) wrote :

I get this crash on my i386 desktop, but not when I ssh to my amd64 server and run oowriter from there (both run Karmic).

Chris Cheney (ccheney)
Changed in openoffice.org (Ubuntu):
status: Triaged → Fix Released
Changed in openoffice:
importance: Unknown → Critical
status: Incomplete → Fix Released
Revision history for this message
dino99 (9d9) wrote :

no recent comment

Changed in baltix:
status: New → Invalid
Displaying first 40 and last 40 comments. View all 110 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.