07-26-2014, 12:10 AM
gold_finger,
Thank you again, but still no luck--at least not yet. I read the post mentioned in Reply #4 of this thread, but neither suggestion worked for me.
Then I used the terminal command to shut the computer down:
Nothing showed up on the terminal at all. It went right into the concentric circles and hung. So, I tried again and this time, the entire screen went black and the following text appeared:
After 15 minutes of hanging, I used the power button to shut the computer off. Hopefully, there is something in the output I posted that will help figure this out. I remain clueless.
Thank you again, but still no luck--at least not yet. I read the post mentioned in Reply #4 of this thread, but neither suggestion worked for me.
Then I used the terminal command to shut the computer down:
Code:
sudo shutdown -h nowNothing showed up on the terminal at all. It went right into the concentric circles and hung. So, I tried again and this time, the entire screen went black and the following text appeared:
Code:
wait-for-state stop/waiting
* Stopping rsync daemon rsync [OK]
* speech-diapatcher disabled; edit /etc/default/speech-dispatcher
* VirtualBox Additions disabled, not in a Virtual Machine
* Asking all remaining processes to terminate… [OK]
* All processes ended within 1 seconds… [OK]
ModemManager [693] : <info> Caught signal, shutting down…
ModemManager [693] : <info> ModemManager is shut down
nm-dispatcher.action: Could not get the system bus. Make sure the message bus daemon is running! Message: Did not receive a reply. Possible causes: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
* Deactivating swap… [OK]
* Will now halt
[369.168266] reboot: Power downAfter 15 minutes of hanging, I used the power button to shut the computer off. Hopefully, there is something in the output I posted that will help figure this out. I remain clueless.