You are not logged in.
Pages: 1
forum is good as is.
usable as no JS or JS disabled.
even users able to register without have to enable JS;
bravo; there is no captcha.
dont forget users of w3m, lynx, and likes.
IMO it is appropriate that:
* Slim must check whether or/not there is a monitor or multiple monitors to put something.
Not blindly do something itself.
* if there is NO monitor at all then it simply go to idle and wait for one to plugged.
listen for plug or check periodically.But that up to user to decide; So it exposed config option to user to what to do when NO monitor, just quit or go to idle and wait?
if slim wants to support headless and/or network login and/or forward the login window on network then it must provides related config options to its users to decide. it is up to user to decide not slim.
if slim wants to work with multiple monitor case then it is exposed related config options to users to decide. then user decides eg:
*present yourself on both monitor simultaneously to interact/login.
*use ID=xyfoobar monitor
*use internal monitor ignore others
* ... likewise
So feel free to file a bug.
it is normal. i dont know its internals but i quess slim is not designed to work without a monitor connected.
When you connect a monitor later it is already too late that slim give up and quit.
Because there is no event listener/handler that catcth that PLUG event then do appropriate i quess.
you have to write that listener/handler yourself and order it to fire slim when event catched.
Or you have to wait until monitor is plugged
or make some service fire up slim every 1 second until its succeeded
or get rid of slim and autologin by some other means.
Take all this as a grain of salt.
Pages: 1