Created attachment 156166 [details] Error message shown when AltSearch is invoked This bug pertains to LO Writer Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group which was installed together with Xubuntu 18.04.3 LTS currently running linux kernel 5.0.0-36-generic x86_64. I frequently use the extension AltSearch.oxt version 1.4.1 (unfortunately I can't communicate with its Czech developers). For one user on this computer, AltSearch works flawless. For another user, it stops with a Basic Runtime error, see attached screenshot. I think, it has worked before. Any idea, how to get out of this bug? Despite of that, LibreOfficeWriter works fine for this user account. BTW: the functionality of AltSearch is great and one should consider to implement its functionality in LibreOfficeWriter itself.
On pc Debian x86-64 with master sources updated today, I installed 1.4.2 version of the extension from https://extensions.libreoffice.org/extensions/alternative-dialog-find-replace-for-writer I noticed these logs on console: warn:configmgr:634432:634432:configmgr/source/xcuparser.cxx:156: bad set node <prop> member in "file:///home/julien/lo/libreoffice/instdir/program/../program/../user/extensions/shared/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/luj6kj7l.tmp/addon.xcu" warn:configmgr:634432:634432:configmgr/source/xcuparser.cxx:901: ignoring modify of unknown set member node "ToolBarItems" in "file:///home/julien/lo/libreoffice/instdir/program/../program/../user/extensions/shared/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/luj6kj7l.tmp/addon.xcu" Anyway, I relaunched Writer but some text in a brand new doc and could use this extension without warning. Could you provide minimum step by step process to reproduce this? Also could you upgrade to 6.3.3? Indeed 6.0, 6.1 are EOL and 6.2 branch will be EOL in 2 days. Also, uninstall the extension and install last version 1.4.2
After removing the old version 6.0.7.3 and installing Version: 6.3.3.2 Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded instead and after installing AltSearch 1.4.2 instead of AltSearch 1.4.1 the same bug happened for one user and it did not happen for the other one, both working on the same file. Ten error message window (showing code of AltSearch) was exactly at the same position. This is of course hard to analyze! Is there something I can reset or replace in the profile of the user who encounters the bug. What files should I copy from the user for whom AltSearch works to the other user's profile?
(In reply to Adalbert Hanßen from comment #2) > After removing the old version 6.0.7.3 and installing > > Version: 6.3.3.2 > Build ID: a64200df03143b798afd1ec74a12ab50359878ed > CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; > Locale: de-DE (de_DE.UTF-8); UI-Language: en-US > Calc: threaded > > instead and after installing AltSearch 1.4.2 instead of AltSearch 1.4.1 the > same bug happened for one user and it did not happen for the other one, both > working on the same file. > > Ten error message window (showing code of AltSearch) was exactly at the same > position. > > This is of course hard to analyze! Is there something I can reset or replace > in the profile of the user who encounters the bug. What files should I copy > from the user for whom AltSearch works to the other user's profile? What about uninstall Altsearch, rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and reinstall Altsearch? Also, do you reproduce this with a brand new empty doc? If not, would it be possible you attach an example after having sanitized it? (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)
After renaming the user profile directory to something else I restarted LO Writer. I had to reinstall AltSearch.oxt and it worked fine. However I had to re-enter all replacement batch commands. Is spellcheck-correction dictionary part of my user profile and where do I find that (in order to transplant it from the renamed user profile).
(In reply to Adalbert Hanßen from comment #4) > After renaming the user profile directory to something else I restarted LO > Writer. I had to reinstall AltSearch.oxt and it worked fine. > > However I had to re-enter all replacement batch commands. > > Is spellcheck-correction dictionary part of my user profile and where do I > find that (in order to transplant it from the renamed user profile). Great! In https://wiki.documentfoundation.org/UserProfile, there's a list of dirs at paragraph "User profile content", you can try to retrieve "autocorr" and "autotext" ones from wrong LO profile. You can also test the reverse: - use wrong LO profile - retrieve registrymodifications.xcu from brand new LO profile
When reporting a bug, one of questions is whether you reseted user profile. If not doing so, you are practically misusing Bugzilla as a support, which is not. I will close this one.