From: Henrik.Carlqvist@deadspam.com   
      
   On Thu, 15 Sep 2022 08:48:01 -0400, bad sector wrote:   
      
   > On 9/15/22 01:44, Henrik Carlqvist wrote:   
   >> On Thu, 15 Sep 2022 00:59:22 +0000, bad sector wrote:   
   >>   
   >>> On booting into the Slaclware-15.0 login prompt I get   
   >>>   
   >>> "Error: Can't open display"   
   >>> "Error: Can't open display"   
   >>>   
   >>> What display is this referencing?   
   >>> (NB. no-one has logged-in at this point)   
      
   >> Did you add any X program to any startup files like /etc/rc.d/rc.local?   
      
   > there are some commands in ~/.profile but seeing   
   > that I still haven't logged in when the error pops up...   
   >   
   > I ran a string search from the outside against the entire Slackware   
   > partition for "Can't open display" asci/binary and it returned two yards   
   > of instances but that don't help me any.   
      
   Before anyone has logged in, the only things that has been run are the   
   kernel itself and /sbin/init which runs files in /etc/rc.d as described   
   in /etc/inittab.   
      
   Some of the files in /etc/rc.d will give an output. Even if those scripts   
   themselves do not echo "Error: Can't open display" they might call some   
   program which does give that output. It might be easier to find the cause   
   of that output by looking at other outputs before and after, where did   
   those outputs come from? For example, the file /etc/rc.d/rc.M starts by   
   doing echo "Going multiuser...", does "Error: Can't open display" come   
   before or after "Going multiuser..."?   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)