Bug 1070762

Summary: When using Fedora 20 with a Lenovo X230 in a dock, routes and Ip adress are kept even when em1 status is down
Product: [Fedora] Fedora Reporter: Sergio Ocón-Cárdenas <soconcar>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw, jklimes, soconcar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:08:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of log file none

Description Sergio Ocón-Cárdenas 2014-02-27 14:09:38 UTC 
Description of problem:
When connected with the fixed network through a dock (possibly also without it), when I disconnect from the dock the ip address is kept even when the link is down, keeping IP adress and default route associated to em1

Version-Release number of selected component (if applicable):
Network manager 1:0.9.9.0-30.git20131003.fc20

How reproducible:
Always

Steps to Reproduce:
1. Connect to a fixed network. Wait until an IP address is assigned to em1
2. Discconnect the network
3. ip link show em1, status is down
4. ip a show em1, ip address assgin3ed
5. ip r, routes show em1 as default 

Actual results:
Adress and routes are kept, making the network unusable. Even connecting to wireless won't chang3e routes. Connection is restored with an ifdown em1 command 


Expected results:
When link is down, ip is deleted and routes are changed 


Additional info:
Comment 1 Jirka Klimes 2014-03-04 17:12:52 UTC 
How do you disconnect the network in point 2?

would you post uptput of the "ip a" and "ip r" commands?
What nmcli say about devices, connections?
$ nmcli device
$ nmcli con show active
Comment 2 Sergio Ocón-Cárdenas 2014-03-14 15:25:01 UTC 
Laptop connected to dock
Undocked with the button.


----------------------------------------------------------------------------
-----------------------------------------------------------------------------

[sergio@sergio ~]$ ip a 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 3c:97:0e:ca:48:5d brd ff:ff:ff:ff:ff:ff
    inet 10.32.240.149/24 brd 10.32.240.255 scope global dynamic em1
       valid_lft 63728sec preferred_lft 63728sec
    inet6 fe80::3e97:eff:feca:485d/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether a4:4e:31:94:85:f0 brd ff:ff:ff:ff:ff:ff
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 52:54:00:60:6a:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500
    link/ether 52:54:00:60:6a:8d brd ff:ff:ff:ff:ff:ff
6: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 52:54:00:07:17:2c brd ff:ff:ff:ff:ff:ff
    inet 172.16.100.1/24 brd 172.16.100.255 scope global virbr1
       valid_lft forever preferred_lft forever
7: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN group default qlen 500
    link/ether 52:54:00:07:17:2c brd ff:ff:ff:ff:ff:ff
13: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr1 state UNKNOWN group default qlen 500
    link/ether fe:54:00:15:9d:6a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe15:9d6a/64 scope link 
       valid_lft forever preferred_lft forever
14: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 500
    link/ether fe:54:00:85:73:da brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe85:73da/64 scope link 
       valid_lft forever preferred_lft forever
[sergio@sergio ~]$ ip r
default via 10.32.240.254 dev em1  proto static  metric 1024 
10.32.240.0/24 dev em1  proto kernel  scope link  src 10.32.240.149 
10.38.5.26 via 10.32.240.254 dev em1  proto static  metric 1 
172.16.100.0/24 dev virbr1  proto kernel  scope link  src 172.16.100.1 
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
[sergio@sergio ~]$ nmcli em1
Error: Object 'em1' is unknown, try 'nmcli help'.
[sergio@sergio ~]$ nmcli dev em1
Usage: nmcli device { COMMAND | help }

  COMMAND := { status | show | disconnect | wifi }

  status

  show [<ifname>]

  disconnect <ifname>

  wifi [list [ifname <ifname>] [bssid <BSSID>]]

  wifi connect <(B)SSID> [password <password>] [wep-key-type key|phrase] [ifname <ifname>] [bssid <BSSID>] [name <name>]

               [private yes|no]

  wifi rescan [[ifname] <ifname>]

Error: 'dev' command 'em1' is not valid.
[sergio@sergio ~]$ nmcli dev status em1
Unknown parameter: em1
DEVICE      TYPE      STATE       
em1         ethernet  connected   
wlp3s0      wifi      unavailable 
lo          loopback  unmanaged   
virbr0-nic  tap       unmanaged   
virbr1-nic  tap       unmanaged   
vnet0       tap       unmanaged   
vnet1       tap       unmanaged   
[sergio@sergio ~]$ nmcli dev status 
DEVICE      TYPE      STATE       
em1         ethernet  connected   
wlp3s0      wifi      unavailable 
lo          loopback  unmanaged   
virbr0-nic  tap       unmanaged   
virbr1-nic  tap       unmanaged   
vnet0       tap       unmanaged   
vnet1       tap       unmanaged   
[sergio@sergio ~]$ nmcli con show active
NAME       UUID                                  DEVICES  DEFAULT  VPN  MASTER-PATH 
Profile 1  5ba5d152-33df-4e9d-abaf-0723fc1540cc  em1      yes      no   --          
[sergio@sergio ~]$ ip a 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 3c:97:0e:ca:48:5d brd ff:ff:ff:ff:ff:ff
    inet 10.32.240.149/24 brd 10.32.240.255 scope global dynamic em1
       valid_lft 63692sec preferred_lft 63692sec
    inet6 fe80::3e97:eff:feca:485d/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether a4:4e:31:94:85:f0 brd ff:ff:ff:ff:ff:ff
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 52:54:00:60:6a:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500
    link/ether 52:54:00:60:6a:8d brd ff:ff:ff:ff:ff:ff
6: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 52:54:00:07:17:2c brd ff:ff:ff:ff:ff:ff
    inet 172.16.100.1/24 brd 172.16.100.255 scope global virbr1
       valid_lft forever preferred_lft forever
7: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN group default qlen 500
    link/ether 52:54:00:07:17:2c brd ff:ff:ff:ff:ff:ff
13: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr1 state UNKNOWN group default qlen 500
    link/ether fe:54:00:15:9d:6a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe15:9d6a/64 scope link 
       valid_lft forever preferred_lft forever
14: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 500
    link/ether fe:54:00:85:73:da brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe85:73da/64 scope link 
       valid_lft forever preferred_lft forever
[sergio@sergio ~]$ ip r
default via 10.32.240.254 dev em1  proto static  metric 1024 
10.32.240.0/24 dev em1  proto kernel  scope link  src 10.32.240.149 
10.38.5.26 via 10.32.240.254 dev em1  proto static  metric 1 
172.16.100.0/24 dev virbr1  proto kernel  scope link  src 172.16.100.1 
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
[sergio@sergio ~]$ nmcli dev status 
DEVICE      TYPE      STATE       
em1         ethernet  connected   
wlp3s0      wifi      unavailable 
lo          loopback  unmanaged   
virbr0-nic  tap       unmanaged   
virbr1-nic  tap       unmanaged   
vnet0       tap       unmanaged   
vnet1       tap       unmanaged   
[sergio@sergio ~]$ nmcli con show active
NAME       UUID                                  DEVICES  DEFAULT  VPN  MASTER-PATH 
Profile 1  5ba5d152-33df-4e9d-abaf-0723fc1540cc  em1      yes      no   


---------------------------------------------------------------------------
---------------------------------------------------------------------------
--
Comment 3 Jirka Klimes 2014-04-29 08:52:03 UTC 
There's 4 seconds interval between carrier change (unpluging cable, undocking) and taking down the device. Does the device go down after 4 seconds?

Can you grab NM logs so that we can see what happens on undocking? (/var/log/messages or journalctl)
Comment 4 Sergio Ocón-Cárdenas 2014-04-29 15:31:32 UTC 
[sergio@sergio ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms

[sergio@sergio ~]$ cat "connecting to wifi"
cat: connecting to wifi: No such file or directory
[sergio@sergio ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 10.32.240.149 icmp_seq=1 Destination Host Unreachable
From 10.32.240.149 icmp_seq=2 Destination Host Unreachable
From 10.32.240.149 icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
pipe 3
[sergio@sergio ~]$ ifdown em1
[sergio@sergio ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=255 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=47 time=270 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 255.542/263.268/270.994/7.726 ms
[sergio@sergio ~]$
Comment 5 Sergio Ocón-Cárdenas 2014-04-29 15:32:24 UTC 
Created attachment 890848 [details]
Output of log file
Comment 6 Sergio Ocón-Cárdenas 2014-04-29 15:33:10 UTC 
To recover connection, ifup em1 is needed when connecting again to the doc
Comment 7 Sergio Ocón-Cárdenas 2014-10-31 09:43:30 UTC 
I've reinstalled Fedora 20 in my laptop.

For one month everything was fine, then after several packages upgrades, I got the same error.

When i disconnect from the dock the system reponds that em1 is down, but the connection is still up.

sergio@sergio manageiq]$ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet 10.32.243.158/24 brd 10.32.243.255 scope global dynamic wlp3s0
       valid_lft 3586sec preferred_lft 3586sec
3: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    inet 10.32.240.220/24 brd 10.32.240.255 scope global dynamic em1
       valid_lft 74442sec preferred_lft 74442sec


Journalctl -xn -f is:

Oct 31 10:37:46 sergio kernel: e1000e: em1 NIC Link is Down
Oct 31 10:37:46 sergio NetworkManager[1387]: <info> (em1): link disconnected...)
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046A:0011.0004: can't reset...71
Oct 31 10:37:46 sergio kernel: hid-generic 0003:046D:C046.0003: can't reset...71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 2 (0080) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8: USB disconnect, device number 6
Oct 31 10:37:46 sergio kernel: usb 2-1.8.2: USB disconnect, device number 8
Oct 31 10:37:46 sergio kernel: usb 2-1.8: clear tt 4 (0070) error -71
Oct 31 10:37:46 sergio kernel: usb 2-1.8.4: USB disconnect, device number 7
Oct 31 10:37:46 sergio kernel: thinkpad_acpi: EC reports that Thermal Table...ed
Oct 31 10:37:46 sergio kernel: thinkpad_acpi: undocked from hotplug port re...or
Oct 31 10:37:46 sergio kernel: ACPI: \_SB_.GDCK: undocking
Oct 31 10:37:47 sergio colord[1490]: device removed: xrandr-NEC Corporation...NB
Oct 31 10:37:50 sergio NetworkManager[1387]: <info> (em1): link disconnected...)
Oct 31 10:38:29 sergio kernel: iwlwifi 0000:03:00.0: RF_KILL bit toggled to...o.
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> WiFi now enabled by radi...h
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0): bringing up de....
Oct 31 10:38:29 sergio kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 31 10:38:29 sergio kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 31 10:38:29 sergio kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 31 10:38:29 sergio kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 31 10:38:29 sergio kernel: usb 1-1.4: new full-speed USB device number ...ci
Oct 31 10:38:29 sergio kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is n...dy
Oct 31 10:38:29 sergio dbus-daemon[1107]: dbus[1107]: [system] Activating vi...'
Oct 31 10:38:29 sergio dbus[1107]: [system] Activating via systemd: service...e'
Oct 31 10:38:29 sergio systemd[1]: Starting WPA Supplicant daemon...
-- Subject: Unit wpa_supplicant.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit wpa_supplicant.service has begun starting up.
Oct 31 10:38:29 sergio dbus-daemon[1107]: dbus[1107]: [system] Successfully ...'
Oct 31 10:38:29 sergio dbus[1107]: [system] Successfully activated service ...1'
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> wpa_supplicant started
Oct 31 10:38:29 sergio systemd[1]: Started WPA Supplicant daemon.
-- Subject: Unit wpa_supplicant.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit wpa_supplicant.service has finished starting up.
-- 
-- The start-up result is done.
Oct 31 10:38:29 sergio kernel: usb 1-1.4: New USB device found, idVendor=0a...e6
Oct 31 10:38:29 sergio kernel: usb 1-1.4: New USB device strings: Mfr=1, Pr...=3
Oct 31 10:38:29 sergio kernel: usb 1-1.4: Product: BCM20702A0
Oct 31 10:38:29 sergio kernel: usb 1-1.4: Manufacturer: Broadcom Corp
Oct 31 10:38:29 sergio kernel: usb 1-1.4: SerialNumber: 3C77E6EBA187
Oct 31 10:38:29 sergio mtp-probe[10003]: checking bus 1, device 4: "/sys/dev..."
Oct 31 10:38:29 sergio mtp-probe[10003]: bus: 1, device: 4 was not an MTP device
Oct 31 10:38:29 sergio kernel: Bluetooth: hci0: BCM: patch brcm/BCM20702A0-...nd
Oct 31 10:38:29 sergio kernel: usbcore: registered new interface driver btusb
Oct 31 10:38:29 sergio kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 31 10:38:29 sergio kernel: Bluetooth: RFCOMM socket layer initialized
Oct 31 10:38:29 sergio kernel: Bluetooth: RFCOMM ver 1.11
Oct 31 10:38:29 sergio bluetoothd[1484]: Endpoint registered: sender=:1.117 ...e
Oct 31 10:38:29 sergio bluetoothd[1484]: Endpoint registered: sender=:1.117 ...k
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0) supports 5 scan...s
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0): supplicant int...y
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0): device state c...]
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0): supplicant int...d
Oct 31 10:38:29 sergio NetworkManager[1387]: <info> (wlp3s0) supports 5 scan...s
Oct 31 10:38:30 sergio systemd[1]: Starting Bluetooth.
-- Subject: Unit bluetooth.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.target has begun starting up.
Oct 31 10:38:30 sergio systemd[1]: Reached target Bluetooth.
-- Subject: Unit bluetooth.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.target has finished starting up.
-- 
-- The start-up result is done.
Comment 9 Fedora End Of Life 2015-05-29 11:04:59 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 10 Fedora End Of Life 2015-06-29 19:08:43 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.