Description of problem: To work around a wireless problem that causes NetworkManager to take a few minutes to reconnect after suspend/resume, I run the following script after resume: #!/bin/bash service NetworkManager stop service NetworkManagerDispatcher stop modprobe -r iwl3945 modprobe iwl3945 service NetworkManagerDispatcher start service MetworkManager start Version-Release number of selected component (if applicable): pidgin-2.4.0-1.fc8 libpurple-2.4.0-1.fc8 NetworkManager-0.7.0-0.6.7.svn3235.fc8 How reproducible: 60% Steps to Reproduce: 1. Connect to internet with NetworkManager 2. start pidgin 3. suspend system 4. resume system (reproduces better if the system is asleep for some time) 5. run wireless reset script Actual results: 1. pidgin segfaults as soon as NetworkManager completes configuring the connection with DHCP Expected results: 1. pidgin does not segfault Additional info: 1. I did not notice this problem happening before I added the NetworkManagerDispatcher steps to the script, but this may have been a coincidence, since it's not 100% reproducible, and the segfault appears as pidgin silently going away.
Woah, just died again, this time after a resume when NetworkManager was able to restore the wireless connection immediately, without running the script. I just realized that I don't think I ever saw this with the previous version of pidgin, so the addition of the NetworkManagerDispatcher logic in my script may be a pure coincidence. It's looking now like the new reconnect logic in pidgin is the culprit.
New failure mode: pidgin segfaults as soon as NetworkManager is restarted *before* it brings up the connection. Bottom line, pidgin does not like NetworkManager restarts at all.
This is probably a duplicate of bug 436641 but to confirm please install the debuginfo packages (with "debuginfo-install pidgin") and get a backtrace as described on http://fedoraproject.org/wiki/StackTraces
Ummm... that's a touchpad bug. My touchpad is disabled in the BIOS, and has been since before I did this install. Nothing on my system should be doing anything touchpad-related.
It gets weirder. A couple of times it has died several seconds after NetworkManager has finished bringing up the connection. Once was without needing to run the script. Pidgin reconnects to all my services, and then suddenly disappears a few seconds later. Something's just borked in the new pidgin connection restore code.
Sorry, typo, I meant bug 436631. Still waiting for the backtrace.
Yes, this does appear to be a duplicate of 436631. I am using AIM and Google Talk I get no backtrace on the console. Are you asking for a core? I can do that.
*** This bug has been marked as a duplicate of 436631 ***