Running LibreOffice 3.3 beta2 on my (outdated) kubuntu 7.10 I experience reproducible freeze on operations calling the "save as" dialog box.
File -> save (or Icon)
File -> save as
File -> export to pdf... (or Icon)
File -> open doesn't show any effect.
all of these leave [soffice.bin] <defunct> processes
Linux bombadil 2.6.22-16-generic #1 SMP Thu Apr 2 01:27:50 GMT 2009 i686 GNU/Linux
I also reproduced on Kubuntu 8.04 valid LTS
Linux hardy 2.6.24-28-generic #1 SMP Sat Oct 16 17:46:03 UTC 2010 i686 GNU/Linux
Forgot to mention:
Installation from deb packages
same effect installing from repo:
deb http://download.tuxfamily.org/gericom/libreoffice /
do we still even support kde3 :-/ iirc it doesn't ( but I am not sure )
in the konsole before manaually launching libreoffice ( 'soffice' ) from the cmd line help?
> do we still even support kde3 :-/ iirc it doesn't (
> but I am not sure )
I stick with it using kdepim due to optimizing to death kmail and a not
reasonable working adressbook/akonadi server in kubuntu lucid..
>in the konsole before manaually launching libreoffice ( 'soffice' )
> from the cmd line help?
yes! Then the LibO dialogboxes are called as far as I see in an
Is there a way to make LibO recognizing that an do the right thing?
like I said, I am not sure exactly what the state of kde3 support is, putting this to lubos ( who is on vacation at the moment ) who might have more of an idea
This bug persists in beta3
any progress on this?
I managed to work around by change settings:
Tools -> options -> LibreOffice -> general -> [x] use LibreOffice dialogs
instead of setting the environment
this avoids changing all *.desktop files. And having crashfree LibO started from elsewhere :o))
I'm afraid obsolete KDE3 is way too low priority for this getting any attention, sorry. Either use the workaround from comment #5 or use KDE4 (note that you can use KDE4 workspace together with KDE3 KMail, assuming Kubuntu provides the necessary packages).
Should be fixed now, after all.
Have to reopen this one.
Problem persists with Libo-3.3.2.
What should be the expected behaviour after the fix? As I was upgrading it's probably an issue of preferences already present.
So if You tell me under which conditions it should work, I'll test and help estimate, whether this is reasonable to avoid bad experience in a range wide enough.
3.3.2 is too old.
*** Bug 32313 has been marked as a duplicate of this bug. ***
*** Bug 33575 has been marked as a duplicate of this bug. ***
*** Bug 37093 has been marked as a duplicate of this bug. ***