Closed Bug 319319 Opened 17 years ago Closed 17 years ago
Web Search spyware toolbar breaks the browser with a large grey bar at the bottom of the screen
39.02 KB, image/gif
32.83 KB, image/gif
2.59 KB, text/plain
1.95 KB, text/plain
1.79 KB, application/octet-stream
614 bytes, patch
|Details | Diff | Splinter Review|
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Large area under the status bar. Appears the browser window is incorrectly placing the status bar. There is a red upward facing arrow on the left side of the large area. This bug is similar to but not the same as 309495 & 298874. This first appeared after I upgraded from 1.0 to 1.5. I have since uninstalled Firefox 3 times and reinstalled it and the area still appears. Reproducible: Always Steps to Reproduce: 1. Open the browser, thats all. 2. 3. Actual Results: Large area appears under the status bar. This was not happening in prior version. This may or may be playing a factor but on my machine my userid is XSXBTSO. Because of a earlier non-browser related issue another account got created and it was named XSXBTSO.000, I don't know if the simliarities between account names is confusing it or not.
This may well be a duplicate of bug 314674 if you installed 1.5 over the top of 1.0.x. Does the problem occur in safe mode ? (http://kb.mozillazine.org/Safe_mode)
If this is still visible in safe mode, what exntension do you have installed?
Bringing Firefox up in Safemode does not appear to make a difference.
I am not running with any extensions. I added a new gif attachment of Firefox up in Safemode, no noticeable difference. Could the funky account situation I mentioned in the bug be playing a role? Assumming not many others are seeing this I'm just wondering what is different about my setup.
Another thing and this may be non-related but each time I initially bring up Firefox after a reboot my bookmarks toolbar does not display and the "rolling" icon that shows a page is being loaded does not stop. If I kill Firefox and bring it back up then the toolbar appears and the icon stops "rolling". This might be be a separate issue.
The gif attachment demonstrates what I mean about the missing toolbar and rolling icon on when I fire up Firefox the first time after a reboot.
I just realized something, I'm running with TalkBack 1.5, which is the crash reporting tool Firefox comes with. I didn't realize it was installed as an extension. Again starting up in Safemode made no difference.
Nick, I can see from your suggestion about the console that the Chrome theme seems to be corrupted. I provided a gif of Chrome folder contents. Assumming the Chrome theme is the problem do I just delete the folder? BTW you rock bud, I didnt know I could look at the console to see what was going on. Thanks! Scott
Are those console errors from before you have to kill Firefox or after ? What series of steps did you perform before copying the console output. Looks like you went to about:config once (the navigator.properties and region.properties errors). Chrome is actually a generic term meaning the UI of the application (the shiny stuff). What we're trying to do is figure out what happens to the chrome when 1.5 is installed over the top of 1.0.x (bug 314674). Since it isn't easy to reproduce this problem please do not delete anything out of the broken profile. To be getting on with you can create a new profile using the profile manager (http://kb.mozillazine.org/Profile_manager) and migrate your settings across (look for a migrate link at the url for the manager).
Can you please zip the contents of your <installed-firefox-directory>/chrome/*.manifest folder and attach it?
OK, this is definitely spyware infestation, see http://www3.ca.com/securityadvisor/pest/pest.aspx?id=453096424 I'll talk to the security group to decide whether/how Firefox should try to fix this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Large area under status bar showing red upward arrow. → MyWebSearch spyware toolbar breaks the browser with a large grey bar at the bottom of the screen
Hmmm....I read the link about the Spyware and I'm not seeing a connection. The link didn't mention anything about how it affects Firefox, if it even can. No mention at all about it creating a area under the status bar. The link said it affects toolbars at the top. Ad-Aware finds no evidence of the MyWebSearch spyware on my machine. Just in case AD-Aware was unable to detect it I did a search of my systems registry via RegEdit looking for the partial string: "MyWeb". No MyWebSearch hits. Just so I can learn, what leads you to believe its spyware? Yes the red arrow is still present. Scott
The manifest files that were posted include m3ffxtbr.manifest, which is shipped by this piece of spyware. For some reason the spyware is broken, so instead of displaying a toolbar it displays an XML parsing error at the bottom of the screen.
Benjamin, Thanks for that info! Will deleting that file help fix the problem? Scott
Never mind I can answer that. I renamed the file m3ffxtbr.manifest to BAD-m3ffxtbe.manifest-BAD and restarted. Problem gone! As far as I am concerned this bug can be closed. This might be a solution to put in a FAQ somewhere to aid others. Scott
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Scott, I think the devs. want to leave this open to decide what we're going to do if something like this arrises again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #21) > The manifest files that were posted include m3ffxtbr.manifest, which is shipped > by this piece of spyware. For some reason the spyware is broken, so instead of > displaying a toolbar it displays an XML parsing error at the bottom of the > screen. I've helped half a dozen people with this bug in the last couple of days in #firefox. What do you think to adding chrome\m3ffxtbe.manifest to the list of files to be removed at install time ? Are there consquences to that ?
*** Bug 327651 has been marked as a duplicate of this bug. ***
This is coming up often in the support forums, so I'm asking for blocking.
Assignee: nobody → dveditz
Status: REOPENED → NEW
Flags: blocking18.104.22.168? → blocking22.214.171.124+
Fixed on trunk, 1.8 and 1.8.0 branches
Someone might want to reopen this bug: it seems that the same spyware has reappeared with a slightly altered name. See the thread started on news://news.mozilla.org/mozilla.support.firefox 19-Dec-2006 20:38 +0100 by Scot Ausborn under the title "FF 2.0 problems: Help menu, bookmarks, area below status bar" and how the problem was solved.
(In reply to comment #19) > OK, this is definitely spyware infestation, see > http://www3.ca.com/securityadvisor/pest/pest.aspx?id=453096424 > > I'll talk to the security group to decide whether/how Firefox should try to fix > this. > That www3.ca.com page seems to have been withdrawn: I get a ca.com error page by trying to browse it.
see comment #30
(In reply to comment #30) > Someone might want to reopen this bug: Please don't. I appreciate the effort, but this really ought to go in a new bug otherwise everyone gets confused -- is it fixed or not fixed? The original version is fixed, this mutation needs a new fix and a new bug. Your initiative in tackling this is very much appreciated!
(In reply to comment #33) > (In reply to comment #30) > > Someone might want to reopen this bug: > > Please don't. I appreciate the effort, but this really ought to go in a new bug > otherwise everyone gets confused -- is it fixed or not fixed? The original > version is fixed, this mutation needs a new fix and a new bug. Done. You should by now have received a couple of Bugzilla messages for bug 364460 (I put you on the CC list). > > Your initiative in tackling this is very much appreciated! > :) This is my first Mozilla patch. (The fix seemed obvious, after seeing how you had fixed this one.)
Comment on attachment 249163 [details] [diff] [review] proposed patch for mutated spyware This patch goes into bug 364460
You need to log in before you can comment on or make changes to this bug.