error installing LO 5.2.2

users
#1

I just removed 5.2.0 and tried to install 5.2.2. Below is the error message I received.

I do not know what dependencies are needed for 5.2.2 that was not for 5.2.0?

Any Idea?

I run Ubuntu/Mate 16.04 64-bit.

#2

See that it is complaining about libobasis5.2-en-us. If you removed 5.2.0 first,
perhaps this dependency was removed then, and not replaced in the 5.2.2
installation.

Gordon.

#3

Send reply to: webmaster@krackedpress.com
<webmaster@krackedpress.com>
Date sent: Fri, 7 Oct 2016 22:03:21 -0400

I just removed 5.2.0 and tried to install 5.2.2. Below is the error
message I received.

I do not know what dependencies are needed for 5.2.2 that was not for 5.2.0?

Any Idea?

I run Ubuntu/Mate 16.04 64-bit.

I've had the same issue for some time when updating the LibreOffice on
systems manually. If the help package has been loaded, the update process
only works if you do it all at once.

I generally download and extract the whole LibreOffice, and then download
and extract the help file. Copy the RPM for the help file into the same
directory as the other RPM files, and then run the rpm -Uvh *.rpm. Probable
a similar issue with Ubuntu. They need to be insync.

The windows version will let you install them out of sync, but it probable
shouldn't, but don't think that systems has the checks.

#4

dpkg: error processing package libobasis5.2-en-us-help (--install):
   dependency problems - leaving unconfigured

After I failed to install 5.2.2.x, I installed 5.2.1.x.

The "LibreOffice_5.2.1.2_Linux_x86-64_deb.tar.gz" files installed without a hitch. So the problem was with the install of the file in 5.5.2.x, not 5.2.0 or 5.2.1. After I installed the main set of files with the terminal, then I installed the help file .deb.

I used these commands to install 5.2.x.x;

sudo apt-get remove libreoffice?
sudo dpkg -i *.deb

This is only way I have installed LO onto my Ubuntu partitions on various laptops and desktops.

#5

​Tim, have you tried adding *ppa:libreoffice/libreoffice-prereleases* to
your systems Software sources ? Works like a charm for me on Linux Mint
18....

Henri

#6

Hi :slight_smile:
Does this fix it?

sudo dpkg --configure -a

(of course that is two - signs in front of the word "configure"). It
usually fixes most package errors on my Debian-family distros such as
Ubuntu, Mint etc. At worst it usually gets me to a state where i can open
Synaptic package manaager and then use it's;

Edit - "Fix broken packages"

I'm just starting to get used to Raspberry Pi where i have moved to other
families where i have almost no idea how to fix anything like that.
Regards from
Tom :slight_smile:

#7

Henri,
I do not install the PPA versions of LO. I choose which version I install. A lot of times I keep using a "still" version instead of the newest "fresh" version. Actually, this laptop is running 5.2.1.2, since the 5.2.2.x fresh version that has the pesky error. 5.2.0 and 5.2.1 does not have that error. So, the PPA release may not be the right move for me. I still have one laptop [Windows and Ubuntu partitions] that still use 5.1.x.

Tim L.

#8

Sorry Tom, but it does not work. I do not think the "fix broken packages" would not be useful since the error was telling me that I do not have all the dependencies that was listed for 5.2.2, even though I did not have that error with 5.2.1.2. So something within one of the upgraded .deb files decided that it needed a package that 5.2.1 need with the Ubuntu "terminal" based install.

Actually, I tend to check for broken package every few weeks.

Which version of Raspberry Pi are you using? "Pi 2" or "Pi 3 B"? Running Raspbian or Ubuntu Mate? It looks like the RPi 3 can run the "Windows 10 IOT Core"

  RPi 3 seems to have come out a few months ago. "They" released the first "starter kit" last month. One day, I hope to get a RPi with all the "starter equipment" needed to complete it - except the VGA or HDMI connector monitor and USB keyboard/mouse because I have them already.

Hi :slight_smile:
Does this fix it?

sudo dpkg --configure -a

(of course that is two - signs in front of the word "configure"). It
usually fixes most package errors on my Debian-family distros such as
Ubuntu, Mint etc. At worst it usually gets me to a state where i can open
Synaptic package manaager and then use it's;

Edit - "Fix broken packages"

I'm just starting to get used to Raspberry Pi where i have moved to other
families where i have almost no idea how to fix anything like that.
Regards from
Tom :slight_smile:

<snip>