Closed
Bug 196595
Opened 22 years ago
Closed 20 years ago
skin download freezes and cannot be cancelled after usually one other skin download and install
Categories
(Core Graveyard :: Skinability, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: laijerrad, Assigned: andreww)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
Software Installation dialog freezes when trying to install a skin. I install
first skin, everything is ok. Then, I sometimes can install the second skin and
everything is ok. But then when I click to install the third skind (and
sometimes this happens for the second skin), the software installation dialog
freezes and cannot be cancelled.
Reproducible: Always
Steps to Reproduce:
1. Go to some skin site and click on a skin for 1.3b to be installed.
2. After that is done, look at some other skins, and click to install.
3. Usually the second time goes through ok, but then click on some other skin to
intall, and the dialog freezes.
4. Important, don't close browser between installs.
Actual Results:
The Software Installation dialog froze. Progress indicator is empty and clicking
on Cancel button doesn't work. It can be clicked on, just that it's not
functional. The dialog doesn't go away. I can browse freely, but the dialog is
there. And it seems that the only way to stop it is to use End Process which
causes all open Mozilla instances to go down.
Expected Results:
Software Installation dialog should go on installing or tell the user that
install is not possible. It definately should be responsive. I mean, the problem
is not a big deal, just some buggy thing you might want to get rid of.
The theme that I'm using seems to not be important. THe bug was reproduced under
various themes (Classical, Modern, Orbit 3+1 for Moz1.3b).
Updated•22 years ago
|
QA Contact: pmac → gbush
Comment 1•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•