F8 k3b problem or just random glitch?

Tom Horsley tom.horsley at att.net
Wed Jun 18 23:19:28 UTC 2008


On Wed, 18 Jun 2008 18:23:28 -0400
Gene Heskett <gene.heskett at verizon.net> wrote:

> I personally am not inclined to blame it on the 
> kernel unless some error message was changed and whatever k3b uses to keep 
> track of that stuff is now getting an answer it doesn't like or doesn't know 
> how to translate.

It sure *seems* like some recent update, if not the kernel itself.
I'm running the same fedora 8 system with the same hardware in which
k3b previously had no problems at least trying to verify, but with
the latest kernel I got the "no tracks" message.

Plus the redhat bugzilla pointed at earlier in this thread says
the bug disappears if an earlier kernel is booted with all else
the same, and that really makes it seem like a kernel issue.




More information about the fedora-list mailing list