I installed Yoper just 2 days ago and I've noticed that if I select "Turn of the computer"(or something like that) when logging out of KDE it actually reboots rather than switch off lsmod tells me that the apm module is loaded, so I am not sure why this happens. I normally use Slackware and use an alias via sudo to perform this task without any problems. Is this normal Yoper behaviour? What do I need to edit to make it do what it says on the tin?

i odn't anything about Yoper.. but if that doesn't work... than just do a sudo halt...

or see if you can edit the menu for KDE and view/change the command that it issues??

It sounds like a KDE issue.

Try going into runlevel 3, and see if swapping to runlevel 6 (Shutdown), works. If it does, then it is definitely KDE. From there, you have 2 options. Attempt a re-install (Not always...fun =P), or you can attempt to find the error in the KDE source (Horrendously hard, I'd say =P), and recompile KDE.

Also, to enter runlevel 3 you will need to use the graphical Runlevel Editor tool if you don't want to use /sbin/init. Its fairly straightforward as well, so no worries. :-)

Cliekid

So, does this happen to others? I can try the suggested fixes, no probs there. I just struck me as being a bit odd and was wondering whether this is a "feature" of either Yoper or KDE 3.3 - the first time I have used either

I personally have not had this issue...

It seems more of a specific hardware thing interacting with KDE. Ya never know these days :-)

Hi,

I've never had anything like this before myself... I've had problems with the machine not turning off, but not this...

In adition to Cliekid's runlevel 6 suggestion, try doing a

as root from a console.

I'd also have a peek at the system logs to see if there's any clue there.

Cheers.

Um guys... runlevel 6 is reboot, 0 is halt. 'telinit 0'

Steve.

I was always sure 6 was shutdown - and 0 didn't exist.

1 is..boot
2 is non-graphical, single user
3 is multiuser non-graphical
4 is...4
5 is X / Multiuser
6 is shutdown

Thats what I always thought it was..?

Cliekid

Looking in /etc//init.d we find in the header:
#
# rc.halt This file is executed by init when it goes into runlevel
# 0 (halt) or runlevel 6 (reboot). It kills all processes,
# unmounts file systems and then either halts or reboots.
#

-------

We have a similar thread going... I believe it may be the same problem.
http://www.linuxquestions.org/questi...hreadid=260562
if you'd care to have a looky-lou.

Suggest you look in /home/{user}/.xsession-errors for some clues as to what is not right at boot.
Also; /var/log/messages and /var/log/dmesg.

Please give a shout back as to what you find/don't-find.

Even with the few problems (BUGs?) with the various distros of Linux with which I've toyed, it is BY FAR easier to deal with than the days and months and YEARS I've WASTED trying to get a decent install of Brand-X Windows. At least linux is stable and will half-assed run even when severely wounded!

I'll get off my soapbox now!

Hey guy, I think the correct one are
0 --> halt
1 --> maintenance mode (single user)
2 --> multiuser without networking (text)
3 --> multiuser with networking (text)
4 --> forget it!
5 --> multiuser, networking with X
6 --> reboot

You can find it in your /etc/inittab.