bcooksley wrote:Hmm, that is unfortunate then, as there is nothing of particular detail in there which can help.

Thank you for looking at it anyway.

bcooksley wrote:You'll need to ask the NetworkManager folks why this happens

And is the best way to email them? Is that the same email address you gave me in the other thread? (kde-hardware-devel@kde.org)

The NetworkManager folks are on a different mailing list I'm afraid - i'm not sure what is the best way to reach them.
I'll point the KDE Network Management dev(s) at this topic first to get confirmation and ask them what the next step is from here.

Thank you so much for doing that.

Hi, I read this thread and this looks like a driver issue. One of my wifi cards (Intel Ultimate-N 6300) also uses iwlwifi driver and my wifi connection auto-starts in less than 5s after my notebook resumes from disk or ram.

You can contact the NetworkManager guys in this mailing list https://mail.gnome.org/mailman/listinfo ... nager-list

You can start NetworkManager in debug mode using:

NetworkManager --no-daemon --log-level=debug 2> nm_debug.txt

You must stop NetworkManager before running the command above and must run it as root.

lamarque wrote:Hi, I read this thread and this looks like a driver issue. One of my wifi cards (Intel Ultimate-N 6300) also uses iwlwifi driver and my wifi connection auto-starts in less than 5s after my notebook resumes from disk or ram.

That sounds reasonable. It's annoying since it is a regression for me. Also, the vast majority of bugs that I encounter appear to be driver related (perhaps unsurprisingly).

lamarque wrote:You must stop NetworkManager before running the command above and must run it as root.

How should I stop NetworkManager? I tried

Code: Select all

sudo pkill NetworkManager

but it immediately started up again automatically.

You'll probably need to stop it using the appropriate init system command. This is probably "service networking stop" or similar on Ubuntu and it's derivates.

bcooksley wrote:I'll point the KDE Network Management dev(s) at this topic first to get confirmation and ask them what the next step is from here.

Hi bcooksley, I was just wondering if you had any update with this, or whether I should contact them myself with the details provided by lamarque? Cheers.

I would suggest going ahead and contacting them with the details provided by Lamarque (who is one of the developers who works on KDE Network Management).

Thanks again. I'll post there when I can. (My ISP's SMTP has just been blacklisted, so the mailing list is bouncing me right now. )

Was the rejection message from KDE infrastructure (postbox.kde.org) or another system?
If it is postbox.kde.org, then I'd like to know more details about the email in question (ISP being sent from, etc) so I can investigate to ensure it is not a problem with the spam filter.

Thanks for that, but it's just my ISP. It was rejected (I think at the recipient server) based on rules from uceprotect. I contacted my ISP, and they said they requested removal of the block. It's one of their four SMTP servers, and apparently was blacklisted based on someone sending spam.

Okay. That doesn't sound like our system then - as we perform blacklist evaluation in Spam Assassin.