Openoffice.org crash when i try to open a file

[Paymon]

Binary package hint: openoffice.org

I'm using edgy elf and i find this bug.

When i click on open icon or when i click on file->open openoffice call the file browser, crash and restart leaving the browser opened and asking me if i want recover the Untitled1 file. This problem still when i try to change the paths from the options pannel.
The problem is bind with another one. "My documents" directory is blocked and i can't browse it with nothing. I had rm and mkdir but still blocked. I have to force the closing of the file browser.

[Warren Uniewski (wrnu)]

I think this is a problem with the gtk-dialogs in Oo

[John Teddy (masterjediyoda-gmail-deactivatedaccount)]

yes, I also have the same bug with x86 Ubuntu. I did a fresh install with edgy on Sep. 16th, and I started OO.o Writer, and when I go to save it crashes, then recovers my document. Except EVERYTIME I try and save it crashes and recovers my document. So the only way to truly recover my document is to copy/paste into another text editor.

[bubba (kevin-turner)]

i have the same problem.

also, the quickstarter for gnome keeps crashing.

however, i can open *.odt documents from within nautilus without any crashes or recovery dialogues appearing???

[Paymon (matteo-noris)]

Now i use ubuntu without openoffice.org-gnome and openoffice.org-gtk.

This isn't the solution of problem but you can use openoffice on Ubuntu 6.10

sudo apt-get remove openoffice.org-gnome openoffice.org-gtk --purge

Now you can use openoffice but without a ubuntu theme and without gtk-dialog

[ChrisDesjardins (cddesjardins)]

It should also be noted that I'm experiencing this problem on an i386
machine as well.

On Tue, 2006-09-19 at 13:05 +0000, Matthias Klose wrote:
> ** Changed in: openoffice.org-amd64 (Ubuntu)
> Sourcepackagename: openoffice.org-amd64 => openoffice.org
> Assignee: (unassigned) => Matthias Klose
> Status: Confirmed => In Progress
>

[Bruce Cowan (bruce89-deactivatedaccount)]

Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.