Public bug reported: Kubuntu 13.04 64-bits
When suspending to RAM and resuming, the network connectivity is not re- established on resume. I am expecting connectivity to be re-established and IP address assigned, but no IP is assigned. I am using a script to suspend to RAM, here is the command line launched: dbus-send --print-reply --dest='org.freedesktop.PowerManagement' /org/freedesktop/PowerManagement org.freedesktop.PowerManagement.Suspend To re-establish connectivity I tried 'service network-manager restart' but that doesn't re-establish it. Loging out KDE session and back in does not help either. When I resume, I get this: ----- ~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:21:91:21:d5:0d inet6 addr: fe80::221:91ff:fe21:d50d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4438 errors:0 dropped:0 overruns:0 frame:0 TX packets:4273 errors:4 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4355203 (4.3 MB) TX bytes:612818 (612.8 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:606 errors:0 dropped:0 overruns:0 frame:0 TX packets:606 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:59902 (59.9 KB) TX bytes:59902 (59.9 KB) ----- But in eth0 it should show like this: ----- eth0 Link encap:Ethernet HWaddr 00:21:91:21:d5:0d inet addr:1.2.3.4 Bcast:1.225.255.255 Mask:255.255.0.0 (the IP address has been changed for posting) inet6 addr: fe80::221:91ff:fe21:d50d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:235 errors:0 dropped:0 overruns:0 frame:0 TX packets:279 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:36696 (36.6 KB) TX bytes:27691 (27.6 KB) Interrupt:18 Base address:0x6c00 ----- It's missing the INET address line, for the most of it. Not sure if that's normal, but I also get this: ----- ~$ sudo ifup eth0 Ignoring unknown interface eth0=eth0. ----- I checked pm-suspend.log, here it is: ----- Mon Jun 3 16:34:17 EDT 2013: Awake. Mon Jun 3 16:34:17 EDT 2013: Running hooks for resume Running hook /etc/pm/sleep.d/novatel_3g_suspend resume suspend: /etc/pm/sleep.d/novatel_3g_suspend resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend: /usr/lib/pm-utils/sleep.d/99video: 22: /usr/lib/pm-utils/sleep.d/99video: shopt: not found /usr/lib/pm-utils/sleep.d/99video resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend: /usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable. Running hook /usr/lib/pm-utils/sleep.d/95hdparm-apm resume suspend: /usr/lib/pm-utils/sleep.d/95hdparm-apm resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/95anacron resume suspend: /usr/lib/pm-utils/sleep.d/95anacron resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend: /usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable. Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend: Reloaded unloaded modules. /usr/lib/pm-utils/sleep.d/75modules resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: not executable. (I do not have wlan so I disabled it) Running hook /etc/pm/sleep.d/11custom resume suspend: * Stopping fan speed regulator fancontrol ...done. network-manager stop/waiting network-manager start/running, process 3824 * Starting fan speed regulator fancontrol ...done. ----- As you can see I even tried to have a script run the network-manager restart, which it did successfully but still no IP assigned to eth0. Thank you ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in Ubuntu. https://bugs.launchpad.net/bugs/1187530 Title: Cannot re-establish network connection after resuming (from suspend to RAM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/1187530/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs