Problem Installing/Updating LO

users
#1

*Hi All*

Since I upgraded to LO 4.3.4 I have a problem with LO Manager!!

Whenever I start it it shows the error -

/Please close your package manager 'synaptic' //
// and then run LibreOffice Manager again.//
//
// Exiting../.

Synaptic is _*NOT*_ running - So am unable to update the package.

* I tried re-installing LO Manager - still get the error.
* Then I 'Completely Removed' all LO files with Synaptic and re-installing LO with but still get the same error.
* I then removed the hidden .config/libreoffice files and reinstalled the Manager but still get the same error.

I'm now stuck with no LO on my system at all!!

My system runs PClinuxOS (latest) 32-bit.

Any suggestions please??

IanW
Pretoria RSA

#2

LibreOffice Manager does not seem directly related to LibreOffice (or to
this mailing list). Maybe you'll have better chances of getting help about
it on a dedicated forum.

Now, if you want to install LibreOffice by hand, you can always grab an
archive containing all the application packages from
https://www.libreoffice.org/download/libreoffice-fresh/. This will most
likely result in a complete and working installation of LibreOffice on your
system.

#3

This sounds like LO Manager is calling to synaptic twice.
Did you confirm synaptic is not running by process status command "ps" that includes all processes before starting LO Manager?

Try "lomanager --no-updatetest" from http://www.pclinuxos.com/forum/index.php?topic=125725.0

Also suggested is...
Close Synaptic, then reboot. Log in, then open Synaptic and do a full upgrade... *Reload --> Mark All Upgrades --> Apply* then *Apply* again, from the confirmation window. When the upgrade has finished, close Synaptic. Then run the *updated version* of LbreOffice Manager.
from http://www.pclinuxos.com/forum/index.php?topic=108906.0

In linux it is possible to have someone else login and start synaptic and leave it open. Is this a possible scenario?

Hope this helps.

#4

*Thanks Paul - answers below ...*

This sounds like LO Manager is calling to synaptic twice.
Did you confirm synaptic is not running by process status command "ps" that includes all processes before starting LO Manager? /*- YES NOT RUNNING*/

Try "lomanager --no-updatetest" from http://www.pclinuxos.com/forum/index.php?topic=125725.0

*This is what I get ...*
[root@localhost ianw]# lomanager --no-updatetest

** (zenity:19120): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-hWMDwz5vcY: Connection refused

Also suggested is...
Close Synaptic, then reboot. Log in, then open Synaptic and do a full upgrade... *Reload --> Mark All Upgrades --> Apply* then *Apply* again, from the confirmation window. When the upgrade has finished, close Synaptic. Then run the *updated version* of LbreOffice Manager.
from http://www.pclinuxos.com/forum/index.php?topic=108906.0

Synaptic only gives option to install LO Manager

In linux it is possible to have someone else login and start synaptic and leave it open. Is this a possible scenario?

NO - I'm single user on single machine!!

#5

Hi :slight_smile:
Have you tried going to a command-line and doing things like

ps aux | grep synaptic

sudo apt-get check
sudo apt-get update
sudo apt-get upgrade

sudo dpkg --configure -a

That first line should show if somehow synaptic is running at a weird
time. Just "top" generates an active "process manager" or "task manager"
type of thing. The last line is unlikely to be needed but can help fix
things if any of the middle run into trouble.
Regards from

Tom :slight_smile:

#6

Hello Ian

Checked "WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket Connection refused" on Google

There are quite a few errors listed there. It may be a Gnome/Debian error of some type involving dbus. Possibly a dbus crash.

(zenity:19120): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-hWMDwz5vcY: Connection refused

I checked the specific message and nothing came up.

Does the version of Debian your using match the errors from Google and Ubuntu?