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: 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
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Lines: 20
X-Complaints-To: abuse@bellsouth.net
X-Abuse-Info: Please forward a copy of all headers for proper handling
X-Trace: pcpocbcnbdmdhgfgdbdpiflmbcekedmfhojhikkbagflhcboomnnajp
koddalloagpmbpkbdccaanhcbdgoopiocngcbhdhhlbjpbippnceoinfolcepfpb
egecelahahflomdibnlfgkeohcmihglpnjegilp
NNTP-Posting-Date: Tue, 23 Jan 2007 12:05:52 EST
Organization: BellSouth Internet Group
Date: Tue, 23 Jan 2007 12:06:14 -0500
Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:8814
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
*****
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta BBS (1:261/20)
|
