On Mon, Nov 1, 2010 at 12:56 PM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com">awilliam@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, 2010-10-31 at 20:16 -0430, Patrick O'Callaghan wrote:<br>
<br>
> BTW the Live CD has exactly the same problem. I don't understand why<br>
> people aren't screaming about this. It's a very ordinary machine with<br>
> very standard hardware.<br>
<br>
</div>Just in case subsequent discussion didn't render it obvious, people<br>
mostly aren't screaming because this bug isn't a general one. On most<br>
systems, networking works fine. This has some hardware- or<br>
configuration-specific element to it.</blockquote><div><br></div><div>Clearly. I'm just trying to understand what it might be given that the identical hardware (a very common Intel LAN chip on an Intel mobo) on the identical network had no problems with any previous version of Fedora including F13, and I'm using a fresh install of the default Desktop profile of F14 with no changes whatsoever. It's particularly worrying that nm-applet gives a message complaining about not connecting to "the session bus" (presumably Dbus) followed by a core dump. I realize that it's not practical to test every possible combination of hardware and network before release, but given that the problem is real and reproducible I'm looking for suggestions to resolve it.</div>
<div><br></div><div>I've not yet reported this to BZ, mainly because copying the various messages and log files is going to have to be done the hard way, but I'll try and get round to it after work.</div><div><br>
</div><div>poc</div></div>