| 2006-11-21 19:34:10 |
John Haitas |
bug |
|
|
added bug |
| 2006-11-21 20:19:22 |
Ben Collins |
linux-meta: status |
Unconfirmed |
Needs Info |
|
| 2006-11-21 20:19:22 |
Ben Collins |
linux-meta: statusexplanation |
|
At the very least, provide what update-manager or apt-get shows when trying to upgrade.
Need more information from you before I can do anything. |
|
| 2006-11-27 19:21:00 |
John Haitas |
bug |
|
|
assigned to coreutils (Ubuntu) |
| 2006-12-04 14:35:53 |
John Haitas |
coreutils: status |
Unconfirmed |
Fix Released |
|
| 2006-12-04 14:35:53 |
John Haitas |
coreutils: statusexplanation |
|
|
|
| 2006-12-04 14:36:49 |
John Haitas |
linux-meta: status |
Needs Info |
Fix Released |
|
| 2006-12-04 14:36:49 |
John Haitas |
linux-meta: statusexplanation |
At the very least, provide what update-manager or apt-get shows when trying to upgrade.
Need more information from you before I can do anything. |
|
|
| 2006-12-06 19:10:11 |
John Haitas |
description |
Binary package hint: linux-restricted-modules-2.6-686
the latest update for feisty broke my x-server... the restricted-modules could not install and i suspect this is the reason... but i am unable to fix it at the moment |
Binary package hint: linux-restricted-modules-2.6-686
the latest update for feisty broke my x-server... the restricted-modules could not install and i suspect this is the reason... but i am unable to fix it at the moment
UPDATE: this was not a problem with nvidia, x, or restricted modules...
it was a bad coreutils package |
|
