Bug#390630: It's back
Joseph Neal wrote:
> This bug seems to be back with the most recent update of the driver in sid.
>
Strange, it was supposed to be fixed in 2.1.2-6. Current sid is 2.1.3-1,
and there are almost _no_ difference between these packages (our 2.1.2-6
contained all fixes planned for the upcoming 2.1.3). Are you sure it is
the same bug? Can you easily reproduce it? If so, could you downgrade to
2.1.2-6 in testing and check that it does not occur there? Maybe another
package upgrade broke it again...
Brice
Reply to: