Closed
Bug 753775
Opened 13 years ago
Closed 12 years ago
Maintenance service blocked by avast antivirus
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: marco, Unassigned)
References
Details
Attachments
(2 files)
I've tried to cancel the avast prompt, and Firefox started normally.
Reporter | ||
Comment 1•13 years ago
|
||
This is the dialog shown by avast
Comment 2•13 years ago
|
||
Kev, do you have any contacts at avast or shall i outreach
Reporter | ||
Comment 3•13 years ago
|
||
These are the options, in English they are:
1) Allow
2) Allow and add to the whitelist
3) Deny
4) Refuse and close the application
5) Refuse and move in the trash
As I said in the first comment, I've tried to deny the execution, but Firefox started normally (and looks like it updated correctly).
Comment 4•13 years ago
|
||
Adding Marcia, who also has the same contacts as I do at Avast. I note the platform is x86_64, which makes me wonder if you're using nightlies, which are unsigned and can create problems like this.
Marco - can you please let us know what version of Fx, you're using?
Reporter | ||
Updated•13 years ago
|
Version: unspecified → 14 Branch
Reporter | ||
Comment 5•13 years ago
|
||
I'm using the 32bit version of Firefox, but my platform is 64bit.
Note that the UAC dialog doesn't appear, even though I denied the execution.
Comment 6•13 years ago
|
||
> if you're using nightlies, which are unsigned and can create problems like this.
So what could possibly be happening is that there is only 1 version of the service installed. If you install a Nightly and a Release channel build, the maintenance service will update to the Nightly one because it is a higher version.
I think the Nightly builds though are signed by a trusted authority as well, just using a different secondary cert.
Reporter | ||
Comment 7•13 years ago
|
||
The workaround that the technical support gave me is:
"You can right-click on the orange a-ball icon in system tray and from the menu select AVAST! SHIELDS CONTROL -> DISABLE... Later you can enable it the same way."
I've asked if there's a way to completely solve the problem and I sent them the URL to this bug.
Reporter | ||
Comment 8•13 years ago
|
||
Jason, I'm wondering if it's my strict Avast configuration at fault here. Could you verify on your machine?
Ehsan, what is the specific ask for QA on this bug? Please provide that info whenever adding qawanted, thanks.
(In reply to Brian R. Bondy [:bbondy] from comment #6)
> > if you're using nightlies, which are unsigned and can create problems like this.
It would appear that the Maintenance service takes on the version of the most recently installed/updated Firefox version:
1. Installed Firefox 16.0a1 2012-06-08
> Maintenance Service version = 16.0a1
2. Installed Firefox 13.0 release
> Maintenance Service version = 13.0
3. Update Nightly to latest via About dialog and restart Firefox
> Maintenance Service version = 16.0a1
Marco, can you please clarify your steps to reproduce? I need to know what Avast product you have installed, what versions of Firefox you have installed, whether any of them were updated from a previous version, and your Avast configuration settings.
1. Install Nightly 16.0a1 2012-06-08
2. Install Firefox 13.0 release
3. Install trial version of Avast Internet Security
4. Restart Windows
5. Start Nightly
6. Allow installation of AVG WebPrep 7.0.1426 add-on and restart Nightly
7. Start Avast and ensure all shields are active
8. Install Nightly update via About dialog
9. Restart Nightly
> Nightly and Maintenance Service updated to 16.0a1 2012-06-13
> Avast does not prevent update in any way
Comment 10•13 years ago
|
||
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #9)
> Ehsan, what is the specific ask for QA on this bug? Please provide that info
> whenever adding qawanted, thanks.
I'm sorry, I was confused. I was thinking of another bug. Nevermind!
Keywords: qawanted → #relman/triage/defer-to-group
Updated•13 years ago
|
Keywords: #relman/triage/defer-to-group
Reporter | ||
Comment 11•12 years ago
|
||
I'm not using Avast anymore, but I strongly suspect this problem was due to my strict configuration.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•