This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
It no longers appears to be a problem ( for me at least ) and can be
closed I guess
--
swap vol_id incorrect after some updates
https://bugs.launchpad.net/bugs/97480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Are you still using Feisty or have you upgraded?
--
swap vol_id incorrect after some updates
https://bugs.launchpad.net/bugs/97480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
just upgraded to hardy a few days ago. I was about to file a bug when
I realised this
one was still open.
On Tue, Feb 26, 2008 at 11:40 PM, Brian Murray [EMAIL PROTECTED] wrote:
Are you still using Feisty or have you upgraded?
--
swap vol_id incorrect after some updates
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in recently. We were wondering if this is still and issue
for you? Thanks in advance.
** Changed in: ubuntu
Assignee: (unassigned) =
