Back to bug 19578
Who | When | What | Removed | Added |
---|---|---|---|---|
gordon.jin | 2009-01-15 06:19:42 UTC | Blocks | 18858 | |
Assignee | gordon.jin | zhenyu.z.wang | ||
Summary | [915gm] X will be black screen after vt switch | [915GM non-DRI] VT->X get black screen | ||
bugs | 2009-01-16 04:41:29 UTC | CC | bugs | |
gordon.jin | 2009-01-18 01:31:20 UTC | Severity | normal | major |
Priority | medium | high | ||
Summary | [915GM non-DRI] VT->X get black screen | VT->X get black screen if non-DRI or UXA | ||
gordon.jin | 2009-01-30 20:21:58 UTC | CC | bjoern.martensen | |
cworth | 2009-02-24 15:49:35 UTC | Blocks | 20276 | |
gordon.jin | 2009-02-24 22:38:53 UTC | Severity | major | critical |
Summary | VT->X get black screen if non-DRI or UXA | [i915] VT->X get black screen if non-DRI or UXA | ||
zhenyu.z.wang | 2009-03-12 08:44:21 UTC | Severity | critical | normal |
Priority | high | medium | ||
zhenyu.z.wang | 2009-03-16 00:06:50 UTC | Status | NEW | RESOLVED |
Resolution | --- | FIXED | ||
jian.j.zhao | 2009-04-01 21:32:19 UTC | Status | RESOLVED | REOPENED |
Resolution | FIXED | --- | ||
cworth | 2009-04-17 10:50:18 UTC | Blocks | 21255 | |
gordon.jin | 2009-04-27 00:01:49 UTC | CC | waldauf | |
mike.lifeguard | 2009-06-01 17:34:15 UTC | CC | mike.lifeguard | |
dr-xorg | 2009-06-04 07:52:25 UTC | CC | dr-xorg | |
gordon.jin | 2009-06-05 16:02:14 UTC | Severity | normal | major |
Priority | medium | high | ||
gordon.jin | 2009-06-23 19:20:29 UTC | CC | zorael | |
zhenyu.z.wang | 2009-06-30 19:23:18 UTC | Status | REOPENED | RESOLVED |
Resolution | --- | FIXED | ||
gordon.jin | 2009-06-30 23:04:03 UTC | Status | RESOLVED | REOPENED |
Resolution | FIXED | --- | ||
zhenyu.z.wang | 2009-07-01 19:10:02 UTC | Status | REOPENED | RESOLVED |
Resolution | --- | FIXED | ||
jian.j.zhao | 2009-07-01 20:16:20 UTC | Status | RESOLVED | VERIFIED |
bugzi11.fdo.tormod | 2009-07-10 12:08:17 UTC | CC | bugzi07.fdo.tormod |
Back to bug 19578
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.