LibreOffice Manager (lomanager)

[Neal ManBear]

@luikki,
It is not necessary to run aptupgrade on the 2011.6 ISOs.

@DarkEra,

Download and installation canceled. Please use the offline-installer described in Important Notes 1b in the lomanager-thread.

This indicates a problem occurred with the download; i.e. it is very likely that your internet connection was reset or stopped, then started again during each of the several attempts that LOManager made to download the needed files for installation.

When that occurs, do this; i.e. use the offline installer.

LOManager did its job. The error message confirms that.

[pinoc]

still doesn't do it's jobs as it should

i do not second that statement!

did you install and run aptupgrade prior to run lomanager?

3.4.2 will test if aptupgrade was installed on the system and if this test fails it will provide you with instructions on how to install aptupgrade. As mentioned before I think there is some other network issue going on for DarkEra preventing lomanager to download the base-pack with the way downloading is setup in lomanager. For these cases we have the offline-installer and 3.4.2 will provide this info.
-p.

[melodie]

Hi,

Here it worked but libreoffice does not start. When I use the Exec command which is implemented in the desktop file of the writer module:
libreoffice3.4 --writer %U

I get a window with the message : /home/melodie/%U does not exist.

I start libreoffice with the same without %U argument, libreoffice starts. And if I remove the argument '%U' from the desktop file, libreoffice write module menu entry launches it correctly.

I didn't try the other modules, but I suppose it might follow the same scheme ?

luikki : why do you want anyone to use aptupgrade if the distro is the last iso installed ? aptupgrade needed to be started ONCE only, and only on former installs. This is a script Texstar provided in order to ease the update of the apt-rpm chain, and which is to be used once only and exceptionnally. The new iso provided since this summer don't need anything more as they have been provided **with** the new apt-rpm packages (apt, apt-common, synaptic, etc... )

maybe did you mean "apt-get update" instead ? Reloading the packages information ?

[luikki]

 

[7272andy]

Sorry to say it's failing here, I keeps presenting the dialog box

To run LibreOffice Manager please temporarily switch from your local repo to an online repo.

Exiting...

in order to get the installer to work I need to delete the local repo lines from my sources, simply hashing them out is not good enough.

[Agent Smith]

Hi,

Here it worked but libreoffice does not start. When I use the Exec command which is implemented in the desktop file of the writer module:
libreoffice3.4 --writer %U

I get a window with the message : /home/melodie/%U does not exist.

I start libreoffice with the same without %U argument, libreoffice starts. And if I remove the argument '%U' from the desktop file, libreoffice write module menu entry launches it correctly.

I didn't try the other modules, but I suppose it might follow the same scheme ?

luikki : why do you want anyone to use aptupgrade if the distro is the last iso installed ? aptupgrade needed to be started ONCE only, and only on former installs. This is a script Texstar provided in order to ease the update of the apt-rpm chain, and which is to be used once only and exceptionnally. The new iso provided since this summer don't need anything more as they have been provided **with** the new apt-rpm packages (apt, apt-common, synaptic, etc... )

maybe did you mean "apt-get update" instead ? Reloading the packages information ?

I wonder if the libreoffice hidden folder in your /home exists. Perhaps this error is related to this. Ok
See if there is the hidden folder, if not, create one and then try it again to see what happens.
Hope I have helped somehow
Best regards

[Neal ManBear]

  Commenting (adding #) my local repo works fine.

[melodie]

Don't cry, anyone mistakes once a while.

To pinoc : I just tried to start all the other modules from the menu, and all start well from there. I changed only the libreoffice write desktop file by removing the %U : don't know why it was bothering, or even if it was present in the desktop file of the former version.

[melodie]

I wonder if the libreoffice hidden folder in your /home exists. Perhaps this error is related to this. Ok
See if there is the hidden folder, if not, create one and then try it again to see what happens.
Hope I have helped somehow
Best regards

Hidden files and folders are created at the launch of the application *along with the configuration files it contains*. If you will install Libreoffice for the first time in your system the hidden directory does not exist, but libreoffice manager will still do it's job : otherwise having the hidden directory is of no use, without the configuration files which are created in it at same time...

[pinoc]

To pinoc : I just tried to start all the other modules from the menu, and all start well from there. I changed only the libreoffice write desktop file by removing the %U : don't know why it was bothering, or even if it was present in the desktop file of the former version.

the %U is part of all LO-app desktop-files and these files are setup not by lomanager but by the LO-devs, see /opt/libreoffice3.4/share/xdg/
Starting Writer from the menu works just fine and is one of the very first things I test before releasing any lomanager-version
Must be a problem specific to your system?
-p.

[Bald Brick]

Hi,

Here it worked but libreoffice does not start. When I use the Exec command which is implemented in the desktop file of the writer module:
libreoffice3.4 --writer %U

I get a window with the message : /home/melodie/%U does not exist.

I start libreoffice with the same without %U argument, libreoffice starts. And if I remove the argument '%U' from the desktop file, libreoffice write module menu entry launches it correctly.

I didn't try the other modules, but I suppose it might follow the same scheme ?

Are you running KDE? "%U" is a KDE option that tells LibreOffice to load whichever file or url you have clicked. If you click a .desktop file directly in KDE it will normally be ignored, but even in KDE you'll get the same error message if you enter "libreoffice3.4 --writer %U" in Konsole. It's not intended to be used on the command line, and when it comes to other desktop environments ...

In some cases you get the error message but the program (e.g. LibreOffice) loads anyway.

[Vorteggs]

It installs Java

Never saw lomanager or addlocale installing Java.

I'd consider something's very wrong in your PCLOS install.

[wayne1932]

The latest LOmgr and LO worked fine with my Desktop and my Laptop.  2011.6 KDE fully updated.  Did nothing about java, but probably OK, since it was already installed by the previous version. 

[melodie]

Hi,

Here it worked but libreoffice does not start. When I use the Exec command which is implemented in the desktop file of the writer module:
libreoffice3.4 --writer %U

I get a window with the message : /home/melodie/%U does not exist.

I start libreoffice with the same without %U argument, libreoffice starts. And if I remove the argument '%U' from the desktop file, libreoffice write module menu entry launches it correctly.

I didn't try the other modules, but I suppose it might follow the same scheme ?

Are you running KDE? "%U" is a KDE option that tells LibreOffice to load whichever file or url you have clicked. If you click a .desktop file directly in KDE it will normally be ignored, but even in KDE you'll get the same error message if you enter "libreoffice3.4 --writer %U" in Konsole. It's not intended to be used on the command line, and when it comes to other desktop environments ...

In some cases you get the error message but the program (e.g. LibreOffice) loads anyway.

I believe pinoc uses KDE, I don't. Only Openbox standalone are my current systems. I think however pinoc might be right, I will check in my other machine if Libreoffice write does start from the menus, or if I need to change the desktop entry as well.

Regards,
Mélodie

[7272andy]

Commenting (adding #) my local repo works fine.

Hmm, I've tried it all ways now, the only way I can get it to work is to delete the lines for the local repo's.
Most odd.