Description of problem: I am using Fedora 18 x86_64, kernel 3.8.9-200.fc18. My computer is a Dell Latitude e6430 laptop. It is installed on a Dell Port Replicator. When my laptop is on its Dell Port Replicator, Fedora has this very weird behavior: if I turn off the computer (with the shutdown command or the turn off button of the Fedora menu), it does turns off (all lights on the computer turn off), BUT it _spontaneously_ starts again after a few seconds. The problem does not appear when the laptop is not on a Dell Port Replicator. Similarly, as I have a dual boot with Windows 7, I can assure that this does not happen when I shut down the computer from Windows. I have been having this problem since I installed Fedora 18 beta on this laptop, and no update managed to solve this problem. My contigency plan is to turn off from Fedora, wait until grub appears, and turn off the computer by long-pressing the button. How reproducible: Probably requires a Dell Port Replicator. Steps to Reproduce: 1. Put the laptop on a Dell Port Replicator 2. Turn off the computer from Fedora 3. Wait until the computer is off 4. Wait a few seconds Actual results: The computer turns on once again. Expected results: The computer should stay off.
Are you still seeing this with the 3.9.8 or newer kernels?
I am actually far from my office because of work, so I can't test right now with the Dell Port Replicator with the very last system update. Nonetheless, I keep my system up to date on a daily basis, and the problem was still present last week. So I'm almost sure that the answer to this question is yes.
I confirm that the problem is still there. However, I am running the 3.9.6-200.fc18.x86_64 kernel, since I am still using Fedora 18. Thus I cannot answer your question regarding newer kernels.
Fedora 18 has been updated to 3.9.9-201.fc18.x86_64. I am now running this kernel, and the problem is still there.
After a fedup to Fedora 19, I now have the kernel 3.10.10-200.fc19.x86_64, and the problem is still present.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
I still have this bug with Fedora 20 freshly installed.
I've done some experiments, and I think I am very close to the cause of the problem: the problem disappears when WakeOnLan is disabled in the BIOS of the computer. Yet, if WOL is enabled, the problem remains even with the network cable unplugged. I am guessing that the problem is located in the use of the network card of the Dell Port Replicator by Fedora (or more likely the kernel itself), which goes wrong during shutdown ONLY WHEN the WOL is enabled in the BIOS. Note that I am using the last version of the BIOS for this laptop (A13, released on 10/17/2013). Thus the problem is solved for my personnal case, as I don't need WOL. But the bug remains.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.