[Bug 902771] New: No network with wireless card and wicked service
http://bugzilla.suse.com/show_bug.cgi?id=902771 Bug ID: 902771 Summary: No network with wireless card and wicked service Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: pilotgi@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After bug #893678 was marked as a duplicate of #895447 I am creating a new bug as I am still unable to get a network connection with my wireless card and wicked. I followed the instructions from the last comment of bug #893678 to shut down NetworkManager and verify that wicked is the only service running. Here is the output of 'systemctl status network.service wickedd.service wpa_supplicant.service NetworkManager.service' wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Mon 2014-10-27 12:41:05 CDT; 4min 44s ago Process: 917 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 917 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Oct 27 12:41:05 linux-0a83 wicked[917]: device enp9s0 failed: operation timed out Oct 27 12:41:05 linux-0a83 wicked[917]: device wlp5s5 failed: operation timed out Oct 27 12:41:05 linux-0a83 wicked[917]: lo up Oct 27 12:41:05 linux-0a83 wicked[917]: enp9s0 setup-in-progress Oct 27 12:41:05 linux-0a83 wicked[917]: wlp5s5 setup-in-progress wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:35 CDT; 5min ago Main PID: 903 (wickedd) CGroup: /system.slice/wickedd.service └─903 /usr/sbin/wickedd --systemd --foreground Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol AKA Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol AKA' Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol FAST Oct 27 12:40:36 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 12:40:37 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease wpa_supplicant.service - WPA Supplicant daemon Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:33 CDT; 5min ago Main PID: 815 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service └─815 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_sup... Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) And here is the result of the same command with ethernet connected: wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Mon 2014-10-27 13:10:09 CDT; 8min ago Process: 4483 ExecStop=/usr/sbin/wicked --systemd ifdown all (code=exited, status=0/SUCCESS) Process: 2630 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS) Process: 4490 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 4490 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Oct 27 13:10:09 linux-0a83 wicked[4490]: device wlp5s5 failed: operation timed out Oct 27 13:10:09 linux-0a83 wicked[4490]: lo up Oct 27 13:10:09 linux-0a83 wicked[4490]: enp9s0 up Oct 27 13:10:09 linux-0a83 wicked[4490]: wlp5s5 setup-in-progress wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:35 CDT; 37min ago Main PID: 903 (wickedd) CGroup: /system.slice/wickedd.service └─903 /usr/sbin/wickedd --systemd --foreground Oct 27 13:04:39 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:06:26 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:06:26 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:08:19 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:08:19 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:08:53 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:08:53 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:09:39 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:09:39 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:09:41 linux-0a83 wickedd[903]: enp9s0: Notified neighbours about IP address 192.xxx.x.xx wpa_supplicant.service - WPA Supplicant daemon Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:33 CDT; 37min ago Main PID: 815 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service └─815 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_sup... Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) And the result of 'ps axwww | grep -E "dhc|NetworkManager" | grep -v grep' 900 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground 901 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground enp9s0 is set to 'Connect automatically on cable connection'. If I unplug the cable and reboot, I have to restart the network 3-4 times after conncecting the cable before I get a connection -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 kevin vandeventer <pilotgi@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pilotgi@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Christoph Feck <christoph@maxiom.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christoph@maxiom.de --- Comment #1 from Christoph Feck <christoph@maxiom.de> --- I can confirm that the issue is also occuring without NetworkManager being installed (no output from "rpm -qa | grep -i networkmanager"). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pwieczorkiewicz@suse.com --- Comment #2 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- (In reply to Christoph Feck from comment #1)
I can confirm that the issue is also occuring without NetworkManager being installed (no output from "rpm -qa | grep -i networkmanager").
We still have not received proper logs with disabled NetworkManager. Please provide them. Here is how to do it: ‒ set DEBUG=all in /etc/sysconfig/network/config ‒ systemctl restart wickedd ‒ wicked --debug all ifup all # systemctl restart wicked ‒ wicked ifstatus all > status.log ‒ wicked show-config > configs.log ‒ journalctl -b -o short-iso > wicked.log - edit /usr/lib/systemd/system/wpa_supplicant.service file: -ExecStart=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log +ExecStart=/usr/sbin/wpa_supplicant -dddt -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log - systemctl daemon-reload - systemctl restart wpa_supplicant reproduce the issue and attach: status.log, configs.log, wicked.log and /var/log/wpa_supplicant.log Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pilotgi@gmail.com | |) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #3 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> ---
enp9s0 is set to 'Connect automatically on cable connection'. If I unplug the cable and reboot, I have to restart the network 3-4 times after conncecting the cable before I get a connection
This can be fixed by enabling nanny. Which is supposed to deal with hotplug scenarios like the one above. In order to do so edit /etc/wicked/common.xml - <use-nanny>false</use-nanny> + <use-nanny>true</use-nanny> and call: systemctl restart wickedd wicked ifup enp9s0 you should be able to plug in and unplug the cable and the network should be configured automatically for you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #4 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- (In reply to Christoph Feck from comment #1)
I can confirm that the issue is also occuring without NetworkManager being installed (no output from "rpm -qa | grep -i networkmanager").
Please provide logs as requested in the comment #2. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #5 from kevin vandeventer <pilotgi@gmail.com> --- (In reply to Pawel Wieczorkiewicz from comment #3)
enp9s0 is set to 'Connect automatically on cable connection'. If I unplug the cable and reboot, I have to restart the network 3-4 times after conncecting the cable before I get a connection
This can be fixed by enabling nanny. Which is supposed to deal with hotplug scenarios like the one above.
In order to do so edit /etc/wicked/common.xml
- <use-nanny>false</use-nanny> + <use-nanny>true</use-nanny>
and call: systemctl restart wickedd wicked ifup enp9s0
you should be able to plug in and unplug the cable and the network should be configured automatically for you.
The only text in my /etc/wicked/common.xml is 'false'. I also have /etc/wicked/nanny.xml but it is blank. Should I change false to true in the common.xml file? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com --- Comment #6 from Marius Tomaschewski <mt@suse.com> --- (In reply to kevin vandeventer from comment #5)
systemctl restart wickedd wicked ifup enp9s0 ^^^^^^ all
All config has to be reapplied.
The only text in my /etc/wicked/common.xml is 'false'.
Then the file is broken, please reinstall wicked.
I also have /etc/wicked/nanny.xml but it is blank.
No, do not touch nanny.xml. It is for nanny only. The use-nanny flag is also used in nanny but basically most important in the _client_ which has to feed the config into nanny and not into the wickedd directly.
Should I change false to true in the common.xml file?
It needs this content: <!-- Common configuration file sourced by all application-specific files --> <config> <piddir path="/run/wicked" mode="0755"/> <statedir path="/run/wicked" mode="0755"/> <storedir path="/var/lib/wicked" mode="0755"/> <!-- Config options specific to DBus service --> <dbus> <service name="org.opensuse.Network" /> <schema name="/usr/share/wicked/schema/wicked.xml"/> </dbus> <!-- Use nanny or not: 'false': causes ifup (and ifreload) to apply the config directly into wickedd without nanny involved (one shot setup). 'true': causes ifup (and ifreload) to apply a policy with the effective config to nanny and nanny configures wickedd then; with hotplug support. After a change, restart wickedd.service and execute "wicked ifup all" to (re)apply the config / policies. --> <use-nanny>true</use-nanny> <!-- If you want to make changes to this file, consider putting your changes into /etc/wicked/local.xml instead. Otherwise, you may lose your changes when applying future maintenance updates. --> <include name="local.xml" optional="true" /> </config> -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #7 from kevin vandeventer <pilotgi@gmail.com> --- I used YaST to uninstall wicked and libwicked-0-6. After reinstallation, /etc/wicked/common.xml still only contains one word: false. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #8 from Marius Tomaschewski <mt@suse.com> --- # echo true > /etc/wicked/common.xml # cat /etc/wicked/common.xml true # zypper in -f wicked wicked-service libwicked-0-6 Loading repository data... Reading installed packages... Forcing installation of 'wicked-0.6.12-1.1.x86_64' from repository 'Main Repository (OSS)'. Forcing installation of 'wicked-service-0.6.12-1.1.x86_64' from repository 'Main Repository (OSS)'. Forcing installation of 'libwicked-0-6-0.6.12-1.1.x86_64' from repository 'Main Repository (OSS)'. Resolving package dependencies... The following 3 packages are going to be reinstalled: libwicked-0-6 wicked wicked-service 3 packages to reinstall. Overall download size: 847.0 KiB. Already cached: 0 B No additional space will be used or freed after the operation. Continue? [y/n/? shows all options] (y): Retrieving package libwicked-0-6-0.6.12-1.1.x86_64 (1/3), 343.9 KiB (1020.7 KiB unpacked) Retrieving: libwicked-0-6-0.6.12-1.1.x86_64.rpm ....................................[done] Retrieving package wicked-0.6.12-1.1.x86_64 (2/3), 463.2 KiB ( 1.5 MiB unpacked) Retrieving: wicked-0.6.12-1.1.x86_64.rpm ..............................[done (97.1 KiB/s)] Retrieving package wicked-service-0.6.12-1.1.x86_64 (3/3), 39.9 KiB ( 9.2 KiB unpacked) Retrieving: wicked-service-0.6.12-1.1.x86_64.rpm ...................................[done] Checking for file conflicts: .......................................................[done] (1/3) Installing: libwicked-0-6-0.6.12-1.1 .........................................[done] (2/3) Installing: wicked-0.6.12-1.1 ................................................[done] Additional rpm output: Updating /etc/sysconfig/network/config... (3/3) Installing: wicked-service-0.6.12-1.1 ........................................[done] # cat /etc/wicked/common.xml true # ls -l /etc/wicked/common.xml* -rw-r--r-- 1 root root 5 Nov 17 15:24 /etc/wicked/common.xml Hmm... A "%config(noreplace) %_sysconfdir/wicked/common.xml" should at least create a "/etc/wicked/common.xml.rpmnew"... why it doesn't? # zypper -v in -f -d wicked # find /var/cache/zypp/ -name wicked-0.6.12-1.1.x86_64.rpm /var/cache/zypp/packages/download.opensuse.org-oss_1/suse/x86_64/wicked-0.6.12-1.1.x86_64.rpm # cat /etc/wicked/common.xml true # rpm -Uvvvh /var/cache/zypp/packages/download.opensuse.org-oss_1/suse/x86_64/wicked-0.6.12-1.1.x86_64.rpm --force 2>out Preparing... ################################# [100%] Updating / installing... 1:wicked-0.6.12-1.1 ################################# [100%] Updating /etc/sysconfig/network/config... # grep common.xml out D: skip 100644 1 ( 0, 0) 1161 /etc/wicked/common.xml;546a0744 Hmm... it still skips it. Please use this as workaround: # rm /etc/wicked/common.xml # zypper in -f wicked wicked-service libwicked-0-6 Please verify the installation using: rpm -V wicked wicked-service libwicked-0-6 the output should be empty. When not, remove all modified files and repeat. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@suse.com Flags| |needinfo?(mls@suse.com) --- Comment #9 from Marius Tomaschewski <mt@suse.com> --- Michael, any idea why rpm does not install at least a ".rpmnew" file, but just silently skips install? This is a new behavior to me... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #10 from kevin vandeventer <pilotgi@gmail.com> --- I followed the instructions from comment 8 to reinstall wicked. After, the result of 'ls -l /etc/wicked/common.xml*' is: -rw-r--r-- 1 root root 1161 Oct 14 01:02 /etc/wicked/common.xml The date is still from last month and the file still says 'false'. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #11 from Bernhard Wiedemann <bwiedemann@suse.com> --- (In reply to kevin vandeventer from comment #10)
I followed the instructions from comment 8 to reinstall wicked. After, the result of 'ls -l /etc/wicked/common.xml*' is:
-rw-r--r-- 1 root root 1161 Oct 14 01:02 /etc/wicked/common.xml
The date is still from last month and the file still says 'false'.
1161 is the correct size of the original file, though. How did you see the "false" ? did you try vim? You can get the correct one with old /etc/wicked/common.xml ; zypper in -f wicked -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 Michael Schröder <mls@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mls@suse.com) | --- Comment #12 from Michael Schröder <mls@suse.com> --- It doesn't create a rpmnew file if the file didn't change in the update, i.e. the old rpm and the new rpm contained the same config file. That's because in that case rpm knows that the user changed the file, and it makes sense to keep the change. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #13 from kevin vandeventer <pilotgi@gmail.com> --- (In reply to Bernhard Wiedemann from comment #11)
(In reply to kevin vandeventer from comment #10)
I followed the instructions from comment 8 to reinstall wicked. After, the result of 'ls -l /etc/wicked/common.xml*' is:
-rw-r--r-- 1 root root 1161 Oct 14 01:02 /etc/wicked/common.xml
The date is still from last month and the file still says 'false'.
1161 is the correct size of the original file, though. How did you see the "false" ? did you try vim?
You can get the correct one with old /etc/wicked/common.xml ; zypper in -f wicked
I see now that the default app to open the common.xml file is Konqueror, while I was assuming it was KWrite. Konqueror is the one that just shows 'false'. If I use KWrite to open the file, it has content similar to the example in comment 6 from Mr. Tomaschewski except instead of-- <use-nanny>true</use-nanny> I have <use-nanny>false</use-nanny> Also, I have no /etc/wicked/local.xml I tried using the 'old /etc/wicked/common.xml ;' command, but the new common.xml file still says it was created Oct 14. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #14 from Marius Tomaschewski <mt@suse.com> --- (In reply to kevin vandeventer from comment #13)
If I use KWrite to open the file, it has content similar to the example in comment 6 from Mr. Tomaschewski except instead of-- <use-nanny>true</use-nanny>
I have <use-nanny>false</use-nanny>
OK, then please either _change_ it to <use-nanny>true</use-nanny>, e.g. using: old /etc/wicked/common.xml sed -e 's|<use-nanny>false</use-nanny>|<use-nanny>true</use-nanny>|g' -i /etc/wicked/common.xml or create a local.xml containing it: printf "<config>\n\t<use-nanny>true</use-nanny>\n</config>\n" > /etc/wicked/local.xml both commands have to be executed as root of course. Then verify that the file is changed: grep use-nanny /etc/wicked/*.xml and contains a <use-nanny>false</use-nanny> now, then restart wickedd and reapply the configs: rcwickedd restart # note: wickedd with 2 * d here wicked ifup all or reboot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=902771 --- Comment #16 from kevin vandeventer <pilotgi@gmail.com> --- I noticed an update to wicked today so I thought I would try to reconnect with wicked.service. Still no luck. It's still showing 'setup-in-progress' for both ethernet and wireless. Here is some output after shutting down NetworkManager and starting wicked. linux:/home/kevin # systemctl status network.service wickedd.service wpa_supplicant.service NetworkManager.service -l wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Fri 2015-01-02 08:59:19 CST; 7min ago Process: 4512 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 4512 (code=exited, status=0/SUCCESS) Jan 02 08:59:19 linux.site wicked[4512]: lo up Jan 02 08:59:19 linux.site wicked[4512]: enp9s0 setup-in-progress Jan 02 08:59:19 linux.site wicked[4512]: wlp5s5 setup-in-progress wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: active (running) since Fri 2015-01-02 08:58:33 CST; 7min ago Main PID: 4502 (wickedd) CGroup: /system.slice/wickedd.service └─4502 /usr/sbin/wickedd --systemd --foreground Jan 02 08:58:49 linux.site wickedd[4502]: unable to translate eap protocol AKA Jan 02 08:58:49 linux.site wickedd[4502]: unable to translate eap protocol AKA' Jan 02 08:58:49 linux.site wickedd[4502]: unable to translate eap protocol FAST Jan 02 08:58:49 linux.site wickedd[4502]: lo: address 127.0.0.1 covered by a static lease Jan 02 08:58:49 linux.site wickedd[4502]: lo: address ::1 covered by a static lease wpa_supplicant.service - WPA Supplicant daemon Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled) Active: active (running) since Fri 2015-01-02 08:58:11 CST; 8min ago Main PID: 4493 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service └─4493 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log Jan 02 08:58:49 linux.site wpa_supplicant[4493]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Jan 02 08:58:49 linux.site wpa_supplicant[4493]: ioctl[SIOCSIWENCODEEXT]: Invalid argument NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) since Fri 2015-01-02 08:55:52 CST; 10min ago Main PID: 781 (code=exited, status=0/SUCCESS) Jan 02 08:55:52 linux.site NetworkManager[781]: Received signal 15, initiating shutdown. Jan 02 08:55:52 linux.site NetworkManager[781]: DHCPRELEASE on wlp5s5 to 192.168.1.254 port 67 (xid=0x4a8c3e69) Jan 02 08:55:52 linux.site NetworkManager[781]: <info> (wlp5s5): device state change: activated -> deactivating (reason 'removed') [100 110 36] Jan 02 08:55:52 linux.site NetworkManager[781]: <info> NetworkManager state is now DISCONNECTING Jan 02 08:55:52 linux.site NetworkManager[781]: <info> (wlp5s5): device state change: deactivating -> unmanaged (reason 'removed') [110 10 36] Jan 02 08:55:52 linux.site NetworkManager[781]: <info> (wlp5s5): deactivating device (reason 'removed') [36] Jan 02 08:55:52 linux.site NetworkManager[781]: <warn> (wlp5s5): DHCP client pid 1474 didn't exit, will kill it. Jan 02 08:55:52 linux.site NetworkManager[781]: <info> (wlp5s5): canceled DHCP transaction, DHCP client pid 1474 Jan 02 08:55:52 linux.site NetworkManager[781]: <info> NetworkManager state is now DISCONNECTED Jan 02 08:55:52 linux.site NetworkManager[781]: (NetworkManager:781): GLib-CRITICAL **: Source ID 20 was not found when attempting to remove it -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com