System crashes when leaving init 4
My custom Slackware install crashes whenever I leave init 4 and I can't quite figure out what is causing it. I was able to ignore the problem for awhile, but now I am working on a project that requires me to keep entering and exiting xwindows, and having to reboot (uncleanly) is getting increasingly annoying.
I am pretty sure the problem is with the init process and not X11 because it doesn't happen when I initiate startx from init 3. If however, I go strait into init 4, my screen blanks whenever I try to exit the xsession and it will not accept any further input. It will even stop in the middle of an 'init 6' run from an xterm. Initially I was using XDM and fluxbox, and I would only experience this when I had to exit X uncleanly (VT switching or a call to init 3 from xterm). Now I have KDM with fluxbox, and I get the results no matter how I try to exit. This is another reason why I belive it is being cause by an incorrect desktop manager setup. Unfortunately, I am still haven't completely figured out how all this xsession stuff works so I'm not sure what to post. Here is some general info about my install. xwindows packages (the K's mean it is not a standard Slackware pkg): Code:
dejavu-ttf-2.10-noarch-1.tgz x11-6.9.0-i486-11.tgz /opt/kde/share/config/kdm/kdmrc: Code:
# KDM master configuration file Code:
#! /bin/sh Code:
# These are the default runlevels in Slackware: Code:
# fluxbox startup-script: Code:
X Window System Version 6.9.0 Thanks! ...aaron **edit** one last thing, all packages from l/ are installed. **edit again** Also, if anyone is interested in browsing the current directory tree for this project, it can be found at: http://www.splashlabs.com/dev/kiox-current/ I am uploading the most recent build which containts this bug. It should finish uploading in a couple hours from the time I posted this thread. |
What about using startx or xinit instead of init 5?
|
init 5 works just fine (which does use startx).
Code:
#! /bin/sh This is for a custom kiosk system my company will be using for POS software so I will not be able to release something with such a huge bug. Otherwise I would have just worked around it as you suggested ;) Thanks! ...aaron **edit** By the way, Kiox Linux is essentially a custom Slackware build, but Pat's License prevents me from calling it so. |
And if you login as root and run an X session with KDM and login into it as user, does it break the same way?
|
Good suggestion! I didn't think to try that. Unfortunatly, I got the same results. Logged in as root, opened xterm and ran 'init 3'. Screen blanks with no chance of recovery.
My hard disks are starting to hate me, I had to grab a boot CD and rerun lilo to recover this time. :( Next time I will not mount all my other partitions (including my primary install partition) in my test system. ...aaron |
I've played quite a bit with WDM using init 4. I found I could safely exit runlevel 4 by just running 'init 5' from an xterm. Should dump you CLI login.
|
And at least going to text console or doing Ctrl-Alt-BackSpace works?
|
Problem solved. Thank you both for your help!
To try out gnashley's suggestion, I replaced my custom inittab with the stalk Slackware inittab. After that, I could cleanly exit any way I chose. I didn't realize the inittab was the problem, because it was working fine with XDM. I could use runlevel 4 for password login, and my custom implemented runlevel 5 for an auto login. So this asks the question, why does KDM not like runlevel 5 to be implemented? Did I perhaps do it incorrectly and XDM just didn't really care as much? I don't really know how to set up a custom runlevel 5, so I just guessed and it appeared to be working (until now obviously). Code:
# Runlevel 4 I guess it's not to important since I was planning to eventually phase this out and use KDM's auto login feature. But I am still curious to know how one would correctly implement their own runlevel. Thanks again for all the help and suggestions! ...aaron |
I've used 5 the same way you show, except for use with WDM, which is similar to XDM. I currently boot using init 4, but rc.4 is modified with an entry before XDM to use WDM instead. I use a standard inittab with default init 3 and pass the init 4 as a boot option.
After login I can run an xterm as root or with su and from there run 'init 5'. It dumps you back to the CLI login, as if rc.4 had not run and no login had occurred. If you really need to be in runlevel 3 you can run 'init 3' after 'init 5'. If you have runlevel 5 setup as you do, this might not work. But I get the same behaviour of locking up when trying to go directly from runlevel 4 to 3. You might find some useful stuff here: http://distro.ibiblio.org/pub/linux/...jects/AFX-wdm/ |
All times are GMT -5. The time now is 07:06 AM. |