Issue 24788 - Upon starting, OOO induces network activity
Summary: Upon starting, OOO induces network activity
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2004-01-24 16:28 UTC by berthierp
Modified: 2013-02-07 22:42 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description berthierp 2004-01-24 16:28:55 UTC
Upon starting, OOO 1.1.0 (645m19(Build:8693)) induces network activity, which
fires up dialup connection.  

This may be annoying because OOO waits for the dialup connection to be up before
it even displays the splash screen and goes further with the loading process. 
In my case, this can take 1-2 minutes using a "56k modem" kind of connection.

I am using Linux slackware 9.1, with loopback network configured, and with a
pppd daemon waiting for network accesses and firing up the dialup connection

I have read another issue (16186) which says that such problems may be related
to the use of gethostbyname() by OOO.  Just in case, I paste below my /etc/hosts
and /etc/resolv.conf + output of ifconfig (with ppp connection up).

root@normaskompi:~# cat /etc/hosts
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.  Just add the names, addresses
#               and any aliases to this file...
# By the way, Arnt Gulbrandsen <> says that
# should NEVER be named with the name of the machine.  It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
# For loopbacking.       localhost
# This next entry is technically wrong, but good enough to get TCP/IP apps
# to quit complaining that they can't verify the hostname on a loopback-only
# Linux box.       normaskompi
# End of hosts.
root@normaskompi:~# cat /etc/HOSTNAME
root@normaskompi:~# ifconfig
lo        Link encap:Local Loopback
          inet addr:  Mask:
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:458 (458.0 b)  TX bytes:458 (458.0 b)
ppp0      Link encap:Point-to-Point Protocol
          inet addr:  P-t-P:  Mask:
          RX packets:1271 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1298 errors:0 dropped:20 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:1170011 (1.1 Mb)  TX bytes:168742 (164.7 Kb)
root@normaskompi:~# cat /etc/resolv.conf
Comment 1 thorsten.martens 2004-02-10 13:08:19 UTC
TM->BH: Please have a look, thanks !
Comment 2 ace_dent 2008-05-16 02:57:40 UTC Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version:
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 3 bettina.haberer 2010-05-21 15:03:54 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".