[SOLVED] Cumputer will not shut down. Mint17

[psioniks]

Hello everyone! I am new to linux mint. I just installed Linux Mint 17 in a dual boot with widnows 7. Eveything looks fine exept when I shut down the computer.
I get this message:
ModemManager [746]: <warn> COuld not acquire the 'org.freedesktop.ModemManager1' service name
ModemManager [746] <info> ModemManager is shut down
.....
Sometimes I get this:
.....
ModemManager[704]: <info> Cought signal, shutting down...

ModemManager[704]: <warn> Could not acquire the 'org.freedesktop.ModemManager1'
service name
......

But the cumputer is stuck in this screeen and doesn't shut down.


Help Please!

[niowluka]

Same problem here, although I do not get any warnings. System hangs on 'System Halted' message (or something similar).

Frankly, I do not think modemamanager is at fault here, but if you are not using it, it will not hurt to remove it. Mine was flooding logs with some dbus errors, not dissimilar to the messages you posted.

Code: Select all

sudo apt-get purge modemmanager

I used to have that problem on Slackware and the fix was to force unload my tv card drivers at shutdown. Will dig deeper this weekend...

[WinterTroubles]

Just for reference, I get the same messages during shutdown as the OP and something very similar in MINT 16, both of which shutdown correctly. I believe those messages are simply the machine shutting down proccesses and unconnected to your shutdown hanging. Sorry I can't be more help.

[psioniks]

Thanks a lot for the quick answer.
I am new to Linux and I don´t know if I need ModemManager. Is it needed for internet connections? I´m using a usb wireless adapter.

[niowluka]

Thanks a lot for the quick answer.
I am new to Linux and I don´t know if I need ModemManager. Is it needed for internet connections? I´m using a usb wireless adapter.

Then you don't need it.

[Mute Ant]

I often get this shutting down, with no noticable pattern. Windows used to do it too, like the kernel has run out of things to do because the Power-Off command was ignored. Tell Linux to switch off directly from the keyboard...

• Ctrl-Alt-SysRq-S
  Ctrl-Alt-SysRq-U
  Ctrl-Alt-SysRq-O

[psioniks]

Thanks a lot for the quick answer.
I am new to Linux and I don´t know if I need ModemManager. Is it needed for internet connections? I´m using a usb wireless adapter.

Then you don't need it.

I uninstalled the ModemManager, but the problem persists.
Now I don't get anymore the warning about modemmanager.
The strange thing is that the green led light is off, indicating that the computer is off, but I can hear the fan working and the screen is on.

[Petiepotamus]

I also had this problem after installing Mint 17 32 bit Mate on Compaq Laptop which originally had Windows XP installed and replaced with Mint.
The broadcom wireless network card also was not showing up.

I got wireless working, and also fixed the shutdown problem with the following.

sudo modprobe -r BCMA
sudo modprobe -r B43

Then reference the following article by Geekster at LinuxG.net

http://linuxg.net/how-to-fix-broadcom-b ... inux-mint/

This got wireless working, and also fixed the shutdown problem.

I hope this helps you.
This site has many fixes for non functioning hardware.

[psioniks]

Hey guys thanks to all of you for your support.
I finally found the solution. After trying different linux distros (mint, xubuntu, fedora, pclinuxos etc) I always was faced with the same problem.
Finally I changed a setting in my BIOS: In power management I changed from Bios to ACPI.
And the magic happened.
Now the computer shuts down normally!

P.S. - I installed the 64 bit version of Mint! (with the 32 bit version, my usb mouse would stay on after computer shutdown).

[Darthperil]

I'm having this issue (I'm installing from DVD to an older emachine that had windows xp on it) after it finished I selected restart and it gave the "could not acquire the org.freedesktop.modemmanager service name" message. I performed the Ctrl-Alt-SysRq-S and it worked but the Ctrl-Alt-SysRq-U and Ctrl-Alt-SysRq-O stated "This sysrq operation is disabled" and it is stuck, won't reboot!! Can I perform a hard shutdown??? Any information will be greatly appreciated!!

[Reorx]

I'm having this issue (I'm installing from DVD to an older emachine that had windows xp on it) after it finished I selected restart and it gave the "could not acquire the org.freedesktop.modemmanager service name" message. I performed the Ctrl-Alt-SysRq-S and it worked but the Ctrl-Alt-SysRq-U and Ctrl-Alt-SysRq-O stated "This sysrq operation is disabled" and it is stuck, won't reboot!! Can I perform a hard shutdown??? Any information will be greatly appreciated!!

I have had this experience and it always makes me uneasy... it might not be necessary but I recommend shutdown any way you like and then just do a re-install. At the end of the installation, select "Continue testing" and get back to the desktop. Close all applications and then shutdown. When you power back up, tap whichever F key gets you to a boot menu and remove the DVD and then select to boot from the HD... and then Enjoy the Mint!!!

[Darthperil]

I got back into mint using compatibility mode, entered Driver Manager which told me the broadcom emachines 802.11g built-in wireless was not working. There are 4 choices: bcmwl-kernel-source (recommended) which I applied but didn't work, it gave the same error as before "<warn> COuld not acquire the 'org.freedesktop.ModemManager1' service name". The next one is; firmware-b43legacy-installer, which gave the same error. Then I applied the "firmware-b43-installer" it didn't give the error but when I rebooted, mint came up, asked for my login and password then eventually went to a black screen with a working mouse cursor!! I also tried "sudo modprobe -r bcm4306" (bcm4306 being the model of wireless NIC) and I got 'FATAL: module bcm4306 not found". I did turn off wireless in BIOS, but I still got the modemmanager error! And, to be thorough, I used the function key on the laptop to disable wifi and that didn't work!! I do have it connected to my router with a patch cable!! My laptop is a eMachine M5312. Again, any information will be greatly appreciated!!

[Reorx]

I presume you did a hard shutdown... did you do a re-install??? If not, I would suggest doing so... while it is possible and perhaps likely that you didn't damage anything doing a hard shutdown, it is almost impossible to be sure - and if some aberrant bytes were written or left remaining in some file, from my POV, it is difficult to assess the effects of that on a particular system... On a freshly installed system, there is no user data of any importance and a re-install is quick and easy - cheap insurance!

Having said that, if you DID do a re-install, you should consider starting a new thread for this problem.

[Darthperil]

I did do a re-install, that is the one thing I didn't mention!! I will try another re-install and create a new post for my issue!! Thank you very much for your help, it is greatly appreciated!! See you in the next adventure!!