On Fri, 23 Sep 2005 20:48:41 +1000 David Seikel <[EMAIL PROTECTED]> babbled:
> On Thu, 22 Sep 2005 22:32:11 -0400 (EDT) [EMAIL PROTECTED] wrote: > > > Actually I had this problem with a gentoo install a little while ago, > > the login process for some reason wasn't triggering the usual scripts > > for a login shell, so e17 was starting without any of the profile > > scripts triggering (/etc/profile, ~/.bash_profile). Consequently all > > of gentoo's environment configurations in /etc/env.d weren't loading > > up, the path being just one of the problems. > > > > Unfortunately I can't remember for the life of me how I fixed it > > without resorting to hacks in the bashrc or session files. If I > > remember I'll let you know. > > Hacks to session and startup scripts is exactly how I fixed entranced, > just sprinkled calls to /etc/profile librally. Entranced seems a little > brittle and fussy. > > My symptoms are that the keyboard gets mostly locked out. I am unable > to type user name and password which makes entranced exceedingly > useless. If I use Ctrl-Alt-F1 to switch to a text virtual terminal, so > that I can log in as root and kill entranced, the screen goes black for > a few seconds and then I am returned to the entranced screen, so no > access to VT's (my monitor blacks out for a few seconds when changing > resolution, this may or may not be the same blackout). Ctrl-Alt-Del > won't reboot, so my only option is to kill the power. ctrl+alt+f1 problems are likely x problems, not entrace. there is a power off button too :) but well entrance is not production ready and likely will not be for a long long time. use at your own risk. > > This usually doesn't happen when I run entranced manually, or invoke > it's startup script manually. When the startup script is started as > part of the boot sequence, it almost always happens. Sometimes it won't > happen straight away, but will fail later. > > Running /etc/profile as part of the startup script, and also calling > enlightenment through a wrapper script that first calls /etc/profile > seems to fix it, mostly. I still get keyboard killed once in a > while (happened once yesterday after a fresh boot). > > A related symptom (which is what prompted me to sprinkle /etc/profile) > is that xawtv4 won't start up properly, it has trouble talking to the > TV card, but other TV software (kdetv for instance) had no problem. > Obviously this happens when I can login. Using xdm, kdm, gdm, and wdm > doesn't display any of these problems. > > Wrapper scripts, and entranced writing to /var/run/entranced.pid itself > caused other problems when I try to do the LSB standard startup script > thing, which is the best way to integrate e17 into SuSE (9.3 > Professional). Each of these problems will invoke the locked out > keyboard problem if I try to work around them. The current working > version has enlightenment spew debugging info all over my boot console > (redirecting it to /dev/null invokes keyboard lockout), and needs an > explicit 'killall -TERM entranced' and removal of the pid file in the > startup script for the stop action. I also pass -nodeamon to entranced, > call it via a wrapper, and call enlightenment via a wrapper. All the > wrappers do is call /etc/profile first. > > I really want to use entranced and enlightenment, which is why I went to > all the trouble of trying to get it to work. It is a lot of trouble, > because it often works fine when run manually, but fails when boot > starts it (booting SuSE takes a few minutes). Having the keyboard > locked out makes debugging very tricky, as all I can do is power down > the box, reboot into single user mode, swap to gdm, and reboot again. > This is also why I haven't looked at the code yet. Yes, I could probably > ssh into the box from a spare computer, but that's not possible at the > moment. > > So, it's mostly working now, with only the odd time when I need to just > power cycle my computer. But I would rather not have enlightenment spew > info all over my boot console, and I would rather not have to explicitly > kill entranced and remove it's pid file. For obvious reasons, I can't > provide any gdb output, and any attempt to work around the various > remaining problems invokes the keyboard lockout bug. Entranced is > brittle and fussy, it's probably some sort of uninitialized memory or > environment problem. > > Hope something in here gives some sort of clue. > > -- > Stuff I have no control over could be added after this line. > > Send instant messages to your online friends http://au.messenger.yahoo.com > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 [EMAIL PROTECTED] Tokyo, Japan (東京 日本) ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
