On Sat, Jun 5, 2010 at 4:11 PM, Casimiro de Almeida Barreto
<casimiro.barreto@gmail.com> wrote:
> Em 05-06-2010 10:46, João Neto escreveu:
>> Hello,
>>
>> I have submitted a bug on Fedora Bugzilla:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=600656
>>
>> But i wonder if someone has had this problem before.
>>
>> This as ocurred after notebook suspend on KDE, and Network Manager do
>> not create any eth0 connection!
>>
> Same thing happened with me. My daughter put her notebook in "hibernate"
> state & when rebooted NetworkManager was unable to start any connection.
> Clicking the icon returned a "NetworkManager disabled" message, there
> was a DBus problem message at the /var/log/messages. I tried everything
> (system-config-network, enabling /etc/rc.d/init.d/network start, same
> for NetworkManager...), manually reconfig things, etc... Then used the
> Microsoft approach for such things: saved /home & reinstalled Fedora 13.
> Not a happy end...

Ugh..

You can either run
dbus_send --print-reply --system
--dest=org.freedesktop.NetworkManager
/org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.wake

or run
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

When you suspend there's a script that disable all interfaces, if you
wake up your laptop it runs again and starts it again. I guess you
didn't wakeup your laptop, but started normally after the suspend in
that case NM remains in disabled mode.

I replied to the bug as well.

--
LG Thomas

Dubium sapientiae initium
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Hi,

> You can either run
> dbus_send --print-reply --system
> * * * *--dest=org.freedesktop.NetworkManager
> * * * */org/freedesktop/NetworkManager
> * * * *org.freedesktop.NetworkManager.wake
>
> or run
> service network-manager stop
> rm /var/lib/NetworkManager/NetworkManager.state
> service network-manager start

I have been poking around NM lately, would this have the same effect?:

nmcli nm wakeup

I noticed nmcli is used from the networking scripts. Coincidentally I
saw a message on the local LUG about getting NM stuck and nothing
making it 'go' again.

-Cam
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

On Sat, Jun 5, 2010 at 6:57 PM, Camilo Mesias <camilo@mesias.co.uk> wrote:
> Hi,
>
>> You can either run
>> dbus_send --print-reply --system
>> * * * *--dest=org.freedesktop.NetworkManager
>> * * * */org/freedesktop/NetworkManager
>> * * * *org.freedesktop.NetworkManager.wake
>>
>> or run
>> service network-manager stop
>> rm /var/lib/NetworkManager/NetworkManager.state
>> service network-manager start
>
> I have been poking around NM lately, would this have the same effect?:
>
> nmcli nm wakeup

To be honest, i'm not really familiar with nmcli. I should have a
closer look at it, to stay uptodate. But it looks about right.

> I noticed nmcli is used from the networking scripts. Coincidentally I
> saw a message on the local LUG about getting NM stuck and nothing
> making it 'go' again.

The script i meant is: /usr/lib64/pm-utils/sleep.d/55NetworkManager
No nmcli used there.

--
LG Thomas

Dubium sapientiae initium
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

On Sat, 2010-06-05 at 10:46 -0300, João Neto wrote:
> Hello,
>
> I have submitted a bug on Fedora Bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=600656
>
> But i wonder if someone has had this problem before.
>
> This as ocurred after notebook suspend on KDE, and Network Manager do
> not create any eth0 connection!

This might be #589108; the symptom is that networking will be disabled
after a failed suspend/hibernate. The fix is committed upstream, and
should filter down into F13-updates soon.

Dan


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

2010/6/8 Dan Williams <dcbw@redhat.com>


This might be #589108; the symptom is that networking will be disabled

after a failed suspend/hibernate. *The fix is committed upstream, and

should filter down into F13-updates soon.
Ok Thanks!

I hope soon no
longer need to use ifconfig and dhclient to configure my network again!

--
Joao Neto - Web Developer | PHP Zend Certified Engineer
@joao_neto | http://www.joaoneto.blog.br



--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel