Ask Your Question
0

What happened in 4.4?

asked 2015-06-25 11:50:41 +0100

Bart Friederichs gravatar image

updated 2015-08-24 18:16:58 +0100

Alex Kemp gravatar image

I have updated my Fedora to 22 and with it, LibreOffice version 4.4.3.2. I must say, LibreOffice has never been so buggy before. It is in fact damaging productivity. Over the last few weeks I have encountered the following issues:

  • incorrect rendering of the "sidebar" (where the sylist now is located) after switching desktops
  • general slowness; menus take 2-3 seconds to show, etc
  • a full on crash (never happened before) when showing a print preview
  • there is no page number in the page number field on the last page

I know I can file a bug, but this is getting a little too much (I do not have the time to file and track four major bugs).

Next to that, why integrate the Stylist in a sidebar, that doesn't remember the setting? I want the stylist to always show, not the "Properties" sidebar.

My question basically is: is this known and can we put the issues under growth-pains?

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted
1

answered 2015-06-25 14:01:09 +0100

petermau gravatar image

A general piece of advice everybody gives when there have been problems after a major system update is to reset the user profile. The recommended way to do this is to rename the profile so that it can be restored if this change does not help. I always do this when I update LibO before the update, and more especially when I update my system with all its dependencies. On my Linux Mint Mate the file is found in ./config/libreoffice/4 for version 4.x of LibO.

LibO 4.4.3.2 is a late version of 4.4 and my copy runs well. There may be specific Fedora 22 problems with LibO but I cannot test them on my system. Have you checked whether there are any known problems?..Peter

edit flag offensive delete link more
0

answered 2015-06-25 19:55:49 +0100

vmiklos gravatar image

Also, if you see problems but you have limited time, a good compromise is to select one problem that you can reliably reproduce and report it, so QA can triage & prioritize is properly. If everyone does that, developers are aware of the most annoying problems and can keep them under control. :-)

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2015-06-25 11:50:41 +0100

Seen: 183 times

Last updated: Jun 25 '15