https://bugs.kde.org/show_bug.cgi?id=276077
--- Comment #9 from S Clark <smc+kdebugs dogphilosophy net> 2011-07-14 01:40:51 --- Okay, one last note and I'll shut up - I finally got it to send by disconnecting and reconnecting, which I assume made KDE notice that I was connected (I had originally connected to the network before starting KDE). Once I did that, it looks like the stuck messages finally went through. It looks to me like solid/KDE has gotten stuck in the NetworkManager "why would you be connected to the network without starting a GUI login first?" thinking, so KDE assumes you're offline unless it gets a "we've just connected to the network" signal after starting. That would also explain the report on the forum from someone seeing this problem with a static IP as well. That's my guess anyway. The aspect of this bug that I would argue belongs to kmail is the lack of a warning or indication that the reason it's not sending is because it hasn't been told the network has been started (even though it runs IMAP just fine in the meantime.) Should a separate bug be opened for solid(?) about it not checking for a pre-existing network connection when KDE starts? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- 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
