I suddenly cannot use the shutdown button in the kickoff menu (it simply does nothing but close the kickoff menu) and ctrl+alt+del also does nothing! The rest of the OS works fine. The only way I was able to shutdown was by holding the power button on the computer. I have since restarted and again cannot shutdown! (Logout button also does not work)
How do I figure out what’s happened?
I have not updated any software packages recently (I did a few days ago but had successfully shutdown since then).
I’m on OpenSUSE 12.1 (x86_64), Linux 3.1.10-1.19-desktop x86_64, KDE: 4.8.5 (4.8.5) “release 522”.
More info:
I restarted the computer with systemV (by pressing F5 at grub) and it started up and ran slowly but I was able to shut down! What does this mean? Why would systemd be working all this time and suddenly not work? what’s the difference in using systemV vs systemd? What should I do?
subsequently, and after the 12.2 is fully patched/updated either of
those above can then be used to upgrade from 12.2 to 12.3
additionally, there is one supported path to upgrade directly from
12.1 to 12.3, it is explained here: http://tinyurl.com/7l4m2td
however, my personal preference is to do none of those “upgrades” and
instead save/copy all data to an off-machine location and do a
complete format, fresh install, system rebuild and data rejoin.
why? because i find the fresh install is less likely to have
stability problems AND considering the time it takes to run down all
the little problems an ‘upgrade’ usually includes, it is faster to do
it my way. ymmv
I was afraid of that. ok, I will but can you still explain to me why this might happen and why systemV would work but systemd would not (especially when systemd had been working)?
On 05/17/2013 01:46 PM, 6tr6tr wrote:
> can you still explain to me why
> this might happen and why systemV would work but systemd would not
> (especially when systemd had been working)?
no i can’t explain it except to say that some updates do not take
effect completely until after a boot…so, if you updated (as you
said) “few days ago” and then (maybe) hibernated or put it to sleep a
couple times (maybe over night) or maybe you let it run overnight to
download something…and, then finally fully shut it down (say) day
before last…and then use it all day long and THEN try to shut it
down and does not, well it didn’t shut down after the first boot
after the update–and,the update is the cause for the problem.
i do not know, maybe ‘they’ pushed out all the ready updates they
could for 12.1 on the LAST day updates flowed…and, maybe one of
those was a kernel update, and it broke the shutdown…that happens
rather often…
i make it a habit to, immediately after an update, run
zypper ps
to see if anything, and what, is running from memory only…meaning
the executable/library on the disk is different from that running,
because it was replaced by an update (read more in man zypper)
and, if so i go ahead and reboot…so, if it breaks i KNOW that it
was update caused, and i can get right on to fixing it, without
having to wonder what caused the problem…
On 2013-05-17 10:20, dd wrote:
>> I’m on OpenSUSE 12.1
>
> openSUSE 12.1 sailed past its end of life two days ago (cite:
> http://en.opensuse.org/Lifetime)…
The official discontinuation email has not been posted yet
(opensuse-announce at opensuse.org). First they have to post a “Advance
discontinuation notice for openSUSE 12.1” email and about a month later
a “openSUSE 12.1 has reached end of SUSE support” email. I’m going to
ask in the project mail list. (Done).
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-05-17 13:46, 6tr6tr wrote:
> I was afraid of that. ok, I will but can you still explain to me why
> this might happen and why systemV would work but systemd would not
> (especially when systemd had been working)?
The systemd version in 12.1 is flaky, many features unfinished. I would
not be surprised that some update broke something, because the devs
assume they have the features of a more recent version available.
In fact, for a long time since I can not power off the machine by the
command posted on the release notes, it stops near the end - using
systemv. At the end, I have to push the button. Several people have
reported this problem.
I can hibernate fine though - which at some time has to power off the
machine, and it does.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
This is not directly related to systemv vs. systemd AFAIK.
It’s a hang in kded, some kind of race condition I guess. So maybe because of the different startup when using systemv this condition is not triggered by luck?
I experienced it a few times in earlier versions. Seemed to happen mostly when my computer was under heavy load during KDE start (because updatedb kicked in f.e.).
On 2013-05-18 15:16, 6tr6tr wrote:
>
> robin_listas;2557593 Wrote:
>> On 2013-05-17 15:06, 6tr6tr wrote:
>>
>>> how would I diagnose this?
>>
>> I would log out, then click power-off.
>> If this also fails, then next time log-out, then go to VT1 and use
>> command line to power off.
> how does that help me diagnose it?
Obviously, if that way you can power-off, the failure is elsewhere. Of
course it helps.
From the release notes:
+++························
systemd: System Shutdown
To halt and poweroff the system when using systemd, issue halt -p or
shutdown -h now on the command-line or use the shutdown button provided
by your desktop environment.
Note: A plain halt will not shutdown the system properly.
························+±
For your consolation, my machine does not power off, it fails. It stops
at the last moment, and then I have to push the button on the metal
case. It works on hibernation, though.
And no, I’m not going to investigate it - this is 12.1 and EOL.
> wouldn’t looking at some log files
> help? which log files should I be looking at? what things should I look
> for?
Session log, perhaps.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Well, his problem is not the shutdown itself.
The problem is that KDE’s Logout/Shoutdown dialog doesn’t appear. And that’s likely caused by a hang in kded4.
In your case you should change the shutdown command in KDE’s Configure Desktop->Login Screen->Shutdown I guess.
It’s “/sbin/shutdown -h -P now” on my system (12.3 though) and that works fine.
To the OP:
Well, I would advise you to upgrade KDE to 4.10, I haven’t seen this happening there. But that’s only available for openSUSE 12.2, 12.3 and Factory.
So I think you should at least upgrade to 12.2, shouldn’t be problematic.
On the other hand, 12.3 has KDE 4.10 included, so you wouldn’t have to add an additional repo…
You could of course try to attach gdb to kded4 and examine the stack backtrace to find out where it hangs if you have the knowledge.
In the bug report I linked to pulseaudio was suspected, but this can’t have been the issue for me because I always had pulseaudio disabled. But you could try to disable pulseaudio and see if that helps. (YaST->Hardware->Sound, click on “Other” in the bottom-right corner and select “PulseAudio Configuration”
You could also enable debug output for kded4 with “kdebugdialog” and then look at the file ~/.xsession-errors.
But somehow I doubt that you will find anything helpful…:sarcastic:
On 2013-05-18 22:56, wolfi323 wrote:
>
> robin_listas;2557880 Wrote:
>> For your consolation, my machine does not power off, it fails. It stops
>> at the last moment, and then I have to push the button on the metal
>> case. It works on hibernation, though.
>>
>> And no, I’m not going to investigate it - this is 12.1 and EOL.
> Well, his problem is not the shutdown itself.
> The problem is that KDE’s Logout/Shoutdown dialog doesn’t appear. And
> that’s likely caused by a hang in kded4.
Could be.
> In your case you should change the shutdown command in KDE’s Configure
> Desktop->Login Screen->Shutdown I guess.
No, I use XFCE (with kdm display manager). It doesn’t seem to be
configurable. Or it is kdm behind which I have to configure instead.
> It’s “/sbin/shutdown -h -P now” on my system (12.3 though) and that
> works fine.
I wrote that into a postit, I’ll try next time
I never poweroff, I normally hibernate, so it is an almost non-issue for
me. This is 12.1, remember, which is days off EOL. I will upgrade soon,
but I need free time and learn some things first.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
