Yoper 2.1

Upon clicking the "Logout" symbol on the taskbar, system acts like it's going to shut down. When it gets to the command line it simply stops.

Typing "shutdown -h now" merely hangs the system.

I've tried all sorts of variants of this with similar results.

Anyone with an idea?

tia

Hey,

I just replied to a *similar* problem.

I would suggest you use the built-in Runlevel editor or use /sbin/init via shell to swap to Runlevel 3 (Graphical MultiUser mode). From there, type in /sbin/init 6, or init 6, whatever it is (Too many different distros ;-) ), if it shuts down properly then it may be a symlink issue with the shut down command. That command should issue a halt signal (Init 6), to check this, type:

ls -l shutdown

It should return some stuff. Check if it says something like "/sbin/init 6". It may have some extra parameters and such, but if it has that then I have no idea what your problem is :-)

I'll do some more research into it on my system and see what I can do.

Cliekid

When exactly does it hang? if you get to the "power down" message then it is just a power managment / BIOS issue...
ie. what is the last console message after issuing "shutdown -h now" or "telinit 0"?

Steve.

no I get the same - its something we should look into
i've seen distros powering my machine down

it doesn't bother me much because pretty everything else is unmounted and defunct and I can reach for the power-off button.

i think its when i reboot from GDM or KDM that it gets funny
from the console
reboot -n
shutdown -h now
seems ok

Hi Steve,

I have "Hot Swap" HDDs, so can change out the OS dirve in about 2 minutes; the machine reboot/shutdown works flawlessly on other distros; Fedora Core2, Linspire 4.5.499, OpenBSD 3.4, Knoppix 3.6, Mepis 2003.10.02 and Libranet 2.8.1. I think there are a couple of others but, you get the picture.

As a second thought; I have issues with/at bootup; /home/[user]/.xsession-errors contains more errors than I can shake a stick at.
Eg.: (gnumeric:2536): WARNING **: Wrong permissions for /tmp/orbit-[user]

Can anyone tell me WHAT the permissions are supposed to be for /tmp/orbit-[user]?

Maybe if I start "fixin" stuff the logs are screaming about, the other problems will go away.

I believe Temp filesystem needs to be Root for most apps. Wine and other things hit problems if the folder owner isn't Root and only Root can write to it - but thats just for that.

If its X maybe you need to allow your user access to tmp?

Never had the problem before so I'm just "guessing" :-)

Cliekid

Hello Cliekid,

I understand what you are saying. I just looked and /tmp is root/root 41777, which means there should not be ANY problems with anyone reading/writing/executing that directory. It is the specific dir/file(s) /tmp/orbit-[user]. Additionally, there is a /tmp/root dir presumably for "root." Interestingly, precipitating the squawk is the creation at Gnumeric startup of "/tmp/orbit-[user] [user]/users 40700."

The question seems to be "who is writing using bad(?) permissions? "

Seems I've heard of such on the regular yoper website.

Well...

First of all - what kind of hardware do you have?

If its an X issue, it may just be a random error that doesn't *really* do with /tmp/orbit-<bla> =P

Several factors can play a role:

Is your Yoper install "ok"?
Is your graphics hardware able to run X on KDE 3.3?
Is your computer not mentally retarded? (Ok..maybe thats not a factor =P)

So you have to look at all aspects of it. If you've used Yoper before and it worked - re-install. I have reinstalled Yoper so many times - mainly because its so darn easy - but also because a file may be "bad" or there was a misconfiguration early on, that may not be entirely fixable.

If worse comes to worse, just reinstall. It takes what, 20 minutes for you to be booted into Yoper? =P

If you don't have 20 minutes in your day...then I fear the worst for all of mankind. (Ok, not really. Had to be dramatic. =P)

Cliekid

It's good, not really a factor in this instance.

X is NOT the problem.

Yes, I'll give it a 60%; about like most other initial linux installs..

Only after I did a manual setup of video.

May be... loose nut behind the wheel?


I believe it will be easier to fix whatever is wrong.

NOPE! It's not the 20 minutes for the initial install... it's the 2 additional weeks of tweaking the install and installing apps.

I'm going to reboot in lindows and see what the "orbit" permissions are set for; takes about 5 minutes from "up-to-up." (Hot-Swap HDDs)

If "shutdown -h now" hangs, then it has nothing to do with x, orbit or any other such thing. AFAIK it can only be:

a: An init script problem, try "halt -f" (WARNING: system should die IMMEDIATLEY, sync disks first!)
If this works then you need to investigate your init scripts to see which script in runlevel 0 is causing the problem...

b: Lack of (correct) power management support in the kernel, or buggy BIOS (most likley the former). If the above command does not halt the system try booting with "acpi=off" on the kernel command line, then do a "modprobe apm"... If you have an ASUS mainboard you could try "modprobe asus_acpi" if it is a Toshiba try "modprobe toshiba_acpi"

If all else fails, recompile the kernel with various apm and acpi options, it's not overly hard :-)


Hope this helps.

Steve.

Linux is not Winblows (duh), short of trashing / there is NO problem that cannot be fixed without a re-install. If you don't believe me install Gentoo. 2 days to download (on my 33.6) + 2days to compile (on my p4 1.5) + 3 weeks of tweaking to get it just right: you WILL find a way to avoid a re-install :-)

Seriously though, for yoper a reinstall may be quicker, but you learn nothing from it. People seem to look at a reinstall as the first / only option whenever something goes wrong. I suspect this comes from using Winblows 9X ;-)


Steve.

again I noticed if I reboot on a console as root - all is fine
but if I go via any X app - it hangs.
dunno what version of Yoper I have though - maybe 2.1

Problem is that a reinstall leaves me right where I'm at! Plus a couple of weeks worth of tweaking and apps install! I suspect the problem is in the install script. These problems do not manifest themselves on half a dozen other linux distros. I'm afraid I've muddied up the water a bit. The Orbit problem is a separate and distinctly different problem from the shutdown. Incidentally, I mis-spoke; when she shuts down I'm dropped to the cli login screen. Logging in as root and then "shutdown -h now", reboot, halt all hang the system. I don't like to power down from the login screen as there are drives mounted!

Linspire is coming out with Linspire 5.0 shortly; and IF they have incorporated Reiser4 I will definitely have to go back to Linspire as my main squeeze. I will continue to play with Yoper however.

Hi henryg,

Yep! Me too! On other distros. I believe this is the first time I've observed this condition on any linux. M$WinDO$, yes. I converted back @ RH5.1 and have played with maybe a dozen or more distros/versions and perhaps installs that exceed 100, just to give an indication of my familiarity. I consider myself a newbie.

Actually, I have this problem for a time. It was randomly freezed after 'shutdown' launched, especially with command line (with KDE shutdown, it was shutdown flawlessly). I've observed that it freezed mostly after sending TERM signal and shutting down the PCMCIA. My laptop freezed 1 out of 5 times after the shutdown command is launched and I don't know why.

By the way, about the permission problem with Orbit-[user] and other gnome apps, just remove the problem ones from your /tmp.