Ron, do you mind if we "commandeer" your bug to handle the latest reported cases? We could open a new one, more specific to the use of uvesafb in your configuration, and making it clear enough in the title that it's unmistakably a different problem than anything else?
Josh, I have no history dealing with you or your bug reports. I'm unaware of any of the previous details, but I also happen to be the person to look at these bug reports now. Let's proceed simply and logically. I will de-duplicate your bugs so I can go through the attachments more easily and threat your bug with the attention it deserves -- however, I like I said above I do not have the previous details. It would be helpful if you could point me to the right previous bugs so I can see what the issue has been in the past and how it was resolved -- please do so in your own bug report, bug 1385027. This could also be a very different problem and thus still require that we get additional data from you; and other bugs may come up with a higher priority that I will need to address first.
Since this bug report has a few instances of being noted in daily iso testing, I'm going to keep it at priority Critical. This could be a High, but the workaround isn't necessarily obvious if the computer you'd use to get to see the workaround appears to not be usable.
Documentation on the workaround still needs to happen in the bug report here; in the description.
This stays at confirmed for now and I will try to reproduce with a daily ISO on a system which would more likely exhibit the issue and push to Triage as necessary, or ask for more information here.
Ron, do you mind if we "commandeer" your bug to handle the latest reported cases? We could open a new one, more specific to the use of uvesafb in your configuration, and making it clear enough in the title that it's unmistakably a different problem than anything else?
Josh, I have no history dealing with you or your bug reports. I'm unaware of any of the previous details, but I also happen to be the person to look at these bug reports now. Let's proceed simply and logically. I will de-duplicate your bugs so I can go through the attachments more easily and threat your bug with the attention it deserves -- however, I like I said above I do not have the previous details. It would be helpful if you could point me to the right previous bugs so I can see what the issue has been in the past and how it was resolved -- please do so in your own bug report, bug 1385027. This could also be a very different problem and thus still require that we get additional data from you; and other bugs may come up with a higher priority that I will need to address first.
Since this bug report has a few instances of being noted in daily iso testing, I'm going to keep it at priority Critical. This could be a High, but the workaround isn't necessarily obvious if the computer you'd use to get to see the workaround appears to not be usable.
Documentation on the workaround still needs to happen in the bug report here; in the description.
This stays at confirmed for now and I will try to reproduce with a daily ISO on a system which would more likely exhibit the issue and push to Triage as necessary, or ask for more information here.