Description: When an existing Sheet is deleted using the GUI from the attached spreadsheet, almost 500 lines of warnings appear on the terminal, repeating these: ** (soffice:14578): WARNING **: ... Exception in getAccessibleIndexInParent() ** (soffice:14578): WARNING **: ... Exception in getAccessibleName() This occurs with the attached spreadsheet, with macros DISABLED. Steps to Reproduce: 1. Open the attached demo spreadsheet ("exceptions2.ods") DO NOT enable macros 2. Click the sheet tab "AAPL" 3. Rightclick->Delete Sheet; click Yes to confirm Actual Results: Hundreds of warnings appear on the terminal. Expected Results: Reassuring silence. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.0.0.alpha0+ Build ID: 32b85ec64e5c901369ce3ce5dbda0e96f2ec7fc0 CPU threads: 12; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-07_16:08:14 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 148253 [details] Demo spreadsheet ("exceptions2.ods")
No repro with Version: 6.3.0.0.alpha0+ Build ID: 892a5cfe557edb405ec0037676f02a1c24dd76ec CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
no repro with Version: 6.3.0.0.alpha0+ Build ID: 62142168e42a050d052d7d75fafd8f6e9cf2a1af CPU threads: 2; OS: Linux 4.19; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-10_12:30:00 Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
> Additional Info: > Version: 6.3.0.0.alpha0+ > Build ID: 32b85ec64e5c901369ce3ce5dbda0e96f2ec7fc0 > CPU threads: 12; OS: Linux 4.15; UI render: default; VCL: gtk3; > TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: > 2019-01-07_16:08:14 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. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
There is something about my personal environment which provokes this; the problem does *not* happen when logged in as another user. I tried removing my profile and removing all environment variables other than PATH=/bin:/usr/bin and DISPLAY, and the problem still happens when logged in as me (but not as another user). I'm using latest master, installed parallel to other version. Give me a few days to try to isolate what is provoking this. I'll post more when I know more. -Jim
DBUS or some other IPC-based thing must be provoking Libre Office to give these warnings. Possibly related to my desktop environment (Gnome on Ubuntu, pretty standard AFAIK). Does anyone have any ideas? Again, resetting profile and eliminating all env variables does not make the problem go away. But logging in as a different user does make the problem disappear.
(In reply to Jim Avera from comment #5) > Give me a few days to try to isolate what is provoking this. I'll post more > when I know more. > -Jim Hi Jim, Please, investigate it a bit further because you're the only one facing this problem,,,
Dear Jim Avera, 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
Ok, some progress! I was able to isolate the conditions to make the bug happen down to having the "gsconnect" gnome shell extension installed to monitor my Android phone. Yea, what the heck does that have to do with Libre Office?!? Anyway, I will attach a script ("setup.sh") which, when executed, will slam the relevant files into the current user's configuration. (The script unpacks an archive into .local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io and stores minimal dconf settings for it). IMPORTANT: Don't run this script as a normal user; instead, create a test user and login as that test user first. I used a Virtual Machine to prevent any possible contamination of my real system. STEPS TO REPRODUCE: 1. Log into a VM after making a checkpoint, or alternatively create a test user e.g. sudo newuser testuser
Created attachment 152884 [details] setup.sh - slam config files to allow bug to reproduce
... sorry hit RETURN before I was finished... STEPS TO REPRODUCE: 1. Log into a VM after making a checkpoint, or alternatively create a test user e.g. with sudo newuser testuser, log out and login as that user. 2. Execute the attached "setup.sh" #attached 3. soffice exceptions2.ods #attached 4. Delete the "AAPL" sheet RESULTS: Many exception messages on the terminal
(sigh). You have to log out and log in again after running setup.sh
Hello Jim, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Yes, bug is still there with latest master Version: 6.5.0.0.alpha0+ Build ID: d1730033b4fa1f0cfeedd136dfb23ec01a194ec0 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-20_03:30:24 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Note the full STEPS TO REPRODUCE as follows: 1. sudo adduser testuser # create disposable user account (or use a VM) 2. Log out and log in as 'testuser' 3. Run the "setup.sh" script (download from this bug) 4. Start LO, open "exceptions2.ods" (download from this bug) Do NOT enable macros. 5. Delete the sheet "AAPL" RESULTS: Many exception messages like these: ** (soffice:17889): WARNING **: 16:27:33.577: Exception in getAccessibleName() ** (soffice:17889): WARNING **: 16:27:33.577: Exception in getAccessibleDescription() Expected Results: No exceptions.
I didn't test but I do not see a point in all those steps nor in fixing this.
The point is that something in how LO interacts with gnome is making LO break and spew errors onto the terminal. I can't tell you exactly what triggers the errors, only that I've narrowed it down to some OS interaction which occurs when a particular gnome extension installed. The setup script I provided allows easy test and debugging without requiring you (i.e. a developer) to actually install this gnome extension in your personal setup.
(In reply to Jim Avera from comment #16) > The point is that something in how LO interacts with gnome is making LO > break and spew errors onto the terminal. > > I can't tell you exactly what triggers the errors, only that I've narrowed > it down to some OS interaction which occurs when a particular gnome > extension installed. > > The setup script I provided allows easy test and debugging without requiring > you (i.e. a developer) to actually install this gnome extension in your > personal setup. Hi jim, Which extension is it ?
> Hi jim, Which extension is it ? It was gsconnect. I uninstalled it to prevent the messages a while ago. The problem seems to be gone now. Recently I updated my OS (from Ubuntu 19.10 to 20.04), which changed to a new version of GNOME. And LO has moved along, of course. So I'm closing this ticket (WFM). Thanks for following up!