You are not logged in.
As usual not content to leave things alone, so had to dork with nodm.
Couldn't find much straight forward info on this, why not post ? First a disclaimer, did this on Jessie, everything appears to be working fine but anything I ever babble about is at own risk if you experience borkage.
1st: install nodm however you prefer gui/cli, I generally prefer apt most times.
sudo apt-get install nodm
I logged my user out of current session and switched to another tty, tty3 with key combo
ctrl+alt+F3
Enter username + password to login. Disabled lightdm with
sudo systemctl disable lightdm
Enabled nodm with
sudo systemctl enable nodm
Then had one more step to get it working. You need a cli text editor, ie: nano, vi, vim etc. Im obviously using nano in the cmd below.
sudo nano /etc/default/nodm
Had to change NODM_ENABLED=, from false to true and edit it to have my username, instead of root. Save the file.
That was it,
sudo reboot
To reboot the system and my user was auto logged in to the default xsession like normal.
Ways to choose which desktop/Wm with nodm. Use
sudo update-alternatives --config x-session-manager
And choose which you want there or as yet unconfirmed, if it doesn't show up here. Edit the file (as root-etc) at /usr/share/xsessions/ called "Default Xsession" and add your preferred WM, where it says Exec= ie: Fluxbox, would/should be
Exec=/usr/bin/startfluxbox
Mentioned this is not confirmed as working yet and any decent De/Wm will be listed in update-alternatives anyway. Ok pretty much it. Hope somebody enjoys.
Vll!
Offline
Well scratch editing Default Xsession, even had issues with openbox-session from update-alternatives cause didnt bother setting up the right configs in ~/ Dratz!
Answer(s) appears to be hither but not dorking with it further for time being.
Bbl though.
Last edited by BLizgreat! (2017-04-10 12:59:56)
Offline
More info...
https://wiki.archlinux.org/index.php/Nodm
I don't care what you do at home. Would you care to explain?
Offline
^Thanks Hhh,
Making progress, the reason openbox-session wouldn't start via x-session-manager was a corrupt config file id put in home, fixed it and openbox-session came up.
A real non-config'ed-primitive session though, haven't setup autostart, no custom keybindings etc but worked alright.
Then got Fluxbox to fire up by editing that /etc/default/nodm file and adding /usr/bin/startfluxbox, where it had said NODM_XSESSION=/etc/x11/Xsession The non-config'ed Fluxbox was better than the openbox one. Shrugs, no biggie will dork around later and get things setup right. Though Should've spent more than 5mins, before posting this junk.
For time being just reversed the process and went back to lightdm.
Last edited by BLizgreat! (2017-04-10 14:05:38)
Offline
i'm surprised to see this is still getting updates.
what is the advantage to just starting openbox from a shell (i.e. startx etc.)?
Offline
Really not finding any compelling reason. Was just curious why so sparse the info on the topic seemed. Does look like it'd work fine w update-alternatives or following that Debian wiki link above.
My problem is atm don't feel like config'ing openbox-session (from scratch). Hadn't messed with fluxbox in quite a bit. Forgot how nice a wm it is too.
Nodm found its way on my gnu/nix things to dork w list. All the cool nixers are autolog-startx'ing w/o a dm. Found a good looking tute Hoas did on it.
Nodm, so far, meh. Barely lighter, barely faster boot-etc. Though seems like it's at least on par with plenty others and haven't messed w it long enough to really know.
Last edited by BLizgreat! (2017-04-10 15:09:33)
Offline
Default Xsession
To use the Default Xsession desktop, simply add the desired startup commands to ~/.xsession
EDIT: also: http://forums.debian.net/viewtopic.php?f=16&t=123694
Last edited by Head_on_a_Stick (2017-04-10 20:07:42)
Offline
^Nice how to and share Hoas. Yeah the order xsession is sourced from is up there hither. Editing that nodm file worked but has to be considered a hack.
Update-alternatives appears to work fine and is one of the sources default xsession is sourced from if xyz isn't present to override.
No worries think dorking w nodm was worth it. Learned some junk but am still torn between being either Hoas or Machinebacon when I grow up.
Last edited by BLizgreat! (2017-04-10 21:30:00)
Offline
^ so no more nodm?
because that HowTo from fdn doesn't mention it.
I am asking because I have a nagging suspicion that nodm is absolutely use- and pointless if you can do it that way, but am open to arguments.
Offline
I have a nagging suspicion that nodm is absolutely use
Actually, I think it may be a little worse than that:
It is meant for devices like smartphones, but can be used on a regular computer as well, if the security implications are acceptable.
https://packages.debian.org/jessie/nodm
Offline
^ because it defaults to autologin?
Offline
Yes. I don't see how this is a good thing even on a smartphone. Especially on a smartphone.
I don't care what you do at home. Would you care to explain?
Offline
To clarify: my concerns relate to the smartphone focus of the application rather than it's security per se — my linked guide presents the same security risk.
Offline
Sowwie fellows, haven't paid attention to this. Not overly worried about nodm and sec on any form factor.
Same can be said for any auto login approach. Debian's just being Debian in any advisory to that effect. Plenty of ways to add however many sec measures someone wants.
Not so much a fan of it either. Nope Ohnonot, haven't docked w it since posting this babble. Really no plans to, shrugs.
Will keep on dorking with whatever hits on the radar. You'll always learn something along the way, messing with whatever thing gnu/nix.
Last edited by BLizgreat! (2017-04-14 03:22:04)
Offline