[kde] [Bug 342462] New: KDE starts delayed if internet is not accessible
Sönke Kraft
soenke.kraft at sackpfeyffer-zu-linden.de
Sat Jan 3 21:15:25 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=342462
Bug ID: 342462
Summary: KDE starts delayed if internet is not accessible
Product: kde
Version: unspecified
Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: soenke.kraft at sackpfeyffer-zu-linden.de
System: KDE 4.10.5; Slackware64 14.1; Kernel 3.17.4
Hardware: AMD and Intel x86_64-Processors, nvidia- & Ati-Graphics cards (nvidia
with nouveau open source or nvidia proprietory driver, Ati with radeon open
source driver)
Linux boots into console. KDE is started by entering the "startx" command:
KDE normally starts if the computer has access to the internet during KDE
start.
KDE starts with a delay of 10 to 20 seconds if the computer hasn't access to
the internet during KDE start. Only a cursor is blinking below the entered
"startx" command during the delay if the computer hasn't access to the internet
during KDE start. KDE starts with normal speed after the delay. The delay is
about 10 seconds if /etc/resolv.conf only contains nothing or one
"nameserver"-entry with the IP-address of local router. The delay is about 20
seconds if /etc/resolv.conf contains a "search"-entry. A KDE program tries to
access the world wide root-servers if /etc/resolv.conf doesn't contain any
"nameserver"-entry.
KDE 3.5.10 (Slackware64 13.0; Kernel 2.6.39.4) normally starts in same hardware
& network environment.
Reproducible: Always
Steps to Reproduce:
1. Boot Linux into console.
2. Start KDE without internet access and measure the time between pressing
<Enter> after entering "startx" and the first appearance of the X-window with
starting KDE splash screen.
3. Start KDE with internet access and measure the time between pressing <Enter>
after entering "startx" and the first appearance of the X-window with starting
KDE splash screen.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list