https://bugs.kde.org/show_bug.cgi?id=294441
--- Comment #39 from Lamarque V. Souza <lamar...@kde.org> --- (In reply to comment #37) > Hi all, I cannot reproduce this in Arch. This was an issue with 4.8.0, but > got fixed with the update to 4.8.1. Hmmm then maybe my commit d0ce3b783382016a0b6049a78066a5fdb089043b to kde-runtime-4.8.1 fixed this issue. NetworkManager emits the StatusChanged signal but network is not really accessible for a couple of seconds. My commit adds a 2s delay before networkstatus relays the StatusChanged signal to all other KDE programs. Maybe I need to increase the delay I contact NetworkManager developers to ony emit StatusChanged when network is really online. > Anyway, if Lamarque suggests to disable Ntrack from kde-runtime, I'll drop > it. Now I am not sure if ntrack is the culprit here, Kubuntu also enables NTrack by default and no Kubuntu user has complained so far. The problem with NetworkManager seems more logical to cause this problem. Does anyone here use Wicd? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
