Using Autokey-py3 in Linux (Antergos with GNOME 3.26) and I notice my phrases in LibreOffice Writer are not activating correctly. For example, if I open Leafpad or gedit I can type nan and it will expand to NaNoWriMo. If I do the same in LO Writer then I get NnaWriM, or some other iteration, that's not NaNoWriMo. This happens with all my phrases.
I have the same problem - but only in Writer (Calc and Impress work as they should). I don't have the problem in Writer Version: 5.3.4.2 I think I also did not have the problem in master~2017-10-18_22.54.20_LibreOfficeDev_6.0.0.0.alpha0_Linux_x86-64_deb.tar.gz ( I could check), although I did have it in a prior version, and then it either went away or I found a fix for it. for example, I have created an Autokey phrase <fox-> which then expands to <the quick brown fox jumps over the lazy dog> (just as it has done here) in Writer it expands to <Fox- the quick brown fox jumps over the laz> (note how it has not removed the key phrase and has dropped the same number of letters from the end of the result. for <jhb-> I get <JhbJohannesbu> instead of <Johannesburg> Only in Writer.
wykidtech: could you test with a fresh master build? https://wiki.documentfoundation.org/Installing_in_parallel/Linux https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/ Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
I have the same problem! Identical, with Kubunu 17.10!
(In reply to Duns from comment #3) > I have the same problem! Identical, with Kubunu 17.10! As Elmar said he did not see the problem in 6.0, would you like to test with it? You might try an appimage for a quick test: http://libreoffice.soluzioniopen.com/
Tried, but the problem remain, identical!
moreover, Elmar did not say that the problem is solved, because autokey in LibreWriter does not work in an acceptable way
Setting to NEW, then
The bug is still here in LibreOffice 6.0.5 (Debian Buster 64, Gnome 3.28.2). But if one installs only the libreoffice packages without the libreoffice-gtk3, Autokey works fine. If one add the libreoffice-gtk3 package, or the libreoffice-gnome, which also installs the gtk3 package, Autokey doesn’t function properly anymore. If one removes it, it works fine again… It would be interesting to know if the same is true with KDE (with package libreoffice-kde)…
It works also in KDE (removing libreoffice-kde4)! Thank you!! The only problem that remains is aesthetic, because in this way (after removing libreoffice-kde4) Libreoffice has really horrible menus...
(In reply to Duns from comment #9) > It works also in KDE (removing libreoffice-kde4)! Thank you!! > The only problem that remains is aesthetic, because in this way (after > removing libreoffice-kde4) Libreoffice has really horrible menus... I completely agree on the terrible aesthetic… Hope this bug will get fixed soon…
I am having the same problem with LO v. 6.0.3.2, Autokey 0.94.1 on Linux Mint 19
Created attachment 144048 [details] example of autokey expansion in LO Writer Created a phrase in Autokey ktt- which should expand to Keirsey Temperament Theory (does it correctly here, and everywhere, except in Writer) The attached doc is simply a repetition of the phrase n-times notice how Writer deals with it differently every time. I have also attached examples using Calc and Impress - there the expansion is correct, consistently, every time. I have tested this in LO 5.1.6.2 Writer It expands correctly every time
Created attachment 144049 [details] example of autokey expansion in LO Calc
Created attachment 144050 [details] example of autokey expansion in LO Impress
Dear wykidtech, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Problem is still present for me. Info from about libreoffice: Version: 6.2.8.2 Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 6; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: es-ES (en_US.UTF-8); UI-Language: en-US Calc: threaded Downloaded from https://www.libreoffice.org/download/ today. Autokey worked perfectly in libreoffice writer for the first say 10 times aprox. Then it stopped working and was back to expanding with errors again. Thanks
(In reply to VH from comment #16) > Problem is still present for me. Have you asked about this from the developer of Autokey-py3?
Have you seen the fix at the comment 9 (https://bugs.documentfoundation.org/show_bug.cgi?id=113842#c8)? For me it worked.
(In reply to Duns from comment #18) > Have you seen the fix at the comment 9 > (https://bugs.documentfoundation.org/show_bug.cgi?id=113842#c8)? > For me it worked. It's not a fix, but a very poor workaround.
(In reply to Buovjaga from comment #17) > (In reply to VH from comment #16) > > Problem is still present for me. > > Have you asked about this from the developer of Autokey-py3? It is not a problem with Autokey-py3. Autokey works perfectly in all the other applications, but libreoffice write.
(In reply to VH from comment #20) > (In reply to Buovjaga from comment #17) > > (In reply to VH from comment #16) > > > Problem is still present for me. > > > > Have you asked about this from the developer of Autokey-py3? > > It is not a problem with Autokey-py3. > Autokey works perfectly in all the other applications, but libreoffice write. Sure, but I guess the dev would be rather interested in hearing about this.
I have found a substitute for Autokey that does the text expansion I need. It is not perfect, but it does the trick :) So if anyone else is having the same problem, check out Espanso: https://espanso.org/ https://github.com/federico-terzi/espanso
Dear wykidtech, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug