| 2008-07-19 22:36:39 |
BC7333 |
bug |
|
|
added bug |
| 2008-07-22 11:08:44 |
BC7333 |
None: status |
New |
Confirmed |
|
| 2008-08-27 13:50:56 |
Ryan Kavanagh |
linux: importance |
Undecided |
High |
|
| 2008-08-27 13:50:56 |
Ryan Kavanagh |
linux: statusexplanation |
Two more things:
1) This bug didn't have a package assigned to it, so I have filed it under "linux" which is for the kernel.
2) For future reference, please don't confirm your own bugs, it is up to others to confirm your bug for you. Since Richard and I both experienced read only file systems, I will leave the bug as Confirmed this time. Though the incarnations of this bug seem to be different, the root cause appears to be the same - the read only file system.
Thanks. |
Prevents X from starting here as well. |
|
| 2008-08-28 16:08:47 |
Leann Ogasawara |
bug |
|
|
added subscriber Leann Ogasawara |
| 2008-09-07 01:41:29 |
Ryan Kavanagh |
linux: status |
Confirmed |
Fix Released |
|
| 2008-09-07 01:41:29 |
Ryan Kavanagh |
linux: statusexplanation |
Prevents X from starting here as well. |
The 2.6.27 solved the problem here, thanks, please reset to Confirmed if you are still experiencing the problem. |
|
| 2008-09-07 20:02:34 |
BC7333 |
linux: status |
Fix Released |
Confirmed |
|
| 2008-09-07 20:02:34 |
BC7333 |
linux: statusexplanation |
The 2.6.27 solved the problem here, thanks, please reset to Confirmed if you are still experiencing the problem. |
Still getting these messages when booting 2.6.27-1 using recovery boot. Can't boot 2.6.27-2 Fully updated alpha5 as of today. |
|
| 2009-04-14 15:10:11 |
Hernando Torque |
removed subscriber Hernando Torque |
|
|
|
| 2009-05-12 07:10:17 |
Amit Kucheria |
linux (Ubuntu): importance |
High |
Undecided |
|
| 2009-05-12 07:10:17 |
Amit Kucheria |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
