SUMMARY STEPS TO REPRODUCE 1. ip addr delete ::1/128 dev lo 2. start skrooge 3. stop skrooke 4. ip addr add ::1/128 dev lo 5. start skrooge OBSERVED RESULT The first time skrooge is started it is very slow (start-up time of few minutes instead of seconds). If the IPv6 stack is completely disabled (ipv6.disable=1 as kernel parameter) or partially disabled (echo 1 | tee /proc/sys/net/ipv6/conf/{lo,all,default}/disable_ipv6) or the IPv6 link local address is set, startup is fast. EXPECTED RESULT Always fast startup independent of used IP addresses. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The missing link local address was not on purpose, so finding the root cause fixed this bug for me. Although it would probably be better to not depend on an IPv6 link local address, the important thing is to document this behavior (which this bug report does, at least to some extent).
Hi, I'm not a network specialist and I don't know how to reproduce this issue to try to fix it. My distribution is KDE Neon (based on ubuntu). Do you know how I can reproduce this issue? I tried this: sudo ip addr delete ::1/128 dev lo skrooge But Skrooge starts normally (no performance issue). Thank you in advance if you can help me. Regards.
Hi, what you did triggers it here (just reconfirmed). Unfortunately, I do not have any idea how you could reproduce it besides this way. I am on Debian testing on a 5.5 kernel, which should be close to what KDE Neon provides. Thanks a lot for your effort, but honestly I guess there is more important work than fixing this bug, as it seems to be non-reproducible on other systems and after adding ::1/128 it's neither a problem here. So all in all no one has an issue. So I am totally fine if you close the report. Kind regards Patrick