Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !border2.nntp.dca.giganews.com!nntp.giganews.com!bigfeed3.bellso   
   th.net!bigfeed.bellsouth.net!bignumber.bellsouth.net!news.bellso   
   th.net!bignews1.bellsouth.net.POSTED!5bc78d0b!not-for-mail   
   From: noshellswill    
   Subject: Re: evil firestarter popup window   
   User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux))   
   Message-Id:    
   Newsgroups: alt.os.linux.ubuntu   
   References:  <12rdcn   
   dcvmaode@corp.supernews.com>   
   MIME-Version: 1.0   
   Content-Type: text/plain; charset=ISO-8859-1   
   Content-Transfer-Encoding: 8bit   
   Lines: 44   
   X-Complaints-To: abuse@bellsouth.net   
   X-Abuse-Info: Please forward a copy of all headers for proper handling   
   X-Trace: pcpocbcnbdmdhgfgdbdpiflmbcekedmfhojhikkbagflhcbooggnldh   
   iljojifclkbeambdldciogpabdgoopiocngcbhdhhlbjpbippnceoinfolcepfpb   
   egecelaflbbficleejenodmenoicgmfmohhjpkp   
   NNTP-Posting-Date: Tue, 23 Jan 2007 22:42:19 EST   
   Organization: BellSouth Internet Group   
   Date: Tue, 23 Jan 2007 22:42:44 -0500   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:8876   
      
   On Wed, 24 Jan 2007 01:14:10 +0000, Frank wrote:   
      
   > On Tue, 23 Jan 2007 12:06:14 -0500, noshellswill wrote:   
   >    
   >> Gents:   
   >>    
   >> FIRESTARTER misbehaves on my system. I have tried to squash it   
   >> manually, since all auto-remove functions fail to do this. Using    
   >> as a probe I have manually removed all fires containing the string   
   >> '*firestarter*'.    
   >>    
   >> Yet on each login -- immediately after the UBUNTU splashscreen appears ---   
   >> I am presented with a ( transient ) popup window asking me to enable   
   >> FIRESTARTER. If I fail to quickly ( ~ 5 sec ) refuse, then GNOME locks-up   
   >> and I must do a CLI reboot to re-enable the system. WTF ?   
   >>    
   >> I'm guessing FIRESTARTER (code/reference) has insinuated itself into a   
   >> boot-up(?) script. If true I'll need to locate and comment_out the   
   >> offending lines in that script.   
   >>    
   >> My question: If so ... which script is the likely host?   
   >>    
   >> nss   
   >> *****   
   >    
   > Hmmm, I'm not sure someone named NoShells will want to hear this but it is   
   > a definitive answer to this and many other questions - how do I set   
   > whatever-service to start and stop as desired.   
   >    
   > First type "sudo chkconfig --help" without the quotation marks in a, yes,   
   > shell terminal, and have a look.  Then type "sudo chkconfig -- list   
   > firestarter" and you'll see where it's on and off.  Then type "sudo   
   > chkconfig --level 3 firestarter off" as always without the quotes.   
   >    
   > Frank   
      
      
   Frank:   
      
   BASH does not know the command 'chkconfig '. Neither does MAN .   
      
   nss   
   ******   
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)