On Mar 18, 2014, at 6:19 PM, pgaltieri . <pgaltieri@xxxxxxxxx> wrote: > > When I looked at the grub.cfg the enforcing=0 was there. In you previous email this URL contains a log with a command line that doesn't include enforcing=0. https://www.amazon.com/clouddrive/share?s=4LDATpk0T3IoK1jb-pKshY > > rpm -q selinux-policy > > selinux-policy-3.12.1-74.18.fc19.noarch selinux-policy-3.12.1-74.19.fc19 is stable as of four days ago. There's a newer kernel stable also. > > > I ran shutdown from the Mate login panel and again the system did not powerdown. > > Here's the shutdown log from doing a shutdown from mate. > > https://www.amazon.com/clouddrive/share?s=Tfn2AX3zTZAn01Ljxcsc0c OK keep these additions to boot params, with one addition: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 systemd.unit=rescue.target echo 1 >/proc/sys/kernel/sysrq echo s >/proc/sysrq-trigger echo u >/proc/sysrq-trigger echo o >/proc/sysrq-trigger Does that power down the laptop? If not, it's probably a kernel bug. I'd go back to an old kernel that you know worked and test that. And then file a bug against the kernel noting the last kernel it works with and the first one it doesn't. Note the computer make/model, and firmware version, and the fact it's UEFI. If it does power it off, then test the same boot parameter but use the poweroff command instead of the sysrq trigger. The laptop firmware is for sure up to date? Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
