https://bugs.documentfoundation.org/show_bug.cgi?id=154846

--- Comment #2 from Joysn71 <joys...@gmail.com> ---
On current Linux Mint Debian edition, based on Debian Bullseye, current stable
release, we get LO 7.0.4.2.

I installed 7.5.2.2 from the deb packages from your website. And the first
start with my presentation and playing around ...
Focus on an image on a slide, Properties pane open with Position and Size,
playing with the PosX, PosY, Width, Height values, Shift-F5 to presentation
mode of that slide, Esc, changing numbers in the before mentioned fields. 2-3
times. LibreOffice 7.5 Document Recovery dialog :(
To be honest, it is not funny to use LO. 
Last week on our local yearly Linux Days, I met an few old friend/colleague,
which does talks and presentations about OSS topics every now and then. He told
me he gave up on LO. They are tired of having these troubles all the time and
risk crashes during their presentations. I tried to export to a PDF, but the
animation effects are not working. Installing LO via PortableApp is almost not
possible on my university account, as storage space per account is limited. I
can not install only Impress for presentations, I get the whole package. I
needed to remove all data from the account to be able to install it and still I
need to load the presentation (56mb) from a web storage to be able to uvercome
the storage limitations.
Will it work on the great day? Or will LO crash during the presentation in
front of the commission? I dont know. I will borrow a Windows machine and
recreate the slides PowerPoint. Really tired of Impress, thought I can go
around MS and PP, but no. 40 slides with a few images, two fonts, and 5 slides
with a simple animation is not doable. Till now 3 different versions used, not
a slight improve seen.

And btw: Open Sans Semibold font is not included when I open the presentation
on Windows LO 7.5.2.2 when I edit and save the file on LO 7.5.2.2 on Debian. I
uploaded a simple example file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to