Created attachment 112738 [details] Crash backtrace Hi, From LO 4.3.3, Orca 3.14, steps to reproduce: 1. Open the attach file with Orca enabled. 2. ctrl-home 3. Down arrow key, until A11 When the speech synthetiser is enabled, on A11, LO crashes. Without speech, it's not systematic. I attach the traceback too. Regards,
Created attachment 112741 [details] Test file
I can not confirm with Version: 4.5.0.0.alpha0+ Build ID: 60143f4f7bc50054dcef923218b8c7c3bc154933 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-01-21_04:58:34 Locale: cs_CZ
Hi, I tried with master built today. I reproduce again. Same behavior. I use DEBS packages. Regards, (In reply to raal from comment #2) > I can not confirm with Version: 4.5.0.0.alpha0+ > Build ID: 60143f4f7bc50054dcef923218b8c7c3bc154933 > TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: > 2015-01-21_04:58:34 > Locale: cs_CZ
Created attachment 113612 [details] A trace of what I experience on 4.4.0
Hi, I'm experiencing the same problem with LO 4.4.0, here's the backtrace. The bug nearly makes Calc unusable in many situations. Fixing this bug would fix other a11y issues as we saw with Orca team. Regards,
I don't experience a crash following the instructions in comment 0, but I do see the following when the cursor hits cell A11, which seems relevant: (soffice:26343): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x7f2954d4bc30(0x2775590)
Ubuntu 15.04 LibreOffice 5.0.2.2 No crash. Marking as NEEDINFO: Please do the following: 1. Reset your profile: https://wiki.documentfoundation.org/UserProfile 2. Install 5.0.2.2 or later Rerun your test and see what you get. If you get a crash still, mark the bug as UNCONFIRMED and I will try to find a developer to look at your crash log. Thanks!
(In reply to Jean-Philippe MENGUAL from comment #0) > From LO 4.3.3, Orca 3.14, steps to reproduce: > 1. Open the attach file with Orca enabled. > 2. ctrl-home > 3. Down arrow key, until A11 With the steps describe and LibreOffice 5.1.2 and Orca 3.18 I cannot reproduce the bug. Could you confirm or not your bug ?
Dear all, after a discussion with the bug reporter it seems that the bug no longer appears in the latest 5.1 version. Best regards.