- This topic has 20 replies, 6 voices, and was last updated Jul 29-7:48 pm by Anonymous.
-
Posts
-
seaken64
I agree with Bob’s point. Unless you are aware, and prepared to deal with the updates yourself, you will have less hassle if you keep the system setup as designed. It’s okay to make modifications and respins. That’s partly what makes antiX so interesting and useful. But just be prepared. You will have to manage your respin/modifications yourself.
Seaken64
Anonymous
So those DE-FM entries showing on the menu are mere blank entries which are not working
Two possibilities come to mind for “how could this happen”
Editing (removal of unwanted /usr/share/xsessions/ files) was performed during a non-persistent liveboot session?
(so changes would have been lost at shutdown)
or
You did not kill & restart SLiM after editing, and SLIM applied the (previously-read, and cached) original list when you logged out and slim redisplayed its login screen.anilkagi
I greatly appreciate your efforts skidoo.
Editing (removal of unwanted /usr/share/xsessions/ files) was performed during a non-persistent liveboot session?
(so changes would have been lost at shutdown)This is not a possibility in this case skidoo, because I did not make the editing during the liveboot session.
You did not kill & restart SLiM after editing, and SLIM applied the (previously-read, and cached) original list when you logged out and slim redisplayed its login screen.
This could certainly be THE possibility skidoo. I certainly did not do that because I don’t know what it is.
You mean, immediately after removing the fluxbox, jwm and hebstluftwm via the synaptic and before re-logging or rebooting, I should have killed and restarted SLiM.
How to do it? How to kill and restart SLiM.
Thanks
How to do it? How to kill and restart SLiM.
Although I’m not recommending that you attempt do so, the command “sudo killall slim” or “sudo telinit 5” should accomplish that goal (perhaps not gracefully).
You mean, immediately after removing…
During the boot process, the init.d instructions cause the system to autostart items (configured to be) associated with “runlevel 5”. The SLiM login manager is one of those autostarted items. When SLiM starts, it parses /etc/slim.conf and reads the list of available session types. My point in the earlier post was that I suspect SLiM retains that cached sessions list in a memory variable, reading from it (cache) each time you logout/login. If so, SLiM will not have a need to, or opportunity to, re-read and recognize changed details within its .conf file until the next time it (SLiM) is launched.
After adding or removing window manager packages, instead of forcibly killing the SLiM process and starting a fresh instance… it would probably be better to perform a clean shutdown. After reboot, the SLiM menu items will reflect the updated list (or /xsessions/ directory entries) .
- You must be logged in to reply to this topic.
