Bug 126801 - Exception in getAccessibleName and getAccessibleDescription
Summary: Exception in getAccessibleName and getAccessibleDescription
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-09 21:55 UTC by Jim Avera
Modified: 2020-03-10 03:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
test.ods (see "Steps to reproduce") (106.05 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-08-09 21:57 UTC, Jim Avera
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Avera 2019-08-09 21:55:42 UTC
Description:
When switching between sheets in the attached "test.ods" spreassheet, many exception messages appear on the terminal like these:

** (soffice:23481): WARNING **: 14:50:16.023: Exception in getAccessibleName()

** (soffice:23481): WARNING **: 14:50:16.023: Exception in getAccessibleDescription()


Steps to Reproduce:
1. Open the attached "test.ods"
   Do NOT enable macros.

2. Click buttons to select sheets, starting with _PROTO
   Keep selecting different sheets.


Actual Results:
Many exception messages on the terminal

Expected Results:
No messages


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Jim Avera 2019-08-09 21:57:03 UTC
Created attachment 153275 [details]
test.ods (see "Steps to reproduce")
Comment 2 Julien Nabet 2019-08-10 10:45:55 UTC
On pc Debian x86-64 with master sources + gtk3 updated today, I tried to reproduce but without success.
I clicked about 20 times on sheets tabs, beginning with _PROTO, no crash.
Did I miss something?
Comment 3 Jim Avera 2019-08-10 20:49:45 UTC
Ok, this is reproducible only when logged in as me, not when running in a newly-create pristine user environment.   

However it is *not* a corrupted profile, because the problem still happens in safe mode, i.e. with no profile.

Therefore something in my setup make LibreOffice follow an infrequent code path.  I suspect LO is responding to dbus notifications or some other "outside input".

How can I collect useful debug information to track this down?
Comment 4 Julien Nabet 2019-08-11 09:07:03 UTC
Did you enable some accessibility functions? If yes, could you disable them for the test?

Here's a link which explains how to retrieve a backtrace:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Comment 5 QA Administrators 2020-02-08 03:14:18 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2020-03-10 03:11:39 UTC
Dear Jim Avera,

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