Updates have RUINED Libre

English
,
#1

I made the BIG mistake updating LibreOffice a while back and it has been ruined EVERY since. I have removed it and reloaded it. I have tried 24.2.1 MISTAKE. I have tried reinstalling 7.6.5 and the errors are ALL over this mess. In presentation I can’t change from slide to slide. NOW I have to hit “VIEW” go to “Outline” and click the slide I want. After I get the slide I want ‘highlighted’, I then go back to “View” and click “Normal” in order to edit it. When editing a slide, If I am trying to ‘move’ an object it MAY or MAY NOT move the direction I am clicking on the little arrow, whether it is up or down, side to side. IF I click the “UP” I may go. BUT if I try to go back down and click the down arrow, IT CONTINUES GOING UP!!! OR Vise Versa! AND as I already stated, the same thing goes for side to side. There are some issues in the new Calc also, but off hand I can’t think of them right now, If I remember them I will post again. And it ALL started with an UPDATE to get 7.6.5. IF I could go back to an older version than that, I would! I have NEVER had problems with LibreOffice until that update a few months back.

Oh, and one other issue is it keeps ‘crashing’ on me now also. VERY FRUSTRATING!!

#2

On the download page you’ll find this link:

Older versions of LibreOffice (no longer updated!) are available in the archive

1 Like
#3

Click View > Slide Pane to toggle visibility of slide pane.

1 Like
#5

Is there a place where people benchmark same documents, same template and same extension loaded for all the version on the question of not only loading time (writer) but even once loaded many typical past fluid operations now need frequent patience from the user and no clue as to what is going on. I am now on 24.8, and since I went from 6.xx to 7.xx to that. it is has gone increasingly disappointing. Like I would need to segment all the documents to archaic sizes for when the software market was needing that. Can we talk about regression testing?

#6

I don’t know, but surely NOT in a 6 month old thread where somebody gave a rant about his problems with updates.

It is a free world, but same suggestion as above: On this ask-site open your own topic on this. One reason us simply being polite to the starter of this thread: He/she may be notified on every answer here, and this is annoying, when it is not related to the initial question…

(Besides: this is not really a site where many developers are active…)

#7

from Testing - QA | LibreOffice > Regression

image
image1422×803 155 KB

1 Like
#8

Thanks. I looked in the link. So, I guess our feedback is important, for non-qualitative feature bug exist or not. A question of subjective responsiveness might be difficult to assess or qualify as a new bug, while there might be more important objective bugs, that would be reproducible, like not working at all or not doing what it used to do as it was, qualitatively. So our tone as feedback providers might be more of reporting collaboration. But it has to be here first. As this might not be easy to qualify as actionable bug. Anyway thanks for showing me there is concern and methods in place, possibly not the human resources to go through full method.

#4

This is not a solution for the specific issue, but a reminder concerning a more general advice:

Users mainly wanting a stable LibreOffice should

  • update to a newer first-or-second-digit-version eventually but
  • should only update if a rather high (>=4 e,g,) third digit is reached (“not too fresh”) with an explicit release.

Reasons in short: New features or UI-updates or efficiency enhancements need to change some code “in the deep” and may thereby cause new bugs (or regressions). Fixing these bugs may take some bugfix-versions.

  • Users urgently wanting to try out a new feature should install their “fresh” version in parallel (or try it without an installation as a “portable app” on Win).
  • Users who feel overwhelmed by the instructions should refrain from following them.
4 Likes

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.