Although I had a perfectly serviceable configuration for my home wireless in /etc/sysconfig/network-scripts/ifcfg-Auto_Baythorne_Wavelan, NetworkManager seems to have taken it upon itself to create a *new* one, called ifcfg-Auth_Baythorne_Wavelan-1. This is particularly problematic because of bug 851233, which means that all newly created configs are *misconfigured* to break network connectivity. This time, the combination of these two bugs meant that I lost contact with a remote host right in the middle of a 'yum upgrade' from Fedora 15 to 16. Which I'd stupidly forgotten to run in 'screen'. And there was much rejoicing... The mtime on the new file seems to be October 2nd at 21:45, and I'll attach some logs from about that time in case they shed any light on why it did it...
Created attachment 635439 [details] syslog from when new config was created Both ifcfg-Auto_Baythorne_Wavelan-1 and the corresponding keys-… file have an mtime of 21:45:53 so I'm guessing that's when it was created. Are there any other reasons it would be updated, when I only connect to it and don't ever use the editor to change anything? Looking at the logs from just before that time, it looks like something was playing silly buggers and I ended up unloading and reloading the b43 module. If I could be more specific about what 'playing silly buggers' meant, I'd have filed that in a separate bug...but I haven't properly diagnosed that one yet.
Reassigning to gnome-shell in response to Jirka's comment at https://bugzilla.redhat.com/show_bug.cgi?id=851233#c8
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.