LibreOffice Manager (lomanager)

[JohnW_57]

LibreOffice updated without a issue after the latest update!!

Thanks Peter!! (Pinoc).

[kjpetrie]

thanks for the +. Trust me, I'm all interested in providing a robust and working script because I then do not have to deal with any issues and instead can concentrate on other things which need to be done or developed, and there is lots of things to do. I tested the current version on 5 different setups without issues before uploading it. Now I'm most puzzled, and try to understand why the script works when invoked with gksu while the download crashes at 67% when the script is invoked with kdesu, plus the same cmd works just fine from the terminal, all that makes no sense at all. Really curious to find out what is going on there, too strange...
-p.

Could that be our old friend su v su - ?

[Bernd]

Hy Pinoc,
after lomanager update to version 3.5.0-2, your script works flawlessly  . 32-bit and 64-bit testing iso (kde) !!
Thank you for all your effort and of course time you put in this project (and in the other ones as well  )

Cheers Bernd

[Bald Brick]

thanks for the +. Trust me, I'm all interested in providing a robust and working script because I then do not have to deal with any issues and instead can concentrate on other things which need to be done or developed, and there is lots of things to do. I tested the current version on 5 different setups without issues before uploading it. Now I'm most puzzled, and try to understand why the script works when invoked with gksu while the download crashes at 67% when the script is invoked with kdesu, plus the same cmd works just fine from the terminal, all that makes no sense at all. Really curious to find out what is going on there, too strange...
-p.

Could that be our old friend su v su - ?

I was thinking the same thing. You run gksu with the '-l' option so that it starts a login shell. Does kdesu start a login shell by default?

[pinoc]

maybe that causes it. Anyway, the next version of lomanager will no longer have kdesu as gksu is available on all PCLInuxOS installations and that works fine.
-p.

[Just17]

maybe that causes it. Anyway, the next version of lomanager will no longer have kdesu as gksu is available on all PCLInuxOS installations and that works fine.
-p.

When gksu is used on this KDE install I get a dimming of the display as the password entry box is displayed .....  it does not happen smoothly, but rather in a 'stepped' manner as if the graphics card was unable to display it smoothly.

kdesu does not dim the display so this is not present when that is used.

I have been avoiding gksu for that very reason.

I wonder is this normal?

I guess it will make little difference to my use of lomanager as it will only be run occasionally, but it does give a bad impression to the user (me)

[kjpetrie]

I think that's normal.

[Just17]

I think that's normal.

Thanks 

I don't normally see it anyway .....  for instance I edited the 3.5 script before running it to ensure it would use kdesu, as otherwise it defaults to gksu, which some time ago caused me problems.
I haven't had any problems, thankfully, when using kdesu.

[pinoc]

I think that's normal.

Thanks 

I don't normally see it anyway .....  for instance I edited the 3.5 script before running it to ensure it would use kdesu, as otherwise it defaults to gksu, which some time ago caused me problems.
I haven't had any problems, thankfully, when using kdesu.

nor did I with kdesu on ~ 10 machines, and what is your explanation why for some users apparently only the wget-command in lomanager fails when lomanager is invoked with kdesu? I have not the slightest idea but will leave it now to use gksu exclusively.

[Archie]

maybe that causes it. Anyway, the next version of lomanager will no longer have kdesu as gksu is available on all PCLInuxOS installations and that works fine.
-p.

When gksu is used on this KDE install I get a dimming of the display as the password entry box is displayed .....  it does not happen smoothly, but rather in a 'stepped' manner as if the graphics card was unable to display it smoothly.

kdesu does not dim the display so this is not present when that is used.

I have been avoiding gksu for that very reason.

I wonder is this normal?

I guess it will make little difference to my use of lomanager as it will only be run occasionally, but it does give a bad impression to the user (me)

I have similar experiences with gksu but not in the way you described it. I use LX appearance + Blapple so it doesn't look so bad in its blinding white background.

Anyway, it opens up quite gracefully freezing everything on my desktop like a fullscreen snapshot. Everything moving like my system montior (superkaramba), ongoing builds displayed on the Konsole, etc is like FREEZE, say cheese. But everything returns to normal (quite but the stuff kinda like jumped on a timewarp or something) when I enter my root password.

I suppose that is normal for gksu.

[pinoc]

3.5.0-3 coming to your repo soon, new edition: striving for perfection... 
changes:
- removed kdesu
- fixed missing dependency resulting in crash on MiniME, thanks AS!
- fixed another small error

-p.

[Neal ManBear]

Coming to a repo mirror near you soon.      

[johnmart]

I just installed the current lomanager, ran it & got the announcement that I had the latest version.
In the dialog box explaining that I am up to date, & offering me the choice of reinstalling LO, the 2 button choices are Yes & No. After a careful read of the dialog box, I figured out which button to click, (actually I have done this plenty of times so I was pretty sure which as the right selection).
But, the choices Yes/No seem counter intuitive to me.
I think for most people the default act would be to exit. The ones reinstalling/uninstaling would be few.
Would it be clearer for the button options to be; Exit  or  Continue?
I hope this is not being nitpicky, just a thought. 
Thanks for your dedication to lomanager PLUS all the other PCLinuxOS tasks you maintain. 

[pinoc]

I just installed the current lomanager, ran it & got the announcement that I had the latest version.
In the dialog box explaining that I am up to date, & offering me the choice of reinstalling LO, the 2 button choices are Yes & No. After a careful read of the dialog box, I figured out which button to click, (actually I have done this plenty of times so I was pretty sure which as the right selection).
But, the choices Yes/No seem counter intuitive to me.
I think for most people the default act would be to exit. The ones reinstalling/uninstaling would be few.
Would it be clearer for the button options to be; Exit  or  Continue?
I hope this is not being nitpicky, just a thought. 
Thanks for your dedication to lomanager PLUS all the other PCLinuxOS tasks you maintain. 

In this situation most people will Exit, which is 'Yes' and set as default, so it's ok.
-p.

[kjpetrie]

With zenity, which I think is what pinoc uses to create the dialogues, the text in the buttons is a given. There are many times they could have more appropriate labels, but we're stuck with "Yes" and "No". They used to be "OK" and "Cancel" which made phrasing the question even harder!