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.
Maybe I misinterpret the instructions for the new improved method. It seems we should take a binary package (the same tarball whose content is rearranged to create the apache-ant package that was meant to be pre-installed to build LO) and, rather than installing it in the usual way (effectively unpacking it at /), it is unpacked somewhere else (/tmp) and the SlackBuild is modified to point to the new location.
I'm struggling to see much advantage in this new method. I guess, since apache-ant is not officially installed, there's the potential saving of ~42M of disk space if later removal of the version unpacked in /tmp is remembered (not mentioned in the method description however). Just as easily, the officially installed apache-ant package could also be uninstalled after building LO, resulting in exactly the same saving.
chris
I don't agree with you, but everyone has their own opinion. There is no clear documentation why this package needs to be installed at first place. If you look at the build script, you will see many other packages that are also not used by the standard installation and they are put in the /tmp directory and are only needed to build / compile the libreoffice project, and why this package must be installed in this case. For what reason ?
I wouldn't install any packages to a system that I might forget, it's not used for any of the other packages and might get compromising security.
I'm unable to build the libreoffice-7.4.1.2 on slackware current64.
I receive a error:
checking whether clang is already ccached... no
checking whether clang++ is already ccached... no
checking whether to enable gpgmepp... yes
checking which gpgmepp to use... external
checking for gpgme++/gpgmepp_version.h... yes
checking for progress_callback in -lgpgmepp... no
configure: error: gpgmepp not found or not functional
Error running configure at ./autogen.sh line 322.
sed: can't read Makefile: No such file or directory
libreoffice.SlackBuild FAILED at line 1445
I don't agree with you, but everyone has their own opinion.
Yes, I can definitely agree with you on that.
Quote:
There is no clear documentation why this package needs to be installed at first place. If you look at the build script, you will see many other packages that are also not used by the standard installation and they are put in the /tmp directory and are only needed to build / compile the libreoffice project, and why this package must be installed in this case. For what reason ?
I'm not part of LibreOffice dev team, so can't really say. My assumption is that it is needed up front because it is one of the building tools, not just a feature for the final package.
Quote:
I wouldn't install any packages to a system that I might forget, it's not used for any of the other packages and might get compromising security.
I'm not so concerned about compromising security in this way. Nevertheless I can see that it would be neater if packages used only for building could be removed when no longer needed. It's an issue for many SlackBuilds but relatively easy to fix in this case, so I'll think about it some more for the SlackBuild at SBo.
Quote:
I'm unable to build the libreoffice-7.4.1.2 on slackware current64.
I receive a error:
checking whether clang is already ccached... no
checking whether clang++ is already ccached... no
checking whether to enable gpgmepp... yes
checking which gpgmepp to use... external
checking for gpgme++/gpgmepp_version.h... yes
checking for progress_callback in -lgpgmepp... no
configure: error: gpgmepp not found or not functional
Error running configure at ./autogen.sh line 322.
sed: can't read Makefile: No such file or directory
libreoffice.SlackBuild FAILED at line 1445
I think the SlackBuild needs to be updated for 7.4 series which no longer uses autogen.sh (instead already has a usable configure script).
I was able to compile the project on current.
Slackware-15.0 is using gpgme-1.16.0-x86_64-3.txz, but on Slackware-current the package is upgraded to version 1.18. Apparently there are some changes.
I disable the system package from build script so the libreoffice.SlackBuild to able use the package from archive which is 1.16
Any idea where to find ALL of the config files for libreoffice? I want to annihilate it entirely and start over. just removepkg doesnt clean it ALL OUT. I deleted everything in .config for libreoffice and that doesnt sanitize it.
Reading the links above, it looks like ~/.config/libreoffice is the right place to start. However there is mention that some properties are retained in documents themselves.
When I check paths in my use profile, I see "My Documents" is at ~/Documents - quite separate from ~/.config/libreoffice. Perhaps renaming ~/Documents would help your situation?
it looks like ~/.config/libreoffice is the right place to start. However there is mention that some properties are retained in documents themselves.
I got some things fixed with that.
A recent problem arising is that LibreOffice apps are starting in a tiny sliver of a window. I run two big monitors and I want things to start maximized. I don't find this setting.
A recent problem arising is that LibreOffice apps are starting in a tiny sliver of a window. I run two big monitors and I want things to start maximized. I don't find this setting.
I've been having this problem for quite a while, too. I noticed, also, if they load maximised (such as from document recovery remembering you had them maximised last time) and you drag them away from the top of the screen without explicitly unmaximising them, they turn into an even smaller sliver that you can't resize, forcing you to go into the taskbar and find the "unmaximise" option there, resetting them to the larger sliver that you can resize. It's a really weird issue.
The last post suggests it could be KDE specific? However, I see that murdo is running xfce, so maybe not.
Description is very similar indeed, and length of time matches roughly how long I can remember this being an issue.
Thought it could be to do with my theme - though running Xfce, I use the Breeze theme, which is by KDE - but I just played around with a few other themes and the issue seems to be present on all.
I had a similar issue and so did Richard Herbert -- Alien Bob's Latest LibreOffice 7.4.1 started up minimized.
My issue only affected scalc and was of my own making -- I had an ancient shell script wrapper ( /home/local/bin/scalc ) that was running: exec /usr/lib64/libreoffice/program/scalc -–calc “$@” # note the --calc arg
I removed the erroneous --calc Arg and fixed my minimized scalc
YMMV, depending on how long you've been using LibreOffice and if you've had any previous issues with it. As my first experience with LO in Linux is with version 7.4.1, it dawned on me to search AlienBOB's blog for previous troubleshooting tips.
I've been using LO for 8+ years. This minimized window at startup nuisance is a recent event but not sure when it started. I may have thought it was my fault at first and just tolerated because too busy to work on fixing it. Later I decided I'd had enough. I havent found a fix but I am sure it's because some unreachable setting is set the way some not me wants it. Just need to find how to customize it.
Yup, that minimized window has been driving me 'round the bend. Tried all the settings in profile.d/libreoffice.sh but to no avail. I like apps starting full screen too. I'll minimize them when/if necessary.
Right click on the window title bar'
Select more Actions
then Configure special application settings
then Add property
scroll down and add maximized vertically
add maximized horizonally
then select Force,
Apply and OK
then the next time you open a file, it will open maximized after slight pause.
Right click on the window title bar'
Select more Actions
then Configure special application settings
then Add property
scroll down and add maximized vertically
add maximized horizonally
then select Force,
Apply and OK
then the next time you open a file, it will open maximized after slight pause.
I think it's a kludge but it works.
Well kludge or not, it works fine so thank you very much sir.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.