LibreOffice Manager (lomanager)

[melodie]

I have suggestion about the LOManager .

Can You please change the timing on one of the stops? It asks do You want to keep RPMs in the /tmp/ folder and it only gives 15 seconds to click or it will delete them by default. I am wanting to keep the RPMs but sometimes I will get distracted and boom - it's gone ... Add another 15 seconds or so and I should be golden.

Thanks!

Andy

Hi Andy,
no, I will not do that because then other people will say "I leave this thing running on its own but why do I now have to wait 30 secs until it continues? I am not Andy!" or should I code something like
If $USER = Andy then
  "wait 5 minutes or ring the bell to get distracted Andy alerted"
ELSE
  " do the usual thing"
FI   

 

nope, just leave as is, may include some other things like automatically check for latest version on LO-server without needing updated lomanager.
But not much time for costing right now,
-p.

Hi,

May I suggest no timing at all, but just a YES/NO choice with buttons ? As soon as the person clicks on one the choice is done ? (Even 2 days later if Andy needs to first go out for week-end... )

Else than that here it all works perfect too ! Thanks for this new update and the super job !

Regards,
Mélodie

[ternor]

It's a simple matter to fix by editing the script.  I increase time out to 25.

[AndrzejL]

No timing is not acceptable - some folks are just leaving the script running it downloads / installs and you dont have to sit around and click stuff.

Editing the script is what I would do - and I am glad I am not the only one that finds 15 seconds to read, make a decision and click the choice is not enough.

[pinoc]

lomanager 3.5.1-2 coming with these changes:
- system uptodate check
- if LO comes out with a new release then you will get the info to wait for an updated lomanager or use the offline installer

if you already have LO3.5.1 installed then you do not need to rerun this lomanager.
-p.

[7272andy]

Although I'm up to date, I thought I'd give it a whirl.

lomanager won't run as flash and sweet home are not at the latest releases, neither of these packages work on my machine at the latest release state.

How do I update L-O in this instance?

[DeBaas]

@7272andy
Look at the start of this topic:
http://www.pclinuxos.com/forum/index.php/topic,59009.0.html
scroll down to:
1b) Alternative offline installation:

[pinoc]

lomanager won't run as flash and sweet home are not at the latest releases, neither of these packages work on my machine at the latest release state.

and what does that mean in normal english? Any details, errors, etc. or how I am supposed to debug your problem?

[7272andy]

Hi pinoc
I guess you're looking for these.

lomanager-install.log
lomanager installation log file:
Thu Mar 22 16:55:42 GMT 2012
lomanager-3.5.1-2pclos2012
Detected webbrowser: kfmclient exec
System not uptodate or broken dependencies found

LO_STEP00.log
Reading Package Lists...
Building Dependency Tree...
The following packages will be upgraded
   SweetHome3D (2.0-1pclos2009 => 3.2-1pclos2011)
   flash-player-plugin (10.3.183.7-17272andy2011 => 11.1.102.63-1pclos2012)
2 upgraded, 0 newly installed, 0 removed and 0 not upgraded.
Inst SweetHome3D [2.0-1pclos2009] (3.2-1pclos2011 Unknown:Unknown/Unknown)
Inst flash-player-plugin [10.3.183.7-17272andy2011] (11.1.102.63-1pclos2012 Unknown:Unknown/Unknown)
Conf SweetHome3D (3.2-1pclos2011 Unknown:Unknown/Unknown)
Conf flash-player-plugin (11.1.102.63-1pclos2012 Unknown:Unknown/Unknown)

The only message was a dialog stating
Please update your system.
(more details: /tmp/LO_STEP00.log).

Exiting...

If I can give anything else just let me know

Thanks for the reminder DeBass, I know I could do things that way, but if pinoc is able to improve what is an already excellent installer it's all to the good, if not there's always the offline method.

Regards

[kjpetrie]

I had similar messages. I think it results from a delay between upgrading and running lomanager. In my case I update the package lists and download the packages using a cron job overnight so as to keep them off my metered usage, then another cron job in the daytime runs rkhunter and opens Synaptic so I can see what I'm approving and ensure nothing silly's happening. I then waited until the following unmetered period to run the script, and of course I was 24 hours behind the repo by then, so when lomanager updated the package lists and checked versions it found differences and refused to proceed.

I had to do an unscheduled upgrade to get things in balance, which isn't my idea of how I want to do things, but if it protects people from partial upgrading I suppose I have to accept it.

I would guess you also delayed between installing and running lomanager and ran into the same problem.

Probably a West-Country thing!

[pinoc]

Hi pinoc
I guess you're looking for these.

lomanager-install.log
lomanager installation log file:
Thu Mar 22 16:55:42 GMT 2012
lomanager-3.5.1-2pclos2012
Detected webbrowser: kfmclient exec
System not uptodate or broken dependencies found

LO_STEP00.log
Reading Package Lists...
Building Dependency Tree...
The following packages will be upgraded
   SweetHome3D (2.0-1pclos2009 => 3.2-1pclos2011)
   flash-player-plugin (10.3.183.7-17272andy2011 => 11.1.102.63-1pclos2012)
2 upgraded, 0 newly installed, 0 removed and 0 not upgraded.
Inst SweetHome3D [2.0-1pclos2009] (3.2-1pclos2011 Unknown:Unknown/Unknown)
Inst flash-player-plugin [10.3.183.7-17272andy2011] (11.1.102.63-1pclos2012 Unknown:Unknown/Unknown)
Conf SweetHome3D (3.2-1pclos2011 Unknown:Unknown/Unknown)
Conf flash-player-plugin (11.1.102.63-1pclos2012 Unknown:Unknown/Unknown)

The only message was a dialog stating
Please update your system.
(more details: /tmp/LO_STEP00.log).

Exiting...

If I can give anything else just let me know

Thanks for the reminder DeBass, I know I could do things that way, but if pinoc is able to improve what is an already excellent installer it's all to the good, if not there's always the offline method.

Regards

since lomanager 3.5.1-2 I have included a test to check if your system is fully updated.

This means that from now on lomanager will only do the LibreOffice installation on a fully updated system and the user is put in charge of ensuring that this is the case.

This is meaningful to avoid any installation issues caused by a partially updated system or using an outdated version of Java for an uptodate LibreOffice.
The update test will
- simulate a full system update, then
- if your system is fully updated lomanager will continue
- if your system is not fully updated then lomanager will abort and
a) you will get informed what you have to upgrade to be fully updated (/tmp/LO_STEP00.log), and
b) your browser will open this website so the user can learn How to properly update your system.

The idea was that the information above would help the user to perform a full system update, which should be done anyway and the avoid installation issues which are not caused by lomanager.

hope this information helps,
-p.

[7272andy]

Cheers guys, I have the issue resolved to the satisfaction of pinocs script (which works flawlessly).

In my case, my system is fully updated with the exception of the two packages shown in the logs (due to hardware issues). The answer to the problem was to pin the packages in synaptic, which meant that lomanager saw a fully updated system.

The downside with pinning (to me), is that I won't know when an updated package that may work with my hardware hits the repos.

Ultimately I believe lomanager (working the way it does) is the correct way of doing things as it has the potential to prevent an awful lot of problems before they occur.

Regards

[pinoc]

updated and uploaded offline installers for 32/64, see initial post for instructions.

lomanager 3.5.2 coming to your repo soon with these changes:
- updated to 3.5.2
- added test for clean up of incomplete previous lomanager run
- added option to skip system uptodate test
- fixed options to be applied properly
- disabled launch of web browser until a safe solution is found

Note:
- a new test will search for existing /tmp/xsulomanager which could be a left-over from an incomplete previous run or if you cancelled the gksu dialog window. Anyway, this file should not be there before or after running lomanager.

- the options were not applied at all, no one realized that??  And for those guys with pinned packages, or other reasons for not fully updating the system, you can now run
lomanager --no-updatetest
to skip the system uptodate test ...

- with earlier versions some instructions/notifications were shown in a web browser which was launched with root-priviledges. Until I find a proper solution to circumvent this this will be disabled.

best,
-p.

[pinoc]

3.5.2-2 will now again launch related websites in a browser but now with the user's privileges.

Note: the following browser will work: konqueror opera midori epiphany jumanji xxxterm dillo surf
and these browsers not: rekonq chromium-browser firefox arora seamonkey

if you do not have a browser of the first group installed then you will just get a simple information window.
-p.

[7272andy]

Cheers pinoc,
just tried that with and without pinned packages, all worked flawlessly.

Regards

[mellon]

I get as far as this after I select English UK as language. I get the mesage that I should do an offline upgrade. First time this happens. Here is what I get in konsole when I run lomanager as root and clicked OK on the popup boxes

Code: [Select]

GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running

stdin: is not a tty

Internet connection working

/usr/bin/konqueror
--2012-04-06 11:30:08--  http://distro.ibiblio.org/pclinuxos/pclinuxos/apt/pclinuxos/2010/RPMS.updates/lomanager-3.5.2-2pclos2012.i586.rpm
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44673 (44K) [application/x-rpm]
Saving to: `lomanager-3.5.2-2pclos2012.i586.rpm'

100%[=====================================================================================================================================>] 44,673      37.1K/s   in 1.2s   

2012-04-06 11:30:10 (37.1 KB/s) - `lomanager-3.5.2-2pclos2012.i586.rpm' saved [44673/44673]

Preparing...                ########################################### [100%]
Download completed
konqueror(7607)/kdeui (kdelibs): Attempt to use QAction "firefox" with KXMLGUIFactory!
konqueror(7607)/kdeui (kdelibs): Attempt to use QAction "kwrite" with KXMLGUIFactory!
konqueror(7607)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active