SabayonThis forum is for the discussion of Sabayon Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kinda premature to guess the machine is frozen given the recent HAL code and newer versions of X, perhaps among other things.
Magic SysRq will work if you have it configured, but before doing that, if the OP just wants to kill X, but doesn't want to reboot the whole machine, why not try switching to a different VT with CTRL-ALT-Fn and logging in, then either switch to a non-X runlevel, or give a `killall X` or `gdm stop` sort of command?
Kinda premature to guess the machine is frozen given the recent HAL code and newer versions of X, perhaps among other things.
Magic SysRq will work if you have it configured, but before doing that, if the OP just wants to kill X, but doesn't want to reboot the whole machine, why not try switching to a different VT with CTRL-ALT-Fn and logging in, then either switch to a non-X runlevel, or give a `killall X` or `gdm stop` sort of command?
Sasha
killall X works but the problem is i have to be root to use it... my video gets pooped every so often and i can't see poop all so what do i need to do to let a normal user use killall X without having type a password, that way ill just assign the keys to it.
Last edited by XavierP; 01-21-2010 at 09:55 AM.
Reason: sanitised for your safety and convenience
If you're using hal, it's (I think...) best to configure it through the .fdi files. They are in /usr/share/hal/fdi/policy/10osvendor/*.fdi from memory.
So they don't get overwritten on update, copy to etc:
If you're using hal, it's (I think...) best to configure it through the .fdi files. They are in /usr/share/hal/fdi/policy/10osvendor/*.fdi from memory.
So they don't get overwritten on update, copy to etc:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.