Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !nntp.giganews.com!nx01.iad01.newshosting.com!newshosting.com!14   
   .99.99.194.MISMATCH!news-in-02.newsfeed.easynews.com!easynews.co   
   !easynews!sn-xt-sjc-02!sn-xt-sjc-08!sn-post-sjc-01!supernews.com   
   corp.supernews.com!not-for-mail   
   From: Frank    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: Re: evil firestarter popup window   
   Date: Wed, 24 Jan 2007 01:14:10 -0000   
   Organization: Posted via Supernews, http://www.supernews.com   
   Message-ID: <12rdcn2dcvmaode@corp.supernews.com>   
   References:    
   User-Agent: pan 0.120 (Plate of Shrimp)   
   MIME-Version: 1.0   
   Content-Type: text/plain; charset=UTF-8   
   Content-Transfer-Encoding: 8bit   
   X-Complaints-To: abuse@supernews.com   
   Lines: 33   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:8864   
      
   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   
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)