Open Bug 691193 Opened 14 years ago Updated 3 years ago

Update window is blank after restoring from sleep

Categories

(Core :: Widget: Win32, defect, P3)

9 Branch
x86_64
Windows 7
defect

Tracking

()

People

(Reporter: jesup, Unassigned)

References

Details

(Whiteboard: [lang=c++][tpi:+])

Attachments

(1 file)

9.0a2 (2011-09-30) The update window was blank. Minimizing it and bringing it back up caused it to refresh and be viewable.
Component: Installer → Widget: Win32
Product: Firefox → Core
QA Contact: installer → win32
Seen this with other windows as well and I suspect this is bug is a duplicate. It definitely isn't an app update specific bug. There might be a better component to put this in than widget win32.
Whiteboard: [DUPEME]
Attached image blank safe mode dialog
jesup, did your "blank dialog" have a title and the contents were blank, like this screen shot? I had someone encounter this on win7 after he updated to version 10. (He crashed immediately except in safe mode. Reboot of the PC cleared it up)
correction - He crashed immediately [and repeatedly on startup] except in safe mode. Reboot of the PC cleared it up the startup crash @rs, I was not able to find a bug to dupe this to
I did not crash; it was a purely visual bug. It probably looked similar to that.
I see this all the time for the update dialog on my laptop when I restore it from sleep mode.
Summary: Update window for Aurora blank → Update window is blank after restoring from sleep
Mentor: jmathies, tabraldes, netzen
Whiteboard: [DUPEME] → [good first bug][lang=c++]
Hi, I would like to work on this bug.
Felipe - great! Feel free to work on any bug. I've seen blank update windows recently as well. Once you have a patch, add it here and ask for review from someone (we can help find someone, or ask who should review it in #developers on IRC)
Unfortunately, I got stuck in some deadlines and I won't be able to try to fix this bug soon. So, if anyone would like to take, feel free :)
Can anyone list the steps to create this bug. Thanks Kapil
Hi! I'm interested to fix one bug, but I'm new no bugzilla. I want to work in this bug and try to fix it until 30th october. Could someone mentor me?
(In reply to Yussif Barcelos from comment #10) > Hi! I'm interested to fix one bug, but I'm new no bugzilla. I want to work > in this bug and try to fix it until 30th october. Could someone mentor me? Hey Yussif, Thank you for offering to help. One caveat however before we start here - everyone within mozilla is really busy right now due to pressing schedules. You probably won't get lots of timely feedback over a very short period time (now -> Oct 31). I would love to have you work on it, and I'd be happy to mentor you, but I can't promise we'll make your Oct. 31 deadline with this particular bug. If you're still interested in taking a shot at a fix here, please let me know so we can get started.
Hi, if nobody is working on this bug then I would like to take it and like Yussif, I am also new to bugzilla and would require a mentor. Thanks
Hi, Harshil - This is marked as a good first bug, and I see you've got a few under your belt already. I'd prefer to save good-first bugs for people getting involved for the first time. You are well along the path already!
Hello Mike! I'd like to contribute here. Could someone please guide me as to where I'd begin editing the code. Also, I'm on nightly; how do I build Aurora and then simulate the Safe Mode? Thanks a lot!
Hi! I'm looking for first issue to resolve. Can I work onto this bug and also ask for mentoring? :) Regards!
Flags: needinfo?(jmathies)
Given the lack of response and the complete lack of any information about how to reproduce this/solve it, I am removing the [good first bug] annotation.
Whiteboard: [good first bug][lang=c++] → [lang=c++]
Yes sorry, this was my mistake. I don't think this would make a good first bug, the problem is likely pretty complex and may be deep in our gfx / painting code.
Mentor: jmathies, netzen, tabraldes
Flags: needinfo?(jmathies)
Priority: -- → P1
Whiteboard: [lang=c++] → [lang=c++][tpi:+]
I thought that I had fixed this via bug 1006765, but sometimes I still see it.
Priority: P1 → P2
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: