Version: (using KDE 4.1.3) OS: Linux Installed from: Gentoo Packages The startup time with yukon network card bugged under linux is very long (4min). For network card I need try restart it 4x at 6x.
How is your network card bugged? Does it have a hardware failure? Is it configured at your Linux config? Have you tried to blacklist it or block it ? Thanks
When I block it all work. But if hardware failed or kernel problem in network layer, the starting is very long, strange because all probe is done in async?
Is the "long loading time" happening on the boot, during the Linux start? If it is that way, this is completely unrelated to KDE and this issue will be marked as INVALID. You should need to report this to your Distribution or to the Kernel itself. Regards
No, linux boot, but ksplash in very long to load, and KDE incoming in 50s but 10s with network card operationnal.
Do you need that buggied network card ? Do you have an option to blacklist it / not load its modules / do not use it ? I guess it is related to the network options, or the network interface being enabled or not (or misconfigured) during the login process. It still reminds me a similar bug on KDE3 when the loopback device was not properly set.
The card is in my laptop, and I work often in internet with it. Then I can't disable it. Can you async in thread the configuration and access at the network card for prevent this bug and continue login process with blocking network card.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!