Description: First of all, THANK YOU developers for your hard work! I LOVE LibreOffice, it's a great peace of software with a good cause and I don't want to aggravate anyone by reporting this. However, at this point, I feel I have to. Here's the deal: Creating and editing slides in Impress (basically: just using it) starts out with slight UI lags/freezes. This isn't too bad, but adding more slides and/or more slide elements makes matters worse quickly. The lags/freezes reach a point where it takes me several seconds to being able a simple text box after I click it. And even then selecting, removing or adding text may take as much between one and several seconds. The same goes for other procedures, such as moving elements (e.g. a picture) around on a slide - it's really choppy and gets worse with time (as the presentation 'grows' and contains more slides and/or elements). I don't know how to be more specific, basically anything I do with slides in Impress' is laggy for me. It has now reached a level where I basically have to turn to other programs to create the simplest presentations. Writer or Calc, to some extent, suffer the same problems, but not nearly as bad as Impress. Enabling/disabling OpenGL/OpenCL; resetting my user profile; reinstalling the LO or the entire OS seems to have little to no effect. Bug reports I've found and *think* that they are somehow related to this (since they describe one or more aspects of what I'm experiencing): 104295/105500/112610/116975/120461 The version I'm reporting this for comes from the official 'Fresh' PPA (ppa:libreoffice/libreoffice-6-1). The problem, however, persists for me since version 5.x.x.x and seems to have worsened over time. So the behavior described above is reproducable for me over multiple versions of LO, over a period of time, on different PCs and notebooks, on different operating systems (mostly Ubuntu-based, however), with installations from the official repositories or from the LibreOffice PPA. Steps to Reproduce: 1. Create some simple text-based or 'heavy' image-/graphic-based slides with Impress (makes no difference for me, but 'heavy' presentations will show the fault sooner). 2. Try editing some text, move shapes/images around, add more slides to the presentation. 3. At some point (I can't really pinpoint it) actions like selecting a textbox/an image/etc., moving it, editing it and so on become less and less responsive. Actual Results: Changes are not displayed smoothly but are choppy/laggy to the point of being displayed with a delay of several seconds. Expected Results: Selecting/Editing/Moving items should happen rather instantaneously and smoothly. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.18.04.2 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3_kde5; Gebietsschema: de-AT (en_GB.UTF-8); Calc: group threaded ------------------- Operating System: KDE neon 5.14 Processors: 4× AMD A8-5545M APU with Radeon HD Graphics Memory: 7.0 GiB of RAM
Created attachment 147389 [details] A rather simple presentation that should show the problems described in my report.
Thank you for reporting the bug. I can not reproduce the bug in Version: 6.1.3.2 Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group threaded
Added slides so there were 20. Did not notice any slowness in editing/moving stuff. Would be great, if you could pinpoint the start of the slowness. After you reach the slowness and save the file, do you still experience the slowness after reopening the file? Although you did reset your profile, it would be interesting, if you tried running the experiment entirely in Safe mode, Help - Restart in safe mode and then Continue in safe mode. You might also experiment with 6.2 or 6.3 as an appimage: https://libreoffice.soluzioniopen.com/ Set to NEEDINFO. Change back to UNCONFIRMED after you have provided further testing information. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: bb30e9e591d5f9f913b3cd8fbaa3c5e412b509bd CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 23 January 2019
(In reply to Buovjaga from comment #3) > Would be great, if you could pinpoint the start of the slowness. After you > reach the slowness and save the file, do you still experience the slowness > after reopening the file? Basically yes, closing/reopening doesn't make any difference. Pinpointing this really has me scratching my head. Sometimes I feel Impress is slow/unresponsive from the moment I open it; then again it might be alright for a few clicks. > Although you did reset your profile, it would be interesting, if you tried > running the experiment entirely in Safe mode, Help - Restart in safe mode > and then Continue in safe mode. I tried this now - only for a short amount of time, mind you - but I didn't notice any improvement. Will try to test longer in the next days. > You might also experiment with 6.2 or 6.3 as an appimage: I downloaded the latest appimage, here's the version data: Version: 6.3.0.0.alpha0+ Build ID: 43836a58ffe943e2fc65be638f9a7d343102cb07 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-12-29_04:29:11 Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded Now, with version 6.3.0.0.alpha0+ I noticed some changes in behaviour: *IMPROVED* Moving images and text boxes is much smoother while also showing a preview of the image/text box. Quite nice! *UNCHANGED* Selecting an element still isn't instant, but delayed by about half a second. Clicking into a text box (or pressing F2) in order to write appears to be smoother, but fonts are still re-rendered which causes an ever so tiny amount of lag. *WORSENED* Switching selections (e.g. having a text box actively selected and now clicking on an image) causes a delay of 3-5 seconds before the selection changes. I can also drag and drop elements this way but there's still the same amount of lag. While I'm waiting for the selection or position of an element to change, Impress freezes, spikes up to two of my CPU cores to 100% and partly freezes my desktop. (I can't click anything with the mouse but, strangely enough, can switch windows with Alt+Tab) However, afterwards the element selection appears or the element has changed to the desired position. ------- So version 6.3 seems to fix part of the problem but not the root cause? I'm really sorry if I'm not of any help here... In any case, thank you for taking a look at this bug report! Please let me know if I can be of further assistance!
(In reply to Stefan Zurucker from comment #4) > So version 6.3 seems to fix part of the problem but not the root cause? I'm > really sorry if I'm not of any help here... In any case, thank you for > taking a look at this bug report! Please let me know if I can be of further > assistance! Well, there is one thing that you could do with your 6.1.3 version, but it is a bit complicated. It would be taking a callgrind trace that will allow developers to see, what calls in the code are taking the most time. The Ubuntu ppa for 6.1.3 offers debug symbol packages, which you need to install: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux I checked here that the -dbgsym packages are available: https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-1/+packages Then you need to install the valgrind program (I guess just sudo apt-get install valgrind). Finally, you need to follow the steps in the section "GNU/Linux: How to get a callgrind trace" in the debug info wiki article. For the actions to perform, I think it would be enough just to move a single element and then quit. For compressing the callgrind.out. file, tar.xz seems to be the best choice (of the commonly available compression formats). If you want to do more for LibreOffice in general, you join us in the QA team: https://wiki.documentfoundation.org/QA/GetInvolved
Hello Stefan, LibreOffice 6.2.2.2 is going to be released today, could you please try again with this version to see if the problem has been resolved meanwhile? Thanks in advance
Hello, everyone! After tinkering around a bit in version 6.2.2 I'm sorry to report that I have to confirm my obversations. I have tried the version from the "fresh" PPA als well as the snap installation. But the good things first: I did notice some improvements, just as with the 6.3.x appimage! Dragging images or text boxes around seems to be persistently smoother! However, it's still choppy, gets worse the "bigger" the presentation becomes and is just not as smooth as other presentation programs behave on my machines in general (WPS, OnlyOffice, ...) Unfortunately that's all I can tell you at this point, I still have to try Buovjaga's callgrind trace mentioned in comment #5. Thanks for your time! :)
Hello there everyone! Sorry to be a nuisance this way, but I can't seem to run the Valgrind trace as I'm unable to install debug-symbols. And I'm not sure why, so maybe some of you could point me in the right direction. As suggested... > The Ubuntu ppa for 6.1.3 offers debug symbol packages, which you need to > install: > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU. > 2FLinux > I checked here that the -dbgsym packages are available: > https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-1/+packages I tried to install the debug-symbols but there simply aren't any in the PPA as far as I can tell...? Am I missing anything? PLEASE NOTE: I had to uninstall the 6.2.x version from the PPA because it turned out to be massively unstable for me, crashing all the time. I'm back to 6.1.5 from the PPA. Would it, however, make more sense to reinstall the 6.2.x version via PPA and then try the callgrind, since 6.1 will be obsolete in the foreseeable future anyway? I would like to give this a shot. If anyone could point out what I might be doing wrong, I'd greatly appreciate it.
(In reply to Stefan Zurucker from comment #8) > I tried to install the debug-symbols but there simply aren't any in the PPA > as far as I can tell...? Am I missing anything? How did you try? If I click the triangle next to "libreoffice - 1:6.1.5~rc2-0ubuntu0.18.10.1~lo3 (Newer version available)", I see the list of built packages and it includes a whole lot of dbgsym packages. So why not install at least libreoffice-core-dbgsym and libreoffice-impress-dbgsym ?
Sorry, I should have been more clear on that. I added the PPA (sudo add-apt-repository ppa:libreoffice/libreoffice-6-1 && sudo apt-get update) and I'm getting 6.1.5 this way just fine, however none of the dbgsym-packages show up in my package manager or via apt in the terminal. But you're right, they are indeed there in the PPA as you describe! Do I need to enable anything else to get dbgsym-packages? Like adding another repo as described here (https://askubuntu.com/a/487567)? (I already tried this to no avail, btw) I apologize for taking you time, I feel stupid to even have to ask this here... I guess I will just manually install the .deb-files for the *-dbgsym from the PPA.
(In reply to Stefan Zurucker from comment #10) > Sorry, I should have been more clear on that. > > I added the PPA (sudo add-apt-repository ppa:libreoffice/libreoffice-6-1 && > sudo apt-get update) and I'm getting 6.1.5 this way just fine, however none > of the dbgsym-packages show up in my package manager or via apt in the > terminal. > > But you're right, they are indeed there in the PPA as you describe! Do I > need to enable anything else to get dbgsym-packages? Like adding another > repo as described here (https://askubuntu.com/a/487567)? (I already tried > this to no avail, btw) > > I apologize for taking you time, I feel stupid to even have to ask this > here... I guess I will just manually install the .deb-files for the *-dbgsym > from the PPA. Ok, sorry. Now I found this: https://bugs.documentfoundation.org/show_bug.cgi?id=122116#c17 Michael W. says: "As far as I can see, you probably have to add deb http://ppa.launchpad.net/libreoffice/libreoffice-prereleases/ubuntu bionic main/debug in addition and install the debug packages from there, called like the "normal" packages with a "-dbgsym" suffix added (e.g. 'libreoffice-writer-dbgsym', 'libreoffice-core-dbgsym', etc.)." So try to adapt the advice. Good luck.
Hello Stefan Zurucker, Since you're using the gtk3_kde5 backend, would you mind trying again on master? In the last couple of month many things have improved wrt KDE5
Dear Stefan Zurucker, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Stefan Zurucker, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp