![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
When I work with a presentation in Impress, it happens quite frequently that
while moving an object the desktop stops responding to input, neither mouse
clicks nor keyboard input. I can move around the mouse pointer (now hand)
but I cannot do anything else. All that I am left with is a hard reboot. I
have dual-boot system and tried the same presentation in windows, only to
experience the same behaviour after a few minutes, so I assume that it is a
problem with LO, not the OS. If someone could advise me how to gather any
relevant information on these crashes, I would be very happy to contribute
to a resolution. Right now LO Impress is not very useful for me.
Hi 
Please could you post a bug-report about it?
http://wiki.documentfoundation.org/BugReport
A copy&paste of your email would be perfect. It might be good to say which
version of LibreOffice you are using, 3.3.3 or 3.4.2 or whatever but don't worry
about it if you don't know right now. Also a hint of which OS, such as Ubuntu
10.04 or Mandriva 2011.2 or whatever. Again it's stuff that you could add to
the report in a later comment if anyone asks.
Impress does have a fwe problems but i have not heard of this happening before.
It sounds fairly serious though. No app should be able to bring down a
Gnu&Linux OS or any other unix-based platform so it's urgent to get a bug-report
out there quickly.
Is the machine a laptop? Have you installed a new graphics card recently?
Ram? Do you know how much ram the machine has? Have other apps also crashed
the machine? Do you know what temperature the Cpu is reaching? On my machine i
can only check the temp at reboot in the bios. Since you are experienced with
Gnu&Linux i was wondering if you are any good with hardware too? Any of those
questions would be nice to have answers too even if you don't know the answers
to all of them.
Regards from
Tom
Hi Tom,
Thanks for the quick reply. The bug report is now
https://bugs.freedesktop.org/show_bug.cgi?id=40141
Unfortunately, I cannot reproduce the crash using strace. Ironic! I'll just
start LO through strace every time and if it doesn't crash, that's fine,
too.
Cheers
Stan
Hi
Nicely done. have you tried using Synaptic Package Manager to
Edit - "Fix broken packages"
Also out of curiosity which format do you use for the presentation? Could
you try "Save As" and change to "the other one", eg if the presentation is
currently a .Ppt try saving as a .Odp
I don't know if it's going to be possible to try that and i don't know why i
didn't think of it before.
Regards from
Tom
this reminded me my experience,not this much serious though.
while creating a presentation,i found LO unresponsive.i was a bit
scared.waited for few minutes and it was working again.later,i found that LO
was making a back-up copy at that time and hence the effect.dont know if
this is normal or not.and this happened only for the first
back-up.subsequent ones went without any problem.
LO-3.3.2,ubuntu lucid.
but the system itself was not hanged in my case;i used other apps
normally.no problem there
Hi
Good point. Also have you tried increasing the size of the memory caches
available to LibreOffice?
Tools - Options - LibreOffice - Memory
However in Gnu&Linux a single app should be able to "grey out" or even crash
completely without affecting any of the other apps or the rest of the desktop.
Usually if you move the mouse arrow outside of the app or switch to another
workspace then you should find that everything else is working fine.
In platforms that are not unix-based apps and processes are not usually
protected from each other. This impacts on stability and security. That is why
i thought it best to get a bug-report posted asap so thanks for doing that.
Regards from
Tom
Hi
this reminded me my experience,not this much serious though.
while creating a presentation,i found LO unresponsive.i was a bit
scared.waited for few minutes and it was working again.later,i found that LO
was making a back-up copy at that time and hence the effect.dont know if
this is normal or not.and this happened only for the first
back-up.subsequent ones went without any problem.
LO-3.3.2,ubuntu lucid.
but the system itself was not hanged in my case;i used other apps
normally.no problem there
I have seen LO appear to hang when backing up very large document. The
computer was completely functional and once the backup was done LO
worked.
One other thing I noticed that could slow down LO is having record
changes on (EDIT >> CHANGES >> RECORD). It really slowed down find &
replace when on.
Thanks for the helpful ideas. At the moment, I am trying to reproduce the
crash while logging events through strace, but still to no avail. From
memory, the crash happened mostly with a particular odp file I had to
finish, but recently it also happened when I opened someone else's ppt and
yesterday just before I sent out my cry for help, it crashed on me just
after removing all but one slide from the odp file I used previously and
pasting a couple of images, i.e. within 5 minutes of opening it. No crashes
since. I'm sure it will crash again when I actually need to get something
done urgently. At least you gave me a few hints what I can try to get it to
do the job when I need to. I'll report when I encounter another crash.
Cheers
Stan
Just to clarify, the issue I was having did not appear to be an effect of a
slowed-down LO, as the entire OS went unresponsive and the first few times
it happened, I waited for a loooong time to give it a chance to recover. It
never did. However, since I cannot reproduce the crashes right now, I can't
add anything useful, sorry about that.
stan wrote (18-08-11 09:40)
However, since I cannot reproduce the crashes right now, I can't
add anything useful, sorry about that.
Never mind. It happens more often that people report crashes or such, and in the end they seem to have disappeared
Cheers,
UPDATE: The same problem now re-occurred with LO writer. Unfortunately,
although running through strace, no strace.log to be found on the system.