Back to bug 41976
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| jbarnes | 2012-01-11 10:55:00 UTC | Status | NEW | RESOLVED |
| Resolution | --- | FIXED | ||
| jbarnes | 2012-01-12 09:57:12 UTC | Status | RESOLVED | REOPENED |
| Resolution | FIXED | --- | ||
| gordon.jin | 2012-01-12 22:00:52 UTC | Priority | medium | high |
| Blocks | 44622 | |||
| Severity | normal | major | ||
| kan.liang | 2012-03-14 05:42:55 UTC | CC | kan.liang | |
| chris | 2012-04-24 09:48:18 UTC | Status | REOPENED | RESOLVED |
| Resolution | --- | FIXED | ||
| guang.a.yang | 2012-05-08 20:16:18 UTC | Status | RESOLVED | VERIFIED |
| guang.a.yang | 2012-07-16 06:35:20 UTC | Status | VERIFIED | REOPENED |
| Resolution | FIXED | --- | ||
| kenneth | 2012-08-02 21:11:39 UTC | CC | keithp | |
| kenneth | 2012-08-10 17:37:13 UTC | CC | eugeni | |
| daniel | 2012-08-22 09:03:44 UTC | Status | REOPENED | NEEDINFO |
| CC | damien.intel | |||
| guang.a.yang | 2012-08-23 07:33:41 UTC | Status | NEEDINFO | NEW |
| daniel | 2012-08-23 08:32:59 UTC | Status | NEW | NEEDINFO |
| guang.a.yang | 2012-09-10 07:40:27 UTC | Status | NEEDINFO | NEW |
| yangweix.shui | 2012-11-05 02:10:29 UTC | CC | yangweix.shui | |
| jbarnes | 2012-11-14 17:43:02 UTC | Status | NEW | NEEDINFO |
| guang.a.yang | 2012-11-16 06:44:09 UTC | Status | NEEDINFO | NEW |
| chris | 2012-11-20 18:28:18 UTC | QA Contact | intel-gfx-bugs | |
| jbarnes | 2012-12-11 19:17:21 UTC | Status | NEW | NEEDINFO |
| guang.a.yang | 2012-12-12 02:11:08 UTC | Status | NEEDINFO | NEW |
| daniel | 2012-12-12 08:45:10 UTC | Status | NEW | NEEDINFO |
| guang.a.yang | 2012-12-12 09:22:30 UTC | Status | NEEDINFO | NEW |
| daniel | 2012-12-12 09:24:36 UTC | Status | NEW | RESOLVED |
| Resolution | --- | FIXED | ||
| yi.sun | 2012-12-12 09:34:45 UTC | Status | RESOLVED | VERIFIED |
| elizabethx.de.la.torre.mena | 2017-10-06 14:51:42 UTC | Status | VERIFIED | CLOSED |
Back to bug 41976
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.