Closed
Bug 473173
Opened 17 years ago
Closed 17 years ago
after applying nightly update Minefield does not restart automatically, it must be restarted manually
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 473417
People
(Reporter: fpiera, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090112 Minefield/3.2a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090112 Minefield/3.2a1pre
Nightly update downloaded and installed but Minefield does not restar automatically. Restart must me done manually. A small rectangular window is left without any text or function apparently and there is no wasy to erase it from the screen or the tool bar. This happens in 20090112 nightly update and in the previous one of 20090111 for both minefield and schredder.
Reproducible: Always
Steps to Reproduce:
1.download of nightly update
2.push button for restart and install
3.a small rectangular window without text appears and a button on the tool bar bu4t they are impossible to erase.
4. Restart must me done manually but small window remains
Actual Results:
Update is installed apparently but programme must be restarted manually
Expected Results:
Programme restart automatically
This has appened already with 20090111 nightly updates
| Reporter | ||
Comment 1•17 years ago
|
||
could apply to component application update
Version: unspecified → Trunk
Comment 2•17 years ago
|
||
Try a new profile, I've had no problems on Vista HP SP1 and Minefield builds.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090109 Minefield/3.2a1pre Firefox/3.0.4 ID:20090109070944
Version: Trunk → unspecified
| Reporter | ||
Comment 3•17 years ago
|
||
The problem was not present with updates of 20090109. It started with 20090111 updates for both minefield and thunderbird usin windows xp SP2 professional
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•