Installing Libreoffice in Ubuntu

[Tom_Davies1]

Hi
+1
Although we often disagree with each other and have heated arguments at
times i have a lot of respect for the technical support Andreas gives and
also for his links to or suggestions of other places that give good
support.

He is a classic example of someone who works in both communities. Not all
have the same attitude (of course) but his way has a lot of energy about
it, which is not always easy to be comfortable with, but his way does seem
to be an effective driving force at times.

I really like Zen-Wiz's script that does the same job as Andreas'
command-line. Instead of having to type in the same commands each time you
would just double-click on the script file. If the script is not already
in the "Extensions" library;
https://www.libreoffice.org/discover/templates-and-extensions/
then i hope he is is generous enough to add it in. It is not really an
Extension as such but having a 3rd "App Store" type of place might be
tricky to arrange.

I keep meaning to add his script to the wiki-page;
https://wiki.documentfoundation.org/Documentation/Install/Linux
if that hasn't been done already and i hope it gets added to the relevant
page on the official website too - preferably as both a downloadable file
and as just plain text on the page itself.

I'm fairly sure ZenWiz would be happy with that but it would be nice to
know that we can do that and use the Creative Commons CC-by-SA or similar
license (such as LGPL or MPL) so that people can modify and re-release in
other places as well as just using it.

Wrt the 3 "package managers" you named; The Software Centre, Synaptic and
"apt-get" - Yes they are 3 ways of doing the same thing. Each has it's own
advantages. The 2 Gui ways are easier for point&click users. The Software
Centre is good for installing entire programs that consist of many parts;
such as LibreOffice, MegaGlest, Wesnoth and so on. Synaptic and "apt-get"
are better for adding individual add-ons, extra libraries for extra
functionality, codecs, specific fonts, command-line tools. Apt-get has
commands to clean and remove temp files created when downloading and
installing things.

Synaptic and "The Software Centre" actually use "apt-get" to do a lot of
their work but they 'just' put a prettier face on it to make it easier for
point&click users. Ok, they often do a lot more than that but it's the
easiest way of thinking about it.

So i might use The Software Centre to install LibreOffice, a camera and
Gimp - then turn to Synaptic to add extra features and fonts - and then use
"apt-get" to clear all the cruft away. I could probably do the whole job
from any 1 of them but this way i have used each package-manager for what
it does best.

Regards from
Tom

[Villeroy]

Thank you for the positive feedback. I hope you noticed the correction of Oct
10, 2015; 1:12pm by Jean-Baptiste Faure-3 that there is no
desktop-integration subfolder anymore. Well, there used to be a reason why
it was organized this way, .... anyway.

If the file /usr/bin/soffice does not exist, there should be no problem.
Run dpkg -i *.deb without additional switch which will include the desktop
integration package.
If you don't want any desktop integration because you want to use the new
suite as a secondary suite, rename/remove the desktop-ingegration.deb file
_before_ running dpkg and everything *should* be fine IMHO.

[Tom_Davies1]

Hi
Yes the separate sub-folders for different Desktop Environments was a
work-around for some intractable problem which did eventually magically
unravel and get fixed.

I can't remember exactly when, maybe 4.2.0 or 4.3.0 - it was just after i
found out about the work-around and was still struggling with it at each
new install.
Regards from
Tom

[cornouws]

Agreed, but not, and I am expressing my own opinion, to the detriment of
dropping a software behaviour nuke on the users/admins.

I hope that, compared to functionality in other software and on other
devices, most changes will not be experienced as such
This of course apart from unwanted side effects.

Sure, but both of these focus on at least LO 4.4.8, from my reading of
their respective websites. That is not an "old" version, it is the
latest version from the Still branch.

Those offer multiple years support. Much longer than the say 9 months
life cycle of normal LibreOffice.

Cheers,

Cor

[Tom_Davies1]

Hi
Many Gnu&Linux distros offer their own somewhat independent support through
their own forums, mailing lists and bug-report systems.

That type of support is not available to Windows users and may not be
available to Mac people.

However it is true that there are many other support systems available and
those are (hopefully) available for all OSes. There may be local support
such as a shop or relative who understands one OS better than others.

All support from TDF is available to anyone regardless of which OS so that
give Gnu&Linuxs users yet another set of places to get support from. It's
usually helpful if we know which OS or at least platform in order to be
able to give more specific and relevant support rather than talking in
general terms. However this seldom includes much help for those who are
stuck on older versions.

Also there are professional support services which can be paid for. Again
these services can often provide support for a variety of platforms and
OSes. This often includes tier 3 (or level 3) support so that might well
include support for older versions.

So one of the few places that doesn't support the notion of a "Long Term
Support" type release is TDF itself! TDF say it cant be done. Other
places just get on with it and do it.

Regards from
Tom

[iplaw67]

FWIW, and I can't comment on CIB supplied versions as I haven't tested
them, but the versions on the AppStore supplied by Collabora come with a
number of their own specific bugs that are not found in the TDF
downloadable versions.

I see no business rationale in paying for a product to gain bugs that
aren't in the freely downloadable version. After all, the aim is not to
have more than those that are in said freely downloadable product, surely ?

To top it all, I end up triaging those extra bugs on top of the QA
triaging I do on the TDF downloads because people add them to LO
bugzilla

Anyway, getting largely off topic, so signing off here.

[Tom_Davies1]

Hi Cor

LibreOffice has many advantages. One is the fast-paced development cycle.

As with all projects there are advantages and disadvantages.

One of the few disadvantages with LibreOffice is it's lack of an official
LTS. Hopefully people who have a strong need for an LTS are able to find
some compromise or an alternative. There are options out there! One is to
use OpenOffice but, as mentioned by other people, that carries a whole raft
of other problems.

My personal preference is to give my clients the "Still" branch or leave
them with an older version. I've never had any problems with any of the
older versions. It seems that about 1/year there is some security issue
but none of my clients have had any problems even with versions that are
years old. On my own machine i try to use the "Fresh" branch in order to
try to find problems with it but again i seldom seem to find anything to
grumble about.

For me LibreOffice is perfect. For my clients "Still" branch is best.

However when i am forced to use OpenOffice i am fairly happy with that
too.

The only time i am really unhappy is when i have to go back and use
Microsoft Office. Their UI changes too much in each release, it's too
heavy and slow, the resulting documents often need some tinkering to get
them up to standard, the format can't be used by other software or even
other versions of itself ... and the list of problems just goes on and on.
People who say they prefer it often ask me for advice on how to do even
quite simple things and i can usually show them but whatever their problem
the simplest answer is usually just to move away from MS Office!

For me the struggle is NOT us against OpenOffice (or KOffice, Caligra,
Gnome Office, Google-docs or others). Each one has it's niche and covers
most of the middle ground extremely well too. If all the rest of the
entire world used OpenOffice or one of the others then it'd be quite fine
with me as long as i was allowed to use LibreOffice = and it would be much
easier to collaborate with everyone else. So for me the struggle is all of
us against the ones who focus on using proprietary formats.

For me, and i suspect quite a lot of the most vociferous detractors here,
the only real problem with LibreOffice is that it's sooo close to being
perfect but just misses by a frustratingly narrow margin.

Many regards from
Tom

[Tom_Davies1]

Hi
As you've probably noticed this mailing list often pulls in at least 2,
often surprisingly opposite directions.

* Technical Support
* User Support

Often those who do an excellent job near the extremes of one find
themselves infuriated by those who work near the extreme of the other.

I tend to aim at "User Support" but i am painfully aware that i often fail
at this. I aim to stand-up for individuals, especially new ones because
they often bring in new ways that might well succeed where current or old
strategies may have failed at some old problems. Again i'm aware that i
often fail at this and that it's often even back-fired somewhat painfully.

So i like the community here on this list and i like it that this mailing
list's unique community sometimes has a different viewpoint than the other
mailing lists. I've also been very impressed by people who came in here
thinking they knew nothing but then found their way into other teams, such
as Marketing, Design, Documentation, QA, List-Moderators or/and just ended
up helping people here.

TDF needs people who can't code to help in the many other things that need
to be done. Even QA can usefully do with more non-coders and not just for
admin type roles. Each of us could probably find some other team where we
could help TDF quite a bit with surprisingly little effort.

Also each of us could probably find a niche in one of the other teams where
we get a lot of reward and satisfaction - maybe even learn quite a bit in
the process.

Many people here already do so. Some tried out a few different teams
before finding somewhere they felt most comfortable. Some are still on
many other teams. Some liaise between different projects, such as between
us and the Caligra Office Suite (a fork of KOffice).

Regards from
Tom

[Charles-H_Schulz]

Charles,

I do not know where you got that support and security updates are

only available on Linux. That is factually wrong and serious bullshit.
Get your facts straight: support is the same for the three officially
supported platforms: Windowslinux and OS X. Remember that many code
contributors have customers too.

I would be interested in learning where longterm support for "older"
versions of LibreOffice on OSX which involves security updates and bug
fixes is generally available. It would certainly help me explain to
people on bugzilla using older versions of LibreOffice on OSX why there
is no hope of bug xyz being fixed unless they upgrade both their OS and
install the latest version of LibreOffice.

Indeed if you speak of older versions (as in versions currently not availabe as one of our two branches) , the LibreOffice project itself has no support for this. Companies such as CIB or Collabora usually do on all platforms.

Now I realize there may be frustrations involved by handling upgrades but you would still deploy upgrades anyway regardless of the software. Would automatic incremental updates do the trick for you?

If I look here :

https://www.libreoffice.org/get-help/system-requirements/#Apple

Either I can't read properly or else the information at that place is
incorrect. As I was unable to find anywhere on the LibreOffice website
that indicates that there is support available for "older" versions of
LibreOffice on OSX < 10.8, then may I assume that my facts are indeed
right after all ?

Your facts are wrong as you expect from LibreOffice what you don't expect from any other software, which is ad vitam support for free by the community. In short you expect "the butter, the money for the butter, the smile and thanks from the dairy merchant" all at the same time.

So yes indeed, LibreOffice does not support all its versions... but then who does ? Microsoft ? Mozilla? Does AOO support the 3.3? Does it patch the 3.2.1? No? How outrageous.

Best,

Charles.

Alex

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted

Hello Alex,

[Charles-H_Schulz]

Hi
Many Gnu&Linux distros offer their own somewhat independent support
through
their own forums, mailing lists and bug-report systems.

That type of support is not available to Windows users and may not be
available to Mac people.

However it is true that there are many other support systems available
and
those are (hopefully) available for all OSes. There may be local
support
such as a shop or relative who understands one OS better than others.

All support from TDF is available to anyone regardless of which OS so
that
give Gnu&Linuxs users yet another set of places to get support from.
It's
usually helpful if we know which OS or at least platform in order to be
able to give more specific and relevant support rather than talking in
general terms. However this seldom includes much help for those who
are
stuck on older versions.

Also there are professional support services which can be paid for.
Again
these services can often provide support for a variety of platforms and
OSes. This often includes tier 3 (or level 3) support so that might
well
include support for older versions.

+1 good description.

So one of the few places that doesn't support the notion of a "Long
Term
Support" type release is TDF itself! TDF say it cant be done. Other
places just get on with it and do it.

Also you might add that TDF does not offer LTS because TDF is not a business and therefore has no incentive in a LTS version which only makes sense if you monetize it. The poster example of this is Canonical and Ubuntu LTS. Canonical makes money on LTS and is only able to do so because the LTS itself is a profitable business. Otherwise you would not even hear of it. Businesses looking for something very similar to a LTS version of LibreOffice can contact our certified developers and their companies though.

Best,

Charles.

Regards from
Tom

>
>Suffice it to say that Andreas is a vociferous participant in this
>discussion list, but that doesn't make his criticisms any less
>justified
>or relevant. What he dislikes is badly implemented change for

change's

>sake, and that is an inherent problem in LibreOffice's development.

The

>project from the start has sacrificed behavioural stability with

regard

>to the end user for feature creep. We are quite clearly in the

"bazaar"

>mode of the cathedral and bazaar dichotomy, where no overlying
>dictatorship (benevolent or otherwise) exists to govern the

direction

>code development should take. This has positive and negative effects

-

>the positive being that people can just turn up and work on the

thing

>they want to implement - the negative being the law of unintended
>consequences, or collateral damage, i.e. bugs newly introduced that
>change long standing behaviour to which users have become

accustomed.

>
>Fortunately, there are still people like Andreas to call the code
>contributors out on those decisions.
>
>I would suggest putting yourself in an admin's place where they have
>probably invested long hours in developing a turnkey
>OpenOffice/LibreOffice solution for their group of users, then

finding

>one day that that longstanding behaviour has changed because someone
>else has not thought through a code change due to the tentacular

nature

>of the code base with no one having an overarching knowledge of it

all,

>and you will perhaps understand Andreas' frustration (which I happen

to

>share and have voiced it on the mailing lists in the past).
>
>At present, long term support (bug fixes, security updates) for

older

>versions is to my knowledge only available on Linux and only with
>regard
>to certain distributions. If you are not on Linux, then you are

stuck

>playing catch up with versions that successively introduce new bugs

or

>behaviours that don't get fixed for at least several point releases,

or

>for certain OSes, over multiple major version releases. Steve's

mention

>in this thread of EPS support and printing is just yet another
>illustration of a change that was made that has a huge impact on
>non-Linux OSes - all because someone thought it would be a good idea

to

>make that change without providing a solution for all platforms.

Video

>support in Impress is yet another issue that got significantly worse
>with the move to the 4.x branch. What was the message we gave to our
>users ? "Suck it up." There is only so much of that that users and
>their
>admins are prepared to do, and in the end, it won't be surprising if
>people switch to another product that offers them greater longterm
>stability where such changes are less invasive or devastating to the
>day-to-day running of the organisation.
>
>
>Alex
>
>
>
>
>
>
>
>
>
>--
>To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
>Problems?

http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
>Posting guidelines + more:
>http://wiki.documentfoundation.org/Netiquette
>List archive: http://listarchives.libreoffice.org/global/users/
>All messages sent to this list will be publicly archived and cannot

be

>deleted

Alex,

I do not know where you got that support and security updates are

only

available on Linux. That is factually wrong and serious bullshit.

Get your

facts straight: support is the same for the three officially

supported

platforms: Windowslinux and OS X. Remember that many code

contributors have

customers too.

As for calling developers on their responsibility that is quite easy
especiaIly when that call takes an oracular form: doing it in such a

way is

one of the things defining a troll. I wonder if Andreas does the same

for

AOO ? Something tells me that is not the case but I could be wrong.

Best,

Charles.
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma

brièveté.

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:

http://wiki.documentfoundation.org/Netiquette

List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot

be

deleted

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted

Hello Tom

[italovignoli]

During the last four years I have helped to migrate to LibreOffice
several Italian organizations - especially public administrations - for
a total of over 30,000 PCs. Today, I am helping the Italian Defense to
migrate to LibreOffice 150,000 PCs.

I might be incredibly lucky, but I have never experienced significant
stability issues with LibreOffice, since version 3.5. Of course, when I
say "I have never experienced" I mean that none of the organizations I
have helped has experienced significant stability issues. Again, we
might be extremely lucky here in Italy.

[planas]

Hi

Looking at the subject line I am confused. Ubuntu ships with a version of LO in each release and LO is in the official Ubuntu repositories. So what was the actual question, which was never clear to me. The only question that made any sense was how to install a Ubuntu ppa for the latest stable LO release but that did seemed to be the question. Adding a ppa is an easy process.

AFAIK most Linux desktop distros ship with LO as the office package with a few shipping with Calligra. In either case the other is often in the distro's repository and is usually trivial to install using the distro's package management tools.

Jay

[planas]

Hi Italo,

The only consistent complaints I hear about LO is that the UI is different from various MSO office versions and concerns about handling MSO file formats. The first is complaint was often due to user unwillingness to learn anything new - not an uncommon problem. This is not an LO specific issue. The second issue, to me, is more legitimate. I have seen many proprietary document formats for office documents come and go over the last 30 years. I can appreciate the concern about being able to open documents in a non-native package in the future.

I have not heard of any (my very limited sample) stability issues that could be attributed to LO. The stability issues I was seeing were Windows issues seen in many packages.

I suspect your stability experience is the norm, LO is very stable. If there are issues they are often user unwillingness to change or system problems outside of LO.

Jay

[Villeroy]

Andreas Säger wrote

If you don't want any desktop integration because you want to use the new
suite as a secondary suite, rename/remove the desktop-ingegration.deb file
_before_ running dpkg and everything *should* be fine IMHO.

Oh, that was sloppy posting because renaming won't prevent that file from
being installed together with the other *.deb files (unless you renamed the
deb extension). This _may_ fail if there is some other suite installed.

1) Do nothing and run sudo dpkg -i *.deb if there is no other suite owning
/usr/bin/soffice

2) Move the desktop-integration.deb to the trash bin if you don't want the
desktop integration for this office suite.

3) If you want desktop integration for the newly installed suite AND there
is an /usr/bin/soffice file from another suite, then you should indeed make
a subdirectory and move that particular deb file before running sudo dpkg -i
*.deb in the DEBS directory without additional switch. This should run
without error. And then run sudo dpkg -i --force-overwrite *.deb in that
subdirectory in order to make this office suite the primary one overwriting
any /usr/bin/soffice. The overwrite switch applies only to this particular
package with this particular problem when there is another suite owning
/usr/bin/soffice.

The desktop-integration*.deb should reside in a separate subdirectory but
the LO guys always know better. Simply applying the overwrite switch to all
the *.deb packages may resolve unforeseen dependencies by overwriting
essential files of alternative office suites which would damage these
installations.

Thank you for your attention.

[Tom_Davies1]

Hi
No need to "beat yourself up over it". Your initial post made enough sense
that people were able to run with it. Effectively it was little more than
a typo and under a stress that none of us enjoy but a few have had to
endure = so i think we can appreciate it being such a tiny and
understandable inaccuracy.

So, both your posts are very much appreciated - as always.
Many regards from
Tom

[Tom_Davies1]

Hi
+1 to both points.

The UI issue is cropping up more often but many people, get over their
initial dislike and prefer the return to sanity because it makes it easier
to find things and easier to learn new stuff.

The formats issue is mostly one of perception. People still believe the MS
formats have longer longevity despite the fact they, almost daily, find
problems sharing such files with each other.

Just as Italo said and Jay agreed i've never had problems with any version
of LO myself (or with clients) but i know there have been many over the
years and even a couple of theoretical security issues. However i (well,
my clients) run into problems with MS Office quite often, despite seldom
actually using it myself. I originally joined this mailing list to learn
about current problems and work-arounds in order to be ready for client's
questions. I've always been over-prepared as a result = so thanks to all
of you for that :))
Regards from
Tom

[JOE_Conner]

Thanks Tom. We try.
Blessings, Joe Conner, Poulsbo, WA USA

[Tom_Davies1]

Hi
The original question was about getting the newer versions installed.
Ubuntu, especially their LTSes, tends to have quite old versions.

Many people take a while to realise they are fine to keep using older
versions, even ones that are no longer officially supported. Others enjoy
being on the bleeding edge or as close as they can get, possibly for the
thrill of it but maybe because it can be so dangerous with proprietary
software.

There are PPAs for both branches (i believe so anyway there were last time
i looked) and those can be used for Ubuntu, Mint and presumably many other
distros in the Debian family. It's also possible to install the "upstream"
version directly from the website and both Andreas and ZenWiz gave us good
instructions for doing that. Then the whole thread took a left turn and
got (imo) very exciting and interesting
Regards from
Tom

[Tom_Davies1]

Hi
"Thanks for the flowers"/approval which i've snipped. It's a shock to
finally agree on something! :))

The LTS approach was a new way of dealing with an old problem. The old and
still current problem is that projects are pulled in 2 opposing
directions;
1. exciting and new developments, fashion, bling
2. stay with something familiar and see it mature. NOT having to
constantly work at it.

That is probably why Redhat and Debian (and family) and many others (even
[shudders] Microsoft and to a lesser extent Apple) provide a version that
basically stays the same for years. Heck, many places grumble about
'having to' upgrade from Xp because it 'only' lasted 10 years! Some
organisations happily pay millions per year extra purely in order to be
able to stay with the same old Xp and STILL haven't developed a strategy
for upgrading.

Arch and others attempt to deal with the problem by doing rolling releases
- which brings it's own set of problems - as Windows 10 users and Microsoft
will doubtless be learning afresh over the next couple of years. Arch has
already long ago grokked this so MS could learn valuable lessons from them
but i think we all know they can't learn wisdom from outside, unless they
really have changed.

So in answer to your question to Alex; "Yes". Many places would appreciate
updates rather than to keep demanding their Sys. Admins have to keep
re-installing new upgrades.

It'd also be great if there were some sort of "Super Still" branch, like
Debian, or Redhat (and many others) that kept getting updates for 3-4
years. So that organisations could install the Super Still branch on new
systems in complete confidence that they wouldn't need to touch the system
again for a couple years.

There are other cases where people don't have broadband for downloading
full upgrades but could do with having a system they could rely on for
years. European city-dwellers might not quite realise what it's like
without broadband.

I think it's interesting that the super-rich share a problem in common with
the desperately isolated and cut-off. One which is largely addressed by
almost all of Gnu&Linux but not by LibreOffice.
Regards from
Tom

<snip />

[planas]

Hi
"Thanks for the flowers"/approval which i've snipped. It's a shock to
finally agree on something! :))

The LTS approach was a new way of dealing with an old problem. The old and
still current problem is that projects are pulled in 2 opposing
directions;
1. exciting and new developments, fashion, bling
2. stay with something familiar and see it mature. NOT having to
constantly work at it.

That is probably why Redhat and Debian (and family) and many others (even
[shudders] Microsoft and to a lesser extent Apple) provide a version that
basically stays the same for years. Heck, many places grumble about
'having to' upgrade from Xp because it 'only' lasted 10 years! Some
organisations happily pay millions per year extra purely in order to be
able to stay with the same old Xp and STILL haven't developed a strategy
for upgrading.

Arch and others attempt to deal with the problem by doing rolling releases
- which brings it's own set of problems - as Windows 10 users and Microsoft
will doubtless be learning afresh over the next couple of years. Arch has
already long ago grokked this so MS could learn valuable lessons from them
but i think we all know they can't learn wisdom from outside, unless they
really have changed.

Both approaches have problems with either needing to maintain security releases for old versions (LTS) or with system stability/breakage (Rolling). The first appears safe because the system is relatively stable but older OSes may not support easily newer technologies. This can be problematic as the OS ages. Also, security releases and bug fixes must be maintained over several version of a library. Rolling releases can be have stability issues with being too close to the bleeding edge but they are likely to support the latest technologies. Also, there are fewer library versions to be maintained.

Having used both, I recommend LTS releases for most users knowing every x years their system must be upgraded to the current supported release.

My fear with W10 is MS does not truly understand the nature of a rolling release and their users are not at all familiar with the quirks of a rolling release. I have found one needs to pay closer attention to update issues as they occur with a rolling release and it helps to have a good grasp of how a computer works. Windows users are not used to more active update management and often have a very poor understanding of how a computer works. IMHO, the potential for a disaster about 6 - 12 months from initial release is very high with W10.