Apache OpenOffice (AOO) Bugzilla – Issue 9431
Long startup times ( 3 mins > ), SIOCGIFADDR error message
Last modified: 2013-08-07 14:38:26 UTC
I needs more than 3 minutes to launch OOWriter without any document as parameter. I previously needed ~10 seconds. I get the following error messages in the console: - when finished to be launched: SIOCGIFADDR got '00:00:00:00:00:00' - after stopping: SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' When I open an OOWriter document, up to the window border drawing, it takes the same time as normally (~10 seconds). I saw the progress bar which was fully filled and which then disappears. Then it take more than 3 minutes to draw the content of the window. It is drawn suddenly. I don't know what I changed to get this behavior.
I forgot to say that I only get the splash screen when launched without arguments. After several minutes, splash screen suddenly disappear and the OOWriter window appear quickly with its new document inside.
It seems that I get the same behavior for other OO components: - OOImpress: blocked on the window 'Autopilot de présentation' (witout content) and then I can follow the 'Autopilot de présentation'. log: SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' - OODraw: blocks on splash screen and then appears log: SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' - OOCalc: blocks on splash screen and then appears log: SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' - OOWriter (presiously described) blocks on splash screen and appears log: SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00' SIOCGIFADDR got '00:00:00:00:00:00'
Sophia, thank you for using and supporting OOo. What has changed on your system since the last time OOo started up quickly for you?
I don't know. I changed my Internet connection configuration. It was previously with Ethernet card and now with ADSL on USB via ppp.
SIOCGIFADDR is a network layer call. There is a networking problem happening here. Try setting Tools->Options->Proxy to None Also try manually set the DNS to a valid DNS server. I'm going to search for more info.
*** Issue 9234 has been marked as a duplicate of this issue. ***
Sophia, does your machine have a hostname? If not, try setting one manually.
I specified manually the DNS server. The proxy value was already to None. But the bug still exist. --- [j@penguin j]$ hostname penguin --- Why do I need to get a network connection for working on a local document ? If so, why a blocking call ? Can it be threaded ? Is it to use a component service ?
I never used Internet inside OO. But if OO makes it alone, maybe is it a misstake.
My lo interface was not activated. route was: [root@penguin j]# route Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface AGrenoble-101-1 * 255.255.255.255 UH 0 0 0 ppp0 default AGrenoble-101-1 0.0.0.0 UG 0 0 0 ppp0 Then I made: [root@penguin sysconfig]# ifup lo [root@penguin sysconfig]# route Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface AGrenoble-101-1 * 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default AGrenoble-101-1 0.0.0.0 UG 0 0 0 ppp0 No problem now. Can OO pop an error message saying local loop not available ?
Sophia, thanks for the additional information. I think you've helped us find a resolution to an issue we've see pop up all over the place. User summary more than 3 minutes to start
Summary: User experiences long OOo startup times ( 3 minutes or more ). User sees SIOCGIFADDR network error message. I've seen an explaination in issue 254, and 353 is the earliest issue that I've seen this error message in. PM->OF: Is this a bug or an enhancment request? I'm sorry if I sent this issue to the wrong group.
*** Issue 9767 has been marked as a duplicate of this issue. ***
Could this be reproduced in 1.1 RC4?
I tested the 1.1 rc3 version (rc4 not available). I used the following configuration (lo interface down): [root@laptop j]# ifconfig eth0 Lien encap:Ethernet HWaddr 08:00:46:4C:E7:FD UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interruption:10 Adresse de base:0x800 ppp0 Lien encap:Protocole Point-Ã -Point inet adr:193.251.23.253 P-t-P:193.251.23.1 Masque:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:101501 errors:0 dropped:0 overruns:0 frame:0 TX packets:129401 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:3 RX bytes:38595700 (36.8 Mb) TX bytes:17764717 (16.9 Mb) [root@laptop j]# route Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface AGrenoble-101-1 * 255.255.255.255 UH 0 0 0 ppp0 default AGrenoble-101-1 0.0.0.0 UG 0 0 0 ppp0 [root@laptop j]# I tested the following programs: [j@laptop j]$ soffice [j@laptop j]$ swriter [j@laptop j]$ simpress [j@laptop j]$ sdraw [j@laptop j]$ scalc [j@laptop j]$ The programs started as slow as usualy (it's always too slow) but were not blocked as in the last bug report. No error messages told I didn't configured my lo interface. It seems to be fixed.
.
*** Issue 35493 has been marked as a duplicate of this issue. ***
I observed the following behavior: after upgrade to 1.1.2rc3 started oowriter very slowly. Loopback interface was already up. After I opened a document and closed them started oowriter completely normally. Sorry for my bad english