Re: 4.2.0 Error starting Slackware 14.2 64 bit
Still get an error: The application cannot be started. exception occurred raising singleton "/singletons/com.sun.star.deployment.ExtensionManager": loading component library failed: file:///opt/openoffice4/program/../program/deployment.uno.so I think I'll abandon trying to install this version for the moment and stick with the older 4.2.0 for testing. On 13/1/20 3:00 pm, Yury wrote: (edited the Nabble post, but forgot of course that it doesn't replicate the email.) So, yes, I use rpm2tXz with the following parameters set: rpm2txz -s -S -n -r -d -c -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Cheers -- David Robley A man's best friend is his dogma. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.2.0 Error starting Slackware 14.2 64 bit
(edited the Nabble post, but forgot of course that it doesn't replicate the email.) So, yes, I use rpm2tXz with the following parameters set: rpm2txz -s -S -n -r -d -c -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.2.0 Error starting Slackware 14.2 64 bit
Thanks Yuri Is there a suggested parameter(s) for rpm2tgz missing from your reply? On 13/1/20 2:08 am, Yury wrote: I too am using OOO on 64-bit slackware after converting the RPMs with rpm2txz, only I do it on -current for about a year. And only like minutes ago I was testing literally the same 4.2.0 archive (converted to TXZ) as the one you did. Things went fine both with the blank profile and with my working profile (which has been used before that by the 4.5.0 built from source). On the very very off chance of conversion going badly in your case: I use the set of parameters. -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Cheers -- David Robley CAT.COM started. Computer will hack furball in 5 seconds. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
Matthias Seidel wrote > So this is your private build? > > I would try to enable dictionaries (and maybe category-b) Once you enable category-b on linux, 'configure' demands coinmp with no regard for --disable-coinmp option. If enabling just the bundled dictionaries, 'configure' doesn't complain, but the result does not do auto-hyphenation either. Thanks for answering. Maybe some guys knowledgeable in building on linux would see the topic. -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Update to python-2.17
Hi Pedro, Everything seems to work. Thanks again! Regards, Matthias Am 10.01.20 um 23:18 schrieb Matthias Seidel: > Hi Pedro, > > Am 10.01.20 um 21:17 schrieb Pedro Giffuni: >> On 2020-01-10 14:53, Matthias Seidel wrote: >>> Hi Pedro, >>> >>> Am 10.01.20 um 20:50 schrieb Pedro Giffuni: On 2020-01-10 13:24, Matthias Seidel wrote: > Hi Pedro, > > Am 10.01.20 um 07:14 schrieb Pedro Giffuni: >> Hi again; >> >> On 2020-01-04 05:16, Matthias Seidel wrote: >>> Hi Pedro, >>> >>> Thanks! >>> >>> Unfortunately the build process just stops at some point (on Windows), >>> no error codes I could give you. >> The problems are usually related to getting the patches applied >> correctly. There can be no hunks or mismatches. >> >> I tested them one by one and they should be OK now. Same place: >> >> https://people.apache.org/~pfg/patches/patch-python-2.17.diff > When trying to apply this patch to trunk I get: > > malformed patch at line 2048: Index: > main/python/python-2.7.15-msvs9.patch > > (It would be nice if you could create a Pull Request on GitHub) Indeed that patch causes issues due to Windows LF characters. I overruled the issue in git and sent the Pull Request: https://github.com/apache/openoffice/pull/23 >>> Thanks! >>> >>> What revision is this patch based on? >>> I see a lot of commits that are already in trunk for longer time... >>> (However, they should be ignored when merging?) >> It's straight from recent git clone but I applied the changes manually. >> Some crap crept into external_dps.lst but I cleaned them up with >> successive commits. >> >> Do feel free to ignore any irrelevant change that might have crept in. > I am now building with your latest changes. > > If everything goes well I will merge the PR tomorrow. > > Regards, > > Matthias > >> Pedro. >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> smime.p7s Description: S/MIME Cryptographic Signature
Re: hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
I've checked with the 4.5.0 build from AOO site and yes, the problem's in my build options. Disabling category-b and then enabling hyphenation does not actually build in the hyphenation capabilities (or disables those somehow anyway). -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
Hi Yury, Am 12.01.20 um 18:39 schrieb Yury: > Matthias Seidel wrote >> Most likely something in your profile for 4.5.0 is corrupt. Try to >> rename it to get a fresh one and look if hyphenation is active again. > It's not the profile. I init'ed two profiles from scratch both for 4.2.0 and > 4.5.0, and the same OXT does get the auto-hyphenation in 4.2.0 and doesn't > in 4.5.0. > Now, I'm thinking maybe the problem is in the build options? > > I was configure'ing with (that's only part of the list) > ... > --disable-bundled-dictionaries \ > --disable-category-b \ > --disable-pam \ > \ > --with-jdk-home=/usr/lib64/java \ > \ > --with-system-libs=no \ > --with-dict=ENGB,ENUS,RURU \ > --enable-hyphen \ > --enable-hunspell \ > ... > > How do I check the hyphenation part actually works? So this is your private build? I would try to enable dictionaries (and maybe category-b) You could also try a build from our buildbots: https://www.openoffice.org/download/devbuilds.html Unfortunately I can't help you further with building on Linux. Regards, Matthias > > > > -- > Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
Matthias Seidel wrote > Most likely something in your profile for 4.5.0 is corrupt. Try to > rename it to get a fresh one and look if hyphenation is active again. It's not the profile. I init'ed two profiles from scratch both for 4.2.0 and 4.5.0, and the same OXT does get the auto-hyphenation in 4.2.0 and doesn't in 4.5.0. Now, I'm thinking maybe the problem is in the build options? I was configure'ing with (that's only part of the list) ... --disable-bundled-dictionaries \ --disable-category-b \ --disable-pam \ \ --with-jdk-home=/usr/lib64/java \ \ --with-system-libs=no \ --with-dict=ENGB,ENUS,RURU \ --enable-hyphen \ --enable-hunspell \ ... How do I check the hyphenation part actually works? -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
Hi Yury, There have been no code changes in this respect. Most likely something in your profile for 4.5.0 is corrupt. Try to rename it to get a fresh one and look if hyphenation is active again. Regards, Matthias Am 12.01.20 um 16:48 schrieb Yury: > I'm using the 4.5.0 built from source on 64-bit slackware system. In my > profile I have an extension dealing with Russian hyphenation -- > https://extensions.libreoffice.org/extensions/hyphenations-for-russian/0-0.4 > > The extension works fine in 4.1.* and in 4.2.0 series (I checked with the > fresh 4.2.0 snapshot just an hour ago or so). > But today I've noticed the extension isn't working in 4.5.0 -- the same OXT > opened in 4.5.0 has no auto hyphenations active. The profile is the same in > both cases (4.5.0 and 4.2.0). > > That's rather unintuitive -- why should the extension stop working, if it > has no code inside, only the dictionary data? Now, I notice it's provided in > 8-bit encoding -- maybe those do not work anymore and the utf-8 is required? > > > > > -- > Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
hyphenation dict not working in 4.5.0 (works in fresh 4.2.0)
I'm using the 4.5.0 built from source on 64-bit slackware system. In my profile I have an extension dealing with Russian hyphenation -- https://extensions.libreoffice.org/extensions/hyphenations-for-russian/0-0.4 The extension works fine in 4.1.* and in 4.2.0 series (I checked with the fresh 4.2.0 snapshot just an hour ago or so). But today I've noticed the extension isn't working in 4.5.0 -- the same OXT opened in 4.5.0 has no auto hyphenations active. The profile is the same in both cases (4.5.0 and 4.2.0). That's rather unintuitive -- why should the extension stop working, if it has no code inside, only the dictionary data? Now, I notice it's provided in 8-bit encoding -- maybe those do not work anymore and the utf-8 is required? -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.2.0 Error starting Slackware 14.2 64 bit
I too am using OOO on 64-bit slackware after converting the RPMs with rpm2txz, only I do it on -current for about a year. And only like minutes ago I was testing literally the same 4.2.0 archive (converted to TXZ) as the one you did. Things went fine both with the blank profile and with my working profile (which has been used before that by the 4.5.0 built from source). On the very very off chance of conversion going badly in your case: I use the set of parameters. -- Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.2.0 Error starting Slackware 14.2 64 bit
Renaming ~/openoffice gives the same result. I assume you meant # ldd /opt/openoffice4/program/soffice.bin linux-vdso.so.1 (0x7ffea898) libuno_sal.so.3 => /opt/openoffice4/program/libuno_sal.so.3 (0x7f0e4bff) libsofficeapp.so => /opt/openoffice4/program/libsofficeapp.so (0x7f0e4bd76000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x7f0e4b9be000) libm.so.6 => /lib64/libm.so.6 (0x7f0e4b6b5000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x7f0e4b49d000) libc.so.6 => /lib64/libc.so.6 (0x7f0e4b0d4000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x7f0e4ae9c000) libdl.so.2 => /lib64/libdl.so.2 (0x7f0e4ac97000) libpthread.so.0 => /lib64/libpthread.so.0 (0x7f0e4aa7a000) libcomphelpgcc3.so => /opt/openoffice4/program/libcomphelpgcc3.so (0x7f0e4a75e000) libuno_cppuhelpergcc3.so.3 => /opt/openoffice4/program/libuno_cppuhelpergcc3.so.3 (0x7f0e4a4bc000) libuno_cppu.so.3 => /opt/openoffice4/program/libuno_cppu.so.3 (0x7f0e4a27d000) libdeploymentmisc.so => /opt/openoffice4/program/libdeploymentmisc.so (0x7f0e4a059000) libdeploymentgui.uno.so => /opt/openoffice4/program/libdeploymentgui.uno.so (0x7f0e49de6000) libi18nisolang1gcc3.so => /opt/openoffice4/program/libi18nisolang1gcc3.so (0x7f0e49bdf000) libsfx.so => /opt/openoffice4/program/libsfx.so (0x7f0e49637000) libsvl.so => /opt/openoffice4/program/libsvl.so (0x7f0e49354000) libsvt.so => /opt/openoffice4/program/libsvt.so (0x7f0e48d57000) libootk.so => /opt/openoffice4/program/libootk.so (0x7f0e487db000) libtl.so => /opt/openoffice4/program/libtl.so (0x7f0e48537000) libucbhelpergcc3.so => /opt/openoffice4/program/libucbhelpergcc3.so (0x7f0e482d4000) libutl.so => /opt/openoffice4/program/libutl.so (0x7f0e47fde000) libvcl.so => /opt/openoffice4/program/libvcl.so (0x7f0e479a5000) libvos3gcc3.so => /opt/openoffice4/program/libvos3gcc3.so (0x7f0e47784000) /lib64/ld-linux-x86-64.so.2 (0x55c9ec9ec000) libuno_salhelpergcc3.so.3 => /opt/openoffice4/program/libuno_salhelpergcc3.so.3 (0x7f0e4757e000) libxcr.so => /opt/openoffice4/program/libxcr.so (0x7f0e4731b000) libsvxcore.so => /opt/openoffice4/program/libsvxcore.so (0x7f0e46a76000) libfwe.so => /opt/openoffice4/program/libfwe.so (0x7f0e46805000) libsax.so => /opt/openoffice4/program/libsax.so (0x7f0e465f) libsb.so => /opt/openoffice4/program/libsb.so (0x7f0e4628f000) libsot.so => /opt/openoffice4/program/libsot.so (0x7f0e4603e000) libxml2.so.2 => /opt/openoffice4/program/libxml2.so.2 (0x7f0e45cdf000) libbasegfx.so => /opt/openoffice4/program/libbasegfx.so (0x7f0e45a5a000) libi18nutilgcc3.so => /opt/openoffice4/program/libi18nutilgcc3.so (0x7f0e45846000) libjvmfwk.so.3 => /opt/openoffice4/program/libjvmfwk.so.3 (0x7f0e4562f000) libicuuc.so.40 => /opt/openoffice4/program/libicuuc.so.40 (0x7f0e452fd000) libi18npaper.so => /opt/openoffice4/program/libi18npaper.so (0x7f0e450f6000) libjvmaccessgcc3.so.3 => /opt/openoffice4/program/libjvmaccessgcc3.so.3 (0x7f0e44ef) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x7f0e44c53000) libicule.so.40 => /opt/openoffice4/program/libicule.so.40 (0x7f0e44a22000) libavmedia.so => /opt/openoffice4/program/libavmedia.so (0x7f0e447f9000) libdrawinglayer.so => /opt/openoffice4/program/libdrawinglayer.so (0x7f0e4450e000) libediteng.so => /opt/openoffice4/program/libediteng.so (0x7f0e44149000) libxo.so => /opt/openoffice4/program/libxo.so (0x7f0e43c39000) libfwi.so => /opt/openoffice4/program/libfwi.so (0x7f0e43a11000) libicudata.so.40 => /opt/openoffice4/program/libicudata.so.40 (0x7f0e42acb000) libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x7f0e4284d000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x7f0e42515000) libbz2.so.1 => /lib64/libbz2.so.1 (0x7f0e42305000) libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x7f0e420d2000) libz.so.1 => /lib64/libz.so.1 (0x7f0e41eba000) liblng.so => /opt/openoffice4/program/liblng.so (0x7f0e41c51000) which seems to show no problems? On 12/1/20 6:42 pm, Peter Kovacs wrote: ldd /opt/openoffice4/openoffice.bin Cheers -- David Robley Why is it called tourist season if we can't shoot them? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.2.0 Error starting Slackware 14.2 64 bit
Hmm. I would rename ~/.openoffice However you can check the consistency of OpenOffice. what gives you ldd /opt/openoffice4/openoffice.bin ? Am 12. Januar 2020 09:00:01 MEZ schrieb David Robley : >Thank you for your reply: responses inline below. > >On 12/1/20 5:35 pm, Peter Kovacs wrote: >> I am not sure about the issue you are facing. >> >> Have you Java installed? >Yes - but I hadn't added it to AOO; I did that in the working version, >then uninstalled again, completely wiping anything under >/opt/openoffice4 and re-installed. Now I get a different dialog box >error: >The application cannot be started. >loading component library failed: >file:///opt/openoffice4/program/../program/expwrap.uno.so >> How did you delete the profile? >Simply by renaming ~/.openoffice/4/user >> If the base directory still exist it might be problematic. I am not >sure. >As I mentioned above, the base directory /opt/openoffice4 was empty. I >failed to mention that I use the Slackware package to remove the old >version before installing the new. >> >> >> >> Am 10. Januar 2020 09:50:34 MEZ schrieb David Robley >: >>> OS - Slackware 14.2 64 bit >>> >>> Download location - >>> https://ci.apache.org/projects/openoffice/install/41x/ >>> >>> Downloaded file - >>> >>> >Apache_OpenOffice_4.2.0_Linux_x86-64_install-rpm_en-US_2020-01-05_12:45:50_5a80ab836302b0f575229ae49f451128d5c5932a.tar.gz >>> >>> My install process: >>> >>> Extracted the contents; cd to the RPM directory and used rpm2tgz to >>> convert RPM files to a format compatible with Slackware's installer >>> pkgtool; use pkgtool to install the application. This is pretty much >>> how >>> I have always installed AOO. >>> >>> If I start AOO from the command line using my existing profile, I >get >>> an >>> error on the command line javaldx: invalid settings. User must >select a >>> >>> JRE from options dialog! >>> >>> followed by a dialog box with the error message The application >cannot >>> be started. exception occurred raising singleton >>> "/singletons/com.sun.star.deployment.ExtensionManager": loading >>> component library failed: >>> file:///opt/openoffice4/program/../program/deployment.uno.so >>> >>> If I remove my profile the error message on the command line changes >to >>> >>> Exit 77 /opt/openoffice4/program/soffice >>> >>> followed by the same dialog box error. >>> >>> I note that a .lock file is left in the top level of the profile >>> structure. >>> >>> I can roll back to AOO420m2 Build 9821 dated 2019-10-24 with no >>> problems. >>> >>> Am I missing something simple? >>> >>> >>> Cheers >>> -- >>> David Robley >>> >>> We're staying together for the sake of the cats. >>> > > >Cheers >-- >David Robley > >Why is it called tourist season if we can't shoot them? > > > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org
