12.1 Computer does not power down upon shutdown

Hi,
When I boot my Opensuse 12.1 in normal mode, and choose “shutdown”, the system will show a few splash screen messages until “[Seconds] The system is halted”, but the computer will not power down. I have tried to leave the system on for about fifteen minutes, nothing happens. I have to power down using the power button.

If I choose to boot in “failsafe” mode, and “shutdown”, the system will display a lot more messages, and then power down.

If I choose “restart”, the system will correctly restart in both boot selections.

I boot from an SSD disk, and the install done is 12.1 root on SSD drive using the existing home partition on another harddisk.
Any help will be appreciated, this is a little nuisance.
Thanks
StG

On 12/01/2011 04:16 PM, Goettschwan wrote:
>
> I have to power down using the power button.

it is almost never a good thing to shutdown with the power button…

this problem is reported here
https://bugzilla.novell.com/show_bug.cgi?id=731551#c2

which explains and offers the work around…

i’d expect it to be fixed quickly (weeks?)

until then instead of clicking on shutdown/or using the power button,
just open a terminal, and enter these


su -
shutdown -h -P now

don’t miss the dash after the su, and give root password when asked…


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

Hi,
thanks for your link.
If I use “shutdown -h -P now” from console the system powers down correctly.
Incidentally, if I use “shutdown now”, my problem as stated above appears.

I have read your link and changed the kdmrc file to

[Shutdown]

The command (subject to word splitting) to run to halt the system.

Default is “/sbin/shutdown -h -P now”

HaltCmd=/sbin/shutdown -h -P now

The command (subject to word splitting) to run to reboot the system.

Default is “/sbin/shutdown -r now”

#RebootCmd=

but now something really strange happens, the system goes on to display the splash screen, and some text about eth0 could not setup the service before now (red failed) appears, and things fall apart: I come to a text only linux prompt asking me to login. This is from /var/log/messages:
(23:14 me going root and editing kdmrc, logging out root and hitting shutdown in KDE)
(26:16 me arriving at the text only prompt to login, going root and typing the shutdown command manually)

Dec 1 19:23:14 linux-s7ok systemd-logind[867]: New session c3 of user root.
Dec 1 19:24:12 linux-s7ok systemd-logind[867]: Removed session c3.
Dec 1 19:24:16 linux-s7ok polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.40, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
Dec 1 19:24:16 linux-s7ok dbus[1110]: [system] Activating via systemd: service name=‘org.freedesktop.NetworkManager’ unit=‘dbus-org.freedesktop.NetworkManager.service’
Dec 1 19:24:16 linux-s7ok dbus-daemon[1110]: dbus[1110]: [system] Activating via systemd: service name=‘org.freedesktop.NetworkManager’ unit=‘dbus-org.freedesktop.NetworkManager.service’
Dec 1 19:24:16 linux-s7ok dbus[1110]: [system] Activation via systemd failed for unit ‘dbus-org.freedesktop.NetworkManager.service’: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and ‘systemctl status dbus-or
g.freedesktop.NetworkManager.service’ for details.
Dec 1 19:24:16 linux-s7ok dbus-daemon[1110]: dbus[1110]: [system] Activation via systemd failed for unit ‘dbus-org.freedesktop.NetworkManager.service’: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and ‘syste
mctl status dbus-org.freedesktop.NetworkManager.service’ for details.
Dec 1 19:24:16 linux-s7ok systemd-logind[867]: Removed session c1.
Dec 1 19:24:17 linux-s7ok kdm[5109]: Failed to execute shutdown command “”
Dec 1 19:25:49 linux-s7ok login[1423]: gkr-pam: error looking up user information
Dec 1 19:25:52 linux-s7ok login[1423]: FAILED LOGIN SESSION FROM /dev/tty1 FOR UNKNOWN, User not known to the underlying authentication module
Dec 1 19:25:55 linux-s7ok systemd[1]: getty@tty1.service holdoff time over, scheduling restart.
Dec 1 19:26:05 linux-s7ok login[5115]: gkr-pam: error looking up user information
Dec 1 19:26:08 linux-s7ok login[5115]: FAILED LOGIN SESSION FROM /dev/tty1 FOR UNKNOWN, User not known to the underlying authentication module
Dec 1 19:26:12 linux-s7ok systemd[1]: getty@tty1.service holdoff time over, scheduling restart.
Dec 1 19:26:16 linux-s7ok systemd-logind[867]: New session 1 of user stefan.
Dec 1 19:26:27 linux-s7ok su: (to root) stefan on /dev/tty1
Dec 1 19:26:32 linux-s7ok avahi-daemon[1018]: Got SIGTERM, quitting.

Did I write the option correctly in kdmrc? Does it need quotes?
Is this maybe connected to your suggestion in another thread to boot using systemV instead of systemD?
Thanks
Stefan

On 12/01/2011 08:06 PM, Goettschwan wrote:

> If I use “shutdown -h -P now” from console the system powers down
> correctly.

GOOD!!

> Incidentally, if I use “shutdown now”, my problem as stated above
> appears.

Question: Do you know why?

Answer: Because “shutdown -h -P now” and “shutdown now” are different. i
gave you the one i was reasonably sure would work…and not the one i
was reasonably sure would not…

>
> I have read your link and changed the kdmrc file to
>> [Shutdown]
>> # The command (subject to word splitting) to run to halt the system.
>> # Default is “/sbin/shutdown -h -P now”
>> HaltCmd=/sbin/shutdown -h -P now
>> # The command (subject to word splitting) to run to reboot the system.
>> # Default is “/sbin/shutdown -r now”
>> #RebootCmd=
>
> but now something really strange happens

no kidding??

<big snip away of a long excerpt /var/log/messages which i barely
glanced at…sorry, someone else may look at it and give you feed back,
but not me, not today (grouchy)>

> Did I write the option correctly in kdmrc?

so, i gave you a work around that works…and, you read a work around
written by “Andrey gorin” which does not work for you, yet–and now you
want me to tell you why, or help you with it… ???

> Does it need quotes?

sorry, i do not know (remember, it was not my first choice of how to
deal with this problem)…but if i were to try i’d try one of these:


HaltCmd='/sbin/shutdown -h -P now'
*or*
HaltCmd="/sbin/shutdown -h -P now"

but i have zero confidence that either will actually work…

and if it does not i would suggest you track down the writer and ask him.

> Is this maybe connected to your suggestion in another thread to boot
> using systemV instead of systemD?

yes, i think so (and really i do NOT know…i’ve been around and used
systemV since the late 90’s and only read (a little) about systemD for
about a week)

while i do not know for sure what is going on on your 12.1 i do believe
it will be fixed eventually…i don’t know how long that will take…

i think booting systemV will ‘solve’ this shutdown problem BUT systemD
will replace systemV eventually…which means that eventually “they”
will have to FIX systemD including this shutdown problem and all the
other problems you are having which may be related to the V vs D thing…

so, it is up to you to decide if you want to shutdown the way i gave you
and be patient, or figure out how to get the “Andrey gorin” way to work,
or try systemD, or even revert back to systemD, or or or

as for me: so far i have decided to continue running my old, reliable,
stable, predictable 11.4! it is supported another 289 days i expect 12.1
and systemD will be fine and dandy long before then…and, i will jump
to 12.1 (or .2) within 280 days…

> Thanks
> Stefan

welcome…see, it all depends on what you want: my 11.4 is far superior
to the desktop in use by maybe 94 percent of earthlings…so, i’m
happy!! (but, i do understand that some folks are willing to give up
some fiddling time and stability to get to be better than 98%… :wink:

{sorry for my grouchy day…and i DO recognize it is wonderful to have
folks who want to be on the better side of 95%, because they will find
the bugs that i have the patience to wait for their fix!}


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

Thanks for your words. I am using Opensuse since back somewhere in the 10 versions, with KDE 3.5 back then. No install I ever did of it was hassle free, and while I have learned a lot, I never had any time nor desire to learn to tweak the innards of this. I am still not used to installing a superior version number and hunt down lots of problems while doing it, so I should probably learn to wait, or calm down my expectations. Or install something else.
My 11.4 was working quite okay, given the amount of bothering bugs still out there, so I figured going 12.1 would fix some of them. Wrong choice. Guess that’s life, but I really do not need the acid mockery on top of it.

> I really do not need the acid mockery

???

if my reply was unhelpful, i missed my goal.


DD
openSUSE®, the “German Engineered Automobiles” of operating systems!

To be fair and on topic: this issue is described in the release notes, as shown during install. The difference is in booting through systemd (the new default) and sysvinit.

@Goettschwan

my two pennies worth,

i first noticed the shutdown problem in openSUSE11.3. It again was seen in
openSUSE11.4 and openSUSE12.1.

whe following worked for me after each update,

in - System Settings, -- Login Screen, -- Shutdown,
the parameter Halt: was changed from '/sbin/halt' to '/sbin/halt -hip'

when openSUSE12.1 was installed, I’m sure something was changed so that
sysvinit was enabled but the info from Yast is that both sysvinit and systemd
are installed

i expect the problem on this OS is not the same as on yours but its a simple
change which can be tried and easily reversed

My 12.1 KDE system powers off as expected from the menu/leave/shutdown button. From the bug report it seems a problem for upgraders not for new installs.

RubyTuesday wrote:

>
> My 12.1 KDE system powers off as expected from the
menu/leave/shutdown
> button. From the bug report it seems a problem for
upgraders not for
> new installs.
>
>
Disagree its problem for up graders. I up grade from
11.4 to 12.1 MS1 and then thru to the final release.
Had shutdown problem in 11.4 but have not since 12.1
MS1.

Appears to be system and maybe BIOS related. I still
have a version of 11.4 (up to date on same system and
it has the shutdown problems. Tried all sugestions in
bug reports, on list etc. Difference in my case is 11.4
and 12.1 are on seperate disks and partitions. 12.1 was
up grade of my test environment.

Wish I could contribute more.

Russ
openSUSE 12.1(Linux 3.1.0-1.2-desktop x86_64)|KDE
Platform Version 4.7.4 (4.7.4) Release “11”|Intel
core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-
Linux-x86_64-285.05.09)

I had the same shutdown issue after upgrading from 11.4 to 12.1. Using the command:
/sbin/shutdown -h -P now within Configure Desktop >> Login Screen >> Shutdown for the parameter Halt: fixed my problem