Alle domenica 21 luglio 2013, Philipp Hagemeister ha scritto: > On 07/21/2013 12:44 PM, Pino Toscano wrote: > > Does this happen any time, or (for example) after resuming from > > suspend? > > It has happened multiple times (so before and after I rebooted), and > most of the times after a suspend (but that's just because I'm using > suspend twice or three times a day, and only rebooting every couple > of months or so). I've tried it out a little bit: Akregator seems to > update itself just after the resume. I can't reboot right now > (long-running process without statefile :( ), but I'll try to > reproduce the problem just after a reboot asap.
Ok, so both at login after boot and after resume, but not always. I see you already reported it upstream [1]; there was also an existing bug [2] although that says explicitly about resuming (only). [1] https://bugs.kde.org/show_bug.cgi?id=322602 [2] https://bugs.kde.org/show_bug.cgi?id=312595 > > $ qdbus org.kde.kded /modules/networkstatus networks $ qdbus > > org.kde.kded /modules/networkstatus status > > $ qdbus org.kde.kded /modules/networkstatus networks > SolidNetwork > ntrack > $ qdbus org.kde.kded /modules/networkstatus status > 1 Hm, it'd seem like the ntrack backend explicitly reports "not connected" somehow, not sure why (especially if you say that you are connected fine -- and the ntrack libraries do not provide utilities). In the meanwhile, you could try to manually set a connected state for the SolidNetwork network: $ qdbus org.kde.kded /modules/networkstatus setNetworkStatus \ "SolidNetwork" 4 -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.
