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.
Is this still happening in Plasma 5.19 or a similarly recent version?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!