tags 352005 - fixed-upstream tags 352005 - fixed tags 352005 + moreinfo reopen 352005 thanks
> I think what I'd like to do is try to duplicate the bug, in hopes of > narrowing down exactly what conditions caused it. This may take a > while, as swapping hardware is inconvenient this week -- perhaps if > somebody reading this is familiar enough with the code to deduce how > K3b displayed its weird error message, they might be able to figure it > out before my hardware level tests could. Ok, that sounds good. I have reopened the bug. Once you have narrowed the problem down, we can submit it again to the upstream developer. > NB: again, I'd like to caution against the mistake of thinking this is > "just a hardware problem", so that it can be safely ignored because > users with the wrong hardware shouldn't blame the software. K3b is a > front end, and by design is meant to insulate users from the > idiosyncrasies of hardware. While it can't turn bad or incompatible > hardware into good or compatible hardware, it can report errors, and it > should do so as accurately as possible. This particular K3b bug is the > error message it displays when it (inevitably I think) encounters buggy > or incompatible hardware. I agree with you. If you've got bad hardware that's your problem and not K3b's. However in order to shift the blame from the front-end to the broken hardware, K3b has to warn you through an appropriate message. Francois -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
