Closed
Bug 489090
Opened 15 years ago
Closed 14 years ago
During update, a license popup appears but all the fields are greyed out.
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: grgoffe, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090413 SeaMonkey/2.0b1pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090413 SeaMonkey/2.0b1pre The current version of seamonkey that I'm using periodically notices that there is an update available. I poke the "update now" button but get a dialogue about a License but the only thing I can do is use the back button or ask later button. Reproducible: Always Steps to Reproduce: 1.I am NOT able to trigger this problem. It seems to happen whenever there is an update available. 2. 3. Actual Results: No update Expected Results: Update to latest version of seamonkey in test. Not put up the disabled license popup or not have the info greyed out and just do the update/upgrade.
Comment 1•15 years ago
|
||
Dupe of Bug 487012, still waiting for 1.9.1 approval and landing.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Updated•15 years ago
|
Assignee: installer → nobody
Component: Installer → Application Update
Product: SeaMonkey → Toolkit
QA Contact: xpi-packages → application.update
Version: unspecified → Trunk
Reporter | ||
Comment 3•15 years ago
|
||
Howdy, Can I get a status on this bug please? I'm still seeing the problem. Regards, George...
Comment 4•15 years ago
|
||
Unduping from bug 487012 since the reporter is still experiencing this. Not sure what is going on... this isn't happening for the majority of users so additional investigation is warranted.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reporter | ||
Comment 5•15 years ago
|
||
Robert, I am most willing to test any new code you guys come up with. Either seamonkey or firefox. Thanks, George...
Comment 6•15 years ago
|
||
It is working for most in SeaMonkey and Firefox and there isn't enough info to figure out why it isn't working for the few that it isn't working for so there is no way to know if it is a code problem or a system configuration difference causing this for you.
Reporter | ||
Comment 7•15 years ago
|
||
Robert, I also have a FC 8 system. I'll test there as well. Current seamonkey = Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b5pre) Gecko/20090424 SeaMonkey/2.0b1pre Current firefox/minefield = Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090807 Minefield/3.6a1pre Thanks again, George...
Reporter | ||
Comment 8•15 years ago
|
||
Robert, In trying to download from the "nightly builds" url of mozilla.org, I tried to get the SeaMonkey version for Linux i686 and the x86_64 but I get a "not found url" for those two. Another problem? George... http://www.mozilla.org/developer/
Comment 9•15 years ago
|
||
I haven't been keeping up with SeaMonkey development so I don't know anything about their 64 bit support
Comment 10•14 years ago
|
||
If you are still experiencing this can you add a new boolean pref in about:config with a name of app.update.log.all and a value of true. The next time it happens open the error console and copy / paste the individual entries that start with AUS into this bug. Thanks
Comment 11•14 years ago
|
||
Please update if you are still experiencing this and did the steps mentioned in comment 10 helped you.
Whiteboard: [closeme 2010-05-28]
Reporter | ||
Comment 12•14 years ago
|
||
Aravind, Thank you for working on this bug. I have not experienced this problem in some time now. I have left my settings, as changed in #10 above, just in case it happens again. So far so good. Regards and again, thanks, George...
Comment 13•14 years ago
|
||
Resolving -> WFM. Reporter, if this happens again please either reopen this bug or file a new one. Thanks/
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago → 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2010-05-28]
You need to log in
before you can comment on or make changes to this bug.
Description
•