libreoffice soffice.bin using 100% cpu

Bug #1724876 reported by Floris
62
This bug affects 13 people
Affects Status Importance Assigned to Milestone
LibreOffice
Unknown
Unknown
libreoffice (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load.

- 'Every action' includes typing as much as one single letter in a cell. Or opening the file.
- the file I am working on is only 1.1Mb in size
- the same file used to open fine in previous versions of libreoffice.

what I've tried so far - without any improvement in speed:
- under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution)
- automatic calculation has been turned off (no solution)
- libreoffice-gnome and libreoffice-gtk have been removed (no solution)
- purged and reinstalled libreoffice. (no solution)
- created new user profile - also no resolve

System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
Libreoffice:
Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
LukeKendall (luke-zeta) wrote :

FWIW, I had a few documents open, but none being actively edited. One very long (about 300k words).
I closed several of them (including the very long one).
One that had changes needing saving, I simply saved.
CPU load dropped to almost nothing.
Sorry I didn't think to check load before saving, and after closing the long one.
In the past I've found that closing LO and reopening files also fixes the issue.

Version: 6.0.1.1
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
Locale: en-GB (en_AU.UTF-8); Calc: group

Hope this helps slightly.

Revision history for this message
Olivier Tilloy (osomon) wrote :

@Floris: please excuse the lack of feedback on that bug. Are you still affected by the issue, or did it somehow resolve itself?

Revision history for this message
LukeKendall (luke-zeta) wrote :

I can add a few notes, as it's happened a few times since I wrote the above.
On each occasion, I've had:
- several documents open in Writer
- one is moderately large (93k words)
- at least one has changes needing to be saved.

If I save the modified doc, CPU usage stays at 100% for soffice.
If I close the large doc, CPU drops to negligible.
If I reopen the large doc, CPU goes back to 100% for up to a minute, then returns to negligible.

Revision history for this message
LukeKendall (luke-zeta) wrote :

But some more googling indicates this is a known bug in glib2 that the developers were very actively working from Jan-Feb 2018, but maybe not finalised by Mar 2018.
https://bugzilla.gnome.org/show_bug.cgi?id=761102#c53

Revision history for this message
Floris (fgjzoet) wrote : Re: [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu

Hi Olivier

Bug definitely did not resolve itself. it has been very persistent for a
long time (16.04 LTS). Forcing me to trying several other spreadsheet
programs. Not satisfactory though. I am actually forced to wait until this
bug is solved before I can continue my spreadsheet. So the bug is
responsible for a huge backlog on work.

I noted that the bug did not present in 17.04 (or 17.10, forgot what i
tried). Unfortunately 17.04 / 10 has issues with dual screen setup (second
screen does not work only mouse pointer visible) so that is not a workable
solution to continue the spreadsheet.

It MAY be that bug will not represent in 18.04 LTS AND dual screens work.
Takes until May for that release though - and then i still need to see dual
screen setup is OK. So please solve this bug!

kind regards, Floris

2018-03-19 11:17 GMT+01:00 Olivier Tilloy <email address hidden>:

> @Floris: please excuse the lack of feedback on that bug. Are you still
> affected by the issue, or did it somehow resolve itself?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724876
>
> Title:
> libreoffice soffice.bin using 100% cpu
>
> Status in libreoffice package in Ubuntu:
> Confirmed
>
> Bug description:
> With literally every action in libreoffice Calc, CPU usage goes to
> 100% due to soffice.bin, and stays on 100% for minutes. To the extend
> that libreoffice calc is UNUSABLE for anything that has to do with
> spreadsheets. As far as I am concerned, this is a critical bug because
> it makes the program unusable, and often even the complete computer
> due to the high cpu load.
>
> - 'Every action' includes typing as much as one single letter in a cell.
> Or opening the file.
> - the file I am working on is only 1.1Mb in size
> - the same file used to open fine in previous versions of libreoffice.
>
> what I've tried so far - without any improvement in speed:
> - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb
> per object (no solution)
> - automatic calculation has been turned off (no solution)
> - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
> - purged and reinstalled libreoffice. (no solution)
> - created new user profile - also no resolve
>
>
> System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
> Libreoffice:
> Version: 5.1.6.2
> Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
> CPU Threads: 4; OS Version: Linux 4.4; UI Render: default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+
> bug/1724876/+subscriptions
>

--
kind regards, met vriendelijke groet,
Floris Zoet

Revision history for this message
Floris (fgjzoet) wrote :

Hi Luke,

I have the issue with spreadsheet. Not seen it while making docs in writer.
Though those have not been that large.

kind regards, Floris

2018-03-19 11:20 GMT+01:00 LukeKendall <email address hidden>:

> I can add a few notes, as it's happened a few times since I wrote the
> above.
> On each occasion, I've had:
> - several documents open in Writer
> - one is moderately large (93k words)
> - at least one has changes needing to be saved.
>
> If I save the modified doc, CPU usage stays at 100% for soffice.
> If I close the large doc, CPU drops to negligible.
> If I reopen the large doc, CPU goes back to 100% for up to a minute, then
> returns to negligible.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724876
>
> Title:
> libreoffice soffice.bin using 100% cpu
>
> Status in libreoffice package in Ubuntu:
> Confirmed
>
> Bug description:
> With literally every action in libreoffice Calc, CPU usage goes to
> 100% due to soffice.bin, and stays on 100% for minutes. To the extend
> that libreoffice calc is UNUSABLE for anything that has to do with
> spreadsheets. As far as I am concerned, this is a critical bug because
> it makes the program unusable, and often even the complete computer
> due to the high cpu load.
>
> - 'Every action' includes typing as much as one single letter in a cell.
> Or opening the file.
> - the file I am working on is only 1.1Mb in size
> - the same file used to open fine in previous versions of libreoffice.
>
> what I've tried so far - without any improvement in speed:
> - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb
> per object (no solution)
> - automatic calculation has been turned off (no solution)
> - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
> - purged and reinstalled libreoffice. (no solution)
> - created new user profile - also no resolve
>
>
> System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
> Libreoffice:
> Version: 5.1.6.2
> Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
> CPU Threads: 4; OS Version: Linux 4.4; UI Render: default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+
> bug/1724876/+subscriptions
>

--
kind regards, met vriendelijke groet,
Floris Zoet

Revision history for this message
Floris (fgjzoet) wrote :

Thanks havent googled the bug for months anymore so good to know some are
finally actively working on it!

2018-03-19 11:33 GMT+01:00 LukeKendall <email address hidden>:

> But some more googling indicates this is a known bug in glib2 that the
> developers were very actively working from Jan-Feb 2018, but maybe not
> finalised by Mar 2018.
> https://bugzilla.gnome.org/show_bug.cgi?id=761102#c53
>
> ** Bug watch added: GNOME Bug Tracker #761102
> https://bugzilla.gnome.org/show_bug.cgi?id=761102
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724876
>
> Title:
> libreoffice soffice.bin using 100% cpu
>
> Status in libreoffice package in Ubuntu:
> Confirmed
>
> Bug description:
> With literally every action in libreoffice Calc, CPU usage goes to
> 100% due to soffice.bin, and stays on 100% for minutes. To the extend
> that libreoffice calc is UNUSABLE for anything that has to do with
> spreadsheets. As far as I am concerned, this is a critical bug because
> it makes the program unusable, and often even the complete computer
> due to the high cpu load.
>
> - 'Every action' includes typing as much as one single letter in a cell.
> Or opening the file.
> - the file I am working on is only 1.1Mb in size
> - the same file used to open fine in previous versions of libreoffice.
>
> what I've tried so far - without any improvement in speed:
> - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb
> per object (no solution)
> - automatic calculation has been turned off (no solution)
> - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
> - purged and reinstalled libreoffice. (no solution)
> - created new user profile - also no resolve
>
>
> System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
> Libreoffice:
> Version: 5.1.6.2
> Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
> CPU Threads: 4; OS Version: Linux 4.4; UI Render: default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+
> bug/1724876/+subscriptions
>

--
kind regards, met vriendelijke groet,
Floris Zoet

Revision history for this message
Floris (fgjzoet) wrote :

Found another non-working tip:

change the configuration file "sofficerc" and change Logo=1 to Logo=0

Tried, to no resolve. Bug and high cpu load persists

see: https://community.alfresco.com/thread/184308-sofficebin-has-cpu-pinned-at-100

Revision history for this message
Floris (fgjzoet) wrote :

Is any developer actively working on this?

Revision history for this message
Olivier Tilloy (osomon) wrote :

If this really is an upstream bug in glib (https://gitlab.gnome.org/GNOME/glib/issues/1128) then it looks like no, this isn't being actively worked on.

Revision history for this message
achevrier (a-chevrier-pro) wrote :

Hello. Affected also by the same 100% CPU soffice.bin with a document containing only one page of text with no image at all, whatever I close or not other applications or software.

Ubuntu LTS 18.04, and LibreOffice Version: 6.0.6.2 - Build ID: 1:6.0.6-0ubuntu0.18.04.1

In terminal, the command 'top' returns:
... 2 zombies ...
%CPU 100%, %MEM 8,3% soffice.bin

It is really boring. Computer is very hot. I have to close LibO. What can we do ?

Revision history for this message
Silas S. Brown (ssb22) wrote :

Also affects LibreOffice 6.0.7.3 on 18.04. In the occurrence I saw, the user had used and closed Calc but had left one Writer document open. All documents visited were made by the user and had no macros, but in case it's relevant I should perhaps mention we have Java disabled as a workaround for bug #1702165.

Revision history for this message
Silas S. Brown (ssb22) wrote :

It seems LibreOffice is more likely to use high CPU when its windows are in the background. Bringing one to the foreground reduced CPU usage.

Revision history for this message
Floris (fgjzoet) wrote :

Focus or no focus didn't have any effect in my case

Op wo 2 jan. 2019 21:40 schreef Silas S. Brown <<email address hidden>:

> It seems LibreOffice is more likely to use high CPU when its windows are
> in the background. Bringing one to the foreground reduced CPU usage.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724876
>
> Title:
> libreoffice soffice.bin using 100% cpu
>
> Status in libreoffice package in Ubuntu:
> Confirmed
>
> Bug description:
> With literally every action in libreoffice Calc, CPU usage goes to
> 100% due to soffice.bin, and stays on 100% for minutes. To the extend
> that libreoffice calc is UNUSABLE for anything that has to do with
> spreadsheets. As far as I am concerned, this is a critical bug because
> it makes the program unusable, and often even the complete computer
> due to the high cpu load.
>
> - 'Every action' includes typing as much as one single letter in a cell.
> Or opening the file.
> - the file I am working on is only 1.1Mb in size
> - the same file used to open fine in previous versions of libreoffice.
>
> what I've tried so far - without any improvement in speed:
> - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb
> per object (no solution)
> - automatic calculation has been turned off (no solution)
> - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
> - purged and reinstalled libreoffice. (no solution)
> - created new user profile - also no resolve
>
>
> System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
> Libreoffice:
> Version: 5.1.6.2
> Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
> CPU Threads: 4; OS Version: Linux 4.4; UI Render: default
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+subscriptions
>

Revision history for this message
adam boncz (aboncz) wrote :

Affects me often with LibreOffice 6.0.7.3 on Ubuntu 18.04 (Build ID: 1:6.0.7-0ubuntu0.18.04.2). Only help is to shut it down and reopen the document I am working on. Very annoying.

Revision history for this message
Floris (fgjzoet) wrote :

wil not confirm that closing and reopening the document helps. That does
not have any effect in my case.

Op di 12 feb. 2019 om 11:25 schreef adam boncz <email address hidden>:

> Affects me often with LibreOffice 6.0.7.3 on Ubuntu 18.04 (Build ID:
> 1:6.0.7-0ubuntu0.18.04.2). Only help is to shut it down and reopen the
> document I am working on. Very annoying.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724876
>
> Title:
> libreoffice soffice.bin using 100% cpu
>
> Status in libreoffice package in Ubuntu:
> Confirmed
>
> Bug description:
> With literally every action in libreoffice Calc, CPU usage goes to
> 100% due to soffice.bin, and stays on 100% for minutes. To the extend
> that libreoffice calc is UNUSABLE for anything that has to do with
> spreadsheets. As far as I am concerned, this is a critical bug because
> it makes the program unusable, and often even the complete computer
> due to the high cpu load.
>
> - 'Every action' includes typing as much as one single letter in a cell.
> Or opening the file.
> - the file I am working on is only 1.1Mb in size
> - the same file used to open fine in previous versions of libreoffice.
>
> what I've tried so far - without any improvement in speed:
> - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb
> per object (no solution)
> - automatic calculation has been turned off (no solution)
> - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
> - purged and reinstalled libreoffice. (no solution)
> - created new user profile - also no resolve
>
>
> System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
> Libreoffice:
> Version: 5.1.6.2
> Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
> CPU Threads: 4; OS Version: Linux 4.4; UI Render: default
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+subscriptions
>

--
kind regards, met vriendelijke groet,
Floris Zoet

Revision history for this message
achevrier (a-chevrier-pro) wrote :

This bug continues to affect me: ubuntu 18.04 LTS, LO Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2

IMPORTANT: I've noticed a link between web browser and this bug. Read bellow:

When Firefox and LO are together opened, then, after a while, LO CPU usage jumps to 100%. As soon as I close Firefox, LO CPU usage falls to less than 4%. I've noticed the same behaviour when Chromium is used.

I can say that this bug appears also when LO is opened, but no document opened (I mean, only the home LO window opened).

So closing the browser used and opened when LO is opened, down the CPU usage from strange 100% to normal less than 4%.

Revision history for this message
TLRobb (terry-maximatcher) wrote :

I have noted the same symptoms for months; i.e. 100% usage of one cpu core with any document opened in LibreOffice for an extended period. Simple 10kB text file in Writer or large spreadsheet in Calc.
Ubuntu 18.04.2 LTS, LibreOffice 6.0.7.3 00m0(Build:3). This behavour has not improved with any main line updates from Ubuntu.

Revision history for this message
Gabriel Staples (ercaguy) wrote :

Exact same as TLRobb notes just above:
100% usage of one cpu core for an extended period (hours?)--no idea what it's doing, but on a slow computer with few cores it's really rendering my computer nearly unusable just to have LibreOffice open in the background with a document minimized while I do something else on the computer.

Please work on this bug. It's making LibreOffice really affect my computer negatively.

Revision history for this message
Gabriel Staples (ercaguy) wrote :

Note: I'm running Ubuntu 18.04 with this LibreOffice:

Version: 6.3.1.2
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Here's a screenshot of my System Monitor, attached.
Notice soffice.bin is really sucking up my system hard with 24% total CPU usage, which is ~100% of one core since I only have 4 cores! It doesn't make any sense.

Revision history for this message
Gabriel Staples (ercaguy) wrote :

FYI these are the tweaks I've made to my Ubuntu 18 installation, in case any of them triggered or shed light on the LibreOffice issue: https://electricrcaircraftguy.github.io/20190919-post_ubuntu_18_todos.html.

Revision history for this message
Gabriel Staples (ercaguy) wrote :

Here's another screenshot showing the *massive* difference in total CPU load that I made simply by calling `pkill soffice.bin`!

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

We had a similar report about high CPU usage that turned out to be a troublesome extension rather than LibreOffice itself:

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825513

Do you perhaps have any additional extensions installed that could be causing this? If so, please disable them and let us know if the problem goes away.

Changed in libreoffice (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
In , Panther3002 (panther3002) wrote :

Description:
I recently installed Ubuntu 18.04 onto a laptop and immediately put LibreOffice 6.3.1 onto it. I've had problems ever since!

If LibreOffice is open, my computer feels laggy.
LibreOffice Writer is EXTREMELY laggy on some very large documents with mixed English and Arabic--but mostly just when looking at certain pages--other pages are much better.

LibreOffice Calc also had major issues: in one finance document I have which was converted from an Excel document a while back, I have some macros and macro-linked buttons. They've never worked since moving to LibreOffice but that's ok.
***When opening up the document, however, on this computer, those buttons would vibrate continually (note that they slightly overlap so it's almost like an algorithms is trying to fix them) and the document is COMPLETELY UNUSABLE. I could click around cells and the formula box would update with that cell's contents, but the cell would not be highlighted.

I finally downgraded to LibreOffice 6.2.8 and now both the Writer and the Calc issue are fixed and everything works just fine!

My system is Ubuntu 18.04 LTS. Here's the 3 LibreOffice versions tested:

Versions Tested:
------------------
LibreOffice_6.3.1_Linux_x86-64_deb.tar.gz [previous latest] - BUG, tested 20191026
LibreOffice_6.3.2_Linux_x86-64_deb.tar.gz [latest] - BUG, tested 20191026
LibreOffice_6.2.8_Linux_x86-64_deb.tar.gz [stable] - WORKS FINE! Tested 20191026

Here's an example of how I've been uninstalling and installing versions:

To uninstall old version:
 - from a NON-libreoffice installation directory (ex: from home dir):
 sudo apt remove libreoffice6.3*
To install new version:
 - manually extract (right click file --> Exract here), then:
 cd into LibreOffice_6.3.2.2_Linux_x86-64_deb/DEBS dir, then:
 sudo dpkg -i *.deb

Steps to Reproduce:
TODO: these are personal documents I cannot share, so if able I'll try to get a document with the problems which does not have personal info.

1.
2.
3.

Actual Results:
Editing in Calc is impossible: vibrating macro buttons and no cells can be properly selected.

Editing in Writer on *some pages* is virtually impossible: it is missing keystrokes like crazy and there is a 1~5 second lag between each character I enter.

Expected Results:
I should be able to edit any cells in Calc.
The macro buttons should sit still, not vibrate up and down rapidly a few pixels at a time.

I should be able to type at a normal speed in Writer.

Reproducible: Always

User Profile Reset: No

Additional Info:
The bug was introduced into LibreOffice between version 6.2.8 and version 6.3.1, as 6.3.1 and 6.3.2 are unusable for me, and 6.2.8 so far works perfectly!

Revision history for this message
In , Panther3002 (panther3002) wrote :
Revision history for this message
In , Panther3002 (panther3002) wrote :

Possibly related/maybe a duplicate of: https://bugs.documentfoundation.org/show_bug.cgi?id=127842

Revision history for this message
Gabriel Staples (ercaguy) wrote :

Marcus, here's all the extensions I have installed.

Also, I just downgraded my LibreOffice installation from 6.3.2 to 6.3.1 then to 6.2.8.
6.3.2 and 6.3.1 both were buggy, but 6.2.8 seems to work perfectly now and actually makes my entire computer feel like I just bought a new computer! All of a sudden it feels totally usable again!

Here's my bug report I just made on this. It may be related: https://bugs.documentfoundation.org/show_bug.cgi?id=128406.

See also this (appears to be the *exact* same problem as my bug report above): https://ask.libreoffice.org/en/question/208712/calc-6312-macro-button-problem/

Revision history for this message
Gabriel Staples (ercaguy) wrote :

Also, here was my work-around to try to fix the 100% cpu soffice.bin bug: https://serverfault.com/questions/953809/soffice-bin-high-cpu-usage/986039#986039.

Revision history for this message
In , Panther3002 (panther3002) wrote :

Possibly also related--or maybe a different bug altogether? https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876

Revision history for this message
In , julien2412 (serval2412-6) wrote :

There are 2 described pbs in your bug:
- slowliness
- flashing buttons (indeed tdf#121963)
We must focus on 1 pb only. (1 bugtracker => 1 problem or 1 group of very related problems)
Considering the number of duplicates about flashing buttons, I propose you we focus on 1.

Since your document seems confidential (financial part), I propose you to sanitize it (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission) then to attach it to the bugtracker so we can try to reproduce the problem.

Before that, you may also upgrade to 6.3.2 (I suppose it should be present on LO ppa) to test this slowlisness problem.

Revision history for this message
In , W-jag (w-jag) wrote :

Bug still living in V6.4.0.0alpha1 with documents created with older version.
(As also in 6.3: Other control type also affected even if not having a macro assigned.)
Not yet observed in a few very simple examples freshly created with 6.4 alpha.

Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → Incomplete
Revision history for this message
In , julien2412 (serval2412-6) wrote :

It might be a dup of tdf#121963 which has just been fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=e8720057aa0f4e612000d68f6de682f3afb8a1ea
It should be present in daily build in 24/48h, to retest.

Revision history for this message
In , Xiscofauli (xiscofauli) wrote :

Thank you for reporting the bug.
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.

Revision history for this message
In , Bsobey (bsobey) wrote :

Created attachment 155789
File to Demonstrate problem with Basic Macro to Solve to target

Changed in df-libreoffice:
status: Incomplete → New
Revision history for this message
In , julien2412 (serval2412-6) wrote :

(In reply to Bruce Sobey from comment #8)
> Created attachment 155789 [details]
> File to Demonstrate problem with Basic Macro to Solve to target

On Win10 with master sources updated today, I don't reproduce this.
Indeed, when opening the file and accepting macros, "Insert 10 lines" button doesn't flash. Did you check with prerelease 6.3.4? (it should be released officially next week, see https://wiki.documentfoundation.org/ReleasePlan/6.3)

Changed in df-libreoffice:
status: New → Incomplete
Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear Gabriel Staples,

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

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear Gabriel Staples,

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

Changed in df-libreoffice:
status: Incomplete → Unknown
Changed in df-libreoffice:
importance: Medium → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.