enlightenment took over my comp
ive been messing around with wm and found one i enjoy...enlightenment. Well until today when i realised i cant get into kde anymore. when i close enlight. it brings up kdm and no matter what wm manager i choose from there it takes me back to enlightenment. i cant use flux/kde or any other wm. I can use them with different user tho. any ideas? oh yeah: SuSE 9.1
|
I'm a Slackware user, so I'm kind-of shooting in the dark but I'll try to help.
Open a command prompt and go to /home/yourname. There should be a file there called .xinitrc. Open it in a text editor and look down at the bottom of the file for something like "#start the window manager". The very next line should be the full path to your favored window manager's executable file. The syntax is "exec /path/filename". Here's my xinitrc file for icewm: Code:
#!/bin/bash Have a good one. --Dane |
thanks a bunch. havent tried switching back to kde yet but pretty sure its fixed. the only thing in the.xinitrc file was #! /bin/bash exec /.../enlightenment. luckly there was a .xinitrc.template (probably a suse thing). thanks again for leading me to the right place.
|
Good; I hope that works out well for you. Glad to be of assistance.
--Dane |
some bad news. it didnt work. the template .xinitrc had a if elif series in it that sets $WINDOWMANAGER. i tried change the last line form exec $WINDOWMANAGER to exec /pathtokde/startkde and still no kde. looking at the ~/.xsession file all there is is:
# Enlightenment inserted Execution string here exec /usr/X11R6/bin/enlightenment i dont know what that file is but that looks weird to me. dang i was hoping it was fixed. |
yay. im in kde. changing the exec ...enlighenment to ...kde work but now i have to change it everytime i want to switch. anyone have a good example of a ~/.xsession ?
|
Hi, Tardigrade.
It looks like some auto-magic configuration gizmo has decided that your window manager is "supposed" to be windowmaker and is inserting the command to start it into your .xinitrc file. Here's what you can do to find out which file is causing the problems: 1) read the man pages on "grep". (yes, I know this is a cop out on my part but there's really no substitute for reading tfm) :) 2) starting in "/", grep recursively for the phrases: "# Enlightenment inserted Execution string here" and "exec /usr/X11R6/bin/enlightenment". 3) remove or comment out (put a "#" at the beginning of the line) all mentions of those phrases. 4) cross your fingers and reboot :) Hopefully this will save you some fingerwork in the future. Anybody more Suse-friendly have any suggestions? --Dane |
searching for those lines worked. thanks a bunch.
|
All times are GMT -5. The time now is 07:27 AM. |