Bug 644990 - On Notebook: Resume problems with NetworkManager an NM-Applet
Summary: On Notebook: Resume problems with NetworkManager an NM-Applet
Keywords:
Status: CLOSED DUPLICATE of bug 638640
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-20 17:46 UTC by Juergen Dankoweit
Modified: 2010-11-02 03:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-02 03:18:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Juergen Dankoweit 2010-10-20 17:46:20 UTC
Description of problem:
After resuming my notebook (IBM Thinkpad T43) the NM-Applet shows me a disabled network and there is no connection to the network. Clicking on "Activate Network" does not activate the network connections. When I restart the NetworkManager then and only then the applet shows me the network connection and I have access to my network.
The notebook works correct after resume!

I tried:
dbus_send --print-reply --system                        \
	--dest=org.freedesktop.NetworkManager \
	/org/freedesktop/NetworkManager       \
	org.freedesktop.NetworkManager.wake

But no reaction of NetworkManager and NM-Applet.

Version-Release number of selected component (if applicable):
Sep 28 10:44:28 Updated: 1:NetworkManager-glib-0.8.1-6.git20100831.fc12.i686
Sep 28 10:44:35 Updated: 1:NetworkManager-0.8.1-6.git20100831.fc12.i686
Sep 28 10:44:54 Updated: 1:NetworkManager-gnome-0.8.1-6.git20100831.fc12.i686

How reproducible:
Waking up a notebook

Steps to Reproduce:
Open the display or push the "wake up button" for resuming the notebook
  
Actual results:
No connections to the network, NM-Applet shows a red cross to indicate that the network is disabled

Expected results:
Connection to the network, NM-Applet with no red cross sign

Additional info:
Restarting the NetworkManager ( /etc/init.d/NetworkManager restart ) solves the problem

Comment 1 Thomas Spura 2010-10-20 20:01:04 UTC
I also had this problem, could you retry with:
https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-9.git20100831.fc12


With the fc14 build resuming works as expected here.

Comment 2 Dan Williams 2010-10-20 22:31:52 UTC
Also when the notebook is in this state, please grab the output of:

nmcli nm status

Comment 3 Juergen Dankoweit 2010-10-21 21:15:10 UTC
Hello.

Thanks for looking at this bugreport.
Here is the additional information you requested:

nmcli nm status:
================
RUNNING         STATE           WIFI-HARDWARE   WIFI          WWAN-HARDWARE   WWAN      
wird ausgeführt schlafend       aktiviert       deaktiviert   aktiviert       aktiviert 
(running)       (sleeping)      (activated)     (deactivated) (activated)     (activated)

.xsession-errors:
=================
(gnome-power-manager:3835): devkit-power-gobject-DEBUG: DBUS timed out, but recovering
TI:22:44:00     FI:pk-task-list.c       FN:pk_task_list_connection_changed_cb,361
 - connected=1
TI:22:44:00     FI:pk-task-list.c       FN:pk_task_list_connection_changed_cb,361
 - connected=1
TI:22:44:00     FI:pk-control.c FN:pk_control_network_state_changed_cb,880
 - emitting network-state-changed: offline
TI:22:54:05     FI:pk-task-list.c       FN:pk_task_list_connection_changed_cb,361
 - connected=0
TI:22:54:05     FI:pk-task-list.c       FN:pk_task_list_connection_changed_cb,361
 - connected=0

** (nm-applet:3844): WARNING **: Error enabling/disabling networking: Already enabled [<- after trying to activate the network with nm-applet, btw nothing happend]

/var/log/messages (suspending notebook):
========================================
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> sleep requested (sleeping: no  enabled: yes)
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> sleeping or disabling...
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): now unmanaged
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): device state change: 8 -> 1 (reason 37)
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): deactivating device (reason: 37).
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): canceled DHCP transaction, DHCP client pid 16906
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): cleaning up...
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): taking down device.
Oct 21 21:19:35 t43 kernel: tg3 0000:02:00.0: PME# enabled
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (wlan0): now unmanaged
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (wlan0): device state change: 2 -> 1 (reason 37)
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (wlan0): cleaning up...
Oct 21 21:19:35 t43 NetworkManager[16366]: <info> (eth0): carrier now OFF (device state 1)

/var/log/messages (resuming notebook):
======================================
no entries!

command:
dbus-send --system --dest=org.freedesktop.NetworkManager \
 /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake
===============================
no entries in /var/log/messages!

Comment 4 Juergen Dankoweit 2010-11-01 05:00:07 UTC
(In reply to comment #1)
> I also had this problem, could you retry with:
> https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-9.git20100831.fc12
> 
> 
> With the fc14 build resuming works as expected here.

Sorry for late answering.

Updating to this version solves the suspend/resume problem. Thanks to the developer.

Best regards

Juergen

Comment 5 Juergen Dankoweit 2010-11-01 05:01:49 UTC
(In reply to comment #2)
> Also when the notebook is in this state, please grab the output of:
> 
> nmcli nm status

Hello Dan,

updating to NetworkManager-0.8.1-9.git20100831.fc12.i686 solved the resume problem. Thanks to the developer.

Best regards

Juergen

Comment 6 Dan Williams 2010-11-02 03:18:56 UTC
Excellent, thanks for the response.

*** This bug has been marked as a duplicate of bug 638640 ***


Note You need to log in before you can comment on or make changes to this bug.