From: robin_listas@es.invalid   
      
   On 2017-11-21 03:47, bad sector wrote:   
   > On 11/20/2017 05:21 PM, Carlos E.R. wrote:   
   >> On 2017-11-20 22:52, bad sector wrote:   
   >>>   
   >>> On Tumbleweed or on Leap, if I give grub2 a   
   >>> kernel argument of "init 3" then how do I   
   >>> start X after logging in?   
   >>>   
   >>   
   >> start X, or startx? It is not the same thing.   
   >   
   > you lost me there   
   >   
   > By start X I mean the human readable form of   
   > "starting the garphical enviromnment directly from cLi"   
   > for which startx is (or used to be) the /command/   
      
      
   startx is a command.   
      
   start X is a human words that name a procedure.   
      
      
   You wrote in the subject line "startx" but your initial post talks of   
   "start X": two words instead of one, and different case. NOT the same   
   thing, in computerese.   
      
      
   If you do not understand it, read it all again, and again, and again,   
   till you do. Like a mantra.  :-)   
      
      
      
      
   >> If you want to start a single graphic session for the current user, then   
   >> run the command "startx". Mind: it will by default fail for all users   
   >> except root. This is intentional and can be changed. The error says why   
   >> and how, if I remember correctly. Just change some permissions, but   
   >> beware of possible security problems.   
   >>   
   >> Also this method has problems with permissions for external media, such   
   >> as an USB stick, or even playing sound. They are known, you can solve   
   >> them on your machine if you insist, but they will not be corrected at   
   >> source.   
   >   
   > Sounds more like an administrative (end user)   
   > decision to me as opposed to a development one :-)   
      
   It is very simple: startx is not maintained, not developed. It has   
   problems and failures, and there is no intention to correct them.   
      
      
      
   >> If what you want is to start the full X graphical system, full mode,   
   >> then issue "init 5" as root. And remember that you have an open console   
   >> as root, so go back and close it.   
   >   
   > Ok, let's back up here a step...   
   >   
   > Do you mean to issue "startx" as root and then   
   > as soon as it starts to bail out because then   
   > kdm or gdm will resume. Wouldn't that be the   
   > same as just issuing kdm or gdm?   
      
   No. I never said that. Nothing of the sort.   
      
   I said: do "init 5" in the console as root. When X starts (you get a   
   graphical prompt for username and password), you go first and close the   
   console session, because it is still open by root, and any one passing   
   by can own your computer!   
      
   That is: type [ctrl][alt][f1] to get back to the console, then close it   
   (type exit or [ctrl][D]), then back to graphics [ctrl][alt][f1].   
      
   Gosh! You have been here two years, you don't know that?  :-?   
      
      
   > In the OP i did not include (for the sake of   
   > simplicity) the fact that I also tried kdm and   
   > gdm, as root, none of those worked either.   
   > Personally I don't have issues with first   
   > launching some form of *dm but the original   
   > way somehow seems less microshitty.   
      
   The proper and correct way is and always has been "init 5". For decades   
   at least. There is another modern way which I don't care to remember so   
   I will not write it here.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)