SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I too, as willysr, always used rpm2tgz on official RPMS of OpenOffice, and then did installation. Well, and the same problem with OO 3.0: neither navigation keys (up, down etc), no backspace are working.
Well, I actually have read the whole thread and wanted to note:
There are NO official (whatever this means) builds of OpenOffice for Slackware.
Rpm2tgz was the best way, why should I compile something big like OO?
Or why to download from linuxpackages?
So, for the time being I will get back to the stable 2.4.1.
You don't have to *compile* it. You can find someone who at least halfway knows what they're doing and let them write a script to repackage the rpm's into a good Slackware package, or use the package they created from it. That "someone" should be easy to find at this point. ;-)
You don't have to *compile* it. You can find someone who at least halfway knows what they're doing and let them write a script to repackage the rpm's into a good Slackware package, or use the package they created from it. That "someone" should be easy to find at this point. ;-)
Well, I know someone, I checked his site and found there re-packaged OpenOffice (about 150 MB).
I am not too much paranoid, it just a matter of principle: why should I download the same stuff again, just because it is repackaged.
I think the best is to ask:
Could you(or someone) actually tell why rpm2tgz-way did not work, and what should be changed to make it work?
(It's second-best; the best would be to do it myself, and post the results here).
Anyway, thank you, rworkman
Well, I know someone, I checked his site and found there re-packaged OpenOffice (about 150 MB).
:-)
Quote:
I am not too much paranoid, it just a matter of principle: why should I download the same stuff again, just because it is repackaged.
If you've already got the binary tarball of rpm's, then use the build script.
Quote:
I think the best is to ask:
Could you(or someone) actually tell why rpm2tgz-way did not work, and what should be changed to make it work?
Good question, and to be honest, I'm not sure. Installing with "rpm --nodeps" would run the post-install scripts embedded within the OOo rpms, and that *might* make a difference. However, rpm2tgz doesn't read those into the converted package, and neither does my method of conversion, so that doesn't explain the discrepancy. The only other major difference would be the menu entries that I fixed, but that shouldn't make a difference, I don't think.
Anyway, I think I've got the spellcheck problem solved. Will find out soon. :-)
Quote:
(It's second-best; the best would be to do it myself, and post the results here).
If you already have the rpm tarball, you can just get the updated script itself; nothing else changed.
Once I get some confirmation that this works elsewhere (please remove all traces of your old installation first), I'll push an update to SlackBuilds.org.
Actually, the problem is not with rpm2tgz, but with pkgtools. Installpkg and the other slackware package tools use tar version 1.13, and when uncompressing the file:
stripping out the end "L". This causes the problem with arrow keys and backspace. Renaming this file to the correct "default.xml" make the keys work correctly.
People who uses rpm2tgz can try that solution and see if it works
You can also click on the auto spell check button at the main toolbar of OOo 3.0 to activate the feature
For some reason none of this mattered for me. The AutoSpellCheck feature was not working. I'm going to test Robby's new SlackBuild now.
Edit:
Robby's new SlackBuild works great! I just had to swap out the SlackBuild file and rerun it. All three dictionaries were added properly with no intervention by me. I did make sure all remnants of the previous installation were deleted first.
Speaking of which, I solved my problem with the AutoSpellCheck. I figured out that I had to start with fresh OpenOffice settings (ie not import them from OOo 2, which is the default option). If you forget to uncheck the import box then delete your ~/.openoffice.org directory and try again.
Last edited by shadowsnipes; 10-15-2008 at 09:13 PM.
why do you need to add two --shared parameter when adding the extensions?
Good question. I think the answer is "you don't" -- BUT I'm not 100% certain. See, I cheated a bit :-) I told rpm to show me the pre/post-install scripts that it runs (which neither rpm2tgz nor my manual conversion grab), and they were using two "--shared" statements, so I thought I'd be safe and do the same. At this point, I'm not fixing what isn't broken :-)
Robby's new SlackBuild works great! I just had to swap out the SlackBuild file and rerun it. All three dictionaries were added properly with no intervention by me. I did make sure all remnants of the previous installation were deleted first.
Quote:
Originally Posted by Bruce Hill
Works fine here, Robby.
Quote:
Originally Posted by hitest
Thanks, Robby:-) Your new package works fine for me as well.
Okay, thanks for the confirmation, guys. The new build is slated to come out in the next push at SlackBuilds.org.
Quote:
Originally Posted by shadowsnipes
I solved my problem with the AutoSpellCheck. I figured out that I had to start with fresh OpenOffice settings (ie not import them from OOo 2, which is the default option). If you forget to uncheck the import box then delete your ~/.openoffice.org directory and try again.
Interestingly enough, I imported my settings back when I first installed rc1 or rc2, and all is well here. If I get any more reports of this happening, I'll document it in the README, but for now, I'm going to assume (hope?) it's an isolated case.
Actually, the problem is not with rpm2tgz, but with pkgtools. Installpkg and the other slackware package tools use tar version 1.13, and when uncompressing the file:
stripping out the end "L". This causes the problem with arrow keys and backspace. Renaming this file to the correct "default.xml" make the keys work correctly.
People who uses rpm2tgz can try that solution and see if it works
You should not believe everything you read on the internet:
Code:
mingdao@t61:~$ ls -l /opt/openoffice.org/basis3.0/share/config/soffice.cfg/modules/swriter/accelerator/en-US/
total 12
-rw-r--r-- 1 root root 10510 2008-09-30 21:35 default.xml
That was the result of building with Robby's new script,
and installing with:
People who uses rpm2tgz can try that solution and see if it works
****
willysr, this was a good tip, thank you!
In short, I installed OOO 3.0, as usual, per rpm2tgz, and up, down keys etc did not work.
Today I renamed, as suggested,
/opt/openoffice.org/basis3.0/share/config/soffice.cfg/modules/swriter/accelerator/en-US/default.xm
into
/opt/openoffice.org/basis3.0/share/config/soffice.cfg/modules/swriter/accelerator/en-US/default.xml
I started OOO3, up, down keys etc still did not work.
I removed .openoffie.org directory, started OO3 again,
navigation keys, backspace work.
P.S. Auto spellcheck does not work, but I did not try to solve this problem yet.
if the autospellcheck does not work, then you can install the dictionary manually via Tools > Extensions Manager
Well, i do suggest that you try out SlackBuild script instead of relying to rpm2tgz. It works better and you will have better shortcut menus and icons as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.