[SOLVED] Libreoffice 6.4.5 not working on clicking
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.
Following are the steps which I have taken for Libreoffice .The installation process was smooth without any error.
Code:
[root@slack142test software]$ cd libreoffice
[root@slack142test libreoffice]$ ls
libreoffice-6.4.6-x86_64-1alien.txz
libreoffice-dict-en-6.4.6-x86_64-1alien.txz
libreoffice-l10n-en_GB-6.4.6-x86_64-1alien.txz
[root@slack142test libreoffice]$ installpkg *.txz
Verifying package libreoffice-6.4.6-x86_64-1alien.txz.
Installing package libreoffice-6.4.6-x86_64-1alien.txz:
PACKAGE DESCRIPTION:
# libreoffice (free office suite)
#
# LibreOffice is an Open Source, community-developed, office
# productivity suite. It includes key desktop applications,
# such as a word processor, spreadsheet, presentation manager,
# formula editor and drawing program, with a user interface and
# feature set similar to other office suites. LibreOffice also
# works transparently with a variety of file formats, including
# Microsoft Office File Formats.
#
# libreoffice home: http://www.documentfoundation.org/
Executing install script for libreoffice-6.4.6-x86_64-1alien.txz.
Package libreoffice-6.4.6-x86_64-1alien.txz installed.
Verifying package libreoffice-dict-en-6.4.6-x86_64-1alien.txz.
Installing package libreoffice-dict-en-6.4.6-x86_64-1alien.txz:
PACKAGE DESCRIPTION:
# libreoffice-dict-en (LibreOffice 'en' dictionaries)
#
# This package contains the 'English' dictionary for LibreOffice.
#
# libreoffice home: http://www.libreoffice.org/
#
Package libreoffice-dict-en-6.4.6-x86_64-1alien.txz installed.
Verifying package libreoffice-l10n-en_GB-6.4.6-x86_64-1alien.txz.
Installing package libreoffice-l10n-en_GB-6.4.6-x86_64-1alien.txz:
PACKAGE DESCRIPTION:
# libreoffice-l10n-en_GB (LibreOffice en_GB localization)
#
# UK English language support for LibreOffice.
#
# libreoffice home: http://www.documentfoundation.org/
Executing install script for libreoffice-l10n-en_GB-6.4.6-x86_64-1alien.txz.
Package libreoffice-l10n-en_GB-6.4.6-x86_64-1alien.txz installed.
[root@slack142test libreoffice]$
I try from a non root user as we as from root user accounts.With both users when I click on any icon of Libreoffice Math /Writer or Impress nothing happens.Please guide me is there any thing I am doing wrong or missing like dependencies or whatever ?
I try from a non root user as we as from root user accounts.With both users when I click on any icon of Libreoffice Math /Writer or Impress nothing happens.Please guide me is there any thing I am doing wrong or missing like dependencies or whatever ?
Your installation steps look OK to me; although the commandprompt you show ($) is not the default root prompt (#) of Slackware. Are you running the real Slackware and do you have a full installation of all packages?
Clicking on menu items will not show any error messages, so please open a terminal and type "lowriter", "localc" or "libreoffice" to see what actually happens when you attempt to start one of the applications.
Thanks "Alien" for your kind reply. First I want to appreciate you and your team for such wonderful/marvellous and superb work for Slackware. Really very good work .
Slackware 14.2 is really rock solid.I had download Slackware from http://www.slackware.com/getslack/torrents.php site and during installation I select fullinstall everything. Later I installed multilib for 32 compatibility.
Coming to my point I have installed libreoffice using root account.About the " $ " which you have mentioned was may be due to wrong script in ".bashcrc file. I don't know why it was still show "$ " even I was using root account! I just "#" Remarks all the lines in .bashrc file. Now it is pure slackware default prompt. Anyway .bashrc is not scope of my post. Later may be discuss.
I am attaching the screen print of "lowriter", "localc" or "libreoffice". Would be thankful if your review it and guide me so that I may fix the issue.
I think that you have never upgraded your Slackware 14.2 installation with the patches that are released regularly. If you use slackpkg to maintain your packages, then after selecting exactly one Slackware mirror in /etc/slackpkg/mirrors file and running "slackpkg update && slackpkg upgrade-all" should give you a truckload of updated packages to install.
If you do not use slackpkg then you will have to download and upgrade all these updates manually. You can get a feeling for how many those are when visiting http://slackware.uk/slackware/slackw...ches/packages/ ... it's a total of 141 packages.
Once your Slackware 14.2 is fully up to date, the issue you apparently ran into - your zlib package being too old - will be fixed along with being a lot less susceptible to attacks from outside when you visit the Internet from your computer.
Well sorry I forget to write ,After installation of Slackware 14.2 (64 bit) I create a test account by help of the site https://docs.slackware.com/slackware:beginners_guide and then also update from the mirror site.
If I recall my steps after Slackware installation it was
1- Full Install Slackware 14.2 (64 bit)
2- Install Multilib from http://www.slackware.com/~alien/multilib/
2- Remove the # for the mirror site for fetching updates using # vi /etc/slackpkg/mirrors
3- Use the command # slackpkg update gpg
4- Use the command # slackpkg update
5- Use the command # slackpkg install-new
6- Use the command # slackpkg upgrade-all
One thing I not execute was " # slackpkg clean-system" it was confusing me.So I cancle it.
It was a proper sequence which I have taken above? The orderinging was correct? please guide me so next time I may not repeate same mistake befor updating.
Well sorry I forget to write ,After installation of Slackware 14.2 (64 bit) I create a test account by help of the site https://docs.slackware.com/slackware:beginners_guide and then also update from the mirror site.
If I recall my steps after Slackware installation it was
1- Full Install Slackware 14.2 (64 bit)
2- Install Multilib from http://www.slackware.com/~alien/multilib/
2- Remove the # for the mirror site for fetching updates using # vi /etc/slackpkg/mirrors
3- Use the command # slackpkg update gpg
4- Use the command # slackpkg update
5- Use the command # slackpkg install-new
6- Use the command # slackpkg upgrade-all
One thing I not execute was " # slackpkg clean-system" it was confusing me.So I cancle it.
That's a correct sequence, and the slackpkg clean-system" is not a requirement.
Quote:
It was a proper sequence which I have taken above? The orderinging was correct? please guide me so next time I may not repeate same mistake befor updating.
Perhaps I insult you now by asking the obvious, but insult is not the intention. Just making very sure. When you type these commands... do you actually also type that "#" character at the beginning? Or do you understand that the "#" character is merely the documentation's way of telling you that the command (excluding the "#") should be run as root?
Thanks “Tonus and Alien” for your valuable guidance. Well $ is for normal user who have no rights for administrative task and “ # “ means you are login as a root user which have full rights .
Inside configuration files “ # “ means linux will not read that particular line. In other word it is just like a comments.
Well when I try to see the info of zlib it shows me
Code:
bash-4.3# slackpkg info zlib
This appears to be the first time you have run slackpkg.
Before you install|upgrade|reinstall anything, you need to uncomment
ONE mirror in /etc/slackpkg/mirrors and run:
# slackpkg update
You can see more information about slackpkg functions in slackpkg manpage.
I just uncomment the line by using vi /etc/slackpkg/mirrors
Code:
#----------------------------------------------------------------
# Slackware64-14.2
#----------------------------------------------------------------
# USE MIRRORS.SLACKWARE.COM (DO NOT USE FTP - ONLY HTTP FINDS A NEARB
Y MIRROR)
http://mirrors.slackware.com/slackware/slackware64-14.2/
#
I am very strange that I had already execute the following commands then why not it update the packages that time!
Anyway,I again try the following commands and it successfully run
Following are the last few lines which i am pasting
Code:
Your kernel image was updated. We highly recommend you run: lilo
Do you want slackpkg to run lilo now? (Y/n)
y
Warning: LBA32 addressing assumed
Added Linux *
One warning was issued.
Searching for NEW configuration files
Some packages had new configuration files installed.
You have four choices:
(K)eep the old files and consider .new files later
(O)verwrite all old files with the new ones. The
old files will be stored with the suffix .orig
(R)emove all .new files
(P)rompt K, O, R selection for every single file
What do you want (K/O/R/P)?
o
bash-4.3# slackpkg info zlib
PACKAGE NAME: zlib-1.2.11-x86_64-1_slack14.2.txz
PACKAGE LOCATION: ./patches/packages
PACKAGE SIZE (compressed): 104 K
PACKAGE SIZE (uncompressed): 420 K
PACKAGE DESCRIPTION:
zlib: zlib (compression library)
zlib:
zlib: zlib is a general purpose thread safe data compression library. The
zlib: data format used by the zlib library is described by RFCs 1950 to
zlib: 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format)
zlib: rfc1951.txt (deflate format) and rfc1952.txt (gzip format).
zlib:
zlib: Homepage: http://www.zlib.net
zlib:
PACKAGE NAME: zlib-1.2.8-x86_64-1.txz
PACKAGE LOCATION: ./slackware64/l
PACKAGE SIZE (compressed): 100 K
PACKAGE SIZE (uncompressed): 400 K
PACKAGE DESCRIPTION:
zlib: zlib (compression library)
zlib:
zlib: zlib is a general purpose thread safe data compression library. The
zlib: data format used by the zlib library is described by RFCs 1950 to
zlib: 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format)
zlib: rfc1951.txt (deflate format) and rfc1952.txt (gzip format).
zlib:
bash-4.3#
I am glad to inform that Libreoffice is now working.
Now just summering steps how to install Libreoffice in Slackware 14.2
Code:
1- Full Install Slackware 14.2 (64 bit)
2- Install Multilib from http://www.slackware.com/~alien/multilib/
2- Remove the # for the mirror site for fetching updates using # vi /etc/slackpkg/mirrors
3- bash-4.3# slackpkg update gpg
4- bash-4.3# slackpkg update
5- bash-4.3# slackpkg install-new
6- bash-4.3# slackpkg upgrade-all
One thing more I want to add that for new users there should be a howto regarding to different packages like,Adobe Reader,VLC,Libreoffice etc etc installation. This will give an idea to the new users of Slackware.May be i am unable to read them,if available on net please let me know.It will be a pleasure for me to study it for my own improvement.
Now just summering steps how to install Libreoffice in Slackware 14.2
Code:
1- Full Install Slackware 14.2 (64 bit)
2- Install Multilib from http://www.slackware.com/~alien/multilib/
2- Remove the # for the mirror site for fetching updates using # vi /etc/slackpkg/mirrors
3- bash-4.3# slackpkg update gpg
4- bash-4.3# slackpkg update
5- bash-4.3# slackpkg install-new
6- bash-4.3# slackpkg upgrade-all
In case you didn't you'll want to make sure to blacklist alien and compat32 packages in /etc/slackpkg/blacklist or the next time you run slackpkg, it will overwrite your multilib packages. The instructions are found in the multilib README.
Quote:
Originally Posted by gardenair
One thing more I want to add that for new users there should be a howto regarding to different packages like,Adobe Reader,VLC,Libreoffice etc etc installation. This will give an idea to the new users of Slackware.May be i am unable to read them,if available on net please let me know.It will be a pleasure for me to study it for my own improvement.
I never use Adobe Reader on Linux. Adobe hasn't updated the Linux version for 7 years and they only provide a 32bit version (which means Slackware64 users would be required to run multilib for a pdf reader)! Chrome (which I install using ruario's latest-chrome script) works just fine as does okular.
If someone absolutely needs VLC (I'm not a fan of VLC... I don't really remember why, but maybe they were crap when I first switched to Linux and I got on the mplayer bandwagon there and have been plenty happy), then they can either go through the insane dependency list on SBo or use Alien's VLC and grab the few dependencies required there.
If you feel that a howto would be beneficial for this, feel free to write one on SlackDocs! We're always looking for new contributors on there.
Thanks for your replay. Though my problem has been solved by all of yours valuable guidance and I appreciate them. Well few things which are indirectly connected with by post and I want to clear its concepts.
What is the purpose of /etc/slackpkg/blacklis file ? Why we use it ? The thing which I have understand is to prevent to install any particular package when applying updating command ? i.e
Code:
bash-4.3# slackpkg update
.
Would be glad if you enlighten on blacklist file .
2-Is possible to install okular in xfce or it is purly design for kde ?
3- Regarding to VLC must windows users prefer it may be it support all media extensions like avi,mp3,mp4?.I have not yet tried "mplayer" but am sure it will be batter than VLC.
Yes it will be a pleasure for me to contribute on SlackDocs so others may also get benefit from it.
thanks in advance.
1. slackpkg will "upgrade" packages that exist on the server that are different than what you have installed. Alien Bob's multilib will replace stock packages and the next time you run slackpkg, it will present those packages to be "upgraded" back to their stock versions, which will break multilib. Putting those packages in the blacklist will prevent them from being upgraded.
2. Okular is included with a full Slackware install and will function within xfce. If you didn't install KDE, then okular may or may not work. I'm not sure. Since Slackware expects a full install, dependencies for individual packages aren't provided, so you'd just need to install okular, try and start it and see if you can look at any error messages to determine what files are missing, then track down the package that provides that file and install it. It is much easier to just install KDE, even if you don't plan to use it, just to make sure all dependencies are met.
3. I honestly don't know if mplayer is better than VLC. I've not really used VLC in probably over a decade, so hopefully it's improved since the last time I used it. mplayer itself is commandline driven, meaning it doesn't have a GUI other than to show the video (it does come with gmplayer, which is a pretty limited GUI and I don't recommend it). mplayer has a plethora of hotkeys, so once you learn them, you can do everything you need with the keyboard. However, most users will use another GUI that will work with mplayer. My preference is smplayer. It's simple to build, easy to use, but still supports the power of mplayer (changing all sorts of video options).
What does this have to do with the topic? Nothing.
OK, boy, what architecture you selected in SlackBuid.sh today, if all 32-bit dos not work now ? Nothing.
All was changed.
There this lib ? I can say. LibreOffice was report in site page, i remember..
what mr.Alien build. bla bla bla.., but where go lib* ? to mr.Alien. You is only one ?
Where dos lib's today ?
All known and all not speak.
Lib is SHARED. This understand ? And SlackBuild script is a quest game.
But $PATH is /usr/lib or /usr/lib64 but application use /usr/shared $PATH.
Where is today ?
I think it like a simple: if $ARCH is not a $x86_64 th echo "error",
and you mr.Alien speak about this more one time, in this blog and mach more.
Compilation is trivial. ./configure && make && make install
What rigth ?
You messead up a Slackware Linux distibution with some one else.
Thank you for understanding.
Last edited by Roman Dyaba; 09-23-2020 at 04:18 PM.
Reason: just add
To be honest, I did not understand a word of what you meant to say.
I think Google translate would do a better job if you enter your russian text in there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.