Well, I restored my machine by booting with an USB stick and then chrooting
into the affected install. There, I could easily downgrade the package.
However, that's not an 'easy' way: you have to know how to chroot, you have
to have a LiveUSB or -CD, etc.
On Thu, Oct 8, 2009 at 15:51, whoop <email address hidden> wrote:
> Not sure if this log is useful at all because it never
> returned/finished. But maybe that's supposed to happen...
>
> ** Attachment added: "sudo mountall --debug > mountall.log 2>&1"
> http://launchpadlibrarian.net/33298349/mountall.log
>
> ** Changed in: mountall (Ubuntu Karmic)
> Status: Incomplete => New
>
> --
> boot hangs during forced fsck
> https://bugs.launchpad.net/bugs/443080
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Well, I restored my machine by booting with an USB stick and then chrooting
into the affected install. There, I could easily downgrade the package.
However, that's not an 'easy' way: you have to know how to chroot, you have
to have a LiveUSB or -CD, etc.
On Thu, Oct 8, 2009 at 15:51, whoop <email address hidden> wrote:
> Not sure if this log is useful at all because it never launchpadlibrar ian.net/ 33298349/ mountall. log /bugs.launchpad .net/bugs/ 443080
> returned/finished. But maybe that's supposed to happen...
>
> ** Attachment added: "sudo mountall --debug > mountall.log 2>&1"
> http://
>
> ** Changed in: mountall (Ubuntu Karmic)
> Status: Incomplete => New
>
> --
> boot hangs during forced fsck
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>