[PROBLEM RECURRED] getopenoffice 1.4 can't find internet

[xheralt]

Running a near-virgin (and fully updated) PCLOS 2009.2 install.  Folliwng issuance of getopenoffice command in root konsole window, it comes back with the error message "stdin: is not a tty", followed by a gui popup saying "internet connection not found" -- the latter of which is patently incorrect, I have KNemo indication that eth0: is active, and I am in fact posting this missive from the same machine.  Is the script fubared, or is it my machine, and if the latter, what can I do to fix it?

[pinoc]

Hi xheralt,

ok, let's see: you are certain that you do not use the belnet server and you do not use the "testing" section in Synaptic, your system is fully updated, and you have already read all information in the original post of getopenoffice?

If this is the case could you then please answer the following questions:
- do you have any other issues with your current installation or is everything working perfectly normal?
- do you get the same error when running getopenoffice as a normal user from: PCmenu -> System -> Configuration -> Get Openoffice?
- which system locale (en-US or any other?) and which window manager do you use: KDE3, KDE4, Gnome, XFCE, LXDE,...
- if OO was already: Which OO-version and which OO-locale? Did you use getopenoffice to install it?
- if OO is not installed: you did not get a window saying "Welcome to GetOpenOffice"?

thanks for detailed answers to the above questions, regards,
-pinoc

[xheralt]

Answering as many of your questions as I can, for not being at THAT machine this moment...

-KDE 3.5.  I'll switch to Gnome before ever using KDE 4 again .
-No other problems noted with the machine.
-Don't know, I'd have to try it from the menu.
-en-US
-No OO install currently (machine was total wipe-and-start-over for other issues)
-I did not get that welcome window

I never use "testing" packages (the machine is intended for public use), and I don't use the belnet server (I try the US-based ones, like USSG, first).  However the post you linked to (which I somehow overlooked searching  ), did turn up one possibility -- I have more than one repo selected.  Now that I think about it, however, last time through, on a different machine, the script was smart enough to recognize that condition, so I'm puzzled it didn't alert me this time.  But then, it looks like the script didn't get very far.

[pinoc]

Hi xheralt,

thanks for the replies. If OO  was not installed before I wonder why you did not get the welcome window, or another window informing you that more than 1 repo was enabled. Could it be that the machine is not fully updated? And why do you have more than 1 repo enabled? The repos are all mirrored and if they are synced at different times, which is very likely, then they will be inconsistent and creating all kind of problems. Please always use only 1 repo. Getopenoffice works fine on a fully updated system. If not on your system, then we need to figure out where the problem starts ...
Unfortunately I must leave now and will only be back next Monday. Sorry to be of no more help right now, and if you like Gnome, maybe a fresh Gnome install, then fully update, and then run getopenoffice?

until Monday, good luck,
-p.

[xheralt]

I understand, real life gets in the way sometimes;  I'll be here when you get back    Thanks for your continuing attention.

I normally keep multiple repos enabled because sometimes www backbone connectivity issues (aka 'internet black holes') cause update attempts to 404 midstream -- I get the packagelists but not the packages themselves.  Annoying as hell, because geographically, I'm only two states over from either Iowa or Indiana   The redundancy was often necessary to succeed with updates.

Disabling all but one repo (the arbitrarily-chosen freebsd.nl) got rid of the command-line err msg, but GOO 1.4 still can't find the internet and exits.  Also, going direct to OO dotorg and downloading the rpm install comes back with missing dependencies (?!).  Synaptic doesn't report any packages as "broken".

I don't know what other info you'd need.  It's not the hardware, as I'm using Firefox on it now, though FYI lspci reports the NIC as being a Realtek RTL-8139.

Just as a side note, I don't like Gnome, using it would be an act of desperation; I just hate it LESS than KDE4.  I'm hoping that some other developer will fork KDE3 and continue with it (in a form closer to current style and sensibilities) now that KDE dotorg themselves have moved on. 

[xheralt]

Hmm, getopenoffice is working on one of the other coffeehouse machines installed from the same media at about the same time.  Might be just a bad download of the script itself, on that machine.  I'll re-install GOO via synaptic and get back to you.  

EDIT:  It's also quite likely that I, counter to Texstar's just-discovered advice in the "How to Properly Upgrade" thread, attempted to "Continue" a busted general update on the affected machine (even though it was via synaptic, not apt-get).  It wouldn't be the end of the world for me to reformat the machine and start from scratch, if that's the simplest solution.

EDIT EDIT:  Reinstalling the script -- and getting all updates for today -- hasn't helped.  All things being equal, why is it working on one machine but not the adjacent one?

[pinoc]

Hi xheralt,

good to hear it is working on one of your machines. This suggests that getopenoffice itself is working well and the reason why it fails on your other machine seems to be that this machine has duplicated, broken, or held-back packages, meaning it is only partially updated. Please ensure that the machine is fully updated: open Synaptic, and verify to have only one (1) reliable repo enabled, then press Reload, Mark All Upgrades, and also check for Broken Packages. Only after your system is fully updated and you have no broken packages you should run getopenoffice. You could also install dupeclean-gui which will help you to remove duplicated packages from your system.

good luck,
-p.

[xheralt]

@pinoc, I'm a little confused by what you mean here -- synaptic is reporting zero broken packages in the status line, do I have to do something specific to force it to look?  Or can I take it as read that I have no broken packages?  I don't see any option in synaptic's menubar or toolbar that relates to broken packages, other than the "what to display in a given category" selector, and 'Broken' category does have the checkbox for broken packages selected.

 I've *been* marking and applying all upgrades as a matter of course.  35 more today.  The coffeeshop is closing for the day, I'll have to report what dupeclean does tomorrow.

[bigsite]

  I just installed it from the OOO website and Synaptic even shows it as good packages in my list...only trub is I always get the OOO desktop icon error, but if you are using the KDE menu the stuff shows up nice and clean........not much of a biggie if the script gives you trubs....(but SSSHHHH, some around here might not like me saying this.....)

[pinoc]

@xheralt,
if you do not have any broken packages, and if a Reload, Mark All Upgrades in Synaptic tells you all is uptodate then good! The latest library updates from yesterday may require a reboot for some programs (including getopenoffice) to start properly. Please reboot your system and then run getopenoffice again.

@bigsite,
you are most likely aware of the fact that installing packages from outside the repo is strongly discouraged and not supported here in this forum. Even more so if the chosen package is available in our repo.

-pinoc

[bigsite]

I know  , makes me a black sheep here sometimes.......... I don't abdicate installing outside the repos, it is just that for this one install it resulted in no borked items, note I said "having kde menu....etc.".........just on a 1 in a 1000 package situation that saved me time and didn't do any harm.........well, OOO is probably the only thing I would install outside the repos anyway........

[xheralt]

Situation has recurred -- on a machine I *thought* I'd installed OO to but apparrently overlooked.  Am now trying this procedure (from another thread):

could you please try the following:
- in a root-terminal enter: apt-get clean
- open Synaptic and enable the openoffice repo
- in Synaptic, click Reload, then search for and install: task-openoffice3-en-US
- after the installation disable the openoffice repo in Synaptic

So far, it seems to be working.   But now I ALSO have OO borked up on another machine as well, possibly needing reinstall.  Unless the OO.org folks can help me straighten it out from their side first...

[pinoc]

Hi xheralt,

a) if you use YouCanToo's frozen repo then:
- start Synaptic, press Reload, and update/install getopenoffice 1.6-2
b) if you use any other repo (don't use belnet)
- install getopenoffice 1.6-1 as instructed here

then if your OO is borked:
- run getopenoffice and select to completely uninstall OO.
- only if you installed OO3.2 already: open a root-konsole and enter: apt-get clean     
   or start Synaptic, Settings -> Preferences -> Files: Delete Cached Package Files
- run getopenoffice and install a fresh version of OO3.2

if this does help then there is something else broken on your system. In this case just wait for the new 2010 iso to come out soon.
good luck,
-p.

[peter_pclos]

I have just bitten on the bullet and installed KDE4 on my PCLinuxOS
OS, with two problematical results.

The first problem was that, after an initial successful start-up of
KDE4 using my usual user account, all subsequent attempts resulted in a
washed-out, empty startup screen as soon as the first kde icon had
displayed, followed by a black screen as the KDE4 startup had completed. 
Fortunately I was able to do a re-start and log in successfully as another
existing user, create a new user for test purposes, and copy the .kde
folder in the home directory of this new user to replace the .kde folder
in my usual user account. Once I had (as root) changed the permissions
throughout the new .kde folder to correspond to my usual username, I was
able to log in normally as myself, with a fully functioning KDE4 desktop. 
However, Dolphin defaults to the home directory of the new user, so I presume
I need to replace the new username by my old username somewhere in the .kde
directory in my old home directory?

My second problem related to OpenOffice, which was automatically removed
from the system by the KDE4 upgrade.  As recommended, I checked via Synaptic to
ensure my system was up to date and that there were no broken files, then
downloaded getopenoffice, and once it was installed, invoked it from the system >
configuration menu.  Despite many attempts, and sundry searches in the Forum,
I have still not succeeded in getting OpenOffice, and am stuck with using
a (Linux-powered) Netbook with OpenOffice installed, exporting the .odt
file to PDF and transferring the PDF file via a USB memory stick to my
desktop PC for printing.  It's all a bit roundabout, and I need to get
access to OpenOffice on the desktop machine asap.

To try to analyse the problem, I have run getopenoffice from Konsole. On
the desktop, at least one (but probably more) message window opens near
the beginning of the process but closes too rapidly to be able to read it. I think
the first one is probably the one which asks what action (install/remove etc) is
required. The first usable message window is the language selector, which does persist,
then a window opens to enable confirmation of the downloading of missing
fonts, while the final window tells me that the operation has failed,
with the following message:

OpenOffice could not be installed due to either
- Internet connection failure or interupt, or
- manual interupt of the OpenOffice installation.
Please try running GetOpenOffice again a little later.

My internet connection is up and running, I have not manually
interrupted the installation, and I have also tried using hard-
coded DNS URLs, as suggested elsewhere in the forum,
without any change to the result.

The full Konsole output (including empty lines, so keep scrolling!) is:

[root@localhost petern]# getopenoffice


























[root@localhost petern]# stdin: is not a tty
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
/var/cache/apt/archives/partial found                               
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
freebsd available                                                   
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Java found                                                           
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".

[pinoc]

Hi peter_pclos,
and you made sure to not have any broken packages on your system and you did run version 1.6 as outlined in the previous post?
Please try this with getopenoffice 1.6:
- run getopenoffice and select to completely remove OO
- open a root-konsole and enter: apt-get clean     
   or start Synaptic, Settings -> Preferences -> Files: Delete Cached Package Files, then close Synaptic
- run getopenoffice and install a fresh version of OO3.2

if you still have problems then something else is wrong on your current system. In this case the easiest solution is to wait some days for the new public beta of 2010.
good luck,
-p.