Closed
Bug 589258
Opened 15 years ago
Closed 15 years ago
some windows 7 machines boot with the wrong resolution sometimes
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: coop)
References
Details
(Whiteboard: [buildduty])
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282316894.1282317410.13910.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282320697.1282321479.32704.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282322189.1282322943.6437.gz
All three runs failed mouse position and selection tests, so I made the sheriff back out a blameless patch that seemed vaguely related, but then before his backout ran, talos-r3-w7-015 passed those tests in http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282330914.1282331746.9799.gz, so given the mouse-and-selection nature of it, now I'd bet on some sort of dialog stuck open.
Comment 1•15 years ago
|
||
This machine had the wrong resolution set. I changed it back and gave it a reboot, but that's very concerning....we have a tool we run at boot that's supposed to fix the screen resolution.
Assignee: nobody → bhearsum
Comment 2•15 years ago
|
||
Updating summary.
The particular machine mentioned (talos-r3-w7-052) is now fixed, leaving this open for the root problem though
Summary: talos-r3-w7-052 needs a talking-to → some windows 7 machines boot with the wrong resolution sometimes
Comment 3•15 years ago
|
||
Pretty sure I filed a bug on this and left buildbot disconnected several days ago.
| Reporter | ||
Comment 4•15 years ago
|
||
That was bug 586841. There's also bug 581864 on talos-r3-w7-051, and there's bug 553081, where the second set of 20 was apparently ignoring the set-resolution-on-boot thing and using the resolution that the ref image was giving them, so maybe it hasn't ever actually worked to set them?
Comment 5•15 years ago
|
||
Seems like a buildduty thing; I'm not going to have time to look at it, personally.
Assignee: bhearsum → nobody
Whiteboard: [buildduty]
| Assignee | ||
Updated•15 years ago
|
Priority: -- → P3
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
Priority: P3 → P2
| Assignee | ||
Comment 8•15 years ago
|
||
I *think* I fixed this, but then I fat-fingered the poorly-designed integrated shutdown button. I've added talos-r3-w7-051 to the reboot list.
Depends on: 594963
| Assignee | ||
Comment 9•15 years ago
|
||
(In reply to comment #8)
> I *think* I fixed this, but then I fat-fingered the poorly-designed integrated
> shutdown button. I've added talos-r3-w7-051 to the reboot list.
Machine is back up, and yes, it maintains the proper resolution over reboots.
For reference, I had to set the resolution through the NVIDIA control panel to get it to stick.
Slave is connected to talos-master02 again.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•